Util-Linux package development
 help / color / mirror / Atom feed
From: J William Piggott <elseifthen@gmx.com>
To: Karel Zak <kzak@redhat.com>, Benno Schulenberg <bensberg@justemail.net>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 4/5] hwclock: add '11 minute mode' information
Date: Tue, 17 Mar 2015 21:16:16 -0400	[thread overview]
Message-ID: <5508D1E0.205@gmx.com> (raw)
In-Reply-To: <20150317095745.GT28925@ws.net.home>



On 03/17/2015 05:57 AM, Karel Zak wrote:
> On Sun, Mar 15, 2015 at 04:47:27PM +0100, Benno Schulenberg wrote:
>> "When in this state, bit 6 (the bit that is set in the mask 0x0040)
>> of the kernel's time_status variable is *unset*."
> 
> Yes, this is more readable (at least for me:-).

I explained to Mr Schulenbuerg that I wrote it that way for layman users. 
Are they going to understand 'the bit that is set in the mask 0x0040'?
What does that even mean? What does 'mask' have to do with it? It could
simply say "the bit that is set by binary 0x0040"
How does that differ from saying the binary 64's bit?

Using hex will help the average user how?

I used decimal because adjtimex displays the status variable as a decimal
number:

adjtimex -p
status: 8193

adjtimex -p
status: 8257

Which one is synchronized?

The adjtimex man-page says:

"status" gives the value of the time_status variable in the kernel.
64	clock unsynchronized

The average user will likely have trouble with this.

By saying 'the binary 64 bit' it will allow average users to understand
the relationship.  When Bryan originally wrote this section (it was
removed because of the adjtimex issue), he used the same language 'the 64
bit'. I suspect he did it for the same reasons. I added the binary
number example to help people that do not understand binary to visualize 
exactly where the the unset bit would be. Then if they manage to convert
the adjtimex output from decimal to binary it should be clear to them.

Calling it bit 6 will likely cause average users to make an off-by-one
error. There is no ambiguity with the binary 64 bit.

Karel, it makes good sense to you because you have a clear understanding of
binary bit masks. Does the rest of the world have the same
understanding?

What I wrote is far from optimum, but I do not think this is an
improvement.

> 
>>> +It can be turned off by running anything, including
>>>  .BR \%hwclock\ \-\-hctosys ,
>>>  that sets the System Clock the old fashioned way.
>>
>> I would move the "including..." phrase to the end of the sentence,
>> as now one at first thinks that really *anything* can turn 11-minute
>> mode off.
> 
> I have applied this two changes.
> 
>     Karel
> 
> 

  reply	other threads:[~2015-03-18  1:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 19:11 [PATCH 1/5] hwclock: add TZDIR J William Piggott
2015-03-13 19:15 ` [PATCH 2/5] hwclock: Improve FILES section J William Piggott
2015-03-13 19:18 ` [PATCH 3/5] hwclock: remove depreciated ntpdate J William Piggott
2015-03-15 15:26   ` Benno Schulenberg
2015-03-16  0:19     ` Isaac Dunham
2015-03-16 10:33     ` Karel Zak
2015-03-17  3:37       ` J William Piggott
2015-03-17  9:29         ` Karel Zak
2015-03-17 21:10           ` J William Piggott
2015-03-13 19:22 ` [PATCH 4/5] hwclock: add '11 minute mode' information J William Piggott
2015-03-15 15:47   ` Benno Schulenberg
2015-03-17  9:57     ` Karel Zak
2015-03-18  1:16       ` J William Piggott [this message]
2015-03-18  9:43         ` Karel Zak
2015-03-13 19:26 ` [PATCH 5/5] hwclock: man-page errata J William Piggott
2015-03-15 15:51   ` Benno Schulenberg
2015-03-15 15:20 ` [PATCH 1/5] hwclock: add TZDIR Benno Schulenberg
2015-03-16 10:30   ` Karel Zak
2015-03-17  9:58 ` 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=5508D1E0.205@gmx.com \
    --to=elseifthen@gmx.com \
    --cc=bensberg@justemail.net \
    --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