On Wed, 2014-08-06 at 07:41 -0400, Tom Horsley wrote: > I've got F21 branched installed on an alternate partition on > my system, and I noticed this nonsense. On F21 I get this: > > enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 10.134.30.143 netmask 255.255.255.0 broadcast 10.134.30.255 > inet6 fe80::20b:eff:fe0f:ed prefixlen 64 scopeid 0x20<link> > ether 00:0b:0e:0f:00:ed txqueuelen 1000 (Ethernet) > RX packets 112 bytes 13242 (12.9 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 84 bytes 10207 (9.9 KiB) > TX errors 0 dropped 0 overruns 0 carrier 1 collisions 0 That's systemd: https://fedoraproject.org/wiki/Features/SystemdPredictableNetworkInterfaceNames > On F20 the same hardware (note the MAC address) gives this: > > p6p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 10.134.30.143 netmask 255.255.255.0 broadcast 10.134.30.255 > inet6 fe80::20b:eff:fe0f:ed prefixlen 64 scopeid 0x20<link> > ether 00:0b:0e:0f:00:ed txqueuelen 1000 (Ethernet) > RX packets 1233320 bytes 144491797 (137.7 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 2058583 bytes 2951769070 (2.7 GiB) > TX errors 0 dropped 0 overruns 0 carrier 1 collisions 0 That's biosdevname: https://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming In Fedora 21 we've more or less dropped biosdevname in favour of systemd. systemd's system is a cleaner implementation and the weight of opinion favours the systemd approach to naming. See the discussion from https://bugzilla.redhat.com/show_bug.cgi?id=965718#c76 onwards. >From F21 onwards new Fedora installations should reliably result in the use of the systemd naming scheme. Existing installs that use biosdevname will continue to use it (with the same naming scheme, obviously) unless the admin intervenes. We should probably put this in the release notes. -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
