public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: "Martin (Joey) Schulze" <joey-1lCxjdRlhQ9g9hUCZPvPmw@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: networks.5 man page
Date: Tue, 02 Sep 2008 11:21:11 +0200	[thread overview]
Message-ID: <48BD0587.4080803@gmail.com> (raw)

Hi Joey,

I see that Debian downstream has a networks(5) page (below) that you
wrote some years back (before my time as maintainer).  It seems
to me that it might make sense to take this page upstream.
What do you think?

Cheers,

Michael

PS The FreeBSD networks(5) page has some details not in your page
http://www.freebsd.org/cgi/man.cgi?query=networks&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE&format=html
Perhaps some of those details might also be usefully
covered in your page?

.\" Copyright (c) 2001 Martin Schulze <joey-1lCxjdRlhQ9g9hUCZPvPmw@public.gmane.org>
.\"
.\" This is free documentation; you can redistribute it and/or
.\" modify it under the terms of the GNU General Public License as
.\" published by the Free Software Foundation; either version 2 of
.\" the License, or (at your option) any later version.
.\"
.\" The GNU General Public License's references to "object code"
.\" and "executables" are to be interpreted as the output of any
.\" document formatting or typesetting system, including
.\" intermediate and printed output.
.\"
.\" This manual is distributed in the hope that it will be useful,
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
.\" GNU General Public License for more details.
.\"
.\" You should have received a copy of the GNU General Public
.\" License along with this manual; if not, write to the Free
.\" Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139,
.\" USA.
.\"
.TH NETWORKS 5 2001-12-22 "GNU/Linux" "Linux System Administration"
.SH NAME
networks \- network name information
.SH DESCRIPTION
The file
.I /etc/networks
is a plain ASCII file that describes known DARPA networks and symbolic
names for these networks.
Each line represents a network and has the following structure:

.RS
.I name number aliases ...
.RE

where the fields are delimited by spaces or tabs.
Empty lines are ignored.
If a line contains a hash mark (#), the hash mark and the remaining
part of the line are ignored.

The field descriptions are:

.TP
.I name
The symbolic name for the network.
.TP
.I number
The official number for this network in dotted-decimal notation.
The trailing ".0" may be omitted.
.TP
.I aliases
Optional aliases for the network.
.LP

This file is read by
.B route
or
.B netstat
utilities.
Only Class A, B or C networks are supported, partitioned networks
(i.e. network/26 or network/28) are not supported by this facility.
.SH FILES
.TP
.I /etc/networks
The networks definition file.
.SH "SEE ALSO"
.BR getnetbyaddr (3),
.BR getnetbyname (3),
.BR getnetent (3),
.BR route (8),
.BR netstat (8)

--
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

             reply	other threads:[~2008-09-02  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02  9:21 Michael Kerrisk [this message]
     [not found] ` <48BD0587.4080803-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-09-02 11:56   ` networks.5 man page Martin Schulze
     [not found]     ` <20080902115633.GK1145-huqzeb3D65vsIRsWchb81X4ryOshet8VQH7oEaQurus@public.gmane.org>
2008-09-02 12:04       ` Michael Kerrisk
     [not found]         ` <cfd18e0f0809020504v26c9b61bu6ad45ce56d5d5be6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-05  6:18           ` Michael Kerrisk
     [not found]             ` <cfd18e0f0809042318w25398e00n9772dfed69fbef0c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-05  7:35               ` Martin Schulze

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=48BD0587.4080803@gmail.com \
    --to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
    --cc=joey-1lCxjdRlhQ9g9hUCZPvPmw@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