| 1 |
On Sat, Aug 06, 2011 at 08:22:23PM +0100, Steven J Long wrote: |
| 2 |
> I have the same setup and no issues either. I think the problem is for other |
| 3 |
> devices, eg someone mentioned having a bluetooth adapter in their laptop |
| 4 |
> which gets picked up at boot by udev, but needs helpers in /usr. |
| 5 |
> |
| 6 |
> According to https://bugs.gentoo.org/show_bug.cgi?id=364235#c1 udev marks |
| 7 |
> (or marked) failing probers as missing devices, not failed, so udev- |
| 8 |
> postmount doesn't pick on them as needing to be rescanned. |
| 9 |
> |
| 10 |
> I'm not sure if that bug's been fixed or not; the call to util_run_program |
| 11 |
> is no longer in that function at: |
| 12 |
> http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob_plain;f=udev/udev- |
| 13 |
> rules.c;hb=HEAD |
| 14 |
> ..but it might well have the same logical error for all I know. |
| 15 |
|
| 16 |
The concern about udev-postmount is the line that says: |
| 17 |
|
| 18 |
udevadm trigger --type=failed |
| 19 |
|
| 20 |
The --type=failed option is going away and upstream is getting rid of |
| 21 |
the failed marking eventually; there will be no more "failed" events |
| 22 |
either. |
| 23 |
|
| 24 |
William |
Archives