Re: ifupdown writes to /etc... a bug?
On Wed, 2003-03-12 at 18:03, Joey Hess wrote:
> To put it another way, this is something that an admin can hack around
> as they are setting up a diskless type system. It needs no special
> support from Debian, though we should document that /var/run must be
> available before the network is brought up and could suggest that both
> /var's have links to a /run directory. Of course if d-i got support for
> setting up diskless systems, it would be modified to do that for the
> We then can just move anything we like into /var/run, and stop worrying
> about the issue. Seems reasonable to me.
Yes, that's the essence of it. One still does need to worry
about systems that have already been set up such that /var/run
doesn't meet the new criteria, and which would break if
early-accessed state files were suddenly moved there. How
should this be phased in? Announce at sarge release time that
"/var/run must henceforth be rw and network-independent", and
start moving files to /var/run in post-sarge package releases?
Thomas Hood <email@example.com>
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts