[Pkg-sysvinit-devel] Re: Supporting tmpfs on /var/run

Miquel van Smoorenburg miquels at cistron.nl
Tue Jan 3 14:47:19 UTC 2006

On Tue, 2006-01-03 at 15:34 +0100, Thomas Hood wrote:
> We need to make a decision about whether and how to support initialization of
> /var/run.  The options are:
>    0. Don't initialize /var/run at all.  If packages need subdirs or initial files
>       in /var/run then they create them in initscripts or elsewhere.
>    1. Copy a skeleton dir to /var/run.  I'd suggest something like this:
>             cp -a /etc/init-skeleton/var/run/* /var/run
>       which could be extended for use elsewhere, e.g.,
>             cp -a /etc/init-skeleton/run/* /run
>    2. Use dpkg-statoverride as described here:
>             http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/2005-December/000295.html
> As things stand now, I prefer #1 and hmh prefers #2.  So someone else will have
> to break the tie.  :)

Sorry. If we go with /run, then /var/run can be on normal disk, and in
that case I prefer #0. In the case of 'early /var/run' /var/run needs to
be on a tmpfs. Then I prefer #1, because it looks like #2 would add
significant startup delay.


More information about the Pkg-sysvinit-devel mailing list