Slackware 10.2 boots to run level 1

norobro · 02-09-2006, 04:40 PM

Hello.

I'm new to Slackware and BSD style init, but I have been running Debian for about a year.

I downloaded 10.2 from the Slackware site using bit torrent, burned a cd, and installed the distribution with no errors. The only variation from the normal install is that I didn't install lilo because I am already using grub.

My problem is the system always ends up in run level 1. I have tried changing the default runlevel in initab to 4 but it still boots to run level 1. telinit from level 1 to 3 or 4 works fine.

My inittab file:

Code:

id:3:initdefault:
si:S:sysinit:/etc/rc.d/rc.S
su:1S:wait:/etc/rc.d/rc.K
rc:2345:wait:/etc/rc.d/rc.M
ca::ctrlaltdel:/sbin/shutdown -t5 -r now
l0:0:wait:/etc/rc.d/rc.0
l6:6:wait:/etc/rc.d/rc.6
pf::powerfail:/sbin/genpowerfail start
pg::powerokwait:/sbin/genpowerfail stop
c1:1235:respawn:/sbin/agetty 38400 tty1 linux
c2:1235:respawn:/sbin/agetty 38400 tty2 linux
c3:1235:respawn:/sbin/agetty 38400 tty3 linux
c4:1235:respawn:/sbin/agetty 38400 tty4 linux
c5:1235:respawn:/sbin/agetty 38400 tty5 linux
c6:12345:respawn:/sbin/agetty 38400 tty6 linux
x1:4:wait:/etc/rc.d/rc.4

When booting the last lines of the boot sequence are:

Quote:

using/etc/random-seed to initialize /dev/urandom

sending all processes the sighup signal
waiting for all processes to hangup
sending all processes the sigterm signal
waiting for all processes to terminate
sending all processes the sigkill signal
waiting for all processes to exit

going to single user mode

There are no error logs or messages because the log deamons don't get started.

Thanks in advance for any help!!!

Norm

gilead · 02-09-2006, 06:22 PM

What do you have in your grub.conf file for the Slackware kernel? It sounds like the boot up process is being forced into single user mode.

Dankles · 02-09-2006, 06:57 PM

Heres your problem (correct me if I'm wrong):
"id:3:initdefault:"

The '3' should = 4 instead. According to the inittab file, your booting to "init 3", which is multiuser CLI mode.
As you know "init 4" is what you want.

norobro · 02-09-2006, 08:00 PM

Steve,

You are correct about it being forced! Thanks for pointing me in the right direction - grub. I have been pounding my head against the wall (you should see the wall) trying to figure out what is going on in rc.d and all of the time it was the way I had grub configured. I recently switched from lilo and just copied menu.lst from LFS.

Code:

title		Debian GNU/Linux, kernel 2.6.14.3.120205
root		(hd1,8)
kernel		/boot/vmlinuz-2.6.14.3.120205 root=/dev/hdb9 ro 
savedefault
boot

title		LFS
root		(hd1,4)
kernel		/boot/lfskernel-2.6.11.12 root=/dev/hdb5 ro single vga=769
savedefault
boot

title		Slackware 2.6.13
root		(hd1,9)
kernel		/boot/vmlinuz root=/dev/hdb10 ro single vga=769
savedefault
boot

The single was the problem. Don't know why I didn't have it on my Debian line.

I should really do some reading before just blindly installing something or next time I might break something.

Thanks for responding Dankles!

'preciate the help!!!!

Norm

gilead · 02-09-2006, 08:59 PM

No problem - glad it's working