Re: hotplug arch. and apps

[Scott Cuyle Fritzinger <scottf@med.unr.edu>]

> scottf@med.unr.edu said:
> > Using a hotplug script (/etc/hotplug/usb/camera), we either set the
> > ownership of the device (/proc/bus/usb/001/003 for example) to that of
> > the locally logged in user in the case of a non-mass-storage camera,
> > or we mount the mass-storage camera to /camera0 and set ownership
> > again to the locally logged in user.
> I had a similar problem with a PROM programmer I built, and tackled
> it with the fxload that is now part of the hotplug CVS repository.
> Basically, I wrote a little script, called by a user map, that uses
> fxload to set the mode of the device to 0666 and create a link to
> the /proc/ device in /var/run so that an application can just poll
> for gflash.lnk.
> I also added REMOVER script support to remove the link when the
> device is disconnected.

but you placed the USB ID for the PROM programmer in the handmap right? or
did you do this some other way...

what i'd like to see is an easy way to update the handmap/usermap ID
definitions so that when a user updates gphoto, for example, we can easily
insert new device ID's for which the hotplug usb agent should recognize
and run the appropriate camera script. split the maps out into several
files in /etc/hotplug/usb.map/* and have the agent open each looking for a
match for the device, instead of just looking through the usb.handmap and
usb.usermap files.

-=Scott


_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel