X-Original-To: alpine-devel@mail.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail.alpinelinux.org (dallas-a1.alpinelinux.org [127.0.0.1]) by mail.alpinelinux.org (Postfix) with ESMTP id EADD8DC01C2 for ; Mon, 20 Jul 2015 15:22:13 +0000 (UTC) Received: from mail-qk0-f173.google.com (mail-qk0-f173.google.com [209.85.220.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id AD14EDC00BA for ; Mon, 20 Jul 2015 15:22:13 +0000 (UTC) Received: by qkdl129 with SMTP id l129so114120437qkd.0 for ; Mon, 20 Jul 2015 08:22:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:mime-version:message-id:in-reply-to:references:from:to:cc :subject:content-type; bh=5Wtn3Y/8YHwJBBoWR58+Ece9oVaeba9cfZEoej6dJyE=; b=a1nwdPI/h0U8AHHrXMgN5z6hy113D+go0Qsr978nKwn7YGNsdyk+gpGCFunaDGF+yO /hcITnGDDzp+CJpvE/BYc/gYoHOiQ5ki6/W58gCYb7Y/skqh9ZYbHnf5Nvmj5jyAHjAw bsHgZ7gsse+DZhNdglGNXOu0oW4+wcUi6CNQhcSPDuCEFHNEgAS36Nd7f1OTRXalDpug CtzJ/DdMol8PK2/DHa1tMX+/vG0KxEhTC2E8cJUKyRpSxVXS2B3ulmyvPkreWaLRphhC f6Egqffvuk2d8m9ffggot7YRTpAJFlGXx8Esx2koLy6bJx9UWALjEcFVmM8DKzaqLSRd iZEQ== X-Received: by 10.55.31.40 with SMTP id f40mr47352960qkf.18.1437405733006; Mon, 20 Jul 2015 08:22:13 -0700 (PDT) Received: from hedwig-14.prd.orcali.com (ec2-54-85-253-60.compute-1.amazonaws.com. [54.85.253.60]) by smtp.gmail.com with ESMTPSA id 202sm11016809qhy.1.2015.07.20.08.22.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Jul 2015 08:22:11 -0700 (PDT) Date: Mon, 20 Jul 2015 08:22:11 -0700 (PDT) X-Google-Original-Date: Mon, 20 Jul 2015 15:22:11 GMT X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 X-Mailer: Nodemailer (0.5.0; +http://www.nodemailer.com/) Message-Id: <1437405731070.2791f84d@Nodemailer> In-Reply-To: <20150720150820.GA1567@localhost> References: <20150720150820.GA1567@localhost> X-Orchestra-Oid: E7E34038-0136-4D9E-8F70-7E59AB550369 X-Orchestra-Sig: 554fa7025947ddf126d238960b45de08a547aa67 X-Orchestra-Thrid: TAFCBD824-F97C-4A91-AA8C-4A9B9BD1E2B2_1507200860546466616 X-Orchestra-Thrid-Sig: 1516983b04f36156b08c7773c10c78460984f9e8 X-Orchestra-Account: 6a43214cd9311cc291bc81471f35eeec5ca26a4e From: chris.spillane@gmail.com To: "Isaac Dunham" Cc: "Natanael Copa" , "Alpine-devel" , "Carlo Landmeter" Subject: Re: Interface names (WAS: [alpine-devel] eudev pushed to git master (edge)) Content-Type: multipart/alternative; boundary="----Nodemailer-0.5.0-?=_1-1437405731953" X-Virus-Scanned: ClamAV using ClamSMTP ------Nodemailer-0.5.0-?=_1-1437405731953 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I'd also like to see us stick with ethX / wlanX naming convention if = possible =E2=80=94 Sent from Mailbox On Mon, Jul 20, 2015 at 4:08 PM, Isaac Dunham wrote: > On Mon, Jul 20, 2015 at 09:52:12AM +0200, Natanael Copa wrote: >> On Sat, 18 Jul 2015 11:35:50 +0200 >> Carlo Landmeter wrote: >>=20 >> > I also have the feeling I have to cleanup older (automatic) udev rules= , >> > because my nic name has changed into something weird. >> > I didnt look into it too much, but i think people should really watch = out >> > with updating edge if they don't want to break anything. >>=20 >> For the record. As mentioned on IRC, The NIC name change is to get >> persistent and predictable net interface names. >>=20 >> https://github.com/gentoo/eudev/blob/master/src/udev/udev-builtin-net=5F= id.c#L20 > At the latter qualification (predictable) it fails, if you're talking = about > mortals. >> To get back the old style names you can do: >>=20 >> ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules > I'd used =22touch=22, but ln -s /dev/null is probably better since it > also discards future modifications. >> This also means that which NIC becomes eth0 and eth1 etc is >> unpredictable. >>=20 >> We will need a long term solution for this. >>=20 >> The problem is that kernel will assign net interface name based on what >> order they are discovered during coldplug. The way we have worked >> around this in Alpine is that we sort the modaliases before doing >> modprobe. That way eth0 will become eth0 every reboot, even after >> kernel upgrades. > Using =22sort -u=22 is also desireable because it means that repeats of = the > same hardware only provoke one module load (if you have multiple > USB buses or ethernet cards from the same manufacturer). >> Udev developers has other solution for this problem: invent a new >> naming standard for network interfaces. >>=20 >> I think we want keep whatever is current for people who are upgrading. >> But for new installs, what do we do=3F How do we name the network >> interfaces=3F >>=20 >> Do we want udev users and non-udev users have same interfaces names, or >> do we want let users who don't want udev keep the old, traditional >> inerface naming and let users who chose udev to get whatever upstream >> udev does=3F >>=20 >> How do we make sure that interface names does not change after = reboot=3F >>=20 >> Do we want be (partially) compatible with other distro's way to name >> interfaces=3F (even a bad naming standard might be better than no = naming >> standard) > I, for one, *do* *NOT* *want* udev-style names. > The kernel developers worked for years on moving from driver-specific > names to =22ethN=22/=22wlanN=22 interface names. =22Predictable=22 = interface naming > a la udev not only reverses those gains, it makes things worse since > anyone who isn't using udev code can't predict interface names even > if they know the driver. > Udev's approach means that if I pull out a network card and replace it, > I have to reconfigure /etc/network/interfaces or whatever else I use. > For what it's worth, Debian Jessie (and Devuan Jessie) use > /lib/udev/write=5Fnet=5Frules to make the kernel name that they detect = first > persistent. > Thanks, > Isaac Dunham > --- > Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org > Help: alpine-devel+help@lists.alpinelinux.org > --- ------Nodemailer-0.5.0-?=_1-1437405731953 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I'd also like to see us stick with ethX / wlanX naming convention if = possible

=E2=80=94
Sent from Mailbox


On Mon, Jul 20, 2015 at 4:08 PM= , Isaac Dunham <ibid.ag@gmail.com> = wrote:

On Mon, Jul 20, = 2015 at 09:52:12AM +0200, Natanael Copa wrote:
> On Sat, 18 Jul 2015 11:35:50 +0200
> Carlo Landmeter <clandmeter@gmail.com> wrote:
>=20
> > I also have the feeling I have to cleanup older (automatic) = udev rules,
> > because my nic name has changed into something weird.
> > I didnt look into it too much, but i think people should = really watch out
> > with updating edge if they don't want to break anything.
>=20
> For the record. As mentioned on IRC, The NIC name change is to = get
> persistent and predictable net interface names.
>=20
> https://github.com/gentoo/eudev/blob/master/src/udev/udev-builtin-= net=5Fid.c#L20

At the latter qualification (predictable) it fails, if you're = talking about
mortals.

> To get back the old style names you can do:
>=20
> ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules

I'd used =22touch=22, but ln -s /dev/null is probably better since = it
also discards future modifications.

> This also means that which NIC becomes eth0 and eth1 etc is
> unpredictable.
>=20
> We will need a long term solution for this.
>=20
> The problem is that kernel will assign net interface name based on= what
> order they are discovered during coldplug. The way we have worked
> around this in Alpine is that we sort the modaliases before doing
> modprobe. That way eth0 will become eth0 every reboot, even after
> kernel upgrades.

Using =22sort -u=22 is also desireable because it means that = repeats of the
same hardware only provoke one module load (if you have multiple
USB buses or ethernet cards from the same manufacturer).

> Udev developers has other solution for this problem: invent a = new
> naming standard for network interfaces.
>=20
> I think we want keep whatever is current for people who are = upgrading.
> But for new installs, what do we do=3F How do we name the network
> interfaces=3F
>=20
> Do we want udev users and non-udev users have same interfaces = names, or
> do we want let users who don't want udev keep the old, = traditional
> inerface naming and let users who chose udev to get whatever = upstream
> udev does=3F
>=20
> How do we make sure that interface names does not change after = reboot=3F
>=20
> Do we want be (partially) compatible with other distro's way to = name
> interfaces=3F (even a bad naming standard might be better than no = naming
> standard)

I, for one, *do* *NOT* *want* udev-style names.

The kernel developers worked for years on moving from = driver-specific
names to =22ethN=22/=22wlanN=22 interface names. =22Predictable=22 = interface naming
a la udev not only reverses those gains, it makes things worse since
anyone who isn't using udev code can't predict interface names even
if they know the driver.
Udev's approach means that if I pull out a network card and replace it,=
I have to reconfigure /etc/network/interfaces or whatever else I use.

For what it's worth, Debian Jessie (and Devuan Jessie) use
/lib/udev/write=5Fnet=5Frules to make the kernel name that they detect = first
persistent.

Thanks,
Isaac Dunham


---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---


------Nodemailer-0.5.0-?=_1-1437405731953-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---