From: "John W. Linville" <linville@tuxdriver.com>
To: Anil Gunturu <anil.gunturu@gmail.com>
Cc: netdev@oss.sgi.com, nhorman@redhat.com
Subject: Re: NETLINK_ROUTE sockets in kernel
Date: Tue, 2 Nov 2004 16:44:40 -0500 [thread overview]
Message-ID: <20041102164440.B19501@tuxdriver.com> (raw)
In-Reply-To: <2f61ba570411021146657f63f4@mail.gmail.com>; from anil.gunturu@gmail.com on Tue, Nov 02, 2004 at 11:46:46AM -0800
On Tue, Nov 02, 2004 at 11:46:46AM -0800, Anil Gunturu wrote:
> Hi,
> I am trying to undestand the NETLINK_ROUTE protocol sockets on 2.4.18
> kernel. Specifically, I am interested in knowing how the kernel
Neil Horman <nhorman@redhat.com> has been working on a paper that
may be of use to you...
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2004-11-02 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 19:46 NETLINK_ROUTE sockets in kernel Anil Gunturu
2004-11-02 21:22 ` David S. Miller
2004-11-02 21:44 ` John W. Linville [this message]
2004-11-03 0:52 ` Neil Horman
2004-11-02 22:15 ` Herbert Xu
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=20041102164440.B19501@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=anil.gunturu@gmail.com \
--cc=netdev@oss.sgi.com \
--cc=nhorman@redhat.com \
/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).