i use the lfs-bootscripts-2.2.2, using the line "make install" to install the scripts.
i added two lines to the /etc/rc.d/init.d/rc script. one at the beginning which echoes the first parameter passed to the script, and on line at the end that echoes "FINISHED". Booting the system shows me that the rc script is called with a parameter of sysinit, and that it finishes OK, but no call to the rc script with the parameter of 3 (the system hangs before a call to the rc script is made). The localnet script (the one that sets the hostname) has a symlink of S80localnet in the rcsysinit.d directory, and no other symlink has a lower priority. I have checked the symlinks in all the rc.d directories, they seem to be OK. This system runs fine on Fedora Core 2, so I don't think its a hardware issue. Just to make sure, I recompiled the SysVinit source, but the same problem still happens. i just recently noticed that I DO get an error executing the cleanfs script. /etc/rc.d/rcsysinit.d/S50cleanfs: line 73: /dev/null: Permission denied Could this be the cause of the hang?? -----Original Message----- From: Ken Moffat <[EMAIL PROTECTED]> Sent: Feb 28, 2005 1:52 PM To: LFS Support List <lfs-support@linuxfromscratch.org> Subject: Re: LFS hangs after "Setting Hostname" On Mon, 28 Feb 2005, Roberto Perpuly wrote: > Hello, > > I can't seem to get my LFS to boot. The kernel loads OK, the init > script runs but stops after "Setting Hostname [OK]". It seems that > only the sysinit scripts are run, no run level 1, 2, or 3 scrips are > run? > > Any ideas? > I'm not running current LFS so I can't comment on what should run when, but (i) are there any more sysinit scripts after the host name is set ? if there are, it's the next of those. (ii) if not, sounds as if the first script for run level 3 hangs. Note that the system does NOT run the level 1 scripts, then level 2, then level 3 on a normal boot to level 3, it goes from the sysinit scripts to rc3. Need to know what is in the hanging scrpt to track it down. These days, we mostly install the downloaded bootscripts, so there is much less scope for error. Maybe you had to edit, or add, something at the end of the sysinit directory ? I've seen some weird hangs on *obscure* hardware, sometimes upgrading to a new kernel release (2.2->2.4, 2.4->2.6) breaks things. If you can identify which script, but can't identify the problem, attach the script. Ken -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
