[Pkg-sysvinit-devel] Problem with RAMRUN/RAMLOCK if /var is mounted

Petter Reinholdtsen pere at hungry.com
Thu Jan 24 18:25:19 UTC 2008

[Edgar Fuß]
> 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 avoid this, some effort is taken to make sure the root file system
include /var/run/ on the file system, to allow it to be mounted before
/var/ is mounted, and then moved to the new /var/run/ when /var/ is
mounted.  An interesting question is why this is not the case for your
machine.  It should have been created when initscripts was installed
or upgraded.

> Who is supposed to access /var/run or /var/lock before /var is
> mounted anyway?

The daemons starting very early in the boot with the new event based
kernel, for example dhclient started via udev for those that want it.
An alternative is to use the new /lib/init/rw/ directory for status
info, but pid files are supposed to go into /var/run/.

Happy hacking,
Petter Reinholdtsen

More information about the Pkg-sysvinit-devel mailing list