January 2013 - docs-commits - Fedora Mailing-Lists

[install-guide] Removing admonition that GRUB cannot construct software RAID

by Jack Reed

commit d9e0aa7dfb72202595f250b6b64c3d8e764dcd6d Author: Jack Reed <jreed(a)redhat.com> Date: Fri Jan 11 12:26:01 2013 +1000 Removing admonition that GRUB cannot construct software RAID en-US/Grub.xml | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) --- diff --git a/en-US/Grub.xml b/en-US/Grub.xml index 433cac2..09a9701 100644 --- a/en-US/Grub.xml +++ b/en-US/Grub.xml @@ -336,7 +336,7 @@ <para> The next time the system boots, the GRUB graphical boot loader menu appears before the kernel loads into memory. </para> - <important> +  </section>

11 years, 4 months

1
0
0 / 0

[system-administrators-guide] Enabling: go to <xref linkend="sec-Configuring_Routes"/>

by stephenw

commit f2b8a3a3354b8818dcecdd08d85e57d2613f2a0f Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Thu Jan 10 11:39:19 2013 +0100 Enabling: go to <xref linkend="sec-Configuring_Routes"/> en-US/NetworkManager.xml | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) --- diff --git a/en-US/NetworkManager.xml b/en-US/NetworkManager.xml index 0e71b48..3a090f7 100644 --- a/en-US/NetworkManager.xml +++ b/en-US/NetworkManager.xml @@ -1578,8 +1578,8 @@ NetworkManager (pid 1527) is running... </listitem> </varlistentry> </variablelist> -  + <para>For information on configuring static routes for the network connection, go to <xref + linkend="sec-Configuring_Routes"/>.</para> </section>

11 years, 4 months

1
0
0 / 0

[system-administrators-guide] I changed and moved "Establishing Routes" to "Configuring Routes" and made it generic not VPN specif

by stephenw

commit f8f645ba682fa7c5e004f3265dbd3f91b5861c98 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Thu Jan 10 11:38:38 2013 +0100 I changed and moved "Establishing Routes" to "Configuring Routes" and made it generic not VPN specific en-US/NetworkManager.xml | 113 +++++++++++++++++++++++++-------------------- 1 files changed, 63 insertions(+), 50 deletions(-) --- diff --git a/en-US/NetworkManager.xml b/en-US/NetworkManager.xml index 5744dcd..0e71b48 100644 --- a/en-US/NetworkManager.xml +++ b/en-US/NetworkManager.xml @@ -1125,37 +1125,6 @@ NetworkManager (pid 1527) is running... </listitem> </varlistentry> </variablelist> - </section> - <section - id="sec-Establishing_Routes"> - <title>Establishing Routes</title> - <figure id="exam-User_and_System_Connections_Static-Routes"> - <title>Configuring static network routes</title> - <mediaobject - id="mediaobj-Network_Configuration-NM-System_eth0-Routes"> - <imageobject> - <imagedata - scalefit="0" - fileref="images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png" - format="PNG" /> - </imageobject> - <textobject><para>A screen shot of the static routes window</para></textobject> - </mediaobject> - </figure> - <variablelist> - <varlistentry> - <term> - <guilabel>Addresses</guilabel> - </term> - <listitem> - <para> - <guimenuitem>Address</guimenuitem> — The IP address of a network, sub-net or host.</para> - <para> - <guimenuitem>Netmask</guimenuitem> — The netmask or prefix length of the IP address just entered.</para> - <para> - <guimenuitem>Gateway</guimenuitem> — The IP address of the gateway leading to the network, sub-net or host.</para> - <para> - <guimenuitem>Metric</guimenuitem> — A network cost, that is to say a preference value to give to this route. Lower values will be preferred over higher values.</para> @@ -1183,25 +1152,10 @@ NetworkManager (pid 1527) is running... linkend="sec-Configuring_IPv4_Settings"/>. </para> </listitem> - </varlistentry> - <varlistentry> - <term> - <guilabel>Ignore automatically obtained routes</guilabel> - </term> - <listitem> - <para>Select this check box to only use manually entered routes for the VPN tunnel.</para> - </listitem> - </varlistentry> - <varlistentry> - <term> - <guilabel>Use this connection only for resources on its network</guilabel> - </term> - <listitem> - <para>Select this checkbox to prevent the VPN from becoming the default route. Then only the specific routes sent by the VPN server (or routes entered here manually) will be routed over the VPN tunnel.</para> - </listitem> - </varlistentry> - </variablelist> - </section> + + </itemizedlist> + </section> + </section> <section id="sec-Configuring_Connection_Settings"> @@ -1627,6 +1581,65 @@ NetworkManager (pid 1527) is running...  </section> + + + + + <section + id="sec-Configuring_Routes"> + <title>Configuring Routes</title> + <para>A hosts routing table will be automatically populated with routes to directly connected networks. The routes are learned by observing the network interfaces when they are <quote>up</quote>. This section is for entering static routes to networks or hosts which can be reached by traversing an intermediate network or connection, such as a VPN or leased line.</para> + <figure id="exam-User_and_System_Connections_Static-Routes"> + <title>Configuring static network routes</title> + <mediaobject + id="mediaobj-Network_Configuration-NM-System_eth0-Routes"> + <imageobject> + <imagedata + scalefit="0" + fileref="images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png" + format="PNG" /> + </imageobject> + <textobject><para>A screen shot of the static routes window</para></textobject> + </mediaobject> + </figure> + <variablelist> + <varlistentry> + <term> + <guilabel>Addresses</guilabel> + </term> + <listitem> + <para> + <guimenuitem>Address</guimenuitem> — The IP address of a network, sub-net or host.</para> + <para> + <guimenuitem>Netmask</guimenuitem> — The netmask or prefix length of the IP address just entered.</para> + <para> + <guimenuitem>Gateway</guimenuitem> — The IP address of the gateway leading to the network, sub-net or host.</para> + <para> + <guimenuitem>Metric</guimenuitem> — A network cost, that is to say a preference value to give to this route. Lower values will be preferred over higher values.</para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <guilabel>Ignore automatically obtained routes</guilabel> + </term> + <listitem> + <para>Select this check box to only use manually entered routes for this conection.</para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <guilabel>Use this connection only for resources on its network</guilabel> + </term> + <listitem> + <para>Select this checkbox to prevent the connection from becoming the default route. Typical examples are where a connection is a VPN or a leased line to a head office and you do not want any Internet bound traffic to pass over the connection. Selecting this option means that only traffic specifically destined for routes learned automatically over the connection or entered here manually will be routed over the connection.</para> + </listitem> + </varlistentry> + </variablelist> + </section> + + + + </section> <section id="sec-NetworkManager_Architecture">

11 years, 4 months

1
0
0 / 0

[system-administrators-guide] Fixing and improving the DSL Section

by stephenw

commit 72cd872651f8b9eca3db0f7cf54963631d6c9009 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Thu Jan 10 11:36:39 2013 +0100 Fixing and improving the DSL Section en-US/NetworkManager.xml | 91 +++++++++++++++++++++++++++++++++++++++++++++- 1 files changed, 89 insertions(+), 2 deletions(-) --- diff --git a/en-US/NetworkManager.xml b/en-US/NetworkManager.xml index 4d9ffd9..5744dcd 100644 --- a/en-US/NetworkManager.xml +++ b/en-US/NetworkManager.xml @@ -1034,10 +1034,71 @@ NetworkManager (pid 1527) is running... <section id="sec-Establishing_a_DSL_Connection"> <title>Establishing a DSL Connection</title> - <para>Open the Network Connections window by running, as a normal user:</para> + <para>This section is intended for those installations which have a DSL card fitted within a host rather than the external combined DSL modem router combinations typical of private consumer or SOHO installations.</para> +<procedure + id="procedure-Adding_a_New_DSL_Connection"> + <title>Adding a New DSL Connection</title> + <step> + <para>Open the Network Connections window by running, as a normal user:</para> + <screen>~]$ <command>nm-connection-editor &</command> + </screen> + </step> + <step> + <para>Select the DSL tab and click <guibutton>Add</guibutton>.</para> + </step> + <step> + <para>The <guilabel>Editing DSL Connection <replaceable>1</replaceable></guilabel> window appears.</para> + </step> +</procedure> + + <procedure + id="procedure-Editing_an_Existing_DSL_Connection"> + <title>Editing an Existing DSL Connection</title> + <para>You can further configure an existing connection by selecting it in the <guilabel>Network Connections</guilabel> window and clicking <guilabel>Edit</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> + +<step> + <para>Open the Network Connections window by running, as a normal user:</para> <screen>~]$ <command>nm-connection-editor &</command> </screen> - <para>Select the DSL tab and click <guibutton>Add</guibutton>.</para> + </step> + <step> + <para>Select the DSL tab.</para> + </step> + <step> + <para>Select the connection you wish to edit and click the <guilabel>Edit</guilabel> button.</para> + </step> + <step> + <para>The <guilabel>Editing DSL Connection</guilabel> window appears.</para> + </step> + + </procedure> + + + +<bridgehead + id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-dsl">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</bridgehead> + <para>Three settings in the <guilabel>Editing</guilabel> dialog are common to all connection types:</para> + <itemizedlist> + <listitem> + <para> + <guilabel>Connection name</guilabel> — Enter a descriptive name for your network connection. This name will be used to list this connection in the <guilabel>DSL</guilabel> section of the <guilabel>Network Connections</guilabel> window. + </para> + </listitem> + <listitem> + <para> + <guilabel>Connect automatically</guilabel> — Check this box if you want <application>NetworkManager</application> to auto-connect to this connection when it is available. Refer to <xref + linkend="sec-Connecting_to_a_Network_Automatically"/> for more information.</para> + </listitem> + <listitem> + <para> + <guilabel>Available to all users</guilabel> — Check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <xref + linkend="sec-User_and_System_Connections"/> for details.</para> + </listitem> + </itemizedlist> + + + <bridgehead id="bh-Configuring_the_DSL_Tab">Configuring the DSL Tab</bridgehead> + <variablelist> <varlistentry> <term> @@ -1095,6 +1156,32 @@ NetworkManager (pid 1527) is running... <guimenuitem>Gateway</guimenuitem> — The IP address of the gateway leading to the network, sub-net or host.</para> <para> <guimenuitem>Metric</guimenuitem> — A network cost, that is to say a preference value to give to this route. Lower values will be preferred over higher values.</para> + + + + <bridgehead + id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-DSL">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead> + + <para>Once you have finished editing your DSL connection, click the <guibutton>Save</guibutton> button to save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <application>NetworkManager</application> Notification Area applet. See <xref + linkend="sec-Connecting_to_a_Network"/> for information on using your new or altered connection.</para> + <para>You can further configure an existing connection by selecting it in the <guilabel>Network Connections</guilabel> window and clicking <guilabel>Edit</guilabel> to return to the <guilabel>Editing</guilabel> dialog.</para> + <para>Then, to configure:</para> + <itemizedlist> + <listitem> + <para> + The MAC address and MTU settings, click the <guilabel>Wired</guilabel> tab and proceed to <xref + linkend="bh-Configuring_the_Wired_Tab" />; + </para> + </listitem> + + <listitem> + <para>Point-to-point settings for the connection, click the <guilabel>PPP Settings</guilabel> tab and proceed to <xref + linkend="sec-Configuring_PPP_Point-to-Point_Settings"/>;</para> + </listitem> + <listitem> + <para>IPv4 settings for the connection, click the <guilabel>IPv4 Settings</guilabel> tab and proceed to <xref + linkend="sec-Configuring_IPv4_Settings"/>. + </para> </listitem> </varlistentry> <varlistentry>

11 years, 4 months

1
0
0 / 0

[system-administrators-guide] specifying a cloned MAC address

by stephenw

commit 4241619597b4571b72d4248e2057c2cb21a1e3b1 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Thu Jan 10 11:34:38 2013 +0100 specifying a cloned MAC address en-US/NetworkManager.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/NetworkManager.xml b/en-US/NetworkManager.xml index 105fb7d..4d9ffd9 100644 --- a/en-US/NetworkManager.xml +++ b/en-US/NetworkManager.xml @@ -299,7 +299,7 @@ NetworkManager (pid 1527) is running... </itemizedlist> <bridgehead id="bh-Configuring_the_Wired_Tab">Configuring the Wired Tab</bridgehead> - <para>The final two configurable settings are located within the <guilabel>Wired</guilabel> tab itself: the first is a text-entry field where you can specify a MAC (Media Access Control) address, and the second allows you to specify the MTU (Maximum Transmission Unit) value. Normally, you can leave the <guilabel>MAC address</guilabel> field blank and the <guilabel>MTU</guilabel> set to <userinput>automatic</userinput>. These defaults will suffice unless you are associating a wired connection with a second or specific NIC, or performing advanced networking. In such cases, refer to the following descriptions:</para> + <para>The final three configurable settings are located within the <guilabel>Wired</guilabel> tab itself: the first is a text-entry field where you can specify a MAC (Media Access Control) address, manually or by using the dropdown list, in order to lock the connection to a specifc hardware device. The second alows specifying a cloned MAC address to be used, and the third allows you to specify the MTU (Maximum Transmission Unit) value. Normally, you can leave the <guilabel>MAC address</guilabel> field blank and the <guilabel>MTU</guilabel> set to <userinput>automatic</userinput>. These defaults will suffice unless you are associating a wired connection with a second or specific NIC, or performing advanced networking. In such cases, refer to the following descriptions:</para> <variablelist> <varlistentry> <term>

11 years, 4 months

1
0
0 / 0

[system-administrators-guide] Appendix A: Consistent Network Device Naming | Removing parts which no longer apply. | Bill Nottingh

by stephenw

commit b6a5464f059fafba4cf50bd99300d452281c48fb Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Thu Jan 10 10:44:20 2013 +0100 Appendix A: Consistent Network Device Naming | Removing parts which no longer apply. | Bill Nottingham e-mail from Bill applies to Fed 17 and 18 From: Bill Nottingham <notting(a)redhat.com> To: Stephen Wadeley <swadeley(a)redhat.com> Subject: Re: Fwd: Re: rhel-7-feature-page-network-interface-renaming | Changes to Appendix A for Fedora SysAdmin Guide en-US/Consistent_Network_Device_Naming.xml | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) --- diff --git a/en-US/Consistent_Network_Device_Naming.xml b/en-US/Consistent_Network_Device_Naming.xml index e9de1cf..8f21f24 100644 --- a/en-US/Consistent_Network_Device_Naming.xml +++ b/en-US/Consistent_Network_Device_Naming.xml @@ -97,15 +97,15 @@ <section id="sect-Consistent_Network_Device_Naming-Enabling_and_Disabling"> <title>Enabling and Disabling the Feature</title> <para> - To disable the consistent network device naming on Dell systems that would normally have it on by default, pass the following option on the boot command line, both during and after installation: + To disable the consistent network device naming on systems that would normally have it on by default, pass the following option on the boot command line, both during and after installation: </para> <screen><option>biosdevname=0</option></screen> <para> - To enable this feature on other system types that meet the minimum requirements (see <xref linkend="sect-Consistent_Network_Device_Naming-System_Requirements" />), pass the following option on the boot command line, both during and after installation: + To enable this feature, pass the following option on the boot command line, both during and after installation: </para> <screen><option>biosdevname=1</option></screen> <para> - Unless the system meets the minimum requirements, this option will be ignored and the system will boot with the traditional network interface name format. + Unless the system meets the minimum requirements (see <xref linkend="sect-Consistent_Network_Device_Naming-System_Requirements" />), this option will be ignored and the system will boot with the traditional network interface name format. </para> <para> If the <option>biosdevname</option> install option is specified, it must remain as a boot option for the lifetime of the system.

11 years, 4 months

1
0
0 / 0

[install-guide] Added Secureboot explanation to PXE EFI procedure

by Jack Reed

commit 5ab81ed1779ed2520747979ec38aa95f426ed63e Author: Jack Reed <jreed(a)redhat.com> Date: Thu Jan 10 16:02:23 2013 +1000 Added Secureboot explanation to PXE EFI procedure en-US/pxe-server-config-efi.xml | 17 +++++++++++++++-- 1 files changed, 15 insertions(+), 2 deletions(-) --- diff --git a/en-US/pxe-server-config-efi.xml b/en-US/pxe-server-config-efi.xml index 0c464c9..863b155 100644 --- a/en-US/pxe-server-config-efi.xml +++ b/en-US/pxe-server-config-efi.xml @@ -91,11 +91,24 @@ range6 3ffe:501:ffff:100:: temporary; prefix6 3ffe:501:ffff:100:: 3ffe:501:ffff:111:: /64; - option dhcp6.bootfile-url "tftp://[3ffe:501:ffff:100::1]/bootia32.efi"; + option dhcp6.bootfile-url "tftp://[3ffe:501:ffff:100::1]/grubx64.efi"; option dhcp6.name-servers 3ffe:501:ffff:100::1; } -</screen> +</screen> + + <para> + In a Secure Boot environment, the configuration file must specify that the <application>shim</application> utility be downloaded rather than the GRUB image. No other file can be downloaded via <command>tftp</command> in Secure Boot mode. <application>shim</application> is specified using the <filename>filename</filename> option in IPv4 configurations and the <filename>bootfile-url</filename> option in IPv6 configurations. + </para> + + <para> + Once the <application>shim</application> utility is downloaded and validated, it will automatically download the GRUB image. This image must be named either <filename>grub.efi</filename> or <filename>grubx64.efi</filename> and be available at the same location as <application>shim</application> and be accessible by <command>tftp</command>. + </para> + + <para> + The <application>shim-signed</application> package is available in the Fedora yum repository. For more information on Secure Boot, refer to the <citetitle>Fedora UEFI Secure Boot Guide</citetitle>. + </para> + </step> <step>

11 years, 4 months

1
0
0 / 0

[install-guide] Added new fedup commands

by Jack Reed

commit b7088a3c7d5bcb9f78918f4b9b3ff78b4beecf98 Author: Jack Reed <jreed(a)redhat.com> Date: Thu Jan 10 16:00:27 2013 +1000 Added new fedup commands en-US/Upgrading-common-procedure-1.xml | 27 +++++++++++++++++++++++++-- 1 files changed, 25 insertions(+), 2 deletions(-) --- diff --git a/en-US/Upgrading-common-procedure-1.xml b/en-US/Upgrading-common-procedure-1.xml index 148478e..2af66b2 100644 --- a/en-US/Upgrading-common-procedure-1.xml +++ b/en-US/Upgrading-common-procedure-1.xml @@ -12,12 +12,35 @@ </step> <step> <para> - To run <application>fedup</application>, type <command>fedup-cli</command> at the command line as root and press <keycap>Enter</keycap>. + The command to run <application>fedup</application> will depend on where you choose to source packages from. Run one of the following commands as root and press <keycap>Enter</keycap>: + </para> + <itemizedlist> + <listitem> + <para> + To upgrade using a network source: + </para> +<screen><command>sudo fedup --network 18 --debuglog fedupdebug.log</command></screen> + </listitem> + <listitem> + <para> + To upgrade using a Fedora &PRODVER; ISO file you have downloaded: + </para> +<screen><command>sudo fedup --iso <replaceable>/path/to/isofile</replaceable>.iso --debuglog=fedupdebug.log </command></screen> + </listitem> + <listitem> + <para> + To upgrade using a mounted storage device such as optical or USB media: + </para> +<screen><command>sudo fedup --device <replaceable>/path/to/mountpoint</replaceable> --debuglog=fedupdebug.log </command></screen> + </listitem> + </itemizedlist> + <para> + If the system you are updating has network access, the latest updates will also be installed regardless of which package source you specify. </para> </step> <step> <para> - If <command>fedup-cli</command> runs successfully without errors, reboot your system. + If <command>fedup</command> runs successfully without errors, reboot your system. </para> </step> <step>

11 years, 4 months

1
0
0 / 0

[release-notes/f18: 22/22] Merge branch 'master' into f18

by Nick Bebout

commit 24c715ed71c531b61c198d6c9811b73c20c37552 Merge: a459a33 32c882c Author: Nick Bebout <nb(a)fedoraproject.org> Date: Tue Jan 8 23:19:55 2013 -0600 Merge branch 'master' into f18 Conflicts: en-US/Revision_History.xml .tx/config | 1 - en-US/Boot.xml | 8 +++--- en-US/Cloud.xml | 6 ---- en-US/Desktop.xml | 16 ++++++++--- en-US/Development.xml | 7 ++++- en-US/File_Systems.xml | 2 +- en-US/I18n.xml | 14 ++++++++-- en-US/Installation.xml | 59 ++++++++++++++++++++++++++++++++---------- en-US/Networking.xml | 2 +- en-US/Revision_History.xml | 7 +++++ en-US/Virtualization.xml | 61 +++---------------------------------------- en-US/Web_Servers.xml | 2 +- 12 files changed, 93 insertions(+), 92 deletions(-) --- diff --cc en-US/Revision_History.xml index fb85df3,f85542b..44f2ddc --- a/en-US/Revision_History.xml +++ b/en-US/Revision_History.xml @@@ -8,13 -8,13 +8,20 @@@ <simpara> <revhistory> <revision> + <revnumber>18.0</revnumber> + <date>Tue Jan 8 2013</date> + <revdescription> + <simplelist> + <member>Revision for F18 final</member> + </simplelist> + </revdescription> + <revnumber>17.98</revnumber> + <date>Wed Nov 7 2012</date> + <revdescription> + <simplelist> + <member>Prepare for Fedora 18 Beta</member> + </simplelist> + </revdescription> </revision> <revision> <revnumber>17.95</revnumber>

11 years, 4 months

1
0
0 / 0

[release-notes/f18: 21/22] Update revision history for F18

by Nick Bebout

commit a459a332a433c46425aa1a02d4603715c342fde2 Author: Nick Bebout <nb(a)fedoraproject.org> Date: Tue Jan 8 23:19:18 2013 -0600 Update revision history for F18 en-US/Revision_History.xml | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) --- diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml index 468e9eb..fb85df3 100644 --- a/en-US/Revision_History.xml +++ b/en-US/Revision_History.xml @@ -8,6 +8,15 @@ <simpara> <revhistory> <revision> + <revnumber>18.0</revnumber> + <date>Tue Jan 8 2013</date> + <revdescription> + <simplelist> + <member>Revision for F18 final</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>17.95</revnumber> <date>Sun Oct 28 2012</date> <revdescription>

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits January 2013