Hi,
> > > PHYSDEVPATH and the 'device' link are both deprecated and will go away
> > > some day in the future, you better pass the values you want to use in
> > > your script down from udev with $sysfs{}. That is not dependent on a
> > > specific order of devices in sysfs.
>
> > I've attached working (for me) rules+bluetooth.sh. $sysfs{manf_id} and
> > $sysfs{card_id} are passed to bluetooth.sh.
>
> Looks fine, and should not break, if something in sysfs changes, which
> is nice.
>
> Btw, you should be able to just do RUN+="bluetooth.sh", as udev will
> look in /lib/udev/ if it does not start with a '/'.
this is nice, but there is no need to run bluetooth.sh on non-serial
based Bluetooth cards like the Nokia DTL1 for example. They work
perfectly fine without any additional udev rule.
I also don't like that bluetooth.sh tries to run /etc/init.d/bluetooth,
because this should not be a task of an udev script. Either Bluetooth is
enabled to be started a system boot or not.
The other thing is that this is not Debian specific. So why does nobody
tried to start an upstream discussion on bluez-devel or linux-hotplug
mailing list.
Regards
Marcel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
