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
| ||
|
Date: Sat, 10 Oct 2009 20:35:42 +0200 From: Kay Sievers <kay.sievers@...y.org> To: Bill Fink <billfink@...dspring.com> Cc: Greg KH <greg@...ah.com>, Matt Domsch <Matt_Domsch@...l.com>, Stephen Hemminger <shemminger@...tta.com>, netdev@...r.kernel.org, linux-hotplug@...r.kernel.org, Narendra_K@...l.com, jordan_hargrave@...l.com Subject: Re: PATCH: Network Device Naming mechanism and policy On Sat, Oct 10, 2009 at 20:11, Bill Fink <billfink@...dspring.com> wrote: > No comment on the specific implementation decision, but I am in the > process of setting up a large number of test systems with identical > hardware configurations, and using a master disk image to clone all the > test systems. The biggest pain in this process is identiying the MAC > addresses for each of the six or more network interfaces in each test > system (we want eth0...ethN to always reference the same physical port > on the test systems), and then having to modify the 70-persistent-net.rules > udev file and the HWADDR entry for all the ifcfg-ethX files to reflect > the correct MAC addresses. It would be fantastic if there were some > mechanism for making this part of the process unnecessary. Udev creates the persistent rules only if no other rule set a name. Adding something like: SUBSYSTEM=="net", KERNEL==""eth*", NAME="eth%n" in any earlier rules file before the udev generated one will skip all off the automatic udev rule creation. Kay -- 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