On Wed, 10 Aug 2011 13:37:30 +0300
Sergei Trofimovich <slyfox@g.o> wrote:

> On Wed, 10 Aug 2011 11:55:19 +0200
> Michał Górny <mgorny@g.o> wrote:
> 
> > Hello,
> > 
> > Many modern systems have their /etc/resolv.conf files autogenerated
> > at runtime with DHCP, PPP or so on. Thus, storing that file in /etc
> > seems no longer correct as that directory may be mounted read-only.
> 
> While i don't disagree on that move i'm suspocious about the
> whole /etc/ ro mode. I don't think it's usable right now. Is your
> main goal to make it working by default?

I would really like to do so but I don't think I have enough power to
do so. Right now, I'm running one machine with read-only root and
resolv.conf was the only really problematic file for it.

> [assuming it is] What is the plan of other volatile stuff in /etc?
> - /etc/mtab

I personally symlink it to /proc/mounts as I don't need additional
features it provides.

> - /etc/mtab.fuselock

Never heard of this one. But I guess it's FUSE-specific and thus easy
to move. I guess you can open a bugreport for it.

> - /etc/blkid*

That one's udev specific? I guess it could be moved as well.

> - /etc/adjtime?

I was never sure what this is for. Does it really need to be updated
randomly during runtime or once is enough?

> Move to /var for default setup as well?

I'd personally prefer /run instead of /var for things that aren't
supposed to last longer than for a single boot.

-- 
Best regards,
Michał Górny