[install-guide/F21-rewrite] Adding Kickstart commands up to ignoredisk
pbokoc
pbokoc at fedoraproject.org
Tue Sep 16 23:48:55 UTC 2014
commit 3ea96ca60ddd7f0f93b3ded9a30377d0566f008f
Author: Petr Bokoc <pbokoc at redhat.com>
Date: Wed Sep 17 01:48:12 2014 +0200
Adding Kickstart commands up to ignoredisk
en-US/Kickstart_Syntax_Reference.xml | 1007 ++++++++++++++++++++++++++++++++--
1 files changed, 952 insertions(+), 55 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index 64f0a11..29993ce 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -50,17 +50,77 @@
</para>
<section id="sect-kickstart-commands-device">
- <title>device - Install Extra Device Drivers</title>
+ <title>device (optional) - Install Extra Device Drivers</title>
<para>
- text
+ 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 - Use a Driver Disk</title>
- <para>
- text
+ <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">
@@ -100,45 +160,540 @@
</para>
<section id="sect-kickstart-commands-autopart">
- <title>autopart - Automatic Partitioning</title>
+ <title>autopart (optional) - Automatic Partitioning</title>
<para>
- text
+ 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.
</para>
+ <programlisting>
+<command>autopart --type=<replaceable>type</replaceable> [--nolvm | --encrypted | --passphrase= | --escrowcert= | --backuppassphrase | --cipher=]</command>
+ </programlisting>
+ <important>
+ <para>
+ The <command>autopart</command> option cannot be used together with the <command>part/partition</command>, <command>raid</command>, <command>logvol</command>, or <command>volgroup</command> options in the same Kickstart file.
+ </para>
+ </important>
+ <variablelist>
+ <varlistentry>
+ <term><option>--type=</option></term>
+ <listitem>
+ <para>
+ Selects one of the predefined automatic partitioning schemes you want to use. Accepts the following values:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>lvm</literal>: The LVM partitioning scheme.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>btrfs</literal>: The Btrfs partitioning scheme.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>plain</literal>: Regular partitions with no LVM or Btrfs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>thinp</literal>: The LVM Thin Provisioning partitioning scheme.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ For a description of the available partition schemes, see <remark>TODO: xref to a list of available auto partitioning schemes</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--nolvm</option></term>
+ <listitem>
+ <para>
+ Do not use LVM or Btrfs for automatic partitioning. This option is equal to <option>--type=plain</option>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--encrypted</option></term>
+ <listitem>
+ <para>
+ Encrypts all partitions. This is equivalent to checking the <guilabel>Encrypt partitions</guilabel> check box on the initial partitioning screen during a manual graphical installation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--passphrase=</option></term>
+ <listitem>
+ <para>
+ Provides a default system-wide passphrase for all encrypted devices.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--escrowcert=<replaceable>URL_of_X.509_certificate</replaceable></option></term>
+ <listitem>
+ <para>
+ Stores 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.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--backuppassphrase</option></term>
+ <listitem>
+ <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>
+ </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/">Fedora Documentation</ulink>. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-bootloader">
- <title>bootloader - Configure Boot Loader</title>
+ <title>bootloader (required) - Configure Boot Loader</title>
<para>
- text
+ Specifies how the boot loader should be installed.
</para>
+ <programlisting>
+<command>bootloader [--append= | --boot-drive= | --leavebootorder | --driveorder= | --location= | --password= | --iscrypted | --timeout= | --default= | --extlinux]</command>
+ </programlisting>
+ <important>
+ <para>
+ You should always use a password to protect your boot loader. An unprotected boot loader can allow a potential attacker to modify the system's boot options and gain unauthorized access to the system.
+ </para>
+ </important>
+ <important>
+ <para>
+ Some systems require a special partition for installing the boot loader. The type and size of this partition depends on whether the disk you are installing the boot loader to uses the <firstterm>Master Boot Record</firstterm> (MBR) or a <firstterm>GUID Partition Table</firstterm> (GPT) schema. For more information, see <remark>TODO: link to a section that deals with boot loaders and EFI/BIOSBoot</remark>
+ </para>
+ </important>
+ <variablelist>
+ <varlistentry>
+ <term><option>--append=</option></term>
+ <listitem>
+ <para>
+ Specifies additional kernel parameters. To specify multiple parameters, separate them with spaces. For example:
+ </para>
+ <programlisting>
+<command>bootloader --location=mbr --append="hdd=ide-scsi ide=nodma"</command>
+ </programlisting>
+ <para>
+ The <option>rhgb</option> and <option>quiet</option> parameters are always used, even if you do not specify them here or do not use the <option>--append=</option> command at all.
+ </para>
+ </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.
+ </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>--leavebootloader</option></term>
+ <listitem>
+ <para>
+ Prevents the installation program from making changes to the existing list of bootable images on UEFI or ISeries/PSeries systems.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--driveorder=</option></term>
+ <listitem>
+ <para>
+ Specifies which drive is first in the BIOS boot order. For example:
+ </para>
+ <programlisting>
+<command>bootloader --driveorder=sda,hda</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--location=</option></term>
+ <listitem>
+ <para>
+ Specifies where the boot record is written. Valid values are the following:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>mbr</literal> - The default option. Depends on whether the drive uses the Master Boot Record (MBR) or GUID Partition Table (GPT) scheme:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ On a GPT-formatted disk, this option will install stage 1.5 of the boot loader into the BIOS boot partition.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ On an MBR-formatted disk, stage 1.5 will be installed into the empty space between the MBR and the first partition.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>partition</literal> - Install the boot loader on the first sector of the partition containing the kernel.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>none</literal> - Do not install the boot loader.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ In most cases, this option does not need to be specified.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--password=</option></term>
+ <listitem>
+ <para>
+ If using <application>GRUB2</application> as the boot loader, sets the boot loader password to the one specified with this option. This should be used to restrict access to the <application>GRUB2</application> shell, where arbitrary kernel options can be passed.
+ </para>
+ <para>
+ If a password is specified, <application>GRUB2</application> will also ask for a user name. The user name is always <literal>root</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--iscrypted</option></term>
+ <listitem>
+ <para>
+ Normally, when you specify a boot loader password using the <option>--password=</option> option, it will be stored in the Kickstart file in plain text. If you want to encrypt the password, use this option and an encrypted password.
+ </para>
+ <para>
+ To generate an encrypted password, use the <command>grub2-mkpasswd-pbkdf2</command> command, enter the password you want to use, and copy the command's output (the hash starting with <literal>grub.pbkdf2</literal>) into the Kickstart file. An example <command>bootloader</command> Kickstart entry with an encrypted password will look similar to the following:
+ </para>
+ <programlisting>
+<command>bootloader --iscrypted --password=grub.pbkdf2.sha512.10000.5520C6C9832F3AC3D149AC0B24BE69E2D4FB0DBEEDBD29CA1D30A044DE2645C4C7A291E585D4DC43F8A4D82479F8B95CA4BA4381F8550510B75E8E0BB2938990.C688B6F0EF935701FF9BD1A8EC7FE5BD2333799C98F28420C5CC8F1A2A233DE22C83705BB614EA17F3FDFDF4AC2161CEA3384E56EB38A2E39102F5334C47405E</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--timeout=</option></term>
+ <listitem>
+ <para>
+ Specifies the amount of time the boot loader will wait before booting the default option (in seconds).
+ </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>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-btrfs">
- <title>btrfs - Create Btrfs Volume or Subvolume</title>
+ <title>btrfs (optional) - Create Btrfs Volume or Subvolume</title>
+ <para>
+ Create a Btrfs volume or subvolume. For a volume, the syntax is:
+ </para>
+ <programlisting>
+<command>btrfs <replaceable>mntpoint</replaceable> --data=<replaceable>level</replaceable> --metadata=<replaceable>level</replaceable> [--label=] <replaceable>partitions</replaceable></command>
+ </programlisting>
<para>
- text
+ One or more partitions can be specified in <replaceable>partitions</replaceable>. When specifying more than one partitions, the entries must be separated by a single space. See <xref linkend="exam-kickstart-create-btrfs" /> for a demonstration.
+ </para>
+ <para>
+ For a subvolume, the syntax is:
+ </para>
+ <programlisting>
+<command>btrfs <replaceable>mntpoint</replaceable> --subvol --name=<replaceable>name</replaceable> <replaceable>parent</replaceable></command>
+ </programlisting>
+ <para>
+ <replaceable>parent</replaceable> should be the identifier of the subvolume's parent volume, <replaceable>name</replaceable> with a name for the subvolume, and <replaceable>mntpoint</replaceable> is the location where the file system is mounted.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><option>--data=</option></term>
+ <listitem>
+ <para>
+ RAID level to use for file system <emphasis>data</emphasis> (such as <literal>0</literal>, <literal>1</literal>, or <literal>10</literal>). This parameter is optional and has no meaning for subvolumes.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--metadata=</option></term>
+ <listitem>
+ <para>
+ RAID level to use for file system/volume <emphasis>metadata</emphasis> (such as <literal>0</literal>, <literal>1</literal>, or <literal>10</literal>). This parameter is optional and has no meaning for subvolumes.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--label=</option></term>
+ <listitem>
+ <para>
+ Specify a label for the Btrfs file system. If the given label is already in use by another file system, a new label will be created. This option has no meaning for subvolumes.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--subvol</option></term>
+ <listitem>
+ <para>
+ Create a Btrfs subvolume instead of a volume.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--name=</option></term>
+ <listitem>
+ <para>
+ Set a name for a Btrfs subvolume.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--noformat</option> or <option>--useexisting</option></term>
+ <listitem>
+ <para>
+ Use an existing Btrfs volume (or subvolume) and do not reformat the file system.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ The following example shows how to create a Btrfs volume from member partitions on three disks with subvolumes for <filename class="directory">/</filename> and <filename class="directory">/home</filename>. The main volume is not mounted or used directly in this example.
</para>
+ <example id="exam-kickstart-create-btrfs">
+ <title>Creating Btrfs Volumes and Subvolumes</title>
+ <programlisting>
+<command>part btrfs.01 --size=6000 --ondisk=sda</command>
+<command>part btrfs.02 --size=6000 --ondisk=sdb</command>
+<command>part btrfs.03 --size=6000 --ondisk=sdc</command>
+
+<command>btrfs none --data=0 --metadata=1 --label=f&PRODVER; btrfs.01 btrfs.02 btrfs.03</command>
+<command>btrfs / --subvol --name=root LABEL=f&PRODVER;</command>
+<command>btrfs /home --subvol --name=home f&PRODVER;</command>
+ </programlisting>
+ </example>
</section>
<section id="sect-kickstart-commands-clearpart">
- <title>clearpart - Remove All Existing Partitions</title>
+ <title>clearpart (optional) - Remove All Existing Partitions</title>
<para>
- text
+ Removes partitions from the system, prior to creation of new partitions. By default, no partitions are removed.
</para>
+ <programlisting>
+<command>clearpart [--all | --drives= | --list= | --linux | --none]</command>
+ </programlisting>
+ <note>
+ <para>
+ If the <command>clearpart</command> command is used, then the <command>part --onpart</command> command cannot be used on a logical partition.
+ </para>
+ </note>
+ <para>
+ For a detailed example of partitioning including the <command>clearpart</command> command, see <xref linkend="sect-kickstart-example-advanced-partitioning" />.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><option>--all</option></term>
+ <listitem>
+ <para>
+ Erases all partitions from the system.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--drives=</option></term>
+ <listitem>
+ <para>
+ Specifies which drives to clear partitions from. For example, the following clears all the partitions on the first two drives on the primary IDE controller:
+ </para>
+ <programlisting>
+<command>clearpart --drives=hda,hdb --all</command>
+ </programlisting>
+ <para>
+ To clear a multipath device, use the format <literal>disk/by-id/scsi-<replaceable>WWID</replaceable></literal>, where <replaceable>WWID</replaceable> is the <firstterm>world-wide identifier</firstterm> for the device. For example, to clear a disk with WWID <literal>58095BEC5510947BE8C0360F604351918</literal>, use:
+ </para>
+ <programlisting>
+<command>clearpart --drives=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918</command>
+ </programlisting>
+ <para>
+ This format is preferable for all multipath devices, but if errors arise, multipath devices that do not use <firstterm>logical volume management</firstterm> (LVM) can also be cleared using the format <literal>disk/by-id/dm-uuid-mpath-<replaceable>WWID</replaceable></literal>, where <replaceable>WWID</replaceable> is the <firstterm>world-wide identifier</firstterm> for the device. For example, to clear a disk with WWID <literal>2416CD96995134CA5D787F00A5AA11017</literal>, use:
+ </para>
+ <programlisting>
+<command>clearpart --drives=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017</command>
+ </programlisting>
+ <warning>
+ <para>
+ Never specify multipath devices by device names like <literal>mpatha</literal>. Device names such as this are not specific to a particular disk. The disk named <filename>/dev/mpatha</filename> during installation might not be the one that you expect it to be. Therefore, the <command>clearpart</command> command could target the wrong disk.
+ </para>
+ </warning>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--list=</option></term>
+ <listitem>
+ <para>
+ Specifies which partitions to clear. This option overrides the <option>--all</option> and <option>--linux</option> options if used. Can be used across different drives. For example:
+ </para>
+ <programlisting>
+<command>clearpart --list=sda2,sda3,sdb1</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--linux</option></term>
+ <listitem>
+ <para>
+ Erases all Linux partitions.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--none</option></term>
+ <listitem>
+ <para>
+ Do not remove any partitions. This is the default behavior - using this option is the same as not using the <command>clearpart</command> command at all.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <note>
+ <para>
+ Using the <command>clearpart --all</command> command in a Kickstart file to remove all existing partitions during the installation will cause <application>Anaconda</application> to pause and prompt you for a confirmation. If you need to perform the installation automatically with no interaction, add the <command>zerombr</command> command to your Kickstart file.
+ </para>
+ </note>
</section>
<section id="sect-kickstart-commands-fcoe">
- <title>fcoe - Configure Fibre Channel Over Ethernet Devices</title>
- <para>
- text
+ <title>fcoe (optional) - Configure Fibre Channel Over Ethernet Devices</title>
+ <para>
+ Specify which FCoE devices should be activated automatically in addition to those discovered by <firstterm>Enhanced Disk Drive Services</firstterm> (EDD).
</para>
+ <programlisting>
+<command>fcoe --nic=<replaceable>name</replaceable> [--dcp= | --autovlan]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--nic=</option> (required)</term>
+ <listitem>
+ <para>
+ Name of the device to be activated.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--dcb=</option></term>
+ <listitem>
+ <para>
+ Establish <firstterm>Data Center Bridging</firstterm> (DCB) settings.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--autovlan</option></term>
+ <listitem>
+ <para>
+ Discover VLANs automatically.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-ignoredisk">
<title>ignoredisk - Ignore Specified Disks</title>
<para>
- text
+ Causes the installation program to ignore the specified disks. This is useful if you use autopartition and want to be sure that some disks are ignored. For example, without <command>ignoredisk</command>, attempting to deploy on a SAN cluster the Kickstart would fail, as the installation program detects passive paths to the SAN that return no partition table.
</para>
+ <programlisting>
+<command>ignoredisk --drives= | --only-use= [--interactive]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--drives=</option></term>
+ <listitem>
+ <para>
+ Specify one or more drives to ignore. Multiple drives can be specified as a comma-separated list. For example:
+ </para>
+ <programlisting>
+<command>ignoredisk --drives=sda,sdc</command>
+ </programlisting>
+ <para>
+ To ignore a multipath device that does not use <firstterm>logical volume management</firstterm> (LVM), use the format <literal>disk/by-id/dm-uuid-mpath-<replaceable>WWID</replaceable></literal>, where <replaceable>WWID</replaceable> is the <firstterm>world-wide identifier</firstterm> for the device. For example, to ignore a disk with WWID <literal>2416CD96995134CA5D787F00A5AA11017</literal>, use:
+ </para>
+ <programlisting>
+<command>ignoredisk --drives=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017</command>
+ </programlisting>
+ <para>
+ Multipath devices that use LVM are not assembled until after <application>Anaconda</application> has parsed the Kickstart file. Therefore, you cannot specify these devices in the format <literal>dm-uuid-mpath</literal>. Instead, to ignore a multipath device that uses LVM, use the format <literal>disk/by-id/scsi-<replaceable>WWID</replaceable></literal>, where <replaceable>WWID</replaceable> is the <firstterm>world-wide identifier</firstterm> for the device. For example, to ignore a disk with WWID <literal>58095BEC5510947BE8C0360F604351918</literal>, use:
+ </para>
+ <programlisting>
+<command>ignoredisk --drives=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918</command>
+ </programlisting>
+ <warning>
+ <para>
+ Never specify multipath devices by device names like <literal>mpatha</literal>. Device names such as this are not specific to a particular disk. The disk named <filename>/dev/mpatha</filename> during installation might not be the one that you expect it to be. Therefore, the <command>clearpart</command> command could target the wrong disk.
+ </para>
+ </warning>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--only-use=</option></term>
+ <listitem>
+ <para>
+ Specifies a list of disks for the installation program to use. All other disks are ignored. For example, to use disk <literal>sda</literal> during installation and ignore all other disks:
+ </para>
+ <programlisting>
+<command>ignoredisk --only-use=sda</command>
+ </programlisting>
+ <para>
+ To include a multipath device that does not use LVM:
+ </para>
+ <programlisting>
+<command>ignoredisk --only-use=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017</command>
+ </programlisting>
+ <para>
+ To include a multipath device that uses LVM:
+ </para>
+ <programlisting>
+<command>ignoredisk --only-use=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--interactive</option></term>
+ <listitem>
+ <para>
+ Allows you to manually navigate the advanced storage screen.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-iscsi">
@@ -206,10 +761,94 @@
</para>
<section id="sect-kickstart-commands-firewall">
- <title>firewall - Configure Firewall</title>
+ <title>firewall (optional) - Configure Firewall</title>
<para>
- text
+ Specify the firewall configuration for the installed system. <remark>TODO: link to the Firewall guide once we have one</remark>
</para>
+ <programlisting>
+<command>firewall --enabled | --disabled <replaceable>device</replaceable> [--trust= | --ssh | --smtp | --http | --ftp | --port= | --service=]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--enabled</option> or <option>--enable</option></term>
+ <listitem>
+ <para>
+ Reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is needed, you can choose to allow specific services through the firewall.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--disabled</option> or <option>--disable</option></term>
+ <listitem>
+ <para>
+ Disable the firewall.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--trust=</option></term>
+ <listitem>
+ <para>
+ Listing a device here, such as <literal>em1</literal>, allows all traffic coming to and from that device to go through the firewall. To list more than one device, use this option again - for example:
+ </para>
+ <programlisting>
+<command>firewall --enable --trust=em1 --trust=em2</command>
+ </programlisting>
+ <para>
+ Do not use a comma-separated format such as <option>--trust em1, em2</option>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><replaceable>incoming</replaceable></term>
+ <listitem>
+ <para>
+ Replace with one or more of the following to allow the specified services through the firewall:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <option>--ssh</option>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <option>--smtp</option>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <option>--http</option>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <option>--ftp</option>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--port=</option></term>
+ <listitem>
+ <para>
+ You can specify that ports be allowed through the firewall using the port:protocol format. For example, to allow IMAP access through your firewall, specify <literal>imap:tcp</literal>. Numeric ports can also be specified explicitly; for example, to allow UDP packets on port 1234 through, specify <literal>1234:udp</literal>. To specify multiple ports, separate them by commas.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--service=</option></term>
+ <listitem>
+ <para>
+ This option provides a higher-level way to allow services through the firewall. Some services (like <systemitem>cups</systemitem>, <systemitem>avahi</systemitem>, etc.) require multiple ports to be open or other special configuration in order for the service to work. You can specify each individual port with the <option>--port</option> option, or specify <command>--service=</command> and open them all at once.
+ </para>
+ <para>
+ Valid options are anything recognized by the <application>firewall-offline-cmd</application> program in the <package>firewalld</package> package. If <systemitem>firewalld</systemitem> is running, <command>firewall-cmd --get-services</command> will provide a list of known service names.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-network">
@@ -278,21 +917,221 @@
</para>
<section id="sect-kickstart-commands-auth">
- <title>auth - Configure Authentication</title>
+ <title>auth or authconfig (optional) - Configure Authentication</title>
<para>
- text
+ Sets up the authentication options for the system using the <command>authconfig</command> command, which can also be run on a command line after the installation finishes. See the <systemitem>authconfig(8)</systemitem> manual page and the <command>authconfig --help</command> command for more details. Passwords are shadowed by default.
</para>
+ <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>
+ <varlistentry>
+ <term><option>--enablenis</option></term>
+ <listitem>
+ <para>
+ Turns on NIS support. By default, <option>--enablenis</option> uses whatever domain it finds on the network. A domain should almost always be set by hand with the <option>--nisdomain=</option> option.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--nisdomain=</option></term>
+ <listitem>
+ <para>
+ NIS domain name to use for NIS services.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--nisserver=</option></term>
+ <listitem>
+ <para>
+ Server to use for NIS services (broadcasts by default).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--useshadow</option>or <option>--enableshadow</option></term>
+ <listitem>
+ <para>
+ Use shadow passwords. Active by default.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--enableldap</option></term>
+ <listitem>
+ <para>
+ Turns on LDAP support in <filename>/etc/nsswitch.conf</filename>, allowing your system to retrieve information about users (for example, their UIDs, home directories, and shells) from an LDAP directory. To use this option, you must install the <package>nss-pam-ldapd</package> package. You must also specify a server and a base <firstterm>DN</firstterm> (distinguished name) with <option>--ldapserver=</option> and <option>--ldapbasedn=</option>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--enableldapauth</option></term>
+ <listitem>
+ <para>
+ Use LDAP as an authentication method. This enables the <systemitem>pam_ldap</systemitem> module for authentication and changing passwords, using an LDAP directory. To use this option, you must have the <package>nss-pam-ldapd</package> package installed. You must also specify a server and a base DN with <option>--ldapserver=</option> and <option>--ldapbasedn=</option>. If your environment does not use <firstterm>TLS</firstterm> (Transport Layer Security), use the <option>--disableldaptls</option> switch to ensure that the resulting configuration file works.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--ldapserver=</option></term>
+ <listitem>
+ <para>
+ If you specified either <option>--enableldap</option> or <option>--enableldapauth</option>, use this option to specify the name of the LDAP server to use. This option is set in the <filename>/etc/ldap.conf</filename> file.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--ldapbasedn=</option></term>
+ <listitem>
+ <para>
+ If you specified either <option>--enableldap</option> or <option>--enableldapauth</option>, use this option to specify the DN in your LDAP directory tree under which user information is stored. This option is set in the <filename>/etc/ldap.conf</filename> file.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--enableldaptls</option></term>
+ <listitem>
+ <para>
+ Use TLS (Transport Layer Security) lookups. This option allows LDAP to send encrypted usernames and passwords to an LDAP server before authentication.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--disableldaptls</option></term>
+ <listitem>
+ <para>
+ Do not use TLS (Transport Layer Security) lookups in an environment that uses LDAP for authentication.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--enablekrb5</option></term>
+ <listitem>
+ <para>
+ Use Kerberos 5 for authenticating users. Kerberos itself does not know about home directories, UIDs, or shells. If you enable Kerberos, you must make users' accounts known to this workstation by enabling LDAP, NIS, or Hesiod or by using the <command>useradd</command> command. If you use this option, you must have the <package>pam_krb5</package> package installed.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--krb5realm=</option></term>
+ <listitem>
+ <para>
+ The Kerberos 5 realm to which your workstation belongs.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--krb5kdc=</option></term>
+ <listitem>
+ <para>
+ The KDC (or KDCs) that serve requests for the realm. If you have multiple KDCs in your realm, use a comma-separated list without spaces.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--krb5adminserver=</option></term>
+ <listitem>
+ <para>
+ The KDC in your realm that is also running kadmind. This server handles password changing and other administrative requests. This server must be run on the master KDC if you have more than one KDC.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--enablehesiod</option></term>
+ <listitem>
+ <para>
+ Enables Hesiod support for looking up user home directories, UIDs, and shells. More information on setting up and using Hesiod on your network is in <filename>/usr/share/doc/glibc-2.x.x/README.hesiod</filename>, which is included in the <package>glibc</package> package. Hesiod is an extension of DNS that uses DNS records to store information about users, groups, and various other items.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--hesiodlhs=</option> and <option>--hesiodrhs=</option></term>
+ <listitem>
+ <para>
+ The <systemitem>Hesiod</systemitem> LHS (left-hand side) and RHS (right-hand side) values, set in <filename>/etc/hesiod.conf</filename>. The <systemitem>Hesiod</systemitem> library uses these values to search DNS for a name, similar to the way that <systemitem>LDAP</systemitem> uses a base DN.
+ </para>
+ <para>
+ To look up user information for the username <systemitem>jim</systemitem>, the Hesiod library looks up <literal>jim.passwd<replaceable>LHS</replaceable><replaceable>RHS</replaceable></literal>, which should resolve to a TXT record that contains a string identical to an entry for that user in the <filename>passwd</filename> file: <computeroutput>jim:*:501:501:Jungle Jim:/home/jim:/bin/bash</computeroutput>. To look up groups, the Hesiod library looks up <literal>jim.group<replaceable>LHS</replaceable><replaceable>RHS</replaceable></literal> instead.
+ </para>
+ <para>
+ To look up users and groups by number, make <literal>501.uid</literal> a CNAME for <literal>jim.passwd</literal>, and <literal>501.gid</literal> a CNAME for <literal>jim.group</literal>. Note that the library does not place a period (<literal>.</literal>) in front of the LHS and RHS values when performing a search. Therefore, if the LHS and RHS values need to have a period placed in front of them, you must include the period in the values you set for <option>--hesiodlhs=</option> and <option>--hesiodrhs=</option>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--enablesmbauth</option></term>
+ <listitem>
+ <para>
+ Enables authentication of users against an SMB server (typically a Samba or Windows server). SMB authentication support does not know about home directories, UIDs, or shells. If you enable SMB, you must make users' accounts known to the workstation by enabling LDAP, NIS, or Hesiod or by using the <command>useradd</command> command.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--smbservers=</option></term>
+ <listitem>
+ <para>
+ The name of the servers to use for SMB authentication. To specify more than one server, separate the names with commas (<literal>,</literal>).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--smbworkgroup=</option></term>
+ <listitem>
+ <para>
+ The name of the workgroup for the SMB servers.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--enablecache</option></term>
+ <listitem>
+ <para>
+ Enables the <systemitem>nscd</systemitem> service. The <systemitem>nscd</systemitem> service caches information about users, groups, and various other types of information. Caching is especially helpful if you choose to distribute information about users and groups over your network using <systemitem>NIS</systemitem>, <systemitem>LDAP</systemitem>, or <systemitem>Hesiod</systemitem>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--passalgo=</option></term>
+ <listitem>
+ <para>
+ Specify <option>sha256</option> to set up the SHA-256 hashing algorithm or <option>sha512</option> to set up the SHA-512 hashing algorithm.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-group">
<title>group - Create User Group</title>
<para>
- text
+ Creates a new user group on the system. If a group with the given name or GID already exists, this command will fail. In addition, the <command>user</command> command can be used to create a new group for the newly created user.
</para>
+ <programlisting>
+<command>group --name=<replaceable>name</replaceable> [--gid=<replaceable>gid</replaceable>]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--name=</option></term>
+ <listitem>
+ <para>
+ Provides the name of the group.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--gid=</option></term>
+ <listitem>
+ <para>
+ The group ID (GID). If not provided, defaults to the next available non-system GID.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-realm">
- <title>realm - Join AD or IPA Domain</title>
+ <title>realm - Join an Active Directory or IPA Domain</title>
<para>
text
</para>
@@ -328,23 +1167,36 @@
</para>
<section id="sect-kickstart-commands-autostep">
- <title>autostep - Go Through Every Screen Automatically</title>
+ <title>autostep (optional) - Go Through Every Screen</title>
<para>
- text
+ Normally, Kickstart installations skip unnecessary screens. This option makes the installation program step through every screen, displaying each briefly. This option should not be used when deploying a system because it may disrupt package installation.
</para>
+ <programlisting>
+<command>autostep [--autoscreenshot]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--autoscreenshot</option></term>
+ <listitem>
+ <para>
+ Take a screenshot at every step during installation and copy the images over to <filename>/tmp/anaconda-screenshots</filename> after installation is complete. This is useful for documentation.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-cmdline">
- <title>cmdline - Perform Installation in Command Line Mode</title>
- <para>
- text
+ <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. The recommended use is in conjunction with the <option>RUNKS=1</option> and <option>inst.ks=</option> parameters.
</para>
</section>
<section id="sect-kickstart-commands-graphical">
- <title>graphical - Perform Installation in Graphical Mode</title>
+ <title>graphical (optional) - Perform Installation in Graphical Mode</title>
<para>
- text
+ Perform the installation in graphical mode. This is the default. This command takes no options.
</para>
</section>
@@ -399,23 +1251,68 @@
</para>
<section id="sect-kickstart-commands-eula">
- <title>eula - Accept the License Agreement</title>
+ <title>eula (optional) - Accept the License Agreement</title>
<para>
- text
+ Use this option to accept the <firstterm>End User License Agreement</firstterm> (EULA) without user interaction. Specifying this option prevents <application>Initial Setup</application> from prompting you to accept the license agreement after you finish the installation and reboot the system for the first time. See <xref linkend="sect-initial-setup" /> for more information.
</para>
+ <variablelist>
+ <varlistentry>
+ <term><option>--agreed</option></term>
+ <listitem>
+ <para>
+ Accept the EULA. This option must always be used, otherwise the <command>eula</command> command is meaningless. <remark>TODO: Does this even make sense on Fedora? Does initial-setup have an EULA in it?</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-firstboot">
- <title>firstboot - Enable or Disable Initial Setup</title>
+ <title>firstboot (optional) - Enable or Disable Initial Setup</title>
<para>
- text
+ Determine whether the <application>Initial Setup</application> application starts the first time the system is booted. If enabled, the <package>initial-setup</package> package must be installed. If not specified, this option is disabled by default. For more information about <application>Initial Setup</application>, see <xref linkend="sect-initial-setup" />.
</para>
+ <programlisting>
+<command>firstboot --enable|--disable [--reconfig]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--enable</option> or <option>--enabled</option></term>
+ <listitem>
+ <para>
+ <application>Initial Setup</application> will be started the first time the installed system boots.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--disable</option> or <option>--disabled</option></term>
+ <listitem>
+ <para>
+ <application>Initial Setup</application> will be disabled.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--reconfig</option></term>
+ <listitem>
+ <para>
+ <application>Initial Setup</application> will start after the reboot in reconfiguration mode. This mode enables the language, mouse, keyboard, root password, security level, time zone and networking configuration options in addition to the default ones.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-halt">
- <title>halt - Halt System After Installation</title>
+ <title>halt (optional) - Halt System After Installation</title>
<para>
- text
+ 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>
+ The <command>halt</command> command is equivalent to the <command>shutdown -h</command> command.
+ </para>
+ <para>
+ For other completion methods, see the <command>poweroff</command>, <command>reboot</command>, and <command>shutdown</command> commands.
</para>
</section>
@@ -700,7 +1597,7 @@ docbook*
</varlistentry>
</variablelist>
<para>
- For an example of a pre-installation script, see <xref linkend="exam-kickstart-pre-script" />.
+ For an example of a pre-installation script, see <xref linkend="sect-kickstart-example-pre-script" />.
</para>
</section>
@@ -783,7 +1680,7 @@ cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
</varlistentry>
</variablelist>
<para>
- For an example of a post-installation script, see <xref linkend="sect-kickstart-example-post" />.
+ For an example of a post-installation script, see <xref linkend="sect-kickstart-example-post-script" />.
</para>
</section>
@@ -825,22 +1722,22 @@ cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
<command>logvol /var/freespace --vgname=sysvg --size=8000 --name=freespacetouse</command>
<command>logvol /usr/local --vgname=sysvg --size=1 --grow --name=usrlocal</command>
</programlisting>
- <para>
- This advanced example implements LVM over RAID, as well as the ability to resize various directories for future growth.
- </para>
- <para>
- First, the <command>clearpart</command> command is used on drives <systemitem>hda</systemitem> and <systemitem>hdc</systemitem> to wipe them. The <command>zerombr</command> command initializes unused partition tables.
- </para>
- <para>
- Then, the two drives are partitioned to prepare them for RAID configuration. Each drive is divided into five partitions, and each drive is partitioned into an identical layout.
- </para>
- <para>
- The next part uses these pairs of physical partitions to create a software RAID device with RAID1 level (mirroring). The first four RAID devices are used for <filename>/</filename> (root), <filename>/safe</filename>, <systemitem>swap</systemitem> and <filename>/usr</filename>. The fifth, largest pair of partitions is named <literal>pv.01</literal> and will be used in the following part as a physical volume for LVM.
- </para>
- <para>
- Finally, the last set of commands first creates a volume group named <literal>sysvg</literal> on the <literal>pv.01</literal> physical volume. Then, three logical volumes (<literal>/var</literal>, <literal>/var/freespace</literal> and <literal>/usr/local</literal>) are created and added to the <literal>sysvg</literal> volume group. The <literal>/var</literal> and <literal>/var/freespace</literal> volumes have a set size of 8 GB, and the <literal>/usr/local</literal> volume uses the <option>--grow</option> option to fill all remaining available space.
- </para>
</example>
+ <para>
+ This advanced example implements LVM over RAID, as well as the ability to resize various directories for future growth.
+ </para>
+ <para>
+ First, the <command>clearpart</command> command is used on drives <systemitem>hda</systemitem> and <systemitem>hdc</systemitem> to wipe them. The <command>zerombr</command> command initializes unused partition tables.
+ </para>
+ <para>
+ Then, the two drives are partitioned to prepare them for RAID configuration. Each drive is divided into five partitions, and each drive is partitioned into an identical layout.
+ </para>
+ <para>
+ The next part uses these pairs of physical partitions to create a software RAID device with RAID1 level (mirroring). The first four RAID devices are used for <filename>/</filename> (root), <filename>/safe</filename>, <systemitem>swap</systemitem> and <filename>/usr</filename>. The fifth, largest pair of partitions is named <literal>pv.01</literal> and will be used in the following part as a physical volume for LVM.
+ </para>
+ <para>
+ Finally, the last set of commands first creates a volume group named <literal>sysvg</literal> on the <literal>pv.01</literal> physical volume. Then, three logical volumes (<literal>/var</literal>, <literal>/var/freespace</literal> and <literal>/usr/local</literal>) are created and added to the <literal>sysvg</literal> volume group. The <literal>/var</literal> and <literal>/var/freespace</literal> volumes have a set size of 8 GB, and the <literal>/usr/local</literal> volume uses the <option>--grow</option> option to fill all remaining available space.
+ </para>
<important>
<para>
The above example uses identifiers <systemitem>hda</systemitem> and <systemitem>hdc</systemitem> to identify disk drives. You should use unique identifiers, such as a disk labels or an UUIDs, to identify disk drives. See the note in introduction to this appendix.
@@ -848,7 +1745,7 @@ cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
</important>
</section>
- <section id="sect-kickstart-example-pre">
+ <section id="sect-kickstart-example-pre-script">
<title>Example Pre-installation Script</title>
<para>
The following is an example <command>%pre</command> section:
@@ -903,7 +1800,7 @@ fi
</example>
</section>
- <section id="sect-kickstart-example-post">
+ <section id="sect-kickstart-example-post-script">
<title>Example Post-installation Script</title>
<para>
The following is an example <command>%post</command> section:
More information about the docs-commits
mailing list