[install-guide] Add --mkfsoptions to part/raid/logvol/btrfs in Kickstart
by pbokoc
commit b43344bd3479290d3c5792a7bb83d2444ef5cecb
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Oct 19 23:33:47 2015 +0200
Add --mkfsoptions to part/raid/logvol/btrfs in Kickstart
en-US/Kickstart_Syntax_Reference.xml | 32 ++++++++++++++++++++++++++++++++
1 files changed, 32 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index 97f238f..ea267ef 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -799,6 +799,14 @@
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>--mkfsoptions=</option></term>
+ <listitem>
+ <para>
+ Specifies additional parameters to be passed to the program that makes a filesystem on this volume or subvolume. No processing is done on the list of arguments, so they must be supplied in a format that can be passed directly to the mkfs program. This means multiple options should be comma-separated or surrounded by double quotes, depending on the filesystem.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
<para>
The following example shows how to create a Btrfs volume from member partitions on three disks with subvolumes for <filename class="directory">/</filename> and <filename class="directory">/home</filename>. The main volume is not mounted or used directly in this example.
@@ -1186,6 +1194,14 @@
</listitem>
</varlistentry>
<varlistentry>
+ <term><option>--mkfsoptions=</option></term>
+ <listitem>
+ <para>
+ Specifies additional parameters to be passed to the program that makes a filesystem on this logical volume. No processing is done on the list of arguments, so they must be supplied in a format that can be passed directly to the mkfs program. This means multiple options should be comma-separated or surrounded by double quotes, depending on the filesystem.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
<term><option>--label=</option></term>
<listitem>
<para>
@@ -1600,6 +1616,14 @@
</listitem>
</varlistentry>
<varlistentry>
+ <term><option>--mkfsoptions=</option></term>
+ <listitem>
+ <para>
+ Specifies additional parameters to be passed to the program that makes a filesystem on this partition. No processing is done on the list of arguments, so they must be supplied in a format that can be passed directly to the mkfs program. This means multiple options should be comma-separated or surrounded by double quotes, depending on the filesystem.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
<term><option>--label=</option></term>
<listitem>
<para>
@@ -1741,6 +1765,14 @@
</listitem>
</varlistentry>
<varlistentry>
+ <term><option>--mkfsoptions=</option></term>
+ <listitem>
+ <para>
+ Specifies additional parameters to be passed to the program that makes a filesystem on this partition. No processing is done on the list of arguments, so they must be supplied in a format that can be passed directly to the mkfs program. This means multiple options should be comma-separated or surrounded by double quotes, depending on the filesystem.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
<term><option>--label=</option></term>
<listitem>
<para>
8 years, 6 months
[install-guide] Add reqpart command to Kickstart, kexec option to reboot, and cache options to logvol
by pbokoc
commit b225164a6f3c7a89c61a3668659ce3bca8695711
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Oct 19 23:20:41 2015 +0200
Add reqpart command to Kickstart, kexec option to reboot, and cache options to logvol
en-US/Kickstart_Syntax_Reference.xml | 60 ++++++++++++++++++++++++++++++++++
1 files changed, 60 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index c216456..97f238f 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -1339,7 +1339,36 @@
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>--cachepvs=</option></term>
+ <listitem>
+ <para>
+ A comma-separated list of (fast) physical volumes which should be used for LVM cache.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--cachesize=</option></term>
+ <listitem>
+ <para>
+ Requested size of cache attached to the logical volume, in MiB. (Requires the <option>--cachepvs=</option> option.)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--cachemode=</option></term>
+ <listitem>
+ <para>
+ Mode to be used for LVM cache (either <literal>writeback</literal> or <literal>writethrough</literal>).
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
+ <note>
+ <para>
+ The <option>--cachepvs=</option>, <option>--cachesize=</option>, and <option>--cachemode=</option> options listed above are used to configure LVM caching. For more information, see the <systemitem>lvmcache(7)</systemitem> man page.
+ </para>
+ </note>
<para>
Create one or more partitions first using <xref linkend="sect-kickstart-commands-part" />, create the logical volume group (<xref linkend="sect-kickstart-commands-volgroup" />), and then create logical volumes. For example:
</para>
@@ -1800,6 +1829,29 @@
</example>
</section>
+ <section id="sect-kickstart-commands-reqpart">
+ <title>reqpart (optional) - Create Required Partitions</title>
+ <para>
+ Automatically create partitions required by your hardware platform. These include a <filename>/boot/efi</filename> for x86_64 and Aarch64 systems with UEFI firmware, <systemitem>biosboot</systemitem> for x86_64 systems with BIOS firmware and GPT (GUID Partition Table), and <systemitem>PRePBoot</systemitem> for IBM Power Systems.
+ </para>
+ <note>
+ <para>
+ This command can not be used together with <command>autopart</command>, because <command>autopart</command> does the same and creates other partitions or logical volumes such as <filename>/</filename> and <systemitem>swap</systemitem> on top. In contrast with <command>autopart</command>, this command only creates platform-specific partitions and leaves the rest of the drive empty, allowing you to create a custom layout.
+ </para>
+ </note>
+ <programlisting><command>reqpart [--add-boot]</command></programlisting>
+ <variablelist>
+ <varlistentry>
+ <term><option>--add-boot</option></term>
+ <listitem>
+ <para>
+ Create a separate <filename>/boot</filename> partition in addition to the platform-specific partition created by the base command.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
<section id="sect-kickstart-commands-volgroup">
<title>volgroup (optional) - Create LVM Volume Group</title>
<para>
@@ -3493,6 +3545,14 @@
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>--kexec</option></term>
+ <listitem>
+ <para>
+ Use this option to reboot into the new system using the <systemitem>kexec</systemitem> kernel switching mechanism instead of a full reboot, bypassing the BIOS/Firmware and boot loader.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
</section>
8 years, 6 months
[install-guide] Fix typo in bootloader --leavebootorder in Kickstart
by pbokoc
commit c2ae438d84945c6590e48b448f1a418032d0c5c1
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Oct 19 23:15:27 2015 +0200
Fix typo in bootloader --leavebootorder in Kickstart
en-US/Kickstart_Syntax_Reference.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index e6a4d5f..c216456 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -606,7 +606,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--leavebootloader</option></term>
+ <term><option>--leavebootorder</option></term>
<listitem>
<para>
Prevents the installation program from making changes to the existing list of bootable images on UEFI or ISeries/PSeries systems.
8 years, 6 months
[install-guide] BZ#1217953 - add --nombr to bootloader Kickstart command
by pbokoc
commit 2b2411cb4a0fa572861e76a181dc35ea5677f56e
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Oct 19 23:06:21 2015 +0200
BZ#1217953 - add --nombr to bootloader Kickstart command
en-US/Kickstart_Syntax_Reference.xml | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index 188d624..e6a4d5f 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -719,6 +719,14 @@
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>--nombr</option></term>
+ <listitem>
+ <para>
+ Install the boot loader configuration and support files, but do not modify the MBR.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
</section>
8 years, 6 months
[install-guide] BZ#1255945 - Updated wording regarding minimum required partitions
by pbokoc
commit 67b5dbfe840227c0180e9e5b4a92db010d09fead
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Oct 19 22:22:11 2015 +0200
BZ#1255945 - Updated wording regarding minimum required partitions
en-US/Disk_Partitions.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Disk_Partitions.xml b/en-US/Disk_Partitions.xml
index b03799a..598833c 100644
--- a/en-US/Disk_Partitions.xml
+++ b/en-US/Disk_Partitions.xml
@@ -911,7 +911,7 @@
At this point in the process of preparing to install &PRODUCT;, you should give some consideration to the number and size of the partitions to be used by your new operating system. However, there is no one right answer to this question. It depends on your needs and requirements.
</para>
<para>
- Unless you have a reason for doing otherwise, you should <emphasis>at least</emphasis> create the following partitions: <filename>swap</filename>, <filename>/boot/</filename>, and <filename>/</filename> (root).
+ Unless you have a reason for doing otherwise, you should <emphasis>at least</emphasis> create a <filename>/boot</filename> partition and a <filename>/</filename> (root) partition. Depending on your system's hardware specifications, additional partitions may be necessary, such as <filename>/boot/efi</filename> for 64-bit AMD and Intel systems with UEFI firmware, a <systemitem>biosboot</systemitem> partition for AMD and Intel systems with a GUID Partition Table (GPT) label on the system disk, or a <systemitem>PReP Boot</systemitem> partition on IBM Power Systems servers.
</para>
<para>
See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for more information about the recommended partitioning scheme.
8 years, 6 months
[install-guide] BZ#1214964 - hold down Option on Mac to select boot media
by pbokoc
commit 1ceaaaf0f7194f60ec0bd5e53d589175b7eb7199
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Oct 19 22:14:24 2015 +0200
BZ#1214964 - hold down Option on Mac to select boot media
en-US/Booting_the_Installation.xml | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Booting_the_Installation.xml b/en-US/Booting_the_Installation.xml
index 6ca9a4e..0989bb0 100644
--- a/en-US/Booting_the_Installation.xml
+++ b/en-US/Booting_the_Installation.xml
@@ -21,7 +21,7 @@
</warning>
<important>
<para>
- &PRODUCT; does not support UEFI booting for 32-bit x86 systems. Only BIOS boot is supported on these systems.
+ &PRODUCT; does not support UEFI booting for 32-bit x86 systems. Only BIOS boot is supported on these systems.
</para>
<para>
Also note that &PRODUCT; only fully supports version 2.2 of the UEFI specification. Hardware that supports version 2.3 or later will boot and work normally, but the additional functionality defined by these later specifications will not be available. The UEFI specifications are available from <ulink url="http://www.uefi.org/specs/agreement/" />.
@@ -49,6 +49,9 @@
<para>
Some older systems may not support choosing a boot device at startup. In that case, enter the system's SETUP (BIOS), and change the default boot order so that your boot media (CD, DVD, USB or network) has higher priority than internal hard drives.
</para>
+ <para>
+ On Mac hardware, hold down the <keycap>Option</keycap> key to enter the boot media selection menu.
+ </para>
</note>
</step>
<step>
8 years, 6 months
[networking-guide] master: teaming will not work without a switch (5cf2661)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit 5cf266191afae65cef9b5ec117356c7e3274b4b3
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Oct 15 23:25:50 2015 +0200
teaming will not work without a switch
>---------------------------------------------------------------
en-US/Configure_Network_Teaming.xml | 17 +++++++++++++++++
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/en-US/Configure_Network_Teaming.xml b/en-US/Configure_Network_Teaming.xml
index 720b0e7..c04e3a4 100644
--- a/en-US/Configure_Network_Teaming.xml
+++ b/en-US/Configure_Network_Teaming.xml
@@ -5,6 +5,23 @@
]>
<chapter id="ch-Configure_Network_Teaming">
<title>Configure Network Teaming</title>
+
+
+ <warning>
+ <para>
+ The use of direct cable connections without network switches is not supported for teaming. The failover mechanisms described here will not work as expected without the presence of network switches.
+ </para>
+</warning>
+
+ <note>
+ <para>
+ The active-backup, balance-tlb and balance-alb modes do not require any specific configuration of the switch. Other bonding modes require configuring the switch to aggregate the links. For example, a Cisco switch requires EtherChannel for Modes 0, 2, and 3, but for Mode 4 LACP and EtherChannel are required. See the documentation supplied with your switch and see <ulink url="https://www.kernel.org/doc/Documentation/networking/bonding.txt">https://www.kernel.org/doc/Documentation/networking/bonding.txt</ulink>.
+ </para>
+ <para>
+ Unlike bonding, if a team interface is configured to use link aggregation but LACP is not correctly configured and working on the network switch, no routable connection will be formed.
+ </para>
+ </note>
+
<!-- Topics, Concepts:-->
<section id="sec-Understanding_Network_Teaming">
<title>Understanding Network Teaming</title>
8 years, 6 months
[networking-guide] master: Static routes should only be set in ifcfg files (b28c0e9)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit b28c0e9c2346c4e4b399793ea797469c3f623b68
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Oct 15 23:24:34 2015 +0200
Static routes should only be set in ifcfg files
The use if /etc/sysconfig/network is depricated
>---------------------------------------------------------------
en-US/Configure_Networking.xml | 5 +----
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index f8421f6..b8bf9a8 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -1715,14 +1715,11 @@ default via 192.168.122.1 dev eth1 proto static metric 1024
<para>
The default gateway is determined by the network scripts which parse the <filename>/etc/sysconfig/network</filename> file first and then the network interface <literal>ifcfg</literal> files for interfaces that are <quote>up</quote>. The <literal>ifcfg</literal> files are parsed in numerically ascending order, and the last GATEWAY directive to be read is used to compose a default route in the routing table.</para>
<para>
- The default route can thus be indicated by means of the GATEWAY directive and can be specified either globally or in interface-specific configuration files. Specifying the gateway globally has certain advantages in static networking environments, especially if more than one network interface is present. It can make fault finding simpler if applied consistently.
+ The default route can thus be indicated by means of the GATEWAY directive, either globally or in interface-specific configuration files. However, in &MAJOROS; the use of the global <filename>/etc/sysconfig/network</filename> file is deprecated, and specifying the gateway should now only be done in per-interface configuration files.
</para>
<para>
In dynamic network environments, where mobile hosts are managed by <application>NetworkManager</application>, gateway information is likely to be interface specific and is best left to be assigned by <systemitem class="protocol">DHCP</systemitem>. In special cases where it is necessary to influence <application>NetworkManager</application>'s selection of the exit interface to be used to reach a gateway, make use of the <command>DEFROUTE=no</command> command in the <literal>ifcfg</literal> files for those interfaces which do not lead to the default gateway.
</para>
- <para>
- Global default gateway configuration is stored in the <filename>/etc/sysconfig/network</filename> file. This file specifies gateway and host information for all network interfaces.<!-- For more information about this file and the directives it accepts, see the <citetitle pubwork="book">&MAJOROSVER; System Administrator's Reference Guide</citetitle>.-->
- </para>
</section>
<section id="sec-Configuring_Static_Routes_in_ifcfg_files">
8 years, 6 months
[networking-guide] master: nmcli can set static routes using the CLI (8dc8467)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit 8dc84671682b17bde509f528049c517919e70373
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Oct 15 23:23:13 2015 +0200
nmcli can set static routes using the CLI
>---------------------------------------------------------------
en-US/Configure_Networking.xml | 13 ++++++++++++-
1 files changed, 12 insertions(+), 1 deletions(-)
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index c009441..f8421f6 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -2254,9 +2254,20 @@ Note that you have to use the <option>ifname</option> argument even if you do no
<section id="sec-Configuring_Static_Routes_Using_nmcli">
<title>Configuring Static Routes Using nmcli</title>
<para>
- To configure static routes using the <application>nmcli</application> tool, the interactive editor mode must be used.
+ Static routes can only be set per-interface, not globally, using the <application>nmcli</application> tool. The command line or the interactive editor mode can be be used.
</para>
+<example id="ex-Configuring_Static_Routes_Using_nmcli">
+<title>Configuring Static Routes Using nmcli</title>
+
+<para>
+To configure a static route for an existing Ethernet connection using the command line, enter a command as follows:
+<screen>~]# <command>nmcli connection modify eth0 +ipv4.routes 192.168.122.0/24 ipv4.gateway 10.10.10.1</command></screen>
+ This will direct traffic for the <systemitem class="ipaddress">192.168.122.0/24</systemitem> subnet to the gateway at <systemitem class="ipaddress">10.10.10.1</systemitem>
+</para>
+
+</example>
+
<example id="ex-Configuring_Static_Routes_Using_nmcli_Editor">
<title>Configuring Static Routes Using nmcli Editor</title>
8 years, 6 months
[release-notes/f23] Add fedora-user-agent-chrome note
by Paul Frields
commit 7db84e598d2d4aa601fa752a8456dfa57730882a
Author: Paul W. Frields <stickster(a)gmail.com>
Date: Thu Oct 15 14:57:36 2015 -0400
Add fedora-user-agent-chrome note
en-US/Editions-Workstation.xml | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Editions-Workstation.xml b/en-US/Editions-Workstation.xml
index f6bde18..f3a5d93 100644
--- a/en-US/Editions-Workstation.xml
+++ b/en-US/Editions-Workstation.xml
@@ -17,5 +17,8 @@
<para>
Fedora 23 will include the latest version of the GNOME desktop environment: 3.18. See <xref linkend="desktop-GNOME" /> for details.
</para>
+ <para>
+ Fedora Workstation contains the <package>fedora-user-agent-chrome</package> package by default. This package is used to provide a Fedora-specific user agent string to users who later download Google Chrome for web browsing. This brings the Google Chrome user agent string into closer alignment with the one used by default in the <package>firefox</package> package.
+ </para>
</section>
</section>
8 years, 6 months