linux-kernel - Re: renaming kernel devices [was: VIA EPIA EK: strange eth dev numbering]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 2 Aug 2007 21:45:54 -0700 (PDT)
From:	david@...g.hm
To:	Ondrej Zajicek <santiago@...reenet.org>
cc:	Jan Engelhardt <jengelh@...putergmbh.de>,
	Michael Tokarev <mjt@....msk.ru>,
	Herbert Rosmanith <kernel@...dsau.enemy.org>,
	linux-kernel@...r.kernel.org
Subject: Re: renaming kernel devices [was: VIA EPIA EK: strange eth dev
 numbering]

On Thu, 2 Aug 2007, Ondrej Zajicek wrote:

> 
> On Thu, Aug 02, 2007 at 01:47:23PM +0200, Jan Engelhardt wrote:
>> It does not rename ethX to the "next free" one, but to a _persistent_ one.
>> If it were a "next free" thing, then removing a card would shuffle all
>> your eth around again (and invalidate your iptables rules at the same
>> time, to note).
>
> It is questionable what is _persistent_ . MAC-based names are persistent
> with regard to adding and removing of other cards, 'Plain' names are persistent
> with regard to replacing that card with different item (of a same kind).
>
> I am very happy that (using 'plain' names) i can send technician to
> replace broken NIC in our routers without need for configuration
> change.

this is a very important point, and with the distros (and many kernel 
people) treating udev as a requirement this is going to bite a lot of 
people.

David Lang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/