A couple months ago there was discussion about sync'ing with jpilot
only using the sync button from the palm and without having to push
both the hotsync button on the palm and in jpilot. I have found a
solution. It comes in two steps.
1. Using udev to create the file representing the palm pilot that has
user permissions.
This step is relatively easy and known for a while. One must create a
udev rule that will do this for you. Attached is my udev rule and it
should work for many others.
2. Using hal/ivman to launch the jpilot sync in the event that the
hotsync button is pressed.
This requires you to have hal and ivman installed. Make sure that hal
is running (the daemon's executable is named hald). The first thing
we need to do is find out what hal events are generated once the
hotsync button is pressed. In order to do this, open a terminal and
launch the following command: lshal --monitor.
Then, watch the output once you hit the hotsync button. I use a Treo
600, and there were three events generated when I pressed the hotsync
button. The event I used was the last event, which looks something
like:
/org/freedesktop/Hal/devices/usb_device_82d_300_PalmSN12345678_usbraw
You may have to do some experimenation to find the best hal event to
trigger off of. Once you figure out which hal event to use, it is
time to use ivman to launch the jpilot sync program. So, first edit:
/etc/ivman/IvmConfigActions.xml
And insert the following lines:
<ivm:Match name="hal.info.udi"
value="/org/freedesktop/Hal/devices/usb_device_82d_300_PalmSN12345678_usbraw">
<ivm:Option name="exec" value="jpilot -s" />
</ivm:Match>
Now, just make sure ivman is running and hotsync away!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 10-custom.rules
Type: application/octet-stream
Size: 135 bytes
Desc: not available
Url : http://lists.jpilot.org/pipermail/jpilot/attachments/20060925/22a0a715/attachment.obj
More information about the jpilot mailing list