D Henson wrote:
The latest mandatory update appears to have killed my server. After
running the update, as I have done dozens of times, the server stopped
responding to mouse and keyboard input. Ah, xserver problem, thought I.
Ctrl-alt-backspace. Now I'm looking at the system console @, I think,
runlevel 5. I tried various commands such as xdm, gdm, xserver, etc.
(I'm not a CLI guy.) None of the commands did anything useful. Now for
you had several options:
# shutdown -h now # shutdown and halt system NOW
# shutdown -r now # shutdown and reboot NOW
# # alternate methods using INIT
# init 0 # runlevel 0 = shutdown and halt
# init 6 # runlevel 6 = shutdown and reboot
---------------
For all you newbies...and other who are GUI-dependant:
This should be a lesson to anyone who thinks that they
can rely on GUI tools to solve all of your problems.
Wrong.
Learning the CLI is mandatory for good system administation.
(The lack of a decent CLI system and CLI-friendly
configuration files, etc. is *part* of the reasons
why Windows has always been difficult to administrate.
1 Admin/10 Windows machines.
1 Admin/200+ Unix/Linux machines
the really stupid part. I decided to simulate a power failure. This
resulted in a reboot and the reboot attempted to give me a gui logon
screen (the little clock icon was running) but it never actually got
there. I decided I need some help.
First, be careful when applying this update. Second, does anyone know
how I can recover from this upate? I had a very busy day planned so any
assistance will be sincerely appreciated.
Go to a character console (say, Ctrl-Alt-F3), log in to
root, run yast from the command line, follow the menus
to software management, and roll back to the previous
version BEFORE you updated.
Don Henson
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
