What _not_ to do with your Linux box :)
I just had an eventful (read: heart-attack) little upgrade! I decided to hop from 2.6.6-rc3 to 2.6.6. Sounds simple, right? Well, I accidentally wiped out my configs from the last kernel version. No biggy, I'll just redo them from memory, eh?
Heh.
I have my /usr mounted on an ext3 partition on my 120gig drive. My OS partitions (all 4 of em) are on my 40gig drive. When I redid my kernel config, I decided that since the partitions on my 40gig are ReiserFS, that I'd make ext2 and ext3 modules. lsmod and modprobe are on my 120gig drive (the /usr partition).
Does anyone else see the fun inherent in this? ;)
In any case, I used Knoppix to rebuild the kernel, which failed anyways, so I stepped back to 2.6.5 and did several make mrpropers and rebuilds.
It works now, even if the nVidia module started going all flaky.
In any case, moral of the story is: Pay attention when you're playing with your kernel for pete's sake!
Next fun project: Putting GCC up to current version (I'm on 3.3.1) I bet that'll give me all _sorts_ of wonderful dependency problems :D
Heh.
I have my /usr mounted on an ext3 partition on my 120gig drive. My OS partitions (all 4 of em) are on my 40gig drive. When I redid my kernel config, I decided that since the partitions on my 40gig are ReiserFS, that I'd make ext2 and ext3 modules. lsmod and modprobe are on my 120gig drive (the /usr partition).
Does anyone else see the fun inherent in this? ;)
In any case, I used Knoppix to rebuild the kernel, which failed anyways, so I stepped back to 2.6.5 and did several make mrpropers and rebuilds.
It works now, even if the nVidia module started going all flaky.
In any case, moral of the story is: Pay attention when you're playing with your kernel for pete's sake!
Next fun project: Putting GCC up to current version (I'm on 3.3.1) I bet that'll give me all _sorts_ of wonderful dependency problems :D
