> I guess what I find confusing is when anaconda uses one naming convention in its UI, but upon reboot the installed system uses a different naming convention. > And neither convention helps me know which of two ethernets are > being used. When i installed F19, anaconda wrote the config files as enp* or similar. Issuing an 'ifconfig' on the installed system revealed that the pXXpX scheme was active. Long story short: I modified config files to match whatever ifconfig reported and then setup the network.service and its network bridges. Whatever device names anaconda saw and configured, these needed to be changed after booting. (i this system network.service is used inestead of NetworkManager.service). So, yes, it is somewhat confusing. :-) On Thu, Oct 3, 2013 at 3:41 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > On Oct 3, 2013, at 8:45 AM, Bill Nottingham <notting@xxxxxxxxxx> wrote: > >> "Jóhann B. Guðmundsson" (johannbg@xxxxxxxxx) said: >>>> Apologies, I haven't had time to do investigation. The note in CommonBugs is >>>> certainly correct as far as anaconda using biosdevname by default still - if >>>> there are other consequences where different names are written to the >>>> interface configuration by anaconda than what are assigned with >>>> udev/systemd, that would exacerbate things further. >>>> >>> >>> Should not biosdevice names be dropped from the release now that >>> udev [1] has replaced it's behaviour ? >> >> (repeating what has been said in these discussions multiple times before) >> >> Users want to be able to use biosdevname via configuration. Given how >> anaconda and NM interact, that makes it more complicated than just dropping >> it. Hence the patches from upthread. > > I guess what I find confusing is when anaconda uses one naming convention in its UI, but upon reboot the installed system uses a different naming convention. And neither convention helps me know which of two ethernets are being used. > > > Chris Murphy > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
