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

Re: /run and read-only /etc

I'm concerned about the mess that could result in changing a bunch of
stuff.  Suggestion:

If all affected files are in a subdir, If root is read-only, mount a
tmpfs, use --bind mount to put the tmpfs fs over the read-only config
dir.  output of dhcp/ppp etc will be captured at startup, then if/when
root is rw umount the --bind, and copy it all into place in the real
config dir.  It's no less messing about, but after it's done, it's as if
it never happened, and packages/progs don't need to be modified, except
to put stuff in a subdir (don't want to do this to entire /etc).

2.2 kernels are out though.



On Wed, 2003-04-09 at 01:11, Anthony DeRobertis wrote:
> On Tue, 2003-04-08 at 06:10, Marco d'Itri wrote:
> > On Apr 08, Anthony DeRobertis <asd@suespammers.org> wrote:
> > 
> >  >>  >  * util-linux
> >  >>  >       #156489: Move /etc/adjtime under /var/lib
> >  >> This may have some merit, but you can use a symlink.
> >  >"This would be a FHS violation."
> > The FHS does not apply to local changes.
> Leaving /etc/adjtime as is and telling admins to "move it and use a
> symlink" is a FHS violation because /etc/adjtime is.
> /etc has a "static nature". See the note on /etc/mtab under Table
> It is also for configuration files. /etc/adjtime is neither.
Jeremy Jackson <jerj@coplanar.net>

Reply to: