util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benno Schulenberg <bensberg@justemail.net>
To: JWP <elseifthen@gmx.com>
Cc: "Util-Linux" <util-linux@vger.kernel.org>
Subject: Re: [PATCH 4/4] docs: improve wording and formattin of man page of hwclock
Date: Tue, 28 Oct 2014 21:02:12 +0100	[thread overview]
Message-ID: <1414526532.495299.184374637.2BF00A99@webmail.messagingengine.com> (raw)
In-Reply-To: <544EECC9.2000300@gmx.com>


On Tue, Oct 28, 2014, at 02:09, JWP wrote:
> On 10/27/2014 05:18 PM, Benno Schulenberg wrote:
> >  Since v2.26
> >  .B hwclock
> >  does not update the Hardware Clock's drift factor in @ADJTIME_PATH@ by default.
> > -It is necessary to use \fB\-\-update-drift\fR, with \fB\-\-set\fR or
> > +It is necessary to use the option \fB\-\-update-drift\fR, with \fB\-\-set\fR or
> >  \fB\-\-systohc\fR, to force drift factor updates.
> 
> The rest of the manual uses 'the --xxxx option'.

Well, I can't explain, but in this case "the option --xxxx" is better.

> >  Since v2.26
> >  .B hwclock \-\-hctosys
> > -automatically compensates time read from the Hardware Clock to account for
> > -systematic drift before using it to set the System Clock.  Therefore,
> > -\fB\-\-adjust\fR is no longer necessary during boot. This functionality makes
> > -hwclock usable early in the boot process when the root filesystem is read-only.
> > +automatically takes a systematic drift of the Hardware Clock into account,
> > +setting the System Clock to the drift-compensated time.  Therefore the option
> > +\fB\-\-adjust\fR is no longer necessary during boot.  This feature makes
> > +.B hwclock
> > +usable early on in the boot process when the root filesystem is read-only.
> 
> "a systematic drift"? That entire phrase does not sound natural to me.

:|

> I think it is important to
> stress that *the_time_read* from the Clock is what is being compensated as this is
> a new behavior.

Well, then suggest how exactly to phrase that.

Benno

-- 
http://www.fastmail.fm - Or how I learned to stop worrying and
                          love email again


  reply	other threads:[~2014-10-28 20:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 21:18 [PATCH 1/4] docs: spelling, wording, and grammar fixes in the man page of whereis Benno Schulenberg
2014-10-27 21:18 ` [PATCH 2/4] docs: fix some wording and formatting in man page of swapon Benno Schulenberg
2014-10-31  9:48   ` Karel Zak
2014-10-27 21:18 ` [PATCH 3/4] textual: slice up the usage text of swapon for ease of translation Benno Schulenberg
2014-10-27 21:24   ` Benno Schulenberg
2014-10-31  9:32     ` Karel Zak
2014-10-31  9:48   ` Karel Zak
2014-10-27 21:18 ` [PATCH 4/4] docs: improve wording and formattin of man page of hwclock Benno Schulenberg
2014-10-28  1:09   ` JWP
2014-10-28 20:02     ` Benno Schulenberg [this message]
2014-10-31  9:51       ` Karel Zak
2014-11-02 17:53         ` JWP
2014-11-03 21:15           ` Benno Schulenberg
2014-11-04 13:16             ` JWP
2014-11-18 13:05               ` Karel Zak
2014-11-18 19:48                 ` Benno Schulenberg
2014-11-19  7:26                   ` Karel Zak
2014-10-31  9:47 ` [PATCH 1/4] docs: spelling, wording, and grammar fixes in the man page of whereis 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=1414526532.495299.184374637.2BF00A99@webmail.messagingengine.com \
    --to=bensberg@justemail.net \
    --cc=elseifthen@gmx.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).