before I upgraded my kernel to the 2.6 version everything worked fine. In the 2.6 kernel /dev/ttyUSB* does not exhist but I did as you said with the following results: bmike1 at 2[rules.d]$ sudo ln /dev/ttyUSB1 /dev/pilot ln: accessing `/dev/ttyUSB1': No such file or directory bmike1 at 2[rules.d]$ sudo ln /dev/ttyUSB0 /dev/pilot ln: accessing `/dev/ttyUSB0': No such file or directory bmike1 at 2[rules.d]$ On 12/10/06, David A. Desrosiers <desrod at gnu-designs.com> wrote: > On Sun, 2006-12-10 at 09:40 -0700, Michael Havens wrote: > > I am pretty goofy! > > In any case upon sync jpilot responded with: > > 'no such file or directory' > > > > So I created the directory and it currently responds: > > pi_bind error:/dev/pilot > > Ok, wait... stop stop stop! > > What problem are we trying to solve here? You're winding down a very > ugly, difficult and incorrect path here. > > If you follow the README.usb that came with pilot-link 0.12.1, you > should be pretty well-prepared to get your Palm syncronizing with your > Linux machine, barring any Palm/hardware/misconfiguration issues that > might be specific to your particular setup. > > /dev/pilot is a symlink, created automatically by a udev rule > (documented in the README.usb HOWTO I've written). It will appear when > you hit HotSync, and (hopefully, if your kernel and udev rules are > correct and your Palm device is supported), link /dev/ttyUSB1 > or /dev/ttyUSB0 to /dev/pilot. > > From there, you can then point pilot-xfer, J-Pilot or whatever you want, > at /dev/pilot and sync. When your Palm stops communicating, that symlink > (and the referrant device nodes) will disappear. > > Try that, see how far you get. > > > -- > David A. Desrosiers > desrod at gnu-designs.com > http://gnu-designs.com > > "The price of liberty is not free, nor is it comfortable. But it is > necessary" > >
More information about the jpilot mailing list