Hi Наб,
On Wed, Jun 15, 2022 at 1:15 PM наб <nabijaczleweli@xxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxx>
> ---
> 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
Maybe "in one network" sounds better here?
> +to which it's attached,
> +but typically machines are in more than one network
> +and have several names by which they're reachable.
I'm not sure the use case of many networks and many names is typical,
though it is common. Maybe we can rephrase this to "Note the machine
might sit in more than one network and have several names"?
Thanks,
Stefan.
> 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
> --
> 2.30.2
>
