From: Lloyd Zusman <ljz@asfast.com>
Subject: Testing runit-init, stuck in stage 2 ???
Date: Sat, 26 Jun 2004 15:41:43 -0400 [thread overview]
Message-ID: <m38yeaksy0.fsf@asfast.com> (raw)
I'm following the instructions in the GNU/Linux section of the
"runit - replacing init" documentation
(http://smarden.org/runit/replaceinit.html) in order to replace
'init' with 'runit-init' on my linux box.
After properly installing runit, I have successfully completed steps 1,
2, and 3, and all testing I did in step 3 has succeeded.
Then, I try to do step 4:
Step 4: Reboot into runit for testing
Boot your system with runit for the first time. This does not change
the default boot behavior of your system, lilo will be told to use
runit just once:
a. reboot the system
b. enter the following on the lilo prompt:
init=/sbin/runit-init
c. watch the console output while runit boots up the system
d. switch to tty5 when stage 2 is reached, a getty should run
there, you are able to login.
I rebooted, (step "a"), and then in step "b", I performed the equivalent
step in grub, which I use instead of lilo. Step "c" went fine until I
saw that I was entering runit-init. It made it into runit's stage 1,
which completed with no problem. Then, it went into stage 2 (step "d")
and hung at that point. By "hung", I mean that the boot sequence
stopped cold with nothing more taking place.
I tried to go to tty5, but nothing happened when I issued the
Ctrl-Alt-F5 sequence which normally switches to that tty.
Finally, I had to do a Ctrl-Alt-Delete to interrupt this and to cause my
system to reboot. This seemed to be the only key sequence that caused
anything to happen when I was in this hung state.
Here's the pertinent information:
% uname -srvo
Linux 2.4.20-31.9smp #1 SMP Tue Apr 13 17:40:10 EDT 2004 GNU/Linux
# Contents of /etc/inittab
id:5:initdefault:
si::sysinit:/etc/rc.d/rc.sysinit
l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
## Comment out tty5 so we can test runit-init
##5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
# Run xdm in runlevel 5
x:5:respawn:/etc/X11/prefdm -nodaemon
Does this problem ring a bell with anyone?
Thanks in advance.
--
Lloyd Zusman
ljz@asfast.com
God bless you.
next reply other threads:[~2004-06-26 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 19:41 Lloyd Zusman [this message]
2004-06-26 21:10 ` Lloyd Zusman
2004-06-26 22:29 ` Charlie Brady
2004-06-26 23:13 ` Lloyd Zusman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38yeaksy0.fsf@asfast.com \
--to=ljz@asfast.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).