Philip Walden wrote: > I have just started using jpilot to sync my Palm-top. > > Jpilot expects to have /dev/pilot links to the device file connecting > the palmtop. In this case, I do a > > ln /dev/ttyS0 /dev/pilot > chmod o+rw /dev/pilot > > This work great. However, when I restart the computer the next day, the > link is gone. I have to recreate it. > > This is the first I have noticed this behavior. Any idea as to why this > happens? > > Phil > Because Fedora is using udev to control device entries, devices and symlinks that you create yourself do not survive a reboot. This is because /dev is a memory file system, not a real directory on the hard drive, once udev is started. (Sort of like the /proc file system. "/dev /dev tmpfs rw 0 0") The way to get lasting symlinks is to create a udev rule for it. I probably create a file in /etc/udev/rules.d/55-palm.rules for the rules. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
