Syncing Palm device via USB Cable

[pursley1 at netscape.net]

Les wrote:
> On Tue, 2008-03-11 at 02:09 -0500, pursley1 at netscape.net wrote:
>   
>> With the help of another person, we were able to deduce that the problem 
>> was because of Fedora, which by default, does not give access to the USB 
>> ports to users.  There is no group to add to fix this problem and it 
>> took changing the global security permissions to allow everyone full 
>> access to the ports to get it to work.  This really should be addressed 
>> on future versions of Fedora so I don't have to re-fix this problem 
>> every time the system updates the security.  How do I recommend it?
>>
>> Bradley
>>
>> Patrick O'Callaghan wrote:
>>     
>>> On Mon, 2008-03-10 at 10:11 -0500, pursley1 at netscape.net wrote:
>>>   
>>>       
>>>> Patrick O'Callaghan wrote:
>>>>     
>>>>         
>>>>> On Mon, 2008-03-10 at 08:20 -0500, pursley1 at netscape.net wrote:
>>>>>   
>>>>>       
>>>>>           
>>>>>> I'm new to Fedora and am still classified have been messing around with 
>>>>>> Linux part-time for about a year but am trying to migrate fully to Linux 
>>>>>> now and can't seem to get my Palm device to sync.  It connects via a USB 
>>>>>> cable and I can even 4. Some amount of training to our engineer. Perhaps 1 to 2 weeks istell you how it appears in the proc file system USB 
>>>>>> file when it is activated but how do I tell the software that it's 
>>>>>> there?  This is only one of a few things that is hindering my desire to 
>>>>>> completely eliminate Windows from my computer (I haven't liked Microsoft 
>>>>>> for years).  Any help here?
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> 1) Make sure you have the pilot-link package installed and up to date.
>>>>> 2) Make sure it works: do 'pilot-dlpsh -p usb:' and play around. Check
>>>>> the man pages for the various pilot-* commands.
>>>>> 3) If you want a GUI front-end pick one (e.g. kpilot, gnome-pilot) and
>>>>> install it.
>>>>> 4) Configure the front-end to use 'usb:' as the Pilot device.
>>>>>
>>>>> poc
>>>>>       
>>>>>           
>>>> Well, I tested your examples and all of the things you suggested to 
>>>> check worked just fine except that none of the front-ends are able to 
>>>> connect with it.  I can connect with it manually using the 'pilot-dlpsh' 
>>>> command just fine.  I've tried 'gnome-pilot' & 'jpilot' with no success 
>>>> at all.
>>>>     
>>>>         
>>> I use kpilot myself, so I can't help you. I would suggest making sure
>>> you have the latest version, and that the front end is configured to use
>>> 'usb:' as the device name. Earlier versions of pilot-link had
>>> complicated ways of setting up serial ports, linking to the /dev/pilot
>>> device, loading a 'visor' kernel module etc. etc., all of which gave a
>>> lot of headaches and were unreliable. The current pilot-link uses the
>>> libusb user-land library which is not only more reliable but noticeably
>>> faster, but some of the frontends may not have caught up yet.
>>>
>>> poc
>>>
>>>   
>>>       
> Did you add your users to the uucp group?
>
> Regards,
> Les H
>   
That was something I did from the start but it didn't make any difference.