From: kaih@khms.westfalen.de (Kai Henningsen)
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: of ethernet names (was [PATCH] Futex Asynchronous
Date: 10 Jun 2002 22:53:00 +0200 [thread overview]
Message-ID: <8QbwdDPmw-B@khms.westfalen.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0206091130490.13751-100000@home.transmeta.com>
torvalds@transmeta.com (Linus Torvalds) wrote on 09.06.02 in <Pine.LNX.4.44.0206091130490.13751-100000@home.transmeta.com>:
> Is the "magic ioctl" approach ugly? Sure. But it's fairly well contained
> to just one program (ifconfig), and everybody else just uses that. I think
> it's less horrible than the alternatives right now.
If it *were* all contained in ifconfig, you'd be right, but that isn't
even remotely true.
There are a *huge* number of programs that know about network interfaces.
Apart from ifconfig, we have route, routed, iptables, ip, bootloads of
admin scripts for device configuration, for firewalling, pppd anmd
scripts, arp, dhcpd, portsentry, and I haven't even really scratched the
surface here.
Sure, in the old times, when you could get Unix(tm) with or without the
"networking option" for extra money, there wasn't much. But that has
dramatically changed in these Internet times.
MfG Kai
next prev parent reply other threads:[~2002-06-10 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 18:22 of ethernet names (was [PATCH] Futex Asynchronous Dr. David Alan Gilbert
2002-06-09 18:33 ` Linus Torvalds
2002-06-10 20:53 ` Kai Henningsen [this message]
2002-06-10 21:44 ` Jeff Garzik
2002-06-10 22:52 ` Brad Hards
2002-06-10 23:02 ` Jeff Garzik
2002-06-10 23:46 ` David Ford
[not found] <0C01A29FBAE24448A792F5C68F5EA47D29DD32@nasdaq.ms.ensim.com>
2002-06-10 23:20 ` Paul Menage
2002-06-10 23:32 ` Brad Hards
2002-06-10 23:36 ` Randy.Dunlap
2002-06-11 0:11 ` Brad Hards
2002-06-11 2:25 ` Andi Kleen
2002-06-11 2:34 ` Brad Hards
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=8QbwdDPmw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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