I have created a symoblic link to /dev/ttyS0 called /dev/pilot. I am using Fedora 3 but on the reboot the symbolic link disappears. Also I am trying to keep the permissions to /dev/ttyS0 to 0666. Please advice so that I can keep my symbolic link and permission on reboot. Thanks in advance.

What are you attempting to accomplish?

What i am trying to do is setup gnome-pilot to work with Evolution. Each time I press the Hot-Sync on the Palm Pilot it does not sync. So to check if it is working after a reboot, I use pilot-xfer -p /dev/pilot -l to check if the palm pilot is seen by the system. I get the following message:

$> pilot-xfer -p /dev/pilot -l
The device /dev/pilot does not exist..
Possible solution:

mknod /dev/pilot c <major> <minor>

Unable to bind to port: /dev/pilot
Please use --help for more information

Then I recreate the link using ln -s /dev/ttyS0 /dev/pilot as root. I rerun the pilot-xfer command and receive the following message:


$> pilot-xfer -p /dev/pilot -l
Please check the permissions on /dev/ttyS0..
Possible solution:

chmod 0666 /dev/ttyS0

Unable to bind to port: /dev/pilot
Please use --help for more information


Once I do sthe chmod command, it works.


$> pilot-xfer -p /dev/pilot -l

Listening to port: /dev/pilot

Please press the HotSync button now...



Let me know what I need to do so I do not have to setup the symbolic link and the permissions everytime I boot. Thanks for responding.

Perfect. I'm not sure which distro you are using but with Slackware, there is a file called /etc/rc.d/rc.local. It is made to be a script file that can run user specified commands whenever the computer is started up. All you do is add the necessary commands and they run each time the computer starts up.

is that possible to write this command into .bashrc?

What kernel are you using? If it's a 2.6 udev pretty much controls creation of the /dev directory and you would have to add an additional rule to create that symlink.

Yes I am using 2.6 thanks for the tip. I will read up on how to make a new rule thanks.

the permissions is easy
/etc/udev/permissions.d
and go for the one numbered earliest and in there you find permissions being set for the device
it uses the four numbers format for permissions
ignore the first number
the rest are user,group,others
4=read
2=write
1=execute

man for the link i would just put it in the bootscripts for now -- at the bottom of something that starts last or something -- i wrote mine at the bottom of my firewal script

it's a hack but the alternative is figuring out those udev rules (roll eyes)