dev file goes missing after reboot

[Philip Walden]

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

[Rodolfo Alcazar Portillo]

Am Freitag, den 24.08.2007, 07:24 -0700 schrieb Philip Walden:
>  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 
The manual link is subject to be deleted by udev. But the very udev must
automathically create the link whenever the device is connected. I did
it this way:

https://www.redhat.com/archives/fedora-list/2007-June/msg02092.html

Good luck!
----------------------------------------------
Rodolfo Alcazar - rodolfo.alcazar(a)padep.org.bo
otbits.blogspot.com / counter.li.org: #367962
----------------------------------------------
Möge die Macht mit dir sein. Möge die Saft mit dir sein.

[Mikkel]

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!

[Philip Walden]

Mikkel L. Ellertson wrote:
>  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
>     
Modifying the udev rules worked for me.

You learn something new every day.

Thanksyou