On Tue, 2004-01-13 at 16:08, Matt wrote: > Today I tried to switch to run level 3 via `/sbin/init 3` but it never > completed. It got so far as loading anacron and then hanged. syslogd > reported no error messages; the last entry states that anacron started > successfully. There is a Bugzilla report filed as ID 112015 but there's > been no response as yet. > Has anyone found a workaround or temporary fix? > > TY > -- > Matt Well, it looks like whatever perceived problem I had is now gone after upgrading to the latest 2.4.22-1.2149.nptl kernel. The behaviour I now get, that I see as the correct process, is as follows: o Run `/sbin/init 3` from a shell within X (VT7). o INIT shuts down runlevel 5 related processes, switches to VT6 and presents the login prompt. (NB: The ENTER key must be pressed to push the login process to the console.) o VT7 now displays a blank screen with occasional system messages. o Running `/sbin/init 5` from VT6 starts up the X related processes once again, switches to back to VT7 and displays gdm. Now I have a couple queries about this process I just outlined: 1) Is the need to switch to VT6 when changing from 5 to 3 due to no mingetty process running on VT7 by default? i.e. It only starts the gdm login process upon boot-up? 2) Is it not warranted to see the need to press the ENTER key to see the login prompt as a bug? I realise it is trivial to press it, but as somewhat of a perfectionist, :p, should there not be a way to handle this automatically? 3) When in run level 3 on VT6, there are no processes running on VT7 correct? All I see are INIT messages stating switching to runlevel 3 and sending all processes the TERM signal. This last message would be confirmation as such? What other messages might I expect to see if any? Thank you for your input folks. -- Matt
