On Fri, Dec 18, 2009 at 07:42:22AM -0600, Jan Engelhardt wrote: > What is wrong with just renaming the actual interface? In fact you > could use udev itself for just that. a) The disk image then becomes 'stateful' with respect to MAC addresses for NICs. It breaks the scenario of hardware maintenance whereby you remove the disks from one server, plug them into an identical server, and power it back on. Or replacing a NIC. Or booting the same image on multiple systems. b) I'd really like to be able to use the platform-defined name (e.g. Embedded_NIC_1) early in the installers, long before udev would have set up 70-persistent-net.rules, for doing network-based installs. The syslinux IPAPPEND 2 option is quite helpful I'll admit, but that only sets up a deterministic mapping for one of the N NICs in a system (N>=4 commonplace on all our servers). c) it requires the user to make a choice as to what they want that one-and-only name to be, either at install time (which the anaconda team rejected), or later (meaning it's not really the one-and-only name). > Mapping MACs to interface names is a sort of determinism -- it > remains the same over time. Only so long as you don't replace any hardware components. With the method we're proposing, the image remains stateless with respect to MAC addresses. Thanks, Matt -- 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 netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
