netdev - Re: [PROPOSAL]: Support Alternate Network Device Naming Schemes

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 PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

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

Date:	Mon, 30 Nov 2009 12:07:24 -0500
From:	Jon Masters <jcm@...hat.com>
To:	Discussion of Development and Customization of the Red
	 Hat Linux Installer <anaconda-devel-list@...hat.com>
Cc:	shyam_iyer@...l.com, netdev@...r.kernel.org,
	jordan_hargrave@...l.com, charles_rose@...l.com,
	matt_domsch@...l.com
Subject: Re: [PROPOSAL]: Support Alternate Network Device Naming Schemes

On Fri, 2009-11-27 at 03:42 -0600, Narendra K wrote:
> We have been having discussions in the netdev list about creating multiple names for the network interfaces to bring determinism into the way network interfaces are named in the OSes. In specific, "eth0 in the OS does not always map to the integrated NIC Gb1 as labelled on the chassis".  
> 
> http://marc.info/?l=linux-netdev&m=125510301513312&w=2 - (Re: PATCH: Network Device Naming mechanism and policy)
> http://marc.info/?l=linux-netdev&m=125619338904322&w=2 - ([PATCH] udev: create empty regular files to represent net)
> 
> As a result of those discussions, we propose an installer based solution.

Very cool. Thanks for your continued hard work on this stuff :) Do you
have proof of concept Anaconda patches available?

Jon.


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html