Pilot syncing....

[pursley1 at netscape.net]

As stated in another post, the problem turned out that libusb was 
looking for a group called "dialout" that Fedora never created in the 
first place.  I manually added the group name and gave everyone that 
would need it access to the group and the problem disappeared.

Patrick O'Callaghan wrote:
> On Tue, 2008-03-11 at 02:15 -0500, pursley1 at netscape.net wrote:
>   
>> The problem I encountered, with the help of someone else, was that 
>> libusb does not, but should, give R-W access of the USB ports to users.  
>> I think this is a major oversite with whoever packages libusb and 
>> absolutely *NEEDS* to be included as an option.  Without this fixed, it 
>> is impossible to access your Palm unless you are logged in as root.
>>     
>
> It works for me out of the box, and I did nothing special. Sounds like
> the problem isn't with libusb as such. The Usual Suspect nowadays seems
> to be ConsoleKit. Failing that, take a look
> at /etc/udev/rules.d/60-libpisock.rules where udev sets up permissions.
>
> poc
>
>   
>> Bradley
>>
>> Patrick O'Callaghan wrote:
>>     
>>> On Mon, 2008-03-10 at 16:52 -0700, Leslie Satenstein wrote:
>>>   
>>>       
>>>> Add to /etc/rc.local at the bottom
>>>>
>>>> ## added for palm pilot or sony cle
>>>> /sbin/modprobe --first-time visor
>>>>     
>>>>         
>>> Only for older versions of pilot-link. New versions use libusb instead
>>> of the visor module and in my experience work better (in fact you should
>>> make sure 'visor' is *not* loaded).
>>>
>>> poc
>>>
>>>   
>>>       
>
>