[install-guide/F21-rewrite] Updating description of inst.stage2 in Boot Options
by pbokoc 23 Sep '14
by pbokoc 23 Sep '14
23 Sep '14
commit 758f2e9ed29e2c79a0341c3b58ec497bff0ee097
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Sep 23 15:51:49 2014 +0200
Updating description of inst.stage2 in Boot Options
en-US/Boot_Options.xml | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/en-US/Boot_Options.xml b/en-US/Boot_Options.xml
index cacc661..704d064 100644
--- a/en-US/Boot_Options.xml
+++ b/en-US/Boot_Options.xml
@@ -189,9 +189,9 @@
<varlistentry>
<term><option>inst.stage2=</option></term>
<listitem>
- <para>
- Specifies the location of the installation program runtime image to be loaded. The syntax is the same as in <xref linkend="tabl-boot-options-sources" />. This option will ignore everything except for the image itself, it is not possible to use it to specify the location of packages.
- </para>
+ <para>
+ Specifies the location of the installation program runtime image to be loaded. The syntax is the same as in <xref linkend="tabl-boot-options-sources" />. This option expects a path to a directory containing a valid <filename>.treeinfo</filename> file; the location of the runtime image will be read from this file if found. If a <filename>.treeinfo</filename> file is not available, <application>Anaconda</application> will try to load the image from <filename>LiveOS/squashfs.img</filename>.
+ </para>
</listitem>
</varlistentry>
<varlistentry>
1
0
commit 58e7000290719bf835fd91339f785faa2ff36178
Author: John J. McDonough <jjmcd(a)fedoraproject.org>
Date: Mon Sep 22 10:49:01 2014 -0400
Automatic update
tools/doc-publican-rpm/cleanString.c | 36 +++++++++++++++-------------
tools/doc-publican-rpm/doc-publican-rpm.h | 6 ++--
tools/doc-publican-rpm/makeDesktopFile.c | 12 +++++-----
3 files changed, 28 insertions(+), 26 deletions(-)
---
diff --git a/tools/doc-publican-rpm/cleanString.c b/tools/doc-publican-rpm/cleanString.c
index 8252b8c..864aef7 100644
--- a/tools/doc-publican-rpm/cleanString.c
+++ b/tools/doc-publican-rpm/cleanString.c
@@ -8,6 +8,8 @@
*/
#include <stdio.h>
#include <string.h>
+#include <stdlib.h>
+#include <wchar.h>
/*! cleanString() - remove & tags from a string
@@ -22,43 +24,43 @@
\arg szInT - pointer to the input string
\arg szOut - pointer to a buffer for the result
*/
-void cleanString( char *szInT, char *szOut )
+void cleanString( wchar_t *szInT, wchar_t *szOut )
{
- char *q;
- char szIn[1024];
- int recurse;
+ wchar_t *q;
+ wchar_t szIn[1024];
+ //int recurse;
- recurse = 0;
- strcpy(szIn,szInT);
- q=strchr(szIn,'&');
+ //recurse = 0;
+ wcscpy(szIn,szInT);
+ q=wcschr(szIn,'&');
if ( !q )
{
//printf("Returning original string:\n%s\n",szIn);
- strcpy(szOut,szIn);
+ wcscpy(szOut,szIn);
return;
}
//else
// printf("Found an &:\n%s\n",szIn);
*q='\0';
- strcpy(szOut,szIn);
+ wcscpy(szOut,szIn);
q++;
- if ( !strncmp("amp;",q,4) )
+ if ( !wcsncmp((wchar_t *)"amp;",q,4) )
{
- strcat(szOut,"&");
+ wcscat(szOut,(wchar_t *)"&");
q+=4;
- strcat(szOut,q);
+ wcscat(szOut,q);
}
- else if ( !strncmp("nbsp;",q,5) )
+ else if ( !wcsncmp((wchar_t *)"nbsp;",q,5) )
{
- strcat(szOut," ");
+ wcscat(szOut,(wchar_t *)" ");
q+=5;
- strcat(szOut,q);
+ wcscat(szOut,q);
}
else
{
- strcat(szOut,"&");
- strcat(szOut,q);
+ wcscat(szOut,(wchar_t *)"&");
+ wcscat(szOut,q);
}
}
diff --git a/tools/doc-publican-rpm/doc-publican-rpm.h b/tools/doc-publican-rpm/doc-publican-rpm.h
index 69192ae..b3e3155 100644
--- a/tools/doc-publican-rpm/doc-publican-rpm.h
+++ b/tools/doc-publican-rpm/doc-publican-rpm.h
@@ -4,9 +4,9 @@ EXTERN struct
//! ISO code for the language
char szLang[16];
//! Document title in local language
- char szTitle[128];
+ wchar_t szTitle[128];
//! Document subtitle in local language
- char szSubtitle[512];
+ wchar_t szSubtitle[512];
} rcConvInfo[50];
//! Version number of the produced rpm
@@ -41,4 +41,4 @@ void makeDesktopFile( char * );
void makeIndexFile( char * );
void makeTarFile( void );
void makeSpecFile( void );
-void cleanString( char *, char * );
+void cleanString( wchar_t *, wchar_t * );
diff --git a/tools/doc-publican-rpm/makeDesktopFile.c b/tools/doc-publican-rpm/makeDesktopFile.c
index f805479..60be473 100644
--- a/tools/doc-publican-rpm/makeDesktopFile.c
+++ b/tools/doc-publican-rpm/makeDesktopFile.c
@@ -49,7 +49,7 @@ void makeDesktopFile( char *szDir )
FILE *f;
int i;
char szCLang[16];
- char szTextString[1024];
+ wchar_t szTextString[1024];
// Make the Gnome file
strcpy(szFilename,szDir);
@@ -69,23 +69,23 @@ void makeDesktopFile( char *szDir )
// desktop-file-validate doesn't like this
// fprintf(f,"Encoding=UTF-8\n");
cleanString(rcConvInfo[0].szTitle,szTextString);
- fprintf(f,"Name=%s\n",szTextString);
+ fprintf(f,"Name=%S\n",szTextString);
for ( i=1; i<nEntry; i++ )
{
cvtLang(rcConvInfo[i].szLang ,szCLang);
cleanString(rcConvInfo[i].szTitle,szTextString);
- fprintf(f,"Name[%s]=%s\n",
+ fprintf(f,"Name[%S]=%s\n",
szCLang,szTextString);
}
cleanString(rcConvInfo[0].szTitle,szTextString);
- fprintf(f,"GenericName=%s\n",szTextString);
+ fprintf(f,"GenericName=%S\n",szTextString);
cleanString(rcConvInfo[0].szSubtitle,szTextString);
- fprintf(f,"Comment=%s\n",szTextString);
+ fprintf(f,"Comment=%S\n",szTextString);
for ( i=1; i<nEntry; i++ )
{
cvtLang(rcConvInfo[i].szLang ,szCLang);
cleanString(rcConvInfo[i].szSubtitle,szTextString);
- fprintf(f,"Comment[%s]=%s\n",
+ fprintf(f,"Comment[%S]=%s\n",
szCLang,szTextString);
}
// BZ684546 Changed from htmlview to xdg-open
1
0
commit 17f33cb83459a9037d3a3dd4d6f5c3ddc5b193df
Author: John J. McDonough <jjmcd(a)fedoraproject.org>
Date: Mon Sep 22 10:47:38 2014 -0400
Automatic update
680620.patch | 107 ----------------------------------------------------------
1 files changed, 0 insertions(+), 107 deletions(-)
1
0
[install-guide/F21-rewrite] Added all Kickstart commands to reference except OSTree
by pbokoc 18 Sep '14
by pbokoc 18 Sep '14
18 Sep '14
commit f0af8f85cf728abd0fd15e8f20dd7776055c3ec8
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Thu Sep 18 18:10:56 2014 +0200
Added all Kickstart commands to reference except OSTree
en-US/Kickstart_Syntax_Reference.xml | 2908 +++++++++++++++++++++++++++-------
1 files changed, 2293 insertions(+), 615 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index 229ebc7..68580b4 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -81,7 +81,7 @@
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>
+<command>driverdisk <replaceable>partition</replaceable> | --source= | --biospart=</command>
</programlisting>
<variablelist>
<varlistentry>
@@ -126,199 +126,199 @@
<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:
- </para>
- <programlisting>
+ 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:
+ </para>
+ <programlisting>
<command>install</command>
<command>liveimg --url=file:///images/install/squashfs.img --noverifyssl</command>
- </programlisting>
- <para>
- The installation method commands are:
- </para>
- <variablelist>
- <varlistentry>
- <term><command>cdrom</command></term>
- <listitem>
- <para>
- Install from the first optical (DVD) drive on the system.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>harddrive</command></term>
- <listitem>
- <para>
- Install from a tree or full installation ISO image on a local hard drive. The tree or ISO image must be on a file system which is mountable in the installation environment. Supported file systems are <systemitem>ext2</systemitem>, <systemitem>ext3</systemitem>, <systemitem>ext4</systemitem>, <systemitem>vfat</systemitem>, or <systemitem>xfs</systemitem>.
- </para>
- <programlisting>
+ </programlisting>
+ <para>
+ The installation method commands are:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><command>cdrom</command></term>
+ <listitem>
+ <para>
+ Install from the first optical (DVD) drive on the system.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><command>harddrive</command></term>
+ <listitem>
+ <para>
+ Install from a tree or full installation ISO image on a local hard drive. The tree or ISO image must be on a file system which is mountable in the installation environment. Supported file systems are <systemitem>ext2</systemitem>, <systemitem>ext3</systemitem>, <systemitem>ext4</systemitem>, <systemitem>vfat</systemitem>, or <systemitem>xfs</systemitem>.
+ </para>
+ <programlisting>
<command>install</command>
<command>harddrive --partition= | --biospart= [--dir=]</command>
- </programlisting>
- <variablelist>
- <varlistentry>
- <term><option>--partition=</option></term>
- <listitem>
- <para>
- Partition to install from (such as <literal>sdb2</literal>).
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--biospart=</option></term>
- <listitem>
- <para>
- BIOS partition to install from (such as <literal>82p2</literal>).
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--dir=</option></term>
- <listitem>
- <para>
- Directory containing the installation tree or ISO image.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>liveimg</command></term>
- <listitem>
- <para>
- 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>
- <programlisting>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--partition=</option></term>
+ <listitem>
+ <para>
+ Partition to install from (such as <literal>sdb2</literal>).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--biospart=</option></term>
+ <listitem>
+ <para>
+ BIOS partition to install from (such as <literal>82p2</literal>).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--dir=</option></term>
+ <listitem>
+ <para>
+ Directory containing the installation tree or ISO image.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><command>liveimg</command></term>
+ <listitem>
+ <para>
+ 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>
+ <programlisting>
<command>install</command>
<command>liveimg --url= [--proxy= | --checksum= | --noverifyssl=]</command>
- </programlisting>
- <variablelist>
- <varlistentry>
- <term><option>--url=</option></term>
- <listitem>
- <para>
- The location to install from. Supported protocols are <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem>, <systemitem class="protocol">FTP</systemitem>, and <systemitem class="protocol">file</systemitem>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--proxy=</option></term>
- <listitem>
- <para>
- Specify an <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem> or <systemitem class="protocol">FTP</systemitem> proxy to use while performing the installation.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--checksum=</option></term>
- <listitem>
- <para>
- An optional argument with the <systemitem>SHA256</systemitem> checksum of the image file, used for integrity verification. If you are using a live image provided by Fedora Project, you can find a list of checksums at <ulink url="https://fedoraproject.org/en/verify" />.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--noverifyssl</option></term>
- <listitem>
- <para>
- Disable SSL verification when connecting to an <systemitem class="protocol">HTTPS</systemitem> server.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>nfs</command></term>
- <listitem>
- <para>
- Install from an <systemitem class="protocol">NFS</systemitem> server specified. <remark>TODO: link to the PXE chapter's section on preparing install source on nfs</remark>
- </para>
- <programlisting>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--url=</option></term>
+ <listitem>
+ <para>
+ The location to install from. Supported protocols are <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem>, <systemitem class="protocol">FTP</systemitem>, and <systemitem class="protocol">file</systemitem>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--proxy=</option></term>
+ <listitem>
+ <para>
+ Specify an <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem> or <systemitem class="protocol">FTP</systemitem> proxy to use while performing the installation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--checksum=</option></term>
+ <listitem>
+ <para>
+ An optional argument with the <systemitem>SHA256</systemitem> checksum of the image file, used for integrity verification. If you are using a live image provided by Fedora Project, you can find a list of checksums at <ulink url="https://fedoraproject.org/en/verify" />.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--noverifyssl</option></term>
+ <listitem>
+ <para>
+ Disable SSL verification when connecting to an <systemitem class="protocol">HTTPS</systemitem> server.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><command>nfs</command></term>
+ <listitem>
+ <para>
+ Install from an <systemitem class="protocol">NFS</systemitem> server specified. <remark>TODO: link to the PXE chapter's section on preparing install source on nfs</remark>
+ </para>
+ <programlisting>
<command>install</command>
<command>nfs --server= [--dir=] [--opts= ]</command>
- </programlisting>
- <variablelist>
- <varlistentry>
- <term><option>--server=</option></term>
- <listitem>
- <para>
- Host name of the server.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--dir=</option></term>
- <listitem>
- <para>
- Directory containing the installation tree or ISO image.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--opts=</option></term>
- <listitem>
- <para>
- Mount options to use for mounting the <systemitem class="protocol">NFS</systemitem> export.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>url</command></term>
- <listitem>
- <para>
- Install from a tree on a remote server via <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem>, or <systemitem class="protocol">FTP</systemitem>.
- </para>
- <programlisting>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--server=</option></term>
+ <listitem>
+ <para>
+ Host name of the server.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--dir=</option></term>
+ <listitem>
+ <para>
+ Directory containing the installation tree or ISO image.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--opts=</option></term>
+ <listitem>
+ <para>
+ Mount options to use for mounting the <systemitem class="protocol">NFS</systemitem> export.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><command>url</command></term>
+ <listitem>
+ <para>
+ Install from a tree on a remote server via <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem>, or <systemitem class="protocol">FTP</systemitem>.
+ </para>
+ <programlisting>
<command>install</command>
<command>url --url= | --mirrorlist= [--proxy= | --noverifyssl]</command>
- </programlisting>
- <variablelist>
- <varlistentry>
- <term><option>--url=</option></term>
- <listitem>
- <para>
- The location to install from. Supported protocols are <literal>http</literal>, <literal>https</literal>, <literal>ftp</literal>, and <literal>file</literal>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--mirrorlist=</option></term>
- <listitem>
- <para>
- The mirror URL to install from.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--proxy=</option></term>
- <listitem>
- <para>
- Specify an <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem> or <systemitem class="protocol">FTP</systemitem> proxy to use while performing the installation.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--noverifyssl</option></term>
- <listitem>
- <para>
- Disable SSL verification when connecting to an <systemitem>HTTPS</systemitem> server.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </listitem>
- </varlistentry>
- </variablelist>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--url=</option></term>
+ <listitem>
+ <para>
+ The location to install from. Supported protocols are <literal>http</literal>, <literal>https</literal>, <literal>ftp</literal>, and <literal>file</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--mirrorlist=</option></term>
+ <listitem>
+ <para>
+ The mirror URL to install from.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--proxy=</option></term>
+ <listitem>
+ <para>
+ Specify an <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem> or <systemitem class="protocol">FTP</systemitem> proxy to use while performing the installation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--noverifyssl</option></term>
+ <listitem>
+ <para>
+ Disable SSL verification when connecting to an <systemitem>HTTPS</systemitem> server.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-mediacheck">
- <title>mediacheck - Verify Installation Media Integrity</title>
+ <title>mediacheck (optional) - Verify Installation Media Integrity</title>
<para>
- text
+ This command will force the installation program to perform a media check before starting the installation, similarly to the <option>rd.live.check</option> boot option (see <xref linkend="sect-boot-options-mediacheck" />. This command requires that installations be attended, so it is disabled by default.
</para>
</section>
@@ -330,10 +330,95 @@
</section>
<section id="sect-kickstart-commands-repo">
- <title>repo - Configure Instalaltion Source</title>
+ <title>repo (optional) - Configure Additional Yum Repositories</title>
<para>
- text
+ Configures additional <application>Yum</application> repositories that may be used as sources for package installation. This command can be used multiple times in a single Kickstart file.
</para>
+ <programlisting>
+<command>repo --name=<replaceable>repoid</replaceable> [--baseurl=<replaceable><url></replaceable>|--mirrorlist=<replaceable>url</replaceable>] [<replaceable>options</replaceable>]</command>
+ </programlisting>
+ <para>
+ See the <citetitle>Fedora System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">Fedora Documentation</ulink>, for information about the <application>Yum</application> package manager.
+ </para>
+ <important>
+ <para>
+ Repositories used for installation must be stable. The installation may fail if a repository is modified before the installation concludes.
+ </para>
+ </important>
+ <variablelist>
+ <varlistentry>
+ <term><option>--name=</option></term>
+ <listitem>
+ <para>
+ The repository ID. This option is required. If a repository has a name which conflicts with another previously added repository, it will be ignored. Because the installation program uses a list of pre-configured repositories, this means that you cannot add repositories with the same names as the preconfigured ones.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--baseurl=</option></term>
+ <listitem>
+ <para>
+ The repository URL. The variables that may be used in <application>Yum</application> repo configuration files are <emphasis>not</emphasis> supported. You may use one of either this option or <option>--mirrorlist</option>, not both.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--mirrorlist=</option></term>
+ <listitem>
+ <para>
+ The URL pointing at a list of mirrors for the repository. The variables that may normally be used in yum repository configuration files are not supported here. You may use one of either this option or --baseurl, not both.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--cost=</option></term>
+ <listitem>
+ <para>
+ An integer value to assign a cost to this repository. If multiple repositories provide the same packages, this number will be used to prioritize which repository will be used before another. Repositories with a lower cost take priority over repositories with higher cost.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--excludepkgs=</option></term>
+ <listitem>
+ <para>
+ A comma-separated list of package names that must <emphasis>not</emphasis> be pulled from this repository. This is useful if multiple repositories provide the same package and you want to make sure it comes from a particular repository. Both full package names (such as <literal>publican</literal>) and globs (such as <literal>gnome-*</literal>) are accepted.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--includepkgs=</option></term>
+ <listitem>
+ <para>
+ A comma-separated list of package names and globs that must be pulled from this repository. This is useful if multiple repositories provide the same package and you want to make sure it comes from this repository.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--proxy=</option></term>
+ <listitem>
+ <para>
+ Specify an <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem> or <systemitem class="protocol">FTP</systemitem> proxy server to use when accessing this repository. This setting does not affect any other repositories or installation sources.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--ignoregroups=true</option></term>
+ <listitem>
+ <para>
+ This option is used when composing installation trees and has no effect on the installation process itself. It tells the compose tools to not look at the package group information when mirroring trees so as to avoid mirroring large amounts of unnecessary data.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--noverifyssl</option></term>
+ <listitem>
+ <para>
+ Disable SSL verification when connecting to an <systemitem class="protocol">HTTPS</systemitem> server.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
</section>
@@ -776,7 +861,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>
@@ -811,7 +896,7 @@
</section>
<section id="sect-kickstart-commands-ignoredisk">
- <title>ignoredisk - Ignore Specified Disks</title>
+ <title>ignoredisk (optional) - Ignore Specified Disks</title>
<para>
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>
@@ -884,354 +969,1587 @@
<section id="sect-kickstart-commands-iscsi">
<title>iscsi (optional) - Configure iSCSI Devices</title>
<para>
- Specifies additional iSCSI storage to be attached during installation. If you use the <command>iscsi</command> command, you must also assign a name to the iSCSI node, using the <command>iscsiname</command> command (see <xref linkend="sect-kickstart-commands-iscsiname" />. The <command>iscsiname</command> command must appear before the <command>iscsi</command> command in the Kickstart file.
- </para>
- <para>
- You should configure iSCSI storage in the system BIOS or firmware (iBFT for Intel systems) rather than use the <command>iscsi</command> command if possible. If you do so, <application>Anaconda</application> automatically detects and uses disks configured in BIOS or firmware and no special configuration is necessary in the Kickstart file.
- </para>
- <para>
- If you must use the <command>iscsi</command> command, make sure that networking is activated at the beginning of the installation, and that the <command>iscsi</command> command appears in the Kickstart file <emphasis>before</emphasis> you refer to iSCSI disks with commands such as <command>clearpart</command> or <command>ignoredisk</command>.
- </para>
- <programlisting>
-<command>iscsi --ipaddr= --port= [--target= | --iface= | --user= | --password= | --reverse-user= | --reverse-password=]</command>
- </programlisting>
- <variablelist>
- <varlistentry>
- <term><option>--ipaddr=</option></term>
- <listitem>
- <para>
- The IP address of the target to connect to.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--port=</option></term>
- <listitem>
- <para>
- The port number (typically <literal>3260</literal>).
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--target=</option></term>
- <listitem>
- <para>
- Target <firstterm>IQN</firstterm> (iSCSI Qualified Name).
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--iface=</option></term>
- <listitem>
- <para>
- Bind the connection to a specific network interface instead of using the default one determined by the network layer. Once used, it must be specified in all instances of the <command>iscsi</command> command in the entire Kickstart file.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--user=</option></term>
- <listitem>
- <para>
- User name required to authenticate with the target.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--password=</option></term>
- <listitem>
- <para>
- Password that corresponds with the user name specified for the target.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--reverse-user=</option></term>
- <listitem>
- <para>
- User name required to authenticate with the initiator from a target using reverse CHAP authentication.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--reverse-password=</option></term>
- <listitem>
- <para>
- Password that corresponds with the user name specified for the initiator.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
-
- <section id="sect-kickstart-commands-iscsiname">
- <title>iscsiname (optional) - Assign Name to iSCSI Device</title>
- <para>
- Assigns a name to an iSCSI node specified by the <command>iscsi</command> command (<xref linkend="sect-kickstart-commands-iscsi" />). This command is mandatory if you use the <command>iscsi</command> command, and it must be specified <emphasis>before</emphasis> you use <command>iscsi</command>.
- </para>
- <programlisting>
-<command>iscsiname <replaceable>iqn</replaceable></command>
- </programlisting>
- </section>
-
- <section id="sect-kickstart-commands-logvol">
- <title>logvol - Create LVM Logical Volume</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-kickstart-commands-part">
- <title>part - Create Physical Partition</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-kickstart-commands-raid">
- <title>raid - Create Software RAID</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-kickstart-commands-volgroup">
- <title>volgroup - Create LVM Volume Group</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-kickstart-commands-zerombr">
- <title>zerombr - Reinitialize Partition Tables</title>
- <para>
- text
+ Specifies additional iSCSI storage to be attached during installation. If you use the <command>iscsi</command> command, you must also assign a name to the iSCSI node, using the <command>iscsiname</command> command (see <xref linkend="sect-kickstart-commands-iscsiname" />. The <command>iscsiname</command> command must appear before the <command>iscsi</command> command in the Kickstart file.
</para>
- </section>
-
- <section id="sect-kickstart-commands-zfcp">
- <title>zfcp - Configure Fibre Channel Device</title>
<para>
- text
+ You should configure iSCSI storage in the system BIOS or firmware (iBFT for Intel systems) rather than use the <command>iscsi</command> command if possible. If you do so, <application>Anaconda</application> automatically detects and uses disks configured in BIOS or firmware and no special configuration is necessary in the Kickstart file.
</para>
- </section>
-
- </section>
-
- <section id="sect-kickstart-commands-network-configuration">
- <title>Network Configuration</title>
- <para>
- Commands in this chapter are used for network configuration.
- </para>
-
- <section id="sect-kickstart-commands-firewall">
- <title>firewall (optional) - Configure Firewall</title>
<para>
- Specify the firewall configuration for the installed system. <remark>TODO: link to the Firewall guide once we have one</remark>
+ If you must use the <command>iscsi</command> command, make sure that networking is activated at the beginning of the installation, and that the <command>iscsi</command> command appears in the Kickstart file <emphasis>before</emphasis> you refer to iSCSI disks with commands such as <command>clearpart</command> or <command>ignoredisk</command>.
</para>
<programlisting>
-<command>firewall --enabled | --disabled <replaceable>device</replaceable> [--trust= | --ssh | --smtp | --http | --ftp | --port= | --service=]</command>
+<command>iscsi --ipaddr= --port= [--target= | --iface= | --user= | --password= | --reverse-user= | --reverse-password=]</command>
</programlisting>
<variablelist>
<varlistentry>
- <term><option>--enabled</option> or <option>--enable</option></term>
+ <term><option>--ipaddr=</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.
+ The IP address of the target to connect to.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--disabled</option> or <option>--disable</option></term>
+ <term><option>--port=</option></term>
<listitem>
<para>
- Disable the firewall.
+ The port number (typically <literal>3260</literal>).
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--trust=</option></term>
+ <term><option>--target=</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:
+ Target <firstterm>IQN</firstterm> (iSCSI Qualified Name).
</para>
- <programlisting>
-<command>firewall --enable --trust=em1 --trust=em2</command>
- </programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--iface=</option></term>
+ <listitem>
<para>
- Do not use a comma-separated format such as <option>--trust em1, em2</option>.
+ Bind the connection to a specific network interface instead of using the default one determined by the network layer. Once used, it must be specified in all instances of the <command>iscsi</command> command in the entire Kickstart file.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><replaceable>incoming</replaceable></term>
+ <term><option>--user=</option></term>
<listitem>
<para>
- Replace with one or more of the following to allow the specified services through the firewall:
+ User name required to authenticate with the target.
</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>
+ <term><option>--password=</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.
+ Password that corresponds with the user name specified for the target.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--service=</option></term>
+ <term><option>--reverse-user=</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.
+ User name required to authenticate with the initiator from a target using reverse CHAP authentication.
</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--reverse-password=</option></term>
+ <listitem>
<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.
+ Password that corresponds with the user name specified for the initiator.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
- <section id="sect-kickstart-commands-network">
- <title>network - Configure Network Interfaces</title>
- <para>
- text
- </para>
- </section>
-
- </section>
-
- <section id="sect-kickstart-commands-environment">
- <title>Console and Environment</title>
- <para>
- The following commands control the environment of the system after the installation finishes - language, keyboard layouts, or the graphical interface.
- </para>
-
- <section id="sect-kickstart-commands-keyboard">
- <title>keyboard (optional) - Configure Keyboard Layouts</title>
- <para>
- Sets one or more available keyboard layouts for the system.
- </para>
- <programlisting>
-<command>keyboard --vckeymap= | --xlayouts= [--switch=]</command>
- </programlisting>
- <variablelist>
- <varlistentry>
- <term><option>--vckeymap=</option></term>
- <listitem>
- <para>
- Specify a <systemitem>VConsole</systemitem> keymap which should be used. Valid names correspond to the list of files in the <filename class="directory">/usr/lib/kbd/keymaps/*</filename> directory, without the <literal>.map.gz</literal> extension.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--xlayouts=</option></term>
- <listitem>
- <para>
- Specify a list of <application>X</application> layouts that should be used as a comma-separated list without spaces. Accepts values in the same format as <systemitem>setxkbmap(1)</systemitem>, either in the <literal><replaceable>layout</replaceable></literal> format (such as <literal>cz</literal>), or in the <literal><replaceable>layout</replaceable> (<replaceable>variant</replaceable>)</literal> format (such as <literal>cz (qwerty)</literal>).
- </para>
- <para>
- All available layouts can be viewed on the <systemitem>xkeyboard-config(7)</systemitem> man page under <literal>Layouts</literal>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--switch=</option></term>
- <listitem>
- <para>
- Specify a list of layout-switching options (shortcuts for switching between multiple keyboard layouts). Multiple options must be separated by commas without spaces. Accepts values in the same format as <systemitem>setxkbmap(1)</systemitem>.
- </para>
- <para>
- Available switching options can be viewed on the <systemitem>xkeyboard-config(7)</systemitem> man page under <literal>Options</literal>.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>
- The following example sets up two keyboard layouts (<literal>English (US)</literal> and <literal>Czech (qwerty)</literal>) using the <option>--xlayouts=</option> option, and allows to switch between them using <keycombo><keycap>Alt</keycap><keycap>Shift</keycap></keycombo>:
- </para>
- <programlisting>
-<command>keyboard --xlayouts=us,'cz (qwerty)' --switch=grp:alt_shift_toggle</command>
- </programlisting>
- </section>
-
- <section id="sect-kickstart-commands-lang">
- <title>lang (optional) - Configure Language During Installation</title>
- <para>
- Sets the language to use during installation and the default language to use on the installed system.
- </para>
- <programlisting>
-<command>lang <replaceable>language</replaceable> [--addsupport=]</command>
- </programlisting>
- <para>
- The file <filename>/usr/share/system-config-language/locale-list</filename> provides a list of the valid <replaceable>language</replaceable> codes in the first column of each line and is part of the <package>system-config-language</package> package.
- </para>
- <para>
- Certain languages (for example, Chinese, Japanese, Korean, and Indic languages) are not supported during text-mode installation. If you specify one of these languages with the <command>lang</command> command and use text mode, the installation process will continue in English, but the installed system will use your selection as its default language.
- </para>
- <variablelist>
- <varlistentry>
- <term><option>--addsupport=</option></term>
- <listitem>
- <para>
- Add support for additional languages. Takes the form of comma-separated list without spaces. For example:
- </para>
- <programlisting>
-<command>lang en_US --addsupport=cs_CZ,de_DE,en_UK</command>
- </programlisting>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
-
- <section id="sect-kickstart-commands-services">
- <title>services - Configure Services</title>
+ <section id="sect-kickstart-commands-iscsiname">
+ <title>iscsiname (optional) - Assign Name to iSCSI Device</title>
<para>
- text
+ Assigns a name to an iSCSI node specified by the <command>iscsi</command> command (<xref linkend="sect-kickstart-commands-iscsi" />). This command is mandatory if you use the <command>iscsi</command> command, and it must be specified <emphasis>before</emphasis> you use <command>iscsi</command>.
</para>
+ <programlisting>
+<command>iscsiname <replaceable>iqn</replaceable></command>
+ </programlisting>
</section>
- <section id="sect-kickstart-commands-skipx">
- <title>skipx - Do Not Configure X Window System</title>
+ <section id="sect-kickstart-commands-logvol">
+ <title>logvol (optional) - Create LVM Logical Volume</title>
<para>
- text
+ Create a logical volume for Logical Volume Management (LVM) with the syntax:
</para>
- </section>
-
- <section id="sect-kickstart-commands-timezone">
- <title>timezone - Configure Time Zone</title>
+ <programlisting>
+<command>logvol <replaceable>mntpoint</replaceable> --vgname= --name= [<replaceable>options</replaceable>]</command>
+ </programlisting>
+ <note>
+ <para>
+ Do not use the dash (<literal>-</literal>) character in logical volume and volume group names when installing &PRODUCT; using Kickstart. If this character is used, the installation will finish normally, but the <filename class="directory">/dev/mapper/</filename> directory will list these volumes and volume groups with every dash doubled. For example, a volume group named <literal>volgrp-01</literal> containing a logical volume named <literal>logvol-01</literal> will be listed as <filename>/dev/mapper/volgrp--01-logvol--01</filename>.
+ </para>
+ <para>
+ This limitation only applies to newly created logical volume and volume group names. If you are reusing existing ones using the <option>--noformat</option> or <option>--useexisting</option> option, their names will not be changed.
+ </para>
+ </note>
<para>
- text
+ For a detailed example of <command>logvol</command> in action, see <xref linkend="sect-kickstart-example-advanced-partitioning" />.
</para>
- </section>
-
- <section id="sect-kickstart-commands-xconfig">
- <title>xconfig - Configure X Window System</title>
- <para>
- text
+ <variablelist>
+ <varlistentry>
+ <term><replaceable>mntpoint</replaceable></term>
+ <listitem>
+ <para>
+ Replace with the volume's mount point. This name can take the following forms:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><filename>/<replaceable>path</replaceable></filename></term>
+ <listitem>
+ <para>
+ A path to the mount point - for example, <literal>/</literal> or <literal>/home</literal>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>swap</literal></term>
+ <listitem>
+ <para>
+ The partition is used as swap space.
+ </para>
+ <para>
+ To determine the size of the swap partition automatically, use the <option>--recommended</option> option:
+ </para>
+ <programlisting>
+<literal>swap --recommended</literal>
+ </programlisting>
+ <para>
+ The size assigned will be effective but not precisely calibrated for your system.
+ </para>
+ <para>
+ To determine the size of the swap partition automatically but also allow extra space for your system to hibernate, use the <option>--hibernation</option> option:
+ </para>
+ <programlisting>
+<literal>swap--hibernation</literal>
+ </programlisting>
+ <para>
+ The size assigned will be equivalent to the swap space assigned by <option>--recommended</option> plus the amount of RAM on your system.
+ </para>
+ <para>
+ For the swap sizes assigned by these commands, see <remark>todo: xref to a section about swap sizes</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>none</literal></term>
+ <listitem>
+ <para>
+ Used only when creating a thin pool volume.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--noformat</option></term>
+ <listitem>
+ <para>
+ Use an existing logical volume and do not format it.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--useexisting</option></term>
+ <listitem>
+ <para>
+ Use an existing logical volume and format it.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--fstype=</option></term>
+ <listitem>
+ <para>
+ Sets the file system type for the logical volume. Valid values are <literal>xfs</literal>, <literal>ext2</literal>, <literal>ext3</literal>, <literal>ext4</literal>, <literal>swap</literal>, and <literal>vfat</literal>. For information about file system types, see <remark>TODO: xref to info about fs types</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--fsoptions=</option></term>
+ <listitem>
+ <para>
+ Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the <filename>/etc/fstab</filename> file of the installed system and should be enclosed in quotes. For example:
+ </para>
+ <programlisting>
+<option>--fsoptions="ro, x-systemd.device-timeout=0"</option>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--label=</option></term>
+ <listitem>
+ <para>
+ Sets a label for the logical volume.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--grow</option></term>
+ <listitem>
+ <para>
+ Grow the volume to fill available space (if any), or up to the limit set by the <option>--maxsize=</option> option.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--size=</option></term>
+ <listitem>
+ <para>
+ The minimum size of the logical volume in megabytes. This option is mandatory when creating a new logical volume, and optional if you are reusing an existing logical volume using the <option>--useexisting</option> or <option>--noformat</option> option.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--maxsize=</option></term>
+ <listitem>
+ <para>
+ The maximum size in megabytes when the logical volume is set to grow. Specify an integer value here such as <literal>500</literal> (do not include the unit).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--recommended</option></term>
+ <listitem>
+ <para>
+ Determine the size of the logical volume automatically. For details about the recommended scheme, see <remark>TODO: xref to section with partitioning recommendations</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--resize</option></term>
+ <listitem>
+ <para>
+ Resize an existing logical volume. If you use this option, you must also specify <option>--useexisting</option> and <option>--size</option>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--percent=</option></term>
+ <listitem>
+ <para>
+ Specify the amount by which to grow the logical volume, as a percentage of the free space in the volume group after any statically-sized logical volumes are taken into account. This option must be used in conjunction with the <option>--size</option> and <option>--grow</option> options.
+ </para>
+ </listitem>
+ </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.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--passphrase=</option></term>
+ <listitem>
+ <para>
+ Specifies the passphrase to use when encrypting this logical volume. You must use this option together with the <option>--encrypted</option> option. This option has no effect by itself.
+ </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>
+ <varlistentry>
+ <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.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--backuppassphrase</option></term>
+ <listitem>
+ <para>
+ Add 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>--thinpool</option></term>
+ <listitem>
+ <para>
+ Creates a thin pool logical volume. (Use a mount point of <literal>none</literal>)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--metadatasize=</option></term>
+ <listitem>
+ <para>
+ Metadata area size (in MiB) for a new thin pool device.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--chunksize=</option></term>
+ <listitem>
+ <para>
+ Chunk size (in KiB) for a new thin pool device.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--thin</option></term>
+ <listitem>
+ <para>
+ Create a thin logical volume. (Requires use of <option>--poolname</option>)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--poolname=</option></term>
+ <listitem>
+ <para>
+ Specify the name of the thin pool in which to create a thin logical volume. Requires the <option>--thin</option> option.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ Create one or more partitions first using <xref linkend="sect-kickstart-commands-part" />, create the logical volume group (<xref linkend="sect-kickstart-commands-volgroup" />), and then create logical volumes. For example:
+ </para>
+ <programlisting>
+<command>part pv.01 --size 3000</command>
+<command>volgroup myvg pv.01</command>
+<command>logvol / --vgname=myvg --size=2000 --name=rootvol</command>
+ </programlisting>
+ </section>
+
+ <section id="sect-kickstart-commands-part">
+ <title>part (required) - Create Physical Partition</title>
+ <para>
+ Creates a partition on the system.
+ </para>
+ <para>
+ For a detailed example of <command>part</command> in action, see <xref linkend="sect-kickstart-example-advanced-partitioning" />.
+ </para>
+ <programlisting>
+<command>part|partition <replaceable>mntpoint</replaceable> --name=<replaceable>name</replaceable> --device=<replaceable>device</replaceable> --rule=<replaceable>rule</replaceable> [<replaceable>options</replaceable>]</command>
+ </programlisting>
+ <warning>
+ <para>
+ All partitions created are formatted as part of the installation process unless <option>--noformat</option> and <option>--onpart=</option> are used.
+ </para>
+ </warning>
+ <note>
+ <para>
+ If partitioning fails for any reason, diagnostic messages appear on virtual console 3.
+ </para>
+ </note>
+ <variablelist>
+ <varlistentry>
+ <term><replaceable>mntpoint</replaceable></term>
+ <listitem>
+ <para>
+ Where the partition is mounted. The value must be of one of the following:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><filename>/<replaceable>path</replaceable></filename></term>
+ <listitem>
+ <para>
+ A path to the mount point - for example, <literal>/</literal> or <literal>/home</literal>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>swap</literal></term>
+ <listitem>
+ <para>
+ The partition is used as swap space.
+ </para>
+ <para>
+ To determine the size of the swap partition automatically, use the <option>--recommended</option> option:
+ </para>
+ <programlisting>
+<literal>swap --recommended</literal>
+ </programlisting>
+ <para>
+ The size assigned will be effective but not precisely calibrated for your system.
+ </para>
+ <para>
+ To determine the size of the swap partition automatically but also allow extra space for your system to hibernate, use the <option>--hibernation</option> option:
+ </para>
+ <programlisting>
+<literal>swap--hibernation</literal>
+ </programlisting>
+ <para>
+ The size assigned will be equivalent to the swap space assigned by <option>--recommended</option> plus the amount of RAM on your system.
+ </para>
+ <para>
+ For the swap sizes assigned by these commands, see <remark>todo: xref to a section about swap sizes</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>raid.<replaceable>id</replaceable></literal></term>
+ <listitem>
+ <para>
+ The partition is used for software RAID (see <command>raid</command>).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>pv.<replaceable>id</replaceable></literal></term>
+ <listitem>
+ <para>
+ The partition is used for LVM (see <xref linkend="sect-kickstart-commands-part" />).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>biosboot</literal></term>
+ <listitem>
+ <para>
+ The partition will be used for a BIOS Boot partition. A 1 MB BIOS boot partition is necessary on BIOS-based systems using a <firstterm>GUID Partition Table</firstterm> (GPT); the boot loader will be installed into it. It is not necessary on UEFI systems. Also see <xref linkend="sect-kickstart-commands-part" />.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>efi</literal></term>
+ <listitem>
+ <para>
+ An EFI System Partition. An EFI partition at least 50 MB in size is necessary on UEFI-based systems; the recommended size is 200 MB. It is not necessary on BIOS systems. Also see <xref linkend="sect-kickstart-commands-part" />.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--size=</option></term>
+ <listitem>
+ <para>
+ The minimum partition size in megabytes. Specify an integer value here such as <literal>500</literal> (do not include the unit).
+ </para>
+ <important>
+ <para>
+ If the <option>--size</option> value is too small, the installation will fail. Set the <option>--size</option> value as the minimum amount of space you require. For size recommendations, see <remark>TODO: xref to recommended partitioning scheme</remark>.
+ </para>
+ </important>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--maxsize=</option></term>
+ <listitem>
+ <para>
+ The maximum partition size in megabytes when the partition is set to grow. Specify an integer value here such as <literal>500</literal> (do not include the unit).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--resize</option></term>
+ <listitem>
+ <para>
+ Resize an existing partition. When using this option, specify the new size (in megabytes) using the <option>--size=</option> option and the target partition using the <option>--onpart=</option> option.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--grow</option></term>
+ <listitem>
+ <para>
+ Tells the partition to grow to fill available space (if any), or up to the maximum size setting.
+ </para>
+ <note>
+ <para>
+ If you use <option>--grow=</option> without setting <option>--maxsize=</option> on a swap partition, <application>Anaconda</application> will limit the maximum size of the swap partition. For systems that have less than 2 GB of physical memory, the imposed limit is twice the amount of physical memory. For systems with more than 2 GB, the imposed limit is the size of physical memory plus 2 GB.
+ </para>
+ </note>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--noformat</option></term>
+ <listitem>
+ <para>
+ Specifies that the partition should not be formatted, for use with the <option>--onpart</option> command.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--onpart=</option> or <option>--usepart=</option></term>
+ <listitem>
+ <para>
+ Specifies the device on which to place the partition. For example:
+ </para>
+ <programlisting>
+<command>partition /home --onpart=hda1</command>
+ </programlisting>
+ <para>
+ The above puts <filename>/home</filename> on <filename>/dev/hda1</filename>.
+ </para>
+ <para>
+ These options can also add a partition to a logical volume. For example:
+ </para>
+ <programlisting>
+<command>partition pv.1 --onpart=hda2</command>
+ </programlisting>
+ <para>
+ The device must already exist on the system; the <option>--onpart</option> option will not create it.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--ondisk=</option> or <option>--ondrive=</option></term>
+ <listitem>
+ <para>
+ Forces the partition to be created on a particular disk. For example, <option>--ondisk=sdb</option> puts the partition on the second SCSI disk on the system.
+ </para>
+ <para>
+ To specify 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 specify a disk with WWID <literal>2416CD96995134CA5D787F00A5AA11017</literal>, use:
+ </para>
+ <programlisting>
+<command>part / --fstype=xfs --grow --asprimary --size=8192 --ondisk=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 specify 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 specify a disk with WWID <literal>58095BEC5510947BE8C0360F604351918</literal>, use:
+ </para>
+ <programlisting>
+<command>part / --fstype=xfs --grow --asprimary --size=8192 --ondisk=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>--asprimary</option></term>
+ <listitem>
+ <para>
+ Forces the partition to be allocated as a <emphasis>primary</emphasis> partition. If the partition cannot be allocated as primary (usually due to too many primary partitions being already allocated), the partitioning process will fail. For information about primary partitions, see <remark>TODO: xref to an appendix about partitions or something like that</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--fsprofile=</option></term>
+ <listitem>
+ <para>
+ Specifies a <firstterm>usage type</firstterm> to be passed to the program that makes a filesystem on this partition. A usage type defines a variety of tuning parameters to be used when making a filesystem. For this option to work, the filesystem must support the concept of usage types and there must be a configuration file that lists valid types. For <literal>ext2</literal>, <literal>ext3</literal>, <literal>ext4</literal>, this configuration file is <filename>/etc/mke2fs.conf</filename>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--fstype=</option></term>
+ <listitem>
+ <para>
+ Sets the file system type for the partition. Valid values are <literal>xfs</literal>, <literal>ext2</literal>, <literal>ext3</literal>, <literal>ext4</literal>, <literal>swap</literal>, <literal>vfat</literal>, <literal>efi</literal> and <literal>biosboot</literal>. For information about supported file systems, see <remark>TODO: xref to something about supported fs types</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--fsoptions=</option></term>
+ <listitem>
+ <para>
+ Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the <filename>/etc/fstab</filename> file of the installed system and should be enclosed in quotes. For example:
+ </para>
+ <programlisting>
+<option>--fsoptions="ro, x-systemd.device-timeout=0"</option>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--label=</option></term>
+ <listitem>
+ <para>
+ Assign a label to an individual partition.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--recommended</option></term>
+ <listitem>
+ <para>
+ Determine the size of the partition automatically. For details about the recommended scheme, see <remark>TODO: xref to something about recommended partitioning scheme</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--onbiosdisk</option></term>
+ <listitem>
+ <para>
+ Forces the partition to be created on a particular disk as discovered by the BIOS.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--encrypted</option></term>
+ <listitem>
+ <para>
+ Specifies that this partition should be encrypted, using the passphrase provided in the <option>--passphrase</option> option. If you do not specify a passphrase, <application>Anaconda</application> uses the default, system-wide passphrase set with the <command>autopart --passphrase</command> command, or stops the installation and prompts you to provide a passphrase if no default is set.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--passphrase=</option></term>
+ <listitem>
+ <para>
+ Specifies the passphrase to use when encrypting this partition. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect.
+ </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>
+ <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>
+ Add a randomly-generated passphrase to each encrypted partition. 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>
+ </variablelist>
+ </section>
+
+ <section id="sect-kickstart-commands-raid">
+ <title>raid (optional) - Create Software RAID</title>
+ <para>
+ Assembles a software RAID device. This command is of the form:
+ </para>
+ <programlisting>
+<command>raid <replaceable>mntpoint</replaceable> --level=<replaceable>level</replaceable> --device=<replaceable>mddevice</replaceable> <replaceable>partitions*</replaceable></command>
+ </programlisting>
+ <para>
+ For a detailed example of <command>raid</command> in action, see <xref linkend="sect-kickstart-example-advanced-partitioning" />.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><replaceable>mntpoint</replaceable></term>
+ <listitem>
+ <para>
+ Location where the RAID file system is mounted. If it is <filename>/</filename>, the RAID level must be 1 unless a boot partition (<filename>/boot</filename>) is present. If a boot partition is present, the <filename>/boot</filename> partition must be level 1 and the root (<filename>/</filename>) partition can be any of the available types. The <replaceable>partitions*</replaceable> (which denotes that multiple partitions can be listed) lists the RAID identifiers to add to the RAID array.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--level=</option></term>
+ <listitem>
+ <para>
+ RAID level to use (<literal>0</literal>, <literal>1</literal>, <literal>4</literal>, <literal>5</literal>, <literal>6</literal>, or <literal>10</literal>). <remark>TODO: xref to the section that describes raid levels</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--device=</option></term>
+ <listitem>
+ <para>
+ Name of the RAID device to use. As of &PRODUCT; &PRODVER;, RAID devices are no longer referred to by names like <literal>md0</literal>. If you have an old (v0.90 metadata) array that you cannot assign a name to, you can specify the array by a filesystem label or UUID (for example, <option>--device=rhel7-root --label=rhel7-root</option>).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--spares=</option></term>
+ <listitem>
+ <para>
+ Specifies the number of spare drives allocated for the RAID array. Spare drives are used to rebuild the array in case of drive failure.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--fsprofile=</option></term>
+ <listitem>
+ <para>
+ Specifies a <firstterm>usage type</firstterm> to be passed to the program that makes a filesystem on this partition. A usage type defines a variety of tuning parameters to be used when making a filesystem. For this option to work, the filesystem must support the concept of usage types and there must be a configuration file that lists valid types. For <literal>ext2</literal>, <literal>ext3</literal>, <literal>ext4</literal>, this configuration file is <filename>/etc/mke2fs.conf</filename>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--fstype=</option></term>
+ <listitem>
+ <para>
+ Sets the file system type for the partition. Valid values are <literal>xfs</literal>, <literal>ext2</literal>, <literal>ext3</literal>, <literal>ext4</literal>, <literal>swap</literal>, <literal>vfat</literal>, <literal>efi</literal> and <literal>biosboot</literal>. For information about supported file systems, see <remark>TODO: xref to something about supported fs types</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--fsoptions=</option></term>
+ <listitem>
+ <para>
+ Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the <filename>/etc/fstab</filename> file of the installed system and should be enclosed in quotes. For example:
+ </para>
+ <programlisting>
+<option>--fsoptions="ro, x-systemd.device-timeout=0"</option>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--label=</option></term>
+ <listitem>
+ <para>
+ Specify the label to give to the filesystem to be made. If the given label is already in use by another filesystem, a new label will be created.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--noformat</option></term>
+ <listitem>
+ <para>
+ Use an existing RAID device and do not format it.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--useexisting</option></term>
+ <listitem>
+ <para>
+ Use an existing RAID device and reformat it.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--encrypted</option></term>
+ <listitem>
+ <para>
+ Specifies that this array should be encrypted, using the passphrase provided in the <option>--passphrase</option> option. If you do not specify a passphrase, <application>Anaconda</application> uses the default, system-wide passphrase set with the <command>autopart --passphrase</command> command, or stops the installation and prompts you to provide a passphrase if no default is set.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--passphrase=</option></term>
+ <listitem>
+ <para>
+ Specifies the passphrase to use when encrypting this partition. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect.
+ </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>
+ <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>
+ Add a randomly-generated passphrase to each encrypted partition. 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>
+ </variablelist>
+ <para>
+ The following example shows how to create a RAID level 1 partition for <filename>/</filename>, and a RAID level 5 for <filename>/home</filename>, assuming there are three SCSI disks on the system. It also creates three swap partitions, one on each drive.
+ </para>
+ <example>
+ <title>Creating a RAID array in Kickstart</title>
+ <programlisting>
+<command>part raid.01 --size=6000 --ondisk=sda</command>
+<command>part raid.02 --size=6000 --ondisk=sdb</command>
+<command>part raid.03 --size=6000 --ondisk=sdc</command>
+
+<command>part swap --size=512 --ondisk=sda</command>
+<command>part swap --size=512 --ondisk=sdb</command>
+<command>part swap --size=512 --ondisk=sdc</command>
+
+<command>part raid.11 --size=1 --grow --ondisk=sda</command>
+<command>part raid.12 --size=1 --grow --ondisk=sdb</command>
+<command>part raid.13 --size=1 --grow --ondisk=sdc</command>
+
+<command>raid / --level=1 --device=f&PRODVER;-root --label=f&PRODVER;-root raid.01 raid.02 raid.03</command>
+<command>raid /home --level=5 --device=f&PRODVER;-home --label=f&PRODVER;-home raid.11 raid.12 raid.13</command>
+ </programlisting>
+ </example>
+ </section>
+
+ <section id="sect-kickstart-commands-volgroup">
+ <title>volgroup (optional) - Create LVM Volume Group</title>
+ <para>
+ Creates a Logical Volume Management (LVM) volume group.
+ </para>
+ <programlisting>
+<command>volgroup <replaceable>name</replaceable> <replaceable>partition</replaceable> [<replaceable>options</replaceable>]</command>
+ </programlisting>
+ <important>
+ <para>
+ Do not use the dash (<literal>-</literal>) character in logical volume and volume group names when installing &PRODUCT; using Kickstart. If this character is used, the installation will finish normally, but the <filename class="directory">/dev/mapper/</filename> directory will list these volumes and volume groups with every dash doubled. For example, a volume group named <literal>volgrp-01</literal> containing a logical volume named <literal>logvol-01</literal> will be listed as <filename>/dev/mapper/volgrp--01-logvol--01</filename>.
+ </para>
+ <para>
+ This limitation only applies to newly created logical volume and volume group names. If you are reusing existing ones using the <option>--noformat</option> or <option>--noformat</option> option, their names will not be changed.
+ </para>
+ </important>
+ <para>
+ For a detailed partitioning example including <command>volgroup</command>, see <xref linkend="sect-kickstart-example-advanced-partitioning" />.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><option>--noformat</option></term>
+ <listitem>
+ <para>
+ Use an existing volume group and do not format it.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--useexisting</option></term>
+ <listitem>
+ <para>
+ Use an existing volume group and reformat it.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--pesize=</option></term>
+ <listitem>
+ <para>
+ Set the size of the physical extents. The default size for Kickstart installations is 4 MiB.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--reserved-space=</option></term>
+ <listitem>
+ <para>
+ Specify an amount of space to leave unused in a volume group in megabytes. Applicable only to newly created volume groups.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--reserved-percent=</option></term>
+ <listitem>
+ <para>
+ Specify a percentage of total volume group space to leave unused. Applicable only to newly created volume groups.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ Create one or more partitions first using <xref linkend="sect-kickstart-commands-part" />, create the logical volume group (<xref linkend="sect-kickstart-commands-volgroup" />), and then create logical volumes. For example:
+ </para>
+ <programlisting>
+<command>part pv.01 --size 3000</command>
+<command>volgroup myvg pv.01</command>
+<command>logvol / --vgname=myvg --size=2000 --name=rootvol</command>
+ </programlisting>
+ </section>
+
+ <section id="sect-kickstart-commands-zerombr">
+ <title>zerombr (optional) - Reinitialize Partition Tables</title>
+ <para>
+ If <command>zerombr</command> is specified, any invalid partition tables found on disks are initialized. This destroys all of the contents of disks with invalid partition tables. This command is required when performing an unattended installation on a system with previously initialized disks.
+ </para>
+ <warning>
+ <para>
+ On IBM System z, if <command>zerombr</command> is specified, any <firstterm>Direct Access Storage Device</firstterm> (DASD) visible to the installation program which is not already low-level formatted is automatically low-level formatted with <application>dasdfmt</application>. The command also prevents user choice during interactive installations.
+ </para>
+ <para>
+ If <command>zerombr</command> is not specified and there is at least one unformatted DASD visible to the installation program, a non-interactive Kickstart installation will exit unsuccessfully.
+ </para>
+ <para>
+ If <command>zerombr</command> is not specified and there is at least one unformatted DASD visible to the installation program, an interactive installation exits if the user does not agree to format all visible and unformatted DASDs. To circumvent this, only activate those DASDs that you will use during installation. You can always add more DASDs after installation is complete.
+ </para>
+ </warning>
+ </section>
+
+ <section id="sect-kickstart-commands-zfcp">
+ <title>zfcp (optional) - Configure Fibre Channel Device</title>
+ <para>
+ Define a Fibre channel device. This option only applies on IBM System z. All of the options described below must be specified.
+ </para>
+ <programlisting>
+<command>zfcp --devnum=<replaceable>devnum</replaceable> --wwpn=<replaceable>wwpn</replaceable> --fcplun=<replaceable>lun</replaceable></command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--devnum</option></term>
+ <listitem>
+ <para>
+ The device number (zFCP adaptor device bus ID).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--wwpn</option></term>
+ <listitem>
+ <para>
+ The device's World Wide Port Name (WWPN). Takes the form of a 16-digit number, preceded by <literal>0x</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--fcplun</option></term>
+ <listitem>
+ <para>
+ The device's Logical Unit Number (LUN). Takes the form of a 16-digit number, preceded by <literal>0x</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ For example:
+ </para>
+ <programlisting>
+<command>zfcp --devnum=0.0.4000 --wwpn=0x5005076300C213e9 --fcplun=0x5022000000000000</command>
+ </programlisting>
+ </section>
+
+ </section>
+
+ <section id="sect-kickstart-commands-network-configuration">
+ <title>Network Configuration</title>
+ <para>
+ Commands in this chapter are used for network configuration.
+ </para>
+
+ <section id="sect-kickstart-commands-firewall">
+ <title>firewall (optional) - Configure Firewall</title>
+ <para>
+ 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">
+ <title>network (optional) - Configure Network Interfaces</title>
+ <para>
+ Configures network information for the target system and activates network devices in the installation environment. The device specified in the first <command>network</command> command is activated automatically. Activation of the device can be also explicitly required by the <option>--activate</option> option.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><option>--activate</option></term>
+ <listitem>
+ <para>
+ If you use the <option>--activate</option> option on a device that has already been activated (for example, an interface you configured with boot options so that the system could retrieve the Kickstart file) the device is reactivated to use the details specified in the Kickstart file.
+ </para>
+ <para>
+ Use the <option>--nodefroute</option> option to prevent the device from using the default route.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--bootproto=</option></term>
+ <listitem>
+ <para>
+ One of <literal>dhcp</literal>, <literal>bootp</literal>, <literal>ibft</literal>, or <literal>static</literal>. The default option is <literal>dhcp</literal>; the <literal>dhcp</literal> and <literal>bootp</literal> options are treated the same.
+ </para>
+ <para>
+ The DHCP method uses a DHCP server system to obtain its networking configuration. The BOOTP method is similar, requiring a BOOTP server to supply the networking configuration. To direct a system to use DHCP:
+ </para>
+ <programlisting>
+<command>network --bootproto=dhcp</command>
+ </programlisting>
+ <para>
+ To direct a machine to use BOOTP to obtain its networking configuration, use the following line in the Kickstart file:
+ </para>
+ <programlisting>
+<command>network --bootproto=bootp</command>
+ </programlisting>
+ <para>
+ To direct a machine to use the configuration specified in iBFT, use:
+ </para>
+ <programlisting>
+<command>network --bootproto=ibft</command>
+ </programlisting>
+ <para>
+ The <literal>static</literal> method requires that you specify the IP address, netmask, gateway, and nameserver in the Kickstart file. This information is static and is used during and after the installation.
+ </para>
+ <para>
+ All static networking configuration information must be specified on <emphasis>one</emphasis> line; you cannot wrap lines using a backslash (<literal>\</literal>) as you can on a command line.
+ </para>
+ <programlisting>
+<command>network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver=10.0.2.1</command>
+ </programlisting>
+ <para>
+ You can also configure multiple nameservers at the same time. To do so, specify them as a comma-delimited list in the command line.
+ </para>
+ <programlisting>
+<command>network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver=192.168.2.1,192.168.3.1</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--device=</option></term>
+ <listitem>
+ <para>
+ Specifies the device to be configured (and eventually activated in <application>Anaconda</application>) with the <command>network</command> command.
+ </para>
+ <para>
+ If the <option>--device=</option> option is missing on the <emphasis>first</emphasis> use of the <command>network</command> command, the value of the <option>ksdevice=</option> <application>Anaconda</application> boot option is used, if available. Note that this is considered deprecated behavior; in most cases, you should always specify a <option>--device=</option> for every <command>network</command> command.
+ </para>
+ <para>
+ The behavior of any subsequent <command>network</command> command in the same Kickstart file is unspecified if its <option>--device=</option> option is missing. Make sure you specify this option for any <command>network</command> command beyond the first.
+ </para>
+ <para>
+ You can specify a device to be activated in any of the following ways:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the device name of the interface, for example, <systemitem>em1</systemitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ the MAC address of the interface, for example, <systemitem>01:23:45:67:89:ab</systemitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ the keyword <literal>link</literal>, which specifies the first interface with its link in the <literal>up</literal> state
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ the keyword <literal>bootif</literal>, which uses the MAC address that <application>pxelinux</application> set in the <parameter>BOOTIF</parameter> variable. Set <literal>IPAPPEND 2</literal> in your <filename>pxelinux.cfg</filename> file to have <application>pxelinux</application> set the <parameter>BOOTIF</parameter> variable.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ For example:
+ </para>
+ <programlisting>
+<command>network --bootproto=dhcp --device=em1</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--ip=</option></term>
+ <listitem>
+ <para>
+ IP address of the device.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--ipv6=</option></term>
+ <listitem>
+ <para>
+ IPv6 address of the device, in the form of <replaceable>address</replaceable>[/<replaceable>prefix</replaceable> <replaceable>length</replaceable>] - for example, <literal>3ffe:ffff:0:1::1/128 </literal>. If <replaceable>prefix</replaceable> is omitted, <literal>64</literal> will be used. You can also use <literal>auto</literal> for automatic configuration, or <literal>dhcp</literal> for DHCPv6-only configuration (no router advertisements).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--gateway=</option></term>
+ <listitem>
+ <para>
+ Default gateway as a single IPv4 address.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--ipv6gateway=</option></term>
+ <listitem>
+ <para>
+ Default gateway as a single IPv6 address.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--nodefroute</option></term>
+ <listitem>
+ <para>
+ Prevents the interface being set as the default route. Use this option when you activate additional devices with the <option>--activate=</option> option, for example, a NIC on a separate subnet for an iSCSI target.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--nameserver=</option></term>
+ <listitem>
+ <para>
+ Primary nameserver, as an IP address. Multiple nameservers must each be separated by a comma.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--nodns</option></term>
+ <listitem>
+ <para>
+ Do not configure any DNS server.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--netmask=</option></term>
+ <listitem>
+ <para>
+ Network mask for the installed system.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--hostname=</option></term>
+ <listitem>
+ <para>
+ Hostname for the installed system.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--ethtool=</option></term>
+ <listitem>
+ <para>
+ Specifies additional low-level settings for the network device which will be passed to the <application>ethtool</application> program.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--essid=</option></term>
+ <listitem>
+ <para>
+ The network ID for wireless networks.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--wepkey=</option></term>
+ <listitem>
+ <para>
+ The WEP encryption key for wireless networks.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--wpakey=</option></term>
+ <listitem>
+ <para>
+ The WPA encryption key for wireless networks.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--onboot=</option></term>
+ <listitem>
+ <para>
+ Whether or not to enable the device at boot time.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--dhcpclass=</option></term>
+ <listitem>
+ <para>
+ The DHCP class.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--mtu=</option></term>
+ <listitem>
+ <para>
+ The MTU of the device.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--noipv4</option></term>
+ <listitem>
+ <para>
+ Disable IPv4 on this device.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--noipv6</option></term>
+ <listitem>
+ <para>
+ Disable IPv6 on this device.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--bondslaves=</option></term>
+ <listitem>
+ <para>
+ When this option is used, the network device specified in the <option>--device=</option> option will be created using slaves defined in the <option>--bondslaves=</option> option. For example:
+ </para>
+ <programlisting>
+<command>network --device=mynetwork --bondslaves=em1,em2</command>
+ </programlisting>
+ <para>
+ The above command will create a bond device named <literal>mynetwork</literal> using the <literal>em1</literal> and <literal>em2</literal> interfaces as its slaves.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><command>--bondopts=</command></term>
+ <listitem>
+ <para>
+ A list of optional parameters for a bonded interface, which is specified using the <command>--bondslaves=</command> and <command>--device=</command> options. Options in this list must be separated by commas ("<literal>,</literal>") or semicolons ("<literal>;</literal>"). If an option itself contains a comma, use a semicolon to separate the options. For example:
+ </para>
+ <programlisting>
+<command>network --bondopts=mode=active-backup,balance-rr;primary=eth1</command>
+ </programlisting>
+ <para>
+ Available optional parameters are listed in the <citetitle>Working with Kernel Modules</citetitle> chapter of the <citetitle>Fedora System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">Fedora Documentation</ulink>.
+ </para>
+ <important>
+ <para>
+ The <option>--bondopts=mode=</option> parameter only supports full mode names such as <literal>balance-rr</literal> or <literal>broadcast</literal>, not their numerical representations such as <literal>0</literal> or <literal>3</literal>.
+ </para>
+ </important>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--vlanid=</option></term>
+ <listitem>
+ <para>
+ Specifies virtual LAN (VLAN) ID number (802.1q tag) for the device created using the device specified in <option>--device=</option> as a parent. For example, <command>network --device=em1 --vlanid=171</command> will create a virtual LAN device <literal>em1.171</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--interfacename=</option></term>
+ <listitem>
+ <para>
+ Specify a custom interface name for a virtual LAN device. This option should be used when the default name generated by the <option>--vlanid=</option> option is not desirable. This option must be used along with <option>--vlanid=</option>. For example:
+ </para>
+ <programlisting>
+<command>network --device=em1 --vlanid=171 --interfacename=vlan171</command>
+ </programlisting>
+ <para>
+ The above command will create a virtual LAN interface named <literal>vlan171</literal> on the <literal>em1</literal> device with an ID of <literal>171</literal>.
+ </para>
+ <para>
+ The interface name can be arbitrary (for example, <literal>my-vlan</literal>), but in specific cases, the following conventions must be followed:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ If the name contains a dot (<literal>.</literal>), it must take the form of <literal><replaceable>NAME</replaceable>.<replaceable>ID</replaceable></literal>. The <replaceable>NAME</replaceable> is arbitrary, but the <replaceable>ID</replaceable> must be the VLAN ID. For example: <literal>em1.171</literal> or <literal>my-vlan.171</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Names starting with <literal>vlan</literal> must take the form of <literal>vlan<replaceable>ID</replaceable></literal> - for example, <literal>vlan171</literal>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--teamslaves=</option></term>
+ <listitem>
+ <para>
+ Team device specified by the <option>--device=</option> option will be created using slaves specified in this option. Slaves are separated by commas. A slave can be followed by its configuration, which is a single-quoted JSON string with double quotes escaped by the <literal>\</literal> character. For example:
+ </para>
+ <programlisting>
+<command>network --teamslaves="p3p1'{\"prio\": -10, \"sticky\": true}',p3p2'{\"prio\": 100}'"</command>
+ </programlisting>
+ <para>
+ See also the <option>--teamconfig=</option> option.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--teamconfig=</option></term>
+ <listitem>
+ <para>
+ Double-quoted team device configuration which is a single-quoted JSON string with double quotes escaped by the <literal>\</literal> character. The device name is specified by <option>--device=</option> option and its slaves and their configuration by <option>--teamslaves=</option> option. For example:
+ </para>
+ <programlisting>
+<command>network --device team0 --activate --bootproto static --ip=10.34.102.222 --netmask=255.255.255.0 --gateway=10.34.102.254 --nameserver=10.34.39.2 --teamslaves="p3p1'{\"prio\": -10, \"sticky\": true}',p3p2'{\"prio\": 100}'" --teamconfig="{\"runner\": {\"name\": \"activebackup\"}}"</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
+ </section>
+
+ <section id="sect-kickstart-commands-environment">
+ <title>Console and Environment</title>
+ <para>
+ The following commands control the environment of the system after the installation finishes - language, keyboard layouts, or the graphical interface.
+ </para>
+
+ <section id="sect-kickstart-commands-keyboard">
+ <title>keyboard (optional) - Configure Keyboard Layouts</title>
+ <para>
+ Sets one or more available keyboard layouts for the system.
+ </para>
+ <programlisting>
+<command>keyboard --vckeymap= | --xlayouts= [--switch=]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--vckeymap=</option></term>
+ <listitem>
+ <para>
+ Specify a <systemitem>VConsole</systemitem> keymap which should be used. Valid names correspond to the list of files in the <filename class="directory">/usr/lib/kbd/keymaps/*</filename> directory, without the <literal>.map.gz</literal> extension.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--xlayouts=</option></term>
+ <listitem>
+ <para>
+ Specify a list of <application>X</application> layouts that should be used as a comma-separated list without spaces. Accepts values in the same format as <systemitem>setxkbmap(1)</systemitem>, either in the <literal><replaceable>layout</replaceable></literal> format (such as <literal>cz</literal>), or in the <literal><replaceable>layout</replaceable> (<replaceable>variant</replaceable>)</literal> format (such as <literal>cz (qwerty)</literal>).
+ </para>
+ <para>
+ All available layouts can be viewed on the <systemitem>xkeyboard-config(7)</systemitem> man page under <literal>Layouts</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--switch=</option></term>
+ <listitem>
+ <para>
+ Specify a list of layout-switching options (shortcuts for switching between multiple keyboard layouts). Multiple options must be separated by commas without spaces. Accepts values in the same format as <systemitem>setxkbmap(1)</systemitem>.
+ </para>
+ <para>
+ Available switching options can be viewed on the <systemitem>xkeyboard-config(7)</systemitem> man page under <literal>Options</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ The following example sets up two keyboard layouts (<literal>English (US)</literal> and <literal>Czech (qwerty)</literal>) using the <option>--xlayouts=</option> option, and allows to switch between them using <keycombo><keycap>Alt</keycap><keycap>Shift</keycap></keycombo>:
+ </para>
+ <programlisting>
+<command>keyboard --xlayouts=us,'cz (qwerty)' --switch=grp:alt_shift_toggle</command>
+ </programlisting>
+ </section>
+
+ <section id="sect-kickstart-commands-lang">
+ <title>lang (optional) - Configure Language During Installation</title>
+ <para>
+ Sets the language to use during installation and the default language to use on the installed system.
+ </para>
+ <programlisting>
+<command>lang <replaceable>language</replaceable> [--addsupport=]</command>
+ </programlisting>
+ <para>
+ The file <filename>/usr/share/system-config-language/locale-list</filename> provides a list of the valid <replaceable>language</replaceable> codes in the first column of each line and is part of the <package>system-config-language</package> package.
+ </para>
+ <para>
+ Certain languages (for example, Chinese, Japanese, Korean, and Indic languages) are not supported during text-mode installation. If you specify one of these languages with the <command>lang</command> command and use text mode, the installation process will continue in English, but the installed system will use your selection as its default language.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><option>--addsupport=</option></term>
+ <listitem>
+ <para>
+ Add support for additional languages. Takes the form of comma-separated list without spaces. For example:
+ </para>
+ <programlisting>
+<command>lang en_US --addsupport=cs_CZ,de_DE,en_UK</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
+ <section id="sect-kickstart-commands-services">
+ <title>services (optional) - Configure Services</title>
+ <para>
+ Modifies the default set of services that will run under the default <application>systemd</application> target. The list of disabled services is processed before the list of enabled services - therefore, if a service appears on both lists, it will be enabled.
+ </para>
+ <programlisting>
+<command>services [--disabled=<replaceable>list</replaceable>] [--enabled=<replaceable>list</replaceable>]</command>
+ </programlisting>
+ <para>
+ Do not include spaces in the list of services. If you do, Kickstart will enable or disable only the services up to the first space. For example:
+ </para>
+ <programlisting>
+<command>services --disabled=auditd, cups,smartd, nfslock</command>
+ </programlisting>
+ <para>
+ The above will disable only the <systemitem>auditd</systemitem> service. To disable all four services, the entry should include no spaces:
+ </para>
+ <programlisting>
+<command>services --disabled=auditd,cups,smartd,nfslock</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--disabled=</option></term>
+ <listitem>
+ <para>
+ Disable the services given in the comma separated list.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--enabled=</option></term>
+ <listitem>
+ <para>
+ Enable the services given in the comma separated list.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
+ <section id="sect-kickstart-commands-skipx">
+ <title>skipx (optional) - Do Not Configure X Window System</title>
+ <para>
+ If present, <application>X</application> will not be configured on the installed system.
+ </para>
+ <important>
+ <para>
+ If you install a display manager among your package selection options, this package will create an <application>X</application> configuration, and the installed system will default to <systemitem>graphical.target</systemitem>. The effect of the <command>skipx</command> option will be overridden.
+ </para>
+ </important>
+ </section>
+
+ <section id="sect-kickstart-commands-timezone">
+ <title>timezone (optional) - Configure Time Zone</title>
+ <para>
+ Sets the system time zone to <replaceable>timezone</replaceable>. To view a list of available time zones, use the <command>timedatectl list-timezones</command> command.
+ </para>
+ <programlisting>
+<command>timezone <replaceable>timezone</replaceable> [<replaceable>options</replaceable>]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--utc</option></term>
+ <listitem>
+ <para>
+ If present, the system assumes the hardware clock is set to UTC (Greenwich Mean) time.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--nontp</option></term>
+ <listitem>
+ <para>
+ Disable the NTP service automatic starting.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--ntpservers=</option></term>
+ <listitem>
+ <para>
+ Specify a list of NTP servers to be used as a comma-separated list without spaces.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
+ <section id="sect-kickstart-commands-xconfig">
+ <title>xconfig (optional) - Configure X Window System</title>
+ <para>
+ Configures the <application>X Window System</application>. If you install the <application>X Window System</application> with a Kickstart file that does not include the <command>xconfig</command> command, you must provide the <application>X</application> configuration manually during installation.
+ </para>
+ <para>
+ Do not use this command in a Kickstart file that does not install the <application>X Window System</application>.
</para>
+ <variablelist>
+ <varlistentry>
+ <term><option>--defaultdesktop=</option></term>
+ <listitem>
+ <para>
+ Specify either <literal>GNOME</literal> or <literal>KDE</literal> to set the default desktop (assumes that <application>GNOME Desktop Environment</application> and/or <application>KDE Desktop Environment</application> has been installed in the <command>%packages</command> section).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--startxonboot</option></term>
+ <listitem>
+ <para>
+ Use a graphical login on the installed system.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
</section>
@@ -1279,169 +2597,421 @@
<term><option>--useshadow</option>or <option>--enableshadow</option></term>
<listitem>
<para>
- Use shadow passwords. Active by default.
+ 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 (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.
+ </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 (optional) - Join an Active Directory or IPA Domain</title>
+ <para>
+ Join an Active Directory or IPA domain. For more information about this command, see the <command>join</command> section of the <systemitem>realm(8)</systemitem> man page.
+ </para>
+ <programlisting>
+<command>realm join <replaceable>domain</replaceable> [<replaceable>options</replaceable>]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--computer-ou=OU=</option></term>
+ <listitem>
+ <para>
+ Provide the <firstterm>distinguished name</firstterm> of an organizational unit in order to create the computer account. The exact format of the distinguished name depends on the client software and membership software. The root DSE portion of the distinguished name can usually be left out.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--no-password</option></term>
+ <listitem>
+ <para>
+ Join automatically without a password.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--one-time-password=</option></term>
+ <listitem>
+ <para>
+ Join using a one-time password. This is not possible with all types of realm.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--client-software=</option></term>
+ <listitem>
+ <para>
+ Only join realms which can run this client software. Valid values include <literal>sssd</literal> and <literal>winbind</literal>. Not all realms support all values. By default, the client software is chosen automatically.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--server-software=</option></term>
+ <listitem>
+ <para>
+ Only join realms which can run this server software. Possible values include <literal>active-directory</literal> or <literal>freeipa</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--enableldap</option></term>
+ <term><option>--membership-software=</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>.
+ Use this software when joining the realm. Valid values include <literal>samba</literal> and <literal>adcli</literal>. Not all realms support all values. By default, the membership software is chosen automatically.
</para>
</listitem>
</varlistentry>
+ </variablelist>
+ </section>
+
+ <section id="sect-kickstart-commands-rootpw">
+ <title>rootpw (required) - Set Root Password</title>
+ <para>
+ Sets the system's root password to the <replaceable>password</replaceable> argument.
+ </para>
+ <programlisting>
+<command>rootpw [--iscrypted|--plaintext] [--lock] <replaceable>password</replaceable></command>
+ </programlisting>
+ <variablelist>
<varlistentry>
- <term><option>--enableldapauth</option></term>
+ <term><option>--iscrypted</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.
+ If this option is present, the password argument is assumed to already be encrypted. This option is mutually exclusive with <option>--plaintext</option>. To create an encrypted password, you can use Python:
+ </para>
+ <screen>
+<prompt>$</prompt> <command>python -c 'import crypt; print(crypt.crypt("My Password", "$6$My Salt"))'</command>
+ </screen>
+ <para>
+ This will generate a SHA512 crypt of your password using your provided salt.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--ldapserver=</option></term>
+ <term><option>--plaintext</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.
+ If this option is present, the password argument is assumed to be in plain text. This option is mutually exclusive with <option>--iscrypted</option>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--ldapbasedn=</option></term>
+ <term><option>--lock</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.
+ If this option is present, the root account is locked by default. This means that the root user will not be able to log in from the console.
</para>
</listitem>
</varlistentry>
+ </variablelist>
+ </section>
+
+ <section id="sect-kickstart-commands-selinux">
+ <title>selinux (optional) - Configure SELinux</title>
+ <para>
+ Sets the state of SELinux on the installed system. The default policy is <systemitem>enforcing</systemitem>. For more information regarding SELinux in &PRODUCT;, see <remark>TODO: link to wherever we document SELinux now</remark>
+ </para>
+ <programlisting>
+<command>selinux [--disabled|--enforcing|--permissive]</command>
+ </programlisting>
+ <variablelist>
<varlistentry>
- <term><option>--enableldaptls</option></term>
+ <term><option>--enforcing</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.
+ Enables SELinux with the default targeted policy being <systemitem>enforcing</systemitem>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--disableldaptls</option></term>
+ <term><option>--permissive</option></term>
<listitem>
<para>
- Do not use TLS (Transport Layer Security) lookups in an environment that uses LDAP for authentication.
+ Enables SELinux with the default targeted policy being <systemitem>permissive</systemitem>. This policy outputs warnings based on the SELinux policy, but does not actually enforce the policy.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--enablekrb5</option></term>
+ <term><option>--disabled</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.
+ Disables SELinux completely.
</para>
</listitem>
</varlistentry>
+ </variablelist>
+ </section>
+
+ <section id="sect-kickstart-commands-user">
+ <title>user (optional) - Create User Account</title>
+ <para>
+ Creates a new user on the system.
+ </para>
+ <programlisting>
+<command>user --name=<replaceable>username</replaceable> [<replaceable>options</replaceable>]</command>
+ </programlisting>
+ <variablelist>
<varlistentry>
- <term><option>--krb5realm=</option></term>
+ <term><option>--name=</option></term>
<listitem>
<para>
- The Kerberos 5 realm to which your workstation belongs.
+ Provides the name of the user. This option is required.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--krb5kdc=</option></term>
+ <term><option>--gecos=</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.
+ Provides the GECOS information for the user. This is a string of various system-specific fields separated by a comma. It is frequently used to specify the user's full name, office number, etc. See the <systemitem>passwd(5)</systemitem> man page for more details.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--krb5adminserver=</option></term>
+ <term><option>--groups=</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.
+ In addition to the default group, a comma separated list of group names the user should belong to. The groups must exist before the user account is created. See <xref linkend="sect-kickstart-commands-group" />.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--enablehesiod</option></term>
+ <term><option>--homedir=</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.
+ The home directory for the user. If not provided, this defaults to <filename>/home/<replaceable>username</replaceable></filename>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--hesiodlhs=</option> and <option>--hesiodrhs=</option></term>
+ <term><option>--lock</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>.
+ If this option is present, this account is locked by default. This means that the user will not be able to log in from the console.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--enablesmbauth</option></term>
+ <term><option>--password=</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.
+ The new user's password. If no password is provided, the account will be locked.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--smbservers=</option></term>
+ <term><option>--password=</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>).
+ The new user's password. If not provided, the account will be locked by default.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--smbworkgroup=</option></term>
+ <term><option>--iscrypted</option></term>
<listitem>
<para>
- The name of the workgroup for the SMB servers.
+ If this option is present, the password argument is assumed to already be encrypted. This option is mutually exclusive with <option>--plaintext</option>. To create an encrypted password, you can use Python:
+ </para>
+ <screen>
+<prompt>$</prompt> <command>python -c 'import crypt; print(crypt.crypt("My Password", "$6$My Salt"))'</command>
+ </screen>
+ <para>
+ This will generate a SHA512 crypt of your password using your provided salt.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--enablecache</option></term>
+ <term><option>--plaintext</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>.
+ If this option is present, the password argument is assumed to be in plain text. This option is mutually exclusive with <option>--iscrypted</option>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--passalgo=</option></term>
+ <term><option>--shell=</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.
+ The user's login shell. If not provided, the system default will be used.
</para>
</listitem>
</varlistentry>
- </variablelist>
- </section>
-
- <section id="sect-kickstart-commands-group">
- <title>group - 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.
- </para>
- <programlisting>
-<command>group --name=<replaceable>name</replaceable> [--gid=<replaceable>gid</replaceable>]</command>
- </programlisting>
- <variablelist>
<varlistentry>
- <term><option>--name=</option></term>
+ <term><option>--uid=</option></term>
<listitem>
<para>
- Provides the name of the group.
+ The <firstterm>UID</firstterm> (User ID). If not provided, this defaults to the next available non-system UID.
</para>
</listitem>
</varlistentry>
@@ -1449,41 +3019,13 @@
<term><option>--gid=</option></term>
<listitem>
<para>
- The group ID (GID). If not provided, defaults to the next available non-system GID.
+ The <firstterm>GID</firstterm> (Group ID) to be used for the user's default group. If not provided, this defaults to the next available non-system group ID.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
- <section id="sect-kickstart-commands-realm">
- <title>realm - Join an Active Directory or IPA Domain</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-kickstart-commands-rootpw">
- <title>rootpw - Set Root Password</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-kickstart-commands-selinux">
- <title>selinux - Configure SELinux</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-kickstart-commands-user">
- <title>user - Create User Account</title>
- <para>
- text
- </para>
- </section>
-
</section>
<section id="sect-kickstart-commands-installation-environment">
@@ -1527,74 +3069,175 @@
</section>
<section id="sect-kickstart-commands-logging">
- <title>logging - Configure Error Logging During Installation</title>
+ <title>logging (optional) - Configure Error Logging During Installation</title>
<para>
- Controls the error logging of <application>Anaconda</application> during installation. It has no effect on the installed system.
- </para>
- <programlisting>
+ Controls the error logging of <application>Anaconda</application> during installation. It has no effect on the installed system.
+ </para>
+ <programlisting>
<command>logging [--host= | --port= | --level=]</command>
- </programlisting>
- <variablelist>
- <varlistentry>
- <term><option>--host=</option></term>
- <listitem>
- <para>
- Send logging information to the given remote host, which must be running a <systemitem class="service">syslogd</systemitem> process configured to accept remote logging.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--port=</option></term>
- <listitem>
- <para>
- If the remote syslogd process uses a port other than the default, it may be specified with this option.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--level=</option></term>
- <listitem>
- <para>
- Specify the minimum level of messages that appear on virtual console 3 (<systemitem>tty3</systemitem>). This only affects messages printed to the console; log files will contain messages of all levels. Possible values are <literal>debug</literal>, <literal>info</literal>, <literal>warning</literal>, <literal>error</literal>, or <literal>critical</literal>.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--host=</option></term>
+ <listitem>
+ <para>
+ Send logging information to the given remote host, which must be running a <systemitem class="service">syslogd</systemitem> process configured to accept remote logging.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--port=</option></term>
+ <listitem>
+ <para>
+ If the remote syslogd process uses a port other than the default, it may be specified with this option.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--level=</option></term>
+ <listitem>
+ <para>
+ Specify the minimum level of messages that appear on virtual console 3 (<systemitem>tty3</systemitem>). This only affects messages printed to the console; log files will contain messages of all levels. Possible values are <literal>debug</literal>, <literal>info</literal>, <literal>warning</literal>, <literal>error</literal>, or <literal>critical</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-rescue">
- <title>rescue - Rescue Mode</title>
+ <title>rescue (optional) - Rescue Mode</title>
<para>
- text
+ Automatically enters the installation program's rescue mode. This gives you a chance to repair the system in case of any problems.
</para>
+ <programlisting>
+<command>rescue [--nomount|--romount]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--nomount</option> or <option>--romount</option></term>
+ <listitem>
+ <para>
+ Controls how the installed system is mounted in the rescue environment. By default, the installation program will find your system and mount it in read-write mode, telling you where it has performed this mount. You may optionally choose to not mount anything (the <option>--nomount</option> option) or mount in read-only mode (the <option>--romount</option> option). Only one of these two options may be used.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-sshpw">
- <title>sshpw - Restrict ssh Access During Installation</title>
+ <title>sshpw (optional) - Restrict ssh Access During Installation</title>
<para>
- text
+ During the installation, you can interact with the installation program and monitor its progress over an <systemitem>SSH</systemitem> connection. Use the <command>sshpw</command> command to create temporary accounts through which to log on. Each instance of the command creates a separate account that exists only in the installation environment. These accounts are not transferred to the installed system.
</para>
+ <programlisting>
+<command>sshpw --username=<replaceable>name</replaceable> <replaceable>password</replaceable> [--iscrypted|--plaintext] [--lock]</command>
+ </programlisting>
+ <important>
+ <para>
+ By default, the <systemitem>ssh</systemitem> server is not started during the installation. To make <systemitem>ssh</systemitem> available during the installation, boot the system with the kernel boot option <option>inst.sshd</option>. See <xref linkend="sect-boot-options-display" /> for details.
+ </para>
+ </important>
+ <note>
+ <para>
+ If you want to disable root <systemitem class="protocol">ssh</systemitem> access to your hardware during installation, use the following:
+ </para>
+ <programlisting>
+<command>sshpw --username=root --lock</command>
+ </programlisting>
+ </note>
+ <variablelist>
+ <varlistentry>
+ <term><option>--username</option></term>
+ <listitem>
+ <para>
+ Provides the name of the user. This option is required.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--iscrypted</option></term>
+ <listitem>
+ <para>
+ If this option is present, the password argument is assumed to already be encrypted. This option is mutually exclusive with <option>--plaintext</option>. To create an encrypted password, you can use Python:
+ </para>
+ <screen>
+<prompt>$</prompt> <command>python -c 'import crypt; print(crypt.crypt("My Password", "$6$My Salt"))'</command>
+ </screen>
+ <para>
+ This will generate a SHA512 crypt of your password using your provided salt.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--plaintext</option></term>
+ <listitem>
+ <para>
+ If this option is present, the password argument is assumed to be in plain text. This option is mutually exclusive with <option>--iscrypted</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--lock</option></term>
+ <listitem>
+ <para>
+ If this option is present, this account is locked by default. This means that the user will not be able to log in from the console.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-text">
- <title>text - Perform Installation in Text Mode</title>
+ <title>text (optional) - Perform Installation in Text Mode</title>
<para>
- text
+ Perform the Kickstart installation in text mode. Kickstart installations are performed in graphical mode by default.
</para>
</section>
<section id="sect-kickstart-commands-unsupported_hardware">
- <title>unsupported_hardware - Suppress Unsupported Hardware Alerts</title>
+ <title>unsupported_hardware (optional) - Suppress Unsupported Hardware Alerts</title>
<para>
- text
+ Suppress the <guilabel>Unsupported Hardware Detected</guilabel> alert. If this command is not included and unsupported hardware is detected, the installation will stall at this alert.
</para>
</section>
<section id="sect-kickstart-commands-vnc">
- <title>vnc - Configure VNC Access</title>
+ <title>vnc (optional) - Configure VNC Access</title>
<para>
- text
+ Allows the graphical installation to be viewed remotely via VNC. This method is usually preferred over text mode, as there are some size and language limitations in text installations. With no additional options, this command will start a VNC server on the installation system with no password and will display the details required to connect to it.
+ </para>
+ <programlisting>
+<command>vnc [--host=<replaceable>hostname</replaceable>] [--port=<replaceable>port</replaceable>] [--password=<replaceable>password</replaceable>]</command>
+ </programlisting>
+ <para>
+ For more information about VNC installations, including instructions on how to connect to the installation system, see <xref linkend="chap-vnc-installations" />.
</para>
+ <variablelist>
+ <varlistentry>
+ <term><option>--host=</option></term>
+ <listitem>
+ <para>
+ Connect to a VNC viewer listening on the given hostname.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--port=</option></term>
+ <listitem>
+ <para>
+ Provide a port that the remote VNC viewer process is listening on. If not provided, the VNC default (<literal>5900</literal>) will be used.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--password=</option></term>
+ <listitem>
+ <para>
+ Set a password which must be provided to connect to the VNC session. This is optional, but recommended.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
</section>
@@ -1664,47 +3307,85 @@
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>
<section id="sect-kickstart-commands-poweroff">
- <title>poweroff - Power Off After Installation</title>
+ <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>
- text
+ For other completion methods, see the <command>halt</command>, <command>reboot</command>, and <command>shutdown</command> Kickstart commands.
</para>
</section>
<section id="sect-kickstart-commands-reboot">
- <title>reboot - Reboot After Installation</title>
+ <title>reboot (optional) - Reboot After Installation</title>
<para>
- text
+ 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.
+ </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>
+ <listitem>
+ <para>
+ Attempt to eject the installation media (if installing from a DVD) before rebooting.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-shutdown">
- <title>shutdown - Shut Down After Installation</title>
+ <title>shutdown (optional) - Shut Down After Installation</title>
<para>
- text
+ 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-include">
- <title>%include - Include Contents of Another File</title>
+ <title>%include (optional) - Include Contents of Another File</title>
+ <para>
+ Use the <command>%include <replaceable>/path/to/file</replaceable></command> command to include the contents of another file in the Kickstart file as though the contents were at the location of the <command>%include</command> command in the Kickstart file.
+ </para>
+ </section>
+ <section id="sect-kickstart-commands-ksappend">
+ <title>%ksappend (optional) - Append Contents of Another File</title>
+ <para>
+ The <command>%ksappend <replaceable>url</replaceable></command> directive is very similar to <xref linkend="sect-kickstart-commands-include" /> in that it is used to include the contents of additional files as though they were at the location of the <command>%ksappend</command> command. The difference is in when the two directives are processed.
+ </para>
<para>
- text
+ <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.
</para>
</section>
<section id="sect-kickstart-packages">
- <title>%packages - Package Selection</title>
+ <title>%packages (required) - Package Selection</title>
<para>
- Use the <command>%packages</command> command to begin a Kickstart section which describes the software packages to be installed.
+ Use the <command>%packages</command> command to begin a Kickstart section which describes the software packages to be installed. This section must end with an <command>%end</command> statement.
</para>
<para>
You can specify packages by <firstterm>environment</firstterm>, <firstterm>group</firstterm>, or by their package names. Several environments and groups that contain related packages are defined. See the <filename>repodata/*-comps-<replaceable>variant</replaceable>.<replaceable>architecture</replaceable>.xml</filename> file <remark>TODO: where's comps.xml?</remark>
@@ -1725,9 +3406,6 @@
<application>Initial Setup</application> does not run after a system is installed from a Kickstart file unless a desktop environment and the <application>X Window System</application> were included in the installation and graphical login was enabled. This means that by default, no users except for <systemitem class="username">root</systemitem> will be created. You can either create a user with the <option>user</option> option in the Kickstart file before installing additional systems from it (see <xref linkend="sect-kickstart-commands-user" /> for details) or log into the installed system with a virtual console as <systemitem class="username">root</systemitem> and add users with the <command>useradd</command> command.
</para>
</important>
- <para>
- The <command>%packages</command> section must end with the <command>%end</command> command.
- </para>
<variablelist>
<title>Specifying Environments, Groups and Packages</title>
<varlistentry>
@@ -1899,7 +3577,7 @@ docbook*
</section>
<section id="sect-kickstart-preinstall">
- <title>%pre - Pre-installation Script</title>
+ <title>%pre (optional) - Pre-installation Script</title>
<para>
You can add commands to run on the system immediately after the Kickstart file has been parsed, but before the installation begins. This section must be placed towards the end of the Kickstart file, after the actual Kickstart commands, and must start with <command>%pre</command> and end with <command>%end</command>. If your Kickstart file also includes a <command>%post</command> section, the order in which the <command>%pre</command> and <command>%post</command> sections are included does not matter.
</para>
@@ -1957,7 +3635,7 @@ docbook*
</section>
<section id="sect-kickstart-postinstall">
- <title>%post - Post-installation Script</title>
+ <title>%post (optional) - Post-installation Script</title>
<para>
You have the option of adding commands to run on the system once the installation is complete, but before the system is rebooted for the first time. This section must be placed towards the end of the Kickstart file, after the actual Kickstart commands, and must start with <command>%post</command> and end with <command>%end</command>. If your Kickstart file also includes a <command>%pre</command> section, the order of the <command>%pre</command> and <command>%post</command> sections does not matter.
</para>
1
0
[install-guide/F21-rewrite] Adding commands to Kickstart Syntax Reference up to logvol
by pbokoc 18 Sep '14
by pbokoc 18 Sep '14
18 Sep '14
commit dc5e3e516122f99743550dc9a9fe37592ba9bafd
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Thu Sep 18 12:16:11 2014 +0200
Adding commands to Kickstart Syntax Reference up to logvol
en-US/Kickstart_Syntax_Reference.xml | 389 ++++++++++++++++++++++++++++++++--
1 files changed, 372 insertions(+), 17 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index 29993ce..229ebc7 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -124,10 +124,195 @@
</section>
<section id="sect-kickstart-commands-install">
- <title>install - Configure Installation Method</title>
- <para>
- text
- </para>
+ <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:
+ </para>
+ <programlisting>
+<command>install</command>
+<command>liveimg --url=file:///images/install/squashfs.img --noverifyssl</command>
+ </programlisting>
+ <para>
+ The installation method commands are:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><command>cdrom</command></term>
+ <listitem>
+ <para>
+ Install from the first optical (DVD) drive on the system.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><command>harddrive</command></term>
+ <listitem>
+ <para>
+ Install from a tree or full installation ISO image on a local hard drive. The tree or ISO image must be on a file system which is mountable in the installation environment. Supported file systems are <systemitem>ext2</systemitem>, <systemitem>ext3</systemitem>, <systemitem>ext4</systemitem>, <systemitem>vfat</systemitem>, or <systemitem>xfs</systemitem>.
+ </para>
+ <programlisting>
+<command>install</command>
+<command>harddrive --partition= | --biospart= [--dir=]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--partition=</option></term>
+ <listitem>
+ <para>
+ Partition to install from (such as <literal>sdb2</literal>).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--biospart=</option></term>
+ <listitem>
+ <para>
+ BIOS partition to install from (such as <literal>82p2</literal>).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--dir=</option></term>
+ <listitem>
+ <para>
+ Directory containing the installation tree or ISO image.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><command>liveimg</command></term>
+ <listitem>
+ <para>
+ 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>
+ <programlisting>
+<command>install</command>
+<command>liveimg --url= [--proxy= | --checksum= | --noverifyssl=]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--url=</option></term>
+ <listitem>
+ <para>
+ The location to install from. Supported protocols are <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem>, <systemitem class="protocol">FTP</systemitem>, and <systemitem class="protocol">file</systemitem>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--proxy=</option></term>
+ <listitem>
+ <para>
+ Specify an <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem> or <systemitem class="protocol">FTP</systemitem> proxy to use while performing the installation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--checksum=</option></term>
+ <listitem>
+ <para>
+ An optional argument with the <systemitem>SHA256</systemitem> checksum of the image file, used for integrity verification. If you are using a live image provided by Fedora Project, you can find a list of checksums at <ulink url="https://fedoraproject.org/en/verify" />.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--noverifyssl</option></term>
+ <listitem>
+ <para>
+ Disable SSL verification when connecting to an <systemitem class="protocol">HTTPS</systemitem> server.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><command>nfs</command></term>
+ <listitem>
+ <para>
+ Install from an <systemitem class="protocol">NFS</systemitem> server specified. <remark>TODO: link to the PXE chapter's section on preparing install source on nfs</remark>
+ </para>
+ <programlisting>
+<command>install</command>
+<command>nfs --server= [--dir=] [--opts= ]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--server=</option></term>
+ <listitem>
+ <para>
+ Host name of the server.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--dir=</option></term>
+ <listitem>
+ <para>
+ Directory containing the installation tree or ISO image.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--opts=</option></term>
+ <listitem>
+ <para>
+ Mount options to use for mounting the <systemitem class="protocol">NFS</systemitem> export.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><command>url</command></term>
+ <listitem>
+ <para>
+ Install from a tree on a remote server via <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem>, or <systemitem class="protocol">FTP</systemitem>.
+ </para>
+ <programlisting>
+<command>install</command>
+<command>url --url= | --mirrorlist= [--proxy= | --noverifyssl]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--url=</option></term>
+ <listitem>
+ <para>
+ The location to install from. Supported protocols are <literal>http</literal>, <literal>https</literal>, <literal>ftp</literal>, and <literal>file</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--mirrorlist=</option></term>
+ <listitem>
+ <para>
+ The mirror URL to install from.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--proxy=</option></term>
+ <listitem>
+ <para>
+ Specify an <systemitem class="protocol">HTTP</systemitem>, <systemitem class="protocol">HTTPS</systemitem> or <systemitem class="protocol">FTP</systemitem> proxy to use while performing the installation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--noverifyssl</option></term>
+ <listitem>
+ <para>
+ Disable SSL verification when connecting to an <systemitem>HTTPS</systemitem> server.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-mediacheck">
@@ -697,17 +882,95 @@
</section>
<section id="sect-kickstart-commands-iscsi">
- <title>iscsi - Configure iSCSI Devices</title>
- <para>
- text
- </para>
+ <title>iscsi (optional) - Configure iSCSI Devices</title>
+ <para>
+ Specifies additional iSCSI storage to be attached during installation. If you use the <command>iscsi</command> command, you must also assign a name to the iSCSI node, using the <command>iscsiname</command> command (see <xref linkend="sect-kickstart-commands-iscsiname" />. The <command>iscsiname</command> command must appear before the <command>iscsi</command> command in the Kickstart file.
+ </para>
+ <para>
+ You should configure iSCSI storage in the system BIOS or firmware (iBFT for Intel systems) rather than use the <command>iscsi</command> command if possible. If you do so, <application>Anaconda</application> automatically detects and uses disks configured in BIOS or firmware and no special configuration is necessary in the Kickstart file.
+ </para>
+ <para>
+ If you must use the <command>iscsi</command> command, make sure that networking is activated at the beginning of the installation, and that the <command>iscsi</command> command appears in the Kickstart file <emphasis>before</emphasis> you refer to iSCSI disks with commands such as <command>clearpart</command> or <command>ignoredisk</command>.
+ </para>
+ <programlisting>
+<command>iscsi --ipaddr= --port= [--target= | --iface= | --user= | --password= | --reverse-user= | --reverse-password=]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--ipaddr=</option></term>
+ <listitem>
+ <para>
+ The IP address of the target to connect to.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--port=</option></term>
+ <listitem>
+ <para>
+ The port number (typically <literal>3260</literal>).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--target=</option></term>
+ <listitem>
+ <para>
+ Target <firstterm>IQN</firstterm> (iSCSI Qualified Name).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--iface=</option></term>
+ <listitem>
+ <para>
+ Bind the connection to a specific network interface instead of using the default one determined by the network layer. Once used, it must be specified in all instances of the <command>iscsi</command> command in the entire Kickstart file.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--user=</option></term>
+ <listitem>
+ <para>
+ User name required to authenticate with the target.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--password=</option></term>
+ <listitem>
+ <para>
+ Password that corresponds with the user name specified for the target.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--reverse-user=</option></term>
+ <listitem>
+ <para>
+ User name required to authenticate with the initiator from a target using reverse CHAP authentication.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--reverse-password=</option></term>
+ <listitem>
+ <para>
+ Password that corresponds with the user name specified for the initiator.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-iscsiname">
- <title>iscsiname - Assign Name to iSCSI Device</title>
+ <title>iscsiname (optional) - Assign Name to iSCSI Device</title>
<para>
- text
- </para>
+ Assigns a name to an iSCSI node specified by the <command>iscsi</command> command (<xref linkend="sect-kickstart-commands-iscsi" />). This command is mandatory if you use the <command>iscsi</command> command, and it must be specified <emphasis>before</emphasis> you use <command>iscsi</command>.
+ </para>
+ <programlisting>
+<command>iscsiname <replaceable>iqn</replaceable></command>
+ </programlisting>
</section>
<section id="sect-kickstart-commands-logvol">
@@ -867,17 +1130,80 @@
</para>
<section id="sect-kickstart-commands-keyboard">
- <title>keyboard - Configure Keyboard Layouts</title>
- <para>
- text
- </para>
+ <title>keyboard (optional) - Configure Keyboard Layouts</title>
+ <para>
+ Sets one or more available keyboard layouts for the system.
+ </para>
+ <programlisting>
+<command>keyboard --vckeymap= | --xlayouts= [--switch=]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--vckeymap=</option></term>
+ <listitem>
+ <para>
+ Specify a <systemitem>VConsole</systemitem> keymap which should be used. Valid names correspond to the list of files in the <filename class="directory">/usr/lib/kbd/keymaps/*</filename> directory, without the <literal>.map.gz</literal> extension.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--xlayouts=</option></term>
+ <listitem>
+ <para>
+ Specify a list of <application>X</application> layouts that should be used as a comma-separated list without spaces. Accepts values in the same format as <systemitem>setxkbmap(1)</systemitem>, either in the <literal><replaceable>layout</replaceable></literal> format (such as <literal>cz</literal>), or in the <literal><replaceable>layout</replaceable> (<replaceable>variant</replaceable>)</literal> format (such as <literal>cz (qwerty)</literal>).
+ </para>
+ <para>
+ All available layouts can be viewed on the <systemitem>xkeyboard-config(7)</systemitem> man page under <literal>Layouts</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--switch=</option></term>
+ <listitem>
+ <para>
+ Specify a list of layout-switching options (shortcuts for switching between multiple keyboard layouts). Multiple options must be separated by commas without spaces. Accepts values in the same format as <systemitem>setxkbmap(1)</systemitem>.
+ </para>
+ <para>
+ Available switching options can be viewed on the <systemitem>xkeyboard-config(7)</systemitem> man page under <literal>Options</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ The following example sets up two keyboard layouts (<literal>English (US)</literal> and <literal>Czech (qwerty)</literal>) using the <option>--xlayouts=</option> option, and allows to switch between them using <keycombo><keycap>Alt</keycap><keycap>Shift</keycap></keycombo>:
+ </para>
+ <programlisting>
+<command>keyboard --xlayouts=us,'cz (qwerty)' --switch=grp:alt_shift_toggle</command>
+ </programlisting>
</section>
<section id="sect-kickstart-commands-lang">
- <title>lang - Configure Language During Installation</title>
- <para>
- text
- </para>
+ <title>lang (optional) - Configure Language During Installation</title>
+ <para>
+ Sets the language to use during installation and the default language to use on the installed system.
+ </para>
+ <programlisting>
+<command>lang <replaceable>language</replaceable> [--addsupport=]</command>
+ </programlisting>
+ <para>
+ The file <filename>/usr/share/system-config-language/locale-list</filename> provides a list of the valid <replaceable>language</replaceable> codes in the first column of each line and is part of the <package>system-config-language</package> package.
+ </para>
+ <para>
+ Certain languages (for example, Chinese, Japanese, Korean, and Indic languages) are not supported during text-mode installation. If you specify one of these languages with the <command>lang</command> command and use text mode, the installation process will continue in English, but the installed system will use your selection as its default language.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><option>--addsupport=</option></term>
+ <listitem>
+ <para>
+ Add support for additional languages. Takes the form of comma-separated list without spaces. For example:
+ </para>
+ <programlisting>
+<command>lang en_US --addsupport=cs_CZ,de_DE,en_UK</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-services">
@@ -1203,8 +1529,37 @@
<section id="sect-kickstart-commands-logging">
<title>logging - Configure Error Logging During Installation</title>
<para>
- text
- </para>
+ Controls the error logging of <application>Anaconda</application> during installation. It has no effect on the installed system.
+ </para>
+ <programlisting>
+<command>logging [--host= | --port= | --level=]</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--host=</option></term>
+ <listitem>
+ <para>
+ Send logging information to the given remote host, which must be running a <systemitem class="service">syslogd</systemitem> process configured to accept remote logging.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--port=</option></term>
+ <listitem>
+ <para>
+ If the remote syslogd process uses a port other than the default, it may be specified with this option.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--level=</option></term>
+ <listitem>
+ <para>
+ Specify the minimum level of messages that appear on virtual console 3 (<systemitem>tty3</systemitem>). This only affects messages printed to the console; log files will contain messages of all levels. Possible values are <literal>debug</literal>, <literal>info</literal>, <literal>warning</literal>, <literal>error</literal>, or <literal>critical</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-commands-rescue">
1
0
16 Sep '14
commit 3ea96ca60ddd7f0f93b3ded9a30377d0566f008f
Author: Petr Bokoc <pbokoc(a)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:
1
0
[install-guide/F21-rewrite] show_remarks: 1 in publican.cfg (I hope I remember to turn it on before publishing...)
by pbokoc 16 Sep '14
by pbokoc 16 Sep '14
16 Sep '14
commit b73eb31594158f684c9d4ecbb2a2db31629abc6f
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Sep 16 23:40:11 2014 +0200
show_remarks: 1 in publican.cfg (I hope I remember to turn it on before publishing...)
publican.cfg | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
---
diff --git a/publican.cfg b/publican.cfg
index 1e73244..8b6d321 100644
--- a/publican.cfg
+++ b/publican.cfg
@@ -8,3 +8,4 @@ brand: fedora
#web_version_label: UNUSED
mainfile: Installation_Guide
os_ver: .el6
+show_remarks: 1
1
0
[install-guide/F21-rewrite] More/better section introductions in Kickstart Syntax Reference
by pbokoc 16 Sep '14
by pbokoc 16 Sep '14
16 Sep '14
commit 20dcab9228f770c2951858561bae46e634c1c802
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Sep 16 23:17:13 2014 +0200
More/better section introductions in Kickstart Syntax Reference
en-US/Kickstart_Syntax_Reference.xml | 96 +++++++++++++++++++++------------
1 files changed, 61 insertions(+), 35 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index c579422..64f0a11 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -6,26 +6,47 @@
<appendix id="appe-kickstart-syntax-reference">
<title>Kickstart Syntax Reference</title>
<para>
- This appendix describes commands and options available in Kickstart installations. For information about how to automate your installation using Kickstart, see <xref linkend="chap-kickstart-installations" />.
+ This appendix describes commands and options available in Kickstart installations. For general information about Kickstart, see <xref linkend="chap-kickstart-installations" />.
</para>
-
+ <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>
+ <programlisting>
+<command>part / --fstype=xfs --onpart=sda1</command>
+ </programlisting>
+ <para>
+ You could use an entry similar to one of the following:
+ </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>
+ </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 of &PRODUCT;. 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 &PRODUCT; &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. 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>
- The <option>-f</option> option specifies the release to start the comparison with, and the <option>-t</option> option to specify the release to end with. For additional information, see the <systemitem>ksverdiff(1)</systemitem> man page. Also note that you can not use this to display changes in a release that is newer than your system - the version of <package>pykickstart</package> on &PRODUCT; &PREVVER; can not display changes in &PRODUCT; &PRODVER;.
+ The <option>-f</option> option specifies the release to start the comparison with, and the <option>-t</option> option to specify the release to end with. For additional information, see the <systemitem>ksverdiff(1)</systemitem> man page. Also note that you can not use this to display changes in a release that is newer than your system - the version of <package>pykickstart</package> on Fedora &PREVVER; can not display changes in Fedora &PRODVER;.
</para>
<para>
- Additionally, you can review the <citetitle>&PRODUCT; Release Notes</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation</ulink>, for a list of changes.
+ Additionally, you can review the <citetitle>Fedora &PRODVER; Release Notes</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">Fedora Documentation</ulink>, for a list of changes.
</para>
-
+ <note>
+ <para>
+ 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>
- text
+ The following commands control the way Fedora will be installed.
</para>
<section id="sect-kickstart-commands-device">
@@ -75,7 +96,7 @@
<section id="sect-kickstart-commands-storage">
<title>Storage and Partitioning</title>
<para>
- text
+ Commands in this section are used to determine your system's storage options and partitioning.
</para>
<section id="sect-kickstart-commands-autopart">
@@ -181,7 +202,7 @@
<section id="sect-kickstart-commands-network-configuration">
<title>Network Configuration</title>
<para>
- text
+ Commands in this chapter are used for network configuration.
</para>
<section id="sect-kickstart-commands-firewall">
@@ -203,7 +224,7 @@
<section id="sect-kickstart-commands-environment">
<title>Console and Environment</title>
<para>
- text
+ The following commands control the environment of the system after the installation finishes - language, keyboard layouts, or the graphical interface.
</para>
<section id="sect-kickstart-commands-keyboard">
@@ -253,7 +274,7 @@
<section id="sect-kickstart-commands-users-groups">
<title>Users, Groups and Authentication</title>
<para>
- text
+ The commands below are used to control user accounts, groups, and related areas.
</para>
<section id="sect-kickstart-commands-auth">
@@ -303,7 +324,7 @@
<section id="sect-kickstart-commands-installation-environment">
<title>Installation Environment</title>
<para>
- text
+ The following commands control how the system will behave during the installation.
</para>
<section id="sect-kickstart-commands-autostep">
@@ -374,7 +395,7 @@
<section id="sect-kickstart-commands-after">
<title>After the Installation</title>
<para>
- text
+ This section contains commands which control the system's behavior immediately after the installation finishes.
</para>
<section id="sect-kickstart-commands-eula">
@@ -445,7 +466,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>
@@ -470,7 +491,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>repodata/*-comps-<replaceable>variant</replaceable>.<replaceable>architecture</replaceable>.xml</filename> file.
- </para>
+ </para>
</listitem>
</varlistentry>
<varlistentry>
@@ -544,7 +565,7 @@ docbook*
</para>
<programlisting>
<command>%packages --multilib --ignoremissing</command>
- </programlisting>
+ </programlisting>
<varlistentry>
<term>
<option>--nobase</option>
@@ -690,7 +711,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.
@@ -820,6 +841,11 @@ cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
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>
+ <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.
+ </para>
+ </important>
</section>
<section id="sect-kickstart-example-pre">
@@ -835,10 +861,10 @@ cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
hds=""
mymedia=""
for file in /proc/ide/h* do
- mymedia=`cat $file/media`
- if [ $mymedia == "disk" ] ; then
- hds="$hds `basename $file`"
- fi
+ mymedia=`cat $file/media`
+ if [ $mymedia == "disk" ] ; then
+ hds="$hds `basename $file`"
+ fi
done
set $hds
numhd=`echo $#`
@@ -847,21 +873,21 @@ drive2=`echo $hds | cut -d' ' -f2`
#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
- echo "clearpart --all" >> /tmp/part-include
- echo "part /boot --fstype xfs --size 75 --ondisk hda" >> /tmp/part-include
- echo "part / --fstype xfs --size 1 --grow --ondisk hda" >> /tmp/part-include
- echo "part swap --recommended --ondisk $drive1" >> /tmp/part-include
- echo "part /home --fstype xfs --size 1 --grow --ondisk hdb" >> /tmp/part-include
+ #2 drives
+ echo "#partitioning scheme generated in %pre for 2 drives" > /tmp/part-include
+ echo "clearpart --all" >> /tmp/part-include
+ echo "part /boot --fstype xfs --size 75 --ondisk hda" >> /tmp/part-include
+ echo "part / --fstype xfs --size 1 --grow --ondisk hda" >> /tmp/part-include
+ echo "part swap --recommended --ondisk $drive1" >> /tmp/part-include
+ echo "part /home --fstype xfs --size 1 --grow --ondisk hdb" >> /tmp/part-include
else
- #1 drive
- echo "#partitioning scheme generated in %pre for 1 drive" > /tmp/part-include
- echo "clearpart --all" >> /tmp/part-include
- echo "part /boot --fstype xfs --size 75" >> /tmp/part-include
- echo "part swap --recommended" >> /tmp/part-include
- echo "part / --fstype xfs --size 2048" >> /tmp/part-include
- echo "part /home --fstype xfs --size 2048 --grow" >> /tmp/part-include
+ #1 drive
+ echo "#partitioning scheme generated in %pre for 1 drive" > /tmp/part-include
+ echo "clearpart --all" >> /tmp/part-include
+ echo "part /boot --fstype xfs --size 75" >> /tmp/part-include
+ echo "part swap --recommended" >> /tmp/part-include
+ echo "part / --fstype xfs --size 2048" >> /tmp/part-include
+ echo "part /home --fstype xfs --size 2048 --grow" >> /tmp/part-include
fi
<command>%end</command>
</programlisting>
1
0
[install-guide/F21-rewrite] Adding %packages, %pre and %post + examples to Kickstart Syntax Reference
by pbokoc 16 Sep '14
by pbokoc 16 Sep '14
16 Sep '14
commit 5d7688a00e977b8c43fa228bd733bc5fc0799f03
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Sep 16 22:58:46 2014 +0200
Adding %packages, %pre and %post + examples to Kickstart Syntax Reference
en-US/Kickstart_Syntax_Reference.xml | 412 +++++++++++++++++++++++++++++++++-
1 files changed, 405 insertions(+), 7 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index eaba6fb..c579422 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -429,30 +429,347 @@
</section>
<section id="sect-kickstart-packages">
- <title>Package Selection</title>
+ <title>%packages - Package Selection</title>
<para>
- text
+ Use the <command>%packages</command> command to begin a Kickstart section which describes the software packages to be installed.
+ </para>
+ <para>
+ You can specify packages by <firstterm>environment</firstterm>, <firstterm>group</firstterm>, or by their package names. Several environments and groups that contain related packages are defined. See the <filename>repodata/*-comps-<replaceable>variant</replaceable>.<replaceable>architecture</replaceable>.xml</filename> file <remark>TODO: where's comps.xml?</remark>
+ </para>
+ <para>
+ The <filename>*-comps-<replaceable>variant</replaceable>.<replaceable>architecture</replaceable>.xml</filename> file contains a structure describing available environments (marked by the <literal><environment></literal> tag) and groups (the <literal><group></literal> tag). Each entry has an ID, user visibility value, name, description, and package list. If the group is selected for installation, the packages marked <literal>mandatory</literal> in the package list are always installed, the packages marked <literal>default</literal> are installed if they are not specifically excluded, and the packages marked <literal>optional</literal> must be specifically included even when the group is selected.
+ </para>
+ <para>
+ You can specify a package group or environment using either its ID (the <literal><id></literal> tag) or name (the <literal><name></literal> tag).
</para>
+ <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>
+ </important>
+ <important>
+ <para>
+ <application>Initial Setup</application> does not run after a system is installed from a Kickstart file unless a desktop environment and the <application>X Window System</application> were included in the installation and graphical login was enabled. This means that by default, no users except for <systemitem class="username">root</systemitem> will be created. You can either create a user with the <option>user</option> option in the Kickstart file before installing additional systems from it (see <xref linkend="sect-kickstart-commands-user" /> for details) or log into the installed system with a virtual console as <systemitem class="username">root</systemitem> and add users with the <command>useradd</command> command.
+ </para>
+ </important>
+ <para>
+ The <command>%packages</command> section must end with the <command>%end</command> command.
+ </para>
+ <variablelist>
+ <title>Specifying Environments, Groups and Packages</title>
+ <varlistentry>
+ <term>Specifying an Environment</term>
+ <listitem>
+ <para>
+ In addition to groups, you specify an entire environment to be installed:
+ </para>
+ <programlisting>
+<command>%packages</command>
+@^Infrastructure Server
+<command>%end</command>
+ </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>repodata/*-comps-<replaceable>variant</replaceable>.<replaceable>architecture</replaceable>.xml</filename> file.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Specifying Groups</term>
+ <listitem>
+ <para>
+ 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-<replaceable>variant</replaceable>.<replaceable>architecture</replaceable>.xml</filename> file. For example:
+ </para>
+ <programlisting>
+<command>%packages</command>
+@X Window System
+@Desktop
+@Sound and Video
+<command>%end</command>
+ </programlisting>
+ <para>
+ 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-<replaceable>variant</replaceable>.<replaceable>architecture</replaceable>.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>
+ <varlistentry>
+ <term>Specifying Individual Packages</term>
+ <listitem>
+ <para>
+ 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>
+sqlite
+curl
+aspell
+docbook*
+<command>%end</command>
+ </programlisting>
+ <para>
+ The <literal>docbook*</literal> entry includes the packages <package>docbook-dtds</package>, <package>docbook-simple</package>, <package>docbook-slides</package> and others that match the pattern represented with the wildcard.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Excluding Environments, Groups, or Packages</term>
+ <listitem>
+ <para>
+ 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
+-autofs
+-ipa*fonts
+<command>%end</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ </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.
+ </para>
+ </important>
+ <para>
+ You can change the default behavior of the <command>%packages</command> section by using several options. Some options work for the entire package selection, others are used with only specific groups.
+ </para>
+ <variablelist>
+ <title>Common Package Selection Options</title>
+ <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>
+ <varlistentry>
+ <term>
+ <option>--nobase</option>
+ </term>
+ <listitem>
+ <para>
+ Do not install the <literal>@Base</literal> group. Use this option to perform a minimal installation, for example, for a single-purpose server or desktop appliance.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--ignoremissing</option>
+ </term>
+ <listitem>
+ <para>
+ Ignore any packages, groups and environments missing in the installation source, instead of halting the installation to ask if the installation should be aborted or continued.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--excludedocs</option>
+ </term>
+ <listitem>
+ <para>
+ Do not install any documentation contained within packages. In most cases, this will exclude any files normally installed in the <filename class="directory">/usr/share/doc*</filename> directory, but the specific files to be excluded depend on individual packages.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--multilib</option>
+ </term>
+ <listitem>
+ <para>
+ Configure the installed system for multilib packages (that is, to allow installing 32-bit packages on a 64-bit system) and install packages specified in this section as such.
+ </para>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <variablelist>
+ <title>Options for Specific Package Groups</title>
+ <para>
+ The options in this list only apply to a single package group. Instead of using them at the <command>%packages</command> command in the Kickstart file, append them to the group name. For example:
+ </para>
+ <programlisting>
+<command>%packages</command>
+@Graphical Internet --optional
+<command>%end</command>
+ </programlisting>
+ <varlistentry>
+ <term>
+ <option>--nodefaults</option>
+ </term>
+ <listitem>
+ <para>
+ Only install the group's mandatory packages, not the default selections.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--optional</option>
+ </term>
+ <listitem>
+ <para>
+ Install packages marked as optional in the group definition in the <filename>*-comps-<replaceable>variant</replaceable>.<replaceable>architecture</replaceable>.xml</filename> file, in addition to installing the default selections.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section id="sect-kickstart-preinstall">
- <title>Pre-installation Script</title>
+ <title>%pre - Pre-installation Script</title>
<para>
- text
+ You can add commands to run on the system immediately after the Kickstart file has been parsed, but before the installation begins. This section must be placed towards the end of the Kickstart file, after the actual Kickstart commands, and must start with <command>%pre</command> and end with <command>%end</command>. If your Kickstart file also includes a <command>%post</command> section, the order in which the <command>%pre</command> and <command>%post</command> sections are included does not matter.
+ </para>
+ <para>
+ You can access the network in the <command>%pre</command> section. However, the <firstterm>name service</firstterm> has not been configured at this point, so only IP addresses work, not URLs.
+ </para>
+ <para>
+ The pre-installation script section of Kickstart <emphasis>cannot</emphasis> manage multiple install trees or source media. This information must be included for each created Kickstart file, as the pre-installation script occurs during the second stage of the installation process.
+ </para>
+ <note>
+ <para>
+ Unlike the post-installation script, the pre-installation script is not run in the <systemitem>chroot</systemitem> environment.
+ </para>
+ </note>
+ <para>
+ The following options can be used to change the behavior of pre-installation scripts. To use an option, append it to the <command>%pre</command> line at the beginning of the script. For example:
+ </para>
+ <programlisting>
+<command>%pre --interpreter=/usr/bin/python</command>
+--- Python script omitted --
+<command>%end</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--interpreter=</option></term>
+ <listitem>
+ <para>
+ Allows you to specify a different scripting language, such as Python. Any scripting language available on the system can be used; in most cases, these will be <systemitem>/usr/bin/sh</systemitem>, <systemitem>/usr/bin/bash</systemitem>, and <systemitem>/usr/bin/python</systemitem>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--erroronfail</option></term>
+ <listitem>
+ <para>
+ Display an error and halt the installation if the script fails. The error message will direct you to where the cause of the failure is logged.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--log=</option></term>
+ <listitem>
+ <para>
+ Logs the script's output into the specified log file. For example:
+ </para>
+ <programlisting>
+<command>%pre --log=/mnt/sysimage/root/ks-pre.log</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ For an example of a pre-installation script, see <xref linkend="exam-kickstart-pre-script" />.
</para>
</section>
<section id="sect-kickstart-postinstall">
- <title>Post-installation Script</title>
+ <title>%post - Post-installation Script</title>
<para>
- text
+ You have the option of adding commands to run on the system once the installation is complete, but before the system is rebooted for the first time. This section must be placed towards the end of the Kickstart file, after the actual Kickstart commands, and must start with <command>%post</command> and end with <command>%end</command>. If your Kickstart file also includes a <command>%pre</command> section, the order of the <command>%pre</command> and <command>%post</command> sections does not matter.
+ </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>
+ <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.
+ </para>
+ </important>
+ <para>
+ The following options can be used to change the behavior of post-installation scripts. To use an option, append it to the <command>%post</command> line at the beginning of the script. For example:
+ </para>
+ <programlisting>
+<command>%post --interpreter=/usr/bin/python</command>
+--- Python script omitted --
+<command>%end</command>
+ </programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--interpreter=</option></term>
+ <listitem>
+ <para>
+ Allows you to specify a different scripting language, such as Python. For example:
+ </para>
+ <programlisting>
+<command>%post --interpreter=/usr/bin/python</command>
+ </programlisting>
+ <para>
+ Any scripting language available on the system can be used; in most cases, these will be <systemitem>/usr/bin/sh</systemitem>, <systemitem>/usr/bin/bash</systemitem>, and <systemitem>/usr/bin/python</systemitem>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--nochroot</option></term>
+ <listitem>
+ <para>
+ Allows you to specify commands that you would like to run outside of the chroot environment.
+ </para>
+ <para>
+ The following example copies the file <filename>/etc/resolv.conf</filename> to the file system that was just installed.
+ </para>
+ <programlisting>
+<command>%post --nochroot</command>
+cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
+<command>%end</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--erroronfail</option></term>
+ <listitem>
+ <para>
+ Display an error and halt the installation if the script fails. The error message will direct you to where the cause of the failure is logged.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--log=</option></term>
+ <listitem>
+ <para>
+ Logs the script's output into the specified log file. Note that the path of the log file must take into account whether or not you use the <option>--nochroot</option> option. For example, without <option>--nochroot</option>:
+ </para>
+ <programlisting>
+<command>%post --log=/root/ks-post.log</command>
+ </programlisting>
+ <para>
+ with <option>--nochroot</option>:
+ </para>
+ <programlisting>
+<command>%post --nochroot --log=/mnt/sysimage/root/ks-post.log</command>
+ </programlisting>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ For an example of a post-installation script, see <xref linkend="sect-kickstart-example-post" />.
</para>
</section>
<section id="sect-kickstart-examples">
<title>Example Kickstart Configurations</title>
- <section id="sect-kickstart-partitioning-example">
+ <section id="sect-kickstart-example-advanced-partitioning">
<title>Advanced Partitioning Example</title>
<para>
The following is an integrated example showing the <command>clearpart</command>, <command>zerombr</command>, <command>part</command>, <command>raid</command>, <command>volgroup</command>, and <command>logvol</command> Kickstart options in action:
@@ -504,6 +821,87 @@
</para>
</example>
</section>
+
+ <section id="sect-kickstart-example-pre">
+ <title>Example Pre-installation Script</title>
+ <para>
+ The following is an example <command>%pre</command> section:
+ </para>
+ <example id="exam-kickstart-pre-script">
+ <title>Sample %pre Script</title>
+ <programlisting>
+<command>%pre</command>
+#!/bin/sh
+hds=""
+mymedia=""
+for file in /proc/ide/h* do
+ mymedia=`cat $file/media`
+ if [ $mymedia == "disk" ] ; then
+ hds="$hds `basename $file`"
+ fi
+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
+if [ $numhd == "2" ] ; then
+ #2 drives
+ echo "#partitioning scheme generated in %pre for 2 drives" > /tmp/part-include
+ echo "clearpart --all" >> /tmp/part-include
+ echo "part /boot --fstype xfs --size 75 --ondisk hda" >> /tmp/part-include
+ echo "part / --fstype xfs --size 1 --grow --ondisk hda" >> /tmp/part-include
+ echo "part swap --recommended --ondisk $drive1" >> /tmp/part-include
+ echo "part /home --fstype xfs --size 1 --grow --ondisk hdb" >> /tmp/part-include
+else
+ #1 drive
+ echo "#partitioning scheme generated in %pre for 1 drive" > /tmp/part-include
+ echo "clearpart --all" >> /tmp/part-include
+ echo "part /boot --fstype xfs --size 75" >> /tmp/part-include
+ echo "part swap --recommended" >> /tmp/part-include
+ echo "part / --fstype xfs --size 2048" >> /tmp/part-include
+ echo "part /home --fstype xfs --size 2048 --grow" >> /tmp/part-include
+fi
+<command>%end</command>
+ </programlisting>
+ <para>
+ This script determines the number of hard drives in the system and writes a text file with a different partitioning scheme depending on whether it has one or two drives. Instead of having a set of partitioning commands in the Kickstart file, include the following line:
+ </para>
+ <programlisting>
+<command>%include /tmp/part-include</command>
+ </programlisting>
+ <para>
+ The partitioning commands selected in the script will be used.
+ </para>
+ </example>
+ </section>
+
+ <section id="sect-kickstart-example-post">
+ <title>Example Post-installation Script</title>
+ <para>
+ The following is an example <command>%post</command> section:
+ </para>
+ <example id="exam-kickstart-post-script">
+ <title>Sample %post Script</title>
+ <programlisting>
+# Start of the %post section with logging into /root/ks-post.log
+<command>%post --log=/root/ks-post.log</command>
+
+# Mount an NFS share
+mkdir /mnt/temp
+mount -o nolock 10.10.0.2:/usr/new-machines /mnt/temp
+openvt -s -w -- /mnt/temp/runme
+umount /mnt/temp
+
+# End of the %post section
+<command>%end</command>
+ </programlisting>
+ <para>
+ The above example mounts an NFS share and executes a script named <filename>runme</filename> located at <filename>/usr/new-machines/</filename> on the share. Note that NFS file locking is <emphasis>not</emphasis> supported while in Kickstart mode, therefore the <option>-o nolock</option> option is required.
+ </para>
+ </example>
+ </section>
</section>
1
0
[install-guide/F21-rewrite] More changes to the GUI install chapter's structure - order & titles
by pbokoc 16 Sep '14
by pbokoc 16 Sep '14
16 Sep '14
commit fa638dbb7fbe0e1606cfc9f258fed41700f92626
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Sep 16 18:10:52 2014 +0200
More changes to the GUI install chapter's structure - order & titles
en-US/FilterSpoke.xml | 2 +-
en-US/Installing_Using_Anaconda.xml | 2 +-
en-US/KeyboardSpoke.xml | 4 ++--
en-US/NetworkSpoke.xml | 2 +-
en-US/PasswordSpoke.xml | 2 +-
en-US/UserSpoke.xml | 2 +-
en-US/WelcomeSpoke.xml | 4 ++--
7 files changed, 9 insertions(+), 9 deletions(-)
---
diff --git a/en-US/FilterSpoke.xml b/en-US/FilterSpoke.xml
index e9a7407..7b0d1c3 100644
--- a/en-US/FilterSpoke.xml
+++ b/en-US/FilterSpoke.xml
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<section id="sect-installation-gui-installation-destination">
- <title>Installation Destination</title>
+ <title>Installation Destination - Specialized & Network Disks</title>
<para>
text
</para>
diff --git a/en-US/Installing_Using_Anaconda.xml b/en-US/Installing_Using_Anaconda.xml
index fa7444c..708ddeb 100644
--- a/en-US/Installing_Using_Anaconda.xml
+++ b/en-US/Installing_Using_Anaconda.xml
@@ -66,8 +66,8 @@
<xi:include href="SourceSpoke.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="SoftwareSpoke.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="StorageSpoke.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="CustomSpoke.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="FilterSpoke.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="NetworkSpoke.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="PasswordSpoke.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="UserSpoke.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
diff --git a/en-US/KeyboardSpoke.xml b/en-US/KeyboardSpoke.xml
index 2ef203c..944b3ec 100644
--- a/en-US/KeyboardSpoke.xml
+++ b/en-US/KeyboardSpoke.xml
@@ -3,8 +3,8 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
%BOOK_ENTITIES;
]>
-<section id="sect-installation-gui-keyboard-configuration">
- <title>Keyboard</title>
+<section id="sect-installation-gui-keyboard-layout">
+ <title>Keyboard Layout</title>
<para>
text
</para>
diff --git a/en-US/NetworkSpoke.xml b/en-US/NetworkSpoke.xml
index e54cdcf..649076a 100644
--- a/en-US/NetworkSpoke.xml
+++ b/en-US/NetworkSpoke.xml
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<section id="sect-installation-gui-network-configuration">
- <title>Network Configuration</title>
+ <title>Network & Hostname</title>
<para>
text
</para>
diff --git a/en-US/PasswordSpoke.xml b/en-US/PasswordSpoke.xml
index f14433c..b7e918f 100644
--- a/en-US/PasswordSpoke.xml
+++ b/en-US/PasswordSpoke.xml
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<section id="sect-installation-gui-root-password">
- <title>Create a Root Password</title>
+ <title>Root Password</title>
<para>
text
</para>
diff --git a/en-US/UserSpoke.xml b/en-US/UserSpoke.xml
index 106c818..c2760f2 100644
--- a/en-US/UserSpoke.xml
+++ b/en-US/UserSpoke.xml
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<section id="sect-installation-gui-create-user">
- <title>Create a User</title>
+ <title>Create User</title>
<para>
text
</para>
diff --git a/en-US/WelcomeSpoke.xml b/en-US/WelcomeSpoke.xml
index 70255d3..8809a8c 100644
--- a/en-US/WelcomeSpoke.xml
+++ b/en-US/WelcomeSpoke.xml
@@ -3,8 +3,8 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
%BOOK_ENTITIES;
]>
-<section id="sect-installation-gui-language-selection">
- <title>Language Selection</title>
+<section id="sect-installation-gui-welcome">
+ <title>Welcome Screen and Language Selection</title>
<para>
text
</para>
1
0