Hello, ESG, thanks for your explanation. Brian, If you want to rescue your system from the messed up state, then do the following: 1. Boot your machine with bootable cd/dvd 2. At the installation prompt type "linux rescue" 3. After asking you some question about keyboard-type and enabling network interface, it will give you a shell 4. Type "chroot /mnt/sysimage" 5. Then you would be able to correct your inittab file Note: I am assuming nothing was messed up other than the /etc/inittab file :) Thanks, Ahmed Sharif On Fri, Feb 20, 2009 at 1:29 AM, ESGLinux <esggrupos@xxxxxxxxx> wrote: > Hello, > > as Harry says RTFM --, no, I´m kidding, > > I resume AFAIK > > level 1 - activates SELinux, runs /etc/rc.sysinit, (that mounts the > filesystems) and executes all scritps in /etc/rc1.d > s or single - The same as level 1 but does not execute /etc/rc1.d scripts > emergency - activates SELinux, mounts only / > > if you put at boot prompt > > init=/bin/sh - its like emergency but without SELinux > > I think thats all, if anyone can say anymore its welcome, > > Greetings > > ESG > > > > 2009/2/19 Brian Fox <genkuro@xxxxxxxxx> > > > Studying for the RHCE... > > > > What's the difference between the "emergency" "single" and 1 runlevels? > I > > purposefully clobbered my inittab file and rebooted. Redhat prompted for > a > > runlevel. Of the three, "single" was the only one that booted. > > > > I'm curious why. Grep'ing the words single and emergency in the etc > > directory came up empty. Those runlevels aren't explicitly supported by > > the > > boot scripts. > > > > Any insight greatly appreciated. > > > > Thanks, > > Brian > > -- > > > > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjecthttps://www.redhat.com/mailman/listinfo/redhat-list
