On 04/18/2017 12:54 PM, Marko Myllynen wrote: > I think upper-casing hostnames was a thing of the 90s, is this ok? Thanks, Marko. Applied. Cheers, Michael > --- > man7/hostname.7 | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff --git a/man7/hostname.7 b/man7/hostname.7 > index 23c35e9..bc181a9 100644 > --- a/man7/hostname.7 > +++ b/man7/hostname.7 > @@ -41,8 +41,8 @@ > hostname \- hostname resolution description > .SH DESCRIPTION > Hostnames are domains, where a domain is a hierarchical, dot-separated > -list of subdomains; for example, the machine monet, in the Berkeley > -subdomain of the EDU domain would be represented as "monet.Berkeley.EDU". > +list of subdomains; for example, the machine "monet", in the "berkeley" > +subdomain of the "edu" domain would be represented as "monet.berkeley.edu". > > Hostnames are often used with network client and server programs, > which must generally translate the name to an address for use. > @@ -75,9 +75,9 @@ by searching through a list of domains until a match is found. > The default search list includes first the local domain, > then its parent domains with at least 2 name components (longest first). > For example, > -in the domain CS.Berkeley.EDU, the name lithium.CChem will be checked first > -as lithium.CChem.CS.Berkeley.EDU and then as lithium.CChem.Berkeley.EDU. > -Lithium.CChem.EDU will not be tried, as there is only one component > +in the domain cs.berkeley.edu, the name lithium.cchem will be checked first > +as lithium.cchem.cs.berkeley.edu and then as lithium.cchem.berkeley.edu. > +lithium.cchem.edu will not be tried, as there is only one component > remaining from the local domain. > The search path can be changed from the default > by a system-wide configuration file (see > > Thanks, > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html