Subject: Re: /etc/inittab problems
From: Robert Fout (rfout@damien.edu)
Date: Sun Jul 09 2000 - 19:25:24 MDT
I would recommend booting into single mode (add the word "single" to your
bootx kernel args), and disable linuxconf from starting at boot. I've had it
freeze the machine in the same manner you describe several times. Then type
"/sbin/init 5" at the console,and see if it works.
Bob
------------------------------------------------------------
If Bill Gates had a dime for every time a Windows box crashed
... oh, wait a minute -- he already does.
Robert Fout
MacOS Guru and MkLinux/Yellowdog/LinuxPPC Linux User
rfout@damien.edu
http://osx.damien.edu/rfout/
ICQ# 48433406
From: JCS <chris526@earthlink.net>
Reply-To: yellowdog-general@lists.yellowdoglinux.com
Date: Sun, 09 Jul 2000 20:10:58 -0500
To: YellowDog Linux <yellowdog-general@lists.yellowdoglinux.com>
Subject: /etc/inittab problems
I changed the line in /etc/inittab from
id:3:initdefault:
to
id:5:initdefault:
so that the system would boot up into the KDE/Gnome login window. Before
making the change in the /etc/inittab file, I was able to successfully start
up the KDE environment by using the command startx in the console.
But now after making the /etc/inittab file modification to start up in run
level 5, the X system appears to attempt to start up but then the system
stalls just after the console prints, "Switching back to run-level 3." The
system hangs with a blue screen and I am unable to login in so that I can
fix the /etc/inittab file. The last console message is, "Starting Linuxconf"
I also tried using the interactive startup at boot time but with no
success.. Is there anyway to regain control of the boot process when an
/etc/inittab file needs to be modified?
Thanks,
Chris
This archive was generated by hypermail 2a24 : Sun Jul 09 2000 - 19:29:03 MDT