On October 18, 2005 03:30, Marco d'Itri wrote:
> OK, as it turns out I was half wrong: /proc/bus/ is not syncronous, so
> scripts still need to wait (they may use the wait_for_file function from
> /lib/hotplug/hotplug.functions). OTOH, RUN is still the correct keyword
> to use, because PROGRAM has different semantics (and you must always use
> += unless you know better).
OK.
> > a modular kernel? I did notice that a homebrew everything-built-in
> > kernel did not suffer from this problem. I just took it for granted
> > that the udev/hotplug maintainer would be testing against a stock
> > Debian kernel, or at least something similarly modularized.
>
> I need newer kernels before a debian package is available, and anyway I
> will not use debian kernels again as long as they will break drivers
> by removing uploadable firmwares.
Needing to test newer kernels is quite understandable, but you really ought
to at least test udev with a Debian kernel, just to make sure that module
loading is functioning properly.
> Because the rule matches on many events, among them BUS=="usb".
> The correct rule to change the /dev/bus/usb/ device permissions would
> be:
>
> SUBSYSTEM=="usb_device", SYSFS{idProduct}=="0039",
> SYSFS{idVendor}=="045e", GROUP="plugdev"
>
> (660 is the default.)
That information will be very helpful when /dev/bus/usb arrives, for a
number of developers I'm sure - thanks.
Cheers,
Christopher Martin
Attachment:
pgpKJtyi9ATXo.pgp
Description: PGP signature