From: Alejandro Colomar <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] uname.2: fix standard reference wording
Date: Wed, 15 Jun 2022 17:36:34 +0200 [thread overview]
Message-ID: <4246201e-0ee5-1019-4c5b-79b9d2d4cbc5@gmail.com> (raw)
In-Reply-To: <4a27c7c7295739005855299b23d1ab20b11e0110.1655287466.git.nabijaczleweli@nabijaczleweli.xyz>
[-- Attachment #1.1: Type: text/plain, Size: 2009 bytes --]
Hi наб,
On 6/15/22 12:04, наб wrote:
> Issue 6:
> IEEE Std 1003.1-2001/Cor 2-2004, item XBD/TC2/D6/27 is applied,
> changing the description of nodename within the utsname structure from
> ``an implementation-defined communications network'' to
> ``the communications network to which this node is attached, if any''.
>
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
> man2/uname.2 | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/man2/uname.2 b/man2/uname.2
> index 94c9c951a..b43f5d8d6 100644
> --- a/man2/uname.2
> +++ b/man2/uname.2
> @@ -29,8 +29,8 @@ struct is defined in
> .EX
> struct utsname {
> char sysname[]; /* Operating system name (e.g., "Linux") */
> - char nodename[]; /* Name within "some implementation\-defined
> - network" */
> + char nodename[]; /* Name within communications network
> + to which the node is attached, if any */
> char release[]; /* Operating system release
> (e.g., "2.6.28") */
> char version[]; /* Operating system version */
> @@ -73,9 +73,10 @@ So, four of the fields of the struct are meaningful.
> On the other hand, the field
> .I nodename
> is meaningless:
> -it gives the name of the present machine in some undefined
> -network, but typically machines are in more than one network
> -and have several names.
> +it gives the name of the present machine in some "the" network
That reads a bit weird. Is it a typo, or is it intended?
Regards,
Alex
> +to which it's attached,
> +but typically machines are in more than one network
> +and have several names by which they're reachable.
> Moreover, the kernel has no way of knowing
> about such things, so it has to be told what to answer here.
> The same holds for the additional
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-15 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 10:04 [PATCH 1/2] uname.2: fix standard reference wording наб
2022-06-15 10:08 ` [PATCH 2/2] uname.2: deweirdify наб
2022-06-15 11:58 ` [PATCH 1/2] uname.2: fix standard reference wording Stefan Puiu
2022-06-15 15:12 ` наб
2022-06-15 15:36 ` Alejandro Colomar [this message]
2022-06-15 16:29 ` наб
2022-06-15 16:36 ` Alejandro Colomar
2022-06-15 16:39 ` [PATCH v2 " наб
2022-06-15 16:39 ` [PATCH v2 2/2] uname.2: deweirdify наб
2022-06-15 16:59 ` Alejandro Colomar
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=4246201e-0ee5-1019-4c5b-79b9d2d4cbc5@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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