Product SiteDocumentation Site

2. Changes in Fedora for System Administrators

2.1. Installation

2.1.1. Fedora Media Writer as Primary Downloadable

Fedora Media Writer is a multiplatform tool which allows anyone to easily and quickly download installation ISO images and use them to create a bootable USB drive. This saves you the effort of manually downloading an ISO image, verifying its checksum, and using dd or similar to write the image to an USB drive. Starting with the final release of Fedora 25, this tool will be offered as the primary download solution on https://getfedora.org/ instead of ISO images (ISO images will continue to be provided on the download website as well). Before the final release, you can visit https://stg.getfedora.org/en/workstation/prerelease/ to get the application. The Media Writer is available on Linux (RPM), Mac and Windows, and provides the same experience on all systems. Sources are available on GitHub: https://github.com/MartinBriza/MediaWriter.
Fedora Media Writer
Screenshot of the redesigned Fedora Media Writer
Figure 1. Fedora Media Writer

Warning

Using this tool will destroy any data on the flash drive as well as overwrite its partition layout. Make sure you back up any important data off the drive first. After you finish installing Fedora from the drive, you can use the Media Writer again to restore a single-partition FAT32 layout on the device, which will allow it to be used on all systems as a normal flash drive again.

2.1.2. Installer Changes

This section lists important changes made in this release to the Anaconda installer and related components such as pykickstart, blivet, or initial-setup.
2.1.2.1. General Installer Changes
Static routes configured during installation are now automatically configured on the installed system
Previously, static route configuration files were not copied from the installation environment to the installed system. Consequently, static route configuration during installation was lost after the installation finished. These files are now copied, and static routes configured during installation are automatically configured on the installed system.
Screen Access Manager is now available in Anaconda
A Screen Access Manager (SAM) has been added to Anaconda. The SAM controls which screens will be shown and records spokes visited into a configuration file. This enables tools running before Anaconda to hide specific screens if needed, and post-installation tools can in turn read the list of visited screens and avoid asking the user to configure the same settings twice.
The Anaconda repository now has contribution guidelines
The Anaconda repository on GitHub now contains a CONTRIBUTING file, which provides guidance for anyone wishing to contribute to the repository. Anyone thinking of making a contribution to the installer is strongly encouraged to familiarize themselves with the file at https://github.com/rhinstaller/anaconda/blob/master/CONTRIBUTING before submitting a pull request.
2.1.2.2. Changes to Anaconda Interfaces (GUI and TUI)
Host name is no longer being set automatically when not specified
Previously, if you did not provide any host name in the Network & Hostname screen (or in Kickstart), Anaconda set the target system's host name to one that was obtained during installation. In Fedora 25, the Network & Hostname no longer automatically pre-fills the host name; instead it always defaults to localhost.localdomain, which effectively that the installed system will obtain a host name from NetworkManager during configuration/activation of network devices after the installation finishes. At the same time, the Network & Hostname now displays the current host name for the installation environment next to the host name configuration field, and a new Apply button has been added which can change the host name during the installation.
NTP configuration is now supported in the text-based interface
The text-based interface now allows you to configure NTP servers similar to the Date & Time screen in the graphical interface.
2.1.2.3. Kickstart Changes
The timezone command can now be used without specifying a time zone
Starting with Fedora 25, you can use the timezone Kickstart command without actually specifying a time zone, which was mandatory in previous releases. Every possible option for this command is therefore optional; however, if the command is present in the Kickstart file, at least one of the options must be used.
New option: network --no-activate
The network command has a new option: --no-activate. Use this option to prevent the configured device from activating automatically.
Commands targeting disk devices can now specify targets in multiple variants
Storage-related commands which target disk devices, such as clearpart, part, or ignoredisk, can now have their targets specified in multiple variants using the pipe ("|") delimiter. For example:
part / --device=sd*|hd*|vda,/dev/vdc
The above example will match either of sd*, hd*, or vda and /dev/vdc. The specified variants are processed from left to right, and at least one of them must match an existing device in order for the command to succeed.
The bootloader command now behaves differently when the --boot-drive option is not specified
If you use the bootloader command without specifying a drive using the --boot-drive= option, the bootloader will now be installed on a drive determined by the following rules in this particular order:
  1. If the --driveorder= option was used, the boot loader will be installed on the first valid device specified
  2. The first present and valid disk containing a /boot partition will be used
  3. If none of the above apply, then the first valid disk from the list of all detected disks will be used
2.1.2.4. Changes in Boot Options
New option: inst.nosave=
You can use the inst.nosave= option to control which installation results will be saved to the installed system. Installation results are files generated after the installation, such as the anaconda-ks.cfg autogenerated Kickstart file. This option is useful when using Anaconda to create a disk image, as it allows you to prevent potentially sensitive information such as installation logs and internal URLs from being saved in the disk image.
Valid values for this option are input_ks (do not save the original Kickstart file), output_ks (do not save anaconda-ks.cfg), all_ks (save neither Kickstart file), logs (do not save log files), and all (do not save any of the previous).
New option: inst.singlelang
This option allows you to run the installation in single language mode - in other words, it disables language selection for the installer as well as for the installed system. If a language is specified at the same time as this using the inst.lang=, the specified language will be used during installation and configured on the target system. If no language was specified, Anaconda and the installed system will default to en-US.UTF-8.
2.1.2.5. Miscellaneous Changes in the Installation Process
Initial Setup now logs unhandled exceptions to journal
The Initial Setup utility now logs unhandled exceptions to journal in order to simplify debugging in the event of a fatal crash.
Driver updates can now replace already loaded modules
Drivers loaded from a Driver Update Disk (DUD) using the inst.dd= boot option can now replace already loaded drivers in addition to providing new ones, as long as the original driver/module is not in use.
Logs describing the system's original state are now saved before Anaconda starts
In order to preserve logs describing the system's original state, Anaconda now saves several logs (outputs of the lsblk, dmesg, and lvmdump commands) immediately upon starting, before it makes any changes to the system. This can provide additional debugging information as these logs describe the initial state of the system.

2.2. Directory Server

2.2.1. 389 Directory Server version 1.3.5

389 Directory Server is an LDAPv3-compliant server and a set of related administrative tools, used around the world for Identity Management, Authentication, Authorization, and much more. It is also the foundation of the FreeIPA project’s server. Fedora 25 provides version 1.3.5 of the 389 Directory Server.
For a list of most important changes in the new release, see the announcement at Fedora Magazine: https://fedoramagazine.org/whats-new-389-directory-server-1-3-5/. Also see the project's own release notes for a full list of bug fixes and enhancements: http://www.port389.org/docs/389ds/releases/release-1-3-5-13.html.