On Wednesday 01 May 2002 11:31 pm, R. Douglas Barbieri wrote: > There is a way to do that in the /etc/devfsd.conf. Here is a sample for > the cdrom device in my devfsd.conf file: > > LOOKUP ^cdrom$ CFUNCTION GLOBAL symlink cdroms/cdrom0 $devpath > > You may be able to use the DELETE keyword first to delete the hda1 > directory. Of course, there could be an entry in your devfsd.conf file > that's causing this strangness in the first place. > > *** > > I posted something a while back to vox-tech detailing how to actually > preserve the state of your /dev partition without having to alter the > devfsd.conf file. (/me searches vox-tech archives--ah! there it is!). > Add the following to the top of your rc.sysinit script:
The website says that only deals with permissions. > # Find this at > # http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html#persistence > # > echo -en "Mounting dev filesystem: " > /bin/mount --bind /dev /dev-state > /bin/mount -n -t devfs none /dev > echo > /sbin/devfsd /dev > > You have to make sure that the dev partition is *not* mounted on boot > (make sure this is turned off in the kernel, or just supply the > "devfs=nomount" kernel argument). > > Once rebooted, you may do as you did eariler: remove the /dev/hda1 > directory and then symlink it. On reboot, your state should be preserved. > > Doug > > On Wed, 1 May 2002, Ryan wrote: > > Instead of playing nice and symlinking /dev/hda1 to > > /dev/ide/host0/bus0/target0/lun0/part1 like it should, DevFsd keeps > > making /dev/hda1 an empty direcctory, thwarting my efforts to move my > > installation to a new hard drive. > > > > Oh , and before anyone asks, removing the empty directory and manualy > > creating the symlink works, but is undone when I reboot. > > > > How I fix? _______________________________________________ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
