[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ifupdown writes to /etc... a bug?



On Sat, Mar 15, 2003 at 04:45:09PM +0100, Thomas Hood wrote:
> On Fri, 2003-03-14 at 23:11, Anthony Towns wrote: 
> > Munging around with /var/run is unnecessarily complicated, buys us
> > _nothing_ but pain, and is probably impossible to do reliably. "/run"
> > is a solution that's easy to handle, easy to convert all existing systems
> > to, easy to describe, reliable, and easily adaptible for admins who want
> > to run their systems differently.

> How to implement this?  The easiest way is to do nothing.  Currently,
> ifupdown writes its state files in /etc, which works fine on many
> systems.  If an individual admin wants to make /etc readonly then
> he can do:
>     mkdir /run /run/network
>     mv /etc/network/ifstate /run/network/ifstate
>     ln -s /run/network/ifstate /etc/network/ifstate

This ignores the FHS problem with using /etc/network/ifstate at all (in
the case of /etc/mtab, it follows the letter of the FHS, but the FHS
could stand some improvement here: /etc/mtab is a historical wart).

-- 
Steve Langasek
postmodern programmer

Attachment: pgpQI1TzCIGiR.pgp
Description: PGP signature


Reply to: