From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: JWP <elseifthen@gmx.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: * RECALL * [PATCH 1/2] hwclock: hctosys drift compensation
Date: Tue, 16 Sep 2014 11:32:43 -0500 [thread overview]
Message-ID: <5418662B.5080409@gmail.com> (raw)
In-Reply-To: <54183647.2080101@gmx.com>
JWP wrote:
> 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. ?
/var/state is not in the Filesystem Hierarchy Standard.
"Applications must generally not add directories to the top level of
/var. Such directories should only be added if they have some
system-wide implication, and in consultation with the FHS mailing list."
-- Bruce
next prev parent reply other threads:[~2014-09-16 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 19:29 [PATCH 1/2] hwclock: hctosys drift compensation JWP
2014-09-14 19:46 ` [PATCH 2/2] hwclock: hctosys drift compensation man page JWP
2014-09-15 14:03 ` * RECALL * [PATCH 1/2] hwclock: hctosys drift compensation JWP
2014-09-16 9:35 ` Karel Zak
2014-09-16 13:08 ` JWP
2014-09-16 16:32 ` Bruce Dubbs [this message]
2014-09-16 23:08 ` JWP
2014-09-17 9:55 ` Karel Zak
2014-09-17 13:34 ` elseifthen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5418662B.5080409@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=elseifthen@gmx.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).