From: David Weinehall <tao@acc.umu.se>
To: Wietse Venema <wietse@porcupine.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
kuznet@ms2.inr.ac.ru, 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: Mon, 10 Sep 2001 14:53:25 +0200 [thread overview]
Message-ID: <20010910145325.X26627@khan.acc.umu.se> (raw)
In-Reply-To: <20010910100537.W26627@khan.acc.umu.se> <20010910122603.80CA4BC06C@spike.porcupine.org>
In-Reply-To: <20010910122603.80CA4BC06C@spike.porcupine.org>; from wietse@porcupine.org on Mon, Sep 10, 2001 at 08:26:03AM -0400
On Mon, Sep 10, 2001 at 08:26:03AM -0400, Wietse Venema wrote:
> David Weinehall:
> > Are you saying that Linux should implement compability with _new_
> > features in FreeBSD 4.x, while at the same time frowning at the fact
> > that Linux introduces a new API?! The mind boggles at the thought.
>
> SIOCGIFNETMASK is not "new". It exists in systems as ancient as
> SunOS 4.x, which pre dates FreeBSD 4.x by about 10 years.
>
> Evidence: RTFM the Postfix source code :-)
>
> In other words, SIOCGIFNETMASK existed long before Linux could plug
> into a network.
"[snip] old and the new stuff, please name precisely the objections
against portability and compatibility with FreeBSD 4.x aliasing."
^^^^^^^^^^^^^^^^^^^^
This is what lead me to my conclusion. Care to clarify? If you simply
meant SIOCGIFNETMASK, why not write that instead instead of involving
FreeBSD 4.x?!
/David Weinehall
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
next prev parent reply other threads:[~2001-09-10 12:54 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
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 [this message]
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=20010910145325.X26627@khan.acc.umu.se \
--to=tao@acc.umu.se \
--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=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®