Alvin Oga wrote: > hi ya travis > > - try the various(6) consoles > ( Alt-F1 ... alt-F6 ) > > - start X11 from console ( init 3 ) > and you can kill X by control-C on cosole
No. This seems to have caused quite some confusion. This is NOT how X is started on a regular Debian installation. You seem to be crossing your Red Hat knowledge over into Debian. This is confusing for people. <snip> > - if you cann ssh-in.... > if you can see X processes... kill those you dont want > or blinly kill X11 > "init 3 ; sleep 5 ; init 5" As before, that won't affect X. Because isn't started in /etc/init.d (note, however, that (x|g|w|k)dm may be started in /etc/init.d), just changing runlevels won't affect anything here. "killall -9 X" might do it, however. Again, this is how Red Hat arranges its runlevels (3 = multiuser, 5 = multiuser + graphical login), and as such, is irrelevant to a Debian problem. In short, X lockups are resolved by either connecting remotely and killing the X process, or, if this doesn't work, rebooting the machine in an orderly manner (I have seen games lock the X display in such a way that just killing X doesn't restore order). If the box is locked hard and cannot be remotely connected to, the reset switch is pretty much your only option. Regards Peter. -- [EMAIL PROTECTED] Debian GNU/Linux sid on i386 and hppa Editor, www.kuro5hin.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
