Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #267796 > unrolled thread

Re: Inclusive terminology (instead of master/slave) for network bonding/LACP

Back to article view | Back to linux.debian.user

Contents

  Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP "Andrew M.A. Cater" <amacater@einval.com> - 2024-02-25 00:00 +0100
    I think we can't disappear ifenslave documentation just yet (Was Re:  Inclusive terminology (instead of master/slave) for network bonding/LACP) Andy Smith <andy@strugglers.net> - 2024-02-25 00:10 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-03-15 22:20 +0100

#267796 — Re: Inclusive terminology (instead of master/slave) for network bonding/LACP

[On list: copied to community@debian.org]

Hi people,

As you might have expected: this subject is drifting off-topic and becoming
a little more personal.

In answer to the first question: there's a reference to a wiki page.
It's a wiki page: it can be edited by (almost) anyone. If anyone wants
to remove the references to ifenslave and substitute others, that's
entirely fine.

As regards personal back and forth argument: can I remind _everyone_ on
the list, without exception, of the need to stay within the Debian
Code of Conduct (and the mailing list Code of Conduct).

Please try to be considerate, helpful and ,above all, constructive. It
makes a difference when it comes to dealing with anything remotely
contentious.

I think the discussion might usefully stop at this point before it
degenerates to more heat than light (as is the way of most discussions
eventually - call it an application of mailing list entropy :) ) 

With thanks for your consideration - and with every good wish, as ever,

Andy Cater
[For the Community Team]

[toc] | [next] | [standalone]

#267797 — I think we can't disappear ifenslave documentation just yet (Was Re: Inclusive terminology (instead of master/slave) for network bonding/LACP)

Hello,

On Sat, Feb 24, 2024 at 10:52:17PM +0000, Andrew M.A. Cater wrote:
> If anyone wants to remove the references to ifenslave and
> substitute others, that's entirely fine.

I really don't think in this specific case it would be a good idea
to remove all mention of ifenslave because:

- The current Ethernet bonding support in ifupdown requires
  ifenslave. If you don't install ifenslave, you can't set up a bond
  interface from /etc/network/interfaces except by avoiding the
  actual syntax there for that purpose and doing it with direct
  commands executed by *-up/down hooks.

- Even if it was possible, vast majority of people using bonded
  Ethernets have it done with ifenslave, so it needs at least a
  mention in order that people can understand what they already have.

- ifenslave is a tiny part of the issue. It's fundamental to the
  bonding driver and same terminology will be seen in its
  configuration and in its status output in /proc/net/bonding, e.g:

    $ cat /proc/net/bonding/bond0 
    Ethernet Channel Bonding Driver: v5.10.0-0.deb10.16-amd64

    Bonding Mode: fault-tolerance (active-backup)
    Primary Slave: None
    Currently Active Slave: eth1
    MII Status: up
    MII Polling Interval (ms): 100
    Up Delay (ms): 0
    Down Delay (ms): 0
    Peer Notification Delay (ms): 0

    Slave Interface: eth0
    MII Status: up
    Speed: 1000 Mbps
    Duplex: full
    Link Failure Count: 1
    Permanent HW addr: 00:25:90:5c:f7:ea
    Slave queue ID: 0

    Slave Interface: eth1
    MII Status: up
    Speed: 1000 Mbps
    Duplex: full
    Link Failure Count: 1
    Permanent HW addr: 00:25:90:5c:f7:eb
    Slave queue ID: 0

As I've already mentioned though, if anyone finds time to
investigate the teaming driver then it would be really nice to see a
wiki article on that and perhaps a link to that from the existing
one on bonded Ethernets.

So in summary, I don't think ifenslave can actually be purged from
history, but some useful steps could possibly be taken towards its
deprecation - first involving actually documenting the new thing.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#268309

Hi,

On Sat, Feb 24, 2024 at 10:52:17PM +0000, Andrew M.A. Cater wrote:
> I think the discussion might usefully stop at this point before it
> degenerates to more heat than light (as is the way of most discussions
> eventually - call it an application of mailing list entropy :) ) 

Three weeks on and some have made essentially the same statements
three times over by now.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web