The problem for me is that the device is created and destroyed when you press the hotsync button. Pilot sync and jpilot seem to depend on the device being present all the time.
To get it to work reliably, you have to guess accurately when the device is present and coordinate starting the sync (software) and pressing the hot sync button - a fairly narrow window as it takes time for udev to create the device. I can sync reliably once I worked out the timing! jpilot works well, but pilot sync requires cleaning out (kill the process(es)) between syncs. Yes its crap :( and udev is supposed to be an advance? BillK On Wed, 2006-07-12 at 21:04 +0200, [EMAIL PROTECTED] wrote: > Selon "Timothy A. Holmes" <[EMAIL PROTECTED]>: > > > > On 11/07/06, Timothy A. Holmes <[EMAIL PROTECTED]> wrote: > > > > > > > > > > I have followed the above Wiki article, and have hit a snag. > > > > > > Further down the same webpage it also gives instructions on creating a > > > udev rule . . . > > > > > > Also, check the links at the bottom of the page and the forum. > > > > > > HTH > > > -- > > > Regards, > > > Mick > > > -- > > > gentoo-user@gentoo.org mailing list > > > > [Timothy A. Holmes] > > > > Hi Mick -- I have followed the instructions on creating the UDEV rule, > > and everything works perfectly up to that point. > > > So have I, and it works every once in a while... Sometimes it works 2 or 3 > times > in a row, sometimes it just can't read /dev/pilot (that does exist...) > Finally, I use the final solution as described in the wiki page : create dirs > and links at boot time. Works fine... > Conclusion udev is flaky regarding PDA's sync. -- William Kenworthy <[EMAIL PROTECTED]> Home! -- gentoo-user@gentoo.org mailing list
