Jasper Capel wrote: > Joseph Boyer Jr. wrote: > >> Ok. I see your issue. >> >> > The thing is, it wasn't really an issue until I added the possibility of > giving your network interface any name you like. > > Previously we had intf0, intf1, ..., intfN, and you could just configure > your networking information in the order of your physical devices. The > booting interface is sorted by the IPAPPEND option in syslinux and there > you go. > Now we can have an interface foo, bar, mgmt, internet, mylan0, mylan0, > but these are now processed alphabetically (right?). So this would only > work correctly if my system's first interface is actually connected to > network "bar", hence the need to match a mac-address to a physical > interface in the %pre-section of the kickstart and use that information > to configure networking in anaconda. Of course we'd only want to do this > if the interfaces aren't called ethX in Cobbler. > > Jasper > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler >
Additionally in a future commit/upgrade, any interfaces named "intfN" will be automatically renamed "ethN" to comply. This will not affect existing configurations, but it might affect someone's XMLRPC code in minor ways if they were hardcoding things. Anything not starting with "intf<integer>" will be legal, so you can name interfaces "mgmt". --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
