Tim wrote: > heh, it wont even boot on my athlon let alone be stable
I had to use the test (potato) boot disks, I believe. The problem is just that the old kernels won't boot athlon. Compile a new kernel (the latest 2.2.x should do) and make a boot disk (dunno how to make a bootdisk using the .deb) and you can boot and install from that. llama:~# uname -a Linux llama 2.2.13 #1 Wed Oct 20 21:20:58 EST 1999 i686 unknown llama:~# dmesg | head Linux version 2.2.13 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #1 Wed Oct 20 21:20:58 EST 1999 Detected 598863126 Hz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 596.38 BogoMIPS Memory: 128000k/131072k available (984k kernel code, 416k reserved, 1632k data, 40k init) VFS: Diskquotas version dquot_6.4.0 initialized L1 I Cache: 64K L1 D Cache: 64K L2 Cache: 512K CPU: AMD AMD-K7(tm) Processor stepping 02 Checking 386/387 coupling... OK, FPU using exception 16 error reporting. llama:~# uptime 10:06am up 8 days, 37 min, 4 users, load average: 0.00, 0.00, 0.00 It should be good for a few more weeks, then squid will getting flaky, the hard drive will start printing messages like "unreferenced inode foo count X should be Y", and you'll get a few Oops 0's every now and again. You can fsck the disk, but without a reboot it'll only give it another day or two max. Christopher
