December 2014 - docs-commits - Fedora Mailing-Lists

[system-administrators-guide] A host address requires /32

by stephenw

commit cffe7cad6d73796aa8b51b18ed7459608cb27334 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Mon Dec 8 08:20:45 2014 +0100 A host address requires /32 thank you Sanjiv Marathe for reporting that en-US/Configuring_NTP_Using_ntpd.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/Configuring_NTP_Using_ntpd.xml b/en-US/Configuring_NTP_Using_ntpd.xml index be44744..0346f79 100644 --- a/en-US/Configuring_NTP_Using_ntpd.xml +++ b/en-US/Configuring_NTP_Using_ntpd.xml @@ -252,7 +252,7 @@ restrict ::1</screen> <para> Hosts on the local network are not permitted because of the "restrict default" line above. To change this, for example to allow hosts from the <systemitem class="ipaddress">192.0.2.0/24</systemitem> network to query the time and statistics but nothing more, a line in the following format is required: <screen>restrict 192.0.2.0 mask 255.255.255.0 nomodify notrap nopeer</screen> - To allow unrestricted access from a specific host, for example <systemitem class="ipaddress">192.0.2.250/24</systemitem>, a line in the following format is required: + To allow unrestricted access from a specific host, for example <systemitem class="ipaddress">192.0.2.250/32</systemitem>, a line in the following format is required: <screen>restrict 192.0.2.250</screen> A mask of <systemitem class="ipaddress">255.255.255.255</systemitem> is applied if none is specified. </para>

9 years, 5 months

1
0
0 / 0

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

by pbokoc

commit 799323b6dbbc046b58f06104046a507aa59146a4 Author: Petr Bokoc <pbokoc(a)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 Hat Enterprise 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>

9 years, 5 months

1
0
0 / 0

[install-guide/f21-branch] Moving Next Steps into After Installation

by pbokoc

commit 4797645c88986fc9d42fea4447f9b3c88101b61b Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 23:34:58 2014 +0100 Moving Next Steps into After Installation en-US/After_Installation.xml | 12 ++++++++++-- en-US/Installation_Guide.xml | 1 - 2 files changed, 10 insertions(+), 3 deletions(-) --- diff --git a/en-US/After_Installation.xml b/en-US/After_Installation.xml index 2270e62..2bc716f 100644 --- a/en-US/After_Installation.xml +++ b/en-US/After_Installation.xml @@ -20,7 +20,7 @@ <section id="sect-gnome-initial-setup"> <title>GNOME Initial Setup</title> <para> - The <application>GNOME Initial Setup</application> utility will be displayed after you log in for the first time with any user account - immediately after the installation finishes, and then again for each new user which logs in to the graphical environment. + The <application>GNOME Initial Setup</application> utility will be displayed after you log in for the first time with any user account, as long as your first login is in the <application>GNOME</application> desktop environment. </para> <figure> <title>GNOME Initial Setup</title> @@ -30,7 +30,7 @@ </imageobject> <textobject> <para> - GNOME Initial Setup with keyboard layout selection displayed. + GNOME Initial Setup with language selection displayed. </para> </textobject> </mediaobject> @@ -42,5 +42,13 @@ After you finish configuring all screens, click <guilabel>Start using Fedora</guilabel> to exit the utility. After that, the <guilabel>Getting Started</guilabel> page from GNOME help will be displayed, and you can either browse the help content, or close it and start using your desktop. </para> </section> + + <section id="sect-common-post-installation-tasks"> + <title>Common Post-installation Tasks</title> + <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> </chapter> diff --git a/en-US/Installation_Guide.xml b/en-US/Installation_Guide.xml index d92c565..5c2616a 100644 --- a/en-US/Installation_Guide.xml +++ b/en-US/Installation_Guide.xml @@ -21,7 +21,6 @@ <xi:include href="Installing_Using_Anaconda.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="After_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Troubleshooting.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Next_Steps.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </part> <part id="part-advanced-installation-options">

9 years, 5 months

1
0
0 / 0

[install-guide/f21-branch] it's redhat.com, not redhat.org

by pbokoc

commit 35c693511d1d2e4a3587e9bd17419be7d09fcb53 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 23:34:44 2014 +0100 it's redhat.com, not redhat.org en-US/Next_Steps.xml | 26 -------------------------- en-US/Revision_History.xml | 2 +- 2 files changed, 1 insertions(+), 27 deletions(-) --- diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml index 9f7c4e7..4afbb86 100644 --- a/en-US/Revision_History.xml +++ b/en-US/Revision_History.xml @@ -14,7 +14,7 @@ <author> <firstname>Petr</firstname> <surname>Bokoč</surname> - <email>pbokoc(a)redhat.org</email> + <email>pbokoc(a)redhat.com</email> </author> <revdescription> <simplelist>

9 years, 5 months

1
0
0 / 0

[install-guide/f21-branch] Fixing a broken build + show_remarks: 0

by pbokoc

commit 2309a1f0d7dae9708b3efb20b62e51f25995bb98 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 23:20:36 2014 +0100 Fixing a broken build + show_remarks: 0 en-US/Network_based_Installations.xml | 8 +++--- en-US/Revision_History.xml | 34 ++++++++++++++++++++------------ publican.cfg | 2 +- 3 files changed, 26 insertions(+), 18 deletions(-) --- diff --git a/en-US/Network_based_Installations.xml b/en-US/Network_based_Installations.xml index 38a774a..15e18c3 100644 --- a/en-US/Network_based_Installations.xml +++ b/en-US/Network_based_Installations.xml @@ -62,11 +62,11 @@ A Fedora repository must be available for the installation. The example in this section uses the public Fedora mirrors as the repository source, but you can also use a repo on the local network provided by NFS, FTP, or HTTP. Repositories can be configured using the <option>inst.repo=</option> boot option; see <xref linkend="sect-boot-options-sources" /> for details. </para> </formalpara> -  + <remark>A link to mirrormanager and some instructions to other guides too. All the elaboration on installation methods might be going to far, but we can ref. --Pete</remark> </section> <section id="pxe-dhcpd"> <title>DHCP Server Configuration</title> -  + <remark>Needs adminition about static IP, reference out to Networking Guide. Example assumes 192.168.1.2 for server.</remark> <procedure> <title>Installing and configuring dhcpd</title> <step> @@ -208,8 +208,8 @@ subnet 192.168.1.0 netmask 255.255.255.0 { <title>Configuring client bootloaders</title> <step> <para>Create a boot menu for BIOS clients at <filename>/var/lib/tftpboot/pxelinux/default</filename>.</para> -  + <remark>needs adminition about kickstarts here somewhere, and testing of pulling .ks out of cgit</remark> + <remark>Need to check if the product media ships different or incompatible initramfsen</remark> <programlisting> default vesamenu.c32 prompt 1 diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml index bb40d15..9f7c4e7 100644 --- a/en-US/Revision_History.xml +++ b/en-US/Revision_History.xml @@ -3,11 +3,25 @@ ]> <appendix id="appe-Publican-Revision_History"> <title>Revision History</title> - <para> + <para> Note that revision numbers relate to the edition of this manual, not to version numbers of Fedora. </para> <simpara> <revhistory> + <revision> + <revnumber>1.1-0</revnumber> + <date>Mon Dec 8 2014</date> + <author> + <firstname>Petr</firstname> + <surname>Bokoč</surname> + <email>pbokoc(a)redhat.org</email> + </author> + <revdescription> + <simplelist> + <member>Publishing for Fedora 21</member> + </simplelist> + </revdescription> + </revision> <revision> <revnumber>1.0-1</revnumber> <date>Mon Dec 8 2014</date> @@ -22,26 +36,20 @@ </simplelist> </revdescription> </revision> - <revision> + <revision> <revnumber>1.0-0</revnumber> - <date>Tue Dec 17 2013</date> - <author> + <date>Tue Dec 17 2013</date> + <author> <firstname>Petr</firstname> - <surname>Bokoč</surname> - <email>pbokoc(a)redhat.com</email> + <surname>Bokoč</surname> + <email>pbokoc(a)redhat.com</email> </author> - <revdescription> + <revdescription> <simplelist> <member>Publishing for Fedora 20</member> - </simplelist> - </revdescription> - </revision> - </revhistory> - </simpara> </appendix> - diff --git a/publican.cfg b/publican.cfg index 8b6d321..b347a79 100644 --- a/publican.cfg +++ b/publican.cfg @@ -8,4 +8,4 @@ brand: fedora #web_version_label: UNUSED mainfile: Installation_Guide os_ver: .el6 -show_remarks: 1 +show_remarks: 0

9 years, 5 months

1
0
0 / 0

[install-guide/f21-branch] commenting out a few remarks in Network Based Installations

by pbokoc

commit f12f069064d305228ff417701dff1f60b475d560 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 23:13:43 2014 +0100 commenting out a few remarks in Network Based Installations en-US/Network_based_Installations.xml | 11 +++++------ 1 files changed, 5 insertions(+), 6 deletions(-) --- diff --git a/en-US/Network_based_Installations.xml b/en-US/Network_based_Installations.xml index 54fe19f..38a774a 100644 --- a/en-US/Network_based_Installations.xml +++ b/en-US/Network_based_Installations.xml @@ -59,15 +59,14 @@ <formalpara> <title>Package repository</title> <para> - A Fedora repository must be available for the installation. The example in this section uses the public Fedora mirrors as the repository source, but you can also use a repo on the local network provided by NFS, FTP, or HTTP. + A Fedora repository must be available for the installation. The example in this section uses the public Fedora mirrors as the repository source, but you can also use a repo on the local network provided by NFS, FTP, or HTTP. Repositories can be configured using the <option>inst.repo=</option> boot option; see <xref linkend="sect-boot-options-sources" /> for details. </para> </formalpara> - <remark>Dump a link in here to the inst.repo option. Update the inst.repo option with examples if needed. --Pete</remark> - <remark>A link to mirrormanager and some instructions to other guides too. All the elaboration on installation methods might be going to far, but we can ref. --Pete</remark> +  </section> <section id="pxe-dhcpd"> <title>DHCP Server Configuration</title> - <remark>Needs adminition about static IP, reference out to Networking Guide. Example assumes 192.168.1.2 for server.</remark> +  <procedure> <title>Installing and configuring dhcpd</title> <step> @@ -209,8 +208,8 @@ subnet 192.168.1.0 netmask 255.255.255.0 { <title>Configuring client bootloaders</title> <step> <para>Create a boot menu for BIOS clients at <filename>/var/lib/tftpboot/pxelinux/default</filename>.</para> - <remark>needs adminition about kickstarts here somewhere, and testing of pulling .ks out of cgit</remark> - <remark>Need to check if the product media ships different or incompatible initramfsen</remark> +  <programlisting> default vesamenu.c32 prompt 1

9 years, 5 months

1
0
0 / 0

[install-guide/f21-branch] Removing a remark from LVM creation in Anaconda

by pbokoc

commit 9c79b64ac906685f7fdbdc55512c89f081d06aa8 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 23:08:32 2014 +0100 Removing a remark from LVM creation in Anaconda en-US/CustomSpoke_AddLVM.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/CustomSpoke_AddLVM.xml b/en-US/CustomSpoke_AddLVM.xml index e383b9a..82868d6 100644 --- a/en-US/CustomSpoke_AddLVM.xml +++ b/en-US/CustomSpoke_AddLVM.xml @@ -9,7 +9,7 @@ <firstterm>Logical Volume Management</firstterm> (LVM) presents a simple logical view of underlying physical storage space, such as hard drives or LUNs. Partitions on physical storage are represented as <firstterm>physical volumes</firstterm> that can be grouped together into <firstterm>volume groups</firstterm>. Each volume group can be divided into multiple <firstterm>logical volumes</firstterm>, each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions which can span multiple physical disks. </para> <para> - <remark>See  for additional information about the concepts behind physical partitions.</remark> + See <xref linkend="appe-lvm-overview" /> for additional information about the concepts behind Logical Volume Management. </para> <warning> <para>

9 years, 5 months

1
0
0 / 0

[install-guide/f21-branch] Adding section on GNOME Initial Setup

by pbokoc

commit 53654dd0e90ea24ebc883b1447b4e3872442b467 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 23:08:10 2014 +0100 Adding section on GNOME Initial Setup en-US/After_Installation.xml | 29 +++++++++++++++++++- en-US/images/afterinstall/gnome-initial-setup.png | Bin 0 -> 28440 bytes 2 files changed, 27 insertions(+), 2 deletions(-) --- diff --git a/en-US/After_Installation.xml b/en-US/After_Installation.xml index 69c67ff..2270e62 100644 --- a/en-US/After_Installation.xml +++ b/en-US/After_Installation.xml @@ -6,7 +6,13 @@ <chapter id="chap-after-installation"> <title>After the Installation</title> <para> - intro text + This chapter describes the initial setup tools which open after you finish the instalaltion, reboot the system, and log in for the first time. + </para> + <para> + Two separate configuration tools are part of &PRODUCT;. If you installed the <application>GNOME</application> desktop environment (the default &PRODUCT; environment, installed for example as part of the &PRODUCT; Workstation flavor), the <application>GNOME Initial Setup</application> utility will open; for all other graphical environments, the <application>Initial Setup</application> tool serves the same purpose. + </para> + <para> + Both of these tools will allow you to configure user-specific settings which have not been configured during the installation. Some of the settings are available both in the graphical installer (or as Kickstart commands) as well as in the initial-setup utilities; in that case, they will only be displayed after the first reboot if you skipped them during the installation. This means that, for example, if you configured a user account before the installation finished, you will not be prompted to do so again after the installation completes. </para> <xi:include href="InitialSetupHub.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> @@ -14,7 +20,26 @@ <section id="sect-gnome-initial-setup"> <title>GNOME Initial Setup</title> <para> - text + The <application>GNOME Initial Setup</application> utility will be displayed after you log in for the first time with any user account - immediately after the installation finishes, and then again for each new user which logs in to the graphical environment. + </para> + <figure> + <title>GNOME Initial Setup</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/afterinstall/gnome-initial-setup.png" format="PNG" scalefit="0" /> + </imageobject> + <textobject> + <para> + GNOME Initial Setup with keyboard layout selection displayed. + </para> + </textobject> + </mediaobject> + </figure> + <para> + This utility allows you to configure several user-specific settings, such as system language or the default keyboard layout. Use the <guilabel>Next</guilabel> and <guilabel>Previous</guilabel> buttons at the top of the window to navigate between screens. Some screens (<guilabel>Configure online accounts</guilabel> in particular) are optional and can be skipped using the <guilabel>Skip</guilabel> button in the top right corner. + </para> + <para> + After you finish configuring all screens, click <guilabel>Start using Fedora</guilabel> to exit the utility. After that, the <guilabel>Getting Started</guilabel> page from GNOME help will be displayed, and you can either browse the help content, or close it and start using your desktop. </para> </section> diff --git a/en-US/images/afterinstall/gnome-initial-setup.png b/en-US/images/afterinstall/gnome-initial-setup.png new file mode 100644 index 0000000..5f1b0d8 Binary files /dev/null and b/en-US/images/afterinstall/gnome-initial-setup.png differ

9 years, 5 months

1
0
0 / 0

[install-guide/f21-branch] Clarifications in Booting the Installer

by pbokoc

commit a979cea6f2f865ec4ed158cc59c6a2d2f0a3e5b4 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 22:32:57 2014 +0100 Clarifications in Booting the Installer en-US/Booting_the_Installation.xml | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-) --- diff --git a/en-US/Booting_the_Installation.xml b/en-US/Booting_the_Installation.xml index a067a23..cf2973e 100644 --- a/en-US/Booting_the_Installation.xml +++ b/en-US/Booting_the_Installation.xml @@ -83,6 +83,14 @@ Press F12 to select boot device, or Del to enter SETUP <para> Every menu entry in the list is a predefined set of boot options, and these options can be customized to change some aspects of the installer's behavior. To edit the default set of boot options, press <keycap>Tab</keycap> on BIOS systems, or <keycap>e</keycap> on UEFI systems. The key to use is also displayed at the bottom of the screen. </para> + <note> + <para> + Editing boot options in <application>GRUB2</application> (on UEFI systems) will display the entire configuration for the selected entry. Actual boot options are configured on the line which starts with the <literal>linux</literal> (or <literal>linux16</literal> or <literal>linuxefi</literal>) keyword. Do not modify any other lines in the configuration. + </para> + <para> + On systems with BIOS firmware, only the actual boot options are displayed when you press <keycap>Tab</keycap>. + </para> + </note> <para> When editing the default set of options, you can change the existing ones as well as append additional ones. Once you finish, press <keycap>Enter</keycap> on BIOS or <keycombo><keycap>Ctrl</keycap><keycap>X</keycap></keycombo> on UEFI to boot the installer using your customized options. </para>

9 years, 5 months

1
0
0 / 0

[install-guide/f21-branch] Adding the Booting the Installer chapter

by pbokoc

commit d472c0dc0d49d252a0c9044c9f183db680e3ef14 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 22:25:10 2014 +0100 Adding the Booting the Installer chapter en-US/Booting_the_Installation.xml | 120 ++++++++++++++++++++++++++---------- en-US/VNC_Installations.xml | 2 +- en-US/images/boot/boot-menu.png | Bin 0 -> 4112 bytes 3 files changed, 87 insertions(+), 35 deletions(-) --- diff --git a/en-US/Booting_the_Installation.xml b/en-US/Booting_the_Installation.xml index 0a17821..a067a23 100644 --- a/en-US/Booting_the_Installation.xml +++ b/en-US/Booting_the_Installation.xml @@ -6,50 +6,102 @@ <chapter id="chap-booting-the-installation"> <title>Booting the Installation</title> <para> - intro text + This chapter will explain how to boot the installer from local media or a network server as well as how to navigate the boot menu and use custom options. </para> - <section id="sect-booting-local-media"> - <title>Booting from Local Media</title> + <section id="sect-preparing-boot"> + <title>Preparing to Boot</title> <para> - text + After you have made a bootable USB flash drive or a CD or DVD using the steps described in <xref linkend="sect-preparing-boot-media" />, you are ready to boot the installation. Note that the steps described below are generic and the exact steps will vary somewhat depending on your system - particularly on your motherboard manufacturer. </para> - </section> - - <section id="sect-booting-network"> - <title>Booting from a Network</title> + <warning> + <para> + There are no separate media provided for BIOS and UEFI systems; all of them can boot from the same ISO image. However, once you install &PRODUCT;, you can not switch between UEFI and BIOS. The system must run on the same firmware it was installed on; if you, for example, perform the installation on an UEFI system in UEFI mode, and then switch it to BIOS compatibility mode, &PRODUCT; will no longer boot and will require a reinstallation. + </para> + </warning> + <important> + <para> + &PRODUCT; does not support UEFI booting for 32-bit x86 systems. Only BIOS boot is supported on these systems. + </para> + <para> + Also note that &PRODUCT; only fully supports version 2.2 of the UEFI specification. Hardware that supports version 2.3 or later will boot and work normally, but the additional functionality defined by these later specifications will not be available. The UEFI specifications are available from <ulink url="http://www.uefi.org/specs/agreement/" />. + </para> + </important> <para> - text + To boot the &PRODUCT; installer, follow these steps: </para> + <procedure> + <title>Booting the &PRODUCT; Installer</title> + <step> + <para> + Plug in the boot USB drive, or insert the boot CD or DVD into your computer's optical disc drive. Alternatively, if you plan on booting from a network boot (PXE) server, make sure that the network cable is plugged in. + </para> + </step> + <step> + <para> + Restart the system. Once it starts rebooting, it should display a prompt similar to the following (usually at the bottom of the screen): + </para> + <screen> +Press F12 to select boot device, or Del to enter SETUP + </screen> + <para> + Follow the on-screen instructions to access the boot menu. If no instructions are displayed (some systems only display a graphical logo during early stages of boot), try pressing <keycap>F12</keycap>, <keycap>F11</keycap>, <keycap>F10</keycap> or <keycap>Del</keycap> several times; these are most commonly used keys. Note that there is usually a very short time window provided to access the menu; once it passes, you need to restart the system and try again. + </para> + <note> + <para> + Some older systems may not support choosing a boot device at startup. In that case, enter the system's SETUP (BIOS), and change the default boot order so that your boot media (CD, DVD, USB or network) have higher priority than internal hard drives. + </para> + </note> + </step> + <step> + <para> + When your system's boot menu opens, select an entry such as <guilabel>Boot from USB</guilabel> if you created a bootable USB drive, <guilabel>Boot from CD/DVD</guilabel> if you are using an optical disc to install &PRODUCT;, or <guilabel>Boot from PXE</guilabel> if you want to boot from a network location. + </para> + </step> + <step> + <para> + Wait until the boot menu is displayed. The boot menu is described further in this chapter. + </para> + </step> + </procedure> </section> <section id="sect-boot-menu"> <title>The Boot Menu</title> <para> - text + In most cases, when you boot the &PRODUCT; installer from your prepared boot media or server, the boot menu will the the first thing that appears. From this menu, you can either start the actual installation, or you can use the boot media to rescue an existing system. </para> - - <section id="sect-boot-menu-x86-bios"> - <title>The Boot Menu on BIOS-based AMD and Intel Systems</title> - <para> - text - </para> - </section> - - <section id="sect-boot-menu-x86-uefi"> - <title>The Boot Menu on UEFI-based AMD and Intel Systems</title> - <para> - text - </para> - </section> - - <section id="sect-boot-menu-arm"> - <title>The Boot Menu on ARM Systems</title> - <para> - text - </para> - </section> - - </section> - + <para> + The way the boot menu will look and function will vary somewhat depending on your system's firmware - BIOS systems use the <application>SYSLINUX</application> boot loader, and UEFI systems use <application>GRUB2</application>. However, both of the menus described below function very similarly from a user's point of view. + </para> + <para> + Use arrow keys to select an entry in the menu, and <keycap>Enter</keycap> to confirm your selection. The first two entries in the list will both proceed with the installation; the first one will start the installer directly, and the second one will verify the integrity of the boot media before starting the installation. + </para> + <para> + The final entry in the list is <guilabel>Troubleshooting</guilabel>; this is a submenu. Selecting this entry and pressing <keycap>Enter</keycap> will display a new set of selections, where you can choose to install in basic graphics mode (useful if you want to do a manual graphical installation but your system has issues with the default graphical installer), rescue an existing system, or test your system's memory modules for errors (on BIOS systems only). The troubleshooting menu also allows you to exit the boot menu and boot normally from your system's hard drive via the <guilabel>Boot from local drive</guilabel> option. + </para> + <para> + Every menu entry in the list is a predefined set of boot options, and these options can be customized to change some aspects of the installer's behavior. To edit the default set of boot options, press <keycap>Tab</keycap> on BIOS systems, or <keycap>e</keycap> on UEFI systems. The key to use is also displayed at the bottom of the screen. + </para> + <para> + When editing the default set of options, you can change the existing ones as well as append additional ones. Once you finish, press <keycap>Enter</keycap> on BIOS or <keycombo><keycap>Ctrl</keycap><keycap>X</keycap></keycombo> on UEFI to boot the installer using your customized options. + </para> + <figure> + <title>Editing boot options on a system with BIOS firmware</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/boot/boot-menu.png" format="PNG" scalefit="0" /> + </imageobject> + <textobject> + <para> + The boot menu. + </para> + </textobject> + </mediaobject> + </figure> + <para> + All available <application>Anaconda</application> boot options are described in <xref linkend="sect-boot-options-available" />. + </para> + </section> + </chapter> diff --git a/en-US/VNC_Installations.xml b/en-US/VNC_Installations.xml index dca125a..1dadb28 100644 --- a/en-US/VNC_Installations.xml +++ b/en-US/VNC_Installations.xml @@ -279,7 +279,7 @@ Thu Feb 20 15:23:54 2014 </listitem> <listitem> <para> - Follow the procedure for a VNC Installation using connect mode as described in the <xref linkend="proc-vnc-installations-connect-mode" />. However, when directed to boot the system, boot it from the PXE server as described in <xref linkend="sect-booting-network" />. + Follow the procedure for a VNC Installation using connect mode as described in the <xref linkend="proc-vnc-installations-connect-mode" />. However, when directed to boot the system, boot it from the PXE server. </para> </listitem> </orderedlist> diff --git a/en-US/images/boot/boot-menu.png b/en-US/images/boot/boot-menu.png new file mode 100644 index 0000000..412af59 Binary files /dev/null and b/en-US/images/boot/boot-menu.png differ

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits December 2014