From: Marko Myllynen <myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [PATCH] Use lower case for hostname example
Date: Tue, 18 Apr 2017 13:54:33 +0300 [thread overview]
Message-ID: <142de45e-6ca5-bfea-60ab-9d634740a709@redhat.com> (raw)
I think upper-casing hostnames was a thing of the 90s, is this ok?
---
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,
--
Marko Myllynen
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-04-18 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 10:54 Marko Myllynen [this message]
[not found] ` <142de45e-6ca5-bfea-60ab-9d634740a709-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-18 20:00 ` [PATCH] Use lower case for hostname example Florian Weimer
[not found] ` <dc80bc0c-97ed-c06b-a9f8-328f7e9c07f0-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-26 10:07 ` Marko Myllynen
[not found] ` <9c83498f-bb57-4263-bfb0-fb12ac5cf8d6-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-26 11:14 ` Michael Kerrisk (man-pages)
2017-04-25 13:36 ` Michael Kerrisk (man-pages)
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=142de45e-6ca5-bfea-60ab-9d634740a709@redhat.com \
--to=myllynen-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.