| Art Alexion on 6 Nov 2006 16:45:01 -0000 |
|
On Sunday 05 November 2006 17:10, Jeff Abrahamson wrote: > I want to sync my pilot directly with pilot-link, as the most recent > release of jpilot and libpisock9 have introduced a bug for me. I > think I remember someone here (Art?) talking about doing this. The > obvious thing, pilot-xfer -s ~/.jpilot/ , doesn't work, as it does a > one-way transfer rather than copying in both directions. Does anyone > have any suggestions? > > Thanks for any thoughts. Jeff, Having checked, you are right that the debian documentation and man page seem to suggest that the -s sync parameter is the same as the -b backup parameter. Practically speaking, though, this doesn't make sense. If all the sync command did was backup, there would be no need for it in addition to the backup command. I must confess that I haven't used pilot-xfer to sync in years. Lately, I have only used it to troubleshoot the kernel's ability to connect the handheld. I've been using kpilot which uses pilot-link to do its work, and have been using pilot-link only as a diagnostic tool, i.e. to see if the problem was with kpilot or with the connection to the pilot. I asked if you could sync with pilot-xfer just to see if there was a problem with the connection between your desktop and handheld, as opposed to a problem with jpilot. There seems to be an absence of documentation on the pilot-link web site, specifically, what they mean by "sync" versus what you and I would expect. I see from your other posts that you use gnome. The gpilot program worked best for me except that the Ubuntu version syncs only with evolution, which I hated. With Debian testing, you may be able to have it sync with you jpilot data. If you are OK with KDE, kpilot and Kontact work really well for older, serial palm devices. I think you can configure kpilot to sync with jpilot data, but I never tried. Kontact is a lot more modular than evolution so you can just run the components that you use. If you haven't tried it in a while you may want to. -- _____________________________________________________________ Art Alexion PGP fingerprint: 52A4 B10C AA73 096F A661 92D2 3B65 8EAC ACC5 BA7A Keyserver: hkp://subkeys.pgp.net The attachment - signature.asc - is my electronic signature; no need for alarm. Info @ http://mysite.verizon.net/art.alexion/encryption/signature.asc.what.html _____________________________________________________________ Attachment:
pgpdymHhe41mZ.pgp ___________________________________________________________________________ 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
|
|