From: Paul Bolle <pebolle@tiscali.nl>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-doc@vger.kernel.org, netdev@vger.kernel.org
Subject: Documentation: is there a reason to keep networking/policy-routing.txt
Date: Wed, 25 Jun 2014 16:47:58 +0200 [thread overview]
Message-ID: <1403707678.1960.60.camel@x220> (raw)
0) Documentation/networking/policy-routing.txt was added in v2.1.16.
Since then it has only received spelling fixes. That shows. I'll list
the issues I noticed below. Perhaps this file could be updated, and that
might even be trivial to do. But is that file still relevant? And
besides, why bother to keep documentation that appears to be
unmaintained for 18 years now?
1) RT_CLASS_LOCAL, RT_CLASS_MAIN, and RT_CLASS_DEFAULT: should probably
be RT_TABLE_LOCAL, etc.
2) RTP_ROUTE, RTP_NAT, RTP_MASQUERADE, RTP_DROP, RTP_REJECT, and
RTP_PROHIBIT: cannot be found in the tree.
3) RTRF_LOG, and RTRF_VALVE: ditto.
4) It mentions an iproute command. I'm familiar with route and "ip
route". Fedora doesn't ship an iproute command. Web searches for it are
hard, but it appears to have shipped in (old releases of) Debian.
5) The "IMPORTANT NOTE" about CONFIG_IP_LOCAL_RT_POLICY is obsolete
since v2.1.68.
Paul Bolle
reply other threads:[~2014-06-25 14:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1403707678.1960.60.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).