Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751698AbbAAAXn (ORCPT ); Wed, 31 Dec 2014 19:23:43 -0500 Received: from mail.lang.hm ([64.81.33.126]:46445 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751533AbbAAAXm (ORCPT ); Wed, 31 Dec 2014 19:23:42 -0500 Date: Wed, 31 Dec 2014 16:22:47 -0800 (PST) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Arend van Spriel cc: Linus Torvalds , "Theodore Ts'o" , Jiri Kosina , "Grumbach, Emmanuel" , Borislav Petkov , "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "egrumbach@gmail.com" , "peter@hurleysoftware.com" , "ilw@linux.intel.com" , "Berg, Johannes" , Larry Finger Subject: Re: [PATCH] Revert "cfg80211: make WEXT compatibility unselectable" In-Reply-To: <54A47B7F.9000403@broadcom.com> Message-ID: References: <54A328C2.5080606@lwfinger.net> <54A3D955.6020809@broadcom.com> <0BA3FCBA62E2DC44AF3030971E174FB31B5DD72E@hasmsx107.ger.corp.intel.com> <54A3E1F1.7030807@broadcom.com> <54A41000.3040306@broadcom.com> <20141231173113.GA443@thunk.org> <54A45D4D.7070302@broadcom.com> <20141231214421.GA29273@thunk.org> <54A47B7F.9000403@broadcom.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2294 Lines: 58 On Wed, 31 Dec 2014, Arend van Spriel wrote: > On 12/31/14 22:57, Linus Torvalds wrote: >> On Wed, Dec 31, 2014 at 1:44 PM, Theodore Ts'o wrote: >>> >>> Yeah, the confusing part is that "ip" tends to use "verb object" >>> scheme, which is consistent with the Cisco IOS command set it was >>> trying to emulate. >> >> Side note: does anybody think that was really a good idea to begin >> with? I mean, Cisco iOS is just _soooo_ universally loved, right? > > I think I sense a bit cynical (under)tone here ;-) > >> 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. > > So does "ip" provide the same functionality as "ifconfig" and "route" or does > the package have more to offer. there are things that you can do with "ip" that you can't do with "ifconfig", but they tend to be rather esoteric things (hundreds of IP addresses on "eth0" without using eth0:1, eth0:2, etc as one example) The trouble is that doing simple things is harder with "ip" than "ifconfig" David Lang > The "iw" tool provides much more subcommands to perform different wireless > tasks that are not provided by "iwconfig" and friends. So functionally "iw" > provides a superset. Just have to get equivalent output format to mimic > "iwconfig" as Ted suggested. > > Well, that's something for next year as we are getting close to midnight over > here. > > Regards, > Arend > >> (Ok, "ip route" isn't any more complex than "route", but "ip link" >> sure as hell isn't simpler than "ifconfig" for most things I can think >> of) >> >> Linus > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/