On Thu, 2007-01-11 at 22:21 +0100, Matthias Urlichs wrote:
> robepisc:
> > Matthias, are you sure the absence of udevsettle was the origin of the
> > problem? Did the committed (in casper 1.79) fix actually solve your
> > issue?
> >
> I have manually added the required udevsettle call to my startup script
> at that position -- and yes, the issue went away.
>
udevsettle has been dropped from the initramfs, the script that needs
hardware should either be run from a udev rule, or spin until the
hardware is available.
> > It seems to me that udevtrigger doesn't really understand the -B and
> > -I command line options (see man udevtrigger). And for this reason it
> > returns an error, without actually doing nothing!
> >
> Yeah, that appears to be a problem. However, I'm using Edgy here.
> Edgy's udevtrigger *does* understand those options.
>
> Seems that in Feisty, s/-B /--subsystem-match=/ and s/-I /--attr-match=/
> -- which is kindof annoying, esp. as that change wasn't even documented
> in the changelogs AFAICS.
>
Yes it was ...
* Update patches:
- 40-udevtrigger-filters.patch: dropped, the spirit of this patch is
merged upstream and we don't need most of it anymore.
The -B, -I, etc. stuff was always an Ubuntu patch. Now that udevtrigger
is reliable, and takes less than a nano-second to complete; there was no
point having the filter options anymore.
In addition, now we're going for a completely event-driven boot, we
don't need to call settle either -- we won't be calling it in either the
initramfs or main boot sequence.
Scott
--
Scott James Remnant
[EMAIL PROTECTED]
--
networking script does not wait for udev to settle
https://launchpad.net/bugs/77438
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
