[WBEL-users] missing files in /boot

[Richard Swift]

Thanks for the reply. 

No, the machine is not booted... I'll try this asap.  Thanks again for 
your help!


Luke Scharf wrote:

>On Tue, 2004-12-28 at 09:36, Richard Swift wrote:
>  
>
>>I made a big mistake the other day and apparently removed several files 
>>in the /boot directory.  So now I'm contemplating whether I should 
>>reinstall or use this as a learning experience and try to recover from 
>>this error.  I was hoping one of our resident experts could lead me in 
>>the right direction on fixing this problem.  Don't ask why, it was a 
>>totally stupid move on my part, I just need to get passed this, no major 
>>hurry though.
>>    
>>
>
>Is the machine still booted?
>
>If so, look at the output of 'rpm -qa | grep kernel'
>
>Download the RPMs that are referred to by the list.  Then "rpm -F" the
>RPMs you downloaded.
>
>If you're brave AND lazy, do the following:
># rpm -qa | grep kernel | egrep -v 'utils|pcmcia' > list.txt
># rpm -e `cat list.txt`
>	// --nodeps may be required
># yum install `cat list.txt`
>	// Some editing of the list may be required; version numbers
>	// may need to be removed.
>
>If the machine is not booted, you can work off of a variation of the
>following process:
>     1.  oot up off the install CD, and let the installer start the
>        network and mount the volumes for you.
>     2. Get your bearings -- "df -h" or "mount" should tell you were
>        it's the system is mounted.  It's usually /mnt/sysimage, and the
>        rest of the stuff is the install CD.
>     3. Get your bearings some more -- check the network setup by typing
>        "ifconfig"
>     4. Change into your system with chroot.  The command is usually
>        something like "chroot /mnt/sysimage", and then perform the
>        above steps.
>
>Please note that I'm outlining the process here and working from
>memory.  There may be some quirky little details that I've left out.
>
>I hope this helps!
>-Luke
>
>  
>