1 |
On Wed, 10 Aug 2011 14:28:09 +0300 |
2 |
Sergei Trofimovich <slyfox@g.o> wrote: |
3 |
|
4 |
> > > > Many modern systems have their /etc/resolv.conf files |
5 |
> > > > autogenerated at runtime with DHCP, PPP or so on. Thus, storing |
6 |
> > > > that file in /etc seems no longer correct as that directory may |
7 |
> > > > be mounted read-only. |
8 |
> > > |
9 |
> > > While i don't disagree on that move i'm suspocious about the |
10 |
> > > whole /etc/ ro mode. I don't think it's usable right now. Is your |
11 |
> > > main goal to make it working by default? |
12 |
> > |
13 |
> > I would really like to do so but I don't think I have enough power |
14 |
> > to do so. Right now, I'm running one machine with read-only root and |
15 |
> > resolv.conf was the only really problematic file for it. |
16 |
> |
17 |
> Ah, i see. |
18 |
> |
19 |
> > > - /etc/blkid* |
20 |
> > |
21 |
> > That one's udev specific? I guess it could be moved as well. |
22 |
> |
23 |
> It's a blkid(8) cache to mount stuff by uuid/label and guess FS. |
24 |
> Used at least by udev rules and stuff linked against libblkid |
25 |
> (fsck.*). Both can be triggered at any time later after boot. |
26 |
> blkid(8) can work w/o cache. |
27 |
|
28 |
'Cache' is the key-word here. I suggest pinging upstream |
29 |
that /var/cache is there for some reason. |
30 |
|
31 |
> > > - /etc/adjtime? |
32 |
> > |
33 |
> > I was never sure what this is for. Does it really need to be updated |
34 |
> > randomly during runtime or once is enough? |
35 |
> |
36 |
> It's saved/restored by hwclock(8) when system shutdowns/starts. |
37 |
> In theory hwclock can be reran time to time on running system, |
38 |
> but i don't think it's common. In-kernel copy of clock skew is |
39 |
> expected to be maintained by ntp-alike daemon. |
40 |
|
41 |
Ah, then it should be stored in /var indeed. |
42 |
|
43 |
-- |
44 |
Best regards, |
45 |
Michał Górny |