[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
For a USB pilot sync, I have tried both gnome-pilot and kpilot. Both seem buggier than pilot-link (which I used with jpilot and serial sync). The problems I experienced with gnome-pilot were a deal breaker -- data corruption. Kpilot seems safer in that regard, and I need it because I use kde-pim/kontact. One thing gnome-pilot seems to do better, though, is device configuration. On my system, my device seems to pick different USB ports randomly, so it gets annoying when I have to run 'dmsg | grep USB' and 'ls /dev/ttyUSB*' most of the times I want to do a sync and reconfigure kpilot to listen to the right port. On gnome-pilot, you can configure multiple ports. That way, if the pilot (kernel?) picks a different port, the sync completes without a reconfigure. Is anyone else having these problems? How do you deal with them? -- _______________________________________ Art Alexion Arthur S. Alexion LLC PGP fingerprint: 52A4 B10C AA73 096F A661 92D2 3B65 8EAC ACC5 BA7A The attachment -- signature.asc -- is my electronic signature; no need for alarm. Info @ http://mysite.verizon.net/art.alexion/encryption/signature.asc.what.html Key for signed PDFs available at http://mysite.verizon.net/art.alexion/encryption/ArthurSAlexion.p7c The validation string is TTJY-ZILJ-BJJG. ________________________________________
Attachment:
signature.asc
Description: PGP signature
Attachment:
signature.asc
Description: OpenPGP digital signature
___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug