17" and 19" inch iMacs Coming in 3Q

ikioi writes "It looks like Apple will have 17" and 19" flat panel iMacs later this year." It's funny- the publicity photos of the 15 inch macs really make it look a lot nicer then it is. I finally saw one up close a few weeks ago- the arm and screen is super smooth, but the base looks like a cheap toy. That said, larger screens for the iMac definitely push it into a new territory... not sure if it would convince me to buy one, but it sure would add magic shell to the ice cream.

Comments

Dear Apple

[Anonymous Coward]

Dear Apple,

I am a homosexual. I bought an Apple computer because of its well earned reputation for being "the" gay computer. Since I have become an Apple owner, I have been exposed to a whole new world of gay friends. It is really a pleasure to meet and compute with other homos such as myself. I plan on using my new Apple computer as a way to entice and recruit young schoolboys into the homosexual lifestyle; it would be so helpful if you could produce more software which would appeal to young boys. Thanks in advance.

with much. gayness,

Father Randy O'Day, S.J.

Re:Flamebait

[Ti_Uhl]

what's ur problem ur gay... so quit nagging about apple :)

Well, DUH!

[jonr]

What next here at apple.slashdot.org? Faster iMacs coming? With bigger hard drives? More memory? Heaven forbid that Apple updates their models!

Hope this helps

[Genghis Troll]

1. Installing and using gcc 2.1 Your post has too few characters per line
- Your post has too few characters per line
Your post has too few characters per line
The information in this section is all from the gcc 2.1 FAQ (available Your post has too few characters per line
at tsx-11 and other archive sites). You should get this document and Your post has too few characters per line
read it well. It is clear and very informative. Your post has too few characters per line
Your post has too few characters per line
GCC 2.1 WILL NOT WORK WITH PRE 0.95 KERNELS. IT REQUIRES AT LEAST 2MB Your post has too few characters per line
of RAM AND AT LEAST 4MB OF SWAP SPACE. Your post has too few characters per line
Your post has too few characters per line
n.b. I did this while still running 0.95a with ps patches. Your post has too few characters per line
Your post has too few characters per line
Your post has too few characters per line
Q1. Which files do I need? Your post has too few characters per line
Your post has too few characters per line
A1. 2.1lib.tar.Z Your post has too few characters per line
2.1misc.tar.Z. Your post has too few characters per line
binutils.tar.Z, Your post has too few characters per line
2.1shared-x.tar.Z. Your post has too few characters per line
Gcc 2.1 FAQ <- essential! Your post has too few characters per line
Your post has too few characters per line
Your post has too few characters per line
Q2. What are the contents of them? Your post has too few characters per line
Your post has too few characters per line
A2. - 2.1lib.tar.Z contains cc1, cc1plus and cpp. Your post has too few characters per line
- 2.1misc.tar.Z contains gcc 2.1 drivers, header files, libraries, Your post has too few characters per line
manual pages and installation instructions. Your post has too few characters per line
- binutils.tar.Z contains binaries needed to run gcc 2.1 Your post has too few characters per line
- 2.1shared-x.tar.Z ..... erm, not to sure about this one. It Your post has too few characters per line
contains some example precompiled shared libs stuff I think. Your post has too few characters per line
Your post has too few characters per line
Your post has too few characters per line
Installation Your post has too few characters per line
Your post has too few characters per line
Your post has too few characters per line
1. Backup your old compiler. As root I went into /usr/bin, Your post has too few characters per line
/usr/local/bin, /usr/local/lib and /usr/include and put all the gcc Your post has too few characters per line
related stuff into a tar file (tar -cf tarfile file-to-archive for the Your post has too few characters per line
first file and then tar -rf tarfile file-to-archive for all the rest). Your post has too few characters per line
Your post has too few characters per line
Do NOT throw this tar file away yet 'cos you may need part of it (or Your post has too few characters per line
if nothing works, all of it). Your post has too few characters per line
Your post has too few characters per line
You should not have any C compiler on your system when you install Your post has too few characters per line
2.1 (it has caused problems apparently). Your post has too few characters per line
Your post has too few characters per line
2. From this point I will assume that xxxx is the directory where you Your post has too few characters per line
have put the gcc 2.1 tar files. For me this was /tmp/new/gcc2.1. Your post has too few characters per line
Type Your post has too few characters per line
Your post has too few characters per line
# cd /usr Your post has too few characters per line
# tar xvpfz xxxx/2.1misc.tar.Z Your post has too few characters per line
Your post has too few characters per line
If you tar doesn't support the z option then uncompress the tar Your post has too few characters per line
file before doing this and think about getting a better version. I Your post has too few characters per line
use version 1.10 without problems (tar +version reports the version Your post has too few characters per line
details) Your post has too few characters per line
Your post has too few characters per line
3. Read the FAQ in /usr/install/gcc2. This appears to be the same one Your post has too few characters per line
as is at the archive sites but it doesn't hurt to have a look Your post has too few characters per line
through it. When you've finished type Your post has too few characters per line
Your post has too few characters per line
# cd /usr Your post has too few characters per line
# tar xvpfz xxxx/2.1lib.tar.Z Your post has too few characters per line
Your post has too few characters per line
4. Run the installation script (took a bit of finding this one!) by Your post has too few characters per line
typing Your post has too few characters per line
Your post has too few characters per line
# cd /usr/install/gcc2 Your post has too few characters per line
# inst2.x Your post has too few characters per line
Your post has too few characters per line
If this doesn't do anything check that you have execute permission Your post has too few characters per line
set for it (chmod u+x inst2.x will make sure!). Note that you need Your post has too few characters per line
the contents of binutils.tar.Z for this so if necessary type Your post has too few characters per line
Your post has too few characters per line
# cd /usr Your post has too few characters per line
# tar xvpfz xxxx/binutils.tar.Z Your post has too few characters per line
Your post has too few characters per line
before trying again. Your post has too few characters per line
Your post has too few characters per line
That's it! You now has gcc 2.1 installed on your system. My first test Your post has too few characters per line
was on some code that I'm working on and it failed abysmally with a Your post has too few characters per line
fatal signal 11 (internal compiler error) from ld. I renamed /usr/bin/ld Your post has too few characters per line
to /usr/bin/ld2.1 and retrieved my old ld from the tar file (ld-old in Your post has too few characters per line
the archives is equivalent). I made this /usr/bin/ld and everything Your post has too few characters per line
compiled properly. Your post has too few characters per line
Your post has too few characters per line
Your post has too few characters per line
2. Installing and rebuilding the linux v0.95c+ kernel using gcc 2.1 Your post has too few characters per line
- Your post has too few characters per line
Your post has too few characters per line
Full source code for the linux kernel is available at the archive sites Your post has too few characters per line
and it is useful to know how to rebuild the kernel from this code. This Your post has too few characters per line
is very easy to do. Your post has too few characters per line
Your post has too few characters per line
You will need - the kernel source for the latest version (0.95c+) Your post has too few characters per line
- gcc 2.1 Your post has too few characters per line
- a working copy of make (I use pmake from the archives) Your post has too few characters per line
- 1.5 - 2 Mb of free disk space Your post has too few characters per line
- gcc 2.1 FAQ (read the bit about a.out.h!) Your post has too few characters per line
Your post has too few characters per line
n.b. you need the old ld to compile the kernel (even while running Your post has too few characters per line
under 95c+ with a.out.h changed it seems). Your post has too few characters per line
Your post has too few characters per line
Your post has too few characters per line
The standard place for the linux source tree is in /usr/src/linux so Your post has too few characters per line
if you don't have a /usr/src directory you will need to create one Your post has too few characters per line
with mkdir. Once you have done this move the tar file of the kernel Your post has too few characters per line
source (probably called linux-0.95c+.tar.Z) to /usr/src and type Your post has too few characters per line
Your post has too few characters per line
tar -xzvf linux-0.95a.tar.Z Your post has too few characters per line
Your post has too few characters per line
You should see a whole load of file names flashing by on the screen. Your post has too few characters per line
This is good. When tar finishes you should have a directory called Your post has too few characters per line
/usr/src/linux and this will have a number of subdirectories. You will Your post has too few characters per line
probably want to hang on to the original tar in case you want an Your post has too few characters per line
original source tree. Your post has too few characters per line
Your post has too few characters per line
You might want to make a few small changes to the kernel source tree Your post has too few characters per line
at the point. Your post has too few characters per line
Your post has too few characters per line
1. In the master makefile (/usr/src/linux/Makefile) you should choose Your post has too few characters per line
the keyboard definition that suits you (round about line 12). For Your post has too few characters per line
me this means changing Your post has too few characters per line
Your post has too few characters per line
Your post has too few characters per line
# KEYBOARD = -DKBD_FINNISH Your post has too few characters per line
KEYBOARD = -DKBD_US Your post has too few characters per line
# KEYBOARD = -DKBD_GR Your post has too few characters per line
# KEYBOARD = -DKBD_FR Your post has too few characters per line
# KEYBOARD = -DKBD_UK Your post has too few characters per line
# KEYBOARD = -DKBD_DK Your post has too few characters per line
Your post has too few characters per line
to Your post has too few characters per line
Your post has too few characters per line
# KEYBOARD = -DKBD_FINNISH Your post has too few characters per line
# KEYBOARD = -DKBD_US Your post has too few characters per line
# KEYBOARD = -DKBD_GR Your post has too few characters per line
# KEYBOARD = -DKBD_FR Your post has too few characters per line
KEYBOARD = -DKBD_UK Your post has too few characters per line
# KEYBOARD = -DKBD_DK Your post has too few characters per line
Your post has too few characters per line
Your post has too few characters per line
You should also tell make what your root device is by editing the bit Your post has too few characters per line
that looks like this Your post has too few characters per line
Your post has too few characters per line
# Your post has too few characters per line
# ROOT_DEV specifies the default root-device when making the image. Your post has too few characters per line
# This can be either FLOPPY, /dev/xxxx or empty, in which case the Your post has too few characters per line
# default of FLOPPY is used by 'build'. Your post has too few characters per line
# Your post has too few characters per line
Your post has too few characters per line
# ROOT_DEV = /dev/hdb1 Your post has too few characters per line
Your post has too few characters per line
so that the rootdev entry matches what you use (the bit you ran mkfs Your post has too few characters per line
for). In mine I have the line Your post has too few characters per line
Your post has too few characters per line
ROOT_DEV = /dev/hda2 Your post has too few characters per line
Your post has too few characters per line
Ok, now making sure that you are /usr/src/linux type Your post has too few characters per line
Your post has too few characters per line
make Your post has too few characters per line
Your post has too few characters per line
If your compiler is set up properly you should see something that Your post has too few characters per line
looks like this Your post has too few characters per line
Your post has too few characters per line
Your post has too few characters per line
expr: not found Your post has too few characters per line
[: syntax error Your post has too few characters per line
Usage: date [-q] [[MMDDYY]hhmm[ss]] Your post has too few characters per line
touch include/linux/config.h Your post has too few characters per line
cpp -nostdinc -Iinclude -traditional boot/bootsect.S -o boot/bootsect.s Your post has too few characters per line
as86 -0 -a -o boot/bootsect.o boot/bootsect.s Your post has too few characters per line
ld86 -0 -s -o boot/bootsect boot/bootsect.o Your post has too few characters per line
cpp -nostdinc -Iinclude -traditional boot/setup.S -o boot/setup.s Your post has too few characters per line
as86 -0 -a -o boot/setup.o boot/setup.s Your post has too few characters per line
ld86 -0 -s -o boot/setup boot/setup.o Your post has too few characters per line
as -c -o boot/head.o boot/head.s Your post has too few characters per line
gcc -Wall -O6 -fomit-frame-pointer -nostdinc -Iinclude -c -o init/main.o init/main.c Your post has too few characters per line
init/main.c:23: warning: `fork' declarations disagree about `inline' Your post has too few characters per line
init/main.c:23: warning: static declaration for `fork' follows non-static Your post has too few characters per line
init/main.c:24: warning: `pause' declarations disagree about `inline' Your post has too few characters per line
init/main.c:24: warning: static declaration for `pause' follows non-static Your post has too few characters per line
init/main.c:26: warning: `sync' declarations disagree about `inline' Your post has too few characters per line
init/main.c:26: warning: static declaration for `sync' follows non-static Your post has too few characters per line
init/main.c:46: warning: `strcpy' declarations disagree about `inline' Your post has too few characters per line
init/main.c:184: warning: static declaration for `printf' follows non-static Your post has too few characters per line
(cd kernel; make CFLAGS="-Wall -O6 -fomit-frame-pointer ") Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -fno-omit-frame-pointer -c sched.c Your post has too few characters per line
as -c -o sys_call.o sys_call.s Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o traps.o traps.c Your post has too few characters per line
as -c -o asm.o asm.s Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o fork.o fork.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o panic.o panic.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o printk.o printk.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o vsprintf.o vsprintf.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o sys.o sys.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o exit.o exit.c Your post has too few characters per line
exit.c: In function `do_exit': Your post has too few characters per line
exit.c:367: warning: `volatile' function does return Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o signal.o signal.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o mktime.o mktime.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o ptrace.o ptrace.c Your post has too few characters per line
ld -r -o kernel.o sched.o sys_call.o traps.o asm.o fork.o panic.o printk.o vsprintf.o sys.o exit.o signal.o mktime.o ptrace.o Your post has too few characters per line
sync Your post has too few characters per line
(cd mm; make CFLAGS="-Wall -O6 -fomit-frame-pointer ") Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o memory.o memory.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o swap.o swap.c Your post has too few characters per line
ld -r -o mm.o memory.o swap.o Your post has too few characters per line
(cd fs; make CFLAGS="-Wall -O6 -fomit-frame-pointer ") Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o open.o open.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o read_write.o read_write.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o inode.o inode.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o file_table.o file_table.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o buffer.o buffer.c Your post has too few characters per line
buffer.c: In function `check_disk_change': Your post has too few characters per line
buffer.c:124: warning: implicit declaration of function `put_super' Your post has too few characters per line
buffer.c:125: warning: implicit declaration of function `invalidate_inodes' Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o super.o super.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o block_dev.o block_dev.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o char_dev.o char_dev.c Your post has too few characters per line
char_dev.c: In function `rw_mem': Your post has too few characters per line
char_dev.c:65: warning: implicit declaration of function `un_wp_page' Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o stat.o stat.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o exec.o exec.c Your post has too few characters per line
exec.c: In function `copy_strings': Your post has too few characters per line
exec.c:130: warning: `pag' may be used uninitialized in this function Your post has too few characters per line
exec.c: In function `do_execve': Your post has too few characters per line
exec.c:393: warning: implicit declaration of function `send_sig' Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o pipe.o pipe.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o namei.o namei.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o fcntl.o fcntl.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o ioctl.o ioctl.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o select.o select.c Your post has too few characters per line
ld -r -o fs.o open.o read_write.o inode.o file_table.o buffer.o super.o block_dev.o char_dev.o stat.o exec.o pipe.o namei.o fcntl.o ioctl.o select.o Your post has too few characters per line
(cd fs/minix; make CFLAGS="-Wall -O6 -fomit-frame-pointer ") Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o minix_op.o minix_op.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o bitmap.o bitmap.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o truncate.o truncate.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o namei.o namei.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o inode.o inode.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o file_dev.o file_dev.c Your post has too few characters per line
ld -r -o minix.o minix_op.o bitmap.o truncate.o namei.o inode.o file_dev.o Your post has too few characters per line
(cd kernel/blk_drv; make CFLAGS="-Wall -O6 -fomit-frame-pointer ") Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o ll_rw_blk.o ll_rw_blk.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o floppy.o floppy.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o hd.o hd.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o ramdisk.o ramdisk.c Your post has too few characters per line
ar rcs blk_drv.a ll_rw_blk.o floppy.o hd.o ramdisk.o Your post has too few characters per line
sync Your post has too few characters per line
(cd kernel/chr_drv; make CFLAGS="-Wall -O6 -fomit-frame-pointer " KEYBOARD="-DKBD_UK") Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o tty_io.o tty_io.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o console.o console.c Your post has too few characters per line
console.c: In function `con_write': Your post has too few characters per line
console.c:815: warning: empty body in an else-statement Your post has too few characters per line
console.c:815: warning: empty body in an else-statement Your post has too few characters per line
cpp -nostdinc -I../../include -DKBD_UK -traditional keyboard.S -o keyboard.s Your post has too few characters per line
as -c -o keyboard.o keyboard.s Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o serial.o serial.c Your post has too few characters per line
as -c -o rs_io.o rs_io.s Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o tty_ioctl.o tty_ioctl.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o pty.o pty.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -c -o lp.o lp.c Your post has too few characters per line
ar rcs chr_drv.a tty_io.o console.o keyboard.o serial.o rs_io.o tty_ioctl.o pty.o lp.o Your post has too few characters per line
sync Your post has too few characters per line
(cd kernel/math; make CFLAGS="-Wall -O6 -fomit-frame-pointer " MATH_EMULATION="-DKERNEL_MATH_EMULATION") Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -DKERNEL_MATH_EMULATION -c -o emulate.o emulate.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -DKERNEL_MATH_EMULATION -c -o error.o error.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -DKERNEL_MATH_EMULATION -c -o convert.o convert.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -DKERNEL_MATH_EMULATION -c -o ea.o ea.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -DKERNEL_MATH_EMULATION -c -o get_put.o get_put.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -DKERNEL_MATH_EMULATION -c -o add.o add.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -DKERNEL_MATH_EMULATION -c -o mul.o mul.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -DKERNEL_MATH_EMULATION -c -o div.o div.c Your post has too few characters per line
gcc -nostdinc -I../../include -Wall -O6 -fomit-frame-pointer -DKERNEL_MATH_EMULATION -c -o compare.o compare.c Your post has too few characters per line
ar rcs math.a emulate.o error.o convert.o ea.o get_put.o add.o mul.o div.o compare.o Your post has too few characters per line
sync Your post has too few characters per line
(cd lib; make CFLAGS="-Wall -O6 -fomit-frame-pointer ") Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o ctype.o ctype.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o _exit.o _exit.c Your post has too few characters per line
_exit.c: In function `_exit': Your post has too few characters per line
_exit.c:14: warning: `volatile' function does return Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o open.o open.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o close.o close.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o errno.o errno.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o write.o write.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o dup.o dup.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o setsid.o setsid.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o execve.o execve.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o wait.o wait.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o string.o string.c Your post has too few characters per line
gcc -nostdinc -I../include -Wall -O6 -fomit-frame-pointer -c -o malloc.o malloc.c Your post has too few characters per line
ar rcs lib.a ctype.o _exit.o open.o close.o errno.o write.o dup.o setsid.o execve.o wait.o string.o malloc.o Your post has too few characters per line
sync Your post has too few characters per line
ld -M boot/head.o init/main.o kernel/kernel.o mm/mm.o fs/fs.o fs/minix/minix.o kernel/blk_drv/blk_drv.a kernel/chr_drv/chr_drv.a kernel/math/math.a lib/lib.a -o tools/system > System.map Your post has too few characters per line
gcc -Wall -O6 -fomit-frame-pointer -o tools/build tools/build.c Your post has too few characters per line
cp tools/system system.tmp Your post has too few characters per line
strip system.tmp Your post has too few characters per line
tools/build boot/bootsect boot/setup system.tmp /dev/hda2 > Image Your post has too few characters per line
Root device is (3, 2) Your post has too few characters per line
Boot sector 512 bytes. Your post has too few characters per line
Setup is 1456 bytes. Your post has too few characters per line
System is 188420 bytes. Your post has too few characters per line
rm system.tmp Your post has too few characters per line
sync Your post has too few characters per line
Your post has too few characters per line
Your post has too few characters per line
This takes about 7 minutes on my machine (heavily cached 386-33 with Your post has too few characters per line
8Mb Ram) and seems to use up to about 2.5Mb of memory. Don't worry about Your post has too few characters per line
the expr bit at the start. Expr is in the gnu shell utils 1.6 release Your post has too few characters per line
and is needed for compiling c++ code. You do not NEED it to rebuild Your post has too few characters per line
the 0.95c kernel (but it would make it slightly aesthetically more Your post has too few characters per line
pleasing I suppose :-)). Before anyone asks, no I don't know where you Your post has too few characters per line
can find the shell utils 1.6 (perhaps the gcc2.1 FAQ should indicate Your post has too few characters per line
this). There may be a copy somewhere in the Linux archives (don't Your post has too few characters per line
remember seeing one) but if not you should be able to get the original Your post has too few characters per line
from ftp.gnu.ai.mit.edu. Your post has too few characters per line
Your post has too few characters per line
N.b. don't worry if it seems to hang while compiling floppy.c.... give Your post has too few characters per line
it a few seconds and it should burst back into life.... it's thinking :-) Your post has too few characters per line
Your post has too few characters per line
If it gets all the way through there will be a file called Image Your post has too few characters per line
created in /usr/src/linux. This is the new bootimage and you can put Your post has too few characters per line
it onto a floppy in /dev/PS0 (a 3.5" 1.44Mb floppy on my machine) by Your post has too few characters per line
typing Your post has too few characters per line
Your post has too few characters per line
dd bs=8192 if=Image of=/dev/PS0 Your post has too few characters per line
Your post has too few characters per line
You can do this automatically by typing make disk instead of make Your post has too few characters per line
(above) if you wish. Your post has too few characters per line
Your post has too few characters per line
Congratulations! You have just rebuilt the linux kernel and created a Your post has too few characters per line
new boot floppy. Time to sync, reboot your machine and test it. I Your post has too few characters per line
hope you didn't overwrite your original bootimage; 'cos if you did then Your post has too few characters per line
what are going to use to boot up if the new bootimage is faulty?? Ah, Your post has too few characters per line
the value of forward planning :-) Your post has too few characters per line
- Your post has too few characters per line
Your post has too few characters per line
What now? Your post has too few characters per line
Your post has too few characters per line
You probably want to compile ps (process status) now. There is a Your post has too few characters per line
version of this for 2.1 but it refused to compile for me and Your post has too few characters per line
complained about missing structure members. I don't intend to pursue Your post has too few characters per line
this 'cos my old version of ps (as compiled for 0.95a) works a treat Your post has too few characters per line
with the new kernel! Your post has too few characters per line
Your post has too few characters per line

Re:Ugly.

[jukal]

> Then there is the "13373r 7h4n y00" market segment ...(that would be you)

Woo-haa! Good bait, two fishes already. Reel'em in! :)))

icraped

[Anonymous Coward]

ihate imy iimac. iit iwas ito iexpensive iand iit igave ime ia icrippled iversion iof iunix. imacs iare ijust icrap iso ihate iwhat icomes iout imy ianus.

Re:Flamebait

[skinfitz]

Yeah - lets ramp the price right up for a rackmount machine that no one is going to see when it's mounted in the switchroom. Another great overpriced idea from Apple.

I like goats

[cmdr_shithead]

that is all.

###GOAT###

Lord Job's would not like that

[Minter92]

"but the base looks like a cheap toy"

How dare you say that? The imac is the most beautiful piece of machinary ever devised. Except maybe the ipod or or the powermac... or maybe.. the macse and the lisa.. I would say more but I must clean lord Job's toliet.

Can't resist calling them Niggers.

[BitGeek]

You said:
I don't hate the iMac, I think it's just a piece of hardware. But sometimes I just cannot resist throwing baits at the mac lovers, who don't seem to think it is just that - hardware.

What you said, essentially means:
I don't hate the dark skin, I think it's just a skin color. But sometimes I just cannot resist throwing baits at the Nigger lovers, who don't seem to think it is just that - skin color.

Do you now see what people rise to that "bait"? Why people take it seriously?

It is a prejudice and it a prejudice that has real effects--- products don't get ported, you get passed over for jobs, you deal with derision and what is essentially hatred, in a variety of contexts-- airports when you pull our your power book, online when you deal with bigots like you, etc. etc.

We are no more "zeolots" than MLK was. We deserve recognition for having the content of our character to use a better ,though "unpopular" tool instead of conforming to your political correctness.

Think about it.