Hi,
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.
> 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.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
To mortal men great loads allotted be; But of all packs no pack like poverty.
-- Herrick
--
networking script does not wait for udev to settle
https://launchpad.net/bugs/77438
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
