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/...
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-...
/>
- </para>
- </listitem>
- <listitem>
- <para>
- Backwards incompatible changes: <ulink
url="https://docs.djangoproject.com/en/dev/releases/1.8/#backwards-i...
/>
- </para>
- </listitem>
- <listitem>
- <para>
- Deprecated features: <ulink
url="https://docs.djangoproject.com/en/dev/releases/1.8/#features-de...
/>
- </para>
- </listitem>
- <listitem>
- <para>
- Removed Features: <ulink
url="https://docs.djangoproject.com/en/dev/releases/1.8/#features-re...
/>
- </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....
- </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&quo...;. 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/REA...;.
- </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_wi...
with QEMU</ulink>
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink
url="https://fedoraproject.org/wiki/QA:Testcase_Virt_AArch64_on_x86&...
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&...
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...