On Sun, Jan 18, 2004 at 12:31:08PM +0100, Sven Luther wrote: > On Sat, Jan 17, 2004 at 02:15:39PM -0500, Joey Hess wrote: > > Sven Luther wrote: > > > And there i faced the last problem, well most probably a bug or > > > something, i was simply presented with a login prompt, and i had not the > > > root password to enter it. Normally at this time, it should have booted > > > in the post-d-i install process, and proceeded smoothly with the > > > install. Why this happened has me trully baffled, but i couldn't do > > > much, for lack of root password. > > > > Boot with init=/bin/sh or such, and check /etc/inittab; it should have > > an entry in it to run base-config. > > Well, i have loged in another install on the disk, and mounted the root > partition. i attach the inittab here, there is no such thing as > base-config entry in it. Also strange, altough other files have January > 17 dates, the inittab has date : Dec 23 23:18. > > I have a supsision that maybe there was an older system install on this > partition previously, altough parted did not detect any filesystem and > supposedly did the install. > > This is not supposed to happen, since d-i should have made a new ext3 > filesystem on this partition, at least i asked him to do so, so i am a > bit confused. > > But maybe this is due to one of the previous steps (yaboot in > particular) failing, and d-i all the time wanting to come back to it.
Oops, forgot the inittab, here it is. Friendly, Sven Luther
# /etc/inittab: init(8) configuration. # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $ # The default runlevel. id:2:initdefault: # Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS # What to do in single-user mode. ~~:S:wait:/sbin/sulogin # /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot. l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin # What to do when CTRL-ALT-DEL is pressed. ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now # Action on special keypress (ALT-UpArrow). #kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work." # What to do when the power fails/returns. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop # /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # <id>:<runlevels>:<action>:<process> # # Note that on most Debian systems tty7 is used by the X Window System, # so if you want to add more getty's go ahead but skip tty7 if you run X. # 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 # Example how to put a getty on a serial line (for a terminal) # #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 # Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
