Re: ifupdown writes to /etc... a bug?
On Tue, 2003-03-11 at 08:10, Anthony Towns wrote:
> On Mon, Mar 10, 2003 at 09:41:32AM -0600, Steve Langasek wrote:
>
> Why did you start cc'ing Bug#84074? It is on an entirely different topic.
#84074: ifdown: cannot work if ifstate cannot be written to
There's a discussion about the location of ifstate file in there.
Emile: How about calling the new directory "/run" ?
That eliminates the implication that it has to be a ramfs.
It also implicates a functional similarity with /var/run, which
it does seem to have. (/run is like /var/run but is guaranteed
to be rw and available early. In some cases, one of these might
be symlinked to the other.)
Filesystem Hierarchy Standard
5.10 /var/run : Run-time variable data
This directory contains system information data describing the system
since it was booted. Files under this directory should be cleared
(removed or truncated as appropriate) at the beginning of the boot
process. Programs may have a subdirectory of /var/run; this is
encouraged for programs that use more than one run-time file.
--
Thomas Hood <jdthood0@yahoo.co.uk>
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
Reply to: