Well, I got the thing to connect and "sync."
(See the problem below.)
What it took was:
kernel 2.4.20
pilot-xfer (from pilot-link version 0.11.7)
And, these two commands:
cd /root/.jpilot
pilot-xfer -p /dev/ttyUSB1 -i *.*
This forces the Zire to accept my old jpilot database files in /root/.jpilot.
Jpilot doesn't work for me to sync. I suppose it wasn't built against
the right version of pilot-link, if at all.
THE PROBLEM
This all looks great until I run:
pilot-xfer -p /dev/ttyUSB1 --sync /root/.jpilot
It doesn't really sync. This just copies the databases on the Zire to
the directory /root/.jpilot, overwriting the databases in .jpilot.
There is no effort made to sync. The problem may be that during the
sync the program reports that no changes have been made in the database
if I have made changes in the database using jpilot. I am not sure why
pilot-xfer thinks that. Updated files on the Zire are detected and backed
up to the .jpilot directory.
These two files change in .jpilot when I use jpilot to add an entry into
the address book:
next_id
AddressDB.pc3
Even if I change a file on the Zire, and the program reports it is
syncing, it really doesn't. It just overwrites what in in the .jpilot
directory.
This suggests that although jpilot knows about and needs pilot-link,
pilot-link doesn't know or care about jpilot and its databases.
Any insight appreciated,
BTW, here is a little script to take some of the nuisance out of syncing this
thing:
#!/bin/bash
echo Attempting to detect Palm
echo xxx | grep yyy
while [ $? -eq 1 ]
do
cat /proc/bus/usb/devices | grep "Palm Handheld"
done
echo Palm detected
pilot-xfer -p /dev/ttyUSB1 --sync /root/.jpilot
You will have to change the directory for .jpilot for your setup. I
suppose:
~/.jpilot
might be better. This assumes you keep your data in .jpilot, but any
directory will do.
The grep expression "Palm Handheld" works with my PDA. Yours may be
different. Of course, this script will only be useful if I can get
pilot-xfer to realize that files modified by jpilot have been changed.
It doesn't matter which order you use, that is, you can start the script
first or wait until after you press sync. It is cool to make this into
a daemon so syncing occurs whenever you press the sync button with no
further operator intervention.
Joel
_______________________________________________
Linux-users mailing list
[EMAIL PROTECTED]
Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
