From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 80311] New: Man page for /etc/hosts is inadequate
Date: Tue, 15 Jul 2014 21:17:42 +0000 [thread overview]
Message-ID: <bug-80311-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=80311
Bug ID: 80311
Summary: Man page for /etc/hosts is inadequate
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: low
Priority: P1
Component: man-pages
Assignee: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
Reporter: root-X6/7+m0v+V3YtjvyW6yDsg@public.gmane.org
Regression: No
I am editing a /etc/hosts file and hence reading the man page. I have noticed
two issues.
1: I wish to associate at least two host names with one IP number.
(killmartha.com and worik.org to start with). It is not clear in the man page
if I should use two lines:
IP_address1 hostname1
IP_address1 hostname2
or
IP_address1 hostname1 hostname2
In the second case hostname2 would be an alias for hostname1. From reading the
man page I am guessing I use two lines but it is not clear.
2: canonical_hostname is not defined in the document. (I am fairly sure I know
what it is but it should be defined in the document that uses it) and alias is
defined but it is not clear from the definition if it can be used in the one
line case above.
I am confident I can sort this out for myself. If so I can write what I think
should be added to the man page if any one agrees with me that this is a
problem.
Worik
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
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:[~2014-07-15 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 21:17 bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
[not found] ` <bug-80311-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2014-07-15 21:22 ` [Bug 80311] Not a bug at all bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2014-07-15 21:22 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
[not found] ` <bug-80311-11311-RtVInz26qy-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2014-07-16 7:09 ` walter harms
2014-07-16 7:17 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
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=bug-80311-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox