Anaconda Kickstart Documentation¶
|Authors:||Brian C. Lane <email@example.com>|
Anaconda uses kickstart to automate
installation and as a data store for the user interface. It also extends the kickstart
commands documented here
by adding a new kickstart section named
%anaconda where commands to control the behavior
of Anaconda will be defined.
program: pwpolicy <name> [--minlen=LENGTH] [--minquality=QUALITY] [--strict|notstrict] [--emptyok|notempty] [--changesok|nochanges]
Set the policy to use for the named password entry.
- Name of the password entry, currently supported values are: root, user and luks
- Minimum password length. This is passed on to libpwquality.
- Minimum libpwquality to consider good. When using
--strictit will not allow passwords with a quality lower than this.
- Strict password enforcement. Passwords not meeting the
--minqualitylevel will not be allowed.
- Passwords not meeting the
--minqualitylevel will be allowed after Done is clicked twice.
- Allow empty password.
- Don’t allow an empty password
- Allow UI to be used to change the password/user when it has already been set in the kickstart.
- Do not allow UI to be used to change the password/user if it has been set in the kickstart.
The defaults for interactive installations are set in the
file provided by Anaconda. If a product, such as Fedora Workstation, wishes to override them
product.img needs to be created with a new version of the file included.
When using a kickstart the defaults can be overridded by placing an
%anaconda section into
the kickstart, like this:
%anaconda pwpolicy root --minlen=10 --minquality=60 --strict --notempty --nochanges %end
The commit message for pwpolicy included some incorrect examples.
Require the specified install class to be used for the installation. Otherwise, the best available install class will be used.
--name=Name of the required install class.
Removed since Fedora 30.
You can use the boot options