[release-notes] prep Cloud product info
by Pete Travis
commit 6e5c47f09c9e18c1776cba9767f2fc2aceab44f5
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Mon Sep 21 08:36:58 2015 -0500
prep Cloud product info
en-US/Products-Cloud.xml | 58 +++------------------------------------------
1 files changed, 4 insertions(+), 54 deletions(-)
---
diff --git a/en-US/Products-Cloud.xml b/en-US/Products-Cloud.xml
index 6430eef..162f799 100644
--- a/en-US/Products-Cloud.xml
+++ b/en-US/Products-Cloud.xml
@@ -6,7 +6,7 @@
]>
<section id="Products-Cloud">
- <title>Fedora Cloud</title>
+ <title>Fedora Cloud</title>
<para>
Fedora Cloud is the base building block of the Fedora flavors, ready to be deployed on the fly to meet your changing needs. These small images are backed by the vast set of applications and utilities available in the Fedora package repositories.
</para>
@@ -39,35 +39,7 @@
<!-- Official Docker Image -->
-
-
-
-
- <section id="Cloud-smaller">
- <title>Smaller Cloud images</title>
- <para>
- Fedora maintainers have worked to reduce dependencies and streamline packaging to produce effective Cloud images that are 10% smaller than the previous release. Base <systemitem class="filesystem" >qcow2</systemitem> images are under 200MB, so your Fedora Cloud deployments will use minimal storage resources.
- </para>
- <para>
- The reduced size is made possible by these notable changes:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Fedora packages traditionally include upstream-provided documentation for user or administrator reference, as well as license text. Starting with Fedora 21, Fedora package maintainers have begun using a special location for license files, allowing Cloud images to be built with the license while avoiding the extra space consumed by unneeded documentation.
- </para>
- <para>
- Packages which are included in the official Fedora Docker image, and more, now use a special location for license files, <filename class="directory">/usr/share/licenses/</filename>.
- </para>
- </listitem>
- <listitem>
- <para>
- Kernel packages are smaller due to improved packaging, as described in <ulink url="kernel-packaging" />
- </para>
- </listitem>
- </itemizedlist>
- </section>
-
+
<section id="Cloud-adopt">
<title>Converting Cloud instances to Fedora Server</title>
<para>
@@ -81,7 +53,7 @@
<section id="Cloud-ostree">
<title>Atomic Upgrade and Rollback via RPM-OSTree</title>
<para>
- Fedora 23 includes <application>RPM-OSTree</application>, a mechanism used on Fedora Atomic installations to perform atomic upgrades and rollbacks for the entire system (kernel as well as userspace).
+ Fedora 22 includes <application>RPM-OSTree</application>, a mechanism used on Fedora Atomic installations to perform atomic upgrades and rollbacks for the entire system (kernel as well as userspace).
</para>
<para>
Instead of performing a package-by-package installation and upgrade on each client machine, the tooling supports composing" sets of packages on a server side. Clients can then perform atomic upgrades as a tree.
@@ -93,27 +65,5 @@
For additional information about this tool and Fedora Atomic, see the <ulink url="https://fedoraproject.org//wiki/Changes/RpmOstree">Fedora Project Wiki</ulink>.
</para>
</section>
-
- <section id="Cloud-tunir">
- <title>Tunir</title>
- <para>
- Tunir is a very simple CI (Continuous Integration) system written keeping Fedora Cloud images at mind. At the same time it is generic enough to be used by anyone to configure and run tests in their local system. The goal is to have a system which is simple to setup, and easy to maintain.
- </para>
- <para>
- This tool right now can create virtual machines based on cloud images (without needing an actual cloud), or can run the tests in a bare metal box, or it can even create jobs inside Docker containers.
- </para>
- <para>
- Example:
- </para>
- <para>
- <screen><command>sudo tunir --job dockerjob --stateless</command></screen>
- </para>
- <para>
- The above command will run a stateless job named <systemitem>dockerjob</systemitem>, it will not save the result into any database as it is a stateless run.
- </para>
- <para>
- For additional information about this tool, see the <ulink url="http://tunir.rtfd.org/">Tunir Documentation</ulink>.
- </para>
- </section>
-
</section>
+
--
docs-commits mailing list
docs-commits(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/docs-commits@lists.fedoraproject...
8 years, 7 months
[release-notes] Add Cinnamon into the list of spins
by pbokoc
commit 41a8b4ba78da06c6e15c4d88419bf0b6c2faf17e
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Sep 21 15:35:14 2015 +0200
Add Cinnamon into the list of spins
en-US/Products-Spins.xml | 11 +++++++----
1 files changed, 7 insertions(+), 4 deletions(-)
---
diff --git a/en-US/Products-Spins.xml b/en-US/Products-Spins.xml
index 24307f6..2f046b3 100644
--- a/en-US/Products-Spins.xml
+++ b/en-US/Products-Spins.xml
@@ -5,7 +5,7 @@
]>
<section id="Products-Spins">
- <title>Fedora Spins</title>
+ <title>Fedora Spins</title>
<para>
The Fedora Project also produces a number of <literal>Spins</literal> that provide alternative desktop environments, or package sets crafted for specific use cases. <literal>Spins</literal> are live images that you can use to preview a variety of software that Fedora has to offer.
</para>
@@ -35,6 +35,11 @@
</listitem>
-->
<listitem>
+ <para><emphasis>Cinnamon</emphasis></para>
+ <para>A desktop environment based on the Gtk+ 3 toolkit.</para>
+ <para>This spin has been added in Fedora 23; see <xref linkend="desktop-cinnamon" /> for details.</para>
+ </listitem>
+ <listitem>
<para><emphasis>Security</emphasis></para>
<para>Security analysis tools.</para>
</listitem>
@@ -70,7 +75,5 @@
</listitem>
</itemizedlist>
</para>
-
-</section>
-
+</section>
--
docs-commits mailing list
docs-commits(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/docs-commits@lists.fedoraproject...
8 years, 7 months
[release-notes] Clean up Cloud-specific content
by pbokoc
commit d5ff2a1fc423a558aa4d9a8dfe3af503cd404078
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Sep 21 15:23:58 2015 +0200
Clean up Cloud-specific content
en-US/Products-Cloud.xml | 27 ++++++++-------------------
1 files changed, 8 insertions(+), 19 deletions(-)
---
diff --git a/en-US/Products-Cloud.xml b/en-US/Products-Cloud.xml
index 34391f3..6430eef 100644
--- a/en-US/Products-Cloud.xml
+++ b/en-US/Products-Cloud.xml
@@ -6,14 +6,14 @@
]>
<section id="Products-Cloud">
- <title>Fedora Cloud</title>
+ <title>Fedora Cloud</title>
<para>
Fedora Cloud is the base building block of the Fedora flavors, ready to be deployed on the fly to meet your changing needs. These small images are backed by the vast set of applications and utilities available in the Fedora package repositories.
</para>
<para>
Cloud images are available in several varieties:
</para>
-
+
<section id="cloud-base-image">
<title>Cloud Base</title>
<para>
@@ -41,8 +41,8 @@
<!-- Official Docker Image -->
-
-
+
+
<section id="Cloud-smaller">
<title>Smaller Cloud images</title>
<para>
@@ -67,7 +67,7 @@
</listitem>
</itemizedlist>
</section>
-
+
<section id="Cloud-adopt">
<title>Converting Cloud instances to Fedora Server</title>
<para>
@@ -81,7 +81,7 @@
<section id="Cloud-ostree">
<title>Atomic Upgrade and Rollback via RPM-OSTree</title>
<para>
- Fedora 22 includes <application>RPM-OSTree</application>, a mechanism used on Fedora Atomic installations to perform atomic upgrades and rollbacks for the entire system (kernel as well as userspace).
+ Fedora 23 includes <application>RPM-OSTree</application>, a mechanism used on Fedora Atomic installations to perform atomic upgrades and rollbacks for the entire system (kernel as well as userspace).
</para>
<para>
Instead of performing a package-by-package installation and upgrade on each client machine, the tooling supports composing" sets of packages on a server side. Clients can then perform atomic upgrades as a tree.
@@ -89,11 +89,6 @@
<para>
On systems using <application>RPM-OSTree</application>, standard package managers (<application>DNF</application> and <application>Yum</application>) do not work normally; they can only be used in read-only mode.
</para>
- <important>
- <para>
- The version of <application>RPM-OSTree</application> available in the default <systemitem>updates</systemitem> repository and on installation media will not work due to a known issue. To use this tool, enable the <systemitem>updates-testing</systemitem> <application>DNF</application> repository and update the <package>rpm-ostree</package> package.
- </para>
- </important>
<para>
For additional information about this tool and Fedora Atomic, see the <ulink url="https://fedoraproject.org//wiki/Changes/RpmOstree">Fedora Project Wiki</ulink>.
</para>
@@ -104,11 +99,6 @@
<para>
Tunir is a very simple CI (Continuous Integration) system written keeping Fedora Cloud images at mind. At the same time it is generic enough to be used by anyone to configure and run tests in their local system. The goal is to have a system which is simple to setup, and easy to maintain.
</para>
- <important>
- <para>
- This is a Self Contained Change.
- </para>
- </important>
<para>
This tool right now can create virtual machines based on cloud images (without needing an actual cloud), or can run the tests in a bare metal box, or it can even create jobs inside Docker containers.
</para>
@@ -116,10 +106,10 @@
Example:
</para>
<para>
- <command>sudo tunir --job dockerjob --stateless</command>
+ <screen><command>sudo tunir --job dockerjob --stateless</command></screen>
</para>
<para>
- The above command will run a stateless job named "dockerjob", it will not save the result into any database as it is a stateless run.
+ The above command will run a stateless job named <systemitem>dockerjob</systemitem>, it will not save the result into any database as it is a stateless run.
</para>
<para>
For additional information about this tool, see the <ulink url="http://tunir.rtfd.org/">Tunir Documentation</ulink>.
@@ -127,4 +117,3 @@
</section>
</section>
-
--
docs-commits mailing list
docs-commits(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/docs-commits@lists.fedoraproject...
8 years, 7 months
[release-notes] Removing outdated notes from Fedora Products
by pbokoc
commit ed0d175e34ba947285e5cc6651dbe7b4068f613c
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Sep 21 15:22:22 2015 +0200
Removing outdated notes from Fedora Products
en-US/Section-Products.xml | 25 +------------------------
1 files changed, 1 insertions(+), 24 deletions(-)
---
diff --git a/en-US/Section-Products.xml b/en-US/Section-Products.xml
index f86505c..2dd3bfd 100644
--- a/en-US/Section-Products.xml
+++ b/en-US/Section-Products.xml
@@ -29,34 +29,11 @@
<para>
Fedora also offers images and support for an ever-increasing number of ARM devices, both large and small.
</para>
-
- <note>
- <title>fedora-release Packages</title>
- <para>
- 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 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_.27environ...">F21 Common Bugs</ulink> page describes this in detail.
- </para>
- </note>
-
- <note>
- <title>The netinstall and DVD ISOs</title>
- <para>
- The Fedora netinstall ISO, an installation image that allows you to select and download packages at install time, is now available as the Fedora Server netinstall.
- </para>
- <para>
- The DVD installation image is not produced for Fedora 21.
- </para>
- </note>
<xi:include href="Products-Cloud.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Products-Server.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Products-Workstation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Products-Spins.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!--<xi:include href="ARM.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />-->
-
+
</section>
--
docs-commits mailing list
docs-commits(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/docs-commits@lists.fedoraproject...
8 years, 7 months
[release-notes] Cleaning up Server-specific content
by pbokoc
commit 0bcc762152c4df96b247a3086869eb01c68fe352
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Sep 21 15:10:41 2015 +0200
Cleaning up Server-specific content
en-US/Products-Server.xml | 15 ++++-----------
1 files changed, 4 insertions(+), 11 deletions(-)
---
diff --git a/en-US/Products-Server.xml b/en-US/Products-Server.xml
index d4e63e3..7adf6bb 100644
--- a/en-US/Products-Server.xml
+++ b/en-US/Products-Server.xml
@@ -5,8 +5,8 @@
]>
<section id="Products-Server">
- <title>Fedora Server</title>
-
+ <title>Fedora Server</title>
+
<section id="server-roles">
<title>Fedora Server Roles</title>
<para>
@@ -18,13 +18,13 @@
<section id="Framework-for-Server-Role-Deployment">
<title>Framework for Server Role Deployment</title>
<para>
- A new D-Bus service is available, exposing available server roles, and making it possible to deploy, configure and manage them. Appropriate functionality will also be exposed as a command-line utility.
+ A D-Bus service is available, exposing available server roles, and making it possible to deploy, configure and manage them. Appropriate functionality is also be exposed as a command-line utility.
</para>
<para>
<ulink url="https://fedoraproject.org/wiki/Changes/FrameworkForServerRoleDeployment" />
</para>
</section>
-
+
<section id="Domain-Controller-Server-Role">
<title>Domain Controller Server Role</title>
<para>
@@ -86,11 +86,4 @@
</para>
</section>
- <section id="Fedora-Server-XFS">
- <title>XFS as a Default File System</title>
- <para>
- The <systemitem>XFS</systemitem> file system is now used by default when installing Fedora Server. See <xref linkend="sect-file-systems-xfs" /> for details.
- </para>
- </section>
-
</section>
--
docs-commits mailing list
docs-commits(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/docs-commits@lists.fedoraproject...
8 years, 7 months
[release-notes] Cleaning up old content from F22
by pbokoc
commit 43b04ab34aaba6aede6c3a274136b291a35a1afe
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Wed Sep 16 17:24:38 2015 +0200
Cleaning up old content from F22
en-US/Big_Data.xml | 13 ---
en-US/Development_Haskell.xml | 15 +----
en-US/Development_Web.xml | 42 ----------
en-US/File_Systems.xml | 18 -----
en-US/Kernel.xml | 29 +-------
en-US/Networking.xml | 82 +--------------------
en-US/Server_Configuration_Tools.xml | 137 +---------------------------------
en-US/Virtualization.xml | 43 -----------
en-US/Web_Servers.xml | 14 ----
9 files changed, 5 insertions(+), 388 deletions(-)
---
diff --git a/en-US/Big_Data.xml b/en-US/Big_Data.xml
index 8bcd27d..ac66436 100644
--- a/en-US/Big_Data.xml
+++ b/en-US/Big_Data.xml
@@ -7,17 +7,4 @@
<section id="bigdata">
<title>Big Data</title>
<para />
- <section id="bigdata-elasticsearch">
- <title>Elasticsearch</title>
- <para>
- The <application>Elasticsearch</application> indexing server has been integrated into the <systemitem>updates</systemitem> repository in Fedora 22. You can now install this application using <application>DNF</application> instead of relying on the stand-alone upstream installer.
- </para>
- <para>
- <application>Elasticsearch</application> is a distributed, scalable, highly available search and analysis tool built on top of Apache Lucene, available under the Apache 2 license.
- </para>
- <para>
- For information about <application>Elasticsearch</application>, see the <ulink url="https://www.elastic.co/products/elasticsearch">official project website</ulink>.
- </para>
- </section>
-
</section>
diff --git a/en-US/Development_Haskell.xml b/en-US/Development_Haskell.xml
index e32e68c..a3f2fb0 100644
--- a/en-US/Development_Haskell.xml
+++ b/en-US/Development_Haskell.xml
@@ -7,18 +7,5 @@
<section id="sect-Development-Haskell">
<title>Haskell</title>
- <section id="sect-Development-Haskell-GHC">
- <title>GHC 7.8</title>
- <para>
- The <application>GHC</application> Haskell compiler has been updated to version 7.8 in Fedora 22.
- </para>
- <para>
- Fedora packages have been updated and rebuilt with the new <application>GHC</application> version. User packages will require a rebuild as well, and may need code changes before they build with the new version.
- </para>
- <para>
- For full release notes, describing all bug fixes and enhancements, see the <ulink url="https://downloads.haskell.org/~ghc/7.8.4/docs/html/users_guide/index.html">GHC System User's Guide</ulink>. This document contains information about <application>GHC 7.8.1</application> as well as several subsequent bug fix updates, which are also included in Fedora 22.
- </para>
- </section>
+ <para />
</section>
-
-
diff --git a/en-US/Development_Web.xml b/en-US/Development_Web.xml
index a4f0b4d..a2a7998 100644
--- a/en-US/Development_Web.xml
+++ b/en-US/Development_Web.xml
@@ -7,46 +7,4 @@
<section id="Development-web">
<title>Web Development</title>
<para />
- <section id="webdev-django">
- <title>Django 1.8</title>
- <para>
- The latest release of the versatile, extensible web framework <application>Django</application> is available for Fedora 22. The Python-based framework's 1.8 release has been designated as the Django project's second 'long term support release, and will receive security updates for at least three years from release date.
- </para>
- <para>
- Fedora packages that depend on Django have been updated for the latest release. Those working with Django can review the project's thorough documentation to learn about new, deprecated, and removed features.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- New features: <ulink url="https://docs.djangoproject.com/en/dev/releases/1.8/#what-s-new-in-django-1-8" />
- </para>
- </listitem>
- <listitem>
- <para>
- Backwards incompatible changes: <ulink url="https://docs.djangoproject.com/en/dev/releases/1.8/#backwards-incompatibl..." />
- </para>
- </listitem>
- <listitem>
- <para>
- Deprecated features: <ulink url="https://docs.djangoproject.com/en/dev/releases/1.8/#features-deprecated-i..." />
- </para>
- </listitem>
- <listitem>
- <para>
- Removed Features: <ulink url="https://docs.djangoproject.com/en/dev/releases/1.8/#features-removed-in-1-8" />
- </para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section id="webdev-rails">
- <title>Ruby on Rails 4.2</title>
- <para>
- Fedora 22 includes <application>Ruby on Rails</application> 4.2, the latest version of the well-known web application framework written in Ruby. Highlights in this release include Active Job, asynchronous mails, Adequate Record, Web Console and foreign key support. The upstream release notes are at <ulink url="http://guides.rubyonrails.org/4_2_release_notes.html" />
- </para>
- <para>
- Information for developers upgrading existing applications to Ruby on Rails 4.2 can be found in the Upgrading Ruby on Rails guide at <ulink url="http://guides.rubyonrails.org/upgrading_ruby_on_rails.html" />
- </para>
- </section>
-
</section>
diff --git a/en-US/File_Systems.xml b/en-US/File_Systems.xml
index 966456e..ea14097 100644
--- a/en-US/File_Systems.xml
+++ b/en-US/File_Systems.xml
@@ -7,22 +7,4 @@
<section>
<title>File Systems</title>
<para />
-
- <section id="sect-file-systems-xfs">
- <title>XFS as a Default File System for Fedora Server</title>
- <para>
- The Fedora Server variant of Fedora 22 now uses the <systemitem>XFS</systemitem> file system by default. Other variants (Workstation, Cloud) continue to use <systemitem>ext4</systemitem> as a default; this can be changed during the installation.
- </para>
- <para>
- <systemitem>XFS</systemitem> is a highly scalable, high-performance file system that supports file systems up to 16 exabytes (approximately 16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes), and directory structures containing tens of millions of entries. <systemitem>XFS</systemitem> also supports metadata journaling, which facilitates quicker crash recovery. The maximum supported size of a single <systemitem>XFS</systemitem> file system is 500 TB (the limit for <systemitem>ext4</systemitem> is 50 TB).
- </para>
- <important>
- <para>
- The size of an <systemitem>XFS</systemitem> file system can not be reduced after it is created - it can only be made bigger, not smaller. Use <systemitem>ext4</systemitem> if you require the ability to shrink the file system at any point after the installation.
- </para>
- </important>
- </section>
-
</section>
-
-
diff --git a/en-US/Kernel.xml b/en-US/Kernel.xml
index b032939..92247d1 100644
--- a/en-US/Kernel.xml
+++ b/en-US/Kernel.xml
@@ -11,35 +11,10 @@
</indexterm>
<indexterm>
<primary>Linux kernel</primary>
- </indexterm>
+ </indexterm>
<para>
Fedora &PRODVER; features the &KERNEL; kernel.
</para>
- <section id="kernel-packaging">
- <title>Modular Kernel Packaging</title>
- <para>
- The <package>kernel</package> package is now a meta package that pulls in <package>kernel-core</package> and <package>kernel-modules</package>. The <package>kernel-core</package> package is smaller than a full package and is well-suited for virtualized environments. By optionally uninstalling <package>kernel-modules</package>, cloud image size can be reduced.
- </para>
- <para>
- The <package>kernel-modules</package> package should be included when Fedora is installed on real hardware.
- </para>
- <para>
- Fedora's initramfs is configured to include only drivers required for your system, allowing you to boot Fedora faster. A single, fully featured initramfs is provided under a <literal>Rescue</literal> boot entry in the GRUB menu to allow use after hardware changes. To recreate initramfs after hardware or driver changes, use the rescue boot option and run the command <command>dracut --regenerate-all</command>.
- </para>
- <important>
- <title>Initramfs Changes</title>
- <para>
- Please note, that a new initramfs is only automatically generated by the <package>kernel-core</package> package but not the <package>kernel-modules</package> package. If you only installed <package>kernel-core</package> at first and install <package>kernel-modules</package> at a later point in time, you need to create a new initramfs manually using dracut, if any of the newly installed modules has become critical for your system's boot up.
- </para>
- <para>
- The <command>dracut</command> utility is used to create the initramfs on Fedora. To regenerate an initramfs for all installed kernels, use the following command:
- </para>
- <screen>
- <prompt>#</prompt> <command>dracut --regenerate-all</command>
- </screen>
- </important>
- </section>
+
</section>
-
-
diff --git a/en-US/Networking.xml b/en-US/Networking.xml
index 8d67d92..9669481 100644
--- a/en-US/Networking.xml
+++ b/en-US/Networking.xml
@@ -4,87 +4,7 @@
%BOOK_ENTITIES;
]>
-<section id="networking">
+<section id="networking">
<title>Networking</title>
<para />
- <section id="networking-BIND">
- <title>BIND</title>
- <para>BIND has been updated to the latest major release 9.10. This release comes with new features, some of which are listed below.</para>
- <itemizedlist>
- <listitem>
- <para>New zone file format, "map", stores zone data in a format that can be mapped directly into memory, allowing significantly faster zone loading.</para>
- </listitem>
- <listitem>
- <para>New tool "delv" (domain entity lookup and validation) with dig-like semantics for looking up DNS data and performing internal DNSSEC validation has been added.</para>
- </listitem>
- <listitem>
- <para>New "prefetch" option improving the recursive resolver performance has been added.</para>
- </listitem>
- <listitem>
- <para>Improved EDNS processing allowing better resolver performance.</para>
- </listitem>
- <listitem>
- <para>Substantial improvements have been made in response-policy zone (RPZ) performance.</para>
- </listitem>
- <listitem>
- <para>ACLs can now be specified based on geographic location using the MaxMind GeoIP databases.</para>
- </listitem>
- <listitem>
- <para>The statistics channel can now provide data in JSON format as well as XML.</para>
- </listitem>
- <listitem>
- <para>The new "in-view" zone option allows zone data to be shared between views, so that multiple views can serve the same zones authoritatively without storing multiple copies in memory.</para>
- </listitem>
- <listitem>
- <para>Native PKCS#11 API has been added.</para>
- </listitem>
- <listitem>
- <para>New tool "named-rrchecker" can be used to check the syntax of individual resource records.</para>
- </listitem>
- <listitem>
- <para>New tool "dnssec-importkey" allows "offline" DNSSEC keys.</para>
- </listitem>
- <listitem>
- <para>Network interfaces are re-scanned automatically whenever they change.</para>
- </listitem>
- <listitem>
- <para>New "max-zone-ttl" option enforces maximum TTLs for zones.</para>
- </listitem>
- <listitem>
- <para>Multiple DLZ databases can now be configured, and are searched in order to find one that can answer an incoming query.</para>
- </listitem>
- <listitem>
- <para>"named-checkzone" and "named-compilezone" can now read journal files.</para>
- </listitem>
- </itemizedlist>
- <para>This release also includes feature changes, some of which are listed below.</para>
- <itemizedlist>
- <listitem>
- <para>The version 3 XML schema for the statistics channel, including new statistics and a flattened XML tree for faster parsing, is no longer optional.</para>
- </listitem>
- <listitem>
- <para>The option "named" now listens on IPv6 as well as IPv4 interfaces by default.</para>
- </listitem>
- <listitem>
- <para>The internal and export versions of the BIND libraries have been unified so that external library clients can use the same libraries as BIND itself.</para>
- </listitem>
- <listitem>
- <para>The default setting for the -U option has been adjusted to improve performance.</para>
- </listitem>
- <listitem>
- <para>Adaptive mutex locks are now used on systems which support them.</para>
- </listitem>
- <listitem>
- <para>The option "rndc flushtree" now flushes matching records from the address database and bad cache as well as the DNS cache.</para>
- </listitem>
- <listitem>
- <para>The isc_bitstring API is no longer used and has been removed from the libisc library.</para>
- </listitem>
- <listitem>
- <para>The timestamps included in RRSIG records can now be read as integers indicating the number of seconds since the UNIX epoch, in addition to being read as formatted dates in YYYYMMDDHHMMSS format.</para>
- </listitem>
- </itemizedlist>
- <para>For more information about the release, go read the BIND 9.10 Release Notes at <ulink url="http://ftp.isc.org/isc/bind9/9.10.0-P2/RELEASE-NOTES-BIND-9.10.0-P2.txt">http://ftp.isc.org/isc/bind9/9.10.0-P2/RELEASE-NOTES-BIND-9.10.0-P2.txt</ulink>.</para>
- </section>
-
</section>
diff --git a/en-US/Server_Configuration_Tools.xml b/en-US/Server_Configuration_Tools.xml
index 6ceb0da..c4580a0 100644
--- a/en-US/Server_Configuration_Tools.xml
+++ b/en-US/Server_Configuration_Tools.xml
@@ -7,140 +7,5 @@
<section>
<title>Server Configuration Tools</title>
<para />
- <section id="dnf" >
- <title>Yum replaced by DNF</title>
- <para>
- The <package>yum</package> package manager has been replaced in Fedora 22 by its successor, <package>dnf</package>. The yum fork has been available in Fedora for testing since Fedora 18, and is now the default command line package manager.
- </para>
- <para>
- Most dnf commands use directives that are familiar to yum users, and it uses the same RPM package repositories. Behind the scenes, dnf uses an improved dependency solver, <package>hawkey</package>, along with <package>librepo</package> for repository operations and <package>libcomps</package> for package groups.
- </para>
- <para>
- The <command>/usr/bin/yum</command> command will redirect to <command>/usr/bin/dnf</command> and print a warning about the redirection. The legacy yum package manager can be manually installed; the legacy command line utility has been renamed to <command>yum-deprecated</command>.
- </para>
- <para>
- Read more about using dnf! Consult the upstream documentation at <ulink url="http://dnf.readthedocs.org/en/latest/index.html" />. Extra plugins are documented at <ulink url="https://rpm-software-management.github.io/dnf-plugins-extras/index.htm" />
- </para>
- <para>
- The behavior of dnf differs from yum in some areas:
- </para>
- <section id="dnf_skip-broken_best">
- <title>Updates that don't work are skipped</title>
- <para>
- If a portion of a transaction is not viable, dnf will automatically exclude it and transparently continue with the portions that will work. For example, if a package has unmet dependencies during a <command>dnf update</command> action, that package will not be updated, but others will. This is similar to yum's <option>--skip-broken</option> directive, but evaluates the impact of the problem against the entire transaction. Because this is the default behavior, there is no <option>--skip-broken</option> switch for dnf.
- </para>
- <para>
- To reveal details about a problematic package direction, you can use the <option>--best</option> option. <command>dnf update --best</command> will force dnf to resolve the transaction using the latest versions of involved packages, and report any problems instead of skipping them. This is equivalent to yum's behavior without <option>--skip-broken</option>.
- </para>
- </section>
-
- <section id="dnf_repo-disable">
- <title>Repos that don't work are skipped</title>
- <para>
- If a configured and enabled repository does not respond, <package>dnf</package> will skip it and continue the transaction with the available repos. This differs from yum, which would immediately stop if a repository was not available.
- </para>
- </section>
- <section id="dnf_update-upgrade">
- <title>Update and Upgrade are the same</title>
- <para>
- The commands <command>dnf update</command> and <command>dnf upgrade</command> are equivalent. This differs from yum, where <command>yum upgrade</command> would have the same effect as <command>yum update --obsoletes</command>, and take obsolete packages into account.
- <!-- what does dnf do with obsoletes? -->
- </para>
- </section>
- <section id="dnf_upgrade-requirements">
- <title>Dependencies are not upgraded on package installation</title>
- <para>
- When installing a new package, previously installed dependencies will not be upgraded. Yum offered an option for this behavior, <option>upgrade_requirements_on_install</option>. To upgrade with dnf, use <command>dnf update</command>.
- </para>
- <para>
- If dnf reports that dependencies on installed packages are unmet while installing a new package, update the dependent packages before trying again.
- </para>
- </section>
- <section id='dnf_clean-on-remove'>
- <title>Clean on remove</title>
- <para>
- When removing a package, dnf will automatically remove any dependent packages that were not explicitly installed by the user. If a package was independently installed, it won't be uninstalled this way. Only packages installed as dependencies are removed.
- </para>
- <para>
- This behavior is configured by the <option>clean_requirements_on_remove</option> option in <filename>/etc/dnf/dnf.conf</filename>
- </para>
- </section>
- <section id="dnf_cache-refresh">
- <title>Repo cache refresh schedule</title>
- <para>
- By default, dnf will check for updates in configured repositories hourly, starting ten minutes after the system boots. The action is controlled by a systemd timer unit, <filename>/usr/lib/systemd/system/dnf-makecache.timer</filename>.
- </para>
- <para>
- To adjust this, copy the timer file to <filename>/etc/systemd/system/dnf-makecache.timer</filename> and edit it.
- </para>
- <para>
- Alternatively, setting the <option>metadata_timer_sync</option> in <filename>/etc/dnf/dnf.conf</filename> to a number of seconds configures the minimum number of seconds between makecache operations. If the timer has not expired, <command>dnf makecache</command> will exit immediately.
- </para>
- <para>
- dnf will also honor the metadata_expire option set in individual repo configs, and refresh repo metadata at runtime if it is too old. This option is described in <command>man yum.conf</command>.
- </para>
- </section>
- <section id="dnf_repository-packages" >
- <title>Repository Actions</title>
- <para>
- The <literal>repository-packages</literal> directive can be used to search for or get info about packages in a specific repository, list installed packages from that repository, and more. This simplifies operations that would have required use of <option>--excluderepo</option> and <option>--includerepo</option> options with yum, and is especially useful for managing similar packages from different repositories.
- </para>
- <!-- example? -->
- </section>
- <section id="dnf_provies-requires">
- <title>Listing dependencies</title>
- <para>
- To find out what package supplies a particular provide, use the <command>dnf provides <replaceable>foo</replaceable></command> command. This replaces <command>yum resolvedep <replaceable>foo</replaceable></command>.
- </para>
- <para>
- To list the dependencies of a package, use <command>dnf repoquery --requires <replaceable>foo</replaceable></command>. This replaces <command>yum deplist foo</command>.
- </para>
- </section>
- <section id="dnf_kernels">
- <title>dnf will remove kernels</title>
- <para>
- <package>kernel</package> packages are not protected by dnf. Unlike with yum, you can remove all kernel packages, including the running package, if you direct it to. Be cautious with removing kernels, and specify the full version and release when removing them for best results.
- </para>
- </section>
- <section id="dnf_replace-swap-shell">
- <title>Replacing packages</title>
- <para>
- When a system requires the capabilities of a package you want to replace, use the <option>--allowerasing</option> option. For example, <command>dnf --allowerasing mariadb</command> will allow you to replace mysql with mariadb, without disrupting packages that require capabilities provided by both packages. This replaces <command>yum shell</command> and <command>yum swap</command> functionality.
- </para>
- </section>
- <section id="dnf_replace-langpacks">
- <title>DNF Langpacks Plug-in</title>
- <para>
- DNF supports installing language packs using the <systemitem>dnf-langpacks</systemitem> plug-in, which is expected to work identically to the older <systemitem>yum-langpacks</systemitem> plug-in. See <!--<xref linkend="sect-i18n-dnf-langpacks" />--> for details.
- </para>
- </section>
- <section id="dnf_disabled-repositories">
- <title>Support for disabled repositories</title>
- <para>
- The <application>Software</application> tool and <application>PackageKit</application> now support searching for packages in disabled repositories.
- </para>
- <para>
- If a user searches for a package using one of these applications and the package is found in a repository which includes the line <literal>enabled_metadata=1</literal> in its definition, a dialog window will be displayed informing the user that the package has been found, but an additional repository must be enabled before it can be installed.
- </para>
- <para>
- The same message can also inform the user about the reason why the repository is disabled by default.
- </para>
- <para>
- This change allows Fedora remixes to ship pre-configured but disabled repositories for any reason - for example, if said repositories contain non-free software. Fedora itself does not have any such repositories pre-configured; therefore this feature will not be visible on a Fedora 22 installation unless you specifically configure one or more repositories with the <literal>enabled_metadata=1</literal> statement.
- </para>
- </section>
- </section>
- <section id="preupgrade-assistant">
- <title>Preupgrade Assistant</title>
- <para>
- Fedora 22 introduces the Preupgrade Assistant, a diagnostics utility which assesses the system for possible in-place upgrade limitations and provides a report with the analysis results. It is based on a module system, with each module performing a separate test, checking for package removals, incompatible obsoletes, changes in libraries, names changes, or deficiencies in the compatibilities of some configuration files. The Preupgrade Assistant does not modify your system except for storing log files.
- </para>
- <para>
- Data gathered by the Preupgrade Assistant can be used for migrating the system using a Kickstart file. It also provides post-upgrade scripts to finish more complex problems after an in-place upgrade. The preupgrade-assistant-contents package is part of the preupgrade-assistant package and it delivers the set of scripts and plug-ins that are used to assess the system. Every module runs its own test and display an exit code that represents the result of that text (for example <literal>PASS</literal>, <literal>FAIL</literal>, <literal>NEEDS_ACTION</literal>, etc.). Contents can be done by users on the base of the Packaging Guidelines here: <ulink url="http://fedoraproject.org/wiki/Packaging:PreupgradeAssistant"/>. Package owners are responsible for adding a module if it is suitable, for example changes in the MariaDB database between system versions.
- </para>
- <para>
- To install the Preugrade Assistant with all available contents, use the <command>dnf install preupgrade-assistant-*</command> command. You can find information on how to run the Preupgrade Assistant here: <ulink url="https://github.com/phracek/preupgrade-assistant/blob/master/README"/>.
- </para>
-
- </section>
+
</section>
diff --git a/en-US/Virtualization.xml b/en-US/Virtualization.xml
index 66f7d4f..3ea7d91 100644
--- a/en-US/Virtualization.xml
+++ b/en-US/Virtualization.xml
@@ -7,48 +7,5 @@
<section>
<title>Virtualization</title>
<para />
-
- <section id="sect-virtualization-aarch-qemu-kvm">
- <title>AArch64 QEMU/KVM VM Installation with libvirt and virt-manager Support</title>
- <para>
- You may now use <systemitem>libvirt</systemitem> and <systemitem>virt-manager</systemitem> to install a virtual machine on the <systemitem>AArch64</systemitem> (64-bit ARM) architecture with the KVM hypervisor. For specific instructions, see:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://fedoraproject.org/wiki/Architectures/AArch64/Install_with_QEMU">Architectures/AArch64/Install with QEMU</ulink>
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://fedoraproject.org/wiki/QA:Testcase_Virt_AArch64_on_x86">QA:Testcase Virt AArch64 on x86</ulink>
- </para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section id="sect-virtualization-uefi-with-libvirt">
- <title>UEFI VMs Installation with libvirt and virt-manager Support</title>
- <para>
- UEFI installation options are now automatically available if UEFI/OVMF binaries are installed.
- </para>
- <para>
- Instructions for installing virtual machines with UEFI are available at:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://fedoraproject.org/wiki/Using_UEFI_with_QEMU">Using UEFI with QEMU</ulink>
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://fedoraproject.org/wiki/QA:Testcase_Virtualization_UEFI">QA:Testcase Virtualization UEFI</ulink>
- </para>
- </listitem>
- </itemizedlist>
- </section>
</section>
-
-
diff --git a/en-US/Web_Servers.xml b/en-US/Web_Servers.xml
index 808f51e..46ec367 100644
--- a/en-US/Web_Servers.xml
+++ b/en-US/Web_Servers.xml
@@ -8,18 +8,4 @@
<title>Web Servers</title>
<para />
- <section id="sect-web-servers-ipsilon">
- <title>Ipsilon</title>
- <para>
- The <application>Ipsilon</application> identity provider is now included in the Fedora 22 <systemitem>updates</systemitem> repository, allowing this application to be installed using the <application>DNF</application> package manager.
- </para>
- <para>
- <application>Ipsilon</application> is a server and a toolkit to configure Apache-based Service Providers. The server is a pluggable <systemitem>mod_wsgi</systemitem> application which provides federated single sign-on to web application. User authentication is always performed against a separate Identity Management system, such as an IPA server, and communication with applications is performed using a federation protocol such as SAML or OpenID.
- </para>
- <para>
- See the <ulink url="https://fedorahosted.org/ipsilon/">project page on Fedorahosted</ulink> for more information.
- </para>
- </section>
-
</section>
-
--
docs-commits mailing list
docs-commits(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/docs-commits@lists.fedoraproject...
8 years, 7 months
[release-notes] Clean up i18n & port content from wiki
by pbokoc
commit 51f62f0bf796ccc06bdfd8a2247adef86987ef21
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Wed Sep 16 15:06:31 2015 +0200
Clean up i18n & port content from wiki
en-US/I18n.xml | 97 ++++++----------------------------
en-US/Server_Configuration_Tools.xml | 9 ++--
2 files changed, 21 insertions(+), 85 deletions(-)
---
diff --git a/en-US/I18n.xml b/en-US/I18n.xml
index d8f354d..a82694d 100644
--- a/en-US/I18n.xml
+++ b/en-US/I18n.xml
@@ -6,100 +6,37 @@
<section id="i18n">
<title>Internationalization</title>
- <note>
- <para>
- The localization effort for Fedora packages has moved from Transifex into <ulink url="https://fedora.zanata.org/">Zanata</ulink>. If you are interested in helping localize Fedora into your language, follow the instructions in the <ulink url="https://fedoraproject.org/wiki/L10N/Translate_on_Zanata">Fedora Localization Guide</ulink>.
- </para>
- </note>
- <section id="sect-i18n-ibus">
- <title>Changes in ibus</title>
- <para>
- <application>ibus</application> is an input method switching framework. It is used to switch beween input languages while logged into a desktop environment. Notable changes for ibus in Fedora 22 include:
- </para>
+
+ <section id="sect-i18n-input-methods">
+ <title>Input Methods</title>
<itemizedlist>
<listitem>
<para>
- A user's ibus input method engines will automatically load when loging into GNOME, allowing them to swith engines without waiting for them to load.
+ <systemitem>ibus-libzhuyin</systemitem> ("New Zhuyin") is now the default Traditional Chinese Zhuyin input method.
</para>
</listitem>
<listitem>
<para>
- Input method engines are hidden on GNOME's lock screen.
+ <systemitem>IBus</systemitem> now supports the format of X11 compose file and loads <filename>$HOME/.XCompose</filename> .
</para>
</listitem>
<listitem>
<para>
- KDE has a special panel icon for ibus. Behind the scenes, this is determined by the <varname>XDG_CURRENT_DESKTOP</varname> environment variable, and will use GtkStatusIcon for supporting desktops and the KDE icon for KDE. If you log in with methods such as <command>startkde</command> instead of with a login manager, you may have to set this variable manually.
+ <systemitem>IBus</systemitem> panel now shows XKB language prefix on the icon per XKB layout instead of <filename>ibus-keyboard.svg</filename> on the <application>KDE Plasma 5</application> desktop environment.
</para>
</listitem>
</itemizedlist>
- </section>
-
- <section id="sect-i18n-glibc-unicode">
- <title>Unicode 7.0 Support in Glibc</title>
- <para>
- An update to <systemitem>Glibc</systemitem> locale data (character map, character width, and <systemitem>LC_CTYPE</systemitem> information) in Fedora 22 enables support for Unicode 7.0. Previous Fedora releases supported Unicode 5.1. This change adds almost 8000 new characters, and also corrects Unicode data for some existing characters per the latest Unicode standard.
- </para>
- <para>
- See the <ulink url="https://raw.githubusercontent.com/pravins/glibc-i18n/master/report-utf8">backward compatibility report</ulink> for information about removed, changed and added characters.
- </para>
- </section>
-
- <section id="sect-i18n-dnf-langpacks">
- <title>DNF Langpacks Plug-in</title>
- <para>
- The <application>DNF</application> package manager, which replaces <application>Yum</application> in Fedora 22, now supports langpack installation through the <package>dnf-langpacks</package> plug-in. The functionality is the same as the <package>yum-langpacks</package> plug-in for <application>Yum</application>.
- </para>
- <note>
- <para>
- Currently, the plug-in can not install langpacks automatically due to a missing <application>DNF</application> feature. See BZ#<ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=1114422">1114422</ulink> for details. Manual installation is possible using the <command>dnf langinstall <replaceable>language</replaceable></command> command, and a list of available languages can be obtained using <command>dnf langavailable</command>.
- </para>
- </note>
- <para>
- To display all available commands for <package>dnf-langpacks</package>, use the <command>dnf --help</command> command. All listed commands beginning with <literal>lang*</literal> are provided by this plug-in.
- </para>
- </section>
+ </section>
- <section id="sect-i18n-default-console-font">
- <title>New Default Console Font</title>
- <para>
- The default console font has been changed to <systemitem>eurlatgr</systemitem> in Fedora 22. The new font has the same typeface as the previously used <systemitem>latarcyrheb-sun16</systemitem> font, but supports a broader range of characters from the Latin and Greek alphabets as well as some commonly used symbols. Users should therefore notice less replacement characters displayed on the console when texts using non-ASCII characters are being displayed.
- </para>
- <para>
- The <systemitem>eurlatgr</systemitem> font does not support Arabic, Cyrillic and Hebrew characters; messages written in these alphabets will continue to use the <systemitem>latarcyrheb-sun16</systemitem> font.
- </para>
- <para>
- Full documentation detailing supported code pages and characters is available in the font's <ulink url="http://git.altlinux.org/people/legion/packages/kbd.git?p=kbd.git;a=blob;f...">README file</ulink>.
- </para>
- </section>
-
- <section id="sect-i18n-minglish-input">
- <title>Minglish Input Method for the Marathi Language</title>
- <para>
- A new input method, "Minglish", is available for the Marathi language in Fedora 22.
- </para>
- <para>
- Minglish allows you to write Marathi text phonetically using an English keyboard layout, based on the English letter pronunciation. For example, the word <literal>अनिश</literal> is formed by typing <literal>anish</literal>, whereas normally you would have to type <literal>FniS</literal> using the traditional phonetic input method, or <literal>anisha</literal> using ITRANS.
- </para>
- <para>
- To enable the new input method on your system, install the <package>m17n-db</package> package using <application>DNF</application>, and then select Minglish in your desktop environment or IBus input preferences.
- </para>
- </section>
-
- <section id="sect-i18n-lohit-odia">
- <title>Lohit2 Odia Font Update</title>
- <para>
- Fedora 22 brings an update to the Lohit Odia font, which is the default font for the Odia language in Fedora.
- </para>
- <para>
- This update aims at cleaning up Odia type tables and make them effective and efficient by following all the standards around font technology. It makes this font follow the latest open type specification and incorporates changes made in language guidelines in recent years.
- </para>
- <para>
- Users should not notice any significant changes apart from some "rare" words now being displayed correctly.
- </para>
- <para>
- See <ulink url="http://pravin-s.blogspot.in/2013/08/project-creating-standard-and-reusabl..." /> for additional information about changes made in the new version. The fonts are provided by the <package>google-noto-sans-oriya-fonts</package> and <package>google-noto-sans-oriya-ui-fonts</package> packages.
- </para>
- </section>
+ <section id="sect-i18n-fonts">
+ <title>Fonts</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Lohit Devanagari, Lohit Telugu and Lohit Bengali have been updated with Unicode 8.0 support.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
</section>
diff --git a/en-US/Server_Configuration_Tools.xml b/en-US/Server_Configuration_Tools.xml
index bae1dcf..6ceb0da 100644
--- a/en-US/Server_Configuration_Tools.xml
+++ b/en-US/Server_Configuration_Tools.xml
@@ -20,7 +20,7 @@
</para>
<para>
Read more about using dnf! Consult the upstream documentation at <ulink url="http://dnf.readthedocs.org/en/latest/index.html" />. Extra plugins are documented at <ulink url="https://rpm-software-management.github.io/dnf-plugins-extras/index.htm" />
- </para>
+ </para>
<para>
The behavior of dnf differs from yum in some areas:
</para>
@@ -111,7 +111,7 @@
<section id="dnf_replace-langpacks">
<title>DNF Langpacks Plug-in</title>
<para>
- DNF supports installing language packs using the <systemitem>dnf-langpacks</systemitem> plug-in, which is expected to work identically to the older <systemitem>yum-langpacks</systemitem> plug-in. See <xref linkend="sect-i18n-dnf-langpacks" /> for details.
+ DNF supports installing language packs using the <systemitem>dnf-langpacks</systemitem> plug-in, which is expected to work identically to the older <systemitem>yum-langpacks</systemitem> plug-in. See <!--<xref linkend="sect-i18n-dnf-langpacks" />--> for details.
</para>
</section>
<section id="dnf_disabled-repositories">
@@ -133,7 +133,7 @@
<section id="preupgrade-assistant">
<title>Preupgrade Assistant</title>
<para>
- Fedora 22 introduces the Preupgrade Assistant, a diagnostics utility which assesses the system for possible in-place upgrade limitations and provides a report with the analysis results. It is based on a module system, with each module performing a separate test, checking for package removals, incompatible obsoletes, changes in libraries, names changes, or deficiencies in the compatibilities of some configuration files. The Preupgrade Assistant does not modify your system except for storing log files.
+ Fedora 22 introduces the Preupgrade Assistant, a diagnostics utility which assesses the system for possible in-place upgrade limitations and provides a report with the analysis results. It is based on a module system, with each module performing a separate test, checking for package removals, incompatible obsoletes, changes in libraries, names changes, or deficiencies in the compatibilities of some configuration files. The Preupgrade Assistant does not modify your system except for storing log files.
</para>
<para>
Data gathered by the Preupgrade Assistant can be used for migrating the system using a Kickstart file. It also provides post-upgrade scripts to finish more complex problems after an in-place upgrade. The preupgrade-assistant-contents package is part of the preupgrade-assistant package and it delivers the set of scripts and plug-ins that are used to assess the system. Every module runs its own test and display an exit code that represents the result of that text (for example <literal>PASS</literal>, <literal>FAIL</literal>, <literal>NEEDS_ACTION</literal>, etc.). Contents can be done by users on the base of the Packaging Guidelines here: <ulink url="http://fedoraproject.org/wiki/Packaging:PreupgradeAssistant"/>. Package owners are responsible for adding a module if it is suitable, for example changes in the MariaDB database between system versions.
@@ -141,7 +141,6 @@
<para>
To install the Preugrade Assistant with all available contents, use the <command>dnf install preupgrade-assistant-*</command> command. You can find information on how to run the Preupgrade Assistant here: <ulink url="https://github.com/phracek/preupgrade-assistant/blob/master/README"/>.
</para>
-
+
</section>
</section>
-
--
docs-commits mailing list
docs-commits(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/docs-commits@lists.fedoraproject...
8 years, 7 months
[release-notes] Clean up Workstation & port content from wiki
by pbokoc
commit 1e7c989150c372552977d6e73f049d0730e100ca
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Wed Sep 16 14:47:01 2015 +0200
Clean up Workstation & port content from wiki
en-US/Products-Workstation.xml | 37 ++++---------------------------------
1 files changed, 4 insertions(+), 33 deletions(-)
---
diff --git a/en-US/Products-Workstation.xml b/en-US/Products-Workstation.xml
index c3ea8ba..64ffb72 100644
--- a/en-US/Products-Workstation.xml
+++ b/en-US/Products-Workstation.xml
@@ -5,46 +5,17 @@
]>
<section id="Products-Workstation">
- <title>Fedora Workstation</title>
+ <title>Fedora Workstation</title>
<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>.
+ Fedora Workstation is a reliable, user-friendly, and powerful operating system for laptops or desktop computers. It supports a wide range of developers, from hobbyists and students to professionals in corporate environments. The workstation edition comes with the Gnome desktop environment which supports a variety of current devices along with a wide array of software that aids quick and easy development.
</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>
+ <title>Updates to GNOME</title>
<para>
- Fedora Workstation developers have provided many enhancements to streamline and improve the GNOME Desktop Environment. Read more about changes to GNOME in Fedora &PRODVER; in <xref linkend="desktop-GNOME" />
- </para>
- </section>
- <section>
- <title>Captive Portal Detection</title>
- <para>
- Fedora Workstation, by default, enables a captive portal detection that requests known content from a trusted Fedora server. If the request is redirected, a window automatically appears for you to interact with the portal's login webpage.
- </para>
- <para>
- To disable this feature, remove <filename>/etc/NetworkManager/conf.d/20-connectivity-fedora.conf</filename>
- </para>
- </section>
- <section>
- <title>Developer oriented firewall</title>
- <para>
- Developers often run test servers that run on high numbered ports, and interconnectivity with many modern consumer devices also requires these ports. The firewall in Fedora Workstation, <systemitem class="daemon">firewalld</systemitem>, is configured to allow these things.
- </para>
- <para>
- Ports numbered under 1024, with the exceptions of <systemitem class="daemon">sshd</systemitem> and clients for <application>samba</application> and <application>DHCPv6</application>, are blocked to prevent access to system services. Ports above 1024, used for user-initiated applications, are open by default.
- </para>
- <para>
- Refer to <ulink url="https://fedoraproject.org/wiki/FirewallD" /> for details on customizing the firewall configuration, or install the <package>firewall-config</package> package for a graphical tool.
- </para>
- </section>
- <section id="Workstation-Nautilus">
- <title>Nautilus Improvements</title>
- <para>
- The Nautilus code base was cleaned up by porting it from the deprecated GtkAction API to GAction. As part of this, the view, gear and app menus are updated to match the current designs. In addition, the problematic floating statusbar and keyboard shortcut for deleting things are solved.
+ Fedora 23 will include the latest version of the GNOME desktop environment: 3.18. See <xref linkend="desktop-GNOME" /> for details.
</para>
</section>
</section>
-
-
--
docs-commits mailing list
docs-commits(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/docs-commits@lists.fedoraproject...
8 years, 7 months
[release-notes] Fixed some language on the python 3 default page
by grundblom
commit 7ef93dc31ecb9babbed5b7ddb9743096b251d14b
Author: Glen Rundblom <grundblom(a)fedoraproject.org>
Date: Tue Sep 15 21:36:31 2015 -0500
Fixed some language on the python 3 default page
en-US/Development.xml | 12 +++++-------
1 files changed, 5 insertions(+), 7 deletions(-)
---
diff --git a/en-US/Development.xml b/en-US/Development.xml
index 8e2e372..d7d2484 100644
--- a/en-US/Development.xml
+++ b/en-US/Development.xml
@@ -236,7 +236,10 @@
</itemizedlist>
</section>
<section id="sect-devel-python3-default">
- <title> Python 3 is now the default</title>
+ <title> Python 3 default interpreter</title>
+ <para>
+ Python 3 is now the default interpreter across all flavors of Fedora (Workstation, Server, and Cloud.)
+ </para>
<para>
Benefits to Fedora
</para>
@@ -246,7 +249,7 @@
Moreover, there is currently no end of support date for Python 3.
</para>
<para>
- Fedora already has Python 3 stack that is parallel to Python 2 stack. There are several benefits of switching the "primary" Python stack:
+ Fedora already has Python 3 stack that is parallel to Python 2 stack. There are several benefits of switching the "primary" Python stack to Python 3:
</para>
<itemizedlist>
<listitem>
@@ -264,11 +267,6 @@
As a distribution that stays close to upstream, Fedora should help Python community go forward by contributing patches and working closely with upstreams to get this accomplished. Thus this Change is meant to benefit not only Fedora, but also broader Python community.
</para>
</listitem>
- <listitem>
- <para>
- Switching to Python 3 as a default will once again push Fedora to stay as close to upstream as possible, highlighting the "Features" and "First" (although, to be honest, Arch Linux was first in this...)
- </para>
- </listitem>
</itemizedlist>
<para>
For more information about Python 3 being the default in Fedora please visit: <ulink url="https://fedoraproject.org/wiki/Changes/Python_3_as_Default#Scope">Python 3 default change in Fedora 23</ulink>
--
docs-commits mailing list
docs-commits(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/docs-commits@lists.fedoraproject...
8 years, 7 months