There seems to be a problem with setting RAMRUN/RAMLOCK to yes in case /var is a seperate file system.
Although /lib/init/mount-functions.sh goes into great lenghts to preserve a tmpfs /var/run or /var/lock, the mount in /etc/init.d/mountkernfs will have failed because /var will not have been mounted at this early stage and the root fs will most probably lack the mount point var/run (since the file system to be mounted on /var contains the mount point run). To be honest, I'm not sure what all this hassle with preserving /var/run is all about. If /var is not a file system, you don't need it. If /var is a file system and RAMRUN=no, then /var/run will be hidden by the mount anyway (and nothing be done about it). If /var is a file system and RAMRUN=yes, it all failes as described above. Who is supposed to access /var/run or /var/lock before /var is mounted anyway? A quick work-around is to mount /var in /etc/init.d/mountkernfs before memory file systems are mounted on top of /var/run or /var/lock. But this will give a warning in case /var is not a seperate file system. _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
