On Mon, 2005-02-21 at 22:23 -0500, Piko A. Neal, Jr. wrote: > 1. I wanted to know if I could improve the way my system works with my > Palm. > > 2. Today, I was able to successfully set it up with Kpilot. It works > so that as look as Kpilot is open, it will hotsync whenever I press the > button. > > 3. Yet, when I use pilot-xfer and jpilot, I have to time the execution > of the syncing from the program after I press the hotsync on the Palm > since the computer generates a /dev/pilot node for it each time it hot > sync, but it will go away once the Palm stoppes trying. > > 4. I wanted to know if there was a way to get the /dev/pilot node to > stay, if I could somehow refer to it with something that does stay on my > system, so that pilot-xfer and jpilot are happy without doing some kind > complicated timing procedure each time. ---- I guess it didn't seem all that complicated to me. Press the sync button on my palm cradle and I have about 30 seconds to get around to starting the sync whether (J-Pilot) or (pilot-xfer) Once I got my Kyocera 7135 listed into gpilot-devices.xml - the applet is always looking for the sync process so I would imagine that you could somehow make a daemon process that ignores the lack of /dev/pilot and kicks into gear when it shows up. I am really only worried about syncing with Evolution (gpilotd) though and that works fine. A permanent entry for /dev/pilot doesn't make much sense given the things that they are doing with udev - mounting devices as a specific user. Craig
