[CLUE-Talk] Recovering from loss of /boot directory on Slackware

[Timothy C. Klein]

I just did this last week, on accident.  Go figure.  I thought it was
bad, but it turned out to be no big deal.  I didn't even have to go to
backups.  Most those file were included in the LILO deb for Debian.
If you use RPMs, hopefully it is the same way.  So reinstall lilo from
RPM or deb.  Then get the System.Map, config, and bzImage from your
kernel source tree.  Then rerun lilo, it will recreate a couple of files
(chain.b was it?)  I don't think you actually need the os2_d.b.  The
only really one that can't be recovered is the boot.0300.  That is a
back up of your boot sector before lilo ran, in case you wanted to
restore it later.  For me, that was useless.  But if that wasn't backed
up, you can't get it back.

HTH

Tim
* BOF (bof at pcisys.net) wrote:
> Hello,
> 
> Through a series of events so egregious that they cannot be repeated 
> where small children may read them <g>, I managed to delete the /boot 
> directory on my Slackware 8.0 system.
> 
> I can recover the System.map file from my last kernel recompile. But 
> what would be the most graceful way to restore files like boot.b, 
> boot.0300, chain.b, map and os2_d.b?
> 
> Thanx.
> 
> BOF
> 
> _______________________________________________
> CLUE-Talk mailing list
> CLUE-Talk at clue.denver.co.us
> http://clue.denver.co.us/mailman/listinfo/clue-talk
--
==============================================
== Timothy Klein || teece at silverklein.net   ==
== ---------------------------------------- ==
== "Hello, World" 17 Errors, 31 Warnings... ==
==============================================