From: Theodore Ts'o <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arend van Spriel <arend@broadcom.com>,
Jiri Kosina <jkosina@suse.cz>,
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
Borislav Petkov <bp@alien8.de>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"egrumbach@gmail.com" <egrumbach@gmail.com>,
"peter@hurleysoftware.com" <peter@hurleysoftware.com>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] Revert "cfg80211: make WEXT compatibility unselectable"
Date: Wed, 31 Dec 2014 17:19:48 -0500 [thread overview]
Message-ID: <20141231221948.GB29273@thunk.org> (raw)
In-Reply-To: <CA+55aFzp2bWctqpiHyZVC9ZCtW3wN_bPsGjcbqKFgu9KOZtAJw@mail.gmail.com>
On Wed, Dec 31, 2014 at 01:57:59PM -0800, Linus Torvalds wrote:
> Side note: does anybody think that was really a good idea to begin
> with? I mean, Cisco iOS is just _soooo_ universally loved, right?
Well, at the time when it was "ip" came out, Cisco had a defacto
monopoly on routing equipment, and some of the folks who were working
on Linux networking had this insane dream of having Linux be better at
the routing game than Cisco (there was this minor issue of Cisco
having hardware assist for their fastpath :-). So I think I
*understand* the rationale behind the design choice, even though it's
probably not the decision I would have made at the time, and certainly
not with the benefit of 20/20 hindsight!
And I won't say that I *loved* IOS, but I certainly used it enough
when I was working in the MIT Network Operations group. :-)
> And yeah, I refuse to use "ip link" or other insane commands. Let's
> face it, "ifconfig" and "route" are perfectly fine commands, and a
> whole lot less confusing than "ip" with random crap after it. I'm
> really not seeing why that "ip" command was seen as an improvement.
The real problem is that they were trying to do way more complicated
things in terms of routing rules (including some stuff that could be
done by Cisco IOS). So if you want to try to do the insanely
complicated stuff, you have to use the "ip route" command.
Meh. Could it have been shoehorned into the legacy "route" command?
Perhaps, although it would have been a bit of mess, I suspect.
The question I find more interesting is how many people are actually
*using* all of the complexity that currently can only be accessed via
the "ip", "tc", and "ss" commands.
But in any case, given that "ip", "tc", "ss", etc. are using the IOS
syntax, most users will probably find it confusing and surprising that
"iw" is using something different. It's probably too hard to maintain
script compatibility to make such a UX change to iw at this point,
though. And besides, most users are probably using "ifconfig",
"route", and if they're not using network-manager or wicdw, they're
using "iwconfig" or "iwlist" --- so it's a moot point. :-)
- Ted
next prev parent reply other threads:[~2014-12-31 22:20 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 13:33 iwlwifi-driver card doesn't work with 3.19-rc2+ Jiri Kosina
2014-12-30 14:23 ` Emmanuel Grumbach
2014-12-30 14:34 ` Peter Hurley
2014-12-30 14:38 ` Grumbach, Emmanuel
2014-12-30 15:21 ` Jiri Kosina
2014-12-30 20:28 ` Grumbach, Emmanuel
2014-12-30 20:41 ` Jiri Kosina
2014-12-30 21:23 ` Borislav Petkov
2014-12-30 22:35 ` Larry Finger
2014-12-30 22:42 ` Jiri Kosina
2014-12-30 22:52 ` [PATCH] Revert "cfg80211: make WEXT compatibility unselectable" Jiri Kosina
2014-12-31 7:44 ` Grumbach, Emmanuel
2014-12-31 11:09 ` Arend van Spriel
2014-12-31 11:10 ` Grumbach, Emmanuel
2014-12-31 11:45 ` Arend van Spriel
2014-12-31 14:07 ` Jiri Kosina
2014-12-31 15:02 ` Arend van Spriel
2014-12-31 17:31 ` Theodore Ts'o
2014-12-31 17:44 ` Linus Torvalds
2014-12-31 20:32 ` Arend van Spriel
2014-12-31 21:44 ` Theodore Ts'o
2014-12-31 21:57 ` Linus Torvalds
2014-12-31 22:19 ` Theodore Ts'o [this message]
2014-12-31 22:41 ` Arend van Spriel
2015-01-01 0:22 ` David Lang
2015-01-01 11:32 ` Richard Weinberger
2015-01-01 19:44 ` Lennart Sorensen
2015-01-01 20:14 ` Linus Torvalds
2015-01-02 4:04 ` Lennart Sorensen
2015-01-05 7:26 ` Michal Kubecek
2014-12-31 22:30 ` Arend van Spriel
2014-12-31 15:14 ` Andreas Hartmann
2014-12-31 19:48 ` Arend van Spriel
2015-01-01 10:56 ` Andreas Hartmann
2015-01-01 12:25 ` Arend van Spriel
2014-12-31 13:10 ` Jiri Kosina
2014-12-31 13:26 ` Grumbach, Emmanuel
2014-12-31 13:49 ` Peter Hurley
2014-12-31 14:40 ` Julian Calaby
2014-12-31 14:46 ` Borislav Petkov
2014-12-31 14:56 ` Julian Calaby
2014-12-31 15:03 ` Jiri Kosina
2014-12-31 15:11 ` Borislav Petkov
2015-01-02 5:11 ` Pavel Machek
2014-12-31 16:43 ` Paul Bolle
2014-12-31 7:50 ` iwlwifi-driver card doesn't work with 3.19-rc2+ Grumbach, Emmanuel
2014-12-31 8:05 ` Sujith Manoharan
2014-12-31 13:54 ` Borislav Petkov
2014-12-30 15:03 ` Jiri Kosina
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=20141231221948.GB29273@thunk.org \
--to=tytso@mit.edu \
--cc=Larry.Finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=bp@alien8.de \
--cc=egrumbach@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--cc=jkosina@suse.cz \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).