On Sun, 2006-12-10 at 13:23 -0500, David A. Desrosiers 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. > > but if you're dealing with the same issue i'm dealing with (with Ubuntu Dapper), you find there's a kernel bug that won't allow communication to work with the device. > _______________________________________________ > jpilot mailing list > jpilot at jpilot.org > http://www.jpilot.org/mailman/listinfo/jpilot -- jack wallen, jr /"\ ASCII Ribbon Campaign spreading the word of \ / Respect for open standards gender equality and the FSF X No HTML/RTF in email http://www.monkeypantz.net / \ No M$ Word docs in email
More information about the jpilot mailing list