Well, jpilot and the other pilot link tools don't technically *need* the
symlink - you can point them at whatever device you want, though
/dev/pilot is the default in most cases. But that's kind of missing the
point. Since the port devices are dynamically assigned, how else are
programs supposed to locate the Palm device - udev is all about working
with the information to pick the right ttyUSB device, pilot-link would
have to go grovelling for it.
mulberryst:~$ apt-cache policy libpisock9
libpisock9:
Installed: 0.12.3-5ubuntu6
Candidate: 0.12.3-5ubuntu6
Version table:
*** 0.12.3-5ubuntu6 0
500 http://proxy jaunty/main Packages
100 /var/lib/dpkg/status
--
/dev/pilot link is not always created correctly
https://bugs.launchpad.net/bugs/376521
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
