----- Original Message -----
From: "Rajko M."
On Monday 03 November 2008 07:04:37 pm Andrew Joakimsen wrote:
Another one bites the dust... Here's the exact procedure..
Did an install via SSH. After the install completed I ran online update. "Packages for software management were updated, restarting now" and ran online updates again which did the Kernel update. Restarted the system and it does not come back online.
This is not acceptable.
So, what to do?
Kernel didn't load. It could be that computer is sitting with oops message waiting for reset, or waiting on root password, or running something to keep CPU warm, or all fine except network module.
GRUB prompt can be accessed from serial line, but that requires another computer that has network access.
I guess that Brian described what he is using for remote servers to prevent problems like your's.
Heh, indeed. This is a case of: If "This is not acceptable.", then "Don't do that". You don't get to blame Browning for the hole in your foot when you deliberately loaded in ammo, disengaged the safety, pointed the gun at your foot and pulled the trigger. It's not opensuse's fault for failing to _garantee_ to boot all the way to network connectivity and network services starting. Nothing can ever garantee that. It's the admin's fault for installing a server remotely that must stay up, yet not providing himself the means to deal with a broken system. It's especially, doubly, quadruply, the admins fault for allowing even the slightest change to happen to such a delicate and precarious systems' boot and core os files after it is by some miracle up and running to begin with. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org