Once you've put /dev/ttyUSB1 in Jpilot - File - Preferences - Settings you have no need from a Jpilot perspective /dev/pilot. That is how I've configured Jpilot in both SuSE and Ubuntu and it always works. If per chance another pilot synchronization facility like kpilot of gpilot has been started they will maintain control of that USB port and Jpilot won't have access. On 6/14/06, Dr. Scott S. Jones <scott at fyrenice.com> wrote: > > If you restarted udev (to reparse that new .rules file), and > > cradle your Palm and just hit HotSync. You should see a /dev/pilot > > created, if everything is working correctly. From this point, just > > point your tool(s) of choice to /dev/pilot, and it will always "Do The > > Right Thing(tm)" > > I restarted udev, then tried to sync and it froze again..requiring a cold > boot. > > Currently under Settings | Serial Port I have this> /dev/ttyUSB1 > > I also have the followin in /dev: > > scott at fyrenice:/dev$ ls -al pilot > lrwxrwxrwx 1 root root 12 2006-06-14 14:57 pilot -> /dev/ttyUSB1 > > this after running this: > > ln -s /dev/ttyUSB1 /dev/pilot > > > Still it seems to freeze up....What might I be missing yet? > > Scott > > _______________________________________________ > jpilot mailing list > jpilot at jpilot.org > http://www.jpilot.org/mailman/listinfo/jpilot > -- ____________ George Fragos fragos at gmail.com 73 East Swift Ave. Fresno CA 93704 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jpilot.org/pipermail/jpilot/attachments/20060614/f7b0fec6/attachment.htm
More information about the jpilot mailing list