The original parchment:
Over the weekend, my partner and I upgraded an AS1000A from DU 3.2G to
DU 4.0D (full install). After 3 pots of coffee and two blood
transfusions from all of the bleeding we did getting it to work, we
finally got it to the point where we could install our 3rd party
software.
Well, this wonderfully written software installation script decided that
it wanted to edit the kernel configuration file and add a device driver
to it. While it was in the process, it completely wiped out the
original kernel configuration file without making a backup (I made the
fatal assumption that it would backup the original). When the script
executed doconfig -c, the kernel failed to compile because of the
handywork of the software, so I was stuck with a bad configuration file.
Now, I need to restore the config file so that I can rebuild a kernel
sometime in my lifetime. I did not do a baseline system backup last
night because I opted for sleep (not a smart move in hindsight). What
can I do to restore the configuration file without having to do a
complete reinstall of the OS?
Thanks to the many quick responses from the following:
alan_at_nabeth.cxo.dec.com
Mark R. Allen (PBD) [Mark.Allen_at_pbdir.com]
digital_at_astro.ocis.temple.edu
digiunix_at_bellatlantic.net
Dr. Ram Rao [ram_at_ini.dec.com]
The basic summary is to boot into genvmunix and run doconfig. This will
rebuild the config file from my system. My partner did this from home
as I was summarizing this, and she was successful in rebuilding the
config file. We also have the system backup ready to run after this
config file is done so that I won't blow it up again. ;-)
Thanks for the help!
--Blake Roberts
blarob_at_hbsi.com
Received on Mon Oct 05 1998 - 21:14:45 NZDT