Hello Karel, On 09/16/2014 05:35 AM, Karel Zak wrote: > See Documentation/TODO, the writable /etc/adjtime sucks, because in > many cases we want to keep /etc read-only. I see two possible ways: Yes, I saw that and have it on my todo list. However, it is down my list a ways. I had not planned on attempting to integrate it into the hctosys/show patch. > -- the problem is that the file (specially last UTC/LOCAL line) > may be expected by another tools True, init scripts depend upon that information too. So it is an important consideration. My initial thought when I read u-l's todo list was that adjtimex [ -c | -a ] depend upon /etc/adjtime *drift* data. Do we care about breaking that? BJH's hwclock uses /var/state/adjtime, that seems like a good choice as well. ? I have often thought that hwclock should have a separate 'configuration' file, for example, to allow specific init behavior customization without requiring system admins to modify the init scripts. Will -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
