I would like to officially welcome my brother-in-law to the world of Linux.
Dave, your introduction into it was very appropriate. There is a reason a Linux
admin is more expensive - he has to not be afraid of scary error messages when
things go wrong.
The advice you got from Michael sounds reasonable to me. I have had a problem
like that before after changing the motherboard on a system running SuSE. It
puzzled me for a while until I figured out that the driver for the IDE
controller was not included in the initrd. To spare myself some typing, here is
some reading on how initrd works:
http://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/initrd.html
While in that particular instance I solved the problem by booting from a rescue
CD, mounting the the root, and rebuilding the kernel to include the driver for
the IDE controller, since you have nothing to lose on /dev/hda2 (I suppose) I
would second Michael's suggestion for a quick fix - just try the stable variant.
However, if you are feeling adventurous, boot into rescue mode, mount /dev/hda2,
and mess around with the kernel.
--
Sasha Pachev
AskSasha Linux Consulting
http://www.asksasha.com
--------------------
BYU Unix Users Group
http://uug.byu.edu/
The opinions expressed in this message are the responsibility of their
author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG.
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list