Re: ifupdown writes to /etc... a bug?
In article <20030310133506.GB28596@khazad-dum>,
Henrique de Moraes Holschuh <email@example.com> wrote:
>On Mon, 10 Mar 2003, martin f krafft 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?
>Maybem but it probably creates a lot of headaches. /etc is the ONLY
>directory with guaranteed early write access. Some stuff IS bound to
>have to use /etc instead of /var.
>I would love to have ifstate go kabloom (as in not exist at all), though :)
Perhaps it is time for a /var/bootstate (with a better name though)
on which during early boot a shmfs is mounted, and as soon as
/var becomes available for mounting is copied over to the real
/var/bootstate and unmounted.
On shutdown this should be reversed ofcourse, so a seperate
directory /var/bootstate is needed - you can't copy /var/state
to shmfs in its entirity, it would potentially be way to big.
Would only work with shmfs enabled 2.4 kernels though. Maybe in woody+2 ..
Anyone who is capable of getting themselves made President should
on no account be allowed to do the job -- Douglas Adams.