now fscking
Oct. 30th, 2006 03:54![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
piranhagot past the weird lilo error in the last post. but i think in my tiredness i screwed something else up because now the system hangs ... oh, it didn't. it just had a problem with one of the partitions. hrm. wonder why. anyway, that's just my image drive, so i don't care, OMG, it's done booting. it works!
ok, now to give it back its ADSL.
what i did to fix it :
i made a very nice boot CD, of which i will now burn a backup. also, the .iso is stored on drynwyn's desktop right now, whence it should really be moved, to some other place on drynwyn.
then i mounted aegis' actual root partition, and had a look around. checked the logs, but everything looked normal. so i figured that maybe the simplest thing to start with would be to just re-run lilo. i remounted everything under the actual root mountpoint, and then
which did the trick. i don't really understand, since AFAIK i didn't build a new kernel and forgot to run lilo. next wake cycle if it happens to overlap with your sleep cycle i'm gonna upgrade the system and see whether anything odd happens.
note that the IP address will probably change now that the system has been off the network for so many hours.
ok, now to give it back its ADSL.
what i did to fix it :
i made a very nice boot CD, of which i will now burn a backup. also, the .iso is stored on drynwyn's desktop right now, whence it should really be moved, to some other place on drynwyn.
then i mounted aegis' actual root partition, and had a look around. checked the logs, but everything looked normal. so i figured that maybe the simplest thing to start with would be to just re-run lilo. i remounted everything under the actual root mountpoint, and then
chroot /actualroot /sbin/lilo -vwhich did the trick. i don't really understand, since AFAIK i didn't build a new kernel and forgot to run lilo. next wake cycle if it happens to overlap with your sleep cycle i'm gonna upgrade the system and see whether anything odd happens.
note that the IP address will probably change now that the system has been off the network for so many hours.