From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: hps@intermeta.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19
Date: Fri, 7 Sep 2001 13:13:57 +0200 [thread overview]
Message-ID: <20010907131357.D13826@emma1.emma.line.org> (raw)
In-Reply-To: <20010906204104.A3FBDBC06C@spike.porcupine.org> <Pine.GSO.4.30.0109061643030.14727-100000@shell.cyberus.ca> <20010906232033.L13547@emma1.emma.line.org> <9na3o5$c9$1@forge.intermeta.de>
In-Reply-To: <9na3o5$c9$1@forge.intermeta.de>
Henning P. Schmiedehausen schrieb am Freitag, den 07. September 2001:
> So you actually say "make it the way BSD does, because that's what we
> know and support". Sheesh. Why don't you just use Netlink and start
> preaching to the BSD and Solaris folks that "this is the way how it
> should be done". I'd say there are more Linux machines than BSD and
> Solaris combined out there.
I assume you know the meaning of the words "bloat" and "proliferation".
A portable application needs the BSD interface anyhow, and adding
another interface just for Linux makes it a testing/maintenance and thus
a reliability nightmare.
I wouldn't call the netlink example that's been posted here "trivial"
with its 215 lines. You don't seriously expect a portable program to
add 200 lines of C to pull 5 bits of entropy out of the Linux kernel
where ANY other kernel does it with 4 lines of C, and Linux could do it
as well.
If people only commented (not flamed) constructively on my patch rather
than adding fuel to this unnecessary fire.
The Big Silence[TM].
next prev parent reply other threads:[~2001-09-07 11:14 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 [this message]
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=20010907131357.D13826@emma1.emma.line.org \
--to=matthias.andree@stud.uni-dortmund.de \
--cc=hps@intermeta.de \
--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
all inboxes | Powered by JetHome®