Le Wednesday 08 March 2006 à 23:06:56, Luis Rodrigo Gallardo Cruz a écrit: > Package: libpisock9 > Version: 0.11.8-0.12.0-pre4-300rgc > Followup-For: Bug #346319 > > The following is a proposal to actually enable the use of libusb, now > that it is used for compiling the package. I believe it should be > enabled only on explicit request from the user, since using it disables > the use of the visor kernel module. > > Actually using libusb support requires two things: > > * Disabling tha autoloading of the visor kernel module, and > * Setting correct permissions on the device entry on /proc/bus/usb
What are the "correct permissions"? I already tried to change the permissions on the serial port used by pilot-link. And that resulted in Debian bugs #205125 and #258847. So my plan is to NOT change permissions on any thing any more. What I can do is DOCUMENT how to install all the magic to have a system that is usable. > The first is accomplished by a file in /etc/hotplug/blocklist.d > containing the single word 'visor'. This however is probably no a sane > default for the package, as it would break most everyone's > configurations. > > The second issue can be handled by addapting the solution used > by libsane. The files on > http://nul-unu.com/quien/rodrigo/software/usbdevices.db > and > http://nul-unu.com/quien/rodrigo/software/pilot-link.hotplug > should be added to the package, inside an /etc/pilot-link directory. > > With this in place, enabling libusb support is a matter of creating the > file on /etc/hotplug/blocklist.d and creating a symlink from > /etc/hotplug.d/usb to the /etc/pilot-link/pilot-link.hotplug file. This > could be done by the postinstall script on response to explicit user > request, I guess, or it could be left indicated in the documentation. I propose you talk to pilot-link upstream to add these files in the official pilot-link upstream .tar.gz file. Bye, -- Dr. Ludovic Rousseau [EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
