From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A5CDC13838B for ; Fri, 26 Sep 2014 09:05:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2FF56E0B29; Fri, 26 Sep 2014 09:04:59 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E6D81E09B9 for ; Fri, 26 Sep 2014 09:04:57 +0000 (UTC) Received: from [192.168.1.100] (mobile-internet-bceeb2-119.dhcp.inet.fi [188.238.178.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: ssuominen) by smtp.gentoo.org (Postfix) with ESMTPSA id 836443401A5 for ; Fri, 26 Sep 2014 09:04:56 +0000 (UTC) Message-ID: <54252C2F.1030901@gentoo.org> Date: Fri, 26 Sep 2014 12:04:47 +0300 From: Samuli Suominen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: udev (viable) alternatives ? References: <54245C36.50507@gentoo.org> <20140926002320.GB21773@waltdnes.org> <5424DD13.3060208@gmail.com> <20140926090759.7cf050e8@digimed.co.uk> <54252834.4030305@gentoo.org> In-Reply-To: <54252834.4030305@gentoo.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 833fbb87-2cdb-4f43-be4a-8cf0c813cc13 X-Archives-Hash: cef7142b98a3bdce5051a26b646b7277 On 26/09/14 11:47, Samuli Suominen wrote: > On 26/09/14 11:22, Canek Peláez Valdés wrote: >> On Fri, Sep 26, 2014 at 3:07 AM, Neil Bothwick wrote: >>> On Fri, 26 Sep 2014 05:27:15 +0200, Alan McKinnon wrote: >>> >>>>> I buy machines with one ethernet interface. What I find >>>>> particularly annoying is this doublespeak about calling it >>>>> "predictable". Before the change, it was predicatbly "eth0". Now, >>>>> it's different on every different model. >>>> It's not doublespeak, the interfaces are named exactly according to >>>> where they are on the PCI bus. If you had two interfaces, they show up >>>> to the kernel in random order by time and sometimes eth0/eth1 are nto >>>> the same they were before the reboot. >>> That may be true for PCI devices but not for USB ones. If you unplug a >>> USB device and plug it back into the same port, it will get a different >>> device number. The naming is more predictable, but it's not there yet. >> That doesn't sound right. If unplugging a USB net device and plugging >> it again *in the same port* results in a different device *name*, then >> it is a bug and should be reported; the description of the algorithm >> in [1] sounds like it should get always the same name for the same >> port, unless I'm misunderstanding something. >> >> Regards. >> >> [1] http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-net_id.c#n51 > I've seen this happening once on a cheap laptop with a stripped down > BIOS I can't > even recall brand for, it had a kludge in the BIOS settings for > hotplugging, turning > it off, allowed the port to remain same, turning it on, some machine > specific code > gets executed and the kernel interprets the same port as different port > > Bad hardware, bad hardware settings, maybe missing exception for that > particular > hardware type in the code that determines the name... I'm not sure, I > don't have > the machine anymore > > - Samuli > Later kernels *can mark interfaces predictable in a new form of metadata*, and udev >= 209 can pick that information up, and then it won't do anykind of userspace renaming on it, since kernel has declared the interface name to be steady...predictable...always same, so I hope we are moving towards kernel assigning predictable names for all drivers and we can get rid of the userspace renaming of interfaces all together at some point I really believe this is a task for the kernel to provide predictable names, and all this userspace renaming is just a bandage we can hopefully soon rip off - Samuli