Bugzilla – Bug 105276
Stale files in /etc/hotplug/usb
Last modified: 2005-09-05 14:41:55 UTC
Hi all, there are stale files in /etc/hotplug/usb: /etc/hotplug/usb/kino-jogshuttle: kino-0.7.6-3 sf /etc/hotplug/usb/openct: openct-0.6.5-2 okir /etc/hotplug/usb/tascam_fpga: alsa-tools-1.0.9-4 tiwai /etc/hotplug/usb/tascam_fw: alsa-tools-1.0.9-4 tiwai /etc/hotplug/usb/tascam_fw.usermap: alsa-tools-1.0.9-4 tiwai /etc/hotplug/usb/usb.usermap: kino-0.7.6-3 sf /etc/hotplug/usb/usbcam.usermap: libgphoto2-2.1.99.head.0-8 meissner I guess all these files are obsolete. At least the *usermaps are not used any longer, because usb.agent has gone. What abot the rest? If you use a script for another purpose, please move it somewhere else. Tell me if it is (or has to be) called via udev. But even in this case we should move it to /sbin.
libbgphoto2 now has a HAL FDI map which is used by resmgr. IU removed the files from libgphoto2
In order for openct to handle any USB tokens and card readers, someone needs to start an openct driver process for each device detected.
Then you have to start openct via udev or hal. A file lying around in /etc/hotplug/usb/ has no effect.
I guessed so :) Can you give me a clue how to do this? When a USB token is detected, we need to run openct-control attach $DEVICE usb:$PRODUCT
Since openct-control lies in /usr you cannot go for udev. Via udev the event _may_ be triggered before boot.localfs and more probably before nfs. So you want to be called from hal and Timo will be very happy to tell you how. ;)
Timo, please help.
We could hald let do the callout for openct-control. It *should* be it's as easy as writing an fdi file. Have a look at the example fdi files in /usr/share/hal/ fdi/policy (e.g. 10osvendor/90-block-subfs.fdi). Let me know if you need help.
I'm new to hal. should the following information file work? <?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <match key="info.bus" string="usb_device"> <!-- egate --> <match key="usb_device.vendor_id" int="0x0973"> <match key="usb_device.product_id" int="0x0001"> <merge key="info.category" type="string">smart_card</merge> <append key="info.addons" type="strlist">hald-addon-openct</append> </match> </match> </match> </device> </deviceinfo> And a hald-add-openct script that just invokes openct-control with the appropriate parameters. Is this how it's supposed to work?
I've submitted an updated openct package with the above change, which seems to work.
(In reply to comment #8) [...] > Is this how it's supposed to work? Looks good to me.
The files in alsa-tools were already removed...
So kino is the only remainig part.
Kino is fixed and submitted, Hannes will do the hal part