Last night I was doing a big 'emerge -u --deep world' but wanted to go 
to bed and *didn't* want to leave my computer on all night.  So I just 
hit 'CRTL-C' and figured that I'd finish the building later.  It's not 
like I was building anything crucial to the system.

This morning when I booted up to check email, I was slammed with all 
kinds of errors and the system wouldn't boot.  I've been *very* lucky 
with Linux systems so even though I've been a sys admin for a few years, 
I have very little experience recovering machines.

So step 1 was figuring out grub to get it to boot into single-user mode.  
The last time I had to boot into single-user mode was when I was still 
using LILO.  Anyway, it wasn't very difficult at all.

After I booted the kernel, I still got slammed with a bunch of errors 
and it looked like devfs wasn't being loaded.  But in single user mode 
I was promted to enter 'Crtl-D for normal bootup or the root password 
for maintainance'.  I entered the root password and I've got a shell.  
yippie!

So as I poke around I notice that the root filesystem is still mounted 
read only even though mount clearly shows it mounted "(rw)".  So I 
remount the root filesystem:

mount -o remount,rw /dev/hda2 

Simple enough.  I wanted to get networking up and running so before I
loaded the natsemi module I ran a 'depmod -a' and it came back with
unresolved symbols for the emu10k1 module.  That led me to belive that
there was a problem with my emerge last night because one of the
packages that I installed was an update to the emu10k1-utils (or
something like that??).  So I did an 'emerge -s emu10k1' and saw that 
two versions were loaded.  So I unmerged the old one and at the very end 
it says, "You have 34 config files to update" (or whatever the message 
is, I forgot now that I'm at work...)

And there's the problem.  One of the other updates I did last night was 
baselayout and that changed damn near everything.  So I quickly ran 
through etc-update, rebooted and the system was back up in running.  So 
as usual, it's not Gentoo's fault, just user error.  :)

later,
ajay

--------------------------------------------------------------------
Satyajot (Ajay) Sharma 
[EMAIL PROTECTED]
--------------------------------------------------------------------


--
[EMAIL PROTECTED] mailing list

Reply via email to