On Mon, Aug 27, 2007 at 04:28:48PM +0200, Nigel Henry wrote: > On Monday 27 August 2007 03:52, Douglas A. Tutty wrote:
> > Since this is all happening in /etc/rcS.d, I'd suggest booting with > > init=/bin/sh and running the /etc/rcS.d scripts manually one at a time > > to try to track it down. If you can get a shell while these errors are > > happening, perhaps you can see what processes are running. > > I havn't tried that before. Is that going to be similar to the interactive > boot up that you can do on Fedora? > > I've never used Fedora. There's nothing interactive about it. When you init=/bin/sh, you get sh running instead of init. The only drive mounted is the / and its ro. So you cd to /etc/rcS.d, do an ls and write down all the file names so you can tick them off as you run them. #less README read it.. Then, one at a time, type e.g.: #./S01glibc.sh start #./S02hostname.sh start You're sort-of single-stepping the init process to track down a problem. Once you have, try to fix it and then shutdown. Since init normally does this, I wouldn't want to try to bring the system all the way up in this manner. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]