[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]


I've just been playing with udev version 0.070-3.  It seems that it's start 
script runs after /etc/init.d/mountvirtfs.  This means that when it umount's 
the /dev/pts and /dev/shm file systems it has to mount them again.

It seems that the best solution would be to have mountvirtfs split into two 
parts, one mounts /proc and /sys, the other mounts /dev/pts, /dev/shm (and 
anything else that might get added under /dev).  This means that 
under /etc/rcS.d we might have S02mountprocsys and S04mountptsshm so that 
S03udev can be run between them.

Also the udev script is rather complex.  It seems to me that a better option 
might be to have the /etc/init.d/udev script call a udev setup script (maybe 
named /sbin/setup_udev) and then start the udevd.

One of the reasons for not wanting complex init.d scripts is that for SE Linux 
we don't want to give ultimate access to such scripts.  The udev script does 
many things such as creating directories and device nodes under /dev which we 
normally want to restrict as much as possible.

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

Reply to: