commit 0609fb11946b3c72dfc1ff07ddcb714641548a12
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Sep 29 18:28:27 2014 +0200
Added most of introduction to Installing using Anaconda
en-US/Installing_Using_Anaconda.xml | 133 ++++++++++++++++++++++++++++++----
1 files changed, 117 insertions(+), 16 deletions(-)
---
diff --git a/en-US/Installing_Using_Anaconda.xml b/en-US/Installing_Using_Anaconda.xml
index 708ddeb..9e16ab7 100644
--- a/en-US/Installing_Using_Anaconda.xml
+++ b/en-US/Installing_Using_Anaconda.xml
@@ -6,40 +6,141 @@
<chapter id="chap-installing-using-anaconda">
<title>Installing Using Anaconda</title>
<para>
- intro text
+ This chapter provides step-by-step instructions for installing &PRODUCT; using the
<application>Anaconda</application> installer. The bulk of this chapter
describes installation using the graphical user interface. A text mode is also available
for systems with no graphical display, but this mode is limited in certain aspects (for
example, custom partitioning is not possible in text mode).
</para>
+ <para>
+ If your system does not have the ability to use the graphical mode, you can:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use Kickstart to automate the installation as described in <xref
linkend="chap-kickstart-installations" />
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Perform the graphical installation remotely by connecting to the installation system
from another computer with a graphical display using the
<firstterm>VNC</firstterm> (Virtual Network Computing) protocol - see <xref
linkend="chap-vnc-installations" />
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <section id="sect-installation-new-users">
+ <title>Introduction to Anaconda</title>
+ <para>
+ The &PRODUCT; installer, <application>Anaconda</application>, is
different from most other operating system installation programs due to its parallel
nature. Most installers follow a fixed path: you must choose your language first, then you
configure network, then installation type, then partitioning, etc. There is usually only
one way to proceed at any given time.
+ </para>
+ <para>
+ In <application>Anaconda</application> you are only required to select
your language and locale first, and then you are presented with a central screen, where
you can configure most aspects of the installation in any order you like. This does not
apply to all parts of the installation process, however - for example, when installing
from a network location, you must configure the network before you can select which
packages to install.
+ </para>
+ <para>
+ Some screens will be automatically configured depending on your hardware and the type
of media you used to start the installation. You can still change the detected settings in
any screen. Screens which have not been automatically configured, and therefore require
your attention before you begin the installation, are marked by an exclamation mark. You
can not start the actual installation process before you finish configuring these
settings.
+ </para>
+ <para>
+ Additional differences appear in certain screens; notably the custom partitioning
process is very different from other Linux distributions. These differences are described
in each screen's subsection.
+ </para>
+ </section>
<section id="sect-consoles-logs-during-installation">
<title>Consoles and Logging During the Installation</title>
<para>
- text
+ The following sections describe how to access logs and an interactive shell during the
installation. This is useful when troubleshooting problems, but should not be necessary in
most cases.
</para>
<section id="sect-installation-consoles">
<title>Accessing Consoles</title>
<para>
- text
+ The &PRODUCT; installer uses the <application>tmux</application>
terminal multiplexer to display and control several windows you can use in addition to the
main interface. Each of these windows serves a different purpose - they display several
different logs, which can be used to troubleshoot any issues during the installation, and
one of the windows provides an interactive shell prompt with <systemitem
class="username">root</systemitem> privileges, unless this prompt was
specifically disabled using a boot option or a Kickstart command.
</para>
- </section>
-
- <section id="sect-installation-screenshots">
- <title>Saving Screenshots</title>
+ <note>
+ <para>
+ In general, there is no reason to leave the default graphical installation
environment unless you need to diagnose an installation problem.
+ </para>
+ </note>
<para>
- text
+ The terminal multiplexer is running in virtual console 1. To switch from the actual
installation environment to <application>tmux</application>, press
<keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo>.
To go back to the main installation interface which runs in virtual console 6, press
<keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F6</keycap></keycombo>.
</para>
- </section>
-
- <section id="sect-installation-logs">
- <title>Log Files</title>
+ <note>
+ <para>
+ If you choose text mode installation, you will start in virtual console 1
(<application>tmux</application>), and switching to console 6 will open a
shell prompt instead of a graphical interface.
+ </para>
+ </note>
<para>
- text
+ The console running <application>tmux</application> has 5 available
windows; their contents are described in the table below, along with keyboard shortcuts
used to access them. Note that the keyboard shortcuts are two-part: first press
<keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo>,
then release both keys, and press the number key for the window you want to use.
+ </para>
+ <para>
+ You can also use
<keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo>
<keycap>n</keycap> and
<keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo>
<keycap>p</keycap> to switch to the next or previous
<application>tmux</application> window, respectively.
+ </para>
+ <table id="table-tmux-windows">
+ <title>Available tmux Windows</title>
+ <tgroup cols="2">
+ <colspec colwidth="15%" colname="keystroke"
colnum="1" />
+ <colspec colwidth="85%" colname="contents"
colnum="2" />
+ <thead>
+ <row>
+ <entry>
+ Shortcut
+ </entry>
+ <entry>
+ Contents
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo>
<keycap>1</keycap>
+ </entry>
+ <entry>
+ Main installation program window. Contains text-based prompts (during text mode
installation or if you use VNC direct mode), and also some debugging information.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo>
<keycap>2</keycap>
+ </entry>
+ <entry>
+ Interactive shell prompt with <systemitem
class="username">root</systemitem> privileges.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo>
<keycap>3</keycap>
+ </entry>
+ <entry>
+ Installation log; displays messages stored in
<filename>/tmp/anaconda.log</filename>.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo>
<keycap>4</keycap>
+ </entry>
+ <entry>
+ Storage log; displays messages related storage devices from kernel and system
services, stored in <filename>/tmp/storage.log</filename>.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo>
<keycap>5</keycap>
+ </entry>
+ <entry>
+ Program log; displays messages from other system utilities, stored in
<filename>/tmp/program.log</filename>.
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>
+ In addition to displaying diagnostic information in
<application>tmux</application> windows,
<application>Anaconda</application> also generates several log files, which
can be transferred from the installation system. These log files are described in <xref
linkend="sect-troubleshooting-log-files" />, and directions for transferring
them from the installation system are available in <xref
linkend="sect-troubleshooting-transferring-logs" />.
</para>
</section>
- <section id="sect-installation-remote-logging">
- <title>Remote Logging</title>
+ <section id="sect-installation-screenshots">
+ <title>Saving Screenshots</title>
+ <para>
+ You can press <keycombo><keycap>Shift</keycap><keycap>Print
Screen</keycap></keycombo> at any time during the graphical installation to
capture the current screen. These screenshots are saved to <filename
class="directory">/tmp/anaconda-screenshots</filename>.
+ </para>
<para>
- text
+ Additionanlly, you can use the <command>autostep
--autoscreenshot</command> command in a Kickstart file to capture and save each step
of the installation automatically. See <xref
linkend="sect-kickstart-commands-autostep" /> for details.
</para>
</section>
Show replies by date