On 8/30/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
Hi all,
Here is a bug report I've been meaning to send in for months. Upon
booting my machine this evening, I decided to send it in. I get an
error, that suspends the boot process, which says it is a problem
with the LFS bootscripts.
Following is the error recorded in the /dev/bugreport file. Let me
know if more information is needed to determine the problem. This
build of LFS uses slightly older bootscripts than the LFS-6.2 release,
but I don't think there's been changes that affect ieee1394 devices.
Alexander will probably be able to tell you more specifics about that
error, but we're ignoring them now. In the newer bootscripts, the
/dev/bugreport stuff has been removed. Basically, there's no way to
make udev wait for all the subsequent actions generated from a uevent.
The udevsettle program is run so that the bootscript will wait until
all the uevents regenerated by udevtrigger will be processed.
Unfortunately, udevsettle can't really tell when the rule processing
has finished for each uevent. I can't remember the exact reasons why.
But things that take a longer time to process are sometimes still
processing after udevsettle has determined that all the uevents have
been queued into udevd. For instance, if I have my USB key inserted at
boot time, it loads the USB related kernel modules then calls up the
whole SCSI emulation layer. This takes a long time and usually isn't
done when udevsettle was.
Upstream doesn't care about this because apparently there's no way to
check this. So, it Alexander decided that the /dev/bugreport stuff was
useless after he reported it upstream a bunch of times.
At least, that's the way I understand it.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
