[install-guide/f21-branch] Adding screenshots to the GUI installation chapter
by pbokoc
commit c7a6a70de3922b600ad80b053307adc511fb17d3
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Fri Nov 28 19:35:56 2014 +0100
Adding screenshots to the GUI installation chapter
en-US/CustomSpoke.xml | 32 +++++++++++---
en-US/CustomSpoke_AddBtrfs.xml | 16 +++++-
en-US/CustomSpoke_AddLVM.xml | 16 +++++-
en-US/CustomSpoke_AddPhysical.xml | 16 +++++-
en-US/CustomSpoke_FileSystems.xml | 2 +-
en-US/CustomSpoke_RecommendedScheme.xml | 2 +-
en-US/CustomSpoke_SoftwareRAID.xml | 16 +++++-
en-US/DateTimeSpoke.xml | 32 +++++++++++---
en-US/FilterSpoke.xml | 16 +++++-
en-US/InitialSetupHub.xml | 16 +++++-
en-US/KeyboardSpoke.xml | 16 +++++-
en-US/LangSupportSpoke.xml | 16 +++++-
en-US/NetworkSpoke.xml | 16 +++++-
en-US/PasswordSpoke.xml | 18 ++++++--
en-US/ProgressHub.xml | 16 +++++-
en-US/SoftwareSpoke.xml | 16 +++++-
en-US/SourceSpoke.xml | 16 +++++-
en-US/StorageSpoke.xml | 32 +++++++++++---
en-US/StorageSpoke_BootLoader.xml | 16 +++++-
en-US/SummaryHub.xml | 48 ++++++++++++++++----
en-US/UserSpoke.xml | 31 +++++++++++--
en-US/WelcomeSpoke.xml | 16 +++++-
en-US/images/anaconda/CustomSpoke.png | Bin 0 -> 112962 bytes
en-US/images/anaconda/CustomSpoke_AddBtrfs.png | Bin 0 -> 86907 bytes
en-US/images/anaconda/CustomSpoke_AddLVM.png | Bin 0 -> 89554 bytes
en-US/images/anaconda/CustomSpoke_AddPhysical.png | Bin 0 -> 83841 bytes
en-US/images/anaconda/CustomSpoke_RescanDisks.png | Bin 0 -> 47162 bytes
en-US/images/anaconda/CustomSpoke_SoftwareRAID.png | Bin 0 -> 27847 bytes
en-US/images/anaconda/DateTimeSpoke.png | Bin 0 -> 193476 bytes
en-US/images/anaconda/DateTimeSpoke_AddNTP.png | Bin 0 -> 22558 bytes
en-US/images/anaconda/FilterSpoke.png | Bin 0 -> 55181 bytes
en-US/images/anaconda/InitialSetupHub.png | Bin 0 -> 87255 bytes
en-US/images/anaconda/KeyboardSpoke.png | Bin 0 -> 58886 bytes
en-US/images/anaconda/LangSupportSpoke.png | Bin 0 -> 79695 bytes
en-US/images/anaconda/NetworkSpoke.png | Bin 0 -> 61703 bytes
en-US/images/anaconda/PasswordSpoke.png | Bin 0 -> 35651 bytes
en-US/images/anaconda/ProgressHub.png | Bin 0 -> 124105 bytes
en-US/images/anaconda/SoftwareSpoke.png | Bin 0 -> 208279 bytes
en-US/images/anaconda/SourceSpoke.png | Bin 0 -> 74742 bytes
en-US/images/anaconda/StorageSpoke.png | Bin 0 -> 84150 bytes
en-US/images/anaconda/StorageSpoke_BootLoader.png | Bin 0 -> 31851 bytes
en-US/images/anaconda/StorageSpoke_Selected.png | Bin 0 -> 21577 bytes
en-US/images/anaconda/SummaryHub.png | Bin 0 -> 117120 bytes
en-US/images/anaconda/SummaryHub_Mouseover.png | Bin 0 -> 14177 bytes
en-US/images/anaconda/SummaryHub_States.png | Bin 0 -> 54008 bytes
en-US/images/anaconda/UserSpoke.png | Bin 0 -> 46540 bytes
en-US/images/anaconda/UserSpoke_Advanced.png | Bin 0 -> 91884 bytes
en-US/images/anaconda/WelcomeSpoke.png | Bin 0 -> 124854 bytes
48 files changed, 342 insertions(+), 79 deletions(-)
---
diff --git a/en-US/CustomSpoke.xml b/en-US/CustomSpoke.xml
index 90d61c0..e654b5a 100644
--- a/en-US/CustomSpoke.xml
+++ b/en-US/CustomSpoke.xml
@@ -19,9 +19,19 @@
No permanent changes will be made to your disks during the actual partitioning process. The configuration you have selected will only be written to your system after you press the <guilabel>Begin installation</guilabel> button in <xref linkend="sect-installation-gui-installation-summary" />.
</para>
</note>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Manual Partitioning</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/CustomSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Manual Partitioning screen. At this point, no partitioning has been configured. The left column shows an option to automatically create a pre-defined layout. An existing Linux system has been detected also and is displayed below the automatic configuration selection. The right side of the screen shows available options for the currently selected mount point.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
When you first open the <guilabel>Manual Partitioning</guilabel> screen, the column on the left side will display all previously existing partitions on all drives which you selected as installation targers in <xref linkend="sect-installation-gui-storage-partitioning" />. If none of the selected drives contain any existing partitions, then a message informing you that no mount points currently exist will appear.
</para>
@@ -57,9 +67,19 @@
<para>
To discard all changes, and to also detect any new drives which have not been detected when the installer started (usually when you attached a new drive after you started), press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press <guilabel>Rescan Disks</guilabel> and wait until the scanning process completes. Then, press <guilabel>OK</guilabel> to return to <xref linkend="sect-installation-gui-storage-partitioning" />; all detected disks including any new ones will be displayed in the <guilabel>Local Standard Disks</guilabel> section.
</para>
- <para>
- <remark>TODO: screen of Rescan Disks</remark>
- </para>
+ <figure>
+ <title>Rescan Disks</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/CustomSpoke_RescanDisks.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Rescan Disks dialog, showing a completed scan. Pressing OK now will take you back to the Installation Destination screen.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
After you finish configuring your system storage, press <guilabel>Done</guilabel> in the top left corner to save the configuration and return to the <guilabel>Installation Summary</guilabel> screen. At this point, the installer will check if your storage configuration is valid. If an error was detected, a message will be displayed at the bottom of the screen. Click the message to open a dialog window explaining what kind of error has been detected (for example, you put <filename class="directory">/boot</filename> on a Btrfs subvolume, or you did not create a BIOS Boot partition when your system requires one).
</para>
diff --git a/en-US/CustomSpoke_AddBtrfs.xml b/en-US/CustomSpoke_AddBtrfs.xml
index 6e4aca9..f083495 100644
--- a/en-US/CustomSpoke_AddBtrfs.xml
+++ b/en-US/CustomSpoke_AddBtrfs.xml
@@ -16,9 +16,19 @@
Some partition types - notably the <filename class="directory">/boot</filename> and <filename class="directory">/usr</filename> directories and the BIOS Boot and EFI partitions - can not be placed on Btrfs subvolumes. Use standard physical volumes for them (or an LVM logical volume for <filename class="directory">/usr</filename>). See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for more information.
</para>
</warning>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Create Btrfs Subvolume</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/CustomSpoke_AddBtrfs.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Manual Partitioning screen, showing available options for a selected Btrfs subvolume.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
Follow the procedure below to create Btrfs volumes and subvolumes:
</para>
diff --git a/en-US/CustomSpoke_AddLVM.xml b/en-US/CustomSpoke_AddLVM.xml
index 3ba4616..5b2cb6c 100644
--- a/en-US/CustomSpoke_AddLVM.xml
+++ b/en-US/CustomSpoke_AddLVM.xml
@@ -16,9 +16,19 @@
Some partition types - notably the <filename class="directory">/boot</filename> directory and the BIOS Boot and EFI partitions - can not be placed on logical volumes. Use standard physical volumes for them. See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for more information.
</para>
</warning>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Create LVM Logical Volume</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/CustomSpoke_AddLVM.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Manual Partitioning screen, showing available options for a selected LVM logical volume.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
Follow the procedure below to create LVM logical volumes and volume groups.
</para>
diff --git a/en-US/CustomSpoke_AddPhysical.xml b/en-US/CustomSpoke_AddPhysical.xml
index 846c28a..923046a 100644
--- a/en-US/CustomSpoke_AddPhysical.xml
+++ b/en-US/CustomSpoke_AddPhysical.xml
@@ -11,9 +11,19 @@
<para>
<remark>TODO: xref to the partitioning appendix</remark>
</para>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Create Standard Partition</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/CustomSpoke_AddPhysical.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Manual Partitioning screen, showing available options for a selected standard partition.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
Follow the procedure below to create mount points on standard physical partitions:
</para>
diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml
index 2dbe59f..bc49335 100644
--- a/en-US/CustomSpoke_FileSystems.xml
+++ b/en-US/CustomSpoke_FileSystems.xml
@@ -46,7 +46,7 @@
<title>File Systems</title>
<listitem>
<para>
- <guilabel>ext4</guilabel> - The ext4 file system is based on the ext3 file system and features a number of improvements. These include support for larger file systems and larger files, faster and more efficient allocation of disk space, no limit on the number of subdirectories within a directory, faster file system checking, and more robust journaling. Ext4 is the default and recommended file system used by &PRODUCT; The maximum supported size of a single ext4 file system is 50 TB.
+ <guilabel>ext4</guilabel> - The ext4 file system is based on the ext3 file system and features a number of improvements. These include support for larger file systems and larger files, faster and more efficient allocation of disk space, no limit on the number of subdirectories within a directory, faster file system checking, and more robust journaling. Ext4 is the default and recommended file system used by &PRODUCT;. The maximum supported size of a single ext4 file system is 50 TB.
</para>
</listitem>
<listitem>
diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml
index 7cd1fcc..b103fed 100644
--- a/en-US/CustomSpoke_RecommendedScheme.xml
+++ b/en-US/CustomSpoke_RecommendedScheme.xml
@@ -20,7 +20,7 @@
If your system has a hardware RAID controller, be aware that some BIOS types do not support booting from it. In that case, the <filename class="directory">/boot</filename> partition must be created on a partition outside of the RAID array, such as on a separate hard drive.
</para>
<para>
- Also note that the <filename class="directory">/boot</filename> can not be placed on a LVM logical volume or a Btrfs subvolume. Use a standard partition.
+ Also note that the <filename class="directory">/boot</filename> directory can not be placed on a LVM logical volume or a Btrfs subvolume. Use a standard partition.
</para>
</important>
</listitem>
diff --git a/en-US/CustomSpoke_SoftwareRAID.xml b/en-US/CustomSpoke_SoftwareRAID.xml
index 33a7654..4130eab 100644
--- a/en-US/CustomSpoke_SoftwareRAID.xml
+++ b/en-US/CustomSpoke_SoftwareRAID.xml
@@ -16,9 +16,19 @@
This section only explains how to create software RAID with standard (physical) partitions. However, you can also configure LVM volume groups and Btrfs volumes to use RAID and place their logical volumes or Btrfs subvolumes on top of this RAID array. See <xref linkend="sect-installation-gui-manual-partitioning-lvm" /> and <xref linkend="sect-installation-gui-manual-partitioning-btrfs" /> for instructions on creating RAID in LVM and Btrfs.
</para>
</important>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Create Software RAID</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/CustomSpoke_SoftwareRAID.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Manual Partitioning screen, showing available options for a selected standard partition on software RAID. The RAID Level menu is open, showing all available RAID levels.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<note>
<para>
RAID configuration options are only visible if you have selected two or more disks for installation. At least two disks are required to create a RAID device, and some RAID layouts will require more. Requirements for different types of RAID are described in <xref linkend="sect-installation-gui-manual-partitioning-filesystems" />.
diff --git a/en-US/DateTimeSpoke.xml b/en-US/DateTimeSpoke.xml
index 5a1ce98..1286575 100644
--- a/en-US/DateTimeSpoke.xml
+++ b/en-US/DateTimeSpoke.xml
@@ -8,9 +8,19 @@
<para>
The <guilabel>Date & Time</guilabel> screen allows you to configure time and date-related settings for your system. This screen is automatically configured based on the settings you selected in <xref linkend="sect-installation-gui-welcome" />, but you can change your date, time and location settings before you begin the installation.
</para>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Date & Time</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/DateTimeSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ Screenshot of the Date & Time screen, showing a map in the center, region and city selection on top, and manual time settings at the bottom.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
First, select your <guilabel>Region</guilabel> using the drop-down menu in the top left corner of the screen. Then, select your <guilabel>City</guilabel>, or the city closest to your location in the same time zone. Selecting a specific location helps &PRODUCT; ensure that your time is always set correctly including automatic time changes for daylight savings time if applicable.
</para>
@@ -25,9 +35,19 @@
<para>
The switch labeled <guilabel>Network Time</guilabel> in the top right corner of the screen can be used to enable or disable network time synchronization using the Network Time Protol (NTP). Enabling this option will keep your system time correct as long as the system can access the internet. By default, four NTP <firstterm>pools</firstterm> are configured; you can add others and disable or remove the default ones by clicking the gear wheel button next to the switch.
</para>
- <para>
- <remark>TODO: screen with adding/removing NTP pools</remark>
- </para>
+ <figure>
+ <title>The Add and mark for usage NTP servers dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/DateTimeSpoke_AddNTP.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ A dialog window allowing you to add or remove NTP pools from your system configuration, check their status and mark them for use.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
If you disable network time synchronization, the controls at the bottom of the screen will become active, and you will be able to set the current time and date manually.
</para>
diff --git a/en-US/FilterSpoke.xml b/en-US/FilterSpoke.xml
index e5a4245..42bd868 100644
--- a/en-US/FilterSpoke.xml
+++ b/en-US/FilterSpoke.xml
@@ -13,9 +13,19 @@
This section only explains how to make existing network disks available inside the installer. It does not explain how to set up your network or a storage server, only how to connect to them.
</para>
</important>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Installation Destination - Network Storage Filters</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/FilterSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ A list of currently configured network storage devices, displaying one configured iSCSI target.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
The screen contains a list of all currently available (discovered) network storage devices. When the screen is opened for the first time, the list will be empty in most cases because no network storage has been discovered - the installer makes no attempt at discovering this unless you configure network disks using a Kickstart file.
</para>
diff --git a/en-US/InitialSetupHub.xml b/en-US/InitialSetupHub.xml
index 717cdd2..f3a68b4 100644
--- a/en-US/InitialSetupHub.xml
+++ b/en-US/InitialSetupHub.xml
@@ -30,9 +30,19 @@
</para>
</listitem>
</itemizedlist>
- <para>
- <remark>TODO: screen with --reconfig</remark>
- </para>
+ <figure>
+ <title>Initial Setup</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/InitialSetupHub.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The main Initial Setup screen. This example shows all options; not all of them may be shown, depending on your configuration.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
<application>Initial Setup</application> allows you to configure several system settings. All of these can also be configured during the installation, but they are not required to finish it. Only the settings which have <emphasis>not</emphasis> been configured during the installation will be shown; for example, if you did not create a non-<systemitem class="username">root</systemitem> user account during the installation, <application>Initial Setup</application> will start after the first reboot, and you will be able to configure one. If you configured all available options during the instalaltion, <application>Initial Setup</application> will not be displayed at all.
</para>
diff --git a/en-US/KeyboardSpoke.xml b/en-US/KeyboardSpoke.xml
index 0ecc551..2739e3b 100644
--- a/en-US/KeyboardSpoke.xml
+++ b/en-US/KeyboardSpoke.xml
@@ -16,9 +16,19 @@
All settings configured in this screen will be available on the installed system, and they will also become immediately available inside the installer. You can use the keyboard icon in the top right corner of any screen, or the keyboard switch you configured in this screen, to cycle between your configured layouts.
</para>
</note>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Keyboard Layout</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/KeyboardSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The keyboard layout configuration screen, showing several additional layouts configured in the left column.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
The right half of the screen contains a window listing all currently configured layouts. The order in which the layouts are displayed is important - the same order will be used when switching between layouts, and the first listed layout will be the default on your system.
</para>
diff --git a/en-US/LangSupportSpoke.xml b/en-US/LangSupportSpoke.xml
index ca1da58..5da7543 100644
--- a/en-US/LangSupportSpoke.xml
+++ b/en-US/LangSupportSpoke.xml
@@ -16,9 +16,19 @@
Adding support for another language does not automatically configure the corresponding keyboard layout. Layouts are a separate setting configured in <xref linkend="sect-installation-gui-keyboard-layout" />.
</para>
</note>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Language Support</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/LangSupportSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The language configuration screen. The left side shows that at least one variant of English and French have been selected; the right column shows that French (France) and French (Canada) are selected in the currently highlighted French group.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
The left panel contains a list of available language groups such as <guilabel>English</guilabel> or <guilabel>Bulgarian</guilabel>. If at least one language from a group is selected, a check mark will be displayed next to the group, and the list entry will be highlighted. This allows you to easily see which languages you have configured support for.
</para>
diff --git a/en-US/NetworkSpoke.xml b/en-US/NetworkSpoke.xml
index 731b735..7f410e0 100644
--- a/en-US/NetworkSpoke.xml
+++ b/en-US/NetworkSpoke.xml
@@ -13,9 +13,19 @@
Network configuration is an expansive topic and many of the options available during the installation are beyond the scope of this document. For detailed information about networking, including both theoretical topics and specific instructions and examples, see the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
</note>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Network & Hostname</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/NetworkSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Network & Hostname screen. In the left pane, one physical interface and one custom VLAN interface is shown; the right side shows details of the currently selected interface. System hostname is configured at the bottom.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
Locally accessible interfaces are automatically detected by the installation program and cannot be manually added or deleted. All detected interfaces are listed on the left side of the screen. Click an interface in the list to display its current configuration (such as IP and DNS address); the details are displayed on the right side of the screen.
</para>
diff --git a/en-US/PasswordSpoke.xml b/en-US/PasswordSpoke.xml
index 631439e..b6bb9a5 100644
--- a/en-US/PasswordSpoke.xml
+++ b/en-US/PasswordSpoke.xml
@@ -16,9 +16,19 @@
The <systemitem class="username">root</systemitem> account has complete control over the system. If an unauthorized person gains access to this account, access or delete all users' personal files or otherwise exploit the machine for their own nefarious purposes. See the <citetitle>&PRODUCT; Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for detailed documentation about account security and guidelines for choosing a strong password.
</para>
</warning>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Root Password</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/PasswordSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Root Password screen. Use the text input fields to provide your root password.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
Once you choose a strong password, enter it in the <guilabel>Root Password</guilabel> field. The characters you write will be displayed as dots for security. Then, type the same password into the <guilabel>Confirm</guilabel> field to ensure you entered it properly. Both entered passwords must be the same.
</para>
@@ -32,6 +42,6 @@
If a message similar to the above appears, it is highly recommended to choose a different, stronger password.
</para>
<para>
- Once you configure the superuser password, click <guilabel>Done</guilabel> in the top left corner to return to the <remark>TODO: add a spoke for the progress screen</remark>. If you selected a weak password, you must press the button twice.
+ Once you configure the superuser password, click <guilabel>Done</guilabel> in the top left corner to return to <xref linkend="sect-installation-gui-installation-progress" />. If you selected a weak password, you must press the button twice.
</para>
</section>
\ No newline at end of file
diff --git a/en-US/ProgressHub.xml b/en-US/ProgressHub.xml
index 1d54757..4eedb38 100644
--- a/en-US/ProgressHub.xml
+++ b/en-US/ProgressHub.xml
@@ -8,9 +8,19 @@
<para>
The <guilabel>Configuration</guilabel> screen is displayed after you finish configuring all required items in <xref linkend="sect-installation-gui-installation-summary" /> and press the <guilabel>Begin installation</guilabel> button. After this point, the installation process actually starts and changes are being made to your selected disks. It is not possible to go back to the <guilabel>Installation Summary</guilabel> and change any settings configured there; if you need to do so, you must wait for the installation process to finish, reboot your system, log in and change your settings on the installed system.
</para>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Configuration and Installation Progress</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/ProgressHub.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Configuration screen. Two more screens at the top require configuration. Installation progress is displayed at the bottom.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
In the top part of the screen, two additional options are available, allowing you to configure authentication settings - the <systemitem class="username">root</systemitem> password and an additional user account. Configuring the <systemitem class="username">root</systemitem> password is required to finish the installation; creating a user account can be skipped. If you do so, you will be prompted to create a non-root user account after the installation finishes and your system reboots.
</para>
diff --git a/en-US/SoftwareSpoke.xml b/en-US/SoftwareSpoke.xml
index acee8a2..9fb56b8 100644
--- a/en-US/SoftwareSpoke.xml
+++ b/en-US/SoftwareSpoke.xml
@@ -19,9 +19,19 @@
<para>
The availability of environments and add-ons depends on your installation source. By default, the selection depends on the installation media you used to start the installation; Fedora Server installation image will have different environments and add-ons available for selection than, for example, the Fedora Cloud image. You can change this by configuring a different installation source containing different environments.
</para>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Software Selection</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/SoftwareSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Software Selection screen. On the left side, one environment (Fedora Workstation) is selected; the right side displays several optional add-ons (such as LibreOffice and Books and Guides) selected in addition to it.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
To configure your software selection, first choose an environment on the left side of the screen. Only one environment can be chosen, even if more are available. Then, on the right side of the screen, select one or more add-ons which you want to install by marking the check boxes next to each add-on.
</para>
diff --git a/en-US/SourceSpoke.xml b/en-US/SourceSpoke.xml
index 79f5967..5b99f05 100644
--- a/en-US/SourceSpoke.xml
+++ b/en-US/SourceSpoke.xml
@@ -13,9 +13,19 @@
Some preparation may be necessary to create an installation source. See <xref linkend="sect-preparing-installation-sources" /> for instructions.
</para>
</note>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Installation Source</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/SourceSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Installation Source screen, configured to download packages to be installed from the closest network mirror. An options to use a locally available ISO file is displayed above.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
The following options are available. Note that not all of them may be displayed.
</para>
diff --git a/en-US/StorageSpoke.xml b/en-US/StorageSpoke.xml
index 45db3e8..c286e21 100644
--- a/en-US/StorageSpoke.xml
+++ b/en-US/StorageSpoke.xml
@@ -16,9 +16,19 @@
If you plan to use a disk which already contains some data - for example, if you want to shrink an existing Microsoft Windows partition and install &PRODUCT; as a second system or if you are upgrading a previous release of &PRODUCT;, make sure to back up any important data first. Manipulating partitions always carries a risk - if the process is interrupted or fails for any reason (installer error, hardware failure, power outage, etc.), any data already on the disk may become impossible to recover.
</para>
</warning>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Installation Destination</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/StorageSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Installation Destination screen. There are two local standard disks available, but none are selected; therefore the options at the bottom of the screen (automatic/manual partitioning, encryption, etc.) are grayed out.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
In the top part of the screen, all locally available storage devices (SATA, IDE and SCSI hard drives, USB flash drives, etc.) are displayed in the <guilabel>Local Standard Disks</guilabel> section. Local disks are detected when the installer starts - any storage devices connected after the installation has started will not be shown.
</para>
@@ -36,9 +46,19 @@
USB storage devices such as flash drives and external disks will be shown in the <guilabel>Local Standard Disks</guilabel> as well, and they will be available for selection the same way internal hard drives are. Make sure to <emphasis>not</emphasis> select any removable storage as installation targets unless you really want to do so. If you accidentally use a removable drive to install &PRODUCT; and then unplug it, your system will likely become unusable.
</para>
</important>
- <para>
- <remark>TODO: screen with a selected and an unselected disk</remark>
- </para>
+ <figure>
+ <title>Unselected and Selected Disk</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/StorageSpoke_Selected.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ Disk selection in the Installation Destination screen. Two disks are displayed; only the one on the right side will be used, because it is the only one with a check mark symbol.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
After you select all disks you want to install &PRODUCT;, select one of the two options in the <guilabel>Other Storage Options</guilabel> section:
</para>
diff --git a/en-US/StorageSpoke_BootLoader.xml b/en-US/StorageSpoke_BootLoader.xml
index aca52e2..9d2785b 100644
--- a/en-US/StorageSpoke_BootLoader.xml
+++ b/en-US/StorageSpoke_BootLoader.xml
@@ -19,9 +19,19 @@
<para>
To specify which device the boot loader should be installed on, click the <guilabel>Full disk summary and bootloader</guilabel> link at the bottom of the <guilabel>Installation Destination</guilabel> screen. The <guilabel>Selected Disks</guilabel> dialog will appear. If you are configuring your partitioning layout manually, the same dialog can be accessed from <xref linkend="sect-installation-gui-manual-partitioning" /> using the <guilabel><replaceable>X</replaceable> storage devices selected</guilabel> link in the bottom left corner of the screen.
</para>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Boot Device Selection</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/StorageSpoke_BootLoader.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Selected Disks dialog, displaying all disks selected as installation targets and allowing you to set one of them as a boot device. The boot loader will be installed onto that device.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
In the <guilabel>Boot</guilabel> column, a "tick" icon marks one of the devices as the intended boot device. To change the boot device, select a device from the list and click the <guilabel>Set as Boot Device</guilabel> button to install the boot loader there instead. Only one device can be set as the boot device.
</para>
diff --git a/en-US/SummaryHub.xml b/en-US/SummaryHub.xml
index da24d93..94b48ff 100644
--- a/en-US/SummaryHub.xml
+++ b/en-US/SummaryHub.xml
@@ -8,9 +8,19 @@
<para>
The <guilabel>Installation Summary</guilabel> screen is the central location for setting up an installation. Most of the options which can be configured during the installation can be accessed from here.
</para>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Installation Summary</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/SummaryHub.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Installation Summary screen, showing most of the options configured. The Installation Destination icon has a warning sign, which means it requires the user's attention before the installation can proceed.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<note>
<para>
If you used a Kickstart option or a boot option to specify an installation repository on a network, but no network is available at the start of the installation, the installer will display the <guilabel>Network Configuration</guilabel> screen for you to set up a network connection prior to displaying the <guilabel>Installation Summary</guilabel> screen.
@@ -39,15 +49,35 @@
<para>
A warning message is displayed at the bottom of the summary screen, and the <guilabel>Begin Installation</guilabel> button is greyed out, as long as at least one item has not been configured yet.
</para>
- <para>
- <remark>TODO: screen showing all the different states</remark>
- </para>
+ <figure>
+ <title>Icon States in Installation Summary</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/SummaryHub_States.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ A screenshot of several icons in the Installation Summary screen, showing the different states (configured, needs attention, unavailable).
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
Each screen also has an explanatory text below its title, showing settings currently configured in that screen. This text may be concatenated; in that case, move your mouse cursor over it and wait until a tooltip with the full text appears.
</para>
- <para>
- <remark>TODO: screen showing shortened text on a spoke and a full tooltip</remark>
- </para>
+ <figure>
+ <title>Tooltip in the Installation Summary</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/SummaryHub_Mouseover.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ An entry in the Installation Summary shows a truncated description and a tooltip with full text.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
Once you configure everything required for the installation, you can press the <guilabel>Begin Installation</guilabel> button to start installing &PRODUCT;. This will take you to <xref linkend="sect-installation-gui-installation-progress" />. Note that as the text below this button says, nothing will be written to your hard drive before you press this button. You can press <guilabel>Quit</guilabel> at any point; this will discard all changes you made in the installer so far and reboot the system.
</para>
diff --git a/en-US/UserSpoke.xml b/en-US/UserSpoke.xml
index f4aeb9e..1d3ec3d 100644
--- a/en-US/UserSpoke.xml
+++ b/en-US/UserSpoke.xml
@@ -13,9 +13,19 @@
Creating a normal user account is not required to finish the installation; however, it is highly recommended. If you do not create one, you will have to log in to the system as <systemitem class="username">root</systemitem> directly, which is <emphasis>not</emphasis> recommended.
</para>
</important>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Create User</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/UserSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The Create screen. Use the text input fields to create a user account and configure its settings.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
To configure a user account, fill out the <guilabel>Full name</guilabel> (for example, <literal>John Smith</literal>) and <guilabel>Username</guilabel> (for example, <literal>jsmith</literal>). The <guilabel>username</guilabel> will used to log in from a command line; if you install a graphical environment, then your graphical login manager will use <guilabel>Full name</guilabel>.
</para>
@@ -49,8 +59,21 @@
<section id="sect-installation-gui-create-user-advanced">
<title>Advanced User Configuration</title>
<para>
- The <guilabel>Advanced User Configuration</guilabel> dialog allows you to change the following settings for the new user account:
+ The <guilabel>Advanced User Configuration</guilabel> dialog allows you to change the following settings for the new user account.
</para>
+ <figure>
+ <title>Advanced User Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/UserSpoke_Advanced.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ Advanced settings for the new user account.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<itemizedlist>
<listitem>
<para>
diff --git a/en-US/WelcomeSpoke.xml b/en-US/WelcomeSpoke.xml
index 363435f..f229b1f 100644
--- a/en-US/WelcomeSpoke.xml
+++ b/en-US/WelcomeSpoke.xml
@@ -8,9 +8,19 @@
<para>
The first screen displayed immediately after the graphical installer starts is the Welcome screen.
</para>
- <para>
- <remark>TODO: screen</remark>
- </para>
+ <figure>
+ <title>Welcome Screen</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/WelcomeSpoke.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ Screenshot of the Welcome screen showing language selection options.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
First, select your preferred language in the left hand side column, and then select your locale from the right hand side column. You can use the text input field in the bottom left corner to search for your language instead of looking for it in the full list of more than 70 languages.
</para>
diff --git a/en-US/images/anaconda/CustomSpoke.png b/en-US/images/anaconda/CustomSpoke.png
new file mode 100644
index 0000000..145d9eb
Binary files /dev/null and b/en-US/images/anaconda/CustomSpoke.png differ
diff --git a/en-US/images/anaconda/CustomSpoke_AddBtrfs.png b/en-US/images/anaconda/CustomSpoke_AddBtrfs.png
new file mode 100644
index 0000000..88553d8
Binary files /dev/null and b/en-US/images/anaconda/CustomSpoke_AddBtrfs.png differ
diff --git a/en-US/images/anaconda/CustomSpoke_AddLVM.png b/en-US/images/anaconda/CustomSpoke_AddLVM.png
new file mode 100644
index 0000000..c76a5cf
Binary files /dev/null and b/en-US/images/anaconda/CustomSpoke_AddLVM.png differ
diff --git a/en-US/images/anaconda/CustomSpoke_AddPhysical.png b/en-US/images/anaconda/CustomSpoke_AddPhysical.png
new file mode 100644
index 0000000..a700154
Binary files /dev/null and b/en-US/images/anaconda/CustomSpoke_AddPhysical.png differ
diff --git a/en-US/images/anaconda/CustomSpoke_RescanDisks.png b/en-US/images/anaconda/CustomSpoke_RescanDisks.png
new file mode 100644
index 0000000..53cc560
Binary files /dev/null and b/en-US/images/anaconda/CustomSpoke_RescanDisks.png differ
diff --git a/en-US/images/anaconda/CustomSpoke_SoftwareRAID.png b/en-US/images/anaconda/CustomSpoke_SoftwareRAID.png
new file mode 100644
index 0000000..11060ff
Binary files /dev/null and b/en-US/images/anaconda/CustomSpoke_SoftwareRAID.png differ
diff --git a/en-US/images/anaconda/DateTimeSpoke.png b/en-US/images/anaconda/DateTimeSpoke.png
new file mode 100644
index 0000000..4bee16e
Binary files /dev/null and b/en-US/images/anaconda/DateTimeSpoke.png differ
diff --git a/en-US/images/anaconda/DateTimeSpoke_AddNTP.png b/en-US/images/anaconda/DateTimeSpoke_AddNTP.png
new file mode 100644
index 0000000..d71e295
Binary files /dev/null and b/en-US/images/anaconda/DateTimeSpoke_AddNTP.png differ
diff --git a/en-US/images/anaconda/FilterSpoke.png b/en-US/images/anaconda/FilterSpoke.png
new file mode 100644
index 0000000..3edd731
Binary files /dev/null and b/en-US/images/anaconda/FilterSpoke.png differ
diff --git a/en-US/images/anaconda/InitialSetupHub.png b/en-US/images/anaconda/InitialSetupHub.png
new file mode 100644
index 0000000..060e0ae
Binary files /dev/null and b/en-US/images/anaconda/InitialSetupHub.png differ
diff --git a/en-US/images/anaconda/KeyboardSpoke.png b/en-US/images/anaconda/KeyboardSpoke.png
new file mode 100644
index 0000000..8232580
Binary files /dev/null and b/en-US/images/anaconda/KeyboardSpoke.png differ
diff --git a/en-US/images/anaconda/LangSupportSpoke.png b/en-US/images/anaconda/LangSupportSpoke.png
new file mode 100644
index 0000000..22fb1d9
Binary files /dev/null and b/en-US/images/anaconda/LangSupportSpoke.png differ
diff --git a/en-US/images/anaconda/NetworkSpoke.png b/en-US/images/anaconda/NetworkSpoke.png
new file mode 100644
index 0000000..5878fd1
Binary files /dev/null and b/en-US/images/anaconda/NetworkSpoke.png differ
diff --git a/en-US/images/anaconda/PasswordSpoke.png b/en-US/images/anaconda/PasswordSpoke.png
new file mode 100644
index 0000000..33e2357
Binary files /dev/null and b/en-US/images/anaconda/PasswordSpoke.png differ
diff --git a/en-US/images/anaconda/ProgressHub.png b/en-US/images/anaconda/ProgressHub.png
new file mode 100644
index 0000000..3c4bd08
Binary files /dev/null and b/en-US/images/anaconda/ProgressHub.png differ
diff --git a/en-US/images/anaconda/SoftwareSpoke.png b/en-US/images/anaconda/SoftwareSpoke.png
new file mode 100644
index 0000000..4588183
Binary files /dev/null and b/en-US/images/anaconda/SoftwareSpoke.png differ
diff --git a/en-US/images/anaconda/SourceSpoke.png b/en-US/images/anaconda/SourceSpoke.png
new file mode 100644
index 0000000..f2a384c
Binary files /dev/null and b/en-US/images/anaconda/SourceSpoke.png differ
diff --git a/en-US/images/anaconda/StorageSpoke.png b/en-US/images/anaconda/StorageSpoke.png
new file mode 100644
index 0000000..1e34bbe
Binary files /dev/null and b/en-US/images/anaconda/StorageSpoke.png differ
diff --git a/en-US/images/anaconda/StorageSpoke_BootLoader.png b/en-US/images/anaconda/StorageSpoke_BootLoader.png
new file mode 100644
index 0000000..d3ab511
Binary files /dev/null and b/en-US/images/anaconda/StorageSpoke_BootLoader.png differ
diff --git a/en-US/images/anaconda/StorageSpoke_Selected.png b/en-US/images/anaconda/StorageSpoke_Selected.png
new file mode 100644
index 0000000..28a5624
Binary files /dev/null and b/en-US/images/anaconda/StorageSpoke_Selected.png differ
diff --git a/en-US/images/anaconda/SummaryHub.png b/en-US/images/anaconda/SummaryHub.png
new file mode 100644
index 0000000..03a61de
Binary files /dev/null and b/en-US/images/anaconda/SummaryHub.png differ
diff --git a/en-US/images/anaconda/SummaryHub_Mouseover.png b/en-US/images/anaconda/SummaryHub_Mouseover.png
new file mode 100644
index 0000000..7e4f28b
Binary files /dev/null and b/en-US/images/anaconda/SummaryHub_Mouseover.png differ
diff --git a/en-US/images/anaconda/SummaryHub_States.png b/en-US/images/anaconda/SummaryHub_States.png
new file mode 100644
index 0000000..539a786
Binary files /dev/null and b/en-US/images/anaconda/SummaryHub_States.png differ
diff --git a/en-US/images/anaconda/UserSpoke.png b/en-US/images/anaconda/UserSpoke.png
new file mode 100644
index 0000000..f6cff6f
Binary files /dev/null and b/en-US/images/anaconda/UserSpoke.png differ
diff --git a/en-US/images/anaconda/UserSpoke_Advanced.png b/en-US/images/anaconda/UserSpoke_Advanced.png
new file mode 100644
index 0000000..efa2df9
Binary files /dev/null and b/en-US/images/anaconda/UserSpoke_Advanced.png differ
diff --git a/en-US/images/anaconda/WelcomeSpoke.png b/en-US/images/anaconda/WelcomeSpoke.png
new file mode 100644
index 0000000..ae0bb2e
Binary files /dev/null and b/en-US/images/anaconda/WelcomeSpoke.png differ
9 years, 3 months
[release-notes] Created tag 21.08
by Pete Travis
The unsigned tag '21.08' was created.
Tagger: Pete Travis <immanetize(a)fedoraproject.org>
Date: Thu Nov 27 12:35:45 2014 -0700
Many revisions to F21 RNs
Changes since the last tag '21.06':
Barbora Ancincova (1):
Added the rewheel module to the Python release note.
Pete Travis (60):
remove prerelease content in preparation for F21
Adding containers for Product beats, and a fedora.next/product intro
Use an entity for the link to the Change page instead of a static link to the Features page, and only link there once.
Fedora Workstation is for desktop users, especially developers. It uses GNOME.
bump revision history
Consistent DTD declaration with correct DOCTYPE
Fedora Workstation has captive portal detection
Describe the Workstation Firewall
No PPC32
some monitoring stuff
Eclipse Luna
PHP, jquery+webassets
courtesy merge
markup fix
rails
jdk8, plus java subpackages
boost bump, new GCC
new make, and Jenkins
reviewboard
The Development beat, including: - Python3 - Ruby - RPM - TCL/TK - Erlang/OTP - OpenCL
Systemd - remote journal, private services.
some systemd stateless system enhancements, and more notes in comments (TODO)
modular kernel packaging
too much info about systemd
the best thing about systemd is
autofs amd maps
s/rpstream/upstream/
SHOGUN machine learning toolkit
Converting i18n beat
more on libzhuyin
add an ARM page, and talk about Aaarch64 emulation there.
syncing includes
some include changes, bonus merge
gpodder update info
typos
remove bitmap fill layer from svg icon.
repo, merge thyself
typos
txconfig
adding missing packagename
a script to preform nightly builds for translator preview.
slopmerge.
Spins! Oh, and some adjustments to the hardware overview.
Merge branch 'master' of ssh://git.fedorahosted.org/git/docs/release-notes
comment out spins without composes listed at http://dl.fedoraproject.org/pub/alt/stage/21_Beta_TC4/Spins/x86_64/
Adapting the RNs feedback content. We don't actually want people to be editing the wiki at this point.
no role deployments in anaconda for F21
let's put the cloud stuff in the Cloud product beat
Updating kernel version entity
some notes on the reduced size of cloud images
adopt your cattle
typo
typo
Merge branch 'master' of ssh://git.fedorahosted.org/git/docs/release-notes
a couple typos, fresh POTs
cockpit port
sent fresh POTs
fedora-release conflicts
server for netinstall, NO DVD
varieties of Cloud images
Petr Bokoc (21):
Fixing bad elements
Adding first 3 sections to Installation
Adding CLI options to Installer + turning simplelists to itemizedlists
Fixing a broken build and adding a few unincluded XMLs
Fixing a bad include
Adding the rest of the Installer section
Fixing a broken build and cleaning up Products-Server.xml
better .gitignore
Adding CUPS journal logging
Small streamlining in System Daemons
Adding the Server Configuration Tools category
Adding PrivateDevices and PrivateNetwork to System Daemons
Adding Scala ecosystem to Development
Including Development beat
Improving the Optional Javadocs change in Development-Java
Including Java and Development Tools section into Changes for Developers
Cleaning up the Java pkg guidelines changes in Development-Java
Merges, merges everywhere
Adding anaconda's shiny new built-in help to the Installer beat
Removing duplicate content from Installation
No localized Anaconda help for you
Petr Kovar (2):
Update Fedora desktop content
Fix build for F21 RN
Robert Krátký (4):
Add section on KDE 4.14 and SDDM.
Add section on KDE Frameworks 5.
Merge branch 'master' of ssh://git.fedorahosted.org/git/docs/release-notes
Improved desc. based on feedback by dvratil. Thanks.
Simon Clark (26):
Removed jQuery section as the change has been put back to F22.
Added section for Apache Accumulo
Added section for Apache Ambari
Expanded entry for Apache HBase
Expanded the Apache Hive entry.
Added new sub-section for Cluster under Sysadmin
Added new entry for Apache Mesos
Moved Apache Ambari entry from Database Servers to Cluster
Added entry for Apache Oozie
Added an entry for Apache Pig.
Corrected a typo
Added an entry for Apache Spark.
Added an entry for NFS Ganesha file server.
Tweaked file servers section some more.
Added entry for Improved Ivy Packaging.
Updated the Apache Accumulo entry.
Added an entry for sssd GPO-Based Access Control.
Revised SSSD GPO Access Control entry.
Amended the entry for Improved Ivy Packaging.
Added an entry for Allwinner sunxi ARM SoC Support.
Typo
Updated the entry for Allwinner sunxi ARM SoC Support.
Corrected a typo.
Corrected some typos.
Corrected a typo.
Fixed a typo.
Zach Oglesby (2):
Database Server converted to XML from wiki
Converted Server Specific Content Beat to XML
9 years, 3 months
[system-administrators-guide] Updates to suit Fedora 20
by stephenw
commit 570b5576dcfd34d131513a0bdf062bf2f9a0ada1
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Tue Nov 25 22:13:55 2014 +0100
Updates to suit Fedora 20
en-US/OpenSSH.xml | 576 ++++++++++++++++++++++-------------------------------
1 files changed, 235 insertions(+), 341 deletions(-)
---
diff --git a/en-US/OpenSSH.xml b/en-US/OpenSSH.xml
index 7239f8e..846646f 100644
--- a/en-US/OpenSSH.xml
+++ b/en-US/OpenSSH.xml
@@ -7,13 +7,13 @@
<primary>OpenSSH</primary>
</indexterm>
<para>
- <systemitem class="protocol">SSH</systemitem> (Secure Shell) is a protocol which facilitates secure communications between two systems using a client/server architecture and allows users to log into server host systems remotely. Unlike other remote communication protocols, such as <systemitem class="protocol">FTP</systemitem> or <systemitem class="protocol">Telnet</systemitem>, SSH encrypts the login session, rendering the connection difficult for intruders to collect unencrypted passwords.
+ <systemitem class="protocol">SSH</systemitem> (Secure Shell) is a protocol which facilitates secure communications between two systems using a client-server architecture and allows users to log in to server host systems remotely. Unlike other remote communication protocols, such as <systemitem class="protocol">FTP</systemitem> or <systemitem class="protocol">Telnet</systemitem>, SSH encrypts the login session, rendering the connection difficult for intruders to collect unencrypted passwords.
</para>
<para>
- The <application>ssh</application> program is designed to replace older, less secure terminal applications used to log into remote hosts, such as <command>telnet</command> or <command>rsh</command>. A related program called <command>scp</command> replaces older programs designed to copy files between hosts, such as <command>rcp</command>. Because these older applications do not encrypt passwords transmitted between the client and the server, avoid them whenever possible. Using secure methods to log into remote systems decreases the risks for both the client system and the remote host.
+ The <application>ssh</application> program is designed to replace older, less secure terminal applications used to log in to remote hosts, such as <command>telnet</command> or <command>rsh</command>. A related program called <command>scp</command> replaces older programs designed to copy files between hosts, such as <command>rcp</command>. Because these older applications do not encrypt passwords transmitted between the client and the server, avoid them whenever possible. Using secure methods to log in to remote systems decreases the risks for both the client system and the remote host.
</para>
<para>
- &MAJOROS; includes the general OpenSSH package (<package>openssh</package>) as well as the OpenSSH server (<package>openssh-server</package>) and client (<package>openssh-clients</package>) packages. Note that the OpenSSH packages require the OpenSSL package (<package>openssl</package>), which installs several important cryptographic libraries, enabling OpenSSH to provide encrypted communications.
+ &MAJOROS; includes the general OpenSSH package, <package>openssh</package>, as well as the OpenSSH server, <package>openssh-server</package>, and client, <package>openssh-clients</package>, packages. Note, the OpenSSH packages require the OpenSSL package <package>openssl-libs</package>, which installs several important cryptographic libraries, enabling OpenSSH to provide encrypted communications.
</para>
<section id="s1-ssh-protocol">
<title>The SSH Protocol</title>
@@ -289,8 +289,13 @@
<secondary>configuration files</secondary>
<tertiary>system-wide configuration files</tertiary>
</indexterm>
+ <indexterm>
+ <primary>SSH protocol</primary>
+ <secondary>configuration files</secondary>
+ <tertiary>user-specific configuration files</tertiary>
+ </indexterm>
<para>
- System-wide SSH configuration information is stored in the <filename>/etc/ssh/</filename> directory. See <xref linkend="table-ssh-configuration-configs-system" /> for a description of its content.
+ System-wide SSH configuration information is stored in the <filename class="directory">/etc/ssh/</filename> directory as described in <xref linkend="table-ssh-configuration-configs-system" />. User-specific SSH configuration information is stored in <filename class="directory">~/.ssh/</filename> within the user's home directory as described in <xref linkend="table-ssh-configuration-configs-user" />.
</para>
<table id="table-ssh-configuration-configs-system">
<title>System-wide configuration files</title>
@@ -299,7 +304,7 @@
<colspec colname="description" colnum="2" colwidth="50*" />
<thead>
<row>
- <entry>Configuration File</entry>
+ <entry>File</entry>
<entry>Description</entry>
</row>
</thead>
@@ -330,18 +335,18 @@
</row>
<row>
<entry>
- <filename>/etc/ssh/ssh_host_dsa_key</filename>
+ <filename>/etc/ssh/ssh_host_ecdsa_key</filename>
</entry>
<entry>
- The DSA private key used by the <command>sshd</command> daemon.
+ The ECDSA private key used by the <command>sshd</command> daemon.
</entry>
</row>
<row>
<entry>
- <filename>/etc/ssh/ssh_host_dsa_key.pub</filename>
+ <filename>/etc/ssh/ssh_host_ecdsa_key.pub</filename>
</entry>
<entry>
- The DSA public key used by the <command>sshd</command> daemon.
+ The ECDSA public key used by the <command>sshd</command> daemon.
</entry>
</row>
<row>
@@ -373,20 +378,28 @@
<filename>/etc/ssh/ssh_host_rsa_key.pub</filename>
</entry>
<entry>
- The RSA public key used by the <command>sshd</command> for version 2 of the SSH protocol.
+ The RSA public key used by the <command>sshd</command> daemon for version 2 of the SSH protocol.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <filename>/etc/pam.d/sshd</filename>
+ </entry>
+ <entry>
+ The PAM configuration file for the <command>sshd</command> daemon.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <filename>/etc/sysconfig/sshd</filename>
+ </entry>
+ <entry>
+ Configuration file for the <systemitem class="daemon">sshd</systemitem> service.
</entry>
</row>
</tbody>
</tgroup>
</table>
- <indexterm>
- <primary>SSH protocol</primary>
- <secondary>configuration files</secondary>
- <tertiary>user-specific configuration files</tertiary>
- </indexterm>
- <para>
- User-specific SSH configuration information is stored in the user's home directory within the <filename>~/.ssh/</filename> directory. See <xref linkend="table-ssh-configuration-configs-user" /> for a description of its content.
- </para>
<table id="table-ssh-configuration-configs-user">
<title>User-specific configuration files</title>
<tgroup cols="2">
@@ -394,7 +407,7 @@
<colspec colname="description" colnum="2" colwidth="50*" />
<thead>
<row>
- <entry>Configuration File</entry>
+ <entry>File</entry>
<entry>Description</entry>
</row>
</thead>
@@ -409,18 +422,18 @@
</row>
<row>
<entry>
- <filename>~/.ssh/id_dsa</filename>
+ <filename>~/.ssh/id_ecdsa</filename>
</entry>
<entry>
- Contains the DSA private key of the user.
+ Contains the ECDSA private key of the user.
</entry>
</row>
<row>
<entry>
- <filename>~/.ssh/id_dsa.pub</filename>
+ <filename>~/.ssh/id_ecdsa.pub</filename>
</entry>
<entry>
- The DSA public key of the user.
+ The ECDSA public key of the user.
</entry>
</row>
<row>
@@ -436,7 +449,7 @@
<filename>~/.ssh/id_rsa.pub</filename>
</entry>
<entry>
- The RSA public key used by <command>ssh</command> for version 2 of the SSH protocol
+ The RSA public key used by <command>ssh</command> for version 2 of the SSH protocol.
</entry>
</row>
<row>
@@ -460,14 +473,14 @@
<filename>~/.ssh/known_hosts</filename>
</entry>
<entry>
- Contains DSA host keys of SSH servers accessed by the user. This file is very important for ensuring that the SSH client is connecting the correct SSH server.
+ Contains host keys of SSH servers accessed by the user. This file is very important for ensuring that the SSH client is connecting to the correct SSH server.
</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
- See the <command>ssh_config</command> and <command>sshd_config</command> man pages for information concerning the various directives available in the SSH configuration files.
+ For information concerning various directives that can be used in the SSH configuration files, see the <filename>ssh_config</filename>(5) and <filename>sshd_config</filename>(5) manual pages.
</para>
</section>
<section id="s2-ssh-configuration-sshd">
@@ -479,7 +492,7 @@
<note>
<title>Make sure you have relevant packages installed</title>
<para>
- To run an OpenSSH server, you must have the <package>openssh-server</package> and <package>openssh</package> packages installed. See <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
+ To run an OpenSSH server, you must have the <package>openssh-server</package> package installed. See <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
</para>
</note>
<indexterm>
@@ -488,22 +501,23 @@
<tertiary>starting</tertiary>
</indexterm>
<para>
- To start the <command>sshd</command> daemon, type the following at a shell prompt:
+ To start the <command>sshd</command> daemon in the current session, type the following at a shell prompt as <systemitem class="username">root</systemitem>:
</para>
- <screen><command>systemctl start sshd.service</command></screen>
+ <screen>~]# <command>systemctl start sshd.service</command></screen>
<indexterm>
<primary>OpenSSH</primary>
<secondary>server</secondary>
<tertiary>stopping</tertiary>
</indexterm>
<para>
- To stop the running <command>sshd</command> daemon, use the following command:
+ To stop the running <command>sshd</command> daemon in the current session, use the following command as <systemitem class="username">root</systemitem>:
</para>
- <screen><command>systemctl stop sshd.service</command></screen>
+ <screen>~]# <command>systemctl stop sshd.service</command></screen>
<para>
- If you want the daemon to start automatically at the boot time, type:
+ If you want the daemon to start automatically at the boot time, type as <systemitem class="username">root</systemitem>:
</para>
- <screen><command>systemctl enable sshd.service</command></screen>
+ <screen>~]# <command>systemctl enable sshd.service</command>
+ln -s '/usr/lib/systemd/system/sshd.service' '/etc/systemd/system/multi-user.target.wants/sshd.service'</screen>
<para>
See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
@@ -517,7 +531,7 @@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.</screen>
<para>
- To prevent this, you can back up the relevant files from the <filename class="directory">/etc/ssh/</filename> directory (see <xref linkend="table-ssh-configuration-configs-system" /> for a complete list), and restore them whenever you reinstall the system.
+ To prevent this, you can backup the relevant files from the <filename class="directory">/etc/ssh/</filename> directory (see <xref linkend="table-ssh-configuration-configs-system" /> for a complete list), and restore them whenever you reinstall the system.
</para>
</section>
<section id="s2-ssh-configuration-requiring">
@@ -534,7 +548,7 @@ It is also possible that the RSA host key has just been changed.</screen>
For SSH to be truly effective, using insecure connection protocols should be prohibited. Otherwise, a user's password may be protected using SSH for one session, only to be captured later while logging in using Telnet. Some services to disable include <command>telnet</command>, <command>rsh</command>, <command>rlogin</command>, and <command>vsftpd</command>.
</para>
<para>
- To make sure these services are not running, type the following commands at a shell prompt:
+ These services are not installed by default in &MAJOROS;. If required, to make sure these services are not running, type the following commands at a shell prompt:
</para>
<screen><command>systemctl stop telnet.service</command>
<command>systemctl stop rsh.service</command>
@@ -552,15 +566,18 @@ It is also possible that the RSA host key has just been changed.</screen>
</para>
</section>
<section id="s2-ssh-configuration-keypairs">
- <title>Using a Key-Based Authentication</title>
+ <title>Using Key-based Authentication</title>
<indexterm>
<primary>OpenSSH</primary>
<secondary>using key-based authentication</secondary>
</indexterm>
<para>
- To improve the system security even further, you can enforce the key-based authentication by disabling the standard password authentication. To do so, open the <filename class="directory">/etc/ssh/sshd_config</filename> configuration file in a text editor, and change the <option>PasswordAuthentication</option> option as follows:
+ To improve the system security even further, generate SSH key pairs and then enforce key-based authentication by disabling password authentication. To do so, open the <filename class="directory">/etc/ssh/sshd_config</filename> configuration file in a text editor such as <application>vi</application> or <application>nano</application>, and change the <option>PasswordAuthentication</option> option as follows:
+ </para>
+ <screen>PasswordAuthentication no</screen>
+ <para>
+ If you are working on a system other than a new default installation, check that <command>PubkeyAuthentication no</command> has <emphasis role="bold">not</emphasis> been set. If connected remotely, not using console or out-of-band access, testing the key-based log in process before disabling password authentication is advised.
</para>
- <programlisting>PasswordAuthentication no</programlisting>
<para>
To be able to use <command>ssh</command>, <command>scp</command>, or <command>sftp</command> to connect to the server from a client machine, generate an authorization key pair by following the steps below. Note that keys must be generated for each user separately.
</para>
@@ -576,7 +593,7 @@ It is also possible that the RSA host key has just been changed.</screen>
<note>
<title>Backup your ~/.ssh/ directory</title>
<para>
- If you reinstall your system and want to keep previously generated key pair, backup the <filename class="directory">~/.ssh/</filename> directory. After reinstalling, copy it back to your home directory. This process can be done for all users on your system, including <systemitem class="username">root</systemitem>.
+ If you reinstall your system and want to keep previously generated key pairs, backup the <filename class="directory">~/.ssh/</filename> directory. After reinstalling, copy it back to your home directory. This process can be done for all users on your system, including <systemitem class="username">root</systemitem>.
</para>
</note>
<section id="s3-ssh-configuration-keypairs-generating">
@@ -603,13 +620,13 @@ It is also possible that the RSA host key has just been changed.</screen>
<para>
Generate an RSA key pair by typing the following at a shell prompt:
</para>
- <screen>~]$ <command>ssh-keygen -t rsa</command>
+ <screen>~]$ <command>ssh-keygen -t rsa</command>
Generating public/private rsa key pair.
-Enter file in which to save the key (/home/john/.ssh/id_rsa):</screen>
+Enter file in which to save the key (/home/USER/.ssh/id_rsa):</screen>
</step>
<step>
<para>
- Press <keycap>Enter</keycap> to confirm the default location (that is, <filename>~/.ssh/id_rsa</filename>) for the newly created key.
+ Press <keycap>Enter</keycap> to confirm the default location, <filename>~/.ssh/id_rsa</filename>, for the newly created key.
</para>
</step>
<step>
@@ -619,10 +636,10 @@ Enter file in which to save the key (/home/john/.ssh/id_rsa):</screen>
<para>
After this, you will be presented with a message similar to this:
</para>
- <screen>Your identification has been saved in /home/john/.ssh/id_rsa.
-Your public key has been saved in /home/john/.ssh/id_rsa.pub.
+ <screen>Your identification has been saved in /home/USER/.ssh/id_rsa.
+Your public key has been saved in /home/USER/.ssh/id_rsa.pub.
The key fingerprint is:
-e7:97:c7:e2:0e:f9:0e:fc:c4:d7:cb:e5:31:11:92:14 john(a)penguin.example.com
+e7:97:c7:e2:0e:f9:0e:fc:c4:d7:cb:e5:31:11:92:14 USER(a)penguin.example.com
The key's randomart image is:
+--[ RSA 2048]----+
| E. |
@@ -638,51 +655,51 @@ The key's randomart image is:
</step>
<step>
<para>
- Change the permissions of the <filename class="directory">~/.ssh/</filename> directory:
- </para>
- <screen>~]$ <command>chmod 755 ~/.ssh</command></screen>
- </step>
- <step>
- <para>
- Copy the content of <filename>~/.ssh/id_rsa.pub</filename> into the <filename>~/.ssh/authorized_keys</filename> on the machine to which you want to connect, appending it to its end if the file already exists.
+ By default, the permissions of the <filename class="directory">~/.ssh/</filename> directory are set to <literal>rwx------</literal> or <literal>700</literal> expressed in octal notation. This is to ensure that only the <replaceable>USER</replaceable> can view the contents. If required, this can be confirmed with the following command:
</para>
+ <screen>~]$ <command>ls -ld ~/.ssh</command>
+ ~]$ ls -ld ~/.ssh/
+drwx------. 2 USER USER 54 Nov 25 16:56 /home/USER/.ssh/</screen>
</step>
<step>
<para>
- Change the permissions of the <filename>~/.ssh/authorized_keys</filename> file using the following command:
+ To copy the public key to a remote machine, issue a command in the following format:
+ <synopsis> <command>ssh-copy-id <replaceable>user@hostname</replaceable></command></synopsis>
+ This will copy all <filename>~/.ssh/id*.pub</filename> public keys. Alternatively, specify the public keys file name as follows:
+ <synopsis><command>ssh-copy-id -i <filename>~/.ssh/id_rsa.pub</filename> <replaceable>user@hostname</replaceable></command></synopsis>
+ This will copy the content of <filename>~/.ssh/id_rsa.pub</filename> into the <filename>~/.ssh/authorized_keys</filename> file on the machine to which you want to connect. If the file already exists, the keys are appended to its end.
</para>
- <screen>~]$ <command>chmod 644 ~/.ssh/authorized_keys</command></screen>
</step>
</procedure>
<indexterm>
- <primary>DSA keys</primary>
+ <primary>ECDSA keys</primary>
<secondary>generating</secondary>
</indexterm>
<indexterm>
<primary>OpenSSH</primary>
- <secondary>DSA keys</secondary>
+ <secondary>ECDSA keys</secondary>
<tertiary>generating</tertiary>
</indexterm>
<para>
- To generate a DSA key pair for version 2 of the SSH protocol, follow these steps:
+ To generate an ECDSA key pair for version 2 of the SSH protocol, follow these steps:
</para>
<indexterm>
<primary>OpenSSH</primary>
<secondary>ssh-keygen</secondary>
- <tertiary>DSA</tertiary>
+ <tertiary>ECDSA</tertiary>
</indexterm>
<procedure>
<step>
<para>
- Generate a DSA key pair by typing the following at a shell prompt:
+ Generate an ECDSA key pair by typing the following at a shell prompt:
</para>
- <screen>~]$ <command>ssh-keygen -t dsa</command>
-Generating public/private dsa key pair.
-Enter file in which to save the key (/home/john/.ssh/id_dsa):</screen>
+ <screen>~]$ <command>ssh-keygen -t ecdsa</command>
+Generating public/private ecdsa key pair.
+Enter file in which to save the key (/home/USER/.ssh/id_ecdsa):</screen>
</step>
<step>
<para>
- Press <keycap>Enter</keycap> to confirm the default location (that is, <filename>~/.ssh/id_dsa</filename>) for the newly created key.
+ Press <keycap>Enter</keycap> to confirm the default location, <filename>~/.ssh/id_ecdsa</filename>, for the newly created key.
</para>
</step>
<step>
@@ -692,114 +709,41 @@ Enter file in which to save the key (/home/john/.ssh/id_dsa):</screen>
<para>
After this, you will be presented with a message similar to this:
</para>
- <screen>Your identification has been saved in /home/john/.ssh/id_dsa.
-Your public key has been saved in /home/john/.ssh/id_dsa.pub.
+ <screen>Your identification has been saved in /home/USER/.ssh/id_ecdsa.
+Your public key has been saved in /home/USER/.ssh/id_ecdsa.pub.
The key fingerprint is:
-81:a1:91:a8:9f:e8:c5:66:0d:54:f5:90:cc:bc:cc:27 john(a)penguin.example.com
+fd:1d:ca:10:52:96:21:43:7e:bd:4c:fc:5b:35:6b:63 USER@my-server
The key's randomart image is:
-+--[ DSA 1024]----+
-| .oo*o. |
-| ...o Bo |
-| .. . + o. |
-|. . E o |
-| o..o S |
-|. o= . |
-|. + |
-| . |
++--[ECDSA 256]---+
+| .+ +o |
+| . =.o |
+| o o + ..|
+| + + o +|
+| S o o oE.|
+| + oo+.|
+| + o |
| |
-+-----------------+</screen>
- </step>
- <step>
- <para>
- Change the permissions of the <filename class="directory">~/.ssh/</filename> directory:
- </para>
- <screen>~]$ <command>chmod 775 ~/.ssh</command></screen>
- </step>
- <step>
- <para>
- Copy the content of <filename>~/.ssh/id_dsa.pub</filename> into the <filename>~/.ssh/authorized_keys</filename> on the machine to which you want to connect, appending it to its end if the file already exists.
- </para>
- </step>
- <step>
- <para>
- Change the permissions of the <filename>~/.ssh/authorized_keys</filename> file using the following command:
- </para>
- <screen>~]$ <command>chmod 644 ~/.ssh/authorized_keys</command></screen>
- </step>
- </procedure>
- <indexterm>
- <primary>RSA Version 1 keys</primary>
- <secondary>generating</secondary>
- </indexterm>
- <indexterm>
- <primary>OpenSSH</primary>
- <secondary>RSA Version 1 keys</secondary>
- <tertiary>generating</tertiary>
- </indexterm>
- <para>
- To generate an RSA key pair for version 1 of the SSH protocol, follow these steps:
- </para>
- <indexterm>
- <primary>OpenSSH</primary>
- <secondary>ssh-keygen</secondary>
- <tertiary>RSA Version 1</tertiary>
- </indexterm>
- <procedure>
- <step>
- <para>
- Generate an RSA key pair by typing the following at a shell prompt:
- </para>
- <screen>~]$ <command>ssh-keygen -t rsa1</command>
-Generating public/private rsa1 key pair.
-Enter file in which to save the key (/home/john/.ssh/identity):</screen>
- </step>
- <step>
- <para>
- Press <keycap>Enter</keycap> to confirm the default location (that is, <filename>~/.ssh/identity</filename>) for the newly created key.
- </para>
- </step>
- <step>
- <para>
- Enter a passphrase, and confirm it by entering it again when prompted to do so. For security reasons, avoid using the same password as you use to log into your account.
- </para>
- <para>
- After this, you will be presented with a message similar to this:
- </para>
- <screen>Your identification has been saved in /home/john/.ssh/identity.
-Your public key has been saved in /home/john/.ssh/identity.pub.
-The key fingerprint is:
-cb:f6:d5:cb:6e:5f:2b:28:ac:17:0c:e4:62:e4:6f:59 john(a)penguin.example.com
-The key's randomart image is:
-+--[RSA1 2048]----+
| |
-| . . |
-| o o |
-| + o E |
-| . o S |
-| = + . |
-| . = . o . .|
-| . = o o..o|
-| .o o o=o.|
+-----------------+</screen>
</step>
+ <step>
+ <para>
+ By default, the permissions of the <filename class="directory">~/.ssh/</filename> directory are set to <literal>rwx------</literal> or <literal>700</literal> expressed in octal notation. This is to ensure that only the <replaceable>USER</replaceable> can view the contents. If required, this can be confirmed with the following command:
+ </para>
+ <screen>~]$ <command>ls -ld ~/.ssh</command>
+ ~]$ ls -ld ~/.ssh/
+drwx------. 2 USER USER 54 Nov 25 16:56 /home/USER/.ssh/</screen>
+ </step>
<step>
<para>
- Change the permissions of the <filename class="directory">~/.ssh/</filename> directory:
- </para>
- <screen>~]$ <command>chmod 755 ~/.ssh</command></screen>
- </step>
- <step>
- <para>
- Copy the content of <filename>~/.ssh/identity.pub</filename> into the <filename>~/.ssh/authorized_keys</filename> on the machine to which you want to connect, appending it to its end if the file already exists.
+To copy the public key to a remote machine, issue a command in the following format:
+ <synopsis><command>ssh-copy-id <replaceable>USER@hostname</replaceable></command></synopsis>
+ This will copy all <filename>~/.ssh/id*.pub</filename> public keys. Alternatively, specify the public keys file name as follows:
+ <synopsis><command>ssh-copy-id -i <filename>~/.ssh/id_ecdsa.pub</filename> <replaceable>USER@hostname</replaceable></command></synopsis>
+ This will copy the content of <filename>~/.ssh/id_ecdsa.pub</filename> into the <filename>~/.ssh/authorized_keys</filename> on the machine to which you want to connect. If the file already exists, the keys are appended to its end.
</para>
</step>
- <step>
- <para>
- Change the permissions of the <filename>~/.ssh/authorized_keys</filename> file using the following command:
- </para>
- <screen>~]$ <command>chmod 644 ~/.ssh/authorized_keys</command></screen>
- </step>
- </procedure>
+ </procedure>
<para>
See <xref linkend="s3-ssh-configuration-keypairs-agent" /> for information on how to set up your system to remember the passphrase.
</para>
@@ -814,25 +758,10 @@ The key's randomart image is:
<title>Configuring ssh-agent</title>
<indexterm>
<primary>OpenSSH</primary>
- <secondary>
- <command>ssh-agent</command>
- </secondary>
- </indexterm>
- <indexterm>
- <primary>
- <command>ssh-agent</command>
- </primary>
+ <secondary><command>ssh-agent</command></secondary>
</indexterm>
<indexterm>
- <primary>OpenSSH</primary>
- <secondary>
- <command>ssh-add</command>
- </secondary>
- </indexterm>
- <indexterm>
- <primary>
- <command>ssh-add</command>
- </primary>
+ <primary><command>ssh-agent</command></primary>
</indexterm>
<para>
To store your passphrase so that you do not have to enter it each time you initiate a connection with a remote machine, you can use the <command>ssh-agent</command> authentication agent.
@@ -845,13 +774,11 @@ The key's randomart image is:
<procedure>
<step>
<para>
- Make sure you have the <package>openssh-askpass</package> package installed. If not, refer to <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
+ Make sure you have the <package>openssh-askpass</package> package installed. If not, see <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
</para>
</step>
<step>
- <para>
- Select <menuchoice><guimenu>System</guimenu><guisubmenu>Preferences</guisubmenu><guimenuitem>Startup Applications</guimenuitem></menuchoice> from the panel. The <application>Startup Applications Preferences</application> will be started, and the tab containing a list of available startup programs will be shown by default.
- </para>
+ <para>Press the <keycap>Super</keycap> key to enter the Activities Overview, type <command>Startup Applications</command> and then press <keycap>Enter</keycap>. The <application>Startup Applications Preferences</application> tool appears. The tab containing a list of available startup programs will be shown by default. The <keycap>Super</keycap> key appears in a variety of guises, depending on the keyboard and other hardware, but often as either the Windows or Command key, and typically to the left of the Spacebar.</para>
<figure id="fig-ssh-startup-applications">
<title>Startup Applications Preferences</title>
<mediaobject>
@@ -870,14 +797,10 @@ The key's randomart image is:
</para>
<indexterm>
<primary>OpenSSH</primary>
- <secondary>
- <command>ssh-add</command>
- </secondary>
+ <secondary><command>ssh-add</command></secondary>
</indexterm>
<indexterm>
- <primary>
- <command>ssh-add</command>
- </primary>
+ <primary><command>ssh-add</command></primary>
</indexterm>
<figure id="fig-ssh-startup-applications-add">
<title>Adding new application</title>
@@ -893,7 +816,7 @@ The key's randomart image is:
</step>
<step>
<para>
- Click <guibutton>Add</guibutton> and make sure the check box next to the newly added item is selected.
+ Click <guibutton>Add</guibutton> and make sure the checkbox next to the newly added item is selected.
</para>
<figure id="fig-ssh-startup-applications-check">
<title>Enabling the application</title>
@@ -928,8 +851,8 @@ The key's randomart image is:
-->
To save your passphrase for a certain shell prompt, use the following command:
</para>
- <screen>~]$ <command>ssh-add</command>
-Enter passphrase for /home/john/.ssh/id_rsa:</screen>
+ <screen>~]$ <command>ssh-add</command>
+Enter passphrase for /home/USER/.ssh/id_rsa:</screen>
<para>
Note that when you log out, your passphrase will be forgotten. You must execute the command each time you log in to a virtual console or a terminal window.
</para>
@@ -945,85 +868,98 @@ Enter passphrase for /home/john/.ssh/id_rsa:</screen>
<note>
<title>Make sure you have relevant packages installed</title>
<para>
- To connect to an OpenSSH server from a client machine, you must have the <package>openssh-clients</package> and <package>openssh</package> packages installed. See <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
-
+ To connect to an OpenSSH server from a client machine, you must have the <package>openssh-clients</package> package installed. See <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
</para>
</note>
<section id="s2-ssh-clients-ssh">
<title>Using the ssh Utility</title>
<indexterm>
- <primary>
- <command>ssh</command>
- </primary>
+ <primary><command>ssh</command></primary>
<see>OpenSSH</see>
</indexterm>
<indexterm>
<primary>OpenSSH</primary>
<secondary>client</secondary>
- <tertiary>
- <command>ssh</command>
- </tertiary>
+ <tertiary><command>ssh</command></tertiary>
</indexterm>
<para>
- <command>ssh</command> allows you to log in to a remote machine and execute commands there. It is a secure replacement for the <command>rlogin</command>, <command>rsh</command>, and <command>telnet</command> programs.
+ The <command>ssh</command> utility allows you to log in to a remote machine and execute commands there. It is a secure replacement for the <command>rlogin</command>, <command>rsh</command>, and <command>telnet</command> programs.
</para>
<para>
- Similarly to <command>telnet</command>, to log in to a remote machine named <systemitem class="domainname">penguin.example.com</systemitem>, type the following command at a shell prompt:
+ Similarly to the <command>telnet</command> command, log in to a remote machine by using the following command:
</para>
- <screen>~]$ <command>ssh penguin.example.com</command></screen>
+ <synopsis><command>ssh</command> <replaceable>hostname</replaceable></synopsis>
<para>
- This will log you in with the same username you are using on a local machine. If you want to specify a different one, use a command in the <command>ssh <replaceable>username</replaceable>@<replaceable>hostname</replaceable></command> form. For example, to log in as <systemitem class="username">john</systemitem>, type:
+ For example, to log in to a remote machine named <systemitem class="domainname">penguin.example.com</systemitem>, type the following at a shell prompt:
</para>
- <screen>~]$ <command>ssh john(a)penguin.example.com</command></screen>
+ <screen>~]$ <command>ssh penguin.example.com</command></screen>
+ <para>
+ This will log you in with the same user name you are using on the local machine. If you want to specify a different user name, use a command in the following form:
+ </para>
+ <synopsis><command>ssh</command> <replaceable>username</replaceable>@<replaceable>hostname</replaceable></synopsis>
+ <para>
+ For example, to log in to <systemitem class="domainname">penguin.example.com</systemitem> as <systemitem class="username">USER</systemitem>, type:
+ </para>
+ <screen>~]$ <command>ssh USER(a)penguin.example.com</command></screen>
<para>
The first time you initiate a connection, you will be presented with a message similar to this:
</para>
<screen>The authenticity of host 'penguin.example.com' can't be established.
-RSA key fingerprint is 94:68:3a:3a:bc:f3:9a:9b:01:5d:b3:07:38:e2:11:0c.
+ECDSA key fingerprint is 256 da:24:43:0b:2e:c1:3f:a1:84:13:92:01:52:b4:84:ff.
Are you sure you want to continue connecting (yes/no)?</screen>
+<para>
+ Users should always check if the fingerprint is correct before answering the question in this dialog. The user can ask the administrator of the server to confirm the key is correct. This should be done in a secure and previously agreed way. If the user has access to the server's host keys, the fingerprint can be checked by using the <command>ssh-keygen</command> command as follows:
+ <screen>~]# <command>ssh-keygen -l -f /etc/ssh/ssh_host_ecdsa_key.pub</command>
+256 da:24:43:0b:2e:c1:3f:a1:84:13:92:01:52:b4:84:ff (ECDSA)</screen>
+</para>
<para>
- Type <userinput>yes</userinput> to confirm. You will see a notice that the server has been added to the list of known hosts, and a prompt asking for your password:
+ Type <userinput>yes</userinput> to accept the key and confirm the connection. You will see a notice that the server has been added to the list of known hosts, and a prompt asking for your password:
</para>
- <screen>Warning: Permanently added 'penguin.example.com' (RSA) to the list of known hosts.
-john(a)penguin.example.com's password:</screen>
+ <screen>Warning: Permanently added 'penguin.example.com' (ECDSA) to the list of known hosts.
+USER(a)penguin.example.com's password:</screen>
<important>
<title>Updating the host key of an SSH server</title>
<para>
- If the SSH server's host key changes, the client notifies the user that the connection cannot proceed until the server's host key is deleted from the <filename>~/.ssh/known_hosts</filename> file. To do so, open the file in a text editor, and remove a line containing the remote machine name at the beginning. Before doing this, however, contact the system administrator of the SSH server to verify the server is not compromised.
+ If the SSH server's host key changes, the client notifies the user that the connection cannot proceed until the server's host key is deleted from the <filename>~/.ssh/known_hosts</filename> file. Before doing this, however, contact the system administrator of the SSH server to verify the server is not compromised.
+ </para>
+ <para>
+ To remove a key from the <filename>~/.ssh/known_hosts</filename> file, issue a command as follows:
+ <screen>~]# <command>ssh-keygen</command><option>-R</option><replaceable>penguin.example.com</replaceable>
+# Host penguin.example.com found: line 15 type ECDSA
+/home/USER/.ssh/known_hosts updated.
+Original contents retained as /home/USER/.ssh/known_hosts.old</screen>
</para>
</important>
<para>
After entering the password, you will be provided with a shell prompt for the remote machine.
</para>
<para>
- Alternatively, the <command>ssh</command> program can be used to execute a command on the remote machine without logging in to a shell prompt. The syntax for that is <command>ssh [<replaceable>username</replaceable>@]<replaceable>hostname</replaceable> <replaceable>command</replaceable></command>. For example, if you want to execute the <command>whoami</command> command on <systemitem class="domainname">penguin.example.com</systemitem>, type:
+ Alternatively, the <command>ssh</command> program can be used to execute a command on the remote machine without logging in to a shell prompt:
+ </para>
+ <synopsis><command>ssh</command> <optional><replaceable>username</replaceable>@</optional><replaceable>hostname</replaceable> <replaceable>command</replaceable></synopsis>
+ <para>
+ For example, the <filename>/etc/redhat-release</filename> file provides information about the &MAJOROS; version. To view the contents of this file on <systemitem class="domainname">penguin.example.com</systemitem>, type:
</para>
- <screen>~]$ <command>ssh john(a)penguin.example.com whoami</command>
-john(a)penguin.example.com's password:
-john</screen>
+ <screen>~]$ <command>ssh USER(a)penguin.example.com cat /etc/redhat-release</command>
+USER(a)penguin.example.com's password:
+Fedora release 20 (Heisenbug)</screen>
<para>
- After you enter the correct password, the username will be displayed, and you will return to your local shell prompt.
+ After you enter the correct password, the user name will be displayed, and you will return to your local shell prompt.
</para>
</section>
<section id="s2-ssh-clients-scp">
<title>Using the <command>scp</command> Utility</title>
<indexterm>
- <primary>
- <command>scp</command>
- </primary>
+ <primary><command>scp</command></primary>
<see>OpenSSH</see>
</indexterm>
<indexterm>
<primary>OpenSSH</primary>
<secondary>client</secondary>
- <tertiary>
- <command>scp</command>
- </tertiary>
+ <tertiary><command>scp</command></tertiary>
</indexterm>
<indexterm>
- <primary>
- <command>rcp</command>
- </primary>
+ <primary><command>rcp</command></primary>
</indexterm>
<para>
<command>scp</command> can be used to transfer files between machines over a secure, encrypted connection. In its design, it is very similar to <command>rcp</command>.
@@ -1035,16 +971,16 @@ john</screen>
<para>
For example, if you want to transfer <filename>taglist.vim</filename> to a remote machine named <systemitem class="domainname">penguin.example.com</systemitem>, type the following at a shell prompt:
</para>
- <screen>~]$ <command>scp taglist.vim john@penguin.example.com:.vim/plugin/taglist.vim</command>
-john(a)penguin.example.com's password:
+ <screen>~]$ <command>scp taglist.vim USER@penguin.example.com:.vim/plugin/taglist.vim</command>
+USER(a)penguin.example.com's password:
taglist.vim 100% 144KB 144.5KB/s 00:00</screen>
<para>
Multiple files can be specified at once. To transfer the contents of <filename>.vim/plugin/</filename> to the same directory on the remote machine <systemitem class="domainname">penguin.example.com</systemitem>, type the following command:
</para>
- <screen>~]$ <command>scp .vim/plugin/* john@penguin.example.com:.vim/plugin/</command>
-john(a)penguin.example.com's password:
-closetag.vim 100% 13KB 12.6KB/s 00:00
-snippetsEmu.vim 100% 33KB 33.1KB/s 00:00
+ <screen>~]$ <command>scp .vim/plugin/* USER@penguin.example.com:.vim/plugin/</command>
+USER(a)penguin.example.com's password:
+closetag.vim 100% 13KB 12.6KB/s 00:00
+snippetsEmu.vim 100% 33KB 33.1KB/s 00:00
taglist.vim 100% 144KB 144.5KB/s 00:00</screen>
<para>
To transfer a remote file to the local system, use the following syntax:
@@ -1053,24 +989,20 @@ taglist.vim 100% 144KB 144.5KB/s 00:00</scr
<para>
For instance, to download the <filename>.vimrc</filename> configuration file from the remote machine, type:
</para>
- <screen>~]$ <command>scp john@penguin.example.com:.vimrc .vimrc</command>
-john(a)penguin.example.com's password:
+ <screen>~]$ <command>scp USER@penguin.example.com:.vimrc .vimrc</command>
+USER(a)penguin.example.com's password:
.vimrc 100% 2233 2.2KB/s 00:00</screen>
</section>
<section id="s2-ssh-clients-sftp">
<title>Using the <command>sftp</command> Utility</title>
<indexterm>
- <primary>
- <command>sftp</command>
- </primary>
+ <primary><command>sftp</command></primary>
<see>OpenSSH</see>
</indexterm>
<indexterm>
<primary>OpenSSH</primary>
<secondary>client</secondary>
- <tertiary>
- <command>sftp</command>
- </tertiary>
+ <tertiary><command>sftp</command></tertiary>
</indexterm>
<para>
The <command>sftp</command> utility can be used to open a secure, interactive FTP session. In its design, it is similar to <command>ftp</command> except that it uses a secure, encrypted connection.
@@ -1080,10 +1012,10 @@ john(a)penguin.example.com's password:
</para>
<screen><command>sftp <replaceable>username</replaceable>@<replaceable>hostname</replaceable></command></screen>
<para>
- For example, to log in to a remote machine named <systemitem class="domainname">penguin.example.com</systemitem> with <systemitem class="username">john</systemitem> as a username, type:
+ For example, to log in to a remote machine named <systemitem class="domainname">penguin.example.com</systemitem> with <systemitem class="username">USER</systemitem> as a user name, type:
</para>
- <screen>~]$ <command>sftp john(a)penguin.example.com</command>
-john(a)penguin.example.com's password:
+ <screen>~]$ <command>sftp USER(a)penguin.example.com</command>
+USER(a)penguin.example.com's password:
Connected to penguin.example.com.
sftp></screen>
<para>
@@ -1153,7 +1085,7 @@ sftp></screen>
</tgroup>
</table>
<para>
- For a complete list of available commands, refer to the <command>sftp</command> man page.
+ For a complete list of available commands, see the <filename>sftp</filename>(1) manual page.
</para>
</section>
</section>
@@ -1173,19 +1105,19 @@ sftp></screen>
</para>
<screen><command>ssh -Y <replaceable>username</replaceable>@<replaceable>hostname</replaceable></command></screen>
<para>
- For example, to log in to a remote machine named <systemitem class="domainname">penguin.example.com</systemitem> with <systemitem class="username">john</systemitem> as a username, type:
+ For example, to log in to a remote machine named <systemitem class="domainname">penguin.example.com</systemitem> with <systemitem class="username">USER</systemitem> as a user name, type:
</para>
- <screen>~]$ <command>ssh -Y john(a)penguin.example.com</command>
-john(a)penguin.example.com's password:</screen>
+ <screen>~]$ <command>ssh -Y USER(a)penguin.example.com</command>
+USER(a)penguin.example.com's password:</screen>
<para>
When an X program is run from the secure shell prompt, the SSH client and server create a new secure channel, and the X program data is sent over that channel to the client machine transparently.
</para>
<para>
- X11 forwarding can be very useful. For example, X11 forwarding can be used to create a secure, interactive session of the <application>Printer Configuration</application> utility. To do this, connect to the server using <application>ssh</application> and type:
+ X11 forwarding can be very useful. For example, X11 forwarding can be used to create a secure, interactive session of the <application>Print Settings</application> utility. To do this, connect to the server using <application>ssh</application> and type:
</para>
- <screen>~]$ <command>system-config-printer &</command></screen>
+ <screen>~]$ <command>system-config-printer &</command></screen>
<para>
- The <application>Printer Configuration Tool</application> will appear, allowing the remote user to safely configure printing on the remote system.
+ The <application>Print Settings</application> tool will appear, allowing the remote user to safely configure printing on the remote system.
</para>
</section>
<section id="s2-ssh-beyondshell-tcpip">
@@ -1203,7 +1135,7 @@ john(a)penguin.example.com's password:</screen>
<note>
<title>Using reserved port numbers</title>
<para>
- Setting up port forwarding to listen on ports below 1024 requires root level access.
+ Setting up port forwarding to listen on ports below 1024 requires <systemitem class="username">root</systemitem> level access.
</para>
</note>
<para>
@@ -1213,14 +1145,14 @@ john(a)penguin.example.com's password:</screen>
<para>
For example, to check email on a server called <systemitem class="domainname">mail.example.com</systemitem> using <systemitem class="protocol">POP3</systemitem> through an encrypted connection, use the following command:
</para>
- <screen>~]$ <command>ssh -L 1100:mail.example.com:110 mail.example.com</command></screen>
+ <screen>~]$ <command>ssh -L 1100:mail.example.com:110 mail.example.com</command></screen>
<para>
Once the port forwarding channel is in place between the client machine and the mail server, direct a POP3 mail client to use port <literal>1100</literal> on the <systemitem class="domainname">localhost</systemitem> to check for new email. Any requests sent to port <literal>1100</literal> on the client system will be directed securely to the <systemitem class="domainname">mail.example.com</systemitem> server.
</para>
<para>
If <systemitem class="domainname">mail.example.com</systemitem> is not running an SSH server, but another machine on the same network is, SSH can still be used to secure part of the connection. However, a slightly different command is necessary:
</para>
- <screen>~]$ <command>ssh -L 1100:mail.example.com:110 other.example.com</command></screen>
+ <screen>~]$ <command>ssh -L 1100:mail.example.com:110 other.example.com</command></screen>
<para>
In this example, POP3 requests from port <literal>1100</literal> on the client machine are forwarded through the SSH connection on port <literal>22</literal> to the SSH server, <systemitem class="domainname">other.example.com</systemitem>. Then, <systemitem class="domainname">other.example.com</systemitem> connects to port <literal>110</literal> on <systemitem class="domainname">mail.example.com</systemitem> to check for new email. Note that when using this technique, only the connection between the client system and <systemitem class="domainname">other.example.com</systemitem> SSH server is secure.
</para>
@@ -1249,97 +1181,59 @@ john(a)penguin.example.com's password:</screen>
<secondary>additional resources</secondary>
</indexterm>
<para>
- The OpenSSH and OpenSSL projects are in constant development, and the most up-to-date information for them is available from their websites. The man pages for OpenSSH and OpenSSL tools are also good sources of detailed information.
+ For more information on how to configure or connect to an OpenSSH server on Fedora, see the resources listed below.
</para>
- <section id="s2-openssh-installed-docs">
- <title>Installed Documentation</title>
- <variablelist>
- <varlistentry>
- <term><command>man ssh</command></term>
- <listitem>
- <para>
- The manual page for <application>ssh</application> containing the full documentation on its usage.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>man scp</command></term>
- <listitem>
- <para>
- The manual page for <application>scp</application> containing the full documentation on its usage.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>man sftp</command></term>
- <listitem>
- <para>
- The manual page for <application>sftp</application> containing the full documentation on its usage.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>man sshd</command></term>
- <listitem>
- <para>
- The manual page for <application>sshd</application> containing the full documentation on its usage.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>man ssh-keygen</command></term>
- <listitem>
- <para>
- The manual page for <application>ssh-keygen</application> containing the full documentation on its usage.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>man ssh_config</command></term>
- <listitem>
- <para>
- The manual page with full description of available SSH client configuration options.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><command>man sshd_config</command></term>
- <listitem>
- <para>
- The manual page with full description of available SSH daemon configuration options.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
- <section id="s2-openssh-useful-websites">
- <title>Useful Websites</title>
- <variablelist>
- <varlistentry>
- <term><ulink url="http://www.openssh.com/" /></term>
- <listitem>
- <para>
- The OpenSSH home page containing further documentation, frequently asked questions, links to the mailing lists, bug reports, and other useful resources.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink url="http://www.openssl.org/" /></term>
- <listitem>
- <para>
- The OpenSSL home page containing further documentation, frequently asked questions, links to the mailing lists, and other useful resources.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink url="http://www.freesshd.com/" /></term>
- <listitem>
- <para>
- Another implementation of an SSH server.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
+ <bridgehead id="bh-OpenSSH-Resources-Installed">Installed Documentation</bridgehead>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <systemitem>sshd</systemitem>(8) — The manual page for the <systemitem class="service">sshd</systemitem> daemon documents available command line options and provides a complete list of supported configuration files and directories.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <systemitem>ssh</systemitem>(1) — The manual page for the <command>ssh</command> client application provides a complete list of available command line options and supported configuration files and directories.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <systemitem>scp</systemitem>(1) — The manual page for the <command>scp</command> utility provides a more detailed description of this utility and its usage.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <systemitem>sftp</systemitem>(1) — The manual page for the <command>sftp</command> utility.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <systemitem>ssh-keygen</systemitem>(1) — The manual page for the <command>ssh-keygen</command> utility documents in detail how to use it to generate, manage, and convert authentication keys used by <command>ssh</command>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <systemitem>ssh_config</systemitem>(5) — The manual page named <systemitem>ssh_config</systemitem> documents available SSH client configuration options.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <systemitem>sshd_config</systemitem>(5) — The manual page named <systemitem>sshd_config</systemitem> provides a full description of available SSH daemon configuration options.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <bridgehead id="brid-OpenSSH-Resources-Online">Online Documentation</bridgehead>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://www.openssh.com/">OpenSSH Home Page</ulink> — The OpenSSH home page containing further documentation, frequently asked questions, links to the mailing lists, bug reports, and other useful resources.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://www.openssl.org/">OpenSSL Home Page</ulink> — The OpenSSL home page containing further documentation, frequently asked questions, links to the mailing lists, and other useful resources.
+ </para>
+ </listitem>
+ </itemizedlist>
+
</section>
</chapter>
9 years, 3 months
[install-guide] (9 commits) ...Merge branch 'f21-branch'
by pbokoc
Summary of changes:
43428ca... BZURLFTW (*)
1bbeeb8... Say 'reinstall' instead of 'upgrade' when referring to anac (*)
b77bafd... Downloading (*)
b508255... verification for linux and osx users too (*)
931cb85... dd is not complex (*)
512b964... We should be able to use nbsp in entities with the anaconda (*)
4b4bced... Downloading (*)
546bab2... verification for linux and osx users too (*)
889f7f4... Merge branch 'f21-branch' (*)
(*) This commit already existed in another branch; no separate mail sent
9 years, 3 months
[install-guide/f21-branch] (9 commits) ...Merge branch 'f21-branch'
by pbokoc
Summary of changes:
b6d23d0... We should be able to use nbsp in entities with the anaconda (*)
a392a47... BZURLFTW (*)
4f4f60b... Say 'reinstall' instead of 'upgrade' when referring to anac (*)
4f4ba12... Downloading (*)
e16ccac... verification for linux and osx users too (*)
8265b06... dd is not complex (*)
ba36890... Downloading (*)
fab12aa... verification for linux and osx users too (*)
889f7f4... Merge branch 'f21-branch'
(*) This commit already existed in another branch; no separate mail sent
9 years, 3 months
[install-guide] verification for linux and osx users too
by pbokoc
commit fab12aa8c10f466090852e639b030df4d1fd18d0
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Wed Nov 19 21:09:22 2014 -0700
verification for linux and osx users too
en-US/Preparing_for_Installation.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index 6d7f6f1..68d9f4b 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -56,7 +56,7 @@
<section id="sect-preparing-obtaining-images">
<title>Downloading Boot and Installation Images</title>
<para>
- The Fedora Project offers different flavors for tailored for some specific use cases. Choose the Fedora flavor best for you, or you can build your own using a <xref linkend="sect-kickstart-file-create">kickstart</xref> file or by customizing after the installation.
+ The Fedora Project offers different flavors for tailored for some specific use cases. Choose the Fedora flavor best for you, or you can build your own by customizing after the installation, or by using a kickstart file as described in <xref linkend="sect-kickstart-file-create" />.
</para>
<para>
Learn more about Fedora Workstation, Fedora Cloud, and Fedora Server at <ulink url="http://getfedora.org" />.
9 years, 3 months
[install-guide] Downloading
by pbokoc
commit ba368908e1fc5ef67353ad26174d1a39f6e3af98
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Wed Nov 19 20:27:39 2014 -0700
Downloading
The 'get' sites do a good job of walking users through the process of
choosing a flavor or spin and clicking on the download link, so let's
just refer to them.
en-US/Preparing_for_Installation.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index 68d9f4b..6d7f6f1 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -56,7 +56,7 @@
<section id="sect-preparing-obtaining-images">
<title>Downloading Boot and Installation Images</title>
<para>
- The Fedora Project offers different flavors for tailored for some specific use cases. Choose the Fedora flavor best for you, or you can build your own by customizing after the installation, or by using a kickstart file as described in <xref linkend="sect-kickstart-file-create" />.
+ The Fedora Project offers different flavors for tailored for some specific use cases. Choose the Fedora flavor best for you, or you can build your own using a <xref linkend="sect-kickstart-file-create">kickstart</xref> file or by customizing after the installation.
</para>
<para>
Learn more about Fedora Workstation, Fedora Cloud, and Fedora Server at <ulink url="http://getfedora.org" />.
9 years, 3 months
[install-guide] dd is not complex
by pbokoc
commit 8265b066b9da756bceae9960a0ab3cf4a74d8993
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Wed Nov 19 22:42:26 2014 -0700
dd is not complex
en-US/Preparing_for_Installation.xml | 43 +++++++++++++++++++++++++++++----
1 files changed, 37 insertions(+), 6 deletions(-)
---
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index 0a5c095..68d9f4b 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -214,12 +214,7 @@ Mode LastWriteTime Length Name
</warning>
<procedure>
<title>Creating USB Media on Windows</title>
- <step>
- <para>
- Download the Fedora image of your choice from <ulink url="https://fedoraproject.org/get-fedora" /> and the corresponding checksum file from <ulink url="https://fedoraproject.org/verify " />.
- </para>
- </step>
- <step>
+ <step>
<para>
Download and run the <ulink url="https://github.com/downloads/openSUSE/kiwi/ImageWriter.exe"><application>SUSE Studio ImageWriter</application></ulink> or <ulink url="http://www.netbsd.org/~martin/rawrite32/"><application>Rawrite32</application></ulink>.
</para>
@@ -267,6 +262,42 @@ Mode LastWriteTime Length Name
</step>
</procedure>
+ <procedure>
+ <title>Creating USB Media on the Linux command line</title>
+ <step>
+ <para>
+ Open a terminal window and insert the usb drive.
+ </para>
+ </step>
+ <step>
+ <para>
+ Find the <systemitem class="resource">device node</systemitem> assigned to the drive. In the example below, the drive is given <literal>sdd</literal>.
+ </para>
+ <programlisting>
+<prompt>$ </prompt><command>dmesg|tail</command>
+[288954.686557] usb 2-1.8: New USB device strings: Mfr=0, Product=1, SerialNumber=2
+[288954.686559] usb 2-1.8: Product: USB Storage
+[288954.686562] usb 2-1.8: SerialNumber: 000000009225
+[288954.712590] usb-storage 2-1.8:1.0: USB Mass Storage device detected
+[288954.712687] scsi host6: usb-storage 2-1.8:1.0
+[288954.712809] usbcore: registered new interface driver usb-storage
+[288954.716682] usbcore: registered new interface driver uas
+[288955.717140] scsi 6:0:0:0: Direct-Access Generic STORAGE DEVICE 9228 PQ: 0 ANSI: 0
+[288955.717745] sd 6:0:0:0: Attached scsi generic sg4 type 0
+[288961.876382] sd 6:0:0:0: <literal>[sdd]</literal> Attached SCSI removable disk
+ </programlisting>
+ </step>
+ <step>
+ <para>
+ Use the <command>dd</command> utility to write the image. <emphasis>Make sure you have the right drive!</emphasis>
+ </para>
+ <screen>
+ <prompt># </prompt>dd if=<replaceable>/path/to/Fedora-Live-Security-x86_64-21.iso</replaceable> of=<replaceable>/dev/sdd</replaceable>
+ </screen>
+ </step>
+ </procedure>
+
+
9 years, 3 months
[install-guide] verification for linux and osx users too
by pbokoc
commit e16ccacacbd8b96a136f9a1a2557aef2fd03437e
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Wed Nov 19 21:09:22 2014 -0700
verification for linux and osx users too
en-US/Preparing_for_Installation.xml | 39 +++++++++++++++++++++++++++++++++-
1 files changed, 38 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index ad7673c..0a5c095 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -56,7 +56,7 @@
<section id="sect-preparing-obtaining-images">
<title>Downloading Boot and Installation Images</title>
<para>
- The Fedora Project offers different flavors for tailored for some specific use cases. Choose the Fedora flavor best for you, or you can build your own using a <xref linkend="sect-kickstart-file-create">kickstart</xref> file or by customizing after the installation.
+ The Fedora Project offers different flavors for tailored for some specific use cases. Choose the Fedora flavor best for you, or you can build your own by customizing after the installation, or by using a kickstart file as described in <xref linkend="sect-kickstart-file-create" />.
</para>
<para>
Learn more about Fedora Workstation, Fedora Cloud, and Fedora Server at <ulink url="http://getfedora.org" />.
@@ -135,6 +135,43 @@ Mode LastWriteTime Length Name
</programlisting>
</step>
</procedure>
+
+ <procedure>
+ <title>Verifying checksums on Linux and OSX systems</title>
+ <step>
+ <para>
+ Download the Fedora image of your choice from <ulink url="https://fedoraproject.org/get-fedora" /> and the corresponding checksum file from <ulink url="https://fedoraproject.org/verify " />
+ </para>
+ </step>
+ <step>
+ <para>
+ Open a terminal window, and navigate to the directory with the downloaded files.
+ </para>
+ <screen>
+<prompt>$ </prompt><command>cd ~/Downloads</command>
+ </screen>
+ </step>
+ <step>
+ <para>
+ Use the appropriate utility to verify the image checksum.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>For Linux:</para>
+ <screen>
+<prompt>$ </prompt><command>sha256sum -c *CHECKSUM</command>
+ </screen>
+ </listitem>
+ <listitem>
+ <para>For OSX:</para>
+ <screen>
+<prompt>$ </prompt><command>shasum -a 256 -c *CHECKSUM</command>
+ </screen>
+ </listitem>
+ </itemizedlist>
+ </step>
+ </procedure>
+
9 years, 3 months