Rescue
boot entry in the GRUB menu to allow use after hardware changes. To recreate initramfs after hardware or driver changes, use the rescue boot option and run the command dracut --regenerate-all
.
Initramfs Changes
dracut
utility is used to create the initramfs on Fedora. To regenerate an initramfs for all installed kernels, use the following command:
#
dracut --regenerate-all
pykickstart
.
inst.nodnf
option to revert back to Yum if needed. See Section 3.4.1, “Yum replaced by DNF” for more information about DNF.
inst.dnf
boot option, which was added in Fedora 21, has been replaced by the inst.nodnf
option, which behaves in an opposite way. Use inst.nodnf
to force the installer to use the older Yum package manager to install packages instead of DNF, which is now default.
--nobase
option for the %packages
section has been removed.
sshkey
. Use this command to install a SSH key to the authorized_keys
file for a specified user using the following syntax:
sshkey --username=user "ssh_key"
root
, or it must exist (must be created by the user
command in the Kickstart file, or by a package specified in the %packages
section).
%anaconda
. This section can now be used in a Kickstart file to control the behavior of the installer, but not the installed system. Currently, the only command supported in this section is pwpolicy
, described below. This section must end with an %end
statement.
pwpolicy
. This command sets password requirements such as minimum length for a named password entry.
pwpolicy name [--minlen=LENGTH] [--minquality=QUALITY] [--strict|notstrict] [--emptyok|notempty] [--changesok|nochanges]
root
, user
, or luks
, to set a policy for the root password, user passwords, or LUKS (disk encryption) password.
--minlen=
- The minimum allowed password length. This parameter will be passed to the libpwquality
library. The default minimum length is 8
.
--minquality=
- Minimum allowed quality of the password, as calculated by libpwquality
. If the --strict
option is used, passwords with lower quality will not be allowed. If --notstrict
is used, using a password of lower than specified quality will display a warning require the user to click Done twice in the graphical user interface to confirm. The default quality value is 50
.
--strict
- Passwords with lower quality than specified in --minquality
will be rejected completely. This is the default.
--notstrict
- Passwords with lower quality than specified in --minquality
will be accepted, but Anaconda will display a warning and require the user to click Done twice before accepting the password.
--emptyok
- Allow empty passwords. This is the default.
--notempty
- Do not allow empty passwords.
--changesok
- Allow changing a password pre-configured in the Kickstart file to be changed interactively in the graphical user interface.
--nochanges
- Passwords set in the Kickstart file can not be changed in the GUI. This is the default.
/usr/share/anaconda/interactive-defaults.ks
file provided by Anaconda on installation media. To override the default Kickstart file (and therefore change the installer's password policy), a product.img
file with a separate %anaconda
section must be created and passed to Anaconda.
updates
repository, allowing this application to be installed using the DNF package manager.
mod_wsgi
application which provides federated single sign-on to web application. User authentication is always performed against a separate Identity Management system, such as an IPA server, and communication with applications is performed using a federation protocol such as SAML or OpenID.
/usr/bin/yum
command will redirect to /usr/bin/dnf
and print a warning about the redirection. The legacy yum package manager can be manually installed; the legacy command line utility has been renamed to yum-deprecated
.
dnf update
action, that package will not be updated, but others will. This is similar to yum's --skip-broken
directive, but evaluates the impact of the problem against the entire transaction. Because this is the default behavior, there is no --skip-broken
switch for dnf.
--best
option. dnf update --best
will force dnf to resolve the transaction using the latest versions of involved packages, and report any problems instead of skipping them. This is equivalent to yum's behavior without --skip-broken
.
dnf update
and dnf upgrade
are equivalent. This differs from yum, where yum upgrade
would have the same effect as yum update --obsoletes
, and take obsolete packages into account.
upgrade_requirements_on_install
. To upgrade with dnf, use dnf update
.
clean_requirements_on_remove
option in /etc/dnf/dnf.conf
/usr/lib/systemd/system/dnf-makecache.timer
.
/etc/systemd/system/dnf-makecache.timer
and edit it.
metadata_timer_sync
in /etc/dnf/dnf.conf
to a number of seconds configures the minimum number of seconds between makecache operations. If the timer has not expired, dnf makecache
will exit immediately.
man yum.conf
.
repository-packages
directive can be used to search for or get info about packages in a specific repository, list installed packages from that repository, and more. This simplifies operations that would have required use of --excluderepo
and --includerepo
options with yum, and is especially useful for managing similar packages from different repositories.
dnf provides foo
command. This replaces yum resolvedep foo
.
dnf repoquery --requires foo
. This replaces yum deplist foo
.
--allowerasing
option. For example, dnf --allowerasing mariadb
will allow you to replace mysql with mariadb, without disrupting packages that require capabilities provided by both packages. This replaces yum shell
and yum swap
functionality.
dnf-langpacks
plug-in, which is expected to work identically to the older yum-langpacks
plug-in. See Section 4.3.3, “DNF Langpacks Plug-in” for details.
enabled_metadata=1
in its definition, a dialog window will be displayed informing the user that the package has been found, but an additional repository must be enabled before it can be installed.
enabled_metadata=1
statement.
PASS
, FAIL
, NEEDS_ACTION
, etc.). Contents can be done by users on the base of the Packaging Guidelines here: http://fedoraproject.org/wiki/Packaging:PreupgradeAssistant. Package owners are responsible for adding a module if it is suitable, for example changes in the MariaDB database between system versions.
dnf install preupgrade-assistant-*
command. You can find information on how to run the Preupgrade Assistant here: https://github.com/phracek/preupgrade-assistant/blob/master/README.
updates
repository in Fedora 22. You can now install this application using DNF instead of relying on the stand-alone upstream installer.