i'm reminded of yesterday's run every time i move.
[ IF UNIX IS BORING SKIP A FEW PARAGRAPHS ]
last night's computer switch-up definitely went too smoothly. this morning, i discovered that the router's sshd was non-responsive, although it was still routing our internet like a trooper. a check of the console revealed some "bad slab" errors with some page this or kmem that. making it do anything too hard caused a panic. i thought that maybe the kernel was to blame - since i didn't know if it had the right ide driver. so i built a "new" one - 2.2.23 - and that panicked before it got a whole page of output out.
so i did what any sane person would do: decided to put phoebe 3 on it (i had a backup of it already so i wasn't too concerned with killing it's state). well, i couldn't get it to boot from a floppy, so i installed it on the k6-300, then moved the hard drive over. booted it and... instant panic.
so, i figure at this point it might be a ram problem. so i took out the simms (i don't know what masochist designed those things) and tried to put in a dimm from serendipity. it didn't fit, so i put in the 2 32M simms from serendipity instead. boots perfectly.
[ THE NON-UNIX PART ]
at this point phil came over and we had some tasty indian food. the plan for when shaver and zach come here in march is to get a few dishes from the indian, thai, and vietnamese places nearby and eat until our stomachs burst. i am very excited about this plan.
[ UNIX BITS CONT. ]
then it was back home, to try to get dhcp/dns/masquerading set up on the new install. this took a very long amount of time. i don't remember what took so long, but i think i was distracted by phil's constant whining. it turns out that the tulip card just won't get a dhcp lease from the cablemodem; we have to connect the 3com card to it (funny, it's a 3com modem). and before you suggest that the cablemodem needs the 3com card's mac address, my powerbook and the airport can both dhcp from the cablemodem without a problem.
anyway i finally got it up, and now our network is working flawlessly.
if only i could say the same for my lustre kernels...
they just won't boot. if i'm lucky, i can get to "Uncompressing Linux... Ok, now booting the kernel..." before it goes back to the POST. otherwise it reboots instantly. phil will blame the cross-compiler, but i'm not so convinced.
(incidently, grubby seg faults when i try to run installkernel. go unix!)
it reboots with a cross-compiled kernel, with a normal kernel, with kernel built for the k6, with a kernel built for a 386. i'm building a lustre kernel with a .config from mgalgoci (i don't know what this is supposed to do), and then i have a cross compiled phoebe2 kernel waiting. and then i'm promptly going to bed.
also:
- when i was messing with usb and killed my sun keyboard, i think i also killed my usb floppy drive.
- ...which makes it hard to install linux on my vaio. phoebe3 no worky with my pcmcia cd drive, and i can't get any network drivers w/o the floppy drive. so i might just do a hard drive install (again).
- oj was $2 off (for a 3 quart thing) at the store.
i really have no idea what i was doing before, but the kernels i'm building now seem to work fine. traditionally, i have a night's sleep in between the "i have no idea what's going on" phase and the "what was i thinking?" phase.
there is some bastardization of swsusp in the lustre kernel, but it doesn't build right. i got a nasty merge of the latest 2.4.18 patch to build, but it doesn't suspend. the good news is that with apm, it powers off, so when i do (note confidence) get swsusp working, i won't have to guess when it's done: the box should just turn off.
this may not be exciting to some of you, but i never had an ATX case so it's a nice change for me. although my mac and laptops do it.
i can see the lustre team being thrilled by my swsusp and cross-compiling patches. i think those are the only things keeping them from a 1.0 release.
yikes it's 7 am.