netdev
[Top] [All Lists]

Re: [PATCH] ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19

To: David Weinehall <tao@xxxxxxxxxx>
Subject: Re: [PATCH] ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19
From: wietse@xxxxxxxxxxxxx (Wietse Venema)
Date: Mon, 10 Sep 2001 09:52:30 -0400 (EDT)
Cc: Wietse Venema <wietse@xxxxxxxxxxxxx>, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, kuznet@xxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20010910145325.X26627@xxxxxxxxxxxxxxx> "from David Weinehall at Sep 10, 2001 02:53:25 pm"
Sender: owner-netdev@xxxxxxxxxxx
David Weinehall:
> 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.

Other vendors with SIOCGIFNETMASK in 10-year old releases: DEC, HP, IBM.

> "[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?!

The poster was referring to systems that he has personal experience
with.  Not everyone is a dinosaur like I am.

        Wietse

<Prev in Thread] Current Thread [Next in Thread>