On Mon, Jul 13, 2020 at 03:41:18PM -0700, Stephen Hemminger wrote: > On Tue, 14 Jul 2020 00:00:16 +0200 > Michal Kubecek <mkube...@suse.cz> wrote: > > > On Mon, Jul 13, 2020 at 02:51:39PM -0400, Jarod Wilson wrote: > > > To start out with, I'd like to attempt to eliminate as much of the use > > > of master and slave in the bonding driver as possible. For the most > > > part, I think this can be done without breaking UAPI, but may require > > > changes to anything accessing bond info via proc or sysfs. > > > > Could we, please, avoid breaking existing userspace tools and scripts? > > Massive code churn is one thing and we could certainly bite the bullet > > and live with it (even if I'm still not convinced it would be as great > > idea as some present it) but trading theoretical offense for real and > > palpable harm to existing users is something completely different. > > > > Or is "don't break userspace" no longer the "first commandment" of linux > > kernel development? > > > > Michal Kubecek > > Please consider using same wording as current standard for link aggregration. > Current version is 802.1AX and it uses the terms: > Multiplexer / Aggregator
But both of these are replacements for "master", right? > As far as userspace, maybe keep the old API's but provide deprecation nags. > And don't document the old API values. I'm not a fan of nagging users. And even less of a fan of undocumented keyword and value aliases. Michal
