Skip site navigation (1)Skip section navigation (2)
Date:      19 Mar 2002 11:51:26 -0800
From:      swear@blarg.net (Gary W. Swearingen)
To:        Hiten Pandya <hitmaster2k@yahoo.com>
Cc:        freebsd-doc@FreeBSD.ORG
Subject:   Re: docs/35949: [PATCH] rtprio(1) man page uses incorrect english
Message-ID:  <jc4rjc9w01.rjc@localhost.localdomain>
In-Reply-To: <200203191050.g2JAo4139312@freefall.freebsd.org>
References:  <200203191050.g2JAo4139312@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hiten Pandya <hitmaster2k@yahoo.com> writes:

>  Hmm, OK.  If you guys think the patch is not worth it to go into the
>  rtprio(1) man page, and the previous english is/was correct, then you
>  can close the PR with success.  Otherwise I can submit another patch
>  which has the type of clarity wanted (the comma stuff). 8-)

Everything I've read welcomes such PRs and many, lowest priority,
innocous mispellings are the first PRs to get dealt with.  Go for it.

As for the offending paragraph:
  There is in FreeBSD no way to ensure that a process page is present in
  memory therefore the process may be stopped for pagein (see
  mprotect(2), madvise(2)).
it would be better as
  There is, in FreeBSD, no way to ensure that a process page is present in
  memory, therefore the process might be stopped for pagein.  See
  mprotect(2) and madvise(2).
(as "in FreeBSD" is a sort of parenthetical clause and "might" expresses
probability better than "may" which usually expresses permission),,
or better (as was suggested previously):
  In FreeBSD, there is no way ...
Many would omit the comma, but I put commas where I pause in speech.

One could argue that "In FreeBSD" is dragging in a comment on a VM
design issue that has no place in this manual.

One could also argue that the whole paragraph doesn't belong this manual
because it really has nothing to do with the design or implementation of
the program, nor even its specification.  Note that the "process"
referred to is not the "rtprio" process.  Any fix of the "bug" would be
almost certainly be done in another program.  (Maybe the paragraph
should be in a "Comments" section.  You can bet that some people
wouldn't be happy with the paragraph's deletion.)

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?jc4rjc9w01.rjc>