commit a0ba206e7d252212b66f7c4096c99e4454b98c1f Author: Petr Bokoc pbokoc@redhat.com Date: Mon Jul 20 13:24:19 2015 +0200
UI mode must always be specified for automatic KS installs
en-US/Kickstart_Syntax_Reference.xml | 89 ++++++++++++++++++++-------------- 1 files changed, 52 insertions(+), 37 deletions(-) --- diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml index 9be5da7..ba811e7 100644 --- a/en-US/Kickstart_Syntax_Reference.xml +++ b/en-US/Kickstart_Syntax_Reference.xml @@ -11,7 +11,7 @@ <important> <para> Device names are not guaranteed to be consistent across reboots, which can complicate usage in Kickstart scripts. When a Kickstart option calls for a device node name (such as <literal>sda</literal>), you can instead use any item from <filename>/dev/disk</filename>. For example, instead of: - </para> + </para> <programlisting><command>part / --fstype=xfs --onpart=sda1</command></programlisting> <para> You could use an entry similar to one of the following: @@ -21,8 +21,8 @@ <command>part / --fstype=xfs --onpart=/dev/disk/by-id/ata-ST3160815AS_6RA0C882-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> + 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: @@ -69,7 +69,7 @@
<section id="sect-kickstart-commands-driverdisk"> <title>driverdisk (optional) - Use a Driver Disk</title> - <para> + <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> @@ -171,7 +171,7 @@ Install from a disk image instead of packages. The image can be the <filename>squashfs.img</filename> file from a live ISO image, or any file system that the installation media can mount. Supported file systems are <systemitem>ext2</systemitem>, <systemitem>ext3</systemitem>, <systemitem>ext4</systemitem>, <systemitem>vfat</systemitem>, and <systemitem>xfs</systemitem>. </para> <para> - This command also supports installation from tar archives of the root file system. In that case, the file name must end with <literal>.tar</literal>, <literal>.tbz</literal>, <literal>.tgz</literal>, <literal>.txz</literal>, <literal>.tar.bz2</literal>, <literal>tar.gz</literal>, or <literal>tar.xz</literal>. + This command also supports installation from tar archives of the root file system. In that case, the file name must end with <literal>.tar</literal>, <literal>.tbz</literal>, <literal>.tgz</literal>, <literal>.txz</literal>, <literal>.tar.bz2</literal>, <literal>tar.gz</literal>, or <literal>tar.xz</literal>. </para> <programlisting> <command>install</command> @@ -464,7 +464,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 (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> <important> <para> @@ -626,7 +626,7 @@ <term><option>--location=</option></term> <listitem> <para> - Specifies where the boot record is written. Valid values are the following: + Specifies where the boot record is written. Valid values are the following: </para> <itemizedlist> <listitem> @@ -715,7 +715,7 @@ <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. + 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> @@ -724,7 +724,7 @@
<section id="sect-kickstart-commands-btrfs"> <title>btrfs (optional) - Create Btrfs Volume or Subvolume</title> - <para> + <para> Create a Btrfs volume or subvolume. For a volume, the syntax is: </para> <programlisting> @@ -855,7 +855,7 @@ <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> + </warning> </listitem> </varlistentry> <varlistentry> @@ -901,7 +901,7 @@
<section id="sect-kickstart-commands-fcoe"> <title>fcoe (optional) - Configure Fibre Channel Over Ethernet Devices</title> - <para> + <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> @@ -966,7 +966,7 @@ <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: + 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> @@ -1322,7 +1322,7 @@ <term><option>--profile=</option></term> <listitem> <para> - Specify the configuration profile name to use with thin logical volumes. If used, the name will also be included in the metadata for the given logical volume. By default, the available profiles are <literal>default</literal> and <literal>thin-performance</literal> and are defined in the <filename class="directory">/etc/lvm/profile</filename> directory. See the <systemitem>lvm(8)</systemitem> man page for additional information. + Specify the configuration profile name to use with thin logical volumes. If used, the name will also be included in the metadata for the given logical volume. By default, the available profiles are <literal>default</literal> and <literal>thin-performance</literal> and are defined in the <filename class="directory">/etc/lvm/profile</filename> directory. See the <systemitem>lvm(8)</systemitem> man page for additional information. </para> </listitem> </varlistentry> @@ -1334,7 +1334,7 @@ <command>part pv.01 --size 3000</command> <command>volgroup myvg pv.01</command> <command>logvol / --vgname=myvg --size=2000 --name=rootvol</command> - </programlisting> + </programlisting> </section>
<section id="sect-kickstart-commands-part"> @@ -1848,7 +1848,7 @@ <command>part pv.01 --size 3000</command> <command>volgroup myvg pv.01</command> <command>logvol / --vgname=myvg --size=2000 --name=rootvol</command> - </programlisting> + </programlisting> </section>
<section id="sect-kickstart-commands-zerombr"> @@ -1992,10 +1992,10 @@ <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. + 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. + 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> @@ -2727,7 +2727,7 @@ <section id="sect-kickstart-commands-group"> <title>group (optional) - Create User Group</title> <para> - 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. + 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> @@ -3142,9 +3142,14 @@
<section id="sect-kickstart-commands-cmdline"> <title>cmdline (optional) - Perform Installation in Command Line Mode</title> - <para> + <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. </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"> @@ -3152,6 +3157,11 @@ <para> Perform the installation in graphical mode. This is the default. This command takes no options. </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-logging"> @@ -3268,6 +3278,11 @@ <para> Perform the Kickstart installation in text mode. Kickstart installations are performed in graphical mode by default. </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-unsupported_hardware"> @@ -3529,7 +3544,7 @@ <command>%ksappend</command> is processed in an initial pass, before any other part of the Kickstart file. Then, this expanded Kickstart file is passed to the rest of <application>Anaconda</application> where all <command>%pre</command> scripts are handled, and then finally the rest of the Kickstart file is processed in order, which includes <command>%include</command> directives. </para> <para> - Therefore, <command>%ksappend</command> provides a way to include a file containing <command>%pre</command> scripts, while <command>%include</command> does not. + Therefore, <command>%ksappend</command> provides a way to include a file containing <command>%pre</command> scripts, while <command>%include</command> does not. </para> </section>
@@ -3550,7 +3565,7 @@ <important> <para> To install a 32-bit package on a 64-bit system, you will need to append the package name with the 32-bit architecture for which the package was built - for example, <package>glibc.i686</package>. The <option>--multilib</option> option also must be specified in the Kickstart file; see the available options below. - </para> + </para> </important> <important> <para> @@ -3572,7 +3587,7 @@ </programlisting> <para> This command will install all packages which are part of the <guilabel>Infrastracture Server</guilabel> environment. All available environments are described in the <filename>comps.xml</filename> file. - </para> + </para> </listitem> </varlistentry> <varlistentry> @@ -3582,7 +3597,7 @@ Specify groups, one entry to a line, starting with an <literal>@</literal> symbol, and then the full group name or group id as given in the <filename>comps.xml</filename> file. For example: </para> <programlisting> -<command>%packages</command> +<command>%packages</command> @X Window System @Desktop @Sound and Video @@ -3592,7 +3607,7 @@ The <literal>Core</literal> and <literal>Base</literal> groups are always selected - it is not necessary to specify them in the <command>%packages</command> section. </para> <para> - The <filename>comps.xml</filename> file also defines groups called <literal>Conflicts (<replaceable>variant</replaceable>)</literal> for each variant of &PRODUCT;. This group contains all packages which are known to cause file conflicts, and is intended to be excluded. + The <filename>comps.xml</filename> file also defines groups called <literal>Conflicts (<replaceable>variant</replaceable>)</literal> for each variant of &PRODUCT;. This group contains all packages which are known to cause file conflicts, and is intended to be excluded. </para> </listitem> </varlistentry> @@ -3603,7 +3618,7 @@ Specify individual packages by name, one entry to a line. You can use the asterisk character (<literal>*</literal>) as a <firstterm>wildcard</firstterm> in package names. For example: </para> <programlisting> -<command>%packages</command> +<command>%packages</command> sqlite curl aspell @@ -3622,8 +3637,8 @@ docbook* Use a leading dash (<literal>-</literal>) to specify packages or groups to exclude from the installation. For example: </para> <programlisting> -<command>%packages</command> --@Graphical Internet +<command>%packages</command> +-@Graphical Internet -autofs -ipa*fonts <command>%end</command> @@ -3644,7 +3659,7 @@ docbook* <para> The following options are available for the <command>%packages</command>. To use an option, append it to the start of the package selection section. For example: </para> - <programlisting><command>%packages --multilib --ignoremissing</command></programlisting> + <programlisting><command>%packages --multilib --ignoremissing</command></programlisting> <varlistentry> <term> <option>--nocore</option> @@ -3687,7 +3702,7 @@ docbook* Normally, on a 64-bit system, only packages for this architecture (marked as <literal>x86_64</literal>) and packages for all architectures (marked as <literal>noarch</literal>) would be installed. When you use this option, packages for 32-bit systems (marked as <literal>i686</literal>) will be automatically installed as well, if available. </para> <para> - This only applies to packages explicitly specified in the <command>%packages</command> section. Packages which are only being installed as dependencies without being specified in the Kickstart file will only be installed in architecture versions in which they are needed, even if they are available for more architectures. + This only applies to packages explicitly specified in the <command>%packages</command> section. Packages which are only being installed as dependencies without being specified in the Kickstart file will only be installed in architecture versions in which they are needed, even if they are available for more architectures. </para> </listitem> </varlistentry> @@ -3791,7 +3806,7 @@ docbook* </para> <para> This section is useful for functions such as installing additional software or configuring an additional name server. The post-install script is run in a chroot environment, therefore, performing tasks such as copying scripts or RPM packages from the installation media do not work by default. You can change this behavior using the <option>--nochroot</option> option as described below. - </para> + </para> <important> <para> If you configured the network with static IP information, including a name server, you can access the network and resolve IP addresses in the <command>%post</command> section. If you configured the network for <systemitem>DHCP</systemitem>, the <filename>/etc/resolv.conf</filename> file has not been completed when the installation executes the <command>%post</command> section. You can access the network, but you cannot resolve IP addresses. Thus, if you are using <systemitem>DHCP</systemitem>, you must specify IP addresses in the <command>%post</command> section. @@ -3874,19 +3889,19 @@ cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf <programlisting> <command>clearpart --drives=hda,hdc</command> <command>zerombr</command> -# Raid 1 IDE config -<command>part raid.11 --size 1000 --asprimary --ondrive=hda</command> +# Raid 1 IDE config +<command>part raid.11 --size 1000 --asprimary --ondrive=hda</command> <command>part raid.12 --size 1000 --asprimary --ondrive=hda</command> <command>part raid.13 --size 2000 --asprimary --ondrive=hda</command> <command>part raid.14 --size 8000 --ondrive=hda</command> -<command>part raid.15 --size 16384 --grow --ondrive=hda</command> +<command>part raid.15 --size 16384 --grow --ondrive=hda</command> <command>part raid.21 --size 1000 --asprimary --ondrive=hdc</command> <command>part raid.22 --size 1000 --asprimary --ondrive=hdc</command> <command>part raid.23 --size 2000 --asprimary --ondrive=hdc</command> <command>part raid.24 --size 8000 --ondrive=hdc</command> <command>part raid.25 --size 16384 --grow --ondrive=hdc</command>
-# You can add --spares=x +# You can add --spares=x <command>raid / --fstype xfs --device root --level=RAID1 raid.11 raid.21</command> <command>raid /safe --fstype xfs --device safe --level=RAID1 raid.12 raid.22</command> <command>raid swap --fstype swap --device swap --level=RAID1 raid.13 raid.23</command> @@ -3895,7 +3910,7 @@ cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
# LVM configuration so that we can resize /var and /usr/local later <command>volgroup sysvg pv.01</command> -<command>logvol /var --vgname=sysvg --size=8000 --name=var</command> +<command>logvol /var --vgname=sysvg --size=8000 --name=var</command> <command>logvol /var/freespace --vgname=sysvg --size=8000 --name=freespacetouse</command> <command>logvol /usr/local --vgname=sysvg --size=1 --grow --name=usrlocal</command> </programlisting> @@ -3939,13 +3954,13 @@ mymedia=`cat $file/media` if [ $mymedia == "disk" ] ; then hds="$hds `basename $file`" fi -done +done set $hds numhd=`echo $#` drive1=`echo $hds | cut -d' ' -f1` drive2=`echo $hds | cut -d' ' -f2`
-#Write out partition scheme based on whether there are 1 or 2 hard drives +#Write out partition scheme based on whether there are 1 or 2 hard drives if [ $numhd == "2" ] ; then #2 drives echo "#partitioning scheme generated in %pre for 2 drives" > /tmp/part-include
docs-commits@lists.fedoraproject.org
-
pbokoc