Re: ifupdown writes to /etc... a bug?
On Wed, 12 Mar 2003 11:50:02 -0500
Joey Hess <firstname.lastname@example.org> wrote:
> How about: /boot/state or such? /boot/run if you want it to be
> analagous with /var. The idea being that /boot tends to be small, and
> local, and that there is a mnemonic that this is stuff that gets
> written early during boot. The downside perhaps being that some admins
> choose to mount /boot ro most of the time. Just an idea.
/boot is a directory that is very static, the easiest to make read only.
Its not uncommon to have /boot on a seperate partition, it makes it
easier if you use lilo and ever resize the root partition.
Also by isolating /boot on its own partition its cotents are isolated
from filesystem problems on /
If one were to put run on the seperate /boot partition then the
increased writes on this partition would increase the possibility of fs
corruption. (if you have a dodgy filesystem)
The root directory is supposed to be a container for directories that
have different purpose, i think its purpose is different enough to earn
its place there.