Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC: PATCH 3/3] system: enable predictable net interface names
Date: Sat, 17 Sep 2016 14:20:16 +0200	[thread overview]
Message-ID: <20160917142016.685aec6d@free-electrons.com> (raw)
In-Reply-To: <1474113519-24713-4-git-send-email-eric.le.bihan.dev@free.fr>

Hello,

On Sat, 17 Sep 2016 13:58:39 +0200, Eric Le Bihan wrote:
> Since v197, udev and eudev automatically assign predictable, stable
> network interface names for all local Ethernet, WLAN and WWAN
> interfaces.
> 
> This is a departure from the traditional interface naming scheme
> (eth0, eth1, etc).
> 
> Add a configuration option to enable or disable this feature, which is
> disabled by default to be coherent with the behavior set when udev is
> not used.
> 
> See https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
> for details.
> 
> Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr>

While I am happy with the principles of patches 1/3 and 2/3, I'm a lot
less convinced by this one. Indeed, the "System configuration" menu
already has a good number of options, and I'm not a fan of adding yet
another option for just a relatively minor system configuration detail.
I'd prefer to leave this to per-project customization through
post-build scripts, and just use the upstream default (i.e predictable
interface names).

I'll keep this patch in patchwork for some time in order to allow
others to raise their voice. I've also Cc'ed a bunch of people so they
can give their opinion.

> +ifeq ($(BR2_SYSTEM_PREDICTABLE_NETIF_NAMES),y)
> +define SKELETON_MANAGE_PREDITABLE_NETIF_NAMES
> +	rm -f $(TARGET_DIR)/etc/udev/rules.d/80-net-setup-links.rules
> +endef
> +else
> +define SKELETON_MANAGE_PREDITABLE_NETIF_NAMES
> +	touch $(TARGET_DIR)/etc/udev/rules.d/80-net-setup-links.rules

Why are you touching the file here?

> +config BR2_SYSTEM_PREDICTABLE_NETIF_NAMES
> +	bool "Predictable network interface names"
> +	depends on BR2_PACKAGE_HAS_UDEV
> +	default n

"default n" is never needed: the default for an option is to be
disabled.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-09-17 12:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 11:58 [Buildroot] [RFC: PATCH 0/3] DHCP configuration via networkd Eric Le Bihan
2016-09-17 11:58 ` [Buildroot] [RFC: PATCH 1/3] systemd: configure DHCP " Eric Le Bihan
2016-09-17 12:16   ` Thomas Petazzoni
2017-02-06 17:49   ` Thomas Petazzoni
2016-09-17 11:58 ` [Buildroot] [RFC: PATCH 2/3] system: allow auto net configuration with networkd Eric Le Bihan
2016-09-17 12:17   ` Thomas Petazzoni
2017-02-06 17:50   ` Thomas Petazzoni
2016-09-17 11:58 ` [Buildroot] [RFC: PATCH 3/3] system: enable predictable net interface names Eric Le Bihan
2016-09-17 12:20   ` Thomas Petazzoni [this message]
2017-02-06 20:07   ` Peter Korsgaard
2017-03-10 21:57     ` Thomas Petazzoni

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=20160917142016.685aec6d@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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