Hi! On Wed, Jun 15, 2022 at 02:58:27PM +0300, Stefan Puiu wrote: > On Wed, Jun 15, 2022 at 1:15 PM наб <nabijaczleweli@xxxxxxxxxxxxxxxxxx> wrote: > > @@ -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? Typo! This was supposed to be "some network". I've updated this locally but 2/2 replaces this line, so not resending (yet). > > +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"? It's 100% the case on all systems; your machine is reachable as both $(uname -n) and localhost (and, likely, $(uname -n).your.FQDN, and probably localhost6). localhost (and localhost6) is routed through a different network (obviously your LAN isn't 127/8; the addressof localhost == addressof $(uname -n) 4.2BSDism has died with 4.3BSD) and /through a different NIC/ (the lo prefix dates back to at least 4.2BSD). Also: a machine may only have one name (well, ex def., but also because what other nomenclatural facility beside uname -n is there? you could make the case for SVr3 uname -S that also wrote to sysname, but that's an abuse, and forbidden by the standard). That it's /reachable/ by multiple names doesn't change its utsname. I still think that as a small wording-fixup diff this diff stands, and the larger rewrite in 2/2 avoids this issue completely: > Conversely, the nodename field is configured by the administrator to > match the network (this is what the BSD historically calls the > "hostname", and is set via sethostname(2)). Best, наб
Attachment:
signature.asc
Description: PGP signature
