Immanetize (talk | contribs) (systemd/udevd net device names) |
Immanetize (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
{{Docs_beat_open}} | {{Docs_beat_open}} | ||
== BIND10 == | |||
The latest versions of the popular nameserver `bind` and dhcp server `dhcpd` server are now available for Fedora. The BIND10 suite features include a RESTful configuration API and sqlite database backend for `named` and SQL backend for `dhcpd`. | |||
For more information, consult the `bind10` manual at http://bind10.isc.org/docs/bind10-guide.html . | |||
== stable network interface naming == | == stable network interface naming == | ||
The udevd service has a long history of providing predictable names for block devices and others. Fedora will now also use udev naming for network interfaces by default, providing more reliable interface names on systems with multiple network devices. Alternative naming schemes, such as custom udev rules or biosdevname, will override this default. Users upgrading from previous releases may need to update the device names referenced in `/etc/system/network-scripts`, although in most cases `biosdevname` will continue to manage naming. | The udevd service has a long history of providing predictable names for block devices and others. Fedora will now also use udev naming for network interfaces by default, providing more reliable interface names on systems with multiple network devices. Alternative naming schemes, such as custom udev rules or biosdevname, will override this default. Users upgrading from previous releases may need to update the device names referenced in `/etc/system/network-scripts`, although in most cases `biosdevname` will continue to manage naming. | ||
Revision as of 18:43, 15 April 2013
This beat is now ready to have Fedora 25 content added by the beat writer
BIND10
The latest versions of the popular nameserver bind and dhcp server dhcpd server are now available for Fedora. The BIND10 suite features include a RESTful configuration API and sqlite database backend for named and SQL backend for dhcpd.
For more information, consult the bind10 manual at http://bind10.isc.org/docs/bind10-guide.html .
stable network interface naming
The udevd service has a long history of providing predictable names for block devices and others. Fedora will now also use udev naming for network interfaces by default, providing more reliable interface names on systems with multiple network devices. Alternative naming schemes, such as custom udev rules or biosdevname, will override this default. Users upgrading from previous releases may need to update the device names referenced in /etc/system/network-scripts, although in most cases biosdevname will continue to manage naming.
For more information, read http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames .