devfs
[Top] [All Lists]

symlinks destroyed on boot for a zip drive

To: Devfs <devfs@xxxxxxxxxxx>
Subject: symlinks destroyed on boot for a zip drive
From: Robert <racsw@xxxxxxxxxxxxxxx>
Date: Mon, 21 Oct 2002 08:37:48 -0400
Sender: devfs-bounce@xxxxxxxxxxx
User-agent: KMail/1.4.3
Hello,
   I linux guru friend of mine in England sent me to you folks because of the 
battle I've been waging with my /dev symlinks.   He attributes the problem to 
the quirks of devfs.   Here's the problem.
   I have Mandrake 8.2 installed, and I have, among other devices, a 256Mb 
internal IDE zip drive installed.   When I had 8.2 installed without the 
Upgrade CD, things were working fine.  Since upgrading, I can no longer use 
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 symlink 
called hdd4@, a block device, that pointed to 
"/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 boot.  
I use this syntax:  "ln -s /dev/ide/host0/bus1/target1/lun0/part4  hdd4".
This successfully creates the link, and while I'm logged on, my zip functions 
fine as it originally did, all the files are available.
   When I reboot however, this symlink is wiped out, and replaced by that 
/hdd4 directory again, and again my zip fails to function.   This happens 
every time.   For now, seeing as I can't get around this issue unless you 
folks can help me out, I created the hdd4@ symlink inside of the /hdd4 
directory, and I had to change my fstab file to suit this new arrangement.   
I can use the zip, but only if I manually mount and umount the drive.   I 
would like to fix this problem so that the supermount feature once again 
works the way it's supposed to, and I won't have to mount the zip manually 
again anymore.
Can someone help me out with this?

P.S. - My system uses devfsd.

Thanks,
Robert


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