From: Karel Zak <kzak@redhat.com>
To: Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: Suggested changes to util-linux for FHS compliance.
Date: Fri, 19 Feb 2021 12:30:09 +0100 [thread overview]
Message-ID: <20210219113009.mav3dis3qzofru4c@ws.net.home> (raw)
In-Reply-To: <20210215091625.jzaf6ephntdwmi5w@ws.net.home>
On Mon, Feb 15, 2021 at 10:16:30AM +0100, Karel Zak wrote:
> On Fri, Feb 12, 2021 at 11:04:59AM -0600, Bruce Dubbs wrote:
> > I don't recall if this has come up before, but I suggest a couple of changes
> > to the default util-linux build configuuration:
> >
> > 1. Change the default ADJTIME_PATH to be /var/lib/hwclock/adjtime
>
> Good idea. I'll do that.
Hmm... I remembered now that we have in our TODO:
hwclock
------
- use /var/lib/hwclock/drift to store hw-clock drift numbers.
- use /etc/adjtime as read-only for UTC/LOCAL information only
- the /var/lib/hwclock/drift should be implemented backwardly compatible,
it means use the file only if exists, otherwise follow /etc/adjtime
so maybe the best would be to keep ADJTIME_PATH=/etc/adjtime and use
it as read-only and use ${localstatedir}/lib/hwclock/drift for the
rest.
Note that ADJTIME_PATH is used by more utils, like rtcwake or systemd,
so move it is not so easy.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2021-02-19 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 17:04 Suggested changes to util-linux for FHS compliance Bruce Dubbs
2021-02-15 9:16 ` Karel Zak
2021-02-18 15:37 ` Bruce Dubbs
2021-02-19 11:14 ` Karel Zak
2021-02-19 17:12 ` Bruce Dubbs
2021-02-19 11:30 ` Karel Zak [this message]
2021-03-08 11:21 ` Karel Zak
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=20210219113009.mav3dis3qzofru4c@ws.net.home \
--to=kzak@redhat.com \
--cc=bruce.dubbs@gmail.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).