Hi.-) [EMAIL PROTECTED] (Miquel van Smoorenburg) writes:
> In article <[EMAIL PROTECTED]>, > Josef Oswald <[EMAIL PROTECTED]> wrote: > >The Problem I run into after I installed a HPT370 driven Card, details > >can be found in my other post (HPT370 and other problems), I had to > >install a new Kernel with umda-100 patched with A. Hedrick, I got > >that Kernel and installed it without installing the drivers.. > >Only later did I install those drivers.. > > > >The Problem now is that, during boot up I get a error-message > >/etc/init.d/rc.2 Command not found and I can only login as root, > > It means something fscked up your /etc/inittab file. There is > indeed no /etc/init.d/rc.2 script; there is a /etc/init.d/rc > script that gets called from /etc/inittab as "/etc/init.d/rc 2". > Note there's no period but a space inbetween rc and 2. > > Edit /etc/inittab, fix this and reboot, and things should be > working again. Checking the whole thing during boot-up I found that the error message is actually: /etc/init.d/rc:2: command not found.... also I have some other (linux and winXX partitions) which are mounted automatically during boot up, and I get a error to check it manually... fsck or similar... I could not find anything wring in /etc/inittab ( since I only looked it once without changing something...) # /etc/inittab: init(8) configuration. # $Id: inittab,v 1.8 1998/05/10 10:37:50 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> 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 > > Mike. My next step is let Debian on boot up only check its own partition...... Since every time I start Debian I still can't shutdown the pc with shutdown -h now .... could be the whole problem is caused by the file-system check ( and I don't know how to repair it manually...) thanks anyway for your help :-) -- LinuxUser aka Josef Oswald [EMAIL PROTECTED] registered-linux-user # 134.818 at http://counter.li.org The box said Windows, NT or better, so I installed Linux :-)
