[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

dbootstrap



Hi All,
I'm working my way through a peculiar install (the box is a briq from
Total Impact http://www.totalimpact.com ).  The box is booting over the
network and I haven't been able to run dbootstrap.  I've managed to
activate and mount the swap partition and mount the root partition which
lets me boot the box in single user mode.  My problem is that I can't
change to runlevel 2 or 3.
When I turned debugging on in /etc/init.d/rc it would hang on
    #telinit 1
as well.  Anyway I was trying to find out what dbootstrap does to the
init scripts.  I can't find the source to dbootstrap and I was wondering
if someone could point me to where it lives so that I could take a look
at it.

thanks,
Andy

P.S. in case anyone is wondering here's what happens on telinit 1 with
debug turned on:

stiq:~# telinit 1
INIT: Switching to runlevel: 1
INIT: Sending processes the TERM signal
INIT: Get first argument.  Set new runlevel to this argument.
 Is there an rc directory for this new runlevel?
 First, run the KILL scripts.
startup()
/etc/rc1.d/K12kerneld stop
startup()
/etc/rc1.d/K14ppp stop
startup()
/etc/rc1.d/K19network stop
startup()
/etc/rc1.d/K20inetd stop
startup()
/etc/rc1.d/K20logoutd stop
startup()
/etc/rc1.d/K20makedev stop
startup()
/etc/rc1.d/K90sysklogd stop
Now run the START scripts for this runlevel.
startup()
/etc/rc1.d/S20single start
INIT: no more processes left in this runlevel


And without:


stiq:~# telinit 1
INIT: Switching to runlevel: 1
INIT: Sending processes the TERM signal
INIT:modprobe: Note: /etc/modules.conf is more recent than
/lib/modules/2.2.18/modules.dep
modprobe: modprobe: Can't locate module binfmt-0000
modprobe: Note: /etc/modules.conf is more recent than
/lib/modules/2.2.18/modules.dep
modprobe: modprobe: Can't locate module binfmt-0000
Stopping internet superserver: inetd.
Stopping system log daemon: klogdstart-stop-daemon: warning: failed to
kill 126: No such process
 syslogdstart-stop-daemon: warning: failed to kill 124: No such process
.
Sending all processes the TERM signal... done.
Sending all processes the KILL signal... done.
Entering single-user mode...
INIT: Going single user
INIT: Sending processes the TERM signal
Give root password for maintenance
(or type Control-D for normal startup):
stiq:~#




Reply to: