On Sat, Jun 4, 2011 at 8:54 PM, Dave Reisner
i just created a for-tom branch to get around the conflict i mentioned.
Thanks. I'll do the merge.
HARDWARECLOCK: the third line in /var/lib/hwclock/adjtime contains this information, and should be moved to /etc (following upstream), but discussion needed. The value is set by "hwclock --systohc --{utc,localtime}".
There's gotta be a reason that everyone puts the adjust file in /var/lib instead of /etc. I'm really not sure what that reason is, though.
adjtime contains the driftinformation, that is updated automatically and regularly, and hence really belongs in /var, it also contains the UTC/LOCALTIME info which is needed at early boot and only rarely changed by the admin, so belongs in /etc. The correct fix would be to submit a patch to upstream to split the file in two, but given the choice between the two evils, I think having it in /etc is the correct choice for now (as most people don't even use the drift information, and we can't use /etc ro anyway).
USECOLOR: not important, but we should be able to detect if color is supported...
Even if you can support color, you might not necessarily want it.
Why should anyone care? Then again, I guess I don't really care either way myself, so it can stay.
NETWORK_PERSIST: once we find a way to auto-detect if this is needed. This should be simple, but we would need someone with the relevant setup to test.
Very hard, if not impossible, to do with a high degree of accuracy. I think this one may need to stick around. Maybe there's a magical silver bullet I don't know about. Other distros maintain a list of network filesystem and tie that into their shutdown procedure to avoid killing the network.
I have forgotten, what does systemd do at the moment? They have a list? I guess that at some point the kernel must know that a given filesystem is a networked filesystem, so one would hope that this information was somehow exported in a generic way. -t