[install-guide/f21-branch] Adding common postinstall tasks to After Installation

pbokoc pbokoc at fedoraproject.org
Mon Dec 8 22:51:02 UTC 2014


commit 799323b6dbbc046b58f06104046a507aa59146a4
Author: Petr Bokoc <pbokoc at redhat.com>
Date:   Mon Dec 8 23:50:08 2014 +0100

    Adding common postinstall tasks to After Installation

 en-US/After_Installation.xml |   75 ++++++++++++++++++++++++++++++++++++++--
 en-US/Troubleshooting.xml    |   79 ++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 151 insertions(+), 3 deletions(-)
---
diff --git a/en-US/After_Installation.xml b/en-US/After_Installation.xml
index 2bc716f..ffe2164 100644
--- a/en-US/After_Installation.xml
+++ b/en-US/After_Installation.xml
@@ -48,7 +48,76 @@
 		<para>
 			After you finish the installation and go through one of the initial setup utilities described above, your system is ready for use. However, other administrative tasks not covered by the installer or the initial setup utilities may still be necessary, depending on how you plan to use your system. The list below describes some of the more common tasks usually performed immediately after a new installation.
 		</para>
-		
-	</section>
+		<variablelist>
+            <varlistentry>
+                <term>Recover a lost <systemitem class="username">root</systemitem> password</term>
+                <listitem>
+                    <para>
+                        The <systemitem class="username">root</systemitem> password, which is configured during the installation, is required for accessing the system as the <systemitem class="username">root</systemitem> user. Without this password you will not be able to configure your system or install additional software. If you lost or forgot your <systemitem class="username">root</systemitem> password, you can reset it by following the steps described in <xref linkend="sect-trouble-after-reset-root-password" />.
+                    </para>
+                </listitem>
+            </varlistentry>
+            <varlistentry>
+                <term>Configure the network</term>
+                <listitem>
+                    <para>
+                        In most cases, network access is configured during the installation process, either in the <application>Anaconda</application> installation program (see <xref linkend="sect-installation-gui-network-configuration" />) or in a Kickstart file (see <xref linkend="sect-kickstart-commands-network" />). For information on configuring the network after the installation, see the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
+                    </para>
+                </listitem>
+            </varlistentry>
+            <varlistentry>
+                <term>Perform an initial system update</term>
+                <listitem>
+                    <para>
+                        If you installed &PRODUCT; from a full installation ISO image (such as the Workstation live image or full Server DVD), it is recommended to perform an initial system update, because your installation media likely contained older versions of software packages. During the initial update, all installed packages are updated to their latest available versions. Updates to packages provide security fixes, bug fixes and enhancements. 
+                    </para>
+                    <para>
+                        The <application>Yum</application> package manager is used for updating installed packages. For more information about updating your system with <application>Yum</application>, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
+                    </para>
+                </listitem>
+            </varlistentry>
+            <varlistentry>
+                <term>Install driver updates</term>
+                <listitem>
+                    <para>
+                        Usually, drivers for system devices are already supported in the kernel provided by Red&nbsp;Hat Enterprise&nbsp;Linux. However, occasionally, support for devices that have been released recently could be missing. In these cases, a driver update enabling your device may be available. 
+                    </para>
+                    <para>
+                        Devices necessary to complete the installation can have driver updates provided before the installation begins. If a device is missing a driver, but it is not essential during the installation, it is recommended to wait until after the installation completes, and install additional drivers afterwards. For instructions on installing and enabling additional drivers on the installed system using <application>RPM</application> and <application>Yum</application>, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
+                    </para>
+                </listitem>
+            </varlistentry>
+            <varlistentry>
+                <term>Configure additional repositories</term>
+                <listitem>
+                    <para>
+                        New software is installed from <firstterm>package repositories</firstterm>. Package repositories are organized sets of software and metadata that can be accessed by the <application>Yum</application> package manager. By default, several update repositories provided by &PRODUCT; are configured automatically and you can install updates and additional software from those. However, if you want to set up additional repositories, for example ones containing your own software, some extra steps are needed.
+                    </para>
+                    <para>
+                        For information about configuring additional software repositories, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
+                    </para>
+                </listitem>
+            </varlistentry>
+            <varlistentry>
+                <term>Install additional packages</term>
+                <listitem>
+                <para>
+                    You can control which packages will be installed by selecting an environment in the <systemitem>Software Selection</systemitem> dialog in the graphical installation (see <xref linkend="sect-installation-gui-software-selection" />). This dialog does not provide a way to choose individual packages, only predefined sets. However, you can use the <application>Yum</application> packages manager to install additional packages after the installation. See the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for more information.
+                </para>
+                </listitem>
+            </varlistentry>
+            <varlistentry>
+                <term>Switch to a graphical login</term>
+                <listitem>
+                    <para>
+                        Depending on the options you chose during the installation process, it is possible that your system does not have a graphical interface, instead offering only a text-based prompt. If this is the case and you wish to enable a graphical desktop after the installation, you must install the <application>X Window System</application> and your preferred desktop environment (either <application>GNOME</application> or <application>KDE</application>).
+                    </para>
+                    <para>
+                        As with all other software, these packages can be installed using the <application>Yum</application> package manager. For information about using <application>Yum</application> to install new packages, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. For information on how to enable graphical login by default, see <xref linkend="sect-trouble-after-graphical-login" />. 
+                    </para>
+                </listitem>
+            </varlistentry>
+        </variablelist>
+    </section>
 
-</chapter>
+</chapter>
\ No newline at end of file
diff --git a/en-US/Troubleshooting.xml b/en-US/Troubleshooting.xml
index a054b3a..c1cd611 100644
--- a/en-US/Troubleshooting.xml
+++ b/en-US/Troubleshooting.xml
@@ -496,6 +496,85 @@
 
     <section id="sect-troubleshooting-problems-after-installation">
         <title>Problems After Installation</title>
+        
+        <section id="sect-trouble-after-reset-root-password">
+            <title>Resetting the Root Password</title>
+            <para>
+                If you lost the root password to the system and you have access to the boot loader, you can reset the password by editing the GRUB2 configuration.
+            </para>
+            <procedure>
+                <title>Resetting the Root Password</title>
+                <step>
+                    <para>
+                        Boot your system and wait until the GRUB2 menu appears.
+                    </para>
+                </step>
+                <step>
+                    <para>
+                        In the boot loader menu, highlight any entry and press <keycap>e</keycap> to edit it.
+                    </para>
+                </step>
+                <step>
+                    <para>
+                        Find the line beginning with <literal>linux</literal>. At the end of this line, append the following:
+                    </para>
+                    <screen>
+<userinput>init=/bin/sh</userinput>
+                    </screen>
+                </step>
+                <step>
+                    <para>
+                        Press <keycap>F10</keycap> or <keycombo><keycap>Ctrl</keycap><keycap>X</keycap></keycombo> to boot the system using the options you just edited.
+                    </para>
+                    <para>
+                        Once the system boots, you will be presented with a shell prompt without having to enter any user name or password:
+                    </para>
+                    <screen>
+<prompt>sh-4.2#</prompt>
+                    </screen>
+                </step>
+                <step>
+                    <para>
+                        Load the installed SELinux policy:
+                    </para>
+                    <screen>
+<prompt>sh-4.2#</prompt> <command>/usr/sbin/load_policy -i</command>
+                    </screen>
+                </step>
+                <step>
+                    <para>
+                        Execute the following command to remount your root partition:
+                    </para>
+                    <screen>
+<prompt>sh4.2#</prompt> <command>mount -o remount,rw /</command>
+                    </screen>
+                </step>
+                <step>
+                    <para>
+                        Reset the root password:
+                    </para>
+                    <screen>
+<prompt>sh4.2#</prompt> <command>passwd root</command>
+                    </screen>
+                    <para>
+                        When prompted to, enter your new root password and confirm by pressing the <keycap>Enter</keycap> key. Enter the password for the second time to make sure you typed it correctly and confirm with <keycap>Enter</keycap> again. If both passwords match, a message informing you of a successful root password change will appear.
+                    </para>
+                </step>
+                <step>
+                    <para>
+                        Remount the root partition again, this time as read-only:
+                    </para>
+                    <screen>
+<prompt>sh4.2#</prompt> <command>mount -o remount,ro /</command>
+                    </screen>
+                </step>
+                <step>
+                    <para>
+                        Reboot the system. From now on, you will be able to log in as the root user using the new password set up during this procedure.
+                    </para>
+                </step>
+            </procedure>
+        </section>
 
         <section id="sect-trouble-after-raid">
             <title>Are You Unable to Boot With Your RAID Card?</title>


More information about the docs-commits mailing list