On Tue, Jan 29, 2013 at 06:20:20PM +0100, Miloslav Trmač wrote: > > It's not only "em1" mistakenly hard-coded in applications; it's user's > saved configuration, scripts etc., where often there is no practical > alternative to "hard-coding".
I created a bug report about this issue: https://bugzilla.redhat.com/show_bug.cgi?id=700933 I suppose I could have written a script that goes through the list of interfaces, filters out hardcoded names like "lo", "wlan", "tun", and "tap", and then assumes that whatever is left is the ethernet device. And then I could have fixed such a script each time it breaks when types of devices are added and renamed (surely the current discussion is only the next phase in a long sequence of renames). In the end, though, I just disabled biosdevname. Having a static "eth0" name is much less brittle, even on many multi-interface machines. I'm a little uncomfortable with the apparently prevalent idea that having complicated names for ethernet devices is better for all users in all situations. I'm sure that in some situations it's nice and helpful, but in others, it's harmful. -- Andrew McNabb http://www.mcnabbs.org/andrew/ PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
