From: Magnus Damm <damm@opensource.se>
To: linux-kernel@vger.kernel.org
Subject: incorrect help for NETLINK in 2.2.19
Date: Mon, 28 May 2001 18:02:39 +0200 [thread overview]
Message-ID: <3B12769F.CAC4ED8F@opensource.se> (raw)
Hi all,
I think I've found some incorrect helptexts in 2.2.19:
I've compared the netlink config options for 2.2.19 with 2.4.5.
1. CONFIG_NETLINK - Enabling netlink
The help in 2.4.5 seems correct to me.
2.2.19 raves about nodes under /dev with major 36. (BAD)
2. CONFIG_RTNETLINK - Route messages over netlink.
2.4.5 seems good here too.
2.2.19 tells us to create a /dev/route node. (BAD)
3. CONFIG_NETLINK_DEV - Enable support for major 36 nodes.
2.4.5 says that this option enables major 36 nodes.
2.2.19 says nothing useful at all. (BAD)
CONFIG_NETLINK_DEV enables major 36 char devices for both 2.2
and 2.4, right?
If that is true then I suggest that the 2.4.5-help for NETLINK
is used for next 2.2-kernel.
And - the help for CONFIG_RTNETLINK claims that data sent to the
kernel is ignored. Is that really true?
Tell me if you want a patch.
Thanks /
Magnus Damm
http://opensource.se - open source in sweden
reply other threads:[~2001-05-28 16:04 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=3B12769F.CAC4ED8F@opensource.se \
--to=damm@opensource.se \
--cc=linux-kernel@vger.kernel.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