[install-guide/F21-rewrite] Adding info about ksverdiff into Kickstart Syntax Reference
by pbokoc
commit dd890589d9a63760c600a3d864ccc29763c66ba3
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Sep 16 00:16:44 2014 +0200
Adding info about ksverdiff into Kickstart Syntax Reference
en-US/Kickstart_Syntax_Reference.xml | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index 057d44e..2cd7cb0 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -9,6 +9,19 @@
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" />.
</para>
+ <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:
+ </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;.
+ </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.
+ </para>
+
<section id="sect-kickstart-commands-installation">
<title>Installation Methods and Sources</title>
<para>
9 years, 7 months
[install-guide/F21-rewrite] Adding Kickstart Installations
by pbokoc
commit e9012635f7c875a242f6a97e0a3d6428a9a2c743
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Sep 15 23:09:22 2014 +0200
Adding Kickstart Installations
en-US/Kickstart_Installations.xml | 216 ++++++++++++++++++++++++++-----------
1 files changed, 153 insertions(+), 63 deletions(-)
---
diff --git a/en-US/Kickstart_Installations.xml b/en-US/Kickstart_Installations.xml
index ece14fe..2fc9c5f 100644
--- a/en-US/Kickstart_Installations.xml
+++ b/en-US/Kickstart_Installations.xml
@@ -4,74 +4,164 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-kickstart-installations">
- <title>Automating the Installation with Kickstart</title>
- <para>
- intro text
- </para>
+ <title>Automating the Installation with Kickstart</title>
+ <para>
+ Kickstart installations offer a means to automate the installation process, either partially or fully. Kickstart files contain answers to all questions normally asked by the installation program, such as what time zone do you want the system to use, how should the drives be partitioned or which packages should be installed. Providing a prepared Kickstart file when the installation begins therefore allows the you to perform the installation automatically, without need for any intervention from the user. This is especially useful when deploying &PRODUCT; on a large number of systems at once.
+ </para>
+ <para>
+ All Kickstart scripts and the log files of their execution are stored in the <filename>/tmp</filename> directory to assist with debugging installation issues.
+ </para>
- <section id="sect-kickstart-introduction">
- <title>Introduction to Kickstart Installations</title>
- <para>
- text
- </para>
- </section>
+ <section id="sect-kickstart-howto">
+ <title>How to Perform a Kickstart Installation</title>
+ <para>
+ Kickstart installations can be performed using a local DVD, a local hard drive, or via NFS, FTP, HTTP, or HTTPS.
+ </para>
+ <para>
+ To use Kickstart, you must:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Create a Kickstart file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Create boot media or configure a network boot (PXE) server which will be used to begin the installation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Make the Kickstart file available on removable media, a hard drive, or a network location.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Start the Kickstart installation by booting the installer and using a boot option to tell the installer where to find the Kickstart file.
+ </para>
+ </listitem>
+ </orderedlist>
+ <para>
+ This chapter explains these steps in detail.
+ </para>
- <section id="sect-kickstart-howto">
- <title>How to Perform a Kickstart Installation</title>
- <para>
- text
- </para>
+ <section id="sect-kickstart-file-create">
+ <title>Creating a Kickstart File</title>
+ <para>
+ The Kickstart file itself is a plain text file, containing keywords listed in <xref linkend="appe-kickstart-syntax-reference" />, which serve as directions for the installation. Any text editor able to save files as ASCII text (such as <application>Gedit</application> or <application>vim</application> on Linux systems or <application>Notepad</application> on Windows systems) can be used to create and edit Kickstart files.
+ </para>
+ <para>
+ The recommended approach to creating Kickstart files is to perform a manual installation on one system first. After the installation completes, all choices made during the installation are saved into a file named <filename>anaconda-ks.cfg</filename>, located in the <filename class="directory">/root/</filename> directory on the installed system. You can then copy this file, make any changes you need, and use the resulting configuration file in further installations.
+ </para>
+ <para>
+ When creating a Kickstart file, keep in mind the following:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Lines starting with a pound sign (<literal>#</literal>) are treated as comments and are ignored.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Sections must be specified <emphasis>in order</emphasis>. Items within the sections do not have to be in a specific order unless otherwise specified. The correct section order is:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The command section which contains actual Kickstart commands and options as listed in <xref linkend="appe-kickstart-syntax-reference" />. Note that some commands, such as <command>install</command>, are mandatory, but most commands are optional.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <command>%packages</command> section which contains a list of packages and package groups to be installed. See <xref linkend="sect-kickstart-packages" /> for details.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <command>%pre</command> and <command>%post</command> sections, containing a pre-installation and post-installation scripts. These two sections can be in any order and are not mandatory. See <xref linkend="sect-kickstart-preinstall" /> and <xref linkend="sect-kickstart-postinstall" /> for details.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <important>
+ <para>
+ The <command>%packages</command>, <command>%pre</command> and <command>%post</command> sections must end with <command>%end</command>, otherwise the installation program will refuse the Kickstart file. The main command section has no special ending statement.
+ </para>
+ </important>
+ </listitem>
+ <listitem>
+ <para>
+ Omitting any required item results in the installation program prompting the user for an answer to the related item, just as the user would be prompted during a typical installation. Once the answer is given, the installation will continue. Note that if the system you are installing has no display, you will not be able to see the prompt, and the installation will appear to have failed.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
- <section id="sect-kickstart-file-create">
- <title>Creating a Kickstart File</title>
- <para>
- text
- </para>
- </section>
+ <section id="sect-kickstart-verify">
+ <title>Verifying the Kickstart File</title>
+ <para>
+ When creating or customizing your kickstart file, it is useful to verify that it is valid before attempting to use it in an installation. &PRODUCT; includes the <application>ksvalidator</application> command line utility which can be used to do this. This tool is a part of the <package>pykickstart</package> package. To install this package, execute the following command:
+ </para>
+ <screen>
+<prompt>#</prompt> <command>yum install pykickstart</command>
+ </screen>
+ <para>
+ After installing the package, you can validate a Kickstart file using the following command:
+ </para>
+ <screen>
+<prompt>$</prompt> <command>ksvalidator <replaceable>/path/to/kickstart.ks</replaceable></command>
+ </screen>
+ <para>
+ Replace <replaceable>/path/to/kickstart.ks</replaceable> with the path to the Kickstart file you want to verify.
+ </para>
+ <para>
+ For more information about this tool, see the <systemitem>ksvalidator(1)</systemitem> man page.
+ </para>
+ <important>
+ <para>
+ Keep in mind that the validation tool has its limitations. The Kickstart file can be very complicated; <application>ksvalidator</application> can make sure the syntax is correct and that the file does not include removed options, but it cannot guarantee the installation will be successful. It also does not attempt to validate the <command>%pre</command>, <command>%post</command> and <command>%packages</command> sections of the Kickstart file.
+ </para>
+ </important>
+ </section>
- <section id="sect-kickstart-verify">
- <title>Verifying the Kickstart File</title>
- <para>
- text
- </para>
- </section>
+ <section id="sect-kickstart-making-available">
+ <title>Making the Kickstart File Available</title>
+ <para>
+ Once you create a Kickstart file, you can place it in one of the following locations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ On <emphasis>removable media</emphasis>, such as a DVD or USB flash drive connected to the installation system
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ On a <emphasis>hard drive</emphasis> connected to the installation system
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ On a <emphasis>network share</emphasis> reachable from the installation system
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Normally, a Kickstart file is copied to removable media or a hard drive, or made available on the network. Placing the file in a network location complements the usual approach to Kickstart installations, which is also network-based: the system is booted using a PXE server, the Kickstart file is downloaded from a network share, and software packages specified in the file are downloaded from remote repositories.
+ </para>
+ <para>
+ <remark>TODO: link this with the PXE chapter, and maybe provide a procedure about how to create a new partition on a bootable USB with a netinst iso and put a Kickstart on it</remark>
+ </para>
+ </section>
- <section id="sect-kickstart-making-available">
- <title>Making the Kickstart File Available</title>
- <para>
- text
- </para>
- </section>
+ <section id="sect-kickstart-installation-starting">
+ <title>Starting the Kickstart Installation</title>
+ <para>
+ Once you have everything ready - you have created a valid Kickstart file and you have either local boot media or a PXE server available, you can start the Kickstart installation. You need to use the <option>inst.ks=</option> boot option either in the boot menu (when booting from local media), or add this option to your PXE server configuration. For information about boot options used in Kickstart installations, see <xref linkend="sect-boot-options-kickstart" />.
+ </para>
+ </section>
- <section id="sect-kickstart-installation-source">
- <title>Making the Installation Source Available</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-kickstart-installation-starting">
- <title>Starting the Kickstart Installation</title>
- <para>
- text
- </para>
-
- <section id="sect-kickstart-installation-starting-manual">
- <title>Starting the Kickstart Installation Manually </title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-kickstart-installation-starting-automatic">
- <title>Starting the Kickstart Installation Automatically</title>
- <para>
- text
- </para>
- </section>
-
- </section>
-
- </section>
+ </section>
</chapter>
9 years, 7 months
[install-guide/F21-rewrite] New structure for Kickstart syntax, take 2
by pbokoc
commit 7701f9a12ab80343932225552ede908836c18ac2
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Sep 15 20:08:40 2014 +0200
New structure for Kickstart syntax, take 2
en-US/Boot_Options.xml | 6 +-
en-US/Kickstart_Syntax_Reference.xml | 253 ++++++++++++++++++++--------------
en-US/VNC_Installations.xml | 4 +-
3 files changed, 152 insertions(+), 111 deletions(-)
---
diff --git a/en-US/Boot_Options.xml b/en-US/Boot_Options.xml
index 37c085e..cacc661 100644
--- a/en-US/Boot_Options.xml
+++ b/en-US/Boot_Options.xml
@@ -314,7 +314,7 @@
<term><option>inst.lang=</option></term>
<listitem>
<para>
- Sets the language to be used during the installation. Language codes are the same as the ones used in the <command>lang</command> Kickstart command as described in <xref linkend="sect-kickstart-commands" />. On systems where the <package>system-config-language</package> package is installed, a list of valid values can also be find in <filename>/usr/share/system-config-language/locale-list</filename>.
+ Sets the language to be used during the installation. Language codes are the same as the ones used in the <command>lang</command> Kickstart command as described in <xref linkend="appe-kickstart-syntax-reference" />. On systems where the <package>system-config-language</package> package is installed, a list of valid values can also be find in <filename>/usr/share/system-config-language/locale-list</filename>.
</para>
</listitem>
</varlistentry>
@@ -369,7 +369,7 @@
<term><option>inst.keymap=</option></term>
<listitem>
<para>
- Specifies the keyboard layout to be used by the installation program. Layout codes are the same as the ones used in the <command>keyboard</command> Kickstart command as described in <xref linkend="sect-kickstart-commands" />.
+ Specifies the keyboard layout to be used by the installation program. Layout codes are the same as the ones used in the <command>keyboard</command> Kickstart command as described in <xref linkend="appe-kickstart-syntax-reference" />.
</para>
</listitem>
</varlistentry>
@@ -449,7 +449,7 @@
</para>
<note>
<para>
- During the installation, the <systemitem class="username">root</systemitem> account has no password by default. You can set a root password to be used during the installation with the <command>sshpw</command> Kickstart command as described in <xref linkend="sect-kickstart-commands" />.
+ During the installation, the <systemitem class="username">root</systemitem> account has no password by default. You can set a root password to be used during the installation with the <command>sshpw</command> Kickstart command as described in <xref linkend="appe-kickstart-syntax-reference" />.
</para>
</note>
</listitem>
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index 0667de1..057d44e 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -6,87 +6,88 @@
<appendix id="appe-kickstart-syntax-reference">
<title>Kickstart Syntax Reference</title>
<para>
- intro text
+ 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" />.
</para>
- <section id="sect-kickstart-syntax-changes">
- <title>Changes in Kickstart Syntax</title>
- <para>
- text
- </para>
- </section>
-
- <section id="sect-kickstart-commands">
- <title>Kickstart Commands and Options</title>
+ <section id="sect-kickstart-commands-installation">
+ <title>Installation Methods and Sources</title>
<para>
text
</para>
- <section id="sect-kickstart-commands-auth">
- <title>auth - Configure Authentication</title>
+ <section id="sect-kickstart-commands-device">
+ <title>device - Install Extra Device Drivers</title>
<para>
text
</para>
</section>
-
- <section id="sect-kickstart-commands-autopart">
- <title>autopart - Automatic Partitioning</title>
+
+ <section id="sect-kickstart-commands-driverdisk">
+ <title>driverdisk - Use a Driver Disk</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-autostep">
- <title>autostep - Go Through Every Screen Automatically</title>
+ <section id="sect-kickstart-commands-install">
+ <title>install - Configure Installation Method</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-bootloader">
- <title>bootloader - Configure Boot Loader</title>
+ <section id="sect-kickstart-commands-mediacheck">
+ <title>mediacheck - Verify Installation Media Integrity</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-btrfs">
- <title>btrfs - Create Btrfs Volume or Subvolume</title>
+ <section id="sect-kickstart-commands-ostree">
+ <title>ostree - Install from an OSTree</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-clearpart">
- <title>clearpart - Remove All Existing Partitions</title>
+ <section id="sect-kickstart-commands-repo">
+ <title>repo - Configure Instalaltion Source</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-cmdline">
- <title>cmdline - Perform Installation in Command Line Mode</title>
+ </section>
+
+ <section id="sect-kickstart-commands-storage">
+ <title>Storage and Partitioning</title>
+ <para>
+ text
+ </para>
+
+ <section id="sect-kickstart-commands-autopart">
+ <title>autopart - Automatic Partitioning</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-device">
- <title>device - Install Extra Device Drivers</title>
+ <section id="sect-kickstart-commands-bootloader">
+ <title>bootloader - Configure Boot Loader</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-driverdisk">
- <title>driverdisk - Use a Driver Disk</title>
+ <section id="sect-kickstart-commands-btrfs">
+ <title>btrfs - Create Btrfs Volume or Subvolume</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-eula">
- <title>eula - Accept the License Agreement</title>
+ <section id="sect-kickstart-commands-clearpart">
+ <title>clearpart - Remove All Existing Partitions</title>
<para>
text
</para>
@@ -99,134 +100,158 @@
</para>
</section>
- <section id="sect-kickstart-commands-firewall">
- <title>firewall - Configure Firewall</title>
+ <section id="sect-kickstart-commands-ignoredisk">
+ <title>ignoredisk - Ignore Specified Disks</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-firstboot">
- <title>firstboot - Enable or Disable Initial Setup</title>
+ <section id="sect-kickstart-commands-iscsi">
+ <title>iscsi - Configure iSCSI Devices</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-group">
- <title>group - Create User Group</title>
+ <section id="sect-kickstart-commands-iscsiname">
+ <title>iscsiname - Assign Name to iSCSI Device</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-graphical">
- <title>graphical - Perform Installation in Graphical Mode</title>
+ <section id="sect-kickstart-commands-logvol">
+ <title>logvol - Create LVM Logical Volume</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-halt">
- <title>halt - Halt System After Installation</title>
+ <section id="sect-kickstart-commands-part">
+ <title>part - Create Physical Partition</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-ignoredisk">
- <title>ignoredisk - Ignore Specified Disks</title>
+ <section id="sect-kickstart-commands-raid">
+ <title>raid - Create Software RAID</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-install">
- <title>install - Configure Installation Method</title>
+ <section id="sect-kickstart-commands-volgroup">
+ <title>volgroup - Create LVM Volume Group</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-iscsi">
- <title>iscsi - Configure iSCSI Devices</title>
+ <section id="sect-kickstart-commands-zerombr">
+ <title>zerombr - Reinitialize Partition Tables</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-iscsiname">
- <title>iscsiname - Assign Name to iSCSI Device</title>
+ <section id="sect-kickstart-commands-zfcp">
+ <title>zfcp - Configure Fibre Channel Device</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-keyboard">
- <title>keyboard - Configure Keyboard Layouts</title>
+ </section>
+
+ <section id="sect-kickstart-commands-network-configuration">
+ <title>Network Configuration</title>
+ <para>
+ text
+ </para>
+
+ <section id="sect-kickstart-commands-firewall">
+ <title>firewall - Configure Firewall</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-lang">
- <title>lang - Configure Language During Installation</title>
+ <section id="sect-kickstart-commands-network">
+ <title>network - Configure Network Interfaces</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-logging">
- <title>logging - Configure Error Logging During Installation</title>
+ </section>
+
+ <section id="sect-kickstart-commands-environment">
+ <title>Console and Environment</title>
+ <para>
+ text
+ </para>
+
+ <section id="sect-kickstart-commands-keyboard">
+ <title>keyboard - Configure Keyboard Layouts</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-logvol">
- <title>logvol - Create LVM Logical Volume</title>
+ <section id="sect-kickstart-commands-lang">
+ <title>lang - Configure Language During Installation</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-mediacheck">
- <title>mediacheck - Verify Installation Media Integrity</title>
+ <section id="sect-kickstart-commands-services">
+ <title>services - Configure Services</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-network">
- <title>network - Configure Network Interfaces</title>
+ <section id="sect-kickstart-commands-skipx">
+ <title>skipx - Do Not Configure X Window System</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-ostree">
- <title>ostree - Install from an OSTree</title>
+ <section id="sect-kickstart-commands-timezone">
+ <title>timezone - Configure Time Zone</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-part">
- <title>part - Create Physical Partition</title>
+ <section id="sect-kickstart-commands-xconfig">
+ <title>xconfig - Configure X Window System</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-poweroff">
- <title>poweroff - Power Off After Installation</title>
+ </section>
+
+ <section id="sect-kickstart-commands-users-groups">
+ <title>Users, Groups and Authentication</title>
+ <para>
+ text
+ </para>
+
+ <section id="sect-kickstart-commands-auth">
+ <title>auth - Configure Authentication</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-raid">
- <title>raid - Create Software RAID</title>
+ <section id="sect-kickstart-commands-group">
+ <title>group - Create User Group</title>
<para>
text
</para>
@@ -239,57 +264,65 @@
</para>
</section>
- <section id="sect-kickstart-commands-reboot">
- <title>reboot - Reboot After Installation</title>
+ <section id="sect-kickstart-commands-rootpw">
+ <title>rootpw - Set Root Password</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-repo">
- <title>repo - Configure Instalaltion Source</title>
+ <section id="sect-kickstart-commands-selinux">
+ <title>selinux - Configure SELinux</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-rescue">
- <title>rescue - Rescue Mode</title>
+ <section id="sect-kickstart-commands-user">
+ <title>user - Create User Account</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-rootpw">
- <title>rootpw - Set Root Password</title>
+ </section>
+
+ <section id="sect-kickstart-commands-installation-environment">
+ <title>Installation Environment</title>
+ <para>
+ text
+ </para>
+
+ <section id="sect-kickstart-commands-autostep">
+ <title>autostep - Go Through Every Screen Automatically</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-selinux">
- <title>selinux - Configure SELinux</title>
+ <section id="sect-kickstart-commands-cmdline">
+ <title>cmdline - Perform Installation in Command Line Mode</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-services">
- <title>services - Configure Services</title>
+ <section id="sect-kickstart-commands-graphical">
+ <title>graphical - Perform Installation in Graphical Mode</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-shutdown">
- <title>shutdown - Shut Down After Installation</title>
+ <section id="sect-kickstart-commands-logging">
+ <title>logging - Configure Error Logging During Installation</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-skipx">
- <title>skipx - Do Not Configure X Window System</title>
+ <section id="sect-kickstart-commands-rescue">
+ <title>rescue - Rescue Mode</title>
<para>
text
</para>
@@ -309,13 +342,6 @@
</para>
</section>
- <section id="sect-kickstart-commands-timezone">
- <title>timezone - Configure Time Zone</title>
- <para>
- text
- </para>
- </section>
-
<section id="sect-kickstart-commands-unsupported_hardware">
<title>unsupported_hardware - Suppress Unsupported Hardware Alerts</title>
<para>
@@ -323,50 +349,58 @@
</para>
</section>
- <section id="sect-kickstart-commands-user">
- <title>user - Create User Accound</title>
+ <section id="sect-kickstart-commands-vnc">
+ <title>vnc - Configure VNC Access</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-vnc">
- <title>vnc - Configure VNC Access</title>
+ </section>
+
+ <section id="sect-kickstart-commands-after">
+ <title>After the Installation</title>
+ <para>
+ text
+ </para>
+
+ <section id="sect-kickstart-commands-eula">
+ <title>eula - Accept the License Agreement</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-volgroup">
- <title>volgroup - Create LVM Volume Group</title>
+ <section id="sect-kickstart-commands-firstboot">
+ <title>firstboot - Enable or Disable Initial Setup</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-xconfig">
- <title>xconfig - Configure X Window System</title>
+ <section id="sect-kickstart-commands-halt">
+ <title>halt - Halt System After Installation</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-zerombr">
- <title>zerombr - Reinitialize Partition Tables</title>
+ <section id="sect-kickstart-commands-poweroff">
+ <title>poweroff - Power Off After Installation</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-zfcp">
- <title>zfcp - Configure Fibre Channel Device</title>
+ <section id="sect-kickstart-commands-reboot">
+ <title>reboot - Reboot After Installation</title>
<para>
text
</para>
</section>
- <section id="sect-kickstart-commands-include">
- <title>%include - Include Contents of Another File</title>
+ <section id="sect-kickstart-commands-shutdown">
+ <title>shutdown - Shut Down After Installation</title>
<para>
text
</para>
@@ -374,6 +408,13 @@
</section>
+ <section id="sect-kickstart-commands-include">
+ <title>%include - Include Contents of Another File</title>
+ <para>
+ text
+ </para>
+ </section>
+
<section id="sect-kickstart-packages">
<title>Package Selection</title>
<para>
diff --git a/en-US/VNC_Installations.xml b/en-US/VNC_Installations.xml
index 3b6f438..75adc01 100644
--- a/en-US/VNC_Installations.xml
+++ b/en-US/VNC_Installations.xml
@@ -257,14 +257,14 @@ Thu Feb 20 15:23:54 2014
<section id="sect-vnc-kickstart-considerations">
<title>Kickstart Considerations</title>
<para>
- Commands for using a VNC installation are also available in Kickstart installations. Using just the <command>vnc</command> command will set up an installation using Direct Mode. Options are available to set up an installation using Connect Mode. For more information about the <command>vnc</command> command and options used in Kickstart files, see <xref linkend="sect-kickstart-commands" />.
+ Commands for using a VNC installation are also available in Kickstart installations. Using just the <command>vnc</command> command will set up an installation using Direct Mode. Options are available to set up an installation using Connect Mode. For more information about the <command>vnc</command> command and options used in Kickstart files, see <xref linkend="appe-kickstart-syntax-reference" />.
</para>
</section>
<section id="sect-vnc-headless-considerations">
<title>Considerations for Headless Systems</title>
<para>
- When installing headless systems, the only choices are an automated Kickstart installation or an interactive VNC installation using connect mode. For more information about automated Kickstart installation, see <xref linkend="sect-kickstart-commands" />. The general process for an interactive VNC installation is described below.
+ When installing headless systems, the only choices are an automated Kickstart installation or an interactive VNC installation using connect mode. For more information about automated Kickstart installation, see <xref linkend="appe-kickstart-syntax-reference" />. The general process for an interactive VNC installation is described below.
</para>
<orderedlist>
<listitem>
9 years, 7 months
[install-guide/F21-rewrite] Updating .gitignore
by pbokoc
commit 7d62b00a2587ee86f6bc04e194b6c44593f295af
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Sep 15 19:41:22 2014 +0200
Updating .gitignore
.gitignore | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 0ac4db6..a9acd77 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,6 +3,7 @@ publish/**/*
tmp/**/*
en-US/.directory
en-US/*.xml~
+en-US/*.xml#
en-US/*.ent~
*/*.po~
pot/*.pot~
9 years, 7 months
[install-guide/F21-rewrite] Adding ostree to Kickstart commands
by pbokoc
commit 1f55d0ff585e6269f60a3b7f6444f9c04d4d2292
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Sep 15 19:40:44 2014 +0200
Adding ostree to Kickstart commands
en-US/Kickstart_Syntax_Reference.xml | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index a690a44..0667de1 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -204,6 +204,13 @@
</para>
</section>
+ <section id="sect-kickstart-commands-ostree">
+ <title>ostree - Install from an OSTree</title>
+ <para>
+ text
+ </para>
+ </section>
+
<section id="sect-kickstart-commands-part">
<title>part - Create Physical Partition</title>
<para>
9 years, 7 months
[networking-guide] master: It is the GUI that does the saving (bda3839)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit bda3839bdccb89edba0ec8bb8baf08aab16b0b61
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Sun Sep 14 18:59:46 2014 +0200
It is the GUI that does the saving
and NetworkManager is not the GUI
>---------------------------------------------------------------
en-US/Configure_Networking.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index c5a0faa..7de0702 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -436,7 +436,7 @@ To restrict connections and networking, there are two options which can be used
<bridgehead
id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-wireless">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead>
- <para>Once you have finished editing the wireless connection, click the <guibutton>Apply</guibutton> button and <application>NetworkManager</application> will save your customized configuration. Given a correct configuration, you can connect to your modified connection by selecting it from the Notification Area applet. See <xref
+ <para>Once you have finished editing the wireless connection, click the <guibutton>Apply</guibutton> button to save your configuration. Given a correct configuration, you can connect to your modified connection by selecting it from the Notification Area applet. See <xref
linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for details on selecting and connecting to a network.</para>
<para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking the gear wheel icon to reveal the connection details.</para>
<para>Then, to configure:</para>
9 years, 7 months
[networking-guide] master: Improve: static vs dynamic (6aa0e56)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit 6aa0e563f05761aff20c354e57e598043ef45c2d
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Sun Sep 14 18:45:53 2014 +0200
Improve: static vs dynamic
>---------------------------------------------------------------
en-US/Configure_Networking.xml | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index 33bda92..c5a0faa 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -20,6 +20,9 @@
Use static <systemitem class="protocol">IP</systemitem> addressing on those servers and devices whose network availability you want to ensure when automatic assignment methods, such as <systemitem class="protocol">DHCP</systemitem>, fail. <systemitem class="protocol">DHCP</systemitem>, <systemitem class="protocol">DNS</systemitem>, and authentication servers are typical examples. Interfaces for out-of-band management devices are also worth configuring with static settings as these devices are supposed to work, as far as is possible, independently of other network infrastructure.</para>
<para>For hosts which are not considered vital, but for which static <systemitem class="protocol">IP</systemitem> addressing is still considered desirable, use an automated provisioning method when possible. For example, <systemitem class="protocol">DHCP</systemitem> servers can be configured to provide the same <systemitem class="protocol">IP</systemitem> address to the same host every time. This method could be used for communal printers for example.
</para>
+ <para>
+ All the configuration tools listed in <xref linkend="sec-Selecting_Network_Configuration_Methods" /> allow assigning static <systemitem class="protocol">IP</systemitem> addresses manually. The <application>nmcli</application> tool is also suitable for use with scripted assignment of network configuration.
+ </para>
</section>
<section id="sec-When_to_Use_Dynamic_Interface_Settings">
@@ -27,7 +30,7 @@
<para>
</para>
<para>
- Enable and use dynamic assignment of <systemitem class="protocol">IP</systemitem> addresses and other network information whenever there is no compelling reason not to. The time saved in planning and documenting manual settings can be better spent elsewhere. See <xref linkend="sec-dhcp-why" /> for more information on this subject.
+ Enable and use dynamic assignment of <systemitem class="protocol">IP</systemitem> addresses and other network information whenever there is no compelling reason not to. The time saved in planning and documenting manual settings can be better spent elsewhere. The <firstterm>dynamic host control protocol</firstterm> (<acronym>DHCP</acronym>) is a traditional method of dynamically assigning network configurations to hosts. See <xref linkend="sec-dhcp-why" /> for more information on this subject.
</para>
<para>
Note that <application>NetworkManager</application> will start the <systemitem class="protocol">DHCP</systemitem> client, <application>dhclient</application>, automatically.
9 years, 7 months
[networking-guide] master: Improve: Adding a New VPN Connection (7ba58e5)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit 7ba58e526c0407e87791b5cb8e2ad83a173852ab
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Sun Sep 14 18:44:46 2014 +0200
Improve: Adding a New VPN Connection
The first para is an intro, not a step.
>---------------------------------------------------------------
en-US/Configure_Networking.xml | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index 248864f..33bda92 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -476,11 +476,9 @@ To restrict connections and networking, there are two options which can be used
<procedure
id="procedure-Adding_a_New_VPN_Connection">
<title>Adding a New VPN Connection</title>
- <step>
<para>
You can configure a new VPN connection by opening the <guilabel>Network</guilabel> window and selecting the plus symbol below the menu.
</para>
- </step>
<step>
<para>Press the <keycap>Super</keycap> key to enter the Activities Overview, type <command>control network</command> and then press <keycap>Enter</keycap>. The <guilabel>Network</guilabel> settings tool appears.</para>
</step>
9 years, 7 months
[networking-guide] master: Configuring a Network Interface Using ip Commands (4b790d0)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit 4b790d0e20bf24ad1f3a8e47418c80c0fe8e713e
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Sun Sep 14 18:43:47 2014 +0200
Configuring a Network Interface Using ip Commands
>---------------------------------------------------------------
en-US/Configure_Networking.xml | 41 ++++++++++++++++++++++++++++++++++++++++
1 files changed, 41 insertions(+), 0 deletions(-)
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index 213ae57..248864f 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -1602,6 +1602,47 @@ Optionally specify the hardware or MAC address using the <command>HWADDR</comman
</para>
</section>
+ <section id="sec-Configuring_a_Network_Interface_Using_ip_commands">
+<title>Configuring a Network Interface Using ip Commands</title>
+<para>
+ The <application>ip</application> utility can be used to assign <systemitem class="protocol">IP</systemitem> addresses to an interface. The command takes the following form:
+<synopsis>ip addr <optional> add | del </optional> <replaceable>address</replaceable> dev <replaceable>ifname</replaceable></synopsis></para>
+
+ <bridgehead id="bh-Assigning_a_Static_Address_Using_ip_Commands">
+ Assigning a Static Address Using ip Commands
+ </bridgehead>
+ <para>
+To assign an <systemitem class="protocol">IP</systemitem> address to an interface, issue a command as <systemitem class="username">root</systemitem> as follows:
+<screen>~]# <command>ip address add 10.0.0.3/24 dev eth0</command>
+The address assignment of a specific device can be viewed as follows:
+~]# <command>ip addr show dev eth0</command>
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
+ link/ether f0:de:f1:7b:6e:5f brd ff:ff:ff:ff:ff:ff
+ inet 10.0.0.3/24 brd 10.0.0.255 scope global global eth0
+ valid_lft 58682sec preferred_lft 58682sec
+ inet6 fe80::f2de:f1ff:fe7b:6e5f/64 scope link
+ valid_lft forever preferred_lft forever</screen>
+ Further examples and command options can be found in the <filename>ip-address(8)</filename> manual page.
+</para>
+
+ <bridgehead id="bh-Configuring_Multiple_Addresses_Using_ip_Commands">
+ Configuring Multiple Addresses Using ip Commands
+ </bridgehead>
+ <para>
+ As the <application>ip</application> utility supports assigning multiple addresses to the same interface it is no longer necessary to use the alias interface method of binding multiple addresses to the same interface. The <application>ip</application> command to assign an address can be repeated multiple times in order to assign multiple address. For example:
+ <screen>~]# <command>ip address add 192.168.2.223/24 dev eth1</command>
+~]# <command>ip address add 192.168.4.223/24 dev eth1</command>
+~]# <command>ip addr</command>
+3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
+ link/ether 52:54:00:fb:77:9e brd ff:ff:ff:ff:ff:ff
+ inet 192.168.<emphasis role="bold">2</emphasis>.223/24 scope global eth1
+ inet 192.168.<emphasis role="bold">4</emphasis>.223/24 scope global eth1</screen>
+ </para>
+ <para>The commands for the <application>ip</application> utility are documented in the <filename>ip(8)</filename> manual page. Note that <application>ip</application> commands given on the command line will not persist after a system restart.
+ </para>
+
+ </section>
+
<section id="sec-Static-Routes_and_the_Default_Gateway">
<title>Static Routes and the Default Gateway</title>
<para>
9 years, 7 months
[networking-guide] master: power cycle after editing a profile (ca79090)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit ca79090d4584c593216b76bf9efa05c8b08da677
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Sun Sep 14 18:38:03 2014 +0200
power cycle after editing a profile
>---------------------------------------------------------------
en-US/Configure_Networking.xml | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index 616d298..213ae57 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -281,7 +281,7 @@ To restrict connections and networking, there are two options which can be used
<bridgehead
id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-Wired">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead>
- <para>Once you have finished editing your wired connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref
+ <para>Once you have finished editing your wired connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <application>NetworkManager</application> apply the changes. If the profile is OFF, set it to ON. See <xref
linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para>
<para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking the gear wheel icon to return to the editing dialog.</para>
<para>Then, to configure:</para>
@@ -657,7 +657,7 @@ To restrict connections and networking, there are two options which can be used
</variablelist>
<bridgehead
id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-vpn">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead>
- <para>Once you have finished editing your new VPN connection, click the <guibutton>Save</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref
+ <para>Once you have finished editing your new VPN connection, click the <guibutton>Save</guibutton> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <application>NetworkManager</application> apply the changes. If the profile is OFF, set it to ON. See <xref
linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para>
<para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking <guilabel>Configure</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para>
<para>Then, to configure:</para>
@@ -780,7 +780,7 @@ To restrict connections and networking, there are two options which can be used
<bridgehead
id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-mobile_broadband">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead>
- <para>Once you have finished editing your mobile broadband connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref
+ <para>Once you have finished editing your mobile broadband connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <application>NetworkManager</application> apply the changes. If the profile is OFF, set it to ON. See <xref
linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para>
<para>You can further configure an existing connection by selecting it in the <guilabel>Network Connections</guilabel> window and clicking <guilabel>Edit</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para>
<para>Then, to configure:</para>
@@ -994,7 +994,7 @@ To restrict connections and networking, there are two options which can be used
<bridgehead
id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-DSL">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead>
- <para>Once you have finished editing your DSL connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. To make <application>NetworkManager</application> apply the changes, power cycle the interface. See <xref
+ <para>Once you have finished editing your DSL connection, click the <guibutton>Apply</guibutton> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <application>NetworkManager</application> apply the changes. If the profile is OFF, set it to ON. See <xref
linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para>
<para>You can further configure an existing connection by selecting it in the <guilabel>Network Connections</guilabel> window and clicking <guilabel>Edit</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para>
<para>Then, to configure:</para>
9 years, 7 months