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
| ||
|
Message-ID: <20091106220637.GB15533@mock.linuxdev.us.dell.com> Date: Fri, 6 Nov 2009 16:06:37 -0600 From: Matt Domsch <Matt_Domsch@...l.com> To: Narendra_K@...l.com, bryan@...zban.is-a-geek.net, dannf@...com, bhutchings@...arflare.com, netdev@...r.kernel.org, linux-hotplug@...r.kernel.org, Jordan_Hargrave@...l.com, Charles_Rose@...l.com, Sandeep_K_Shandilya@...l.com Subject: Re: PATCH: Network Device Naming mechanism and policy On Fri, Nov 06, 2009 at 09:49:21AM +0100, Marco d'Itri wrote: > On Nov 04, Narendra_K@...l.com wrote: > > > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > > ATTR{smbios_name}=="Embedded_NIC_1", ATTR{type}=="1", KERNEL=="eth*", > > NAME="eth0". > As a distribution developer I highly value solutions like this which do > not require patching every application which deals with interface names > and then teaching users about aliases which only work in some places and > are unknown to the kernel. Fair enough - but would you object if we changed the naming scheme from eth%d to something else? -- Matt Domsch Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux -- 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
Powered by blists - more mailing lists