| |
@@ -18,14 +18,15 @@
|
| |
</para>
|
| |
<programlisting>
|
| |
<command>part / --fstype=xfs --onpart=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0-part1</command>
|
| |
- <command>part / --fstype=xfs --onpart=/dev/disk/by-id/ata-ST3160815AS_6RA0C882-part1</command>
|
| |
+ <command>part / --fstype=xfs --onpart=/dev/disk/by-id/ata-ST3160815AS_6RA0C882-part1</command>i
|
| |
+ <command>part / --fstype=xfs --onpart=/dev/disk/by-uuid/ba555f30-1708-4015-9477-64d65a59f3e9-part1</command>
|
| |
</programlisting>
|
| |
<para>
|
| |
This provides a consistent way to refer to disks that is more meaningful than just <literal>sda</literal>. This is especially useful in large storage environments.
|
| |
</para>
|
| |
</important>
|
| |
<para>
|
| |
- While the general principles of Kickstart installations tend to stay the same, the commands and options can change between major releases. You can use the <command>ksverdiff</command> command to display the differences between two versions of the Kickstart syntax. This is useful when updating an existing Kickstart file to be used with a new release. To display a list of changes in syntax between Fedora &PREVVER; and &PRODVER;, use the following command:
|
| |
+ While the general principles of Kickstart installations tend to stay the same, the commands and options can change between major releases. You can use the <command>ksverdiff</command> command to display the differences between two versions of the Kickstart syntax.(Requires python3-ksvalidator) This is useful when updating an existing Kickstart file to be used with a new release. To display a list of changes in syntax between Fedora &PREVVER; and &PRODVER;, use the following command:
|
| |
</para>
|
| |
<screen><prompt>$</prompt> <command>ksverdiff -f F&PREVVER; -t F&PRODVER;</command></screen>
|
| |
<para>
|
| |
@@ -39,73 +40,8 @@
|
| |
In the following sections, if an option is followed by an equals mark (<literal>=</literal>), a value must be specified after it. In the example commands, options in square brackets (<literal>[ ]</literal>) are optional arguments for the command.
|
| |
</para>
|
| |
</note>
|
| |
- <section id="sect-kickstart-commands-installation">
|
| |
- <title>Installation Methods and Sources</title>
|
| |
- <para>
|
| |
- The following commands control the way Fedora will be installed.
|
| |
- </para>
|
| |
-
|
| |
- <section id="sect-kickstart-commands-device">
|
| |
- <title>device (optional) - Install Extra Device Drivers</title>
|
| |
- <para>
|
| |
- On most PCI systems, the installation program will automatically detect Ethernet and SCSI cards. However, on older systems and some PCI systems, Kickstart requires a hint to find the proper devices. The <command>device</command> command, which tells the installation program to install extra modules, uses the following format:
|
| |
- </para>
|
| |
- <programlisting><command>device <replaceable>moduleName</replaceable> [--opts=]</command></programlisting>
|
| |
- <para>
|
| |
- Replace <replaceable>moduleName</replaceable> with the name of the kernel module which should be installed.
|
| |
- </para>
|
| |
- <variablelist>
|
| |
- <varlistentry>
|
| |
- <term><option>--opts=</option></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- Options to pass to the installed kernel module. For example:
|
| |
- </para>
|
| |
- <programlisting><command>device i2c_piix4 --opts="aic152x=0x340 io=11"</command></programlisting>
|
| |
- </listitem>
|
| |
- </varlistentry>
|
| |
- </variablelist>
|
| |
- </section>
|
| |
-
|
| |
- <section id="sect-kickstart-commands-driverdisk">
|
| |
- <title>driverdisk (optional) - Use a Driver Disk</title>
|
| |
- <para>
|
| |
- Driver disks can be used during Kickstart installations to provide additional drivers not included by default. You must copy the driver disks's contents to the root directory of a partition on the system's hard drive. Then, you must use the <command>driverdisk</command> command to specify that the installation program should look for a driver disk and its location.
|
| |
- </para>
|
| |
- <programlisting><command>driverdisk <replaceable>partition</replaceable> | --source= | --biospart=</command></programlisting>
|
| |
- <variablelist>
|
| |
- <varlistentry>
|
| |
- <term><replaceable>partition</replaceable></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- Search for the driver disk image on a local partition. Replace <replaceable>partition</replaceable> with the name of the partition containing the driver disk. Note that the partition must be specified as a full path. For example:
|
| |
- </para>
|
| |
- <programlisting><command>driverdisk /dev/sdb1</command></programlisting>
|
| |
- </listitem>
|
| |
- </varlistentry>
|
| |
- <varlistentry>
|
| |
- <term><option>--source=</option></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- Search for the driver disk in a network location instead of a local partition. For example:
|
| |
- </para>
|
| |
- <programlisting><command>driverdisk --source=ftp://<replaceable>path/to/dd.img</replaceable></command></programlisting>
|
| |
- <programlisting><command>driverdisk --source=http://<replaceable>path/to/dd.img</replaceable></command></programlisting>
|
| |
- <programlisting><command>driverdisk --source=nfs:<replaceable>hostname</replaceable>:/<replaceable>path/to/dd.img</replaceable></command></programlisting>
|
| |
- </listitem>
|
| |
- </varlistentry>
|
| |
- <varlistentry>
|
| |
- <term><option>--biospart=</option></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- BIOS partition containing the driver disk (for example, <literal>82p2</literal>).
|
| |
- </para>
|
| |
- </listitem>
|
| |
- </varlistentry>
|
| |
- </variablelist>
|
| |
- </section>
|
| |
-
|
| |
- <section id="sect-kickstart-commands-install">
|
| |
+
|
| |
+ <section id="sect-kickstart-commands-install">
|
| |
<title>install (required) - Configure Installation Method</title>
|
| |
<para>
|
| |
The default installation mode. You must specify the type of installation from <literal>cdrom</literal>, <literal>harddrive</literal>, <literal>nfs</literal>, <literal>liveimg</literal>, or <literal>url</literal>. The <command>install</command> command and the installation method command must be on separate lines. For example:
|
| |
@@ -464,7 +400,7 @@
|
| |
<section id="sect-kickstart-commands-autopart">
|
| |
<title>autopart (optional) - Automatic Partitioning</title>
|
| |
<para>
|
| |
- Automatically creates partitions: a root (<filename class="partition">/</filename>) partition (1 GB or larger), a <filename class="partition">swap</filename> partition, and an appropriate <filename class="partition">/boot</filename> partition for the architecture. On large enough drives (50 GB and larger), this also creates a <filename class="partition">/home</filename> partition.
|
| |
+ Automatically creates partitions: a root (<filename class="partition">/</filename>) partition (10 GB -15GB), a <filename class="partition">swap</filename> partition,(on systems with less than 8GB RAM) and an appropriate <filename class="partition">/boot</filename> and / or <filename>/boot/efi</filename>partition for the architecture, a <filename class="partition">/home</filename> partition is created filling the remaining free space (unless 'I want to leave free space' option is 'checked' On large drives this <filename>/home</filename> is generally 50 GB or more.
|
| |
</para>
|
| |
<important>
|
| |
<para>
|
| |
@@ -535,6 +471,12 @@
|
| |
<para>
|
| |
Provides a default system-wide passphrase for all encrypted devices.
|
| |
</para>
|
| |
+ <important>
|
| |
+ <para>
|
| |
+ The ommision of <filename>--passphrase</filename> will prompt the user for a passphrase. This will not work if <command>inst.commandline</command> or <command>inst.text</command> are used at grub menu.
|
| |
+ </para>
|
| |
+ </important>
|
| |
+
|
| |
</listitem>
|
| |
</varlistentry>
|
| |
<varlistentry>
|
| |
@@ -551,13 +493,19 @@
|
| |
<para>
|
| |
Adds a randomly-generated passphrase to each encrypted volume. Store these passphrases in separate files in <filename>/root</filename>, encrypted using the X.509 certificate specified with <option>--escrowcert</option>. This option is only meaningful if <option>--escrowcert</option> is specified.
|
| |
</para>
|
| |
+ important>
|
| |
+ <para>
|
| |
+ The ommision of <filename>--backuppassphrase</filename> will prompt the user for a passphrase. This will not work if <command>inst.commandline</command> or <command>inst.text</command> are used at grub menu.
|
| |
+ </para>
|
| |
+ </important>
|
| |
+ rsvalidator <replaceable>/pat
|
| |
</listitem>
|
| |
</varlistentry>
|
| |
<varlistentry>
|
| |
<term><option>--cipher=</option></term>
|
| |
<listitem>
|
| |
<para>
|
| |
- Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.
|
| |
+ Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. Using <systemitem>aes-xts-plain64</systemitem> is strongly recommended.
|
| |
</para>
|
| |
</listitem>
|
| |
</varlistentry>
|
| |
@@ -593,19 +541,6 @@
|
| |
</listitem>
|
| |
</varlistentry>
|
| |
<varlistentry>
|
| |
- <term><option>--boot-drive=</option></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- Specifies which drive the boot loader should be written to, and therefore which drive the computer will boot from. If you use a multipath device as the boot drive, specify only one member of the device.
|
| |
- </para>
|
| |
- <important>
|
| |
- <para>
|
| |
- The <option>--boot-drive=</option> option is currently being ignored in &PRODUCT; installations on IBM System z systems using the <application>zipl</application> boot loader. When <application>zipl</application> is installed, it determines the boot drive on its own.
|
| |
- </para>
|
| |
- </important>
|
| |
- </listitem>
|
| |
- </varlistentry>
|
| |
- <varlistentry>
|
| |
<term><option>--leavebootorder</option></term>
|
| |
<listitem>
|
| |
<para>
|
| |
@@ -695,41 +630,6 @@
|
| |
</para>
|
| |
</listitem>
|
| |
</varlistentry>
|
| |
- <varlistentry>
|
| |
- <term><option>--default=</option></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- Sets the default boot image in the boot loader configuration.
|
| |
- </para>
|
| |
- </listitem>
|
| |
- </varlistentry>
|
| |
- <varlistentry>
|
| |
- <term><option>--extlinux</option></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- Use the <application>extlinux</application> boot loader instead of <application>GRUB2</application>. This option only works on systems supported by <application>extlinux</application>.
|
| |
- </para>
|
| |
- </listitem>
|
| |
- </varlistentry>
|
| |
- <varlistentry>
|
| |
- <term><option>--disabled</option></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- Do not attempt to install a boot loader. This option overrides all other boot loader configuration; all other boot loader options will be ignored and no boot loader packages will be installed.
|
| |
- </para>
|
| |
- </listitem>
|
| |
- </varlistentry>
|
| |
- <varlistentry>
|
| |
- <term><option>--nombr</option></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- Install the boot loader configuration and support files, but do not modify the MBR.
|
| |
- </para>
|
| |
- </listitem>
|
| |
- </varlistentry>
|
| |
- </variablelist>
|
| |
- </section>
|
| |
-
|
| |
<section id="sect-kickstart-commands-btrfs">
|
| |
<title>btrfs (optional) - Create Btrfs Volume or Subvolume</title>
|
| |
<para>
|
| |
@@ -1248,18 +1148,8 @@
|
| |
</varlistentry>
|
| |
<varlistentry>
|
| |
<term><option>--recommended</option></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- Use this option when creating a <systemitem>swap</systemitem> logical volume to determine the size of this volume automatically, based on your system's hardware. For details about the recommended scheme, see <xref linkend="sect-installation-gui-manual-partitioning-recommended" />.
|
| |
- </para>
|
| |
- <important>
|
| |
- <para>
|
| |
- This option can only be used for partitions which result in a file system such as the <filename>/boot</filename> partition and <systemitem>swap</systemitem> space. It can not be used to create partitionsm, LVM physical or logical volumes or RAID members.
|
| |
- </para>
|
| |
- </important>
|
| |
- </listitem>
|
| |
+
|
| |
</varlistentry>
|
| |
- <varlistentry>
|
| |
<term><option>--resize</option></term>
|
| |
<listitem>
|
| |
<para>
|
| |
@@ -1269,9 +1159,8 @@
|
| |
</varlistentry>
|
| |
<varlistentry>
|
| |
<term><option>--encrypted</option></term>
|
| |
- <listitem>
|
| |
<para>
|
| |
- Specifies that this logical volume should be encrypted, using the passphrase provided in the <option>--passphrase=</option> option. If you do not specify a passphrase, the installation program will use the default, system-wide passphrase set with the <command>autopart --passphrase</command> command, or stop the installation and prompt you to provide a passphrase if no default is set.
|
| |
+ This option requires a value for <filename> --passphrase</filename>, whether it is in the kickstart file or asked of the user during install.
|
| |
</para>
|
| |
</listitem>
|
| |
</varlistentry>
|
| |
@@ -1287,12 +1176,12 @@
|
| |
<term><option>--cipher=</option></term>
|
| |
<listitem>
|
| |
<para>
|
| |
- Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.
|
| |
+ Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. Using <systemitem>aes-xts-plain64</systemitem> is strongly recommended.
|
| |
</para>
|
| |
</listitem>
|
| |
</varlistentry>
|
| |
<varlistentry>
|
| |
- <term><option>--escrowcert=<replaceable>URL_of_X.509_certificate</replaceable></option></term>
|
| |
+ ### <term><option>--escrowcert=<replaceable>URL_of_X.509_certificate</replaceable></option></term>
|
| |
<listitem>
|
| |
<para>
|
| |
Store data encryption keys of all encrypted volumes as files in <filename>/root</filename>, encrypted using the X.509 certificate from the URL specified with <replaceable>URL_of_X.509_certificate</replaceable>. The keys are stored as a separate file for each encrypted volume. This option is only meaningful if <option>--encrypted</option> is specified.
|
| |
@@ -2648,7 +2537,7 @@
|
| |
<programlisting>
|
| |
<command>auth [--enablenis | --nisdomain= | --nisserver= | --enableshadow | --enableldap | --enableldapauth | --ldapserver= | --ldapbasedn= | --enableldaptls | --disableldaptls | --enablekrb5 | --krb5realm= | --krb5kdc= | --krb5adminserver= | --enablehesiod | --hesiodlhs= | --hesiodrhs= | --enablesmbauth | --smbservers= | --smbworkgroup= | --enablecache | --passalgo=]</command>
|
| |
</programlisting>
|
| |
- <variablelist>
|
| |
+ <variablelist>
|
| |
<varlistentry>
|
| |
<term><option>--enablenis</option></term>
|
| |
<listitem>
|
| |
@@ -2855,7 +2744,7 @@
|
| |
<section id="sect-kickstart-commands-pwpolicy">
|
| |
<title>pwpolicy (optional) - Change the Default Password Policy</title>
|
| |
<para>
|
| |
- This command can be used to set custom requirements (policy) such as length and strength for passwords set during the installation - the <systemitem>root</systemitem> password, user passwords and LUKS (disk encryption) password.
|
| |
+ This command can be used to set custom requirements (policy) such as length and strength for passwords set during the installation - the <systemitem>root</systemitem> password, user passwords and LUKS (disk encryption) password. For LUKS Passwords these cahnges are ONLY for future changes / inputs, the previously set one (previous install or earlier in Kickstart file) will be unaffected by this option unless <filename>--changesok</filename> is used.
|
| |
</para>
|
| |
<programlisting>
|
| |
<command>pwpolicy <replaceable>name</replaceable> [--minlen=<replaceable>length</replaceable>] [--minquality=<replaceable>quality</replaceable>] [--strict|nostrict] [--emptyok|noempty] [--changesok|nochanges]</command>
|
| |
@@ -3085,7 +2974,7 @@
|
| |
<section id="sect-kickstart-commands-sshkey">
|
| |
<title>sshkey (optional) - Add an Authorized SSH Key</title>
|
| |
<para>
|
| |
- Use this command to add a specified <systemitem>SSH</systemitem> key to an user's <filename>authorized_keys</filename> file. The specified user must either be <systemitem>root</systemitem>, or it must be created in the Kickstart file - either automatically by an installed package, or using <xref linkend="sect-kickstart-commands-user" />.
|
| |
+ Use this command to add a specified <systemitem>SSH</systemitem> key to any user's <filename>authorized_keys</filename> file. The specified user must either be <systemitem>root</systemitem>, or it must be created in the Kickstart file - either automatically by an installed package, or using <xref linkend="sect-kickstart-commands-user" />.
|
| |
</para>
|
| |
<programlisting><command>sshkey --username=<replaceable>user</replaceable> "<replaceable>ssh_key</replaceable>"</command></programlisting>
|
| |
<para>
|
| |
@@ -3101,7 +2990,7 @@
|
| |
</listitem>
|
| |
</varlistentry>
|
| |
</variablelist>
|
| |
- </section>
|
| |
+ </section>t
|
| |
|
| |
<section id="sect-kickstart-commands-user">
|
| |
<title>user (optional) - Create User Account</title>
|
| |
@@ -3224,10 +3113,7 @@
|
| |
<term><option>--autoscreenshot</option></term>
|
| |
<listitem>
|
| |
<para>
|
| |
- Take a screenshot at every step during installation. These screenshots are stored in <filename class="directory">/tmp/anaconda-screenshots</filename> during the installation, and after the installation finishes you can find them in <filename class="directory">/root/anaconda-screenshots</filename>.
|
| |
- </para>
|
| |
- <para>
|
| |
- Each screen is only captured right before the installer switches to the next one. This is important, because if you do not use all required Kickstart options and the installation therefore does not begin automatically, you can go to the screens which were not automatically configured, perform any configuration you want. Then, when you press <guilabel>Done</guilabel> to continue, the screen will be captured including the configuration you just provided.
|
| |
+ Take a screenshot at every step during installation. These screenshots are stored in <filename class="directory">/tmp/anaconda-screenshots</filename> during the installation, and after the installation finishes you can find them in <filename class="directory">/root/anaconda-screenshots</filename>.Each screen is only captured right before the installer switches to the next one.
|
| |
</para>
|
| |
</listitem>
|
| |
</varlistentry>
|
| |
@@ -3237,13 +3123,8 @@
|
| |
<section id="sect-kickstart-commands-cmdline">
|
| |
<title>cmdline (optional) - Perform Installation in Command Line Mode</title>
|
| |
<para>
|
| |
- Perform the installation in a completely non-interactive command line mode. Any prompts for interaction halts the install. This mode is useful on IBM System z systems with the x3270 terminal.
|
| |
+ Perform the installation in a completely non-interactive command line mode. Any prompts for interaction halts the install. This mode is useful on IBM System z systems with the x3270 terminal and large scale deployments with ansible-ized post install host master configuration.
|
| |
</para>
|
| |
- <important>
|
| |
- <para>
|
| |
- For a fully automatic installation, you must either specify one of the available modes (<command>graphical</command>, <command>text</command>, or <command>cmdline</command>) in the Kickstart file, or you must use the <option>console=</option> boot option as described in <xref linkend="sect-boot-options-display" />. Otherwise the system will halt and ask you to choose a mode.
|
| |
- </para>
|
| |
- </important>
|
| |
</section>
|
| |
|
| |
<section id="sect-kickstart-commands-graphical">
|
| |
@@ -3445,9 +3326,6 @@
|
| |
<application>Kdump</application> is a kernel crash dumping mechanism that allows you to save the contents of the system's memory for later analysis. It relies on <application>kexec</application>, which can be used to start a Linux kernel from the context of another kernel without rebooting the system and preserve the contents of the first kernel memory that would otherwise be lost.
|
| |
</para>
|
| |
<para>
|
| |
- In case of a system crash, <application>kexec</application> starts a second kernel (a <firstterm>capture kernel</firstterm>). This capture kernel resides in a reserved part of the system memory that is inaccessible to the main kernel. <application>Kdump</application> then captures the contents of the crashed kernel's memory (a <firstterm>crash dump</firstterm>) and saves it to a specified location. This location can not be configured using Kickstart; it must be specified after the installation by editing the <filename>/etc/kdump.conf</filename> configuration file.
|
| |
- </para>
|
| |
- <para>
|
| |
Available options are:
|
| |
</para>
|
| |
<variablelist>
|
| |
@@ -3485,16 +3363,7 @@
|
| |
</para>
|
| |
</listitem>
|
| |
</varlistentry>
|
| |
- <varlistentry>
|
| |
- <term><option>--enablefadump</option></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- Enable firmware-assisted dumping on systems which allow it (notably IBM Power Systems servers).
|
| |
- </para>
|
| |
- </listitem>
|
| |
- </varlistentry>
|
| |
- </variablelist>
|
| |
- </section>
|
| |
+
|
| |
|
| |
<section id="sect-kickstart-commands-firstboot">
|
| |
<title>firstboot (optional) - Enable or Disable Initial Setup</title>
|
| |
@@ -3535,39 +3404,20 @@
|
| |
<para>
|
| |
Halt the system after the installation has successfully completed. This is similar to a manual installation, where after the installation finishes, the installer displays a message and waits for the user to press a key before rebooting. During a Kickstart installation, if no completion method is specified, this option is used as the default.
|
| |
</para>
|
| |
- <para>
|
| |
- For other completion methods, see the <command>poweroff</command>, <command>reboot</command>, and <command>shutdown</command> commands.
|
| |
- </para>
|
| |
- </section>
|
| |
+ </section>
|
| |
|
| |
<section id="sect-kickstart-commands-poweroff">
|
| |
<title>poweroff (optional) - Power Off After Installation</title>
|
| |
<para>
|
| |
Shut down and power off the system after the installation has successfully completed.
|
| |
</para>
|
| |
- <note>
|
| |
- <para>
|
| |
- The <command>poweroff</command> command is highly dependent on the system hardware in use. Specifically, certain hardware components such as the BIOS, APM (advanced power management), and ACPI (advanced configuration and power interface) must be able to interact with the system kernel. Consult your hardware documentation for more information on you system's APM/ACPI abilities.
|
| |
- </para>
|
| |
- </note>
|
| |
- <para>
|
| |
- For other completion methods, see the <command>halt</command>, <command>reboot</command>, and <command>shutdown</command> Kickstart commands.
|
| |
- </para>
|
| |
- </section>
|
| |
+ </section>
|
| |
|
| |
<section id="sect-kickstart-commands-reboot">
|
| |
<title>reboot (optional) - Reboot After Installation</title>
|
| |
<para>
|
| |
- Reboot after the installation is successfully completed. If you are installing &PRODUCT; on IBM System z in command line mode (using <xref linkend="sect-kickstart-commands-cmdline" />), this command is necessary for a fully automated installation.
|
| |
+ Reboot after the installation is successfully completed.
|
| |
</para>
|
| |
- <para>
|
| |
- For other completion methods, see the <command>halt</command>, <command>poweroff</command>, and <command>shutdown</command> Kickstart options.
|
| |
- </para>
|
| |
- <important>
|
| |
- <para>
|
| |
- Use of the <command>reboot</command> command <emphasis>may</emphasis> result in an endless installation loop, depending on the installation media and method.
|
| |
- </para>
|
| |
- </important>
|
| |
<variablelist>
|
| |
<varlistentry>
|
| |
<term><option>--eject</option></term>
|
| |
@@ -3577,15 +3427,7 @@
|
| |
</para>
|
| |
</listitem>
|
| |
</varlistentry>
|
| |
- <varlistentry>
|
| |
- <term><option>--kexec</option></term>
|
| |
- <listitem>
|
| |
- <para>
|
| |
- Use this option to reboot into the new system using the <systemitem>kexec</systemitem> kernel switching mechanism instead of a full reboot, bypassing the BIOS/Firmware and boot loader.
|
| |
- </para>
|
| |
- </listitem>
|
| |
- </varlistentry>
|
| |
- </variablelist>
|
| |
+
|
| |
</section>
|
| |
|
| |
<section id="sect-kickstart-commands-shutdown">
|
| |
@@ -3593,35 +3435,12 @@
|
| |
<para>
|
| |
Shut down the system after the installation has successfully completed.
|
| |
</para>
|
| |
- <para>
|
| |
- For other completion methods, see the <command>halt</command>, <command>poweroff</command>, and <command>reboot</command> Kickstart options.
|
| |
- </para>
|
| |
- </section>
|
| |
-
|
| |
- </section>
|
| |
-
|
| |
- <section id="sect-kickstart-commands-addon">
|
| |
- <title>%addon (optional) - Include an Anaconda Add-on</title>
|
| |
- <para>
|
| |
- You can expand the basic <application>Anaconda</application> and Kickstart functionality by using custom add-ons specified using the <command>%addon</command> section.
|
| |
- </para>
|
| |
- <para>
|
| |
- To use an add-on in your Kickstart file, add the <command>%addon <replaceable>addon_name</replaceable> <replaceable>options</replaceable></command> command. The section must be closed with an <command>%end</command> statement. For example, to use the <application>Kdump</application> add-on, which is included by default on some installations, use the following block:
|
| |
- </para>
|
| |
- <programlisting><command>%addon com_redhat_kdump --enable --reserve-mb=128</command><command>%end</command>
|
| |
- </programlisting>
|
| |
- <para>
|
| |
- The <command>%addon</command> section does not have any options of its own; all options depend on the add-on being used.
|
| |
- </para>
|
| |
- <para>
|
| |
- For more information about <application>Anaconda</application> add-ons, see the <ulink url="https://vpodzime.fedorapeople.org/anaconda-addon-development-guide/">Fedora Anaconda Addon Development Guide</ulink>.
|
| |
- </para>
|
| |
</section>
|
| |
|
| |
<section id="sect-kickstart-commands-anaconda">
|
| |
<title>%anaconda (optional) - Additional Anaconda Configuration</title>
|
| |
<para>
|
| |
- This section, introduced in &PRODUCT; 22, is used to specify additional configuration options for the installer. Commands inside this section only control the behavior during installation, not on the installed system. The only command currently available inside this section is <xref linkend="sect-kickstart-commands-pwpolicy" />. The <command>%anaconda</command> section must end with <literal>%end</literal>.
|
| |
+ This section, originally introduced in &PRODUCT; 22, is used to specify additional configuration options for the installer. Commands inside this section only control the behavior during installation, not on the installed system. The only command currently available inside this section is <xref linkend="sect-kickstart-commands-pwpolicy" />. The <command>%anaconda</command> section must end with <literal>%end</literal>.
|
| |
</para>
|
| |
<para>
|
| |
In interactive installations (using the graphical or text interface), the <filename>/usr/share/anaconda/interactive-defaults.ks</filename> file contains the default <command>%anaconda</command> section. To change the defaults, you must create a <filename>product.img</filename> file with a Kickstart file replacing the default one, and pass this file to <application>Anaconda</application> using a boot option.
|
| |
@@ -3700,9 +3519,9 @@
|
| |
</para>
|
| |
<programlisting>
|
| |
<command>%packages</command>
|
| |
- @X Window System
|
| |
- @Desktop
|
| |
- @Sound and Video
|
| |
+ @^X Window System
|
| |
+ @^Desktop
|
| |
+ @^Sound and Video
|
| |
<command>%end</command>
|
| |
</programlisting>
|
| |
<para>
|
| |
@@ -3740,7 +3559,7 @@
|
| |
</para>
|
| |
<programlisting>
|
| |
<command>%packages</command>
|
| |
- -@Graphical Internet
|
| |
+ -@^Graphical Internet
|
| |
-autofs
|
| |
-ipa*fonts
|
| |
<command>%end</command>
|
| |
@@ -3750,7 +3569,7 @@
|
| |
</variablelist>
|
| |
<important>
|
| |
<para>
|
| |
- Installing all available packages using only <literal>*</literal> in a Kickstart file is not supported, even if you exclude the <literal>@Conflicts (<replaceable>variant</replaceable>)</literal> group.
|
| |
+ Installing all available packages using only <literal>*</literal> in a Kickstart file is not supported, even if you exclude the <literal>@^Conflicts (<replaceable>variant</replaceable>)</literal> group.
|
| |
</para>
|
| |
</important>
|
| |
<para>
|
| |
immanetize commented 7 years ago
Appending to the end here, after the 'or', makes it read as if USB drives are an example of a network location. How about ~"an ISO image.... on either optical or USB disk?"