devfs
[Top] [All Lists]

Re: symlinks destroyed on boot for a zip drive

To: Robert <racsw@xxxxxxxxxxxxxxx>, Devfs <devfs@xxxxxxxxxxx>
Subject: Re: symlinks destroyed on boot for a zip drive
From: Russell Coker <russell@xxxxxxxxxxxx>
Date: Tue, 22 Oct 2002 11:19:06 +0200
In-reply-to: <200210210837.48896.racsw@xxxxxxxxxxxxxxx>
References: <200210210837.48896.racsw@xxxxxxxxxxxxxxx>
Reply-to: Russell Coker <russell@xxxxxxxxxxxx>
Sender: devfs-bounce@xxxxxxxxxxx
User-agent: KMail/1.4.3
On Mon, 21 Oct 2002 14:37, Robert wrote:
> my zip drive with supermount.   The reason is that something is wiping out
> my symlink called "hdd4" in the /dev directory.   Originally, I had a

/dev is effectively a ram-disk, every reboot clears it out...

> "/ide/host0/bus1/target1/lun0/part4".  If I go to create the link, I have
> to first eliminate the /hdd4 directory that is being created each time I

It sounds like something in your devfsd configuration or your boot scripts is 
creating it.  But as you didn't attach copies of any configuration files to 
your message it's difficult to even guess what the error might be.

What is 8.2 anyway?

> boot. I use this syntax:  "ln -s /dev/ide/host0/bus1/target1/lun0/part4 

That only creates it as a transient entry in a ram disk.  When you reboot it 
disappears.  You need to put something like the following in your devfsd 
config:
REGISTER        ^ide/.*      MKOLDCOMPAT
UNREGISTER      ^ide/.*      RMOLDCOMPAT

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


<Prev in Thread] Current Thread [Next in Thread>