From: jamal <hadi@cyberus.ca>
To: Wietse Venema <wietse@porcupine.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, <kuznet@ms2.inr.ac.ru>,
Matthias Andree <matthias.andree@gmx.de>,
<linux-kernel@vger.kernel.org>, <linux-net@vger.kernel.org>,
<netdev@oss.sgi.com>
Subject: Re: [PATCH] ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19
Date: Thu, 6 Sep 2001 16:20:39 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.30.0109061612450.14727-100000@shell.cyberus.ca> (raw)
In-Reply-To: <20010906195958.222DFBC06C@spike.porcupine.org>
On Thu, 6 Sep 2001, Wietse Venema wrote:
> Alan Cox:
> > > Soldiers are marching down the street. The mother of one of those
> > > soldiers is ever so proud. All the other guys are marching out of
> > > step. Her son is the only one who does it right.
> > >
> > > That's what it looks like for a person who writes Internet software
> > > that aims to work on a wide variety of platforms.
> >
> > I think you have the metaphor wrong. The older API is a bit like the
> > cavalry charging into battle at the start of world war one. It may have been
> > how everyone did it but they guys with the "newfangled, really not how it
> > should be done, definitely not cricket" machine guns got the last laugh
>
> Keep your superiority complex out of my mailbox, thank you.
>
Wietse,
netlink, as a few people have pointed to you is the 'proper' way to do
things. Sure, the BSDs did it the way you love it, but linux is a
different operating system (cut the "if its not Scottish its crap
mentality"). Netlink does improve on "the way its always been done for
the last 80 years". Infact netlink has already been approved to be (at
least informational) RFC. Look at a slightly dated draft at:
http://search.ietf.org/internet-drafts/draft-salim-netlink-jhshk-00.txt
Maybe you should preach to the BSDs about netlink?
cheers,
jamal
PS:- If you want help on writting netlink based code to achieve what you
are trying to do, just yell. Look at the source for the ip utility which
is within the iproute2 package.
next prev parent reply other threads:[~2001-09-06 20:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010906155920.B29583@maggie.dt.e-technik.uni-dortmund.de>
[not found] ` <200109061554.TAA11031@ms2.inr.ac.ru>
2001-09-06 17:48 ` Matthias Andree
2001-09-06 18:06 ` kuznet
2001-09-06 18:18 ` Wietse Venema
2001-09-06 18:38 ` kuznet
2001-09-06 19:45 ` Alan Cox
2001-09-06 19:59 ` Wietse Venema
2001-09-06 20:20 ` jamal [this message]
2001-09-06 20:41 ` Wietse Venema
2001-09-06 20:44 ` jamal
2001-09-06 21:20 ` Matthias Andree
2001-09-07 6:11 ` Patrick Schaaf
2001-09-07 9:24 ` Henning P. Schmiedehausen
2001-09-07 11:13 ` Matthias Andree
2001-09-08 13:25 ` Kai Henningsen
2001-09-06 20:22 ` Alan Cox
2001-09-06 20:38 ` Wietse Venema
2001-09-10 16:11 ` Dennis
2001-09-06 20:13 ` Matthias Andree
2001-09-10 8:05 ` David Weinehall
2001-09-10 12:26 ` Wietse Venema
2001-09-10 12:53 ` David Weinehall
2001-09-10 13:52 ` Wietse Venema
2001-09-10 15:18 ` Matthias Andree
2001-09-10 15:12 ` Matthias Andree
2001-09-10 19:36 ` kuznet
2001-09-10 20:14 ` Matthias Andree
2001-09-11 15:22 ` kuznet
2001-09-11 16:39 ` Matthias Andree
2001-09-10 20:40 ` Andi Kleen
2001-09-10 21:19 ` Matthias Andree
2001-09-11 11:26 ` Matthias Andree
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=Pine.GSO.4.30.0109061612450.14727-100000@shell.cyberus.ca \
--to=hadi@cyberus.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=matthias.andree@gmx.de \
--cc=netdev@oss.sgi.com \
--cc=wietse@porcupine.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
all inboxes | Powered by JetHome®