From: kaih@khms.westfalen.de (Kai Henningsen)
To: thunder@ngforever.de
Cc: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: Re: [PATCH] Futex Asynchronous Interface
Date: 10 Jun 2002 22:46:00 +0200 [thread overview]
Message-ID: <8QbwcRg1w-B@khms.westfalen.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0206100808180.6159-100000@hawkeye.luckynet.adm>
thunder@ngforever.de (Thunder from the hill) wrote on 10.06.02 in <Pine.LNX.4.44.0206100808180.6159-100000@hawkeye.luckynet.adm>:
> On Mon, 10 Jun 2002, Helge Hafting wrote:
> > ls /dev/net
> > eth0 eth1 eth2 ippp0
>
> What is it worth? You have a few more files which you can't do anything
> with, and ifconfig output is much more greppable etc.
Ifconfig output is *WHAT*?!
Ifconfig output, to be parsed by a script, is one of the shittiest
interfaces possible.
Look at this, and then tell me again that "ifconfig output is much more
greppable"!
# ifconfig eth0
eth0 Protokoll:Ethernet Hardware Adresse 00:50:FC:0C:63:69
inet Adresse:10.0.41.2 Bcast:10.255.255.255 Maske:255.255.255.0
EtherTalk Phase 2 Adresse:65280/237
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26841078 errors:4240 dropped:0 overruns:0 frame:0
TX packets:26134055 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:8481
RX bytes:60708618 (57.8 MiB) TX bytes:2654812652 (2.4 GiB)
# LANG= ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:50:FC:0C:63:69
inet addr:10.0.41.2 Bcast:10.255.255.255 Mask:255.255.255.0
EtherTalk Phase 2 addr:65280/237
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26841182 errors:4240 dropped:0 overruns:0 frame:0
TX packets:26134181 errors:0 dropped:0 overruns:0 carrier:0
collisions:8481
RX bytes:60727233 (57.9 MiB) TX bytes:2654827939 (2.4 GiB)
#
Even rooting around in /proc is better than this!
> I remember these network devices from Solaris. There wasn't any good about
> them IIRC, the only sane way of working with them was to work around them,
> i.e. ignoring. Do you want a /dev/ignoreme directory?
I have no idea what Solaris did, nor do I necessarily want to know, but I
*do* have experience with what Linux does, and I'm certainly not
impressed.
Given that I've fairly often been irritated about not having these things
be filesystem nodes, I'd expect there to *be* benefit in having them in
the filesystem if this is done halfway reasonable.
MfG Kai
next prev parent reply other threads:[~2002-06-10 21:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 7:26 [PATCH] Futex Asynchronous Interface Rusty Russell
2002-06-02 0:10 ` Pavel Machek
2002-06-10 6:57 ` Rusty Russell
2002-06-06 16:36 ` Linus Torvalds
2002-06-06 19:27 ` Alan Cox
2002-06-06 23:21 ` Rusty Russell
2002-06-07 8:33 ` Peter Wächtler
2002-06-08 22:28 ` Linus Torvalds
2002-06-09 9:49 ` Kai Henningsen
2002-06-09 18:09 ` Linus Torvalds
2002-06-09 19:06 ` Thunder from the hill
2002-06-10 6:39 ` Kai Henningsen
2002-06-10 7:55 ` Helge Hafting
2002-06-10 14:10 ` Thunder from the hill
2002-06-10 20:46 ` Kai Henningsen [this message]
2002-06-11 14:14 ` john slee
2002-06-10 15:11 ` Linus Torvalds
2002-06-11 15:06 ` Eric W. Biederman
2002-06-10 20:57 ` H. Peter Anvin
2002-06-09 10:07 ` Peter Wächtler
2002-06-09 17:49 ` Linus Torvalds
2002-06-07 9:06 ` Rusty Russell
2002-06-08 22:42 ` Linus Torvalds
2002-06-11 9:15 ` Rusty Russell
2002-06-11 16:53 ` Linus Torvalds
2002-06-12 5:32 ` Rusty Russell
2002-06-12 9:16 ` Peter Wächtler
2002-06-12 14:19 ` Hubertus Franke
2002-06-12 16:50 ` Peter Wächtler
2002-06-12 18:15 ` Vladimir Zidar
2002-06-12 15:39 ` Linus Torvalds
2002-06-12 16:29 ` Peter Wächtler
2002-06-12 16:52 ` Linus Torvalds
2002-06-12 17:07 ` Peter Wächtler
2002-06-12 18:32 ` Saurabh Desai
2002-06-12 20:05 ` Oliver Xymoron
2002-06-12 20:16 ` Linus Torvalds
2002-06-13 2:57 ` Rusty Russell
2002-06-13 9:37 ` Peter Wächtler
2002-06-13 9:55 ` Rusty Russell
2002-06-13 16:38 ` Gabriel Paubert
2002-06-13 16:40 ` Linus Torvalds
2002-06-13 1:32 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 16:08 Martin Wirth
2002-06-06 22:59 ` Rusty Russell
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=8QbwcRg1w-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@ngforever.de \
/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