[networking-guide] 21: Adding some paras to improve layout (186e863)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : 21
>---------------------------------------------------------------
commit 186e8638f77b5c93bfbd05861effcbd7f9e7593b
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Feb 26 22:34:48 2015 +0100
Adding some paras to improve layout
>---------------------------------------------------------------
en-US/Configure_Networking.xml | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index fca052f..b3751da 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -2114,10 +2114,12 @@ Connection 'test-lab' (05abfd5e-324e-4461-844e-8501ba704773) successfully added.
<para>
To set two <systemitem class="protocol">IPv4</systemitem> <systemitem class="protocol">DNS</systemitem> server addresses:
<screen>~]$ <command>nmcli con mod <replaceable>test-lab</replaceable> ipv4.dns "8.8.8.8 8.8.4.4"</command></screen>
- Note that this will replace any previously set <systemitem class="protocol">DNS</systemitem> servers.
+ Note that this will replace any previously set <systemitem class="protocol">DNS</systemitem> servers.</para>
+ <para>
To set two <systemitem class="protocol">IPv6</systemitem> <systemitem class="protocol">DNS</systemitem> server addresses:
<screen>~]$ <command>nmcli con mod <replaceable>test-lab</replaceable> ipv6.dns "2001:4860:4860::8888 2001:4860:4860::8844"</command></screen>
- Note that this will replace any previously set <systemitem class="protocol">DNS</systemitem> servers.
+ Note that this will replace any previously set <systemitem class="protocol">DNS</systemitem> servers.</para>
+ <para>
Alternatively, to add additional <systemitem class="protocol">DNS</systemitem> servers to any previously set, use the <literal>+</literal> prefix as follows:
<screen>~]$ <command>nmcli con mod <replaceable>test-lab</replaceable> +ipv4.dns "8.8.8.8 8.8.4.4"</command></screen>
<screen>~]$ <command>nmcli con mod <replaceable>test-lab</replaceable> +ipv6.dns "2001:4860:4860::8888 2001:4860:4860::8844"</command></screen>
9 years, 1 month
[networking-guide] master: VLAN name should correspond with VLAN id (edc6c31)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit edc6c31500484f9c48a2377344a8cee9d95ae09c
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Sun Mar 29 19:21:13 2015 +0200
VLAN name should correspond with VLAN id
>---------------------------------------------------------------
en-US/Configure_802_1Q_VLAN_Tagging.xml | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/en-US/Configure_802_1Q_VLAN_Tagging.xml b/en-US/Configure_802_1Q_VLAN_Tagging.xml
index f09c7ad..6f0810c 100644
--- a/en-US/Configure_802_1Q_VLAN_Tagging.xml
+++ b/en-US/Configure_802_1Q_VLAN_Tagging.xml
@@ -363,16 +363,16 @@ GENERAL.STATE: activating
Further options for the VLAN command are listed in the VLAN section of the <filename>nmcli(1)</filename> man page. In the man pages the device on which the VLAN is created is referred to as the parent device. In the example above the device was specified by its interface name, <literal>eth0</literal>, it can also be specified by the connection UUID or MAC address.
</para>
<para>
- To create an 802.1Q VLAN connection profile with ingress priority mapping on Ethernet interface <replaceable>eth1</replaceable>, with name <interface>VLAN1</interface> and ID <literal>13</literal>, issue a command as follows:
- <screen>~]$ <command>nmcli con add type vlan con-name <replaceable>VLAN1</replaceable> dev <replaceable>eth2</replaceable> id 13 ingress "2:3,3:5"</command></screen>
+ To create an 802.1Q VLAN connection profile with ingress priority mapping on Ethernet interface <replaceable>eth1</replaceable>, with name <interface>VLAN13</interface> and ID <literal>13</literal>, issue a command as follows:
+ <screen>~]$ <command>nmcli con add type vlan con-name <replaceable>VLAN13</replaceable> dev <replaceable>eth2</replaceable> id 13 ingress "2:3,3:5"</command></screen>
</para>
<para>
To view all the parameters associated with the VLAN created above, issue a command as follows:
- <screen>~]$ <command>nmcli connection show <replaceable>vlan-VLAN10</replaceable></command></screen>
+ <screen>~]$ <command>nmcli connection show <replaceable>VLAN13</replaceable></command></screen>
</para>
<para>
To change the MTU, issue a command as follows:
- <screen>~]$ <command>nmcli connection modify <replaceable>vlan-VLAN10</replaceable> 802.mtu 1496</command></screen>
+ <screen>~]$ <command>nmcli connection modify <replaceable>VLAN13</replaceable> 802.mtu 1496</command></screen>
The MTU setting determines the maximum size of the network layer packet. The maximum size of the payload the link-layer frame can carry in turn limits the network layer MTU. For standard Ethernet frames this means an MTU of 1500 bytes. It should not be necessary to change the MTU when setting up a VLAN as the link-layer header is increased in size by 4 bytes to accommodate the 802.1Q tag.
</para>
<para>
9 years, 1 month
[networking-guide] master: Fix: Assigning Addresses to VLAN Interfaces (e0ef542)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit e0ef5424c24f817adcb4b0c3143057feaaf0e092
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Sat Mar 28 23:04:46 2015 +0100
Fix: Assigning Addresses to VLAN Interfaces
>---------------------------------------------------------------
en-US/Configure_802_1Q_VLAN_Tagging.xml | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/en-US/Configure_802_1Q_VLAN_Tagging.xml b/en-US/Configure_802_1Q_VLAN_Tagging.xml
index dc5852c..f09c7ad 100644
--- a/en-US/Configure_802_1Q_VLAN_Tagging.xml
+++ b/en-US/Configure_802_1Q_VLAN_Tagging.xml
@@ -301,11 +301,11 @@ Connection 'VLAN12' (b796c16a-9f5f-441c-835c-f594d40e6533) successfully added.</
You can use the same <application>nmcli</application> commands to assign static and dynamic interface addresses as with any other interface.</para>
<para>
For example, a command to create a VLAN interface with a static <systemitem class="protocol">IPv4</systemitem> address and gateway is as follows:
- <screen>~]$ <command>nmcli con add type vlan con-name <replaceable>VLAN20</replaceable> ifname <replaceable>eth0</replaceable> ip4 10.10.10.10/24 \</command>
-<command>gw4 10.10.10.254</command></screen></para>
+ <screen>~]$ <command>nmcli con add type vlan con-name <replaceable>VLAN20</replaceable> ifname <replaceable>VLAN20</replaceable> id 20 \</command>
+<command>dev <replaceable>eth0</replaceable> ip4 10.10.10.10/24 gw4 10.10.10.254</command></screen></para>
<para>
To create a VLAN interface with dynamically assigned addressing, issue a command as follows:
- <screen>~]$ <command>nmcli con add type vlan con-name <replaceable>VLAN30</replaceable> ifname <replaceable>eth0</replaceable></command></screen>
+ <screen>~]$ <command>nmcli con add type vlan con-name <replaceable>VLAN30</replaceable> ifname <replaceable>VLAN30</replaceable> id 30 dev <replaceable>eth0</replaceable></command></screen>
</para>
<para>
See <xref linkend="sec-Connecting_to_a_Network_Using_nmcli" /> for examples of using <application>nmcli</application> commands to configure interfaces.
9 years, 1 month
[install-guide/f22-branch] Better description for network --hostname= in Kickstart
by pbokoc
commit ab9da9dce9be661d355afd01cee109be20df0870
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Fri Mar 13 16:01:21 2015 +0100
Better description for network --hostname= 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 cda2711..1a88f08 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -2260,7 +2260,7 @@
<term><option>--hostname=</option></term>
<listitem>
<para>
- Hostname for the installed system.
+ Host name for the installed system. The host name can be either a <firstterm>fully-qualified domain name</firstterm> (FQDN) in the format <replaceable>hostname</replaceable>.<replaceable>domainname</replaceable>, or a short host name with no domain name. Many networks have a <firstterm>Dynamic Host Configuration Protocol</firstterm> (<systemitem class="protocol">DHCP</systemitem>) service that automatically supplies connected systems with a domain name; to allow the <systemitem class="protocol">DHCP</systemitem> service to assign the domain name to this machine, only specify the short host name.
</para>
</listitem>
</varlistentry>
9 years, 2 months
[install-guide/f21-branch] Better description for network --hostname= in Kickstart
by pbokoc
commit cb1225233e3b97203e0775ae2983a8064d59b381
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Fri Mar 13 16:01:21 2015 +0100
Better description for network --hostname= 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 98076b2..f4c609a 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -2260,7 +2260,7 @@
<term><option>--hostname=</option></term>
<listitem>
<para>
- Hostname for the installed system.
+ Host name for the installed system. The host name can be either a <firstterm>fully-qualified domain name</firstterm> (FQDN) in the format <replaceable>hostname</replaceable>.<replaceable>domainname</replaceable>, or a short host name with no domain name. Many networks have a <firstterm>Dynamic Host Configuration Protocol</firstterm> (<systemitem class="protocol">DHCP</systemitem>) service that automatically supplies connected systems with a domain name; to allow the <systemitem class="protocol">DHCP</systemitem> service to assign the domain name to this machine, only specify the short host name.
</para>
</listitem>
</varlistentry>
9 years, 2 months
[docsite-publican] add a title to the fromt page
by Jeff Fearn
commit 599db9d71adc8ec161a66e8c53e67556a079e56c
Author: Jeff Fearn <jfearn(a)redhat.com>
Date: Wed Mar 11 13:59:17 2015 +1000
add a title to the fromt page
site_home/en-US/Welcome.xml | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
---
diff --git a/site_home/en-US/Welcome.xml b/site_home/en-US/Welcome.xml
index f776c0d..61ea4f4 100644
--- a/site_home/en-US/Welcome.xml
+++ b/site_home/en-US/Welcome.xml
@@ -2,6 +2,7 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<article>
+ <title>Fedora Documentation Hub</title>
<!-- <xi:include href="Article_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<para>
Fedora documentation describes how to install and use the Fedora operating system and the software packaged by the Fedora Project.
9 years, 2 months
[install-guide/f22-branch] EFI system partition mntpoint needs to be /boot/efi
by pbokoc
commit 2d18078e16b9a0aa1e2ae9051f449252adeb0073
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Mar 10 16:26:48 2015 +0100
EFI system partition mntpoint needs to be /boot/efi
en-US/CustomSpoke_AddPhysical.xml | 2 +-
en-US/Kickstart_Syntax_Reference.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/CustomSpoke_AddPhysical.xml b/en-US/CustomSpoke_AddPhysical.xml
index 8f44062..aab3b97 100644
--- a/en-US/CustomSpoke_AddPhysical.xml
+++ b/en-US/CustomSpoke_AddPhysical.xml
@@ -40,7 +40,7 @@
</para>
<note>
<para>
- When creating a swap partition, specify the mount point as <literal>swap</literal>. For a BIOS Boot partition, use <literal>biosboot</literal>. For an EFI System Partition, use <literal>efi</literal>.
+ When creating a swap partition, specify the mount point as <literal>swap</literal>. For a BIOS Boot partition, use <literal>biosboot</literal>. For an EFI System Partition, use <literal>/boot/efi</literal>.
</para>
<para>
For information about these partition types, see <xref linkend="sect-installation-gui-manual-partitioning-recommended" />.
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index d512ed0..cda2711 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -1486,7 +1486,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>efi</literal></term>
+ <term><literal>/boot/efi</literal></term>
<listitem>
<para>
An EFI System Partition. An EFI partition at least 50 MB in size is necessary on UEFI-based systems; the recommended size is 200 MB. It is not necessary on BIOS systems. Also see <xref linkend="sect-kickstart-commands-part" />.
9 years, 2 months
[install-guide/f21-branch] EFI system partition mntpoint needs to be /boot/efi
by pbokoc
commit 06deb15cc71de848749343c6c91aeb4959eb03c2
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Tue Mar 10 16:26:48 2015 +0100
EFI system partition mntpoint needs to be /boot/efi
en-US/CustomSpoke_AddPhysical.xml | 2 +-
en-US/Kickstart_Syntax_Reference.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/CustomSpoke_AddPhysical.xml b/en-US/CustomSpoke_AddPhysical.xml
index 8f44062..aab3b97 100644
--- a/en-US/CustomSpoke_AddPhysical.xml
+++ b/en-US/CustomSpoke_AddPhysical.xml
@@ -40,7 +40,7 @@
</para>
<note>
<para>
- When creating a swap partition, specify the mount point as <literal>swap</literal>. For a BIOS Boot partition, use <literal>biosboot</literal>. For an EFI System Partition, use <literal>efi</literal>.
+ When creating a swap partition, specify the mount point as <literal>swap</literal>. For a BIOS Boot partition, use <literal>biosboot</literal>. For an EFI System Partition, use <literal>/boot/efi</literal>.
</para>
<para>
For information about these partition types, see <xref linkend="sect-installation-gui-manual-partitioning-recommended" />.
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index 9b3db04..98076b2 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -1486,7 +1486,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>efi</literal></term>
+ <term><literal>/boot/efi</literal></term>
<listitem>
<para>
An EFI System Partition. An EFI partition at least 50 MB in size is necessary on UEFI-based systems; the recommended size is 200 MB. It is not necessary on BIOS systems. Also see <xref linkend="sect-kickstart-commands-part" />.
9 years, 2 months
