On May 30, 2008, at 11:23 AM, Tom wrote:
> On Friday 30 May 2008, Christopher Sean Hilton wrote:
>> 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/
>
> Yes, there's a method to do this which I found quite simple to set
> up and
> works exactly as desired. It involves running the 'ivman' daemon
> after it is
> configured to respond to the hotsync event initiated on the Palm.
>
> http://www.jpilot.org/pipermail/jpilot/2006-September/006483.html
>
> The process is described for a system using the old USB device nodes
> (/dev/ttyUSB, etc), rather than the new usb: thingy, though, so your
> mileage
> may vary.
>
Thanks, that sounds perfect but I didn't think that jpilot -s
connected to the main jpilot via a Unix domain socket. Perhaps jpilot -
s just syncs the data...
-- 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