All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Stefano Brivio <sbrivio@redhat.com>, David Ahern <dsahern@gmail.com>
Cc: Phil Sutter <phil@nwl.cc>, Eric Garver <egarver@redhat.com>,
	Tomas Dolezal <todoleza@redhat.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Lennert Buytenhek <buytenh@gnu.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] Introduce ip-brctl shell script
Date: Wed, 23 Jan 2019 17:09:42 +0200	[thread overview]
Message-ID: <800cb3d3-c749-3f36-83ea-0375e67fbd33@cumulusnetworks.com> (raw)
In-Reply-To: <ed6b04eab48a70d6416a6b021f04f9901f7e9f01.1547830302.git.sbrivio@redhat.com>

On 18/01/2019 19:00, Stefano Brivio wrote:
> This script wraps 'ip' and 'bridge' tools to provide a drop-in replacement
> of the standalone 'brctl' utility.
> 
> It's bug-to-bug compatible with brctl as of bridge-utils version 1.6,
> has no dependencies other than a POSIX shell, and it's less than half
> the binary size of brctl on x86_64.
> 
> As many users (including myself) seem to find brctl usage vastly more
> intuitive than ip-link, possibly due to habit, this might be a lightweight
> approach to provide brctl syntax without the need to maintain bridge-utils
> any longer.
> 
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> Acked-by: Phil Sutter <phil@nwl.cc>
> ---
>  man/man8/Makefile   |   5 +-
>  man/man8/ip-brctl.8 | 187 +++++++++++++++
>  misc/Makefile       |   9 +-
>  misc/ip-brctl.in    | 572 ++++++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 770 insertions(+), 3 deletions(-)
>  create mode 100644 man/man8/ip-brctl.8
>  create mode 100755 misc/ip-brctl.in

Hi,
IMO the effort should be towards improving iproute2 to be
easier to use and more intuitive. We should be pushing people to use the new tools
instead of trying to find workarounds to keep the old tools alive.
I do like to idea of deprecating bridge-utils, but I think it should be done
via improving ip/bridge enough to be pleasant to use. We will have to
maintain this compatibility layer forever if it gets accepted and we'll never
get rid of brctl this way.

Thanks,
 Nik



  reply	other threads:[~2019-01-23 15:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 17:00 [PATCH iproute2-next] Introduce ip-brctl shell script Stefano Brivio
2019-01-23 15:09 ` Nikolay Aleksandrov [this message]
2019-01-23 16:33   ` Roopa Prabhu
2019-01-25 10:05     ` Stefano Brivio
2019-01-28  5:08       ` Roopa Prabhu
2019-01-28  7:57         ` Stefano Brivio
2019-01-30 22:30           ` Roopa Prabhu
2019-01-31 12:46             ` Stefano Brivio
2019-01-31 16:28               ` Roopa Prabhu
2019-02-05 22:50                 ` Stephen Hemminger
2019-02-06 10:55                   ` Stefano Brivio
2019-01-25 10:04   ` Stefano Brivio
2019-01-30  4:51 ` David Ahern
2019-01-30 10:55   ` Stefano Brivio
2019-01-31  5:12     ` David Ahern
2019-01-31 12:46       ` Stefano Brivio
2019-01-31 12:49 ` Stefano Brivio

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=800cb3d3-c749-3f36-83ea-0375e67fbd33@cumulusnetworks.com \
    --to=nikolay@cumulusnetworks.com \
    --cc=buytenh@gnu.org \
    --cc=dsahern@gmail.com \
    --cc=egarver@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=phil@nwl.cc \
    --cc=sbrivio@redhat.com \
    --cc=stephen@networkplumber.org \
    --cc=todoleza@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.