> > ... I think the UI suggested here is really bad, as is the process behind > it. Adding a "pick your network device name" step anywhere in anaconda, even > in kickstart, is a bad plan. A better plan would be something like: > > 1) make kickstart accept various different names by using libnetdevname or > something similar > 2) make libnetdevname capable of telling us a reasonable name for an interface > for user display (i.e. smbios name with spaces instead of _ or somesuch) > 3) display and log those names (and /possibly/ the real interface name) where > appropriate, which might include something like a "details" section describing > a particular interface. > Libnetdevname is needed when we have to map pathnames like /dev/netdev/by-chassis-label/Embedded_NIC_1 to ethN names. Since we do not have these pathnames, libnetdevname is useless here.Biosdevname can suggest names to anaconda which can be shown to the users. > > You mean the kernel name here, not the "OS" name. And in general, changing > the kernel names isn't something we want. That's why we went down the whole > aliasing route in the first place! The idea of multiple names for network interface devices, which allows the ethN names to remain unaltered, was not accepted. An installer based fix was suggested. Hence this proposal. With regards, Narendra K _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
