docs-commits December 2014

docs-commits@lists.fedoraproject.org

10 participants
199 discussions

[install-guide/f21-branch] Removing most TODOs from Kickstart Syntax Reference
by pbokoc 07 Dec '14

07 Dec '14

commit 479a49cbc807a6f64ccf426ae72fee915c77c00d Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Sun Dec 7 20:10:06 2014 +0100 Removing most TODOs from Kickstart Syntax Reference en-US/Kickstart_Syntax_Reference.xml | 49 +++++++++++----------------------- 1 files changed, 16 insertions(+), 33 deletions(-) --- diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml index f50060b..3b6a943 100644 --- a/en-US/Kickstart_Syntax_Reference.xml +++ b/en-US/Kickstart_Syntax_Reference.xml @@ -232,7 +232,7 @@ <term><command>nfs</command></term> <listitem> <para> - Install from an <systemitem class="protocol">NFS</systemitem> server specified. <remark>TODO: link to the PXE chapter's section on preparing install source on nfs</remark> + Install from an <systemitem class="protocol">NFS</systemitem> server specified. The NFS server must be exporting the full installation ISO image (such as the &PRODUCT; Server DVD) or its extracted contents. </para> <programlisting> <command>install</command> @@ -472,7 +472,7 @@ </listitem> </itemizedlist> <para> - For a description of the available partition schemes, see <remark>TODO: xref to a list of available auto partitioning schemes</remark> + The created partitioning scheme will follow the recommended scheme described at <xref linkend="sect-installation-gui-manual-partitioning-recommended" />. </para> </listitem> </varlistentry> @@ -537,12 +537,12 @@ </programlisting> <important> <para> - You should always use a password to protect your boot loader. An unprotected boot loader can allow a potential attacker to modify the system's boot options and gain unauthorized access to the system. + You should always use a password to protect your boot loader. An unprotected boot loader can allow a potential attacker to modify the system's boot options and gain unauthorized access to the system. </para> </important> <important> <para> - Some systems require a special partition for installing the boot loader. The type and size of this partition depends on whether the disk you are installing the boot loader to uses the <firstterm>Master Boot Record</firstterm> (MBR) or a <firstterm>GUID Partition Table</firstterm> (GPT) schema. For more information, see <remark>TODO: link to a section that deals with boot loaders and EFI/BIOSBoot</remark> + Some systems require a special partition for installing the boot loader. The type and size of this partition depends on whether the disk you are installing the boot loader to uses the <firstterm>Master Boot Record</firstterm> (MBR) or a <firstterm>GUID Partition Table</firstterm> (GPT) schema. For more information, see <xref linkend="sect-installation-gui-storage-partitioning-bootloader" />. </para> </important> <variablelist> @@ -1115,7 +1115,7 @@ The size assigned will be equivalent to the swap space assigned by <option>--recommended</option> plus the amount of RAM on your system. </para> <para> - For the swap sizes assigned by these commands, see <remark>todo: xref to a section about swap sizes</remark> + For the swap sizes assigned by these commands, see the section describing swap in <xref linkend="sect-installation-gui-manual-partitioning-recommended" />. </para> </listitem> </varlistentry> @@ -1150,7 +1150,7 @@ <term><option>--fstype=</option></term> <listitem> <para> - Sets the file system type for the logical volume. Valid values are <literal>xfs</literal>, <literal>ext2</literal>, <literal>ext3</literal>, <literal>ext4</literal>, <literal>swap</literal>, and <literal>vfat</literal>. For information about file system types, see <remark>TODO: xref to info about fs types</remark> + Sets the file system type for the logical volume. Valid values are <literal>xfs</literal>, <literal>ext2</literal>, <literal>ext3</literal>, <literal>ext4</literal>, <literal>swap</literal>, and <literal>vfat</literal>. See <xref linkend="sect-installation-gui-manual-partitioning-filesystems" /> for information about available file systems. </para> </listitem> </varlistentry> @@ -1214,7 +1214,7 @@ <term><option>--recommended</option></term> <listitem> <para> - Use this option when creating a <systemitem>swap</systemitem> logical volume to determine the size of this volume automatically, based on your system's hardware. For details about the recommended scheme, see <remark>TODO: xref to section with partitioning recommendations</remark> + Use this option when creating a <systemitem>swap</systemitem> logical volume to determine the size of this volume automatically, based on your system's hardware. For details about the recommended scheme, see <xref linkend="sect-installation-gui-manual-partitioning-recommended" />. </para> </listitem> </varlistentry> @@ -1379,7 +1379,7 @@ The size assigned will be equivalent to the swap space assigned by <option>--recommended</option> plus the amount of RAM on your system. </para> <para> - For the swap sizes assigned by these commands, see <remark>todo: xref to a section about swap sizes</remark> + For the swap sizes assigned by these commands, see the section describing swap in <xref linkend="sect-installation-gui-manual-partitioning-recommended" />. </para> </listitem> </varlistentry> @@ -1426,7 +1426,7 @@ </para> <important> <para> - If the <option>--size</option> value is too small, the installation will fail. Set the <option>--size</option> value as the minimum amount of space you require. For size recommendations, see <remark>TODO: xref to recommended partitioning scheme</remark>. + If the <option>--size</option> value is too small, the installation will fail. Set the <option>--size</option> value as the minimum amount of space you require. For size recommendations, see <xref linkend="sect-installation-gui-manual-partitioning-recommended" />. </para> </important> </listitem> @@ -1536,7 +1536,7 @@ <term><option>--fstype=</option></term> <listitem> <para> - Sets the file system type for the partition. Valid values are <literal>xfs</literal>, <literal>ext2</literal>, <literal>ext3</literal>, <literal>ext4</literal>, <literal>swap</literal>, <literal>vfat</literal>, <literal>efi</literal> and <literal>biosboot</literal>. For information about supported file systems, see <remark>TODO: xref to something about supported fs types</remark> + Sets the file system type for the partition. Valid values are <literal>xfs</literal>, <literal>ext2</literal>, <literal>ext3</literal>, <literal>ext4</literal>, <literal>swap</literal>, <literal>vfat</literal>, <literal>efi</literal> and <literal>biosboot</literal>. For information about supported file systems, see <xref linkend="sect-installation-gui-manual-partitioning-filesystems" />. </para> </listitem> </varlistentry> @@ -1563,7 +1563,7 @@ <term><option>--recommended</option></term> <listitem> <para> - Determine the size of the partition automatically. For details about the recommended scheme, see <remark>TODO: xref to something about recommended partitioning scheme</remark> + Determine the size of the partition automatically. For details about the recommended scheme, see <xref linkend="sect-installation-gui-manual-partitioning-recommended" />. </para> </listitem> </varlistentry> @@ -1642,7 +1642,7 @@ <term><option>--level=</option></term> <listitem> <para> - RAID level to use (<literal>0</literal>, <literal>1</literal>, <literal>4</literal>, <literal>5</literal>, <literal>6</literal>, or <literal>10</literal>). <remark>TODO: xref to the section that describes raid levels</remark> + RAID level to use (<literal>0</literal>, <literal>1</literal>, <literal>4</literal>, <literal>5</literal>, <literal>6</literal>, or <literal>10</literal>). See <xref linkend="sect-installation-gui-manual-partitioning-filesystems" /> for information about various RAID types and their requirements. </para> </listitem> </varlistentry> @@ -1674,7 +1674,7 @@ <term><option>--fstype=</option></term> <listitem> <para> - Sets the file system type for the partition. Valid values are <literal>xfs</literal>, <literal>ext2</literal>, <literal>ext3</literal>, <literal>ext4</literal>, <literal>swap</literal>, <literal>vfat</literal>, <literal>efi</literal> and <literal>biosboot</literal>. For information about supported file systems, see <remark>TODO: xref to something about supported fs types</remark> + Sets the file system type for the partition. Valid values are <literal>xfs</literal>, <literal>ext2</literal>, <literal>ext3</literal>, <literal>ext4</literal>, <literal>swap</literal>, <literal>vfat</literal>, <literal>efi</literal> and <literal>biosboot</literal>. For information about supported file systems, see <xref linkend="sect-installation-gui-manual-partitioning-filesystems" />. </para> </listitem> </varlistentry> @@ -1920,7 +1920,7 @@ <section id="sect-kickstart-commands-firewall"> <title>firewall (optional) - Configure Firewall</title> <para> - Specify the firewall configuration for the installed system. <remark>TODO: link to the Firewall guide once we have one</remark> + Specify the firewall configuration for the installed system. </para> <programlisting> <command>firewall --enabled | --disabled <replaceable>device</replaceable> [--trust= | --ssh | --smtp | --http | --ftp | --port= | --service=]</command> @@ -2882,9 +2882,9 @@ </section> <section id="sect-kickstart-commands-selinux"> - <title>selinux (optional) - Configure SELinux</title> + <title>selinux (optional) - Configu re SELinux</title> <para> - Sets the state of SELinux on the installed system. The default policy is <systemitem>enforcing</systemitem>. For more information regarding SELinux in &PRODUCT;, see <remark>TODO: link to wherever we document SELinux now</remark> + Sets the state of SELinux on the installed system. The default policy is <systemitem>enforcing</systemitem>. For more information regarding SELinux in &PRODUCT;, see the <citetitle>&PRODUCT; SELinux User's and Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. </para> <programlisting> <command>selinux [--disabled|--enforcing|--permissive]</command> @@ -3256,23 +3256,6 @@ This section contains commands which control the system's behavior immediately after the installation finishes. </para> - <section id="sect-kickstart-commands-eula"> - <title>eula (optional) - Accept the License Agreement</title> - <para> - Use this option to accept the <firstterm>End User License Agreement</firstterm> (EULA) without user interaction. Specifying this option prevents <application>Initial Setup</application> from prompting you to accept the license agreement after you finish the installation and reboot the system for the first time. See <xref linkend="sect-initial-setup" /> for more information. - </para> - <variablelist> - <varlistentry> - <term><option>--agreed</option></term> - <listitem> - <para> - Accept the EULA. This option must always be used, otherwise the <command>eula</command> command is meaningless. <remark>TODO: Does this even make sense on Fedora? Does initial-setup have an EULA in it?</remark> - </para> - </listitem> - </varlistentry> - </variablelist> - </section> - <section id="sect-kickstart-commands-firstboot"> <title>firstboot (optional) - Enable or Disable Initial Setup</title> <para>

1 0

[release-notes] Fixed typos reported in tx
by Zach Oglesby 07 Dec '14

07 Dec '14

commit 399b381cf10cb8d5edea78b03f34dbe1dd5debdc Author: Zach Oglesby <zach(a)oglesby.co> Date: Sun Dec 7 07:48:48 2014 -0500 Fixed typos reported in tx en-US/Section-Products.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/Section-Products.xml b/en-US/Section-Products.xml index 93f538c..abb626e 100644 --- a/en-US/Section-Products.xml +++ b/en-US/Section-Products.xml @@ -36,7 +36,7 @@ The named Fedora flavors are identified in part by a set of packages with configuration details and dependencies specific to that flavor. For example, the presence of <package>fedora-release-server</package> identifies a system as Fedora Server, and ensures that core features like <application>Cockpit</application> are present. </para> <para> - Update or installation operations may involve the <package>fedora-release</package> packages, sometimes inadvertently due to the way depenencies are resolved. Environment groups are most succeptible to related conflicts, such as installing extra desktops on Fedora Workstation. + Update or installation operations may involve the <package>fedora-release</package> packages, sometimes inadvertently due to the way dependencies are resolved. Environment groups are most susceptible to related conflicts, such as installing extra desktops on Fedora Workstation. </para> <para> If you encounter package conflicts, add <command>--exclude fedora-release\*</command> to your yum or dnf command. The <ulink url="https://fedoraproject.org/wiki/Common_F21_bugs#Installation_of_.27environme…">F21 Common Bugs</ulink> page describes this in detail.

1 0

[install-guide/f21-branch] there is no boot button on the device dialog when initiated from manual partitioning.
by Pete Travis 06 Dec '14

06 Dec '14

commit 480a6d23a793065d0e6e77a256c306ca0f24f086 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Sat Dec 6 15:34:04 2014 -0700 there is no boot button on the device dialog when initiated from manual partitioning. en-US/StorageSpoke_BootLoader.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/StorageSpoke_BootLoader.xml b/en-US/StorageSpoke_BootLoader.xml index be8eefe..fef792c 100644 --- a/en-US/StorageSpoke_BootLoader.xml +++ b/en-US/StorageSpoke_BootLoader.xml @@ -17,7 +17,7 @@ If you have other operating systems already installed, the &PRODUCT; installer will attempt to automatically detect and configure the boot loader to start them. You can manually configure any additional operating systems after you finish the installation, if they are not detected properly. For instructions on editing <application>GRUB2</application> configuration, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" /> </para> <para> - If you are installing Fedora system with more than one disk, you may want to manually specify where the bootloader should be installed. 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. The bootloader will be installed on the device of your choice, or on a UEFI system, the <systemitem class="resource" >EFI system partition</systemitem> will be created on that device during guided partitioning. + If you are installing Fedora system with more than one disk, you may want to manually specify where the bootloader should be installed. 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. The bootloader will be installed on the device of your choice, or on a UEFI system, the <systemitem class="resource" >EFI system partition</systemitem> will be created on that device during guided partitioning. </para> <figure> <title>Boot Device Selection</title>

1 0

[install-guide/f21-branch] UEFI systems use the specified bootloader target device too.
by Pete Travis 06 Dec '14

06 Dec '14

commit 93b3ea0d494f202eb19c1d29b04c10eaa6daefa5 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Sat Dec 6 13:35:49 2014 -0700 UEFI systems use the specified bootloader target device too. en-US/StorageSpoke_BootLoader.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/StorageSpoke_BootLoader.xml b/en-US/StorageSpoke_BootLoader.xml index 0c1c416..be8eefe 100644 --- a/en-US/StorageSpoke_BootLoader.xml +++ b/en-US/StorageSpoke_BootLoader.xml @@ -17,7 +17,7 @@ If you have other operating systems already installed, the &PRODUCT; installer will attempt to automatically detect and configure the boot loader to start them. You can manually configure any additional operating systems after you finish the installation, if they are not detected properly. For instructions on editing <application>GRUB2</application> configuration, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" /> </para> <para> - If you are installing Fedora on a non-UEFI system with more than one disk, you may want to manually specify where the bootloader should be installed. 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. + If you are installing Fedora system with more than one disk, you may want to manually specify where the bootloader should be installed. 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. The bootloader will be installed on the device of your choice, or on a UEFI system, the <systemitem class="resource" >EFI system partition</systemitem> will be created on that device during guided partitioning. </para> <figure> <title>Boot Device Selection</title>

1 0

[install-guide/f21-branch: 2/2] Merge branch 'f21-branch' of ssh://git.fedorahosted.org/git/docs/install-guide into f21-branch
by Pete Travis 06 Dec '14

06 Dec '14

commit 6144f61df8b68cd445d258002378cbb5e8d563ba Merge: ba0a4ae 6c83cc7 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Sat Dec 6 13:24:10 2014 -0700 Merge branch 'f21-branch' of ssh://git.fedorahosted.org/git/docs/install-guide into f21-branch 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/NetworkSpoke_EditConnection.xml | 4 +- 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 prepare_anaconda_help_content.py | 2 + 50 files changed, 346 insertions(+), 81 deletions(-) --- diff --cc en-US/StorageSpoke_BootLoader.xml index 1cd1d52,9d2785b..0c1c416 --- a/en-US/StorageSpoke_BootLoader.xml +++ b/en-US/StorageSpoke_BootLoader.xml @@@ -17,11 -17,21 +17,21 @@@ If you have other operating systems already installed, the &PRODUCT; installer will attempt to automatically detect and configure the boot loader to start them. You can manually configure any additional operating systems after you finish the installation, if they are not detected properly. For instructions on editing <application>GRUB2</application> configuration, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" /> </para> <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. + If you are installing Fedora on a non-UEFI system with more than one disk, you may want to manually specify where the bootloader should be installed. 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>

1 0

[install-guide/f21-branch: 1/2] Some readers might get confused when their bootloader doesn't go where they expect. Lead off the par
by Pete Travis 06 Dec '14

06 Dec '14

commit ba0a4ae02b3028b67a1cf8fd4c56bcdbce6abc0d Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Sat Dec 6 13:23:47 2014 -0700 Some readers might get confused when their bootloader doesn't go where they expect. Lead off the para about selecting it with an example of a situation that might require it. en-US/StorageSpoke_BootLoader.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/StorageSpoke_BootLoader.xml b/en-US/StorageSpoke_BootLoader.xml index aca52e2..1cd1d52 100644 --- a/en-US/StorageSpoke_BootLoader.xml +++ b/en-US/StorageSpoke_BootLoader.xml @@ -17,7 +17,7 @@ If you have other operating systems already installed, the &PRODUCT; installer will attempt to automatically detect and configure the boot loader to start them. You can manually configure any additional operating systems after you finish the installation, if they are not detected properly. For instructions on editing <application>GRUB2</application> configuration, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" /> </para> <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. + If you are installing Fedora on a non-UEFI system with more than one disk, you may want to manually specify where the bootloader should be installed. 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>

1 0

[install-guide/f21-branch] (2 commits) ...Merge branch 'f21-branch' of ssh://git.fedorahosted.org/git/docs/install-guide into f21-branch
by Pete Travis 06 Dec '14

06 Dec '14

Summary of changes: ba0a4ae... Some readers might get confused when their bootloader doesn 6144f61... Merge branch 'f21-branch' of ssh://git.fedorahosted.org/git

1 0

[release-notes] You can do workstation and server with kickstart easily
by Pete Travis 06 Dec '14

06 Dec '14

commit ee45ce37a8421448af91372971834df36bd56b78 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Sat Dec 6 13:10:40 2014 -0700 You can do workstation and server with kickstart easily en-US/Products-Server.xml | 5 ++++- en-US/Products-Workstation.xml | 3 +++ 2 files changed, 7 insertions(+), 1 deletions(-) --- diff --git a/en-US/Products-Server.xml b/en-US/Products-Server.xml index cdd1c16..f5a181b 100644 --- a/en-US/Products-Server.xml +++ b/en-US/Products-Server.xml @@ -11,7 +11,10 @@ <title>Fedora Server Roles</title> <para> A Featured Server role is an installable component of Fedora Server that provides a well-integrated service on top of the Fedora Server platform. These prepared roles simplify deployment and management of a service compared to setting up an upstream server from scratch; their use is recommended but optional; existing users of upstream servers based on Fedora RPMs will not be impeded. - </para> + </para> + <para> + For kickstart installations, you can use the <package>Fedora Server</package> environment group to deploy Server. + </para> <section id="Framework-for-Server-Role-Deployment"> <title>Framework for Server Role Deployment</title> <para> diff --git a/en-US/Products-Workstation.xml b/en-US/Products-Workstation.xml index 5f3c38e..33df6e2 100644 --- a/en-US/Products-Workstation.xml +++ b/en-US/Products-Workstation.xml @@ -9,6 +9,9 @@ <para> The Fedora Workstation product provides an easy to use, powerful environment for developers to both work and play. Desktop users can enjoy the familiar GNOME Desktop Environment, with support for devices and applications used every day. Developers will appreciate how Workstation is configured for their needs, and provides useful tools like <application>DevAssistant</application>. </para> + <para> + For kickstart installations, you can use the <package>Fedora Workstation</package> environment group to deploy Workstation. + </para> <section id="Workstation-GNOME"> <title>GNOME powered</title> <para>

1 0

[release-notes] slight context adjustment
by Pete Travis 06 Dec '14

06 Dec '14

commit a8db9e63c7c8509fce5b7210149b84cfde9f4309 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Sat Dec 6 11:10:58 2014 -0700 slight context adjustment en-US/Security.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/Security.xml b/en-US/Security.xml index cf01960..219eba7 100644 --- a/en-US/Security.xml +++ b/en-US/Security.xml @@ -38,7 +38,7 @@ OpenSSL was patched to disallow verification of certificates that are signed with MD5 algorithm. The use of MD5 hash algorithm for certificate signatures is now considered as insecure and thus all the main crypto libraries in Fedora were patched to reject such certificates. </para> <para> - Certificates signed with MD5 algorithm are not present on public https web sites anymore but they can be still in use on private networks or used for authentication on openvpn based VPNs such as in bug 1157260. It is highly recommended to replace such certificates with new ones signed with SHA256 or at least SHA1. As a temporary measure the <envar>OPENSSL_ENABLE_MD5_VERIFY</envar> environment variable can be set to allow verification of certificates signed with MD5 algorithm. + Certificates signed with MD5 algorithm are not present on public https web sites anymore but they may still be in use on private networks or used for authentication on openvpn based VPNs. It is highly recommended to replace such certificates with new ones signed with SHA256 or at least SHA1. As a temporary measure the <envar>OPENSSL_ENABLE_MD5_VERIFY</envar> environment variable can be set to allow verification of certificates signed with MD5 algorithm. </para> </section> </section>

1 0

[release-notes: 2/2] Merge branch 'master' of ssh://git.fedorahosted.org/git/docs/release-notes
by Pete Travis 06 Dec '14

06 Dec '14

commit 8afacb080e18c0a9df3b8e79ceed5bc6d60b5244 Merge: b62fd2f 9684e5a Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Sat Dec 6 11:08:16 2014 -0700 Merge branch 'master' of ssh://git.fedorahosted.org/git/docs/release-notes en-US/Desktop.xml | 6 +++--- en-US/Products-Server.xml | 10 +++++++--- en-US/Section-Developers.xml | 3 ++- en-US/Section-Sysadmin.xml | 11 ++++++----- 4 files changed, 18 insertions(+), 12 deletions(-) ---

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits December 2014