On May 30, 2008, at 8:08 AM, David A. Desrosiers wrote:
> On Thu, May 29, 2008 at 10:53 AM, Andrew Taylor <ampers at gmail.com>
> wrote:
>> Can anyone through some light on the subject. I am using a high
>> spec ASUS
>> desktop running Ubuntu 8.04 (Hardy Heron).
>
> Have you verified that your udev rules have been correctly set up by
> your distribution, as documented in README.usb?
>
Has anyone ever asked how much effort it would be to modify jpilot so
that the sync operation could be completely initiated from the Palm?
Feel free to correct me if I'm wrong. I'm on FreeBSD and I know that
things are a little different there but here what I'm thinking:
Now:
I initiate a hotsync on the palm
The USB subsystem starts the driver and creates a device node for the
next step.
I wait a couple of moments and tell Jpilot to sync
This spawns a jpilot-sync process which updates the data in
~/.jpilot/
Desired:
I initiate a hotsync on the Palm.
The USB subsystem starts the driver and creates a device node.
The USB subsystem runs a script with starts a jpilot-sync program that
connects to my running jpilot process over a Unix Domain Socket. This
updates the data in ~/.jpilot/
--------------------
This would make Jpilot work much more like the pilot programs in the
Mac and PC.
My problem is that there is a timing issue. If I don't wait long
enough my Treo botches the Sync. If I wait too long the result is the
same. If the USB subsystem initiated the syncing program then I could
resolve the timing issue in the shell script.
-- Chris
Chris Hilton tildeChris -- http://myblog.vindaloo.com
email -- chris/at/vindaloo/
dot/com
.~
~
.--.~
~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.
"I'm on the outside looking inside, What do
I see?
Much confusion, disillution, all
around me."
-- Ian McDonald / Peter
Sinfield
More information about the jpilot mailing list