[release-notes] Fixed spelling error in Development_Tools bug # 1283087
by grundblom
commit a2e01292e39e4dfc062a35c4f81caefb5e711530
Author: Glen Rundblom <grundblom(a)fedoraproject.org>
Date: Wed Nov 18 21:03:33 2015 -0600
Fixed spelling error in Development_Tools bug # 1283087
en-US/Development_Tools.xml | 2 +-
en-US/Revision_History.xml | 18 +++++++++++++++++-
2 files changed, 18 insertions(+), 2 deletions(-)
---
diff --git a/en-US/Development_Tools.xml b/en-US/Development_Tools.xml
index c1a6856..a4d6b61 100644
--- a/en-US/Development_Tools.xml
+++ b/en-US/Development_Tools.xml
@@ -11,7 +11,7 @@
<section id='development-tools-eclipse'>
<title>Eclipse</title>
<para>
- <application>Eclipse</application> in Fedora has had a major update to the Mars (4.5) release. Som enew key features in this release include:
+ <application>Eclipse</application> in Fedora has had a major update to the Mars (4.5) release. Some new key features in this release include:
</para>
<simplelist>
<member>
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index 974a30a..84d7137 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -7,6 +7,22 @@
<title>Revision History</title>
<simpara>
<revhistory>
+<revision>
+ <revnumber>23-05</revnumber>
+ <date>Wednesday, November 18 2015</date>
+ <author>
+ <firstname>Fedora></firstname>
+ <surname>Docs</surname>
+ <email>docs AT lists.fedoraproject.org</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>
+ Fixed spelling error in Development_Tools bug # 1283087
+ </member>
+ </simplelist>
+ </revdescription>
+ </revision>
<revision>
<revnumber>23-04</revnumber>
<date>Wednesday, November 4 2015</date>
@@ -89,4 +105,4 @@
</revision>
</revhistory>
</simpara>
-</appendix>
\ No newline at end of file
+</appendix>
8 years, 5 months
[release-notes] Fixed type-o in perl version of the release notes of F23
by grundblom
commit 03cfee7b7451ac678d32ce65b1414d0b3762b617
Author: Glen Rundblom <grundblom(a)fedoraproject.org>
Date: Thu Nov 12 20:09:25 2015 -0600
Fixed type-o in perl version of the release notes of F23
en-US/Development.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/Development.xml b/en-US/Development.xml
index ff226e7..db7e51c 100644
--- a/en-US/Development.xml
+++ b/en-US/Development.xml
@@ -10,9 +10,9 @@
<para />
<section id="sect-devel-perl-522">
- <title>Perl 5.2.2</title>
+ <title>Perl 5.22</title>
<para>
- The version of Perl in Fedora 23 is now 5.2.2
+ The version of Perl in Fedora 23 is now 5.22
</para>
<para>
New Features:
8 years, 5 months
[fedora-cookbook] master: Fixed my para tags in Networking.xml but had to comment out the preface in Fedora_cookbook.xml because publican keeps saying it is allready defined elsewhere (bc4c114)
by grundblom
Repository : http://git.fedorahosted.org/cgit/docs/fedora-cookbook.git
On branch : master
>---------------------------------------------------------------
commit bc4c11442653b1a50f83a16baba2b482874ecbf2
Author: Glen Rundblom <grundblom(a)fedoraproject.org>
Date: Wed Nov 11 19:53:23 2015 -0600
Fixed my para tags in Networking.xml but had to comment out the preface in Fedora_cookbook.xml because publican keeps saying it is allready defined elsewhere
>---------------------------------------------------------------
en-US/Fedora_Cookbook.xml | 4 ++--
en-US/Networking.xml | 18 +++++++-----------
2 files changed, 9 insertions(+), 13 deletions(-)
diff --git a/en-US/Fedora_Cookbook.xml b/en-US/Fedora_Cookbook.xml
index 4ffc863..2d4d404 100644
--- a/en-US/Fedora_Cookbook.xml
+++ b/en-US/Fedora_Cookbook.xml
@@ -4,8 +4,8 @@
%BOOK_ENTITIES;
]>
<book>
- <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!-- <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<xi:include href="Documenting_Fedora.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Storage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
diff --git a/en-US/Networking.xml b/en-US/Networking.xml
index c25b6b0..d021629 100644
--- a/en-US/Networking.xml
+++ b/en-US/Networking.xml
@@ -1,7 +1,5 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Cookbook.ent">
-%BOOK_ENTITIES;
]>
<chapter id="Networking">
<title>Networking</title>
@@ -12,9 +10,11 @@
Or it can be a reservation. Having a reservation for a client can effectively mimic a static IP. This will give the client the same IP address over and over, without having to manually configure the IP manually on the host.
The advantage to this is less manual configuration on the host.
</para>
- <para>
- <warning> While having a DHCP reservation mimics a static IP, you will be reliant on the DHCP service to be running for your host to keep getting the same IP address.</warning>
- </para>
+ <warning>
+ <para>
+ While having a DHCP reservation mimics a static IP, you will be reliant on the DHCP service to be running for your host to keep getting the same IP address.
+ </para>
+ </warning>
<para>
<emphasis>Static:</emphasis> This way is when you manually assign an IP address into the computer. You may need to do this on a network that has no DHCP server, or the DHCP server will not allow you to have reservations for your computer.
Manually assigning a static IP address has the benefit of making some configurations easier. Especially when configuring a server because in server configuration files
@@ -23,7 +23,6 @@
<para>
If you want to setup your machine with a static IP address there are a few items you need to know:
</para>
- <para>
<itemizedlist>
<listitem>
<para>
@@ -51,7 +50,6 @@
</para>
</listitem>
</itemizedlist>
- </para>
</section>
<section id="How_to_static_command_line">
<title>How to set up a static IP assignment via the command line </title>
@@ -59,7 +57,6 @@
To setup manual an IP address manually, you must first find which network interface, or network card you will be assigning the IP
address to.
</para>
- <para>
<procedure>
<title>Find_Your_Interface</title>
<step>
@@ -107,12 +104,12 @@ IPV6_PEERROUTES=no
In this example, there is a lot of extra lines because this file was auto-created by the system. I marked
lines that are mandatory with #Required.
What is neat in the newer versions of Fedora, is you can set the DNS and Gateway per interface. Please do not have the #Required comments in your config file
- </para>
- <para>
<note>
+ <para>
What is nice about specifying the gateway and DNS at the <emphasis>interface</emphasis> level instead of the <emphasis>system</emphasis> level is so you can have multiple interfaces on a computer
attached to different networks/routes. This is nice especially for a laptop when you want the wired interface to have a special configuration but have the wireless
as general DHCP that attaches to many different networks.
+ </para>
</note>
</para>
</step>
@@ -127,6 +124,5 @@ IPV6_PEERROUTES=no
</para>
</step>
</procedure>
- </para>
</section>
</chapter>
8 years, 5 months
[fedora-cookbook] master: Added content about manual IP assignment in the command line in the Networking.xml file, publican fails to build, but I think that is because I am trying under F23, (bd2585e)
by grundblom
Repository : http://git.fedorahosted.org/cgit/docs/fedora-cookbook.git
On branch : master
>---------------------------------------------------------------
commit bd2585e3f56f2ec41c2564bba6a3a075ab5e77ea
Author: Glen Rundblom <grundblom(a)fedoraproject.org>
Date: Wed Nov 11 16:27:55 2015 -0600
Added content about manual IP assignment in the command line in the Networking.xml file, publican fails to build, but I think that is because I am trying under F23,
>---------------------------------------------------------------
en-US/Networking.xml | 119 ++++++++++++++++++++++++++++++++++++++++++++++++--
1 files changed, 115 insertions(+), 4 deletions(-)
diff --git a/en-US/Networking.xml b/en-US/Networking.xml
index b38cbff..c25b6b0 100644
--- a/en-US/Networking.xml
+++ b/en-US/Networking.xml
@@ -8,14 +8,125 @@
<section id="DHCP_Static">
<title>DHCP VS Static IP assignment</title>
<para>
- DHCP: Dynamic Host protocol: The DHCP server assigns an IP address to the computer. This can be random within the DHCP server's address pool.
+ <emphasis>DHCP:</emphasis> Dynamic Host protocol: The DHCP server assigns an IP address to the computer. This can be random within the DHCP server's address pool.
Or it can be a reservation. Having a reservation for a client can effectively mimic a static IP. This will give the client the same IP address over and over, without having to manually configure the IP manually on the host.
- The advantage to this is less manual configuration on the host
+ The advantage to this is less manual configuration on the host.
</para>
+ <para>
+ <warning> While having a DHCP reservation mimics a static IP, you will be reliant on the DHCP service to be running for your host to keep getting the same IP address.</warning>
+ </para>
<para>
- Static: This way is when you manually assign an IP address into the computer. You may need to do this on a network that has no DHCP server, or the DHCP server will not allow you to have reservations for your computer.
- Manually assigning a static IP address has the benifit of making some configurations easier. Especially when configuring a server because in server configuration files
+ <emphasis>Static:</emphasis> This way is when you manually assign an IP address into the computer. You may need to do this on a network that has no DHCP server, or the DHCP server will not allow you to have reservations for your computer.
+ Manually assigning a static IP address has the benefit of making some configurations easier. Especially when configuring a server because in server configuration files
you can specify the IP address of the server, that you know will be the same every time. An example if configuring MySQL to answer on a specific IP address you have configured on the server.
</para>
+ <para>
+ If you want to setup your machine with a static IP address there are a few items you need to know:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The IP address you want to use
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The sub-net mask of your network sub-net
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Gateway/Router IP of your sub-net
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ DNS servers you will want to use
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Try to make the static address outside of the pool of addresses that the DHCP server assigns
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
</section>
+ <section id="How_to_static_command_line">
+ <title>How to set up a static IP assignment via the command line </title>
+ <para>
+ To setup manual an IP address manually, you must first find which network interface, or network card you will be assigning the IP
+ address to.
+ </para>
+ <para>
+ <procedure>
+ <title>Find_Your_Interface</title>
+ <step>
+ <para>
+ list the contents of directory /etc/sysconfig/network-scripts: <command>ls -l /etc/sysconfig/network-scripts</command>
+ </para>
+ </step>
+ <step>
+ <para>
+ You should see items that start with ifcfg-INTERFACENAME, so usually it is ifcfg-eth0, sometimes it could be something like: ifcfg-enp1s0
+ This is the interface file you will <emphasis>probably</emphasis> be editing
+ </para>
+ </step>
+ <step>
+ <para>
+ open the interface with your text editor of choice, <command> sudo vim /etc/sysconfig/ifcfg-eth0 </command>
+ </para>
+ </step>
+ <step>
+ <para>
+ edit the file with the information you have collected:
+ <programlisting>
+HWADDR=AA:BB:CC:DD:AA:BB #Required
+TYPE=Ethernet #Required
+BOOTPROTO=static #Required
+DEFROUTE=yes #Required
+IPADDR=192.168.1.65 #Required
+NETMASK=255.255.255.0 #Required
+GATEWAY=192.168.1.1 #Required
+IPV4_FAILURE_FATAL=no
+IPV6INIT=no
+IPV6_AUTOCONF=no
+IPV6_DEFROUTE=no
+IPV6_FAILURE_FATAL=no
+NAME=eth0
+UUID=
+ONBOOT=yes #Required
+DNS1=8.8.8.8 #Required
+DNS2=8.8.4.4
+PEERDNS=yes
+PEERROUTES=yes
+IPV6_PEERDNS=no
+IPV6_PEERROUTES=no
+</programlisting>
+ In this example, there is a lot of extra lines because this file was auto-created by the system. I marked
+ lines that are mandatory with #Required.
+ What is neat in the newer versions of Fedora, is you can set the DNS and Gateway per interface. Please do not have the #Required comments in your config file
+ </para>
+ <para>
+ <note>
+ What is nice about specifying the gateway and DNS at the <emphasis>interface</emphasis> level instead of the <emphasis>system</emphasis> level is so you can have multiple interfaces on a computer
+ attached to different networks/routes. This is nice especially for a laptop when you want the wired interface to have a special configuration but have the wireless
+ as general DHCP that attaches to many different networks.
+ </note>
+ </para>
+ </step>
+ <step>
+ <para>
+ Save the file
+ </para>
+ </step>
+ <step>
+ <para>
+ Now you need to restart network manager service <command>sudo systemctl restart NetworkManager</command>
+ </para>
+ </step>
+ </procedure>
+ </para>
+ </section>
</chapter>
8 years, 5 months
[install-guide] Removed references to fedup for upgrading Fedora and replaced it with dnf system upgrade with link t
by grundblom
commit 6cc5caeae40ed1d76a98004fe7ed33a5066268e7
Author: Glen Rundblom <grundblom(a)fedoraproject.org>
Date: Wed Nov 11 08:33:36 2015 -0600
Removed references to fedup for upgrading Fedora and replaced it with dnf system upgrade with link to wiki in reference to bug 1277694
en-US/Preparing_for_Installation.xml | 7 +++----
en-US/Upgrading_Your_Current_System.xml | 15 +++------------
2 files changed, 6 insertions(+), 16 deletions(-)
---
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index 8ed2c6b..237d24e 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -8,7 +8,6 @@
<para>
This chapter describes the steps you need take before you begin the installation. Not every step must be strictly followed - for example, if you plan to use the default installation settings, you do not need to gather system information such as disk device labels/UUIDs or network information such as the system's IP address. However, you should still go through this chapter, as it also describes the available types of installation media and how to prepare boot media and installation sources.
</para>
-
<section id="sect-preparing-upgrade-or-install">
<title>Upgrade or Install?</title>
<para>
@@ -16,10 +15,10 @@
</para>
<variablelist>
<varlistentry>
- <term>Automatic upgrade using <application>FedUp</application></term>
+ <term>Automatic upgrade using <application>dnf system upgrade</application></term>
<listitem>
<para>
- The preferred way to upgrade your system is an automatic upgrade using the <application>FedUp</application> utility. For information on performing an automatic upgrade, see <xref linkend="sect-upgrading-fedora-fedup" />.
+ The preferred way to upgrade your system is an automatic upgrade using the <application>dnf system upgrade</application> utility. For information on performing an automatic upgrade, see <ulink url="https://fedoraproject.org/wiki/DNF_system_upgrade">Fedora Wiki dnf system upgrade</ulink>.
</para>
</listitem>
</varlistentry>
@@ -27,7 +26,7 @@
<term>Manual Reinstallation</term>
<listitem>
<para>
- You can upgrade to the latest version of Fedora manually instead of relying on <application>FedUp</application>. This involves booting the installer as if you were performing a clean installation, letting it detect your existing Fedora system, and overwriting the root partition while preserving data on other partitions and volumes. The same process can also be used to reinstall the system, if you need to. For detailed information, see <xref linkend="sect-upgrading-fedora-manual-reinstall" />.
+ You can upgrade to the latest version of Fedora manually instead of relying on <application>dnf system upgrade</application>. This involves booting the installer as if you were performing a clean installation, letting it detect your existing Fedora system, and overwriting the root partition while preserving data on other partitions and volumes. The same process can also be used to reinstall the system, if you need to. For detailed information, see <xref linkend="sect-upgrading-fedora-manual-reinstall" />.
</para>
</listitem>
</varlistentry>
diff --git a/en-US/Upgrading_Your_Current_System.xml b/en-US/Upgrading_Your_Current_System.xml
index 077b13b..d98f48c 100644
--- a/en-US/Upgrading_Your_Current_System.xml
+++ b/en-US/Upgrading_Your_Current_System.xml
@@ -10,10 +10,10 @@
</para>
<variablelist>
<varlistentry>
- <term>Automatic upgrade using <application>FedUp</application></term>
+ <term>Automatic upgrade using <application>dnf system upgrade</application></term>
<listitem>
<para>
- The preferred way to upgrade your system is an automatic upgrade using the <application>FedUp</application> utility. For information on performing an automatic upgrade, see <xref linkend="sect-upgrading-fedora-fedup" />.
+ The preferred way to upgrade your system is an automatic upgrade using the <application>dnf system upgrade</application> utility. For information on performing an automatic upgrade, see <ulink url="https://fedoraproject.org/wiki/DNF_system_upgrade">Fedora Wiki DNF system upgrade</ulink>.
</para>
</listitem>
</varlistentry>
@@ -21,7 +21,7 @@
<term>Manual Reinstallation</term>
<listitem>
<para>
- You can upgrade to the latest version of Fedora manually instead of relying on <application>FedUp</application>. This involves booting the installer as if you were performing a clean installation, letting it detect your existing Fedora system, and overwriting the root partition while preserving data on other partitions and volumes. The same process can also be used to reinstall the system, if you need to. For detailed information, see <xref linkend="sect-upgrading-fedora-manual-reinstall" />.
+ You can upgrade to the latest version of Fedora manually instead of relying on <application>dnf system upgrade</application>. This involves booting the installer as if you were performing a clean installation, letting it detect your existing Fedora system, and overwriting the root partition while preserving data on other partitions and volumes. The same process can also be used to reinstall the system, if you need to. For detailed information, see <xref linkend="sect-upgrading-fedora-manual-reinstall" />.
</para>
</listitem>
</varlistentry>
@@ -31,19 +31,10 @@
Always back up your data before performing an upgrade or reinstalling your system, no matter which method you choose.
</para>
</warning>
-
- <section id="sect-upgrading-fedora-fedup">
- <title>Automatic System Upgrade Using FedUp</title>
- <para>
- Unfortunately, we have not written this chapter yet. In the meantime before we fix this, you can follow the instructions at <ulink url="https://fedoraproject.org/wiki/FedUp" />.
- </para>
- </section>
-
<section id="sect-upgrading-fedora-manual-reinstall">
<title>Manual System Upgrade or Reinstallation</title>
<para>
Unfortunately, we have not written this chapter yet, and there is no dedicated documentation about a manual reinstall on the Wiki, either. In the meantime before we fix this, you can try to start the installation normally (from a boot CD/DVD/USB), select manual partitioning in your installer, and reuse existing partitions instead of destroying them and creating new ones. The instructions at <xref linkend="sect-installation-gui-manual-partitioning" /> should in most cases be easy to adapt for this.
</para>
</section>
-
</chapter>
8 years, 5 months
[release-notes] Created tag 24.00
by Pete Travis
The unsigned tag '24.00' was created.
Tagger: Pete Travis <immanetize(a)fedoraproject.org>
Date: Mon Nov 9 11:02:06 2015 -0600
prerelease f24 content
Changes since the last tag '21.06':
Pete Travis (4):
markup fix
Merge branch 'master' into prerelease
Update prelease branch for F22-rawhide
f24 prerelease
8 years, 5 months
