On Fri, Jan 16, 2015, at 04:15, Peter Cordes wrote:
> > + based on libfdisk. If your use cases depend on sfdisk(8) then it is strongly
>
> Should put a comma after "sfdisk(8)".
True. Will be in V2.
> > + The new version no longer supports some obscure MBR-specific command-line
> > options and legacy CHS addressing.
>
> s/and/or/ in the last line. "no longer supports x or y" is the proper
> usage here.
Hmm. I would tend to use "nor" here. It may not be grammatical or
proper usage, but I think it is the most clear. ("No longer foo or bar"
works fine, but "no longer foo-foo-baz-foo-baz or bar" is unclear to me --
the negation has been mostly forgotten when the eye arrives at "or bar".
The "nor" is then a nice reminder.)
> > + The command hwclock(8) does not automatically (re)calculate the drift factor on
> > + --systohc to avoid several problems (ntpd with '11 minute mode', for example),
> > + but the new command-line option --update-drift has to be explicitly used to
> > + force hwclock(8) to update /etc/adjtime.
>
> Can we just start the sentence "hwclock(8) ...", instead of "The
> command hwclock(8)"? I don't think there's any ambiguity that you
> might actually be talking about the man page.
True. But it's what Karel wrote, and it's fine, it works.
> > - supports new options --reload to force already running agetty processes to
> > - reprint /etc/issue file.
> > + reprint the /etc/issue file
>
> "reprint /etc/issue" would work, and be shorter.
Same comment as above.
> > - - supports sfdisk compatible scripts, it's possible to save your partitioning
> > - layout to text files and (re)use it in all fdisks.
> > + - supports sfdisk compatible scripts; it's possible to save your partitioning
> > + layout to text files and (re)use it in all fdisks
>
> Kudos for good use of a semicolon. I always like a good semicolon. :)
:)
> > + - supports new command-line option "-o <list>" with the same semantic as
>
> semantics, not semantic.
Right. Will be in V2.
> > + -o for mount(8); it's now possible to specify swap options on the command
> > + line by the same string as in fstab
>
> I think "with the same string", rather than "by the same string".
Well, "is specified by" gives me many more google hits than "is specified with".
This comparison may not be valid, but I think "by" is okay here. And even if
most native speakers would prefer "with" here, I think it's fine to let some of
the foreignness of Karel's tongue sound through in his text.
> > +The debug infrastructure in the libraries libmount, libsmartcolsm, libfdisk and
> > +libblkid allows to specify debug options by human-readable strings too. For
> > example "LIBMOUNT_DEBUG=all mount /mnt".
>
> "libblkid allows specifying debug options with human-readable strings, too. For"
>
> would read a bit better.
To a native speaker probably yes. But I'm trying to make the minimum
amount of changes, fixing just the things where my comprehension is
hindered. There's no need to make this text into "English English";
"understandable and acceptable foreigner English" seems good enough.
Thanks for the review.
Shall I add a Reviewed-by tag to V2? Or an Acked-by?
Benno
--
http://www.fastmail.com - Does exactly what it says on the tin
--
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
