Re: ifupdown writes to /etc... a bug?
Steve Langasek <firstname.lastname@example.org> writes:
> On Tue, Mar 11, 2003 at 12:21:45AM +1100, Glenn McGrath wrote:
> > On Mon, 10 Mar 2003 13:49:20 +0100
> > martin f krafft <email@example.com> wrote:
> > > before i file this with the BTS, gimme your opinions...
> > > ifupdown manages the state of interfaces with the file
> > > /etc/network/ifstate. this file is being written to. isn't that
> > > a violation of the FHS, and should ifstate not live under /var?
> > Yes, /var/state/ is a more appropriate place.
> No, /var/state/ is not an FHS directory.
> I also think the "/var may not be mounted yet" argument is a cop-out.
> The FHS says that "Some portions of /var are not shareable
> between different systems", which seems to preclude the possibility that
> a network-mounted /var will work correctly *anyway*. (The 'diskless
> workstation' argument is null -- if it's diskless, where is /etc
> located that makes it a better choice than /var?)
For diskless clients you can have one / for all clients with just some
files shadowed by host specific versions for each. That would be
mounted RO via nfs-root. You certainly don't want a diskless machine
to overwrite a file thats shared among a pool of systems. The /var
would be a different mount point per host and writeable.
Its only due to the disapearance of diskless clients that there is not
a lot of complaining about ifup/down.
> All of the other non-config files stored in /etc have to be available
> before other filesystems are mounted. Given that all local drives are
> mounted in the boot sequence before anything touches the network
> subsystem, I don't think this argument applies for /etc/network/ifstate.
My / (and thus /etc) is readonly and I like it that way.
/etc is no place for anything to write to.