I wrote earlier about an accidental reboot while upgrading glibc. Someone
suggested using --force. Good idea, but didn't work. Someone else suggested
trying to --rebuilddb, which I proceeded to try. My machine rebooted during
the rebuild. This time I am absolutely certain that no one touched the
reboot switch. The system rebooted itself. AFAIK, there were no power
problems or any other external cause for a reboot. Also, I wonder now if I
really did hit the reboot switch during the original glibc upgrade. I
thought it possible at the time and accepted it as an explaination only
because it seemed much more likely than a spontaneous reboot.
So this is either a software problem or a hardware problem.
Unfortunately, the problems don't end there. Fsck found errors on my /var
partition that required fixing from single user mode. Of course, several rpm
libs were listed as having problems. fsck fixed the filesystem stuff, but
now I wonder just how screwed up my rpm setup is.
This is coming to you from WindowMaker, so any damage that there might be
doesn't seem to be affecting daily usage.
Any ideas where to start sorting this out? Could it be a simple problem of
overheating causing a reboot? (can that happen?)
TIA
--
Chris and Yoshiko Spackman
[EMAIL PROTECTED] (English)
[EMAIL PROTECTED] (Japanese)
www.openhistory.org
"I will not be pushed, filed, stamped, indexed, briefed, debriefed, or
numbered. My life is my own."
-The Prisoner
