rpm-guide rpm-guide-advanced-packaging-en.xml, 1.1, 1.2 rpm-guide-command-reference-en.xml, 1.1, 1.2 rpm-guide-creating-rpms-en.xml, 1.1, 1.2 rpm-guide-customizing-rpm-en.xml, 1.1, 1.2 rpm-guide-dependencies-en.xml, 1.1, 1.2 rpm-guide-development-tools-en.xml, 1.1, 1.2 rpm-guide-extra-packaging-tools-en.xml, 1.1, 1.2 rpm-guide-licensing-en.xml, 1.1, 1.2 rpm-guide-management-software-en.xml, 1.1, 1.2 rpm-guide-online-resources-en.xml, 1.1, 1.2 rpm-guide-other-linuxes-en.xml, 1.1, 1.2 rpm-guide-other-os-en.xm
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/rpm-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20760
Modified Files:
rpm-guide-advanced-packaging-en.xml
rpm-guide-command-reference-en.xml
rpm-guide-creating-rpms-en.xml
rpm-guide-customizing-rpm-en.xml rpm-guide-dependencies-en.xml
rpm-guide-development-tools-en.xml
rpm-guide-extra-packaging-tools-en.xml
rpm-guide-licensing-en.xml
rpm-guide-management-software-en.xml
rpm-guide-online-resources-en.xml
rpm-guide-other-linuxes-en.xml rpm-guide-other-os-en.xml
rpm-guide-package-structure-en.xml
rpm-guide-packaging-guidelines-en.xml
rpm-guide-programming-c-en.xml
rpm-guide-programming-perl-en.xml
rpm-guide-programming-python-en.xml
rpm-guide-rpm-evolution-en.xml rpm-guide-rpm-overview-en.xml
rpm-guide-rpmbuild-en.xml rpm-guide-scripting-en.xml
rpm-guide-specfile-syntax-en.xml rpm-guide-specfiles-en.xml
rpm-guide-transactions-en.xml rpm-guide-using-rpm-db-en.xml
rpm-guide-using-rpm-en.xml
Log Message:
Fixed chapter headings and intros
Index: rpm-guide-advanced-packaging-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-advanced-packaging-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-advanced-packaging-en.xml 4 Oct 2005 01:44:20 -0000 1.1
+++ rpm-guide-advanced-packaging-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,44 +1,42 @@
-<!-- $Id: -->
-<chapter id="ch-advanced-packaging">
-<title>Advanced RPM Packaging</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Defining package dependency information
- </para>
-
- <para>
- *Setting triggers
- </para>
-
- <para>
- *Writing verification scripts
- </para>
-
- <para>
- *Creating subpackages
- </para>
-
- <para>
- *Creating relocatable packages
- </para>
+<!-- $Id: -->
+<chapter id="ch-advanced-packaging">
+ <title>Advanced RPM Packaging</title>
<para>
- *Defining conditional builds
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Defining package dependency information
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Setting triggers
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Writing verification scripts
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Creating subpackages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Creating relocatable packages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Defining conditional builds
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
The previous chapter introduced the RPM spec file, which controls
how RPM packages are built and installed. This chapter delves into
@@ -46,7 +44,6 @@
making relocatable packages, starting with how to specify package
dependencies.
</para>
-
<sect1>
<title>Defining Package Dependencies</title>
<para>
@@ -416,7 +413,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Setting Triggers</title>
<para>
@@ -859,7 +855,6 @@
chmod 0400 /var/ftp/bin/bin.md5
</para>
</sect1>
-
<sect1>
<title>Writing Verification Scripts</title>
<para>
@@ -906,7 +901,6 @@
See Chapter 5 for more on package verification.
</para>
</sect1>
-
<sect1>
<title>Creating Subpackages</title>
<para>
@@ -1198,7 +1192,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Creating Relocatable Packages</title>
<para>
@@ -1341,7 +1334,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Defining Conditional Builds</title>
<para>
@@ -1653,7 +1645,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -1721,6 +1712,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-command-reference-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-command-reference-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-command-reference-en.xml 4 Oct 2005 01:45:44 -0000 1.1
+++ rpm-guide-command-reference-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,24 +1,26 @@
-<!-- $Id: -->
-<chapter id="ch-command-reference">
-<title>RPM Command Reference</title>
-
- <para>
- In This Appendix
- </para>
-
- <para>
- *rpm command
- </para>
+<!-- $Id: -->
+<chapter id="ch-command-reference">
+ <title>RPM Command Reference</title>
<para>
- *rpmbuild command
+ This appendix covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ rpm command
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ rpmbuild command
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
This appendix covers the syntax of the command-line options for the
rpm and rpmbuild commands.
</para>
-
<sect1>
<title>The rpm Command</title>
<para>
@@ -1704,7 +1706,6 @@
</informaltable>
</sect2>
</sect1>
-
<sect1>
<title>The rpmbuild Command</title>
<para>
@@ -2307,6 +2308,7 @@
</sect2>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
@@ -2314,4 +2316,3 @@
fill-column: 72
End:
-->
-
Index: rpm-guide-creating-rpms-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-creating-rpms-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-creating-rpms-en.xml 4 Oct 2005 01:48:20 -0000 1.1
+++ rpm-guide-creating-rpms-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,44 +1,42 @@
-<!-- $Id: -->
-<chapter id="ch-creating-rpms">
-<title>Creating RPMs: An Overview</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Preparing to build RPMs
- </para>
-
- <para>
- *Planning for RPMs
- </para>
-
- <para>
- *Explaining the build process
- </para>
-
- <para>
- *Using build files
- </para>
-
- <para>
- *Seeing the results
- </para>
+<!-- $Id: -->
+<chapter id="ch-creating-rpms">
+ <title>Creating RPMs: An Overview</title>
<para>
- *Verifying your RPMs
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Preparing to build RPMs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Planning for RPMs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Explaining the build process
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Using build files
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Seeing the results
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Verifying your RPMs
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
Thus far in this book, all the commands presented have been used to
manage or query packages. With this chapter, though, you start
@@ -47,7 +45,6 @@
use, if only for the ease of management that the RPM system
provides.
</para>
-
<para>
Creating RPMs allows you to create a consistent set of applications
for use on all systems in your organization and easily manage those
@@ -56,7 +53,6 @@
customize for your environment. Making RPMs of the customized
applications reduces work and makes the customizations consistent.
</para>
-
<para>
This chapter introduces the RPM system from the point of view of
creating RPMs and demonstrates the steps and planning necessary to
@@ -64,7 +60,6 @@
RPM-building topics covered in depth in the remaining chapters in
this part.
</para>
-
<sect1>
<title>Preparing to Build RPMs</title>
<para>
@@ -600,7 +595,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Building RPMs</title>
<para>
@@ -1555,7 +1549,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Verifying Your RPMS</title>
<para>
@@ -1647,7 +1640,6 @@
for more on the -V option.
</para>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -1674,6 +1666,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-customizing-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-customizing-rpm-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-customizing-rpm-en.xml 4 Oct 2005 01:48:57 -0000 1.1
+++ rpm-guide-customizing-rpm-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,32 +1,27 @@
-<!-- $Id: -->
-<chapter id="ch-customizing-rpm">
-<title>Customizing RPM Behavior</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Defining RPM macros
- </para>
-
- <para>
- *Configuring RPM settings
- </para>
+<!-- $Id: -->
+<chapter id="ch-customizing-rpm">
+ <title>Customizing RPM Behavior</title>
<para>
- *Adding popt aliases
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Defining RPM macros
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Configuring RPM settings
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Adding popt aliases
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
RPM provides a high degree of customization in the form of basic
settings, such as where your RPM database is located and the path to
@@ -35,7 +30,6 @@
ways to customize RPM behavior: RPM macros, RPM rc settings, and
popt aliases.
</para>
-
<sect1>
<title>Customizing with RPM Macros</title>
<para>
@@ -345,7 +339,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Configuring RPM Settings</title>
<para>
@@ -733,7 +726,6 @@
</sect3>
</sect2>
</sect1>
-
<sect1>
<title>Adding Popt Aliases</title>
<para>
@@ -949,7 +941,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -967,6 +958,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
@@ -974,4 +966,3 @@
fill-column: 72
End:
-->
-
Index: rpm-guide-dependencies-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-dependencies-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-dependencies-en.xml 4 Oct 2005 01:49:40 -0000 1.1
+++ rpm-guide-dependencies-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,42 +1,46 @@
-<!-- $Id: -->
-<chapter id="ch-dependencies">
-<title>Package Dependencies</title>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Understanding dependencies
- </para>
-
- <para>
- *Package capabilities
- </para>
-
- <para>
- *Version dependencies
- </para>
-
- <para>
- *Checking dependencies
- </para>
+<!-- $Id: -->
+<chapter id="ch-dependencies">
+ <title>Package Dependencies</title>
<para>
- *Triggers
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Understanding dependencies
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Package capabilities
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Version dependencies
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Checking dependencies
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Triggers
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
Packages aren���t built in a vacuum. Web applications, for example,
build on system networking libraries, system-encryption libraries,
and system-file input and output libraries.
</para>
-
<para>
This chapter covers dependencies between packages, along with ways
to discover and manage those dependencies.
</para>
-
<sect1>
<title>Understanding the Dependency Concept</title>
<para>
@@ -281,7 +285,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Checking for Dependencies</title>
<para>
@@ -1170,7 +1173,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Triggers</title>
<para>
@@ -1532,7 +1534,6 @@
package changes.
</para>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -1570,6 +1571,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
@@ -1577,4 +1579,3 @@
fill-column: 72
End:
-->
-
Index: rpm-guide-development-tools-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-development-tools-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-development-tools-en.xml 4 Oct 2005 01:50:09 -0000 1.1
+++ rpm-guide-development-tools-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,32 +1,27 @@
-<!-- $Id: -->
-<chapter id="ch-development-tools">
-<title>Linux Text Editors and Development Tools</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Appendix
- </para>
-
- <para>
- *General text editors
- </para>
-
- <para>
- *C-specific tools and integrated development environments
- </para>
+<!-- $Id: -->
+<chapter id="ch-development-tools">
+ <title>Linux Text Editors and Development Tools</title>
<para>
- *Python-specific development tools
+ This appendix covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ General text editors
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ C-specific tools and integrated development environments
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Python-specific development tools
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
Linux includes a number of text editors and integrated development
environments (IDEs), going from plain old text editors all the way
@@ -36,7 +31,6 @@
configuration data, so Linux has always included a number of text
editors.
</para>
-
<para>
This appendix lists a number of tools for those who have not yet set
up an RPM development environment on Linux. Note that choosing an
@@ -46,12 +40,10 @@
out what you have installed on your system and see if that works for
you.
</para>
-
<para>
Note that Internet sites may change or disappear, so you may have to
search to find these tools.
</para>
-
<sect1>
<title>General Text Editors</title>
<para>
@@ -84,7 +76,6 @@
Replace gedit with the editor you choose.
</para>
</sect1>
-
<sect1>
<title>Programming Text Editors</title>
<para>
@@ -115,7 +106,6 @@
www.ibm.com/java/jdk/ and select the IBM Developer Kit for Linux.
</para>
</sect1>
-
<sect1>
<title>Integrated Development Environments for C Programming</title>
<para>
@@ -148,7 +138,6 @@
www.eclipse.org/tools/downloads.html.
</para>
</sect1>
-
<sect1>
<title>Integrated Development Environments for Python Programming</title>
<para>
@@ -205,6 +194,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-extra-packaging-tools-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-extra-packaging-tools-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-extra-packaging-tools-en.xml 4 Oct 2005 01:51:52 -0000 1.1
+++ rpm-guide-extra-packaging-tools-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,28 +1,22 @@
-<!-- $Id: -->
-<chapter id="ch-extra-packaging-tools">
-<title>Supplemental Packaging Software</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Understanding packaging aids
- </para>
+<!-- $Id: -->
+<chapter id="ch-extra-packaging-tools">
+ <title>Supplemental Packaging Software</title>
<para>
- *Manipulating packages
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Understanding packaging aids
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Manipulating packages
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
RPM is intended to make system management easier, both for system
administrators and other users who do all the day-to-day work of
@@ -39,7 +33,6 @@
have less work ahead of them, since they need only concern
themselves with the first step.
</para>
-
<para>
After a packager has prepared an RPM package once, RPM makes the
first step (compilation and configuration) easier when the packager
@@ -56,7 +49,6 @@
same application, but once created, the RPM package takes less time
and effort to keep current than the gzipped tarball requires.
</para>
-
<sect1>
<title>Packaging Aids</title>
<para>
@@ -1452,7 +1444,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -1489,6 +1480,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-licensing-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-licensing-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-licensing-en.xml 4 Oct 2005 01:53:33 -0000 1.1
+++ rpm-guide-licensing-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,16 +1,7 @@
-<!-- $Id: -->
-<chapter id="ch-licensing">
-<title>Licensing RPM</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
+<!-- $Id: -->
+<chapter id="ch-licensing">
+ <title>Licensing RPM</title>
<para>
When incorporating someone else's existing code into your software
project, you should always examine the license of the code
@@ -20,7 +11,6 @@
This is true for commercial code and commercial projects, and it is
equally true for freely licensed code and free software projects.
</para>
-
<para>
RPM itself and most discussed helper applications (rpmlint,
rpm-spec-mode, and so forth) are free software, meaning that the
@@ -28,7 +18,6 @@
these tools are considered open source software, which means the
source code for the applications are also available.
</para>
-
<para>
These facts do not mean that they are unlicensed software, or that
their source code can be used in any desired fashion. RPM and these
@@ -46,9 +35,7 @@
GPL on your project, should you decide to use GPL'ed code in any
commercially licensed project you might undertake).
</para>
-
<para/>
-
<sect1>
<title>The GNU General Public License</title>
<para>
@@ -490,6 +477,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-management-software-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-management-software-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-management-software-en.xml 4 Oct 2005 01:54:10 -0000 1.1
+++ rpm-guide-management-software-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,32 +1,27 @@
-<!-- $Id: -->
-<chapter id="ch-management-software">
-<title>RPM Management Software</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Finding packages in RPM format
- </para>
-
- <para>
- *Graphical tools to manage RPM packages
- </para>
+<!-- $Id: -->
+<chapter id="ch-management-software">
+ <title>RPM Management Software</title>
<para>
- *Extending RPM management with additional tools
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Finding packages in RPM format
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Graphical tools to manage RPM packages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Extending RPM management with additional tools
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
You can find a variety of software packages to ease the work of
managing RPM-based systems. These utilities can help you find a
@@ -38,12 +33,10 @@
with more recent versions or simplification of software installation
by automating installation of any required software dependencies.
</para>
-
<para>
This chapter covers a number of tools for finding packages in RPM
format, as well as tools to help manage the RPMs on your system.
</para>
-
<sect1>
<title>Locating RPMs</title>
<para>
@@ -670,7 +663,6 @@
</sect3>
</sect2>
</sect1>
-
<sect1>
<title>Graphical RPM Management</title>
<para>
@@ -965,7 +957,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Extending RPM Management</title>
<para>
@@ -2074,7 +2065,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -2118,6 +2108,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
@@ -2125,4 +2116,3 @@
fill-column: 72
End:
-->
-
Index: rpm-guide-online-resources-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-online-resources-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-online-resources-en.xml 4 Oct 2005 01:54:38 -0000 1.1
+++ rpm-guide-online-resources-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,33 +1,26 @@
-<!-- $Id: -->
-<chapter id="ch-online-resources">
-<title>RPM Resources</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Appendix
- </para>
-
- <para>
- *Finding RPM sites on the Internet
- </para>
+<!-- $Id: -->
+<chapter id="ch-online-resources">
+ <title>RPM Resources</title>
<para>
- *Accessing RPM newsgroups and mailing lists
+ This appendix covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Finding RPM sites on the Internet
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Accessing RPM newsgroups and mailing lists
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
This appendix covers the material available on the Internet for
working with RPM.
</para>
-
<sect1>
<title>Finding RPM Sites</title>
<para>
@@ -590,7 +583,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Accessing RPM Mailing Lists and Newsgroups</title>
<para>
@@ -613,6 +605,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-other-linuxes-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-other-linuxes-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-other-linuxes-en.xml 4 Oct 2005 01:55:12 -0000 1.1
+++ rpm-guide-other-linuxes-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,67 +1,59 @@
-<!-- $Id: -->
-<chapter id="ch-other-linuxes">
-<title>Using RPM on Non-Red Hat Linuxe</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Dealing with RPM issues on other versions of Linux
- </para>
-
- <para>
- *RPM standardization
- </para>
-
- <para>
- *Working around RPM differences when installing RPMs
- </para>
-
- <para>
- *Working around RPM differences when building RPMs
- </para>
+<!-- $Id: -->
+<chapter id="ch-other-linuxes">
+ <title>Using RPM on Non-Red Hat Linuxes</title>
<para>
- *Dealing with non-RPM-based Linux distributions
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Dealing with RPM issues on other versions of Linux
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ RPM standardization
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Working around RPM differences when installing RPMs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Working around RPM differences when building RPMs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Dealing with non-RPM-based Linux distributions
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
Although its name was originally the Red Hat Package Manager, RPM
has been adopted by most major Linux distributions. With this
adoption, RPM has moved from its Red Hat roots, and RPM now stands
for the RPM Package Manager.
</para>
-
<para>
In addition, the RPM package format is being adopted by the Linux
Standards Base (LSB). The LSB defines a set of standards to help
maintain compatibility for all Linux distributions.
</para>
-
<para>
Cross Reference
</para>
-
<para>
See www.linuxbase.org for more on the LSB.
</para>
-
<para>
This chapter covers differences in how Linux distributions use RPM,
ways to work around these differences, and also tools you can use
for non-RPM distributions.
</para>
-
<sect1>
<title>Troubleshooting RPM Installation Issues</title>
<para>
@@ -307,7 +299,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Handling Problems Building RPMs</title>
<para>
@@ -787,7 +778,6 @@
</sect3>
</sect2>
</sect1>
-
<sect1>
<title>Dealing with Non-RPM-Based Linux Versions</title>
<para>
@@ -816,7 +806,6 @@
<para/>
</sect2>
</sect1>
-
<sect1>
<title>Standardizing RPMs</title>
<para>
@@ -870,7 +859,6 @@
<para/>
</sect2>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -903,6 +891,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-other-os-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-other-os-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-other-os-en.xml 4 Oct 2005 01:55:46 -0000 1.1
+++ rpm-guide-other-os-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,44 +1,42 @@
-<!-- $Id: -->
-<chapter id="ch-other-os">
-<title>RPM on Other Operating Systems</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Running RPM on other operating systems
- </para>
-
- <para>
- *Bootstrapping RPM on other operating systems
- </para>
-
- <para>
- *Setting up the RPM environment
- </para>
-
- <para>
- *Creating non-Linux RPMs
- </para>
-
- <para>
- *Setting up an RPM build environment
- </para>
+<!-- $Id: -->
+<chapter id="ch-other-os">
+ <title>RPM on Other Operating Systems</title>
<para>
- *Cross-building packages
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Running RPM on other operating systems
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Bootstrapping RPM on other operating systems
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Setting up the RPM environment
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Creating non-Linux RPMs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Setting up an RPM build environment
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Cross-building packages
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
RPM was originally designed on Linux and for most of its life has
been a Linux-centric package management system. But most Linux
@@ -46,26 +44,22 @@
operating systems. Linux is, after all, a Unix-workalike operating
system.
</para>
-
<para>
The RPM system is no exception. It has been ported to a number of
operating systems, including quite a few Unix variants. The source
code is freely available, so you can port RPM to other systems as
well.
</para>
-
<para>
This chapter covers running RPM on non-Linux operating systems,
including getting the RPM system in the first place, bootstrapping
an RPM environment, and creating packages for other operating
systems.
</para>
-
<para>
The first step is to get RPM for your system, or port RPM if it
isn���t already available.
</para>
-
<sect1>
<title>Running RPM on Other Operating Systems</title>
<para>
@@ -454,7 +448,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Bootstrapping RPM On Other Operating Systems</title>
<para>
@@ -887,7 +880,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Setting Up the RPM System</title>
<para>
@@ -1359,7 +1351,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Creating Non-Linux RPMS</title>
<para>
@@ -1566,7 +1557,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -1616,6 +1606,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-package-structure-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-package-structure-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-package-structure-en.xml 4 Oct 2005 01:56:31 -0000 1.1
+++ rpm-guide-package-structure-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,32 +1,27 @@
-<!-- $Id: -->
-<chapter id="ch-package-structure">
-<title>RPM Package File Structure</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Appendix
- </para>
-
- <para>
- *RPM package file structure
- </para>
-
- <para>
- *RPM header entry formats
- </para>
+<!-- $Id: -->
+<chapter id="ch-package-structure">
+ <title>RPM Package File Structure</title>
<para>
- *Payload format
+ This appendix covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ RPM package file structure
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ RPM header entry formats
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Payload format
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
This appendix describes the format of RPM package files. You can
combine this information with C, Perl, or Python data structures to
@@ -35,30 +30,24 @@
attempt to access the files directly, as you may inadvertently
damage the RPM file.
</para>
-
<para>
Cross Reference
</para>
-
<para>
Chapters 16, 17, and 18 cover programming with C, Python, and Perl,
respectively.
</para>
-
<para>
The RPM package format described here has been standardized as part
of the Linux Standards Base, or LSB, version 1.3.
</para>
-
<para>
Cross Reference
</para>
-
<para>
The LSB 1.3 section on package file formats is available at
www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB.html#PACKAGEFMT.
</para>
-
<sect1>
<title>The Package File</title>
<para>
@@ -2565,6 +2554,7 @@
</sect2>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-packaging-guidelines-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-packaging-guidelines-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-packaging-guidelines-en.xml 4 Oct 2005 01:57:07 -0000 1.1
+++ rpm-guide-packaging-guidelines-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,28 +1,22 @@
-<!-- $Id: -->
-<chapter id="ch-packaging-guidelines">
-<title>Packaging Guidelines</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Avoiding common mistakes
- </para>
+<!-- $Id: -->
+<chapter id="ch-packaging-guidelines">
+ <title>Packaging Guidelines</title>
<para>
- *Following good practices
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Avoiding common mistakes
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Following good practices
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
RPM is a complex system that helps manage thousands of packages for
a complex operating system. Furthermore, RPM is very, very flexible.
@@ -31,12 +25,10 @@
problems with your RPMs. Following some best practices guidelines
will help you avoid future problems as you release RPM updates.
</para>
-
<para>
This chapter covers ways to avoid common problems as well as
best-practice guidelines for creating your own RPMs.
</para>
-
<sect1>
<title>Avoiding Common Problems</title>
<para>
@@ -282,7 +274,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Following Good Practices</title>
<para>
@@ -652,7 +643,6 @@
</sect3>
</sect2>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -685,6 +675,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-programming-c-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-c-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-programming-c-en.xml 4 Oct 2005 01:57:51 -0000 1.1
+++ rpm-guide-programming-c-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,73 +1,65 @@
-<!-- $Id: -->
-<chapter id="ch-programming-c">
-<title>Programming RPM with C</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Using the RPM C library
- </para>
-
- <para>
- *Setting up a development environment
- </para>
-
- <para>
- *Programming with the RPM C library
- </para>
-
- <para>
- *The power of popt for command-line argument processing
- </para>
+<!-- $Id: -->
+<chapter id="ch-programming-c">
+ <title>Programming RPM with C</title>
<para>
- *Comparing package files to installed packages
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Using the RPM C library
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Setting up a development environment
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Programming with the RPM C library
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The power of <command>popt</command> for command-line argument
+ processing
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Comparing package files to installed packages
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
The RPM C library allows you to perform all the operations of the
rpm command from within your own C or C++ programs.
</para>
-
<para>
The reason is simple: The rpm command was created using the RPM
libraries. These same libraries are available for you to use in your
own programs.
</para>
-
<para>
The rpm command itself is quick and, for the most part, simple. So,
why would you want to write RPM programs?
</para>
-
<para>
There are many reasons, some of which are listed here:
</para>
-
<para>
*Speed: If you need to perform a task on many RPM files such as
verifying a large set of files, then performing the task from one
program will be a lot faster than launching the rpm command for each
file.
</para>
-
<para>
*Custom options: If you need to do something the rpm command doesn't
offer, or doesn't make easy, then you may want to write your own
program.
</para>
-
<para>
*Convenience: If you need to make many packages quickly, with custom
options, your best bet may be to create a program suited for your
@@ -76,7 +68,6 @@
writing RPM shell scripts goes much faster than writing whole
programs.
</para>
-
<para>
*Installation programs: The Windows world has standardized on
graphical installation programs such as InstallShield or
@@ -85,12 +76,10 @@
best of both worlds by writing a graphical installation program on
top of the RPM system.
</para>
-
<para>
*Integration with environments: You may want to better integrate RPM
with a Linux desktop environment such as GNOME or KDE.
</para>
-
<para>
*Working with other languages: This book covers programming RPM with
C, the core language for the library, as well as the Python and Perl
@@ -98,7 +87,6 @@
bind with other languages such as Tcl, Ruby, or even C# (especially
one of the C# implementations for Linux).
</para>
-
<para>
This chapter and the next cover RPM programming. This chapter covers
the RPM C programming library, which provides low-level access to
@@ -108,7 +96,6 @@
your best bet is to try the Python API first. Even so, there is a
lot you can do with the RPM C library.
</para>
-
<sect1>
<title>Programming with the C Library</title>
<para>
@@ -968,7 +955,6 @@
</sect3>
</sect2>
</sect1>
-
<sect1>
<title>The Power of popt</title>
<para>
@@ -2265,7 +2251,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Working with RPM Files</title>
<para>
@@ -2744,7 +2729,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Programming with the RPM Database</title>
<para>
@@ -3083,7 +3067,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Comparing an RPM File to an Installed Package</title>
<para>
@@ -3913,7 +3896,6 @@
jikes Fri 25 Oct 2002 06:49:38 PM CDT
</para>
</sect1>
-
<sect1>
<title>Where to Go from Here</title>
<para>
@@ -3947,7 +3929,6 @@
organization can help you locate the functions you need.
</para>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -3981,6 +3962,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
@@ -3988,4 +3970,3 @@
fill-column: 72
End:
-->
-
Index: rpm-guide-programming-perl-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-perl-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-programming-perl-en.xml 4 Oct 2005 01:58:18 -0000 1.1
+++ rpm-guide-programming-perl-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,37 +1,33 @@
-<!-- $Id: -->
-<chapter id="ch-programming-perl">
-<title>Programming RPM with Perl</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Using the RPM2 module to access information on package files
- </para>
-
- <para>
- *Querying the RPM database from Perl
- </para>
-
- <para>
- *Cross-referencing capabilities by the packages that provide and
- require capabilities
- </para>
+<!-- $Id: -->
+<chapter id="ch-programming-perl">
+ <title>Programming RPM with Perl</title>
<para>
- *Extracting information on packages
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Using the RPM2 module to access information on package files
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Querying the RPM database from Perl
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Cross-referencing capabilities by the packages that provide and
+ require capabilities
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Extracting information on packages
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
Perl is one of the most popular scripting languages. Used by system
administrators, software developers, and a host of other users, Perl
@@ -39,24 +35,20 @@
Perl stands for Practical Extraction and Report Language, or
sometimes Pathologically Eclectic Rubbish Lister.
</para>
-
<para>
Note
</para>
-
<para>
In the same vein, LISP stands for Lots of Irritating Single
Parenthesis and COBOL for Completely Obnoxious Business Oriented
Language.
</para>
-
<para>
I began my book Cross-Platform Perl (John Wiley & Sons, 2000) by
mentioning that when I first started learning Perl, I thought it was
an evil plot. I still do. But it is a very practical evil plot. You
can get a lot of work done with Perl, and quickly.
</para>
-
<para>
Because of a long history of text processing, Perl is especially
popular among system administrators. Perl also supports add-on
@@ -66,30 +58,24 @@
like the Perl syntax script with Perl anyway, because the available
modules save a lot of time.
</para>
-
<para>
Cross Reference
</para>
-
<para>
See search.cpan.org, the Comprehensive Perl Archive Network, for a
listing of many Perl modules.
</para>
-
<para>
This chapter covers working with RPM files and the RPM database
using Perl. You can combine RPM usage with other Perl usage, such as
generating HTML files or downloading RPMs over a network link.
</para>
-
<para>
Cross Reference
</para>
-
<para>
Many of the RPM tools covered in Chapter 8 are written in Perl.
</para>
-
<sect1>
<title>Getting and Using the Perl RPM Modules</title>
<para>
@@ -127,7 +113,6 @@
objects: RPM files and installed packages.
</para>
</sect1>
-
<sect1>
<title>Working with RPM Files</title>
<para>
@@ -355,7 +340,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Programming with the RPM Database</title>
<para>
@@ -1489,7 +1473,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Where to Go from Here</title>
<para>
@@ -1550,7 +1533,6 @@
You can download all these modules from the CPAN site.
</para>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -1580,6 +1562,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-programming-python-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-python-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-guide-programming-python-en.xml 21 Oct 2005 00:20:31 -0000 1.2
+++ rpm-guide-programming-python-en.xml 26 Oct 2005 01:54:11 -0000 1.3
@@ -1,40 +1,37 @@
-<!-- $Id: -->
-<chapter id="ch-rpm-programming-python">
-<title>Programming RPM with Python</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Using the RPM with Python
- </para>
-
- <para>
- *Installing the necessary modules
- </para>
-
- <para>
- *Programming with the RPM database
- </para>
-
- <para>
- *Programming with RPM files
- </para>
+<!-- $Id: -->
+<chapter id="ch-rpm-programming-python">
+ <title>Programming RPM with Python</title>
<para>
- *Installing packages programmatically
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Using the RPM with Python
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Installing the necessary modules
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Programming with the RPM database
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Programming with RPM files
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Installing packages programmatically
+ </para>
+ </listitem>
+ </itemizedlist>
<sect1>
<title>Setting Up a Python Development Environment</title>
<para>
@@ -123,7 +120,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>The Python API Hierarchy</title>
<para>
@@ -251,7 +247,6 @@
version.
</para>
</sect1>
-
<sect1>
<title>Programming with the RPM Database</title>
<para>
@@ -1321,7 +1316,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Reading Package Files</title>
<para>
@@ -1623,7 +1617,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Dependency Comparisons</title>
<para>
@@ -1759,7 +1752,6 @@
a package isn't installed.
</para>
</sect1>
-
<sect1>
<title>Installing and Upgrading Packages</title>
<para>
@@ -3009,7 +3001,6 @@
</sect3>
</sect2>
</sect1>
-
<sect1>
<title>Where to Go from Here</title>
<para>
@@ -3047,7 +3038,6 @@
the Vaults of Parnassus listing of tutorials.
</para>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -3077,6 +3067,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
@@ -3084,4 +3075,3 @@
fill-column: 72
End:
-->
-
Index: rpm-guide-rpm-evolution-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-rpm-evolution-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-rpm-evolution-en.xml 4 Oct 2005 02:00:07 -0000 1.1
+++ rpm-guide-rpm-evolution-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,16 +1,7 @@
-<!-- $Id: -->
-<chapter id="ch-rpm-evolution">
-<title>RPM Feature Evolution</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
+<!-- $Id: -->
+<chapter id="ch-rpm-evolution">
+ <title>RPM Feature Evolution</title>
<para>
Although RPM implementations are largely compatible from version to
version, RPM packagers must remember that RPM is a still-evolving
@@ -25,13 +16,11 @@
considering these revisions of RPM, the main releases of interest
are RPM 2.5, RPM 3.0.5, RPM 4.0.4, and RPM 4.1.
</para>
-
<para>
RPM 2.5 is not widely used anymore; packages should target RPM 2.5
only if the intention is for the RPM package to install using
absolutely all RPM versions.
</para>
-
<para>
RPM 3.0.5 is the final release of the 3.x series of RPM. It was the
release of RPM shipped with Red Hat Linux 6.2 and older releases. It
@@ -39,7 +28,6 @@
distributions use an RPM implementation version based on RPM 3.0.5,
for example. (Red Hat Linux was upgraded to RPM 4 via an errata.)
</para>
-
<para>
RPM 4.0.4 was used with the 7.x releases of Red Hat Linux, and RPM
4.1 first shipped with Red Hat Linux 8.0. Packages produced
@@ -47,7 +35,6 @@
RPM still in use today. Packages produced targeting RPM 4.0.4 or RPM
4.1 will work only with recent RPM implementations.
</para>
-
<para>
RPM 2.5 is the oldest version of RPM that can, by any stretch of the
imagination, still be considered in use. With RPM 2.5, most of the
@@ -57,48 +44,40 @@
also the first version of RPM to use the RPM version 3 RPM file
format.
</para>
-
<para>
RPM 2.5.3 added support for Epochs to the RPM header, implementing
RPMTAG_EPOCH.
</para>
-
<para>
RPM 2.5.4 introduced the %license and %readme file types, which can
be used in the RPM spec file to indicate license and README files.
</para>
-
<para>
RPM 2.5.6 added support for usage of the Epoch: keyword in the RPM
spec file, allowing you to force an Epoch for your package. The
Epoch: keyword replaced the older Serial: keyword, which
semantically behaved similarly.
</para>
-
<para>
RPM 2.5.7 enforced the previously implied standard that the "-"
character should not be used within the Version or Release fields in
the RPM spec file.
</para>
-
<para>
RPM 2.90 introduced support for signing and verifying RPM package
files using GPG, the GNU Privacy Guard.
</para>
-
<para>
RPM 2.91 allowed the usage of Provides: directives that defined
absolute paths to provided files. Prior to RPM 2.91, Provides: could
be used only for listing provided capabilities, not for using
statements like Provides: /path/to/file to indicate provided files.
</para>
-
<para>
RPM 3.0.2 permitted usage of multiple Provides: lines for the first
time, eliminating the need to combine all provided capabilities and
files on the same line in the spec file.
</para>
-
<para>
RPM 3.0.3 added support for versioned dependencies. Prior to RPM
3.0.3, spec files could indicate that a package required another
@@ -106,30 +85,24 @@
indicate the acceptable versions of the required package or which
version of the capability the package provided.
</para>
-
<para>
RPM 3.0.4 introduced CompressedFileNames support to RPM. Prior to
RPM 3.0.4, RPM packaged the absolute paths of all archived files
within the package file. Package file headers contained statements
such as
</para>
-
<para>
fileName #0: /usr/bin/ar
</para>
-
<para>
fileName #1: /usr/bin/as
</para>
-
<para>
fileName #2: /usr/bin/gasp
</para>
-
<para>
fileName #3: /usr/bin/gprof
</para>
-
<para>
With CompressedFileNames support, the RPM package file header
instead stores the directory name, then just the base name of files
@@ -137,31 +110,24 @@
such as the following for a given directory with a number of files
within that directory:
</para>
-
<para>
dirName #0: /usr/bin
</para>
-
<para>
baseName dirIndex
</para>
-
<para>
#0 ar 0
</para>
-
<para>
#1 as 0
</para>
-
<para>
#2 gasp 0
</para>
-
<para>
#3 gprof 0
</para>
-
<para>
Each file entry now holds the file's base name within the directory,
as well as an index number that refers to the directory entry. Since
@@ -169,7 +135,6 @@
CompressedFileNames support results in significant memory savings
when processing packages for installation.
</para>
-
<para>
RPM 3.0.5 added PayloadIsBzip2 support to RPM, allowing the data
payload of RPM package files to be compressed using bzip2 instead of
@@ -181,7 +146,6 @@
version 4 file format packages; packages produced with RPM 3.0.5 can
only be RPM version 3 file format, however.
</para>
-
<para>
RPM 4.0 implemented several significant changes to RPM. RPM 4.0
created package files using RPM version 4 package file format. RPM
@@ -211,12 +175,10 @@
removing the need to provide self-capabilities within the package
spec file.
</para>
-
<para>
RPM 4.0.2 introduced the use of SHA-1 message digests to validate
RPM header regions.
</para>
-
<para>
RPM 4.0.3 added the %dev(type,major,minor) spec file directive,
allowing creation of device nodes. In addition, the %configure spec
@@ -227,7 +189,6 @@
files in RPM version 3 package file format by default, although it
still supports RPM version 4 package file format as well.
</para>
-
<para>
RPM 4.0.4 provided PartialHardlinkSets support. RPM package files
are sometimes created which contain multiple copies of the same
@@ -246,12 +207,10 @@
determined dependencies. In addition, RPM 4.0.4 provides transaction
support for RPM.
</para>
-
<para>
RPM 4.1 adds separate header DSA and RSA signatures, allowing
verification of RPM package headers.
</para>
-
<para>
Finally, when considering the RPM features required by your prepared
package, remember that some required RPM features are specified
Index: rpm-guide-rpm-overview-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-rpm-overview-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-rpm-overview-en.xml 4 Oct 2005 02:00:40 -0000 1.1
+++ rpm-guide-rpm-overview-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,45 +1,38 @@
-<!-- $Id: -->
-<chapter id="ch-rpm-overview">
-<title>RPM Overview</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Understanding the package file
- </para>
-
- <para>
- *Querying the RPM database
- </para>
+<!-- $Id: -->
+<chapter id="ch-rpm-overview">
+ <title>RPM Overview</title>
<para>
- *Running RPM commands
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Understanding the package file
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Querying the RPM database
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Running RPM commands
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
Working with RPM packages, files, commands, and databases can be
complicated. There are thousands of files, for hundreds if not
thousands of packages, installed on your system. You need some way
to manage it all. The RPM system can help you do that.
</para>
-
<para>
This chapter provides an overview of the components that make up the
RPM system for package management: package files, databases, and RPM
commands.
</para>
-
<sect1>
<title>Understanding the Package File</title>
<para>
@@ -235,7 +228,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Querying the RPM Database</title>
<para>
@@ -335,7 +327,6 @@
5.
</para>
</sect1>
-
<sect1>
<title>Running RPM Commands</title>
<para>
@@ -701,7 +692,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -717,6 +707,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-rpmbuild-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-rpmbuild-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-rpmbuild-en.xml 4 Oct 2005 01:59:30 -0000 1.1
+++ rpm-guide-rpmbuild-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,51 +1,46 @@
-<!-- $Id: -->
-<chapter id="ch-rpmbuild">
-<title>Controlling the Build with rpmbuild</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Building with the rpmbuild command
- </para>
-
- <para>
- *Building RPMs without an external spec file
- </para>
-
- <para>
- *Working with source RPMs
- </para>
-
- <para>
- *Optimizing builds
- </para>
+<!-- $Id: -->
+<chapter id="ch-rpmbuild">
+ <title>Controlling the Build with <command>rpmbuild</command></title>
<para>
- *Signing built RPMs
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Building with the <command>rpmbuild</command> command
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Building RPMs without an external spec file
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Working with source RPMs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Optimizing builds
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Signing built RPMs
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
The preceding chapters in this Part cover details on how to put
together RPMs. This chapter rounds out the discussion by delving
into more details on the rpmbuild command.
</para>
-
<para>
You can customize how rpmbuild creates RPMs, and you can use RPM
commands to test and debug your package.
</para>
-
<sect1>
<title>Building RPMs with the rpmbuild Command</title>
<para>
@@ -526,7 +521,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Building RPMs Without an External Spec File</title>
<para>
@@ -718,7 +712,6 @@
<para/>
</sect2>
</sect1>
-
<sect1>
<title>Working with Source RPMs</title>
<para>
@@ -1095,7 +1088,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Signing Built RPMs</title>
<para>
@@ -1750,7 +1742,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -1785,6 +1776,7 @@
<para/>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-scripting-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-scripting-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-scripting-en.xml 4 Oct 2005 02:02:12 -0000 1.1
+++ rpm-guide-scripting-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,32 +1,27 @@
-<!-- $Id: -->
-<chapter id="ch-scripting">
-<title>Automating RPM with Scripts</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Deciding when to program and when to script
- </para>
-
- <para>
- *Examining RPM files with scripts
- </para>
+<!-- $Id: -->
+<chapter id="ch-scripting">
+ <title>Automating RPM with Scripts</title>
<para>
- *Querying the RPM database with scripts
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Deciding when to program and when to script
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Examining RPM files with scripts
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Querying the RPM database with scripts
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
The rpm command provides a very high-level view of package
management. Most of the operations you need to perform require only
@@ -34,12 +29,10 @@
command tend to get very complex, however, especially for detailed
queries. That���s where scripting can help.
</para>
-
<para>
This chapter covers scripting, specifically shell scripting, with
the rpm command, especially for newcomers to Linux scripting
</para>
-
<sect1>
<title>Scripting</title>
<para>
@@ -94,7 +87,6 @@
Don���t get caught up in this. Use the right tool for the job.
</para>
</sect1>
-
<sect1>
<title>Distinguishing Scripting Languages from Programming Languages</title>
<para>
@@ -191,7 +183,6 @@
</tgroup>
</informaltable>
</sect1>
-
<sect1>
<title>Deciding When to Program and When to Script</title>
<para>
@@ -238,7 +229,6 @@
and Chapter 18 covers Perl scripting.
</para>
</sect1>
-
<sect1>
<title>Shell Scripting Basics</title>
<para>
@@ -857,7 +847,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Examining RPM Files</title>
<para>
@@ -1005,7 +994,6 @@
install.
</para>
</sect1>
-
<sect1>
<title>Querying the RPM Database</title>
<para>
@@ -1119,7 +1107,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Where to Go From Here</title>
<para>
@@ -1152,7 +1139,6 @@
perform.
</para>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -1178,6 +1164,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-specfile-syntax-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-specfile-syntax-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-specfile-syntax-en.xml 4 Oct 2005 02:03:52 -0000 1.1
+++ rpm-guide-specfile-syntax-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,29 +1,30 @@
-<!-- $Id: -->
-<chapter id="ch-specfile-syntax">
-<title>Spec File Syntax</title>
-
- <para>
- In This Appendix
- </para>
-
- <para>
- *The package information tags
- </para>
+<!-- $Id: -->
+<chapter id="ch-specfile-syntax">
+ <title>Spec File Syntax</title>
<para>
- *Build sections
+ This appendix covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ The package information tags
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Build sections
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
The RPM spec file is divided into two main parts: the package
information tags, such as the name of the package, and the build
sections, such as the commands to compile the software.
</para>
-
<para>
The following sections summarize the spec file syntax.
</para>
-
<sect1>
<title>Package Information Tags</title>
<para>
@@ -297,7 +298,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Macros</title>
<para>
@@ -658,7 +658,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Build Sections</title>
<para>
@@ -776,7 +775,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>File Tags</title>
<para>
@@ -848,7 +846,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>The Change Log</title>
<para>
@@ -873,6 +870,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
@@ -880,4 +878,3 @@
fill-column: 72
End:
-->
-
Index: rpm-guide-specfiles-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-specfiles-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-specfiles-en.xml 4 Oct 2005 02:15:56 -0000 1.1
+++ rpm-guide-specfiles-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,40 +1,37 @@
-<!-- $Id: -->
-<chapter id="ch-specfiles">
-<title>Working with Spec Files</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Writing spec files
- </para>
-
- <para>
- *Defining package information
- </para>
-
- <para>
- *Controlling the build
- </para>
-
- <para>
- *Listing the files in the package
- </para>
+<!-- $Id: -->
+<chapter id="ch-specfiles">
+ <title>Working with Spec Files</title>
<para>
- *Defining spec file macros
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Writing spec files
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Defining package information
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Controlling the build
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Listing the files in the package
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Defining spec file macros
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
The previous chapter introduces the concepts of how to build RPMs,
and briefly covered the spec file, which controls how RPM packages
@@ -42,13 +39,11 @@
files and the next chapter covers advanced spec file topics such as
using conditional commands and making relocatable packages.
</para>
-
<para>
A spec file defines all the commands and values that are required
for creating a package, everything from the name and version number
to the actual commands used to build the program you are packaging.
</para>
-
<para>
This chapter covers the spec file syntax and how to write spec
files. In goes in depth into defining information about your
@@ -56,7 +51,6 @@
exactly should go into the package, and customizing your build with
RPM macros.
</para>
-
<sect1>
<title>Reading Spec Files</title>
<para>
@@ -104,7 +98,6 @@
these sections.
</para>
</sect1>
-
<sect1>
<title>Writing Spec Files</title>
<para>
@@ -311,7 +304,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Defining Package Information</title>
<para>
@@ -840,7 +832,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Controlling the Build</title>
<para>
@@ -1522,7 +1513,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Filling the List of Files</title>
<para>
@@ -2134,7 +2124,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Adding Change Log Entries</title>
<para>
@@ -2162,7 +2151,6 @@
- updated to 1.3
</para>
</sect1>
-
<sect1>
<title>Defining Spec File Macros</title>
<para>
@@ -2670,7 +2658,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Creating XML Spec Files</title>
<para>
@@ -2866,7 +2853,6 @@
format will likely change.
</para>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -2916,6 +2902,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-transactions-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-transactions-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-transactions-en.xml 4 Oct 2005 02:04:58 -0000 1.1
+++ rpm-guide-transactions-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,27 +1,32 @@
-<!-- $Id: -->
-<chapter id="ch-transactions">
-<title>Transactions</title>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Understanding transactions
- </para>
-
- <para>
- *Querying for packages based on transactions
- </para>
-
- <para>
- *Rolling back transactions
- </para>
+<!-- $Id: -->
+<chapter id="ch-transactions">
+ <title>Transactions</title>
<para>
- *Saving old packages when upgrading
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Understanding transactions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Querying for packages based on transactions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Rolling back transactions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Saving old packages when upgrading
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
When packages depend on other packages, you may have to install
multiple packages to add a single application. Some of the packages
@@ -30,7 +35,6 @@
RPM system understood this problem and added the concept of
transactions to RPM.
</para>
-
<para>
This chapter covers transactions and how they can help you cleanly
install a set of dependent packages. But transactions won���t solve
@@ -38,7 +42,6 @@
dependencies by using the techniques provided in the last three
chapters.
</para>
-
<sect1>
<title>Understanding Transactions</title>
<para>
@@ -117,7 +120,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Transactions with the rpm Command</title>
<para>
@@ -510,7 +512,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Saving Old Packages</title>
<para>
@@ -634,7 +635,6 @@
Download rpmrebuild from http://rpmrebuild.sourceforge.net/.
</para>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -672,6 +672,7 @@
<para/>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-using-rpm-db-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-db-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-using-rpm-db-en.xml 4 Oct 2005 02:07:01 -0000 1.1
+++ rpm-guide-using-rpm-db-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,64 +1,66 @@
-<!-- $Id: -->
-<chapter id="ch-using-rpm-db">
-<title>Using the RPM Database</title>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Querying the RPM database
- </para>
-
- <para>
- *Getting information on RPM files
- </para>
-
- <para>
- * Finding out which packages own files on your system
- </para>
-
- <para>
- * Verifying installed packages
- </para>
-
- <para>
- *Backing up the RPM database
- </para>
+<!-- $Id: -->
+<chapter id="ch-using-rpm-db">
+ <title>Using the RPM Database</title>
<para>
- *Repairing damaged RPM databases
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Querying the RPM database
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Getting information on RPM files
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Finding out which packages own files on your system
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Verifying installed packages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Backing up the RPM database
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Repairing damaged RPM databases
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
Every package you install with RPM is recorded in the RPM database.
The RPM system includes commands to query this database to find out
which packages are installed and to provide quite a few details
about these packages.
</para>
-
<para>
This chapter covers querying both the RPM database and RPM package
files. Both types of query are important:
</para>
-
<para>
*Query the RPM database to see what is installed, or not installed,
on your system.
</para>
-
<para>
*Query package files to see what the files require, as well as what
the files provide.
</para>
-
<para>
In addition to querying the RPM database, you can use the database
to verify packages. Since this database is so important to the
management of your Linux system, this chapter covers how to back it
up, as well as how to repair a damaged RPM database.
</para>
-
<sect1>
<title>Querying the RPM Database</title>
<para>
@@ -713,7 +715,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Getting Information on Packages</title>
<para>
@@ -3617,7 +3618,6 @@
</informaltable>
</sect2>
</sect1>
-
<sect1>
<title>Getting Information on Package Files</title>
<para>
@@ -3767,7 +3767,6 @@
</informaltable>
<para/>
</sect1>
-
<sect1>
<title>Verifying Installed RPM Packages</title>
<para>
@@ -4220,7 +4219,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Working With the RPM Database</title>
<para>
@@ -4480,7 +4478,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -4501,6 +4498,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
Index: rpm-guide-using-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-using-rpm-en.xml 4 Oct 2005 02:08:57 -0000 1.1
+++ rpm-guide-using-rpm-en.xml 26 Oct 2005 01:54:11 -0000 1.2
@@ -1,34 +1,27 @@
-<!-- $Id: -->
-<chapter id="ch-using-rpm">
-<title>Using RPM</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Installing and upgrading software
- </para>
+<!-- $Id: -->
+<chapter id="ch-using-rpm">
+ <title>Using RPM</title>
<para>
- *Removing software
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Installing and upgrading software
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Removing software
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
This chapter covers the most common uses for RPM: installing,
removing, and upgrading software. These are the most frequently used
RPM commands.
</para>
-
<para>
The RPM system includes the options you might expect, such as
installing a package, but there���s a lot more you can do. For
@@ -37,7 +30,6 @@
rpm options you can use to get information and feedback on
installation, for example.
</para>
-
<sect1>
<title>The rpm Command</title>
<para>
@@ -50,7 +42,6 @@
reading this chapter.
</para>
</sect1>
-
<sect1>
<title>Upgrading and Installing Software</title>
<para>
@@ -1737,7 +1728,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Removing Software</title>
<para>
@@ -1925,7 +1915,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Other rpm Command Options</title>
<para>
@@ -2037,7 +2026,6 @@
--pipe command_to_send_out_to
</para>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -2148,6 +2136,7 @@
</para>
</sect1>
</chapter>
+
<!--
Local variables:
mode: xml
18 years, 6 months
rpm-guide rpm-guide-intro-packaging-en.xml,1.2,1.3
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/rpm-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18764
Modified Files:
rpm-guide-intro-packaging-en.xml
Log Message:
Fixed linking of chapter references
Index: rpm-guide-intro-packaging-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-intro-packaging-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-guide-intro-packaging-en.xml 24 Oct 2005 20:34:34 -0000 1.2
+++ rpm-guide-intro-packaging-en.xml 26 Oct 2005 00:49:38 -0000 1.3
@@ -432,58 +432,60 @@
<orderedlist>
<listitem>
<para>
- Chapter 2 provides an overview of the RPM system, exploring
- what it was designed for and where it has weaknesses.
+ <xref linkend="ch-intro-rpm"/> provides an overview of the RPM
+ system, exploring what it was designed for and where it has
+ weaknesses.
</para>
</listitem>
<listitem>
<para>
- Chapter 3 discusses the technical details of how the RPM
- system works, where the database of packages gets stored, and
- what commands should be available for working with RPM
- packages.
+ <xref linkend="ch-rpm-overview" /> discusses the technical
+ details of how the RPM system works, where the database of
+ packages gets stored, and what commands should be available
+ for working with RPM packages.
</para>
</listitem>
<listitem>
<para>
- Chapter 4 continues the discussion by covering the three major
- tasks you need to perform with RPM packages: installing
- software, removing software, and upgrading software you have
- already installed.
+ <xref linkend="ch-using-rpm"/> continues the discussion by
+ covering the three major tasks you need to perform with RPM
+ packages: installing software, removing software, and
+ upgrading software you have already installed.
</para>
</listitem>
<listitem>
<para>
- Chapter 5 covers the RPM database, how it works, where it
- resides, and how you can use it to better manage your system.
+ <xref linkend="ch-using-rpm-db" /> covers the RPM database,
+ how it works, where it resides, and how you can use it to
+ better manage your system.
</para>
</listitem>
<listitem>
<para>
- Chapter 6 delves into package dependencies, a very important
- concept. Most major applications depend on a number of other
- packages. Sometimes these dependencies get very complex, with
- one package depending on particular versions of other
- packages. With thousands of packages on your system, this can
- lead to a big mess. Chapter 6 helps you sort through the
- issues.
+ <xref linkend="ch-dependencies"/> delves into package
+ dependencies, a very important concept. Most major
+ applications depend on a number of other packages. Sometimes
+ these dependencies get very complex, with one package
+ depending on particular versions of other packages. With
+ thousands of packages on your system, this can lead to a big
+ mess. This chapter helps you to sort through the issues.
</para>
</listitem>
<listitem>
<para>
- Chapter 7 covers the important issue of transactions, so that
- you can ensure your system gets updated in an orderly manner
- and so that you can roll back changes if something does not
- work out.
+ <xref linkend="ch-transactions"/> covers the important issue
+ of transactions, so that you can ensure your system gets
+ updated in an orderly manner and so that you can roll back
+ changes if something does not work out.
</para>
</listitem>
<listitem>
<para>
- Chapter 8 introduces a host of tools that can help you find
- RPM packages as well as manage the packages on your system.
- This includes graphical interfaces on top of the RPM system
- and special Internet search sites devoted just to RPM
- packages.
+ <xref linkend="ch-management-software"/> introduces a host of
+ tools that can help you find RPM packages as well as manage
+ the packages on your system. This includes graphical
+ interfaces on top of the RPM system and special Internet
+ search sites devoted just to RPM packages.
</para>
</listitem>
</orderedlist>
18 years, 6 months
docs-common/common opl.xml,1.2,1.3
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18683
Modified Files:
opl.xml
Log Message:
Minor style edits
Index: opl.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/opl.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- opl.xml 18 Oct 2005 23:07:37 -0000 1.2
+++ opl.xml 26 Oct 2005 00:22:25 -0000 1.3
@@ -14,14 +14,14 @@
<para>
Permission is granted to copy, distribute, and/or modify this
document under the terms of the Open Publication Licence, Version
- 1.0 or any later version. The terms of the OPL are set out below.
+ 1.0, or any later version. The terms of the OPL are set out below.
</para>
</section>
<section id="opl.require">
<title>REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED VERSIONS</title>
<para>
- The Open Publication works may be reproduced and distributed in
+ Open Publication works may be reproduced and distributed in
whole or in part, in any medium physical or electronic, provided
that the terms of this license are adhered to, and that this
license or an incorporation of it by reference (with any options
18 years, 6 months
docs-common/bin tidy-bowl,1.2,1.3
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11728/docs-common/bin
Modified Files:
tidy-bowl
Log Message:
Avoid trying to pretty-print non-English XML files, for now at least.
Index: tidy-bowl
===================================================================
RCS file: /cvs/docs/docs-common/bin/tidy-bowl,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- tidy-bowl 17 Aug 2005 07:58:01 -0000 1.2
+++ tidy-bowl 25 Oct 2005 20:30:24 -0000 1.3
@@ -45,8 +45,9 @@
for fn in $@
do
case "${fn}" in
- *.[Xx][Mm][Ll] )
+ *-[Ee][Nn].[Xx][Mm][Ll] )
# Make sure we can find the input file
+ # /bin/echo "$0: English XML file ${fn} prettyprinted."
if [ ! -f "${fn}" ]; then
/bin/echo $0 "Cannot find '${fn}'"
exit 1
@@ -58,7 +59,13 @@
exit 1
fi
;;
+ *.[Xx][Mm][Ll] )
+ # A non-English XML file. What to do, what to do?
+ # /bin/echo "$0: Non-English XML file ${fn} left unchanged."
+ ;;
* )
+ # Some other kind of file. DO NOTHING!!!
+ # /bin/echo "$0: file ${fn} left unchanged."
;;
esac
done
18 years, 6 months
release-notes package-movement-en.xml, 1.3, 1.4 package-notes-en.xml, 1.3, 1.4
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10111
Modified Files:
package-movement-en.xml package-notes-en.xml
Log Message:
Typos that broke the build, sorry, forgot to test the build before I did my last commits.
Index: package-movement-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-movement-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- package-movement-en.xml 25 Oct 2005 09:07:12 -0000 1.3
+++ package-movement-en.xml 25 Oct 2005 19:40:56 -0000 1.4
@@ -1052,7 +1052,6 @@
<para>
Screensavers not installed by default anymore? Explain
why and provide commands to install them.
- </emphasis>)
</para>
<!-- FIXME
<para>
Index: package-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- package-notes-en.xml 25 Oct 2005 09:07:12 -0000 1.3
+++ package-notes-en.xml 25 Oct 2005 19:40:56 -0000 1.4
@@ -36,7 +36,7 @@
have undergone significant changes for &DISTRO; &DISTROVER;. For
easier access, they are generally organized using the same groups
used in Anaconda.
- </para
+ </para>
<caution>
<title>Information Out-of-Date</title>
<para>
18 years, 6 months
release-notes RELEASE-NOTES-en.xml, 1.3, 1.4 hardware-reqs-en.xml, 1.1, 1.2 install-notes-en.xml, 1.2, 1.3 multimedia-en.xml, 1.2, 1.3 overview-en.xml, 1.1, 1.2 package-movement-en.xml, 1.2, 1.3 package-notes-en.xml, 1.2, 1.3 splash-en.xml, 1.2, 1.3
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24035
Modified Files:
RELEASE-NOTES-en.xml hardware-reqs-en.xml install-notes-en.xml
multimedia-en.xml overview-en.xml package-movement-en.xml
package-notes-en.xml splash-en.xml
Log Message:
Cleanup before tagging for trans.
Index: RELEASE-NOTES-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- RELEASE-NOTES-en.xml 25 Oct 2005 08:34:00 -0000 1.3
+++ RELEASE-NOTES-en.xml 25 Oct 2005 09:07:11 -0000 1.4
@@ -40,7 +40,7 @@
<!-- *************** Local entities *************** -->
- <!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-07-26-T16:20-0700)"> <!-- version of manual and date -->
+ <!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-10-25-T04:20-0700)"> <!-- version of manual and date -->
<!ENTITY LOCALVER "5 test1"> <!-- Set value to your choice, when guide version is out -->
<!-- of sync with FC release, use instead of FEDVER or FEDTESTVER -->
<!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
@@ -48,9 +48,9 @@
<!ENTITY DISTRO "&FC;"> <!-- The software's name -->
<!ENTITY DISTROVER "&LOCALVER;"> <!-- The software's version -->
<!ENTITY BUG-NUM "151189"> <!-- Tracker bug number -->
- <!ENTITY BUG-URL "https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?assigned_to=relnotes&p...!
ion=&estimated_time=0.0&estimated_time_presets=0.0&ext_bz_bug_id=&ext_bz_id=0&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Linux&priority=normal&product=Fedora%20Core&rep_platform=All&short_desc=Describe%20problem%2C%20fix%2C%20or%20request%20for%20release%20notes&version=devel&GoAheadAndLogIn=Login">
+ <!ENTITY BUG-URL "https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%...!
ercnt;3A%0D%0A1.%0D%0A2.%0D%0A3.%0D%0A%20%20%0D%0AActual%20results%3A%0D%0A%0D%0A%0D%0AExpected%20results%3A%0D%0A%0D%0A%0D%0AAdditional%20info%3A&status_whiteboard=&keywords=&issuetrackers=&dependson=&blocked=151189%2C%20168083&ext_bz_id=0&ext_bz_bug_id=&data=&description=&contenttypemethod=list&contenttypeselection=text%2Fplain&contenttypeentry=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug">
<!-- Pre-filled bz -->
-<!ENTITY TINY-BUG-URL "http://tinyurl.com/al5g4">
+<!ENTITY TINY-BUG-URL "http://tinyurl.com/byvk2">
]>
<article id="index" lang="en" arch="x86;x86_64;ppc" os="test;final">
Index: hardware-reqs-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/hardware-reqs-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hardware-reqs-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ hardware-reqs-en.xml 25 Oct 2005 09:07:12 -0000 1.2
@@ -230,14 +230,11 @@
<listitem>
<para>
<!--<remark os="test">(ppc)</remark> --> &FC; &LOCALVER;
- supports only the <quote>New World</quote> generation of
- <trademark class="registered">Apple</trademark> Power
- Macintosh, shipped circa 1999 onwards. It also supports the
- 64-bit G5 processor and, POWER processors in <trademark
- class="registered">IBM</trademark>
- <trademark>eServer</trademark> <trademark>pSeries</trademark>.
- Currently 32-bit <trademark class="registered">IBM</trademark>
- <trademark>RS/6000</trademark> machines are not supported.
+ supports only the <quote>New World</quote> generation of Apple
+ Power Macintosh, shipped circa 1999 onwards. It also supports
+ the 64-bit G5 processor and, POWER processors in IBM eServer
+ pSeries. Currently 32-bit IBM RS/6000 machines are not
+ supported.
</para>
</listitem>
<listitem>
Index: install-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- install-notes-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ install-notes-en.xml 25 Oct 2005 09:07:12 -0000 1.3
@@ -59,88 +59,90 @@
RAM.</para>
</listitem>
</itemizedlist>
- </section>
- <para>
- The DVD or first CD of the installation set of &FC; is set to be
- bootable on supported hardware. In addition, bootable CD images
- can be found in the <filename>images/</filename> directory of the
- DVD or first CD. These will behave differently according to the
- hardware:
- </para>
- <variablelist>
- <title>Boot Image Behavior by Hardware</title>
+ <para>
+ The DVD or first CD of the installation set of &FC; is set to be
+ bootable on supported hardware. In addition, bootable CD images
+ can be found in the <filename>images/</filename> directory of
+ the DVD or first CD. These will behave differently according to
+ the hardware:
+ </para>
+ <variablelist>
+ <title>Boot Image Behavior by Hardware</title>
<varlistentry>
<term>Apple Macintosh </term>
- <listitem>
- <para>The bootloader should automatically boot the appropriate
- 32-bit or 64-bit installer. Power management support,
- including sleep and backlight level management, is present
- in the <filename>apmud</filename> package, which is in &FEX;.
- &FEX; for &FC; is configured by default for yum. Following
- installation, <filename>apmud</filename> can be installed by
- running the command <command>yum install apmud</command>
- in a terminal.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>64-bit IBM eServer pSeries (POWER4/POWER5)</term>
- <listitem>
- <para>After using OpenFirmware to boot the CD, the bootloader
- (<command>yaboot</command>) should automatically boot the
- 64-bit installer.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>32-bit CHRP (IBM RS/6000 and others)</term>
- <listitem>
- <para>After using OpenFirmware to boot the CD, select the
- <filename>linux32</filename> boot image at the
- <prompt>boot:</prompt> prompt to start the 32-bit installer.
- Otherwise, the 64-bit installer is started, which does not
- work.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Genesi Pegasos II</term>
- <listitem>
- <para>As of &DISTRO; &DISTROVER;, firmware with full support
- for ISO9660 file systems is not yet released for the
- Pegasos. However, the network boot image can be used. At
- the OpenFirmware prompt, enter the command: </para>
+ <listitem>
+ <para>The bootloader should automatically boot the
+ appropriate 32-bit or 64-bit installer. Power management
+ support, including sleep and backlight level management,
+ is present in the <filename>apmud</filename> package,
+ which is in &FEX;. &FEX; for &FC; is configured by default
+ for yum. Following installation,
+ <filename>apmud</filename> can be installed by running the
+ command <command>yum install apmud</command> in a
+ terminal.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>64-bit IBM eServer pSeries (POWER4/POWER5)</term>
+ <listitem>
+ <para>After using OpenFirmware to boot the CD, the
+ bootloader (<command>yaboot</command>) should
+ automatically boot the 64-bit installer.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>32-bit CHRP (IBM RS/6000 and others)</term>
+ <listitem>
+ <para>After using OpenFirmware to boot the CD, select the
+ <filename>linux32</filename> boot image at the
+ <prompt>boot:</prompt> prompt to start the 32-bit installer.
+ Otherwise, the 64-bit installer is started, which does not
+ work.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Genesi Pegasos II</term>
+ <listitem>
+ <para>As of &DISTRO; &DISTROVER;, firmware with full support
+ for ISO9660 file systems is not yet released for the
+ Pegasos. However, the network boot image can be used. At
+ the OpenFirmware prompt, enter the command:
+ </para>
<screen>
<command>boot cd: /images/netboot/ppc32.img</command>
</screen>
- <para>
- You will also need to configure OpenFirmware on the Pegasos
- manually to make the installed &FC; system bootable. To do
- this, you need to set the <envar>boot-device</envar> and
- <envar>boot-file</envar> environment variables
- appropriately.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Network booting</term>
- <listitem>
- <para>There are combined images containing the installer
- kernel and ramdisk in the images/netboot/ directory of the
- install tree. These are intended for network booting with
- TFTP, but can be used in many ways.
- </para>
- <para>
- The command <command>yaboot</command> supports tftp
- booting for IBM eServer pSeries and Apple Macintosh.
- &FED; recommends using yaboot over the netboot images.
- </para>
+ <para>
+ You will also need to configure OpenFirmware on the
+ Pegasos manually to make the installed &FC; system
+ bootable. To do this, you need to set the
+ <envar>boot-device</envar> and <envar>boot-file</envar>
+ environment variables appropriately.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Network booting</term>
+ <listitem>
+ <para>There are combined images containing the installer
+ kernel and ramdisk in the images/netboot/ directory of the
+ install tree. These are intended for network booting with
+ TFTP, but can be used in many ways.
+ </para>
+ <para>
+ The command <command>yaboot</command> supports tftp
+ booting for IBM eServer pSeries and Apple Macintosh. &FED;
+ recommends using yaboot over the netboot images.
+ </para>
</listitem>
- </varlistentry>
- </variablelist>
+ </varlistentry>
+ </variablelist>
+ </section>
</section>
<section>
<title>Anaconda Notes</title>
-
+
<itemizedlist>
<listitem>
<para>
Index: multimedia-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/multimedia-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- multimedia-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ multimedia-en.xml 25 Oct 2005 09:07:12 -0000 1.3
@@ -59,7 +59,7 @@
playback or recording, because the MP3 and MPEG (DVD) formats
are patented, and the patent owners have not provided the
necessary licenses. For more information, refer to <xref
- linkend="sn-multimedia-exluded"/>.
+ linkend="sn-multimedia-excluded"/>.
</para>
</listitem>
</varlistentry>
Index: overview-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/overview-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- overview-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ overview-en.xml 25 Oct 2005 09:07:12 -0000 1.2
@@ -1,5 +1,13 @@
<section id="sn-overview">
<title>Overview of This Release</title>
+ <caution>
+ <title>Information Out-of-Date</title>
+ <para>
+ The content in this section needs to be updated for &DISTRO;
+ &DISTROVER;
+ </para>
+ </caution>
+<!--
<para>
The following list includes brief summaries of some of the more
significant aspects of &DISTRO; &DISTROVER;:
@@ -69,10 +77,6 @@
</para>
</listitem>
<listitem>
-<!-- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136251">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136251</ulink>
- %%%</remark>-->
-
<para>
&SEL; — This release includes coverage for 80 new
daemons by the targeted policy. There are changes to the
@@ -543,42 +547,6 @@
</itemizedlist>
</listitem>
</itemizedlist>
- <!--
- <note>
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136774">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136774</ulink>
- %%%</remark>
- <title>Note</title>
- <para>
- VMware WS 4.5.2 is known to work on &DISTRO; &DISTROVER; after
- the following workarounds are used:</para>
-
- <itemizedlist>
- <listitem>
- <para>You must upgrade the kernel modules and configuration
- using the unofficial <filename>vmware-any-any-*</filename>
- toolkit available from:</para>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137378">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137378</ulink>
- %%%</remark>
-
- <para><ulink
- url="http://platan.vc.cvut.cz/ftp/pub/vmware/">http://platan.vc.cvut.cz/ftp/pub/vmware/</ulink></para>
-
- </listitem>
-
- <listitem>
- <para>After <filename>vmware-config.pl</filename> is run and the
- VMware modules are loaded, the following command creates the
- <filename>/sys/class/*</filename> nodes needed for
- udev:</para>
-
- <para><command>cp -rp /dev/vm*
- /etc/udev/devices/</command></para>
- </listitem>
- </itemizedlist>
- </note>
-->
</section>
<!--
Index: package-movement-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-movement-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- package-movement-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ package-movement-en.xml 25 Oct 2005 09:07:12 -0000 1.3
@@ -1044,18 +1044,14 @@
<section>
<title>Notes</title>
<para>
- system-config-mouse configuration utility has been dropped in this
- release because synaptic and 3 button mouse configuration is being
- done automatically and serial mice are not supported (<emphasis
- role='strong'>copied to <ulink
- url='/Docs/Beats/Desktop'>Docs/Beats/Desktop</ulink>
- </emphasis> - OK?)
+ <application>system-config-mouse</application> configuration
+ utility has been dropped in this release because synaptic and 3
+ button mouse configuration is being done automatically and serial
+ mice are not supported.
</para>
<para>
Screensavers not installed by default anymore? Explain
- why and provide commands to install them (<emphasis
- role='strong'>copied to <ulink
- url='/Docs/Beats/Desktop'>Docs/Beats/Desktop</ulink>
+ why and provide commands to install them.
</emphasis>)
</para>
<!-- FIXME
Index: package-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- package-notes-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ package-notes-en.xml 25 Oct 2005 09:07:12 -0000 1.3
@@ -36,8 +36,14 @@
have undergone significant changes for &DISTRO; &DISTROVER;. For
easier access, they are generally organized using the same groups
used in Anaconda.
- </para>
-
+ </para
+ <caution>
+ <title>Information Out-of-Date</title>
+ <para>
+ The content in this section needs to be updated for &DISTRO;
+ &DISTROVER;
+ </para>
+ </caution>
<section id="sn-basic-components">
<title>Basic Components</title>
<para>
Index: splash-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- splash-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ splash-en.xml 25 Oct 2005 09:07:12 -0000 1.3
@@ -39,11 +39,13 @@
Refer to these webpages to find out more information about &FED;:
</para>
<itemizedlist>
+<!-- FIXME Return when the section is updated
<listitem>
<para>
<xref linkend="sn-new-in-fc"/>
</para>
</listitem>
+-->
<listitem>
<para>
<xref linkend="sn-intro"/> — Technical release notes
18 years, 6 months
release-notes entertainment-en.xml, NONE, 1.1 i18n-en.xml, NONE, 1.1 legacy-en.xml, NONE, 1.1 Makefile, 1.2, 1.3 RELEASE-NOTES-en.xml, 1.2, 1.3 daemons-en.xml, 1.1, 1.2 desktop-en.xml, 1.1, 1.2 development-tools-en.xml, 1.1, 1.2 file-servers-en.xml, 1.1, 1.2 install-notes-en.xml, 1.1, 1.2 java-package-en.xml, 1.1, 1.2 kernel-en.xml, 1.1, 1.2 multimedia-en.xml, 1.1, 1.2 networking-en.xml, 1.1, 1.2 package-movement-en.xml, 1.1, 1.2 package-notes-en.xml, 1.1, 1.2 security-en.xml, 1.1, 1.2 server-tools-en.xml,
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22258
Modified Files:
Makefile RELEASE-NOTES-en.xml daemons-en.xml desktop-en.xml
development-tools-en.xml file-servers-en.xml
install-notes-en.xml java-package-en.xml kernel-en.xml
multimedia-en.xml networking-en.xml package-movement-en.xml
package-notes-en.xml security-en.xml server-tools-en.xml
splash-en.xml web-servers-en.xml xorg-en.xml
Added Files:
entertainment-en.xml i18n-en.xml legacy-en.xml
Log Message:
All of the content from the Wiki has been incorporated, some other changes, cautions and such applied, this is truly a test release notes with some poor language and other lack of polish.
--- NEW FILE entertainment-en.xml ---
<section id="sn-entertainment">
<title>Games and Entertainment</title>
<para>
&FC; and &FEX; provide a selection of games that cover a variety of
genres. By default, &FC;includes a small package of games for GNOME
(called <filename>gnome-games</filename>). For a list of other
games that are available for installation through
<command>yum</command>, open a terminal and enter the following
command:
</para>
<screen>
<command>yum groupinfo "Games and Entertainment"</command>
</screen>
<para>
For help using <command>yum</command> to install the assorted game
packages, refer to the guide available at: </para>
<para>
<ulink
url="http://fedora.redhat.com/docs/yum/">http://fedora.redhat.com/docs/yum/</ulink>
</para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE i18n-en.xml ---
<section id="sn-i18n">
<title>Internationalization (i18n)</title>
<para>
SCIM has replaced all the other input methods. Major highlight.
</para>
<section>
<title>Language Support</title>
<para>
This section includes information related to the support of
various languages under &DISTRO;.
</para>
<section>
<title>The IIIMF Input System</title>
<para>
IIIMF is the Internet/Intranet Input Method Framework. In &FC;
&LOCALVER; the <filename>iiimf</filename> package is updated to
version 12.2.
</para>
<variablelist>
<varlistentry>
<term>File Path Changes</term>
<listitem>
<para>
The names and locations of some files in the
<filename>iiimf</filename> packages have changed.
</para>
<para>
The IIIMF server has been renamed from
<filename>/usr/sbin/htt</filename> to
<filename>/usr/bin/iiimd</filename>, and the XIM bridge
client renamed from <filename>httx</filename> to
<filename>iiimx</filename>. The
<filename>init.d</filename> script name has not changed:
it is still called <filename>iiim</filename>. All the
global system configuration files are now located under
<filename>/etc/iiim/</filename>.
</para>
<para>
Language Engine (LE) developers should note that LE
modules and their data now live under
<filename>${libdir}/iiim/le/<filename><LE_NAME></filename>/</filename>,
while runtime data is stored under
<filename>/var/lib/iiim/le/<replaceable><LE_NAME></replaceable>/</filename>.
</para>
<para>
For more information on the exact path and file location
changes, please refer to Fedora IIIMF FAQ:
</para>
<para>
<ulink
url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Hotkeys</term>
<listitem>
<para>
Trigger keys, such as
<keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>
used to activate Input Methods, are now configurable with
the command-line tool <command>iiimf-le-tools</command>.
This feature is only supported by GTK2 applications
currently. For other applications using XIM the trigger
key can be changed using an X resource. Refer to the
IIIMF FAQ at <ulink
url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>
for more details on how to change trigger hotkeys.
</para>
<para>
Note that the keyname refers to the X key symbol name. For
example, if you want to activate with
<keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>,
you need to specify '<Control>at' as the keyname not
'<Control>@'.
</para>
<para>
The per-user configuration of hotkeys does not work
currently with &SEL; in enforcing mode due to lack of
&SEL; policy. In this case, the hotkey can only be
changed in the system-wide configuration.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Qt Support</term>
<listitem>
<para>
A Qt immodule for <filename>iiimf</filename> is now
included. This immodule works but lacks a status window
and is considered experimental. Therefore, the default
for Qt applications is to continue using XIM for IIMF
input.
</para>
<para>
If you wish to try the immodule in a Qt application, first
install the <filename>iiimf-qt</filename> package, start
the application, then click mouse button-3 in an input
area and select <guimenuitem>iiimqcf</guimenuitem> from
the <guisubmenu>Select Input Method</guisubmenu>' submenu.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE legacy-en.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
Index: Makefile
===================================================================
RCS file: /cvs/docs/release-notes/Makefile,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Makefile 24 Oct 2005 14:08:53 -0000 1.2
+++ Makefile 25 Oct 2005 08:34:00 -0000 1.3
@@ -12,7 +12,7 @@
#
LANGUAGES = en
DOCBASE = RELEASE-NOTES
-XMLEXTRAFILES-en=daemons.xml database-servers.xml desktop.xml development-tools.xml feedback.xml file-servers.xml file-systems.xml hardware-reqs.xml install-notes.xml intro.xml java-package.xml kernel.xml misc-server.xml multimedia.xml networking.xml overview.xml package-movement.xml package-notes.xml printing.xml project-overview.xml samba.xml security.xml server-tools.xml splash.xml web-servers.xml xorg.xml
+XMLEXTRAFILES-en=daemons-en.xml database-servers-en.xml desktop-en.xml development-tools-en.xml feedback-en.xml file-servers-en.xml file-systems-en.xml hardware-reqs-en.xml install-notes-en.xml intro-en.xml java-package-en.xml kernel-en.xml misc-server-en.xml multimedia-en.xml networking-en.xml overview-en.xml package-movement-en.xml package-notes-en.xml printing-en.xml project-overview-en.xml samba-en.xml security-en.xml server-tools-en.xml splash-en.xml web-servers-en.xml xorg-en.xml
#
######################################################
include ../docs-common/Makefile.common
Index: RELEASE-NOTES-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- RELEASE-NOTES-en.xml 24 Oct 2005 13:33:23 -0000 1.2
+++ RELEASE-NOTES-en.xml 25 Oct 2005 08:34:00 -0000 1.3
@@ -3,57 +3,59 @@
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!-- *************** Section files *************** -->
-<!ENTITY FEEDBACK SYSTEM "./feedback.xml">
-<!ENTITY HARDWARE-REQS SYSTEM "./hardware-reqs.xml">
-<!ENTITY INSTALL-NOTES SYSTEM "./install-notes.xml">
-<!ENTITY SPLASH SYSTEM "./splash.xml">
-<!ENTITY INTRO SYSTEM "./intro.xml">
-<!ENTITY OVERVIEW SYSTEM "./overview.xml">
-<!ENTITY PACKAGE-MOVEMENT SYSTEM "./package-movement.xml">
-<!ENTITY PACKAGE-NOTES SYSTEM "./package-notes.xml">
-<!ENTITY PROJECT-OVERVIEW SYSTEM "./project-overview.xml">
-<!ENTITY KERNEL SYSTEM "./kernel.xml">
-<!ENTITY SAMBA SYSTEM "./samba.xml">
-<!ENTITY PRINTING SYSTEM "./printing.xml">
-<!ENTITY SERVER-TOOLS SYSTEM "./server-tools.xml">
-<!ENTITY DEVELOPMENT-TOOLS SYSTEM "./development-tools.xml">
-<!ENTITY SECURITY SYSTEM "./security.xml">
-<!ENTITY FILE-SYSTEMS SYSTEM "./file-systems.xml">
-<!ENTITY FILE-SERVERS SYSTEM "./file-servers.xml">
-<!ENTITY DATABASE-SERVERS SYSTEM "./database-servers.xml">
-<!ENTITY WEB-SERVERS SYSTEM "./web-servers.xml">
-<!ENTITY DAEMONS SYSTEM "./daemons.xml">
-<!ENTITY MULTIMEDIA SYSTEM "./multimedia.xml">
-<!ENTITY MISC-SERVER SYSTEM "./misc-server.xml">
-<!ENTITY JAVA-PACKAGE SYSTEM "./java-package.xml">
-<!ENTITY NETWORKING SYSTEM "./networking.xml">
-<!ENTITY XORG SYSTEM "./xorg.xml">
+<!ENTITY FEEDBACK SYSTEM "./feedback-en.xml">
+<!ENTITY HARDWARE-REQS SYSTEM "./hardware-reqs-en.xml">
+<!ENTITY INSTALL-NOTES SYSTEM "./install-notes-en.xml">
+<!ENTITY SPLASH SYSTEM "./splash-en.xml">
+<!ENTITY INTRO SYSTEM "./intro-en.xml">
+<!ENTITY OVERVIEW SYSTEM "./overview-en.xml">
+<!ENTITY PACKAGE-MOVEMENT SYSTEM "./package-movement-en.xml">
+<!ENTITY PACKAGE-NOTES SYSTEM "./package-notes-en.xml">
+<!ENTITY PROJECT-OVERVIEW SYSTEM "./project-overview-en.xml">
+<!ENTITY KERNEL SYSTEM "./kernel-en.xml">
+<!ENTITY SAMBA SYSTEM "./samba-en.xml">
+<!ENTITY PRINTING SYSTEM "./printing-en.xml">
+<!ENTITY SERVER-TOOLS SYSTEM "./server-tools-en.xml">
+<!ENTITY DEVELOPMENT-TOOLS SYSTEM "./development-tools-en.xml">
+<!ENTITY SECURITY SYSTEM "./security-en.xml">
+<!ENTITY FILE-SYSTEMS SYSTEM "./file-systems-en.xml">
+<!ENTITY FILE-SERVERS SYSTEM "./file-servers-en.xml">
+<!ENTITY DATABASE-SERVERS SYSTEM "./database-servers-en.xml">
+<!ENTITY WEB-SERVERS SYSTEM "./web-servers-en.xml">
+<!ENTITY DAEMONS SYSTEM "./daemons-en.xml">
+<!ENTITY MULTIMEDIA SYSTEM "./multimedia-en.xml">
+<!ENTITY MISC-SERVER SYSTEM "./misc-server-en.xml">
+<!ENTITY JAVA-PACKAGE SYSTEM "./java-package-en.xml">
+<!ENTITY NETWORKING SYSTEM "./networking-en.xml">
+<!ENTITY XORG SYSTEM "./xorg-en.xml">
+<!ENTITY ENTERTAINMENT SYSTEM "./entertainment-en.xml">
+<!ENTITY I18N SYSTEM "./i18n-en.xml">
+<!ENTITY LEGACY SYSTEM "./legacy-en.xml">
<!-- *************** COMMON FDP entities *************** -->
-<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
-%FEDORA-ENTITIES-EN;
-<!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
-
-<!-- *************** Local entities *************** -->
-
-<!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-07-26-T16:20-0700)"> <!-- version of manual and date -->
-<!ENTITY LOCALVER "4"> <!-- Set value to your choice, when guide version is out -->
-<!-- of sync with FC release, use instead of FEDVER or FEDTESTVER -->
-<!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
-<!ENTITY PROJ "&FP;"> <!-- The project's name -->
-<!ENTITY DISTRO "&FC;"> <!-- The software's name -->
-<!ENTITY DISTROVER "&LOCALVER;"> <!-- The software's version -->
-<!ENTITY BUG-NUM "151189"> <!-- Tracker bug number -->
-<!ENTITY BUG-URL "https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?assigned_to=relnotes&p...!
on=&estimated_time=0.0&estimated_time_presets=0.0&ext_bz_bug_id=&ext_bz_id=0&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Linux&priority=normal&product=Fedora%20Core&rep_platform=All&short_desc=Describe%20problem%2C%20fix%2C%20or%20request%20for%20release%20notes&version=devel&GoAheadAndLogIn=Login">
+ <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
+ %FEDORA-ENTITIES-EN;
+ <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
+
+ <!-- *************** Local entities *************** -->
+
+ <!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-07-26-T16:20-0700)"> <!-- version of manual and date -->
+ <!ENTITY LOCALVER "5 test1"> <!-- Set value to your choice, when guide version is out -->
+ <!-- of sync with FC release, use instead of FEDVER or FEDTESTVER -->
+ <!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
+ <!ENTITY PROJ "&FP;"> <!-- The project's name -->
+ <!ENTITY DISTRO "&FC;"> <!-- The software's name -->
+ <!ENTITY DISTROVER "&LOCALVER;"> <!-- The software's version -->
+ <!ENTITY BUG-NUM "151189"> <!-- Tracker bug number -->
+ <!ENTITY BUG-URL "https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?assigned_to=relnotes&p...!
ion=&estimated_time=0.0&estimated_time_presets=0.0&ext_bz_bug_id=&ext_bz_id=0&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Linux&priority=normal&product=Fedora%20Core&rep_platform=All&short_desc=Describe%20problem%2C%20fix%2C%20or%20request%20for%20release%20notes&version=devel&GoAheadAndLogIn=Login">
<!-- Pre-filled bz -->
<!ENTITY TINY-BUG-URL "http://tinyurl.com/al5g4">
]>
-<!-- <!ENTITY DISTROVER "@VERSION@"> --> <!-- The software's version -->
<article id="index" lang="en" arch="x86;x86_64;ppc" os="test;final">
<articleinfo>
- <title>&DISTRO; &DISTROVER; Release Notes <emphasis>(updated)</emphasis></title>
+ <title>&DISTRO; &DISTROVER; Release Notes</title>
<copyright>
<year>2005</year>
<holder>&FORMAL-RHI;</holder>
@@ -70,12 +72,7 @@
&OVERVIEW;
&INSTALL-NOTES;
&PACKAGE-NOTES;
+ &LEGACY;
&PACKAGE-MOVEMENT;
&PROJECT-OVERVIEW;
- <!--
- <ackno>(
- <emphasis arch="x86">x86</emphasis>
- <emphasis arch="x86_64">x86_64</emphasis>
- )</ackno>
- -->
</article>
Index: daemons-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/daemons-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- daemons-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ daemons-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -1,23 +1,33 @@
- <section id="sn-daemons">
- <title>System Services</title>
-
- <section id="sn-daemons-updatedb">
- <title><filename>cron</filename> and <filename>slocate</filename></title>
-
- <para>The <command>updatedb</command> utility is no longer
- automatically run by <command>cron</command> to create and
- update the database of files used by <command>slocate</command>.
- Updating this database is an intensive process that users of
- workstations and laptops may find disruptive.</para>
-
- <para>To enable daily updates of the <command>slocate</command>
- database, edit the file <filename>/etc/updatedb.conf</filename> as follows:
- </para>
+<section id="sn-daemons">
+ <title>System Services</title>
+ <caution>
+ <title>Information Out-of-Date</title>
+ <para>
+ The content in this section needs to be updated for &DISTRO;
+ &DISTROVER;
+ </para>
+ </caution>
+ <section id="sn-daemons-updatedb">
+ <title><filename>cron</filename> and
+ <filename>slocate</filename></title>
+ <para>
+ The <command>updatedb</command> utility is no longer automatically
+ run by <command>cron</command> to create and update the database
+ of files used by <command>slocate</command>. Updating this
+ database is an intensive process that users of workstations and
+ laptops may find disruptive.
+ </para>
+ <para>
+ To enable daily updates of the <command>slocate</command>
+ database, edit the file <filename>/etc/updatedb.conf</filename> as
+ follows:
+ </para>
-<screen>
-DAILY_UPDATE=yes
-</screen>
-
+ <screen>
+ DAILY_UPDATE=yes
+ </screen>
+ </section>
+</section>
<!--
Local variables:
mode: xml
@@ -25,3 +35,4 @@
fill-column: 72
End:
-->
+
Index: desktop-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/desktop-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- desktop-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ desktop-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -1,3 +1,73 @@
+<section id="sn-desktop">
+ <title>Desktop</title>
+ <itemizedlist>
+ <title>Notes</title>
+ <listitem>
+ <para>GNOME 2.12 and KDE 3.4.2 Major highlight
+ </para>
+ </listitem>
+ <listitem>
+ <para>The current test release has GNOME 2.12.1, together with
+ some previews of technology from the forthcoming GNOME 2.14:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>gnome-power-manager: brings the Hardware Abstraction
+ Layer to the world of laptop batteries and UPS units - these
+ things should "Just Work", with a simple UI (naturally, in
+ a test release, they might not)
+ </para>
+ </listitem>
+ <listitem>
+ <para>gnome-screensaver: giving a fresh UI to screensavers and
+ the <guilabel>Lock Screen</guilabel> dialog
+ </para>
+ </listitem>
+ <listitem>
+ <para>Memory optimizations in the fontconfig and
+ shared-mime-info packages (these now use shared
+ memory-mapped caches for this data). Both of these caches
+ are still somewhat experimental.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <para>
+ Test feedback on these experimental packages is especially
+ appreciated.
+ </para>
+ <para>
+ GNOME 2.12 has removed the terminal option from the desktop root
+ menu. nautilus-open-terminal in Fedora Extras repository provides a
+ enhanced replacement. It is also mentioned in the GNOME 2.12 release
+ notes itself but we might highlight it since the package is provided
+ with the extras repository.
+ </para>
+ <para>
+ Screensavers not installed by default anymore. Should explain why
+ and provide commands to install them.
+ </para>
+ <para>MCS SELinux is in rawhide. Major highlight
+ (<emphasis>tentative</emphasis> - not sure about classification of
+ this change)
+ </para>
+ <caution>
+ <title>OpenOffice and upgrading from test releases</title>
+ <para>
+ If you choose to go counter to the recommendation to <emphasis
+ role='strong'>not</emphasis> upgrade from a previous test
+ release, you may encounter a problem with <ulink
+ url='/OpenOffice'>OpenOffice</ulink> following the upgrade.
+ </para>
+ <para>
+ To resolve this, you must do the following command <emphasis
+ role='strong'>before</emphasis> doing the upgrade:
+ </para>
+<screen>
+<command>rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
+</screen>
+ </caution>
+</section>
<!--
Local variables:
mode: xml
Index: development-tools-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/development-tools-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- development-tools-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ development-tools-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -9,6 +9,7 @@
]>
-->
+<!-- Content commented out, no update performed by beat writer yet.
<section id="sn-devel">
<title>
Development Tools
@@ -176,7 +177,7 @@
</itemizedlist>
</section>
</section>
-
+-->
<!--
Local variables:
Index: file-servers-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/file-servers-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- file-servers-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ file-servers-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -1,46 +1,54 @@
<section id="sn-file-servers">
- <title>File Servers</title>
-
- <para>This section refers to file transfer and sharing servers. Please
- refer to the &WEB-SERVERS; and &SAMBA; sections for information on HTTP (Web) file
- transfer and Samba (Windows) file sharing.</para>
-
-
+ <title>File Servers</title>
+ <caution>
+ <title>Information Out-of-Date</title>
+ <para>
+ The content in this section needs to be updated for &DISTRO;
+ &DISTROVER;
+ </para>
+ </caution>
+ <para>
+ This section refers to file transfer and sharing servers.
+ Please refer to the &WEB-SERVERS; and &SAMBA; sections for
+ information on HTTP (Web) file transfer and Samba (Windows) file
+ sharing.
+ </para>
<section id="sn-file-servers-netatalk-suite">
- <title>Netatalk (Macintosh Compatibility)</title>
-
- <para>This section contains information related to Netatalk, a suite of
- software that enables Linux to interact with Macintosh systems using
- the AppleTalk network protocols.</para>
-
-
- <section id="sn-file-servers-netatalk-package">
- <title><filename>netatalk</filename></title>
-
- <para>&DISTRO; &DISTROVER; includes version 2 of Netatalk. <emphasis>Upgrading
- from Netatalk version 1 to version 2 may result in data
- loss</emphasis>. Version 2 of Netatalk uses a different
- method to store file resource forks from the previous version,
- and may require a different file name encoding scheme. Please
- read the documentation and plan your migration before upgrading.</para>
-
- <para>Upgrade information is available directly from the Netatalk site:</para>
-
- <para>
- <ulink url="http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html">http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html</ulink>
- </para>
-
- <para>The documentation is also included in the
- <filename>netatalk</filename> package. Refer to either
- <filename>/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html</filename>,
- or
- <filename>/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf</filename>
- (numbered page 25, document page 33).</para>
-
- </section>
-
-</section>
-
+ <title>Netatalk (Macintosh Compatibility)</title>
+ <para>
+ This section contains information related to Netatalk, a suite
+ of software that enables Linux to interact with Macintosh systems
+ using the AppleTalk network protocols.
+ </para>
+ <section id="sn-file-servers-netatalk-package">
+ <title><filename>netatalk</filename></title>
+ <para>
+ &DISTRO; &DISTROVER; includes version 2 of Netatalk.
+ <emphasis>Upgrading from Netatalk version 1 to version 2 may
+ result in data loss</emphasis>. Version 2 of Netatalk uses
+ a different method to store file resource forks from the
+ previous version, and may require a different file name encoding
+ scheme. Please read the documentation and plan your migration
+ before upgrading.
+ </para>
+ <para>
+ Upgrade information is available directly from the Netatalk
+ site:
+ </para>
+ <para>
+ <ulink
+ url="http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html">http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html</ulink>
+ </para>
+ <para>
+ The documentation is also included in the
+ <filename>netatalk</filename> package. Refer to either
+ <filename>/usr/share/doc/netatalk-<replaceable>version</replaceable>/doc/htmldocs/upgrade.html</filename>,
+ or
+ <filename>/usr/share/doc/netatalk-<replaceable>version</replaceable>/doc/Netatalk-Manual.pdf</filename>
+ (numbered page 25, document page 33).
+ </para>
+ </section>
+ </section>
</section>
<!--
Index: install-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- install-notes-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ install-notes-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -31,47 +31,112 @@
</note>
<section id="sn-install-notes-ppc">
<title>PPC Installation Notes</title>
+ <section>
+ <title>PPC Hardware Requirements</title>
+ <para>
+ This section lists the minimum PowerPC (PPC) hardware needed
+ to install &DISTRO; &DISTROVER;.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Minimum: PowerPC G3 / POWER4 </para>
+ </listitem>
+ <listitem>
+ <para>&DISTRO; &DISTROVER; supports only the ���New World��� generation
+ of Apple Power Macintosh, shipped circa 1999 onwards.
+ </para>
+ </listitem>
+ <listitem>
+ <para>&DISTRO; &DISTROVER; also supports IBM eServer pSeries, IBM
+ RS/6000, and Genesi Pegasos II machines.</para>
+ </listitem>
+ <listitem>
+ <para>Recommended for text-mode: 233 MHz G3 or better, 64MB
+ RAM.</para>
+ </listitem>
+ <listitem>
+ <para>Recommended for graphical: 400 MHz G3 or better, 128MB
+ RAM.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
<para>
- <!--<remark os="test">(ppc)</remark>--> The DVD or first CD of the
- installation set of &FC; is set to be bootable on the <trademark
- class="registered">Apple</trademark> Macintosh and should boot
- the appropriate 32-bit or 64-bit installer. In addition, bootable
- CD images can be found in the <filename>images/</filename>
- directory of the DVD or first CD. Choose the appropriate
- <filename>boot.iso</filename> according to the hardware:
+ The DVD or first CD of the installation set of &FC; is set to be
+ bootable on supported hardware. In addition, bootable CD images
+ can be found in the <filename>images/</filename> directory of the
+ DVD or first CD. These will behave differently according to the
+ hardware:
</para>
- <itemizedlist>
- <listitem>
- <para><filename>images/mac/boot.iso</filename> - 32-bit
- <trademark class="registered">Apple</trademark> Macintosh
- (G3/G4)
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>images/mac64/boot.iso</filename> - 64-bit <trademark
- class="registered">Apple</trademark> Macintosh (G5)
- </para>
- </listitem>
- <listitem>
- <para><filename>images/pseries/boot.iso</filename> - 64-bit
- <trademark class="registered">IBM</trademark>
- <trademark>eServer</trademark> <trademark>pSeries</trademark>
- (POWER4/POWER5)
- </para>
- </listitem>
- <listitem>
- <para>
- <!-- <remark os="test">(ppc)</remark> --> Power management
- support, including sleep and backlight level management, is
- present in the <command>apmud</command> package, which is in
- &FEX;. &FEX; for &FC; is configured by default for
- <command>yum</command>. Following installation,
- <command>apmud</command> can be installed by running
- <command>yum install apmud</command>.
- </para>
- </listitem>
- </itemizedlist>
+ <variablelist>
+ <title>Boot Image Behavior by Hardware</title>
+ <varlistentry>
+ <term>Apple Macintosh </term>
+ <listitem>
+ <para>The bootloader should automatically boot the appropriate
+ 32-bit or 64-bit installer. Power management support,
+ including sleep and backlight level management, is present
+ in the <filename>apmud</filename> package, which is in &FEX;.
+ &FEX; for &FC; is configured by default for yum. Following
+ installation, <filename>apmud</filename> can be installed by
+ running the command <command>yum install apmud</command>
+ in a terminal.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>64-bit IBM eServer pSeries (POWER4/POWER5)</term>
+ <listitem>
+ <para>After using OpenFirmware to boot the CD, the bootloader
+ (<command>yaboot</command>) should automatically boot the
+ 64-bit installer.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>32-bit CHRP (IBM RS/6000 and others)</term>
+ <listitem>
+ <para>After using OpenFirmware to boot the CD, select the
+ <filename>linux32</filename> boot image at the
+ <prompt>boot:</prompt> prompt to start the 32-bit installer.
+ Otherwise, the 64-bit installer is started, which does not
+ work.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Genesi Pegasos II</term>
+ <listitem>
+ <para>As of &DISTRO; &DISTROVER;, firmware with full support
+ for ISO9660 file systems is not yet released for the
+ Pegasos. However, the network boot image can be used. At
+ the OpenFirmware prompt, enter the command: </para>
+<screen>
+<command>boot cd: /images/netboot/ppc32.img</command>
+</screen>
+ <para>
+ You will also need to configure OpenFirmware on the Pegasos
+ manually to make the installed &FC; system bootable. To do
+ this, you need to set the <envar>boot-device</envar> and
+ <envar>boot-file</envar> environment variables
+ appropriately.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Network booting</term>
+ <listitem>
+ <para>There are combined images containing the installer
+ kernel and ramdisk in the images/netboot/ directory of the
+ install tree. These are intended for network booting with
+ TFTP, but can be used in many ways.
+ </para>
+ <para>
+ The command <command>yaboot</command> supports tftp
+ booting for IBM eServer pSeries and Apple Macintosh.
+ &FED; recommends using yaboot over the netboot images.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section>
<title>Anaconda Notes</title>
Index: java-package-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/java-package-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- java-package-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ java-package-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -1,5 +1,12 @@
-<section>
+<section id="sn-java-packages">
<title>Java Package Recommendations</title>
+ <caution>
+ <title>Information Out-of-Date</title>
+ <para>
+ The content in this section needs to be updated for &DISTRO;
+ &DISTROVER;
+ </para>
+ </caution>
<para>
&FC; &LOCALVER; users are advised not to use the Java RPM provided
by Sun. It contains <computeroutput>Provides</computeroutput> that
@@ -10,8 +17,8 @@
<para>
&FC; &LOCALVER; users should use either the RPM from jpackage.org or
manually install the Sun Java tarball into
- /opt<filename></filename>. Sun Java 1.5+ is recommended for
- stability purposes.
+ <filename>/opt</filename>. <!-- Sun Java 1.5+ is recommended for
+ stability purposes. -->
</para>
</section>
<!--
Index: kernel-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/kernel-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- kernel-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ kernel-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -18,19 +18,19 @@
<section id="sn-kernel-lotsa">
<title>Version</title>
<para>
- The &DISTRO; is based on a 2.6.11 kernel. &FC; may include
+ The distribution is based on the 2.6 series of the Linux kernel. &FC; may include
additional patches for improvements, bug fixes, or additional
features. For this reason, the &FC; kernel may not be
- line-for-line equivalent to the so-called vanilla kernel from the
+ line-for-line equivalent to the vanilla<firstterm></firstterm> kernel from the
<ulink
url="http://www.kernel.org"><filename>kernel.org</filename></ulink>
- web site.
+ website.
</para>
<para>
You may obtain a list of any such patches by using the command on the &FC; package:
</para>
<screen width="56">
-<command>rpm <parameter class="option">-qpl</parameter> <filename>kernel-<replaceable><version></replaceable>.src.rpm</filename></command>
+<command>rpm <parameter class="option">-qpl</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
</screen>
</section>
<section id="sn-kernel-flavors">
@@ -40,51 +40,46 @@
</para>
<itemizedlist>
<listitem>
- <para>
- Native kernel, in both uniprocessor and <abbrev>SMP</abbrev>
- varieties.
- </para>
- <para>
- Configured sources are available in the
- <filename>kernel-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
- package.
+ <para>Native kernel, in both uniprocessor and
+ <abbrev>SMP</abbrev> varieties. Configured sources are
+ available in the
+ <filename>kernel-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>
+ package.
</para>
</listitem>
<listitem>
<para>
- Virtual kernel for use with the <wordasword>Xen</wordasword> emulator package.
- </para>
- <para>
- Configured sources are available in the
- <filename>kernel-xen0-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
- package.
+ Virtual kernel for use with the <application>Xen</application>
+ emulator package. Configured sources are available in the
+ <filename>kernel-xen0-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>
+ package.
</para>
</listitem>
</itemizedlist>
<para>
Sources for both kernel flavors may be installed at the same time.
- The files will be installed into the
- <filename>/usr/src/kernels/<replaceable><version></replaceable>[-xen0]-<replaceable><arch></replaceable>/</filename>
+ The files are installed into the
+ <filename>/usr/src/kernels/<replaceable>version</replaceable>[-xen0]-<replaceable>arch</replaceable>/</filename>
tree. Use the command:
</para>
<screen width="56">
-<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-devel[-xen0]-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename></command>
+<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename></command>
</screen>
<para>
as appropriate.
</para>
<tip>
- <title>Following Generic Textbooks</title>
+ <title>Following Generic Textbooks About the Linux Kernel</title>
<para>
Many of the tutorials, examples, and textbooks about Linux
- kernel development assume the kernel sources are installed under
- the <filename>/usr/src/linux</filename> directory. If you make a
- symbolic link, as shown below, you should be able to use those
- learning materials with the &FC; packages. Install the
- appropriate kernel sources, as shown earlier, and then:
+ kernel development assume the kernel sources are installed under
+ the <filename>/usr/src/linux</filename> directory. If you make a
+ symbolic link, as shown below, you should be able to use those
+ learning materials with the &FC; packages. Install the
+ appropriate kernel sources, as shown earlier, and then:
</para>
<screen width="56">
-<command>ln <parameter class="option">-s</parameter> <filename>/usr/src/kernels/kernel-<replaceable><all-the-rest></replaceable></filename> <filename>/usr/src/linux</filename></command>
+<command>ln <parameter class="option">-s</parameter> <filename>/usr/src/kernels/kernel-<replaceable>all-the-rest</replaceable></filename> <filename>/usr/src/linux</filename></command>
</screen>
</tip>
</section>
@@ -99,7 +94,7 @@
-e</command> to remove older versions of the kernel packages.
</para>
<para>
- When using <command>rpm -e kernel-<replaceable><version></replaceable> </command> to remove the kernel, you must also remove the assisting user-space packages. You may wish to consider a dependency resolving tool such as <command>yum remove kernel-<replaceable><version></replaceable> </command>.
+ When using <command>rpm -e kernel-<replaceable>version</replaceable> </command> to remove the kernel, you must also remove the assisting user-space packages. You may wish to consider a dependency resolving tool such as <command>yum remove kernel-<replaceable>version</replaceable> </command>.
This automatically removes any dependent packages.
</para>
</tip>
@@ -122,12 +117,12 @@
<important>
<title>These Instructions Refer to the Currently-running Kernel!</title>
<para>
- To simplify the following directions, we have assumed that you
- want to configure the kernel sources to match your
- currently-running kernel. In the steps below, you must
- understand that the phrase
- <replaceable><version></replaceable> refers to the kernel
- version shown by this command:
+ To simplify the following directions, the assumption is that you
+ want to configure the kernel sources to match your
+ currently-running kernel. In the steps below, you must
+ understand that the phrase
+ <replaceable>version</replaceable> refers to the kernel
+ version shown by this command:
</para>
<screen width="56">
<command>uname <parameter class="option">-r</parameter></command>
@@ -137,26 +132,24 @@
<step>
<para>
Obtain the
- <filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
- file from one of the following sources:
+ <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename>
+ file from one of the following sources:
</para>
<itemizedlist>
<listitem>
- <para>
- The <filename>SRPMS</filename> directory on the
- appropriate <wordasword>SRPMS</wordasword>
- <abbrev>CD</abbrev> <filename>iso</filename> image.
+ <para>The <filename>SRPMS/</filename> directory on the
+ appropriate <wordasword>SRPMS</wordasword>
+ <abbrev>CD</abbrev> <filename>ISO</filename> image.
</para>
</listitem>
<listitem>
- <para>
- The FTP site where you got the kernel package.
+ <para>The FTP site where you got the kernel package.
</para>
</listitem>
<listitem>
- <para>
- By running the following command:
+ <para>By running the following command:
</para>
+<!-- FIXME up2date is sorta deprecated for FC, how to do this with yum? -->
<screen width="56">
<command>up2date <parameter class="option">--get-source</parameter> <filename>kernel</filename></command>
</screen>
@@ -166,16 +159,16 @@
<step>
<para>
Install
- <filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
- using the command:
+ <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename>
+ using the command:
</para>
<screen width="56">
-<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-<replaceable><version></replaceable>.src.rpm</filename></command>
+<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
</screen>
<para>
This writes the <abbrev>RPM</abbrev> contents into
- <filename>/usr/src/redhat/SOURCES</filename> and
- <filename>/usr/src/redhat/SPECS</filename>.
+ <filename>/usr/src/redhat/SOURCES</filename> and
+ <filename>/usr/src/redhat/SPECS</filename>.
</para>
</step>
<step>
@@ -187,57 +180,73 @@
<command>rpmbuild <parameter class="option">-bp --target $(arch)</parameter> <filename>kernel-2.6.spec</filename></command>
</screen>
<para>
- The kernel source tree will be located in the
- <filename>/usr/src/redhat/BUILD/kernel-</filename><replaceable><version></replaceable>
- directory. It is common practice to move the resulting
- <filename>linux-</filename><replaceable><version></replaceable>
- directory to the <filename>/usr/src</filename> tree; while not
- strictly necessary, we suggest that you do this to match the
- generally-available documentation.
+ The kernel source tree is located in the
+ <filename>/usr/src/redhat/BUILD/kernel-</filename><replaceable>version</replaceable>
+ directory. It is common practice to move the resulting
+ <filename>linux-<replaceable>version</replaceable></filename>
+ directory to the <filename>/usr/src</filename> tree; while not
+ strictly necessary, doing so matches you with the
+ generally-available documentation.
</para>
<screen width="56">
-<command>cd <filename>/usr/src/redhat/BUILD/kernel-<replaceable><version></replaceable></filename> <filename>/usr/src/</filename></command>
-<command>mv <filename>linux-<replaceable><version></replaceable></filename> <filename>/usr/src/</filename></command>
+<command>cd <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
+<command>mv <filename>linux-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
<command>cd <filename>/usr/src</filename></command>
-<command>ln <parameter class="option">-s</parameter> <filename>./linux-<replaceable><version></replaceable></filename> <filename>linux</filename></command>
+<command>ln <parameter class="option">-s</parameter> <filename>./linux-<replaceable>version</replaceable></filename> <filename>linux</filename></command>
<command>cd <filename>/usr/src/linux</filename></command>
</screen>
</step>
<step>
<para>
The configurations for the specific kernels shipped in
- &DISTRO; &DISTROVER; are in the <filename>configs/</filename>
- directory. For example, the i686 SMP configuration file is
- named
- <filename>configs/kernel-<replaceable><version></replaceable>-i686-smp.config</filename>.
- Issue the following command to place the desired configuration
- file in the proper place for building:
+ &DISTRO; &DISTROVER; are in the <filename>configs/</filename>
+ directory. For example, the i686 SMP configuration file is
+ named
+ <filename>configs/kernel-<replaceable>version</replaceable>-i686-smp.config</filename>.
+ Issue the following command to place the desired configuration
+ file in the proper place for building:
</para>
<screen width="56">
-<command>cp <filename>configs/<replaceable><desired-config-file></replaceable></filename> <filename>.config</filename></command>
+<command>cp <filename>configs/<replaceable>desired-config-file</replaceable></filename> <filename>.config</filename></command>
</screen>
<para>
- You can also find the <filename>.config</filename> file that matches your current kernel configuration in the <filename>/lib/modules/</filename><replaceable><version></replaceable><filename>/build/.config</filename> file.
+ You can also find the <filename>.config</filename> file that
+ matches your current kernel configuration in the
+ <filename>/lib/modules/</filename><replaceable>version</replaceable><filename>/build/.config</filename>
+ file.
</para>
</step>
<step>
<para>
- Every kernel gets a name based on its version number.
- This is the value the <command>uname -r</command> command displays.
- The kernel name is defined by the first four lines of the kernel <filename>Makefile</filename>.
- To protect the innocent, the <filename>Makefile</filename> has been changed to generate a kernel with a different name from that of the running kernel.
- Before a module can be accepted by the running kernel, that
- module must have been compiled for a kernel with the correct
- name. To do this, you must edit the kernel <filename>Makefile</filename>
- </para>
- <para>
- For example, if the <command>uname -r</command> returns the string <systemitem class="osname">2.6.11-1.234_FC4</systemitem>, change the <systemitem class="macro">EXTRAVERSION</systemitem> definition from this:
- </para>
- <screen width="60">EXTRAVERSION = -prep</screen>
- <para>to this:</para>
- <screen width="60">EXTRAVERSION = -1.234_FC4</screen>
+ Every kernel gets a name based on its version number. This is
+ the value the <command>uname -r</command> command displays.
+ The kernel name is defined by the first four lines of the
+ kernel <filename>Makefile</filename>. To protect the innocent,
+ the <filename>Makefile</filename> has been changed to generate
+ a kernel with a different name from that of the running
+ kernel. Before a module can be accepted by the running kernel,
+ that module must have been compiled for a kernel with the
+ correct name. To do this, you must edit the kernel
+ <filename>Makefile</filename>
+ </para>
+ <para>
+ For example, if the <command>uname -r</command> returns the
+ string <systemitem
+ class="osname">2.6.11-1.234_FC4</systemitem>, change the
+ <systemitem class="macro">EXTRAVERSION</systemitem> definition
+ from this:
+ </para>
+<screen width="60">
+EXTRAVERSION = -prep
+</screen>
+ <para>
+ to this:
+ </para>
+<screen width="60">
+EXTRAVERSION = -1.234_FC4
+</screen>
<para>
- that is, substitute everything from the final dash onward.
+ That is, substitute everything from the final dash onward.
</para>
</step>
<step>
@@ -287,13 +296,12 @@
utilities, such as management daemons. Consequently, to remove
such a kernel, perhaps after an update, you
<emphasis>cannot</emphasis> simply use the <command>rpm -e
- kernel-<replaceable><version></replaceable></command>
- command as in earlier distributions because these user space
- packages depend on the kernel package. You may either list both
- the kernel package and its user space dependent packages on the
- <command>rpm -e</command> command, or you may wish to use the
- <command>yum remove
- kernel-<replaceable><version></replaceable></command>
+ kernel-<replaceable>version</replaceable></command> command as
+ in earlier distributions because these user space packages depend
+ on the kernel package. You may either list both the kernel package
+ and its user space dependent packages on the <command>rpm
+ -e</command> command, or you may wish to use the <command>yum
+ remove kernel-<replaceable>version</replaceable></command>
command instead since <command>yum</command> automatically removes
dependent packages if necessary.
</para>
Index: multimedia-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/multimedia-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- multimedia-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ multimedia-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -1,9 +1,99 @@
<section id="sn-multimedia">
<title>Multimedia</title>
<para>
- This section contains information related to multimedia
- applications.
+ &FC; includes applications for assorted multimedia functions,
+ including playback, recording, and editing. Additional packages are
+ available through the &FEX; repository.
</para>
+ <variablelist>
+ <varlistentry>
+ <term>Multimedia Players</term>
+ <listitem>
+ <para>By default, &FC; installs with
+ <filename>rhythmbox</filename>, <filename>totem</filename>,
+ and <application>Helix Player</application>
+ (<command>hxplay</command>) for media playback. In addition,
+ many other programs are available in the &FC; and &FEX;
+ repositories, including the popular xmms package. Both GNOME
+ and KDE also have specific sets of programs that can be used
+ with a variety of formats. Other popular programs, such as
+ Adobe/Macromedia's Flash Player, Real Player, VLC, MPlayer,
+ and Xine, can also be installed, but are excluded from the
+ &FED; repositories since they are not compatible with &FED;'s
+ licensing or are usually distributed with support for
+ restricted formats. For more on this, refer to <xref
+ linkend="sn-multimedia-excluded"/>.
+ </para>
+ <para>
+ &FC; is also equipped to take full advantage of the Advanced
+ Linux Sound Architecture (ALSA) sound system. This means that
+ many programs can play sound simultaneously, which was once
+ difficult on Linux systems. When all multimedia software is
+ configured to use ALSA for sound support, this old limitation
+ disappears. For more information about ALSA, visit the
+ project website:
+ </para>
+ <para>
+ <ulink url='http://www.alsa-project.org/'>http://www.alsa-project.org/</ulink>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Ogg and Xiph.Org Foundation Formats</term>
+ <listitem>
+ <para>Fedora includes complete support for the Ogg media
+ container format, the Vorbis audio, Theora video, Speex audio,
+ and FLAC lossless audio formats. More information on these
+ formats and how to use them can be found at the Xiph.Org
+ Foundation's web site:
+ </para>
+ <para>
+ <ulink url='http://www.xiph.org/'>http://www.xiph.org/</ulink>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>MP3 & DVD Support</term>
+ <listitem>
+ <para>&FC; and &FEX; cannot include support for MP3 or DVD
+ playback or recording, because the MP3 and MPEG (DVD) formats
+ are patented, and the patent owners have not provided the
+ necessary licenses. For more information, refer to <xref
+ linkend="sn-multimedia-exluded"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <section id="sn-multimedia-excluded">
+ <title>Excluded Multimedia Software</title>
+ <para>
+ Several programs are excluded from &FC; and &FEX; due to licensing
+ issues. These include programs that provide MP3 and DVD support,
+ Flash Player and Real Player. Users who wish to use these
+ programs or restricted formats have to acquire additional
+ packages from third-party repositories. Many of the multimedia
+ applications in the Fedora repositories support plugins, so
+ support for new formats can be easily added or removed. For more
+ on this subject, please see:
+ </para>
+ <para>
+ <ulink url='http://fedoraproject.org/wiki/ForbiddenItems'>http://fedoraproject.org/wiki/ForbiddenItems</ulink>
+ </para>
+ </section>
+ <section id="sn-multimedia-cd-dvd-burning">
+ <title>CD and DVD Authoring and Burning</title>
+ <para>
+ Tools are included in &FC; and &FEX; for easily mastering and
+ burning CDs and DVDs. Tools that can be used from the console
+ include <command>cdrecord</command>, <command>readcd</command>,
+ <command>mkisofs</command>, and other typical Linux applications.
+ For GNOME users, the <filename>xcdroast</filename> package from
+ &FC; and the <filename>graveman</filename> package from &FEX;
+ allow easy preparation of audio and data discs. For KDE users,
+ the <filename>k3b</filename> package provides a very robust tool
+ for these tasks.
+ </para>
+ </section>
</section>
<!--
Local variables:
Index: networking-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/networking-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- networking-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ networking-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -1,5 +1,218 @@
<section id="sn-networking">
<title>Networking</title>
+ <variablelist>
+ <title>Major Kernel Changes 2.6.11 - 2.6.14</title>
+ <varlistentry>
+ <term>IPv4 Address Promotion</term>
+ <listitem>
+ <para>Starting with version 2.6.12 of the kernel a new feature has
+ been added called named address promotion. It allows secondary IPv4
+ addresses to be promoted to primary addresses. Usually when the
+ primary address is deleted all secondary addresses are deleted
+ as well. By enabling the new <command>sysctl</command>
+ <option>net.ipv4.conf.all.promote_secondaries</option> (or one of the
+ interface specific variants) this behaviour can be changed to
+ promote one of the secondary addresses to be the new primary
+ address.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Configurable Source Address for ICMP Errors</term>
+ <listitem>
+ <para>
+ The current behaviour when selecting the source address for
+ ICMP error messages is to use the address of the interface the
+ ICMP error is going to be sent out. Kernel version 2.6.12
+ introduces a new <command>sysctl</command>
+ <option>net.ipv4.icmp_errors_use_inbound_ifaddr</option> which
+ allows to change this behaviour to use the address of the
+ interface which has received the original packet causing the
+ error.
+ </para>
+ <para>
+ For example, the kernel receives an ICMP echo request on
+ <computeroutput>eth0</computeroutput>. Because the new
+ <command>sysctl</command> option is enabled, this causes the
+ ICMP echo reply to be sent out via
+ <computeroutput>eth1</computeroutput>. The address of
+ <computeroutput>eth0</computeroutput> is used when the default
+ behaviour would use the address of
+ <computeroutput>eth</computeroutput>.
+ </para>
+ <para>
+ This may ease network debugging in asynchronous routing
+ setups.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>LC-Trie Based Routing Lookup Algorithm</term>
+ <listitem>
+ <para>
+ A new routing lookup algorithm called
+ <firstterm>trie</firstterm> has been added. It is intended for
+ large routing tables and shows a clear performance improvement
+ over the original hash implementation at the cost of increased
+ memory consumption and complexity.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Pluggable Congestion Control Algorithm Infrastructure</term>
+ <listitem>
+ <para>TCP congestion control algorithms are now pluggable and
+ thus modular. The legacy <firstterm>new RENO</firstterm>
+ algorithm stays default and acts as fallback algorithm. During
+ the period of this work the following new congestion control
+ algorithms have been added:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>High Speed TCP congestion control.
+ </para>
+ </listitem>
+ <listitem>
+ <para>TCP Hybla congestion avoidance.
+ </para>
+ </listitem>
+ <listitem>
+ <para>H-TCP congestion control.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Scalable TCP congestion control.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>All existing congestion control modules have been
+ converted to this new infrastructure and the BIC congestion
+ control has received enhancements from BICTCP 1.1 to handle
+ low latency links.
+ </para>
+ <note>
+ <title>Affecting the Congestion Control Algorithm</title>
+ <para>
+ An interesting addition for developers is that the
+ congestion control algorithm is socket specific and can be
+ changed via the socket option
+ <option>TCP_CONGESTION</option>.
+ </para>
+ </note>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Queue Avoidance upon Carrier Loss</term>
+ <listitem>
+ <para>When a network driver notices a carrier loss, for example
+ when the cable is pulled out, the driver stops the queue in
+ front of the driver. This has been causing the packets to be
+ queued at the queueing discipline layer for an unbound period
+ of time causing unexpected effects. In order to prevent this
+ effect, the core networking stack now ceases to accept any
+ packets for queueing for any device that is operationally
+ down, that is, has its queue disabled.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>DCCP Protocol Support</term>
+ <listitem>
+ <para>Kernel version 2.6.14-rc1 was the first version to receive
+ support for the DCCP protocol. The implementation is still
+ experimental but known to work. Work to make userspace
+ applications aware of this new protocol has started.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Wireless</term>
+ <listitem>
+ <para>A new driver named HostAP has been added to 2.6.14-rc1
+ allowing the emulation of a wireless access point in software.
+ Currently this driver only works for Intersil Prism2-based
+ cards (PC Card/PCI/PLX). Support for wireless cards Intel(R)
+ PRO/Wireless 2100 and 2200 has been added.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Miscellaneous</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>A lot of TCP Segmentation Offloading (TSO) related
+ fixes have been included.
+ </para>
+ </listitem>
+ <listitem>
+ <para>A new textsearch infrastructure has been added
+ useable with the corresponding iptables and extended
+ match.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Both the IPv4 and IPv6 multicast joining interface
+ visible by userspace have been reworked and brought up to
+ the latest standards.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The SNMPv2 MIB counter ipInAddrErrors is finally
+ supported for IPv4.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Various new socket options proposed in Advanced API
+ (RFC3542) have been added.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <section sn="kernel-userspace-tools">
+ <title>Userspace Tools</title>
+ <title>iproute</title>
+ <para>
+ The IPv4 address deletion algorithm did not take the prefix
+ length into account up to kernel version 2.6.12. Since this has
+ changed the iproute2 tool now issues a warning if no prefix length
+ is provided to warn about possible unintended deletions:
+ </para>
+<screen>
+ip addr list dev eth0
+4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
+ inet 10.0.0.3/24 scope global eth0
+su -c 'ip addr del 10.0.0.3 dev eth0'
+Warning: Executing wildcard deletion to stay compatible with old
+ scripts. Explicitly specify the prefix length (10.0.0.3/32) to
+ avoid this warning. This special behaviour is likely to disappear
+ in further releases, fix your scripts!
+</screen>
+ <para>
+ The correct method of deleting the address and thus avoiding the
+ warning is:
+ </para>
+<screen>
+su -c 'ip addr del 10.0.0.3/24 dev eth0'
+</screen>
+ <para>
+ It has not been possible to tell if an interface is down
+ administratively or because no carrier can be found (cable
+ unplugged). The flag <computeroutput>NO-CARRIER</computeroutput>
+ has been introduced that shows up as a link flag if the link is
+ administratively up but no carrier can be found.
+ </para>
+ <para>
+ The <command>ip</command> command now supports a batch mode via
+ the argument <option>-batch</option> just like the
+ <command>tc</command> command to speed up batches of tasks.
+ </para>
+ </section>
+</section>
+
+<!-- cruft, but saved just in case :)
<para>
This section contains information relating to network connectivity.
</para>
@@ -42,7 +255,7 @@
that cannot be included with &DISTRO;. This software must be
installed separately for <command>NetworkManager</command> to function.
</para>
-
+-->
<!--
Local variables:
mode: xml
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.1 -r 1.2 package-movement-en.xml
Index: package-movement-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-movement-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- package-movement-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ package-movement-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -1,2586 +1,1071 @@
- <section id="sn-package-movement">
- <title>Packages Movement</title>
+<section id="sn-package-movement">
+ <title>Packages Movement</title>
<!--
FIXME
Needs updating of entire contents for FC4.
-->
- <section id="sn-packages-moved">
- <title>Packages Moved to &FEX;</title>
- <para>
- These are some of the packages that have moved from &CORE; to
- &FEX;. These are active packages that are maintained and
- supported by the &FP;. If you are looking for information about
- &EX;, refer to this URL:
+ <para>
+ This command was used to generate the list of package changes. The
+ backslash <computeroutput>\</computeroutput> is used to artificially
+ break the line for printing purposes.:
+ </para>
+<screen>
+<command>treediff.py dist-fc4 dist-rawhide > /tmp/diff \
+sed -e 's,^,* ,g' -e 's,$,\n,g' /tmp/diff > diffwiki</command>
+</screen>
+ <section>
+ <title>Package Changes</title>
+ <para>As of 21st September 2005 </para>
+ <para>[106429] MAKEDEV-3.19-1 -> [115423] MAKEDEV-3.19-4 </para>
+ <para>[111566] <ulink
+ url='/ImageMagick'>ImageMagick</ulink>-6.2.2.0-2 -> [112246]
+ <ulink url='/ImageMagick'>ImageMagick</ulink>-6.2.2.0-4 </para>
+ <para>[105261] newt-0.51.6-7 -> [117695] newt-0.51.6-8 </para>
+ <para>[106878] am-utils-6.0.9-12 -> [117066] am-utils-6.1.1-2
</para>
- <para>
- <ulink
- url="http://fedoraproject.org/wiki/Extras">http://fedoraproject.org/wiki/Extras</ulink>
+ <para>[108819] amanda-2.4.5-2 -> [115871] amanda-2.4.5-3 </para>
+ <para>[112105] anaconda-10.2.1.5-2 -> [118390]
+ anaconda-10.3.0.24-1 </para>
+ <para>[105300] aspell-0.50.5-6 -> [114172] aspell-0.60.3-2 </para>
+ <para>[108035] aspell-ca-0.50-2 -> [114184] aspell-ca-0.50-4
+ </para>
+ <para>[108036] aspell-cs-0.51-2 -> [114270] aspell-cs-0.51-3
+ </para>
+ <para>[108038] aspell-da-0.50-11 -> [114276] aspell-da-0.50-12
+ </para>
+ <para>[106443] libsoup-2.2.3-2 -> [116988] libsoup-2.2.6.1-1
+ </para>
+ <para>[108042] aspell-es-0.50-11 -> [117058] aspell-es-0.50-13
+ </para>
+ <para>[108044] aspell-fr-0.50-8 -> [114285] aspell-fr-0.50-9
+ </para>
+ <para>[108051] aspell-it-0.53-2 -> [114362] aspell-it-0.53-3
+ </para>
+ <para>[108055] aspell-nl-0.50-6 -> [114363] aspell-nl-0.50-7
+ </para>
+ <para>[108058] aspell-no-0.50.1-8 -> [114366] aspell-no-0.50.1-9
+ </para>
+ <para>[108060] aspell-pl-0.51-3 -> [118018] aspell-pl-0.51-5
+ </para>
+ <para>[108061] aspell-sv-0.50-7 -> [114371] aspell-sv-0.50-8
+ </para>
+ <para>[107959] at-3.1.8-77_FC4 -> [112026] at-3.1.8-78 </para>
+ <para>[108132] gtkhtml3-3.6.2-1 -> [117587] gtkhtml3-3.8.0-1
+ </para>
+ <para>[108304] ntp-4.2.0.a.20040617-8 -> [117060]
+ ntp-4.2.0.a.20050816-1 </para>
+ <para>[108909] autofs-4.1.4-5 -> [112718] autofs-4.1.4-9 </para>
+ <para>[102923] automake-1.9.5-1 -> [114414] automake-1.9.6-1
+ </para>
+ <para>[108562] autorun-3.16-1 -> [118091] autorun-3.17-1 </para>
+ <para>[105321] awesfx-0.5.0d-2 -> [113536] awesfx-0.5.0d-3 </para>
+ <para>[105808] nut-2.0.1-1 -> [114509] nut-2.0.2-1 </para>
+ <para>[110344] bash-3.0-31 -> [118423] bash-3.0-34 </para>
+ <para>[110908] bind-9.3.1-4 -> [116915] bind-9.3.1-11 </para>
+ <para>[111486] binutils-2.15.94.0.2.2-2 -> [116754]
+ binutils-2.16.91.0.2-4 </para>
+ <para>[105319] bootparamd-0.17-22.devel -> [116780]
+ bootparamd-0.17-23.devel </para>
+ <para>[106988] bug-buddy-2.10.0-1 -> [117633] bug-buddy-2.12.0-1
+ </para>
+ <para>[111028] bzip2-1.0.2-16 -> [117182] bzip2-1.0.3-1 </para>
+ <para>[106470] pax-3.0-11 -> [116422] pax-3.4-1 </para>
+ <para>[109185] <ulink url='/SysVinit'>SysVinit</ulink>-2.85-39 ->
+ [113360] <ulink url='/SysVinit'>SysVinit</ulink>-2.85-40 </para>
+ <para>[111393] control-center-2.10.1-6 -> [118105]
+ control-center-2.12.0-2 </para>
+ <para>[111120] openldap-2.2.23-5 -> [111936] openldap-2.2.26-1
+ </para>
+ <para>[110745] cpio-2.6-7 -> [113389] cpio-2.6-8 </para>
+ <para>[106419] cracklib-2.8.2-1 -> [111862] cracklib-2.8.3-1
+ </para>
+ <para>[104496] bluez-hcidump-1.18-1 -> [115995]
+ bluez-hcidump-1.24-1 </para>
+ <para>[104877] ctags-5.5.4-3 -> [115419] ctags-5.5.4-4 </para>
+ <para>[108614] cvs-1.11.19-8 -> [116935] cvs-1.11.19-10 </para>
+ <para>[108252] cyrus-sasl-2.1.20-5 -> [117833] cyrus-sasl-2.1.21-5
+ </para>
+ <para>[109650] pam-0.79-8 -> [118330] pam-0.80-8 </para>
+ <para>[109663] dhcp-3.0.2-12 -> [117972] dhcp-3.0.3-6 </para>
+ <para>[110743] apr-0.9.6-3 -> [118164] apr-0.9.6-6 </para>
+ <para>[110347] e2fsprogs-1.37-4 -> [117739] e2fsprogs-1.38-1
+ </para>
+ <para>[104668] diffstat-1.38-2 -> [116208] diffstat-1.38-4 </para>
+ <para>[107298] doxygen-1.4.2-1 -> [118248] doxygen-1.4.4-2 </para>
+ <para>[110505] dump-0.4b40-2 -> [113542] dump-0.4b40-4 </para>
+ <para>[110508] eject-2.0.13-15 -> [117061] eject-2.1.2-1 </para>
+ <para>[110262] parted-1.6.22-2 -> [117238] parted-1.6.24-1 </para>
+ <para>[110911] emacs-21.4-5 -> [114092] emacs-21.4-7 </para>
+ <para>[111808] esound-0.2.35-5 -> [114327] esound-0.2.36-1 </para>
+ <para>[105304] passwd-0.69-2 -> [112701] passwd-0.70-1 </para>
+ <para>[106286] fetchmail-6.2.5-7 -> [114678] fetchmail-6.2.5.2-1
+ </para>
+ <para>[109759] patch-2.5.4-24 -> [117794] patch-2.5.4-29 </para>
+ <para>[111272] filesystem-2.3.4-1 -> [116817] filesystem-2.3.5-1
+ </para>
+ <para>[106330] findutils-4.2.20-1 -> [117490] findutils-4.2.25-2
+ </para>
+ <para>[105012] finger-0.17-28 -> [113967] finger-0.17-29 </para>
+ <para>[105097] freetype-2.1.9-2 -> [116586] freetype-2.1.9-4
+ </para>
+ <para>[111401] ftp-0.17-26 -> [117241] ftp-0.17-29 </para>
+ <para>[104499] gawk-3.1.4-5 -> [118359] gawk-3.1.5-2 </para>
+ <para>[111099] gcc-4.0.0-8 -> [118294] gcc-4.0.1-14 </para>
+ <para>[108458] gd-2.0.33-2 -> [117628] gd-2.0.33-3 </para>
+ <para>[109684] gdb-6.3.0.0-1.21 -> [117661] gdb-6.3.0.0-1.65
+ </para>
+ <para>[106626] gettext-0.14.3-1 -> [116274] gettext-0.14.5-1
+ </para>
+ <para>[111402] gdm-2.6.0.8-16 -> [117776] gdm-2.8.0.4-1 </para>
+ <para>[108333] gedit-2.10.2-3 -> [117719] gedit-2.12.0-1 </para>
+ <para>[110935] perl-5.8.6-15 -> [117489] perl-5.8.7-0.3.fc5
+ </para>
+ <para>[107237] gok-1.0.3-1 -> [116496] gok-1.0.5-4 </para>
+ <para>[110356] php-5.0.4-10 -> [118097] php-5.0.5-3 </para>
+ <para>[110581] gimp-2.2.7-4 -> [116538] gimp-2.2.8-3 </para>
+ <para>[111654] gnome-applets-2.10.1-9 -> [117721]
+ gnome-applets-2.12.0-1 </para>
+ <para>[111691] glibc-2.3.5-10 -> [117966] glibc-2.3.90-12 </para>
+ <para>[111104] gnome-games-2.10.0-5 -> [117724]
+ gnome-games-2.12.0-1 </para>
+ <para>[111214] gnome-media-2.10.2-4 -> [117726]
+ gnome-media-2.12.0-1 </para>
+ <para>[106508] kdeadmin-3.4.0-1 -> [118336] kdeadmin-3.4.2-2
+ </para>
+ <para>[110919] gnome-utils-2.10.0-3 -> [117738]
+ gnome-utils-2.12.0-1 </para>
+ <para>[110246] gnupg-1.4.1-3 -> [116120] gnupg-1.4.2-3 </para>
+ <para>[104528] gnuplot-4.0.0-7 -> [117403] gnuplot-4.0.0-8 </para>
+ <para>[104506] gperf-3.0.1-6 -> [115552] gperf-3.0.1-7 </para>
+ <para>[104548] grep-2.5.1-48 -> [113236] grep-2.5.1-50 </para>
+ <para>[108057] xinitrc-4.0.18-1 -> [111974] xinitrc-4.0.19-1
+ </para>
+ <para>[104544] guile-1.6.7-2 -> [117402] guile-1.6.7-4 </para>
+ <para>[104475] hdparm-5.9-1 -> [112183] hdparm-6.1-1 </para>
+ <para>[111501] initscripts-8.11.1-1 -> [117977] initscripts-8.14-1
+ </para>
+ <para>[107880] inn-2.4.2-3 -> [115559] inn-2.4.2-4 </para>
+ <para>[106114] iproute-2.6.11-1 -> [118247] iproute-2.6.14-3
+ </para>
+ <para>[106499] iptables-1.3.0-2 -> [114287] iptables-1.3.2-1
+ </para>
+ <para>[107881] iputils-20020927-22 -> [117698] iputils-20020927-26
+ </para>
+ <para>[111656] isdn4k-utils-3.2-28 -> [115009] isdn4k-utils-3.2-32
+ </para>
+ <para>[105032] joe-3.1-8 -> [112056] joe-3.3-1 </para>
+ <para>[108237] kdebase-3.4.0-5 -> [118422] kdebase-3.4.2-5 </para>
+ <para>[106532] kdegames-3.4.0-1 -> [116019] kdegames-3.4.2-1
+ </para>
+ <para>[107198] kdegraphics-3.4.0-2 -> [117508] kdegraphics-3.4.2-3
+ </para>
+ <para>[104526] openobex-1.0.1-3 -> [111937] openobex-1.0.1-4
+ </para>
+ <para>[107226] kdemultimedia-3.4.0-2 -> [115553]
+ kdemultimedia-3.4.2-1 </para>
+ <para>[106551] kdeutils-3.4.0-1 -> [117699] kdeutils-3.4.2-2
+ </para>
+ <para>[105322] minicom-2.00.0-21 -> [114175] minicom-2.1-1 </para>
+ <para>[112015] kernel-2.6.11-1.1369_FC4 -> [118394]
+ kernel-2.6.13-1.1565_FC5 </para>
+ <para>[108707] libbtctl-0.4.1-7 -> [114382] libbtctl-0.4.1-8
+ </para>
+ <para>[107067] krb5-1.4-3 -> [118053] krb5-1.4.2-4 </para>
+ <para>[106252] krbafs-1.2.2-7 -> [115422] krbafs-1.2.2-8 </para>
+ <para>[111032] kudzu-1.1.116.2-2 -> [118290] kudzu-1.2.7-1 </para>
+ <para>[105596] lam-7.1.1-3 -> [115564] lam-7.1.1-7.FC5 </para>
+ <para>[105047] less-382-7 -> [117533] less-382-8 </para>
+ <para>[104599] libieee1284-0.2.9-2 -> [114409] libieee1284-0.2.9-3
+ </para>
[...3253 lines suppressed...]
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> quanta-devel</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> raidtools</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> redhat-java-rpm-scripts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> rep-gtk</para>
- </listitem>
-
- <listitem arch="x86_64">
- <para><remark os="test">(x86_64)</remark> samba (i386)</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> sawfish</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> servletapi</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> servletapi-devel</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> shapecfg</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> struts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> struts-webapps</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> system-config-proc</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> tomcat</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> tomcat-devel</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> tomcat-libs</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> tomcat-test</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> unarj</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xalan-j</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xalan-j-devel</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xalan-j-xsltc</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xerces-j</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xerces-j-devel</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xffm-icons</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-100dpi-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-75dpi-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-14-100dpi-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-14-75dpi-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-15-100dpi-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-15-75dpi-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-2-100dpi-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-2-75dpi-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-9-100dpi-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-9-75dpi-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-base-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-cyrillic-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-libs-data</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-syriac-fonts</para>
- </listitem>
-
- <listitem arch="x86;x86_64">
- <para><remark os="test">(x86;x86_64)</remark> xorg-x11-truetype-fonts</para>
- </listitem>
- </itemizedlist>
- </section>
- <section>
- <title>Packages Deprecated</title>
-
- <para>The following packages have been deprecated, and may be removed from
- a future release of &DISTRO;:</para>
-
- <itemizedlist>
- <listitem>
- <para>dbskkd-cdb — Only used by deprecated package
- skkinput</para>
- </listitem>
-
- <listitem>
- <para>FreeWnn — Only used by deprecated package
- kinput2-canna-wnn6</para>
- </listitem>
-
- <listitem arch="x86">
- <para><remark os="test">(x86)</remark> lilo — GRUB is the
- recommended bootloader</para>
- </listitem>
-
- <listitem>
- <para>miniChinput — IIIMF is the recommended input method</para>
- </listitem>
-
- <listitem>
- <para>nabi — IIIMF is the recommended input method</para>
- </listitem>
-
- <listitem>
- <para>ncpfs — No longer part of &DISTRO; profile</para>
- </listitem>
-
- <listitem>
- <para>skkinput — IIIMF is the recommended input method</para>
- </listitem>
-
- <listitem>
- <para>xcin — IIIMF is the recommended input method</para>
- </listitem>
- </itemizedlist>
- </section>
--->
</section>
<!--
Local variables:
Index: package-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- package-notes-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ package-notes-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -29,7 +29,7 @@
<title>Package-Specific Notes</title>
<!--
FIXME
- Needs updating of entire contents for FC4.
+ Needs updating of entire contents for FC5.
-->
<para>
The following sections contain information regarding packages that
@@ -241,35 +241,6 @@
&SERVER-TOOLS;
&JAVA-PACKAGE;
</section>
- <!-- Saving these just in case ...
- <section os="bogus">
- <title>Administration Tools</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Authoring and Publishing</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Compatibility Arch Development Support</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Compatibility Arch Support</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
--->
<section id="sn-packages-core">
<title>Core</title>
<para>
@@ -285,612 +256,21 @@
<para>
The Fedora Extras repository is now enabled by default.
</para>
- </section>
+ </section>
&KERNEL;
&SECURITY;
</section>
-<!--
- <section>
- <title><filename>e2fsprogs</filename></title>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131918">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131918</ulink>
- %%%</remark>
-
- <para>The <filename>ext2online</filename> utility has been added for
- online growing of existing ext3 file systems.</para>
-
- <note>
- <title>Note</title>
-
- <para>It is important to keep in mind that
- <filename>ext2online</filename> does not grow the underlying block
- device itself — there must be sufficient unused space already
- present on the device. The easiest way to ensure this is to use LVM
- volumes and to run <filename>lvresize</filename> or
- <filename>lvextend</filename> to extend the device.</para>
- </note>
-
- <para>In addition, file systems must be specially prepared in order to
- be resized past a certain point. The preparation involves reserving a
- small amount of space into which on-disk tables can grow. For
- newly-created file systems, <filename>mke2fs</filename> reserves such
- space automatically; the space reserved is sufficient to grow the file
- system by a factor of 1000. The creation of this reserved space can
- be disabled by the following command:</para>
-
- <para><command>mke2fs -O ^resize_inode</command></para>
-
- <para>Future releases of &DISTRO; will allow the creation of this
- reserved space on existing file systems.</para>
- </section>
-
- <section>
- <title><filename>glibc</filename></title>
-
- <itemizedlist>
- <listitem>
- <remark os="test">%%% <ulink
- url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133267">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133267</ulink>
- %%%</remark>
-
- <para>The version of <filename>glibc</filename> provided with
- &DISTRO; &DISTROVER; performs additional internal sanity checks to
- prevent and detect data corruption as early as possible. By
- default, should corruption be detected, a message similar to the
- following will be displayed on standard error (or logged via
- syslog if stderr is not open):</para>
-
- <para><computeroutput>*** glibc detected *** double free or
- corruption: 0x0937d008 ***</computeroutput></para>
-
- <para>By default, the program that generated this error will also be
- killed; however, this (and whether or not an error message is
- generated) can be controlled via the <envar>MALLOC_CHECK_</envar>
- environment variable. The following settings are
- supported:</para>
-
- <itemizedlist>
- <listitem>
- <para>0 — Do not generate an error message, and do not
- kill the program</para>
- </listitem>
-
- <listitem>
- <para>1 — Generate an error message, but do not kill the
- program</para>
- </listitem>
-
- <listitem>
- <para>2 — Do not generate an error message, but kill the
- program</para>
- </listitem>
-
- <listitem>
- <para>3 — Generate an error message and kill the
- program</para>
- </listitem>
- </itemizedlist>
-
- <note>
- <title>Note</title>
-
- <para>If MALLOC_CHECK_ is explicitly set a value other than 0,
- this causes <filename>glibc</filename> to perform more tests
- that are more extensive than the default, and may impact
- performance.</para>
- </note>
-
- <para>Should you have a program from a third party ISV that triggers
- these corruption checks and displays a message, you should file a
- defect report with the application's vendor, since this indicates
- a serious bug.</para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title><filename>hotplug</filename></title>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136348">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136348</ulink>
- %%%</remark>
-
- <para>The location where <filename>hotplug</filename> expects firmware
- to be loaded into (for example, firmware for Cardbus cards) has
- changed from <filename>/usr/lib/hotplug/firmware</filename> to
- <filename>/lib/firmware</filename>. Existing firmware files must be
- moved into the new directory.</para>
- </section>
- -->
-<!--
- <section os="bogus">
- <title>DNS Name Server</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Development Libraries</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Development Tools</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Dialup Networking Support</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Editors</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Emacs</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Engineering and Scientific</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>FTP Server</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>GNOME</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>GNOME Desktop Environment</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
--->
- &DEVELOPMENT-TOOLS;
-<!--
- <section os="bogus">
- <title>Games and Entertainment</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Graphical Internet</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Graphics</title>
-
- <para>This section includes packages that help you manipulate and scan
- images.</para>
-
- </section>
-
- <section os="bogus">
- <title>ISO8859-2 Support</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>ISO8859-9 Support</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>KDE</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>KDE Desktop Environment</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>KDE Software Development</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Kernel Development</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
- -->
- <section>
- <title>Language Support</title>
- <para>
- This section includes information related to the support of various
- languages under &DISTRO;.
- </para>
- <section>
- <title>The IIIMF Input System</title>
- <para>
- IIIMF is the Internet/Intranet Input Method Framework. In &FC;
- &LOCALVER; the <filename>iiimf</filename> package is updated to
- version 12.2.
- </para>
- <variablelist>
- <varlistentry>
- <term>File Path Changes</term>
- <listitem>
- <para>
- The names and locations of some files in the
- <filename>iiimf</filename> packages have changed.
- </para>
- <para>
- The IIIMF server has been renamed from
- <filename>/usr/sbin/htt</filename> to
- <filename>/usr/bin/iiimd</filename>, and the XIM bridge
- client renamed from <filename>httx</filename> to
- <filename>iiimx</filename>. The
- <filename>init.d</filename> script name has not changed:
- it is still called <filename>iiim</filename>. All the
- global system configuration files are now located under
- <filename>/etc/iiim/</filename>.
- </para>
- <para>
- Language Engine (LE) developers should note that LE
- modules and their data now live under
- <filename>${libdir}/iiim/le/<filename><LE_NAME></filename>/</filename>,
- while runtime data is stored under
- <filename>/var/lib/iiim/le/<replaceable><LE_NAME></replaceable>/</filename>.
- </para>
- <para>
- For more information on the exact path and file location
- changes, please refer to Fedora IIIMF FAQ:
- </para>
- <para>
- <ulink
- url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Hotkeys</term>
- <listitem>
- <para>
- Trigger keys, such as
- <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>
- used to activate Input Methods, are now configurable with
- the command-line tool <command>iiimf-le-tools</command>.
- This feature is only supported by GTK2 applications
- currently. For other applications using XIM the trigger
- key can be changed using an X resource. Refer to the
- IIIMF FAQ at <ulink
- url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>
- for more details on how to change trigger hotkeys.
- </para>
- <para>
- Note that the keyname refers to the X key symbol name. For
- example, if you want to activate with
- <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>,
- you need to specify '<Control>at' as the keyname not
- '<Control>@'.
- </para>
- <para>
- The per-user configuration of hotkeys does not work
- currently with &SEL; in enforcing mode due to lack of
- &SEL; policy. In this case, the hotkey can only be
- changed in the system-wide configuration.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Qt Support</term>
- <listitem>
- <para>
- A Qt immodule for <filename>iiimf</filename> is now
- included. This immodule works but lacks a status window
- and is considered experimental. Therefore, the default
- for Qt applications is to continue using XIM for IIMF
- input.
- </para>
- <para>
- If you wish to try the immodule in a Qt application, first
- install the <filename>iiimf-qt</filename> package, start
- the application, then click mouse button-3 in an input
- area and select <guimenuitem>iiimqcf</guimenuitem> from
- the <guisubmenu>Select Input Method</guisubmenu>' submenu.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
- </section>
-<!-- keeping for historical informative purpose as a resource
- <itemizedlist>
- <listitem>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136409">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136409</ulink>
- %%%</remark>
-
- <para>The default Input Method (IM) for Chinese (Simplified and
- Traditional), Japanese, and Korean has been changed to IIIMF
- — the Internet/Intranet Input Method Framework. IIIMF is
- supported as a native GTK2 IM module, and also through XIM using
- the httx client. IIIMF supports the use of multiple Language
- Engines (LEs) at the same time; using the GNOME Input Method
- Language Engine Tool (<application>GIMLET</application> — an
- applet) it is possible to switch between LEs of different
- languages inside GTK2 applications.</para>
-
- <para>IIIMF currently defaults to using
- <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>
- or
- <keycombo><keycap>Shift</keycap><keycap>Space</keycap></keycombo>
- for toggling the input method on and off
- (<application>Emacs</application> users can use
- <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>
- instead of
- <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>
- to set the mark.)</para>
-
- <para>Depending on your selection at the language support screen
- during installation, one or more IIIMF language engines may be
- installed. The IIIMF server package
- (<filename>iiimf-server</filename>) will also be installed if a
- language engine has been selected. The language to language
- engine (LE) package mappings are as follows:</para>
-
- <itemizedlist>
- <listitem>
- <para>ja_JP — <filename>iiimf-le-canna</filename></para>
- </listitem>
-
- <listitem>
- <para>zh_CN — <filename>iiimf-le-chinput</filename></para>
- </listitem>
-
- <listitem>
- <para>zh_TW — <filename>iiimf-le-xcin</filename></para>
- </listitem>
-
- <listitem>
- <para>ko_KR — <filename>iiimf-le-hangul</filename></para>
- </listitem>
-
- <listitem>
- <para>{bn,gu,pa,ta,hi}_IN —
- <filename>iiimf-le-unit</filename></para>
- </listitem>
- </itemizedlist>
-
- <para>Accordingly, input via IIIMF will be enabled if you have
- chosen one of the following as your default locale:</para>
-
- <itemizedlist>
- <listitem>
- <para>ja_JP</para>
- </listitem>
-
- <listitem>
- <para>zh_CN</para>
- </listitem>
-
- <listitem>
- <para>zh_TW</para>
- </listitem>
-
- <listitem>
- <para>ko_KR</para>
- </listitem>
-
- <listitem>
- <para>{bn,gu,pa,ta,hi}_IN</para>
- </listitem>
- </itemizedlist>
-
- <para>To aid your use of IIIMF, if you have selected one of the
- above locales and you are using the GNOME Desktop, when you first
- login the <application>GIMLET</application> utility (part of the
- <filename>iiimf-gnome-im-switcher</filename> package) will
- automatically be added to your panel.</para>
-
- <para><application>GIMLET</application> is a utility for switching
- between the different LEs that are installed on your system.
- Using a different language engine allows you to enter text in
- different languages. Alternatively you may add
- <application>GIMLET</application> manually to your panel by right
- clicking on the panel and selecting:</para>
-
- <para><guimenuitem>Add to Panel</guimenuitem> ->
- <guimenuitem>GIMLET</guimenuitem></para>
-
- <para>Should you wish to switch between IIIMF or the legacy input
- method framework XIM, you can use the
- <application>system-switch-im</application> application. After
- changing the input method framework your changes will be reflected
- when you next start the X Window System.</para>
- </listitem>
- </itemizedlist>
- </section>
- <section os="bogus">
- <title>Legacy Software Development</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section>
- <title>Mail Server</title>
-
- <para>This section contains information related to the mail transport
- agents included with &DISTRO;.</para>
-
- <section>
- <title><filename>mailman</filename></title>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134015">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134015</ulink>
- %%%</remark>
-
- <para>Earlier <filename>mailman</filename> RPMs installed all files
- under the <filename>/var/mailman/</filename> directory.
- Unfortunately, this did not conform to the Filesystem Hierarchy
- Standard (FHS) and also created security violations when &SEL; was
- enabled.</para>
-
- <para>If you previously had <filename>mailman</filename> installed and
- had edited files in <filename>/var/mailman/</filename> (such as
- <filename>mm_cfg.py</filename>) you must move those changes to their
- new location, as documented in the following file:</para>
-
- <para><filename>/usr/share/doc/mailman-*/INSTALL.REDHAT</filename></para>
- </section>
-
- <section>
- <title><filename>sendmail</filename></title>
-
- <itemizedlist>
- <listitem>
- <para>By default, the Sendmail mail transport agent (MTA) does not
- accept network connections from any host other than the local
- computer. If you want to configure Sendmail as a server for other
- clients, you must edit <filename>/etc/mail/sendmail.mc</filename>
- and change the <parameter>DAEMON_OPTIONS</parameter> line to also
- listen on network devices (or comment out this option entirely using
- the <command>dnl</command> comment delimiter). You must then
- regenerate <filename>/etc/mail/sendmail.cf</filename> by running the
- following command (as root):</para>
-
- <para><command>make -C /etc/mail</command></para>
-
- <para>Note that you must have the <filename>sendmail-cf</filename>
- package installed for this to work.</para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
- <section os="bogus">
- <title>Network Servers</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>News Server</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Office/Productivity</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
--->
+ &DEVELOPMENT-TOOLS;
+ &I18N;
&PRINTING;
-<!--
- <section os="bogus">
- <title>Ruby</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
- <section os="bogus">
- <title>Server</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
--->
-<!-- not content for this release
- &DATABASE-SERVERS;
- &MULTIMEDIA; -->
-<!--
- <section os="bogus">
- <title>Supported Packages</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>System Tools</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>Text-based Internet</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
- -->
+<!-- no content for this release
+ &DATABASE-SERVERS; -->
+ &MULTIMEDIA;
+ &ENTERTAINMENT;
&WEB-SERVERS;
&SAMBA;
&XORG;
- <!-- <section os="bogus">
- <title>Workstation Common</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>X Software Development</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>XEmacs</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
- -->
+ &ENTERTAINMENT;
</section>
<!--
Local variables:
Index: security-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/security-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- security-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ security-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -3,25 +3,40 @@
<para>
This section highlights various security items from &FC;.
</para>
- <section id="sn-security-digital-certs">
- <title>Digital Certificates Consolidated</title>
+ <para>
+ <computeroutput>Pam_stack</computeroutput> is deprecated. More
+ details available from fedora-test-list (<ulink
+ url="http://www.redhat.com/mailman/listinfo/fedora-test-list">http://www.redhat.com/mailman/listinfo/fedora-test-list</ulink>
+ </para>
+ <section id="sn-security-highlights">
+ <title>Security Highlights</title>
<para>
- Digital certificates are now centralised in directories under
- <filename>/etc/pki/</filename>. Users performing an upgrade must
+ This section highlights various security items from &FC;.
+ </para>
+ <para>
+ Digital certificates are now centralised in directories
+ under <filename>/etc/pki/</filename>. Users performing an upgrade must
relocate their digital certificates.
</para>
<para>
- OpenSSL: the <filename>/usr/share/ssl</filename> contents have
- moved to <filename>/etc/pki/tls</filename> and
- <filename>/etc/pki/CA</filename>.
+ OpenSSL: the <filename>/usr/share/ssl/</filename> contents have
+ moved to <filename>/etc/pki/tls/</filename> and
+ <filename>/etc/pki/CA/</filename>.
+ </para>
+ <para>
+ Dovecot: A dovecot-openssl.cnf file is automatically installed in
+ <filename>/etc/pki/dovecot/</filename>.
</para>
+ </section>
+ <section id="sn-security-selinux-changes">
+ <title>SELinux Changes</title>
<para>
- Dovecot: A <filename>dovecot-openssl.cnf</filename> file is
- automatically installed in <filename>/etc/pki/dovecot/</filename>.
+ MCS SELinux is in somewhere. Major highlight. For more
+ information, read this informative article:
</para>
<para>
- For information about &SEL;, refer to <xref
- linkend="sn-overview"/>.
+ <ulink
+ url="http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/m...">http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/m...</ulink>
</para>
</section>
</section>
Index: server-tools-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/server-tools-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- server-tools-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ server-tools-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -1,5 +1,12 @@
<section id="sn-server-sys-config">
<title>Server and System Configuration Tools</title>
+ <caution>
+ <title>Information Out-of-Date</title>
+ <para>
+ The content in this section needs to be updated for &DISTRO;
+ &DISTROVER;
+ </para>
+ </caution>
<para>
This section highlights changes and additions to the various GUI server
and system configuration tools in &FC;.
Index: splash-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- splash-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ splash-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -1,5 +1,12 @@
<section id="sn-splash">
<title>Welcome to &FC; &LOCALVER;</title>
+ <caution>
+ <title>Information Out-of-Date</title>
+ <para>
+ The content in this section needs to be updated for &DISTRO;
+ &DISTROVER;
+ </para>
+ </caution>
<para>
&FC; is a completely free, user friendly, and secure general purpose
platform based on Linux. The &FP; is an open source project that
@@ -61,6 +68,7 @@
</para>
</listitem>
</itemizedlist>
+<!-- commented out until the content can be updated
<section id="sn-new-in-fc">
<title>New in &FC; &LOCALVER;</title>
<para>
@@ -358,6 +366,7 @@
find many interesting things with Google.
</para>
</section>
+-->
</section>
<!--
Local variables:
Index: web-servers-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/web-servers-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- web-servers-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ web-servers-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -1,73 +1,24 @@
<section id="sn-web-servers">
<title>Web Servers</title>
<para>
- This section contains information on Web-related
- applications.
+ This section contains information on Web-related applications.
</para>
- <section id="sn-web-servers-modperl">
- <title><filename>mod_perl</filename></title>
+ <section>
+ <title><command>httpd</command></title>
<para>
- The RC5 release of mod_perl 2.0 is now included. The API provided
- by this release is incompatible with previous 1.99_xx releases.
- Please refer to the following document for a discussion of how to
- adapt code to use the new API:
- </para>
- <para>
- <ulink
- url="http://perl.apache.org/docs/2.0/rename.html">http://perl.apache.org/docs/2.0/rename.html</ulink>
- </para>
- </section>
- <section id="sn-web-servers-php">
- <title><filename>php</filename></title>
- <para>
- Version 5.0 of PHP is now included, which includes a number of
- changes to the language along with significant performance
- improvements. Please refer to the PHP documentation for more
- information on migrating from PHP 4.3 to PHP 5.0:
- </para>
- <para>
- <ulink
- url="http://www.php.net/manual/en/migration5.php">http://www.php.net/manual/en/migration5.php</ulink>
- </para>
- <para>
- The <filename>/usr/bin/php</filename> binary is now built using
- the CLI command-line SAPI, rather than the CGI SAPI. Use
- <filename>/usr/bin/php-cgi</filename> for CGI SAPI. The
- <command>php-cgi</command> also includes FastCGI support.
- </para>
- <para>
- The following extensions have been added:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- The <command>mysqli</command> extension, a new interface
- designed specifically for MySQL 4.1. This is included in the
- <filename>php-mysql</filename> package.
- </para>
- </listitem>
- <listitem>
- <para>
- The <command>soap</command> extension, for implementing SOAP
- clients and servers.
- </para>
- </listitem>
- </itemizedlist>
- <para>
- The following extensions are now available as optional loadable
- extensions, rather than being built in to the PHP binaries:
+ The following changes have been made to the default <command></command>httpd
+ configuration:
</para>
<itemizedlist>
<listitem>
- <para>
- The <command>dba</command> extension, now available in the
- <filename>php-dba</filename> package
+ <para>The <computeroutput>mod_cern_meta</computeroutput> and
+ <computeroutput>mod_asis</computeroutput> modules are no
+ longer loaded by default.
</para>
</listitem>
<listitem>
- <para>
- The <command>bcmath</command> extension, now available in the
- <filename>php-bcmath</filename> package
+ <para>The <computeroutput>mod_ext_filter</computeroutput> module
+ is now loaded by default
</para>
</listitem>
</itemizedlist>
Index: xorg-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/xorg-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xorg-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ xorg-en.xml 25 Oct 2005 08:34:00 -0000 1.2
@@ -1,5 +1,12 @@
<section id="sn-xwindows">
<title>X Window System (Graphics)</title>
+ <caution>
+ <title>Information Out-of-Date</title>
+ <para>
+ The content in this section needs to be updated for &DISTRO;
+ &DISTROVER;
+ </para>
+ </caution>
<para>
This section contains information related to the X Window System
implementation provided with &DISTRO;.
18 years, 6 months
release-notes daemons-en.xml, NONE, 1.1 database-servers-en.xml, NONE, 1.1 desktop-en.xml, NONE, 1.1 development-tools-en.xml, NONE, 1.1 feedback-en.xml, NONE, 1.1 file-servers-en.xml, NONE, 1.1 file-systems-en.xml, NONE, 1.1 hardware-reqs-en.xml, NONE, 1.1 install-notes-en.xml, NONE, 1.1 intro-en.xml, NONE, 1.1 java-package-en.xml, NONE, 1.1 kernel-en.xml, NONE, 1.1 misc-server-en.xml, NONE, 1.1 multimedia-en.xml, NONE, 1.1 networking-en.xml, NONE, 1.1 overview-en.xml, NONE, 1.1 package-movement-en.xml, NO
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11423
Modified Files:
fedora.css
Added Files:
daemons-en.xml database-servers-en.xml desktop-en.xml
development-tools-en.xml feedback-en.xml file-servers-en.xml
file-systems-en.xml hardware-reqs-en.xml install-notes-en.xml
intro-en.xml java-package-en.xml kernel-en.xml
misc-server-en.xml multimedia-en.xml networking-en.xml
overview-en.xml package-movement-en.xml package-notes-en.xml
printing-en.xml project-overview-en.xml samba-en.xml
security-en.xml server-tools-en.xml splash-en.xml
web-servers-en.xml xorg-en.xml
Removed Files:
daemons.xml database-servers.xml desktop.xml
development-tools.xml feedback.xml file-servers.xml
file-systems.xml hardware-reqs.xml install-notes.xml intro.xml
java-package.xml kernel.xml misc-server.xml multimedia.xml
networking.xml overview.xml package-movement.xml
package-notes.xml printing.xml project-overview.xml samba.xml
security.xml server-tools.xml splash.xml web-servers.xml
xorg.xml
Log Message:
Renaming files to have English suffix, now these can be translated properly.
--- NEW FILE daemons-en.xml ---
<section id="sn-daemons">
<title>System Services</title>
<section id="sn-daemons-updatedb">
<title><filename>cron</filename> and <filename>slocate</filename></title>
<para>The <command>updatedb</command> utility is no longer
automatically run by <command>cron</command> to create and
update the database of files used by <command>slocate</command>.
Updating this database is an intensive process that users of
workstations and laptops may find disruptive.</para>
<para>To enable daily updates of the <command>slocate</command>
database, edit the file <filename>/etc/updatedb.conf</filename> as follows:
</para>
<screen>
DAILY_UPDATE=yes
</screen>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE database-servers-en.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE desktop-en.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE development-tools-en.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY BOILERPLATE "This header makes editing XML easier" >
<!ENTITY DISTRO "DISTRO" >
<!ENTITY DISTROVER "DISTROVER" >
]>
-->
<section id="sn-devel">
<title>
Development Tools
</title>
<section id="sn-devel-gcc">
<title>GCC Compiler Collection</title>
<para>
&DISTRO; &DISTROVER; has been built using <abbrev>GCC</abbrev>
4.0, which is included with the distribution.
</para>
<itemizedlist>
<title>Caveats</title>
<listitem>
<para>
<abbrev>GDB</abbrev> 6.1 or newer is needed to debug binaries
unless compiled using the <parameter
class="option">-fno-var-tracking</parameter> compilation
option.
</para>
</listitem>
<listitem>
<para>
The <parameter class="option">-fwritable-strings</parameter>
option is no longer accepted.
</para>
</listitem>
<listitem>
<para>
English-language diagnostic messages now use Unicode quotes;
if you cannot read this, set your <envar>LC_CTYPE</envar>
environment variable to "<filename>C</filename>" or
change your terminal emulator.
</para>
</listitem>
<listitem>
<para>
The <filename>specs</filename> file is no longer installed on
most systems. Ordinary users will not notice, but developers
who need to alter the file can use the <parameter
class="option">-dumpspecs</parameter> option to generate the
file for editing.
</para>
</listitem>
</itemizedlist>
<itemizedlist>
<title>Code Generation</title>
<listitem>
<para>
The <abbrev>SSA</abbrev> code optimizer is now included and
brings with it better constant propagation, partial redundancy
elimination, load and store code motion, strength reduction,
dead storage elimination, better detection of unreachable
code, and tail recursion by accumulation.
</para>
</listitem>
<listitem>
<para>
Autovectorization is supported. This technique achieves higher
performance for repetitive loop code, in some circumstances.
</para>
</listitem>
</itemizedlist>
<itemizedlist>
<title>Language Extentions</title>
<listitem>
<para>
A <computeroutput>sentinel</computeroutput> attribute has been
added so that the compiler will now issue a warning if a
function such as <function>execl(char *path, const char *arg,
...)</function>, which requires a <literal>NULL</literal>
list terminator is missing the <literal>NULL</literal>.
</para>
</listitem>
<listitem>
<para>
The <wordasword>cast-as-lvalue</wordasword>,
<wordasword>conditional-expression-as-lvalue</wordasword>, and
<wordasword>compund-expression-as-lvalue</wordasword>
extentions have been removed.
</para>
</listitem>
<listitem>
<para>
The <computeroutput>#pragma pack()</computeroutput> semantics
have been brought closer to those used by other compilers.
</para>
</listitem>
<listitem>
<para>
Taking the address of a variable declared with the
<computeroutput>register</computeroutput> modifier now
generates an error instead of a warning.
</para>
</listitem>
<listitem>
<para>
Arrays of incomplete element types now generate an error. This
implies no forward reference to structure definitions.
</para>
</listitem>
<listitem>
<para>
The basic compiler, without any optimization (<parameter
class="option">-O0</parameter>), has been measured as much
as 25% faster in real-world code.
</para>
</listitem>
<listitem>
<para>
Libraries may now contain function-scope static variables in
multi-threaded programs. The <parameter
class="option">-fno-threadsafe-statics</parameter> can be
used by embedded developers to turn off this feature, but
ordinary users should never do this.
</para>
</listitem>
</itemizedlist>
<itemizedlist>
<title>Java</title>
<listitem>
<para>
To avoid naming conflicts: <filename>rmic</filename> is now
<filename>grmic</filename>; <filename>rmiregistry</filename>
is now <filename>grmiregistry</filename>; and
<filename>jar</filename> is now <filename>fastjar</filename>.
</para>
</listitem>
<listitem>
<para>
The <application>GCJ</application> compiler can now be used as
a just-in-time (<abbrev>JIT</abbrev>) tool by using the
<filename>gnu.jit</filename> facilities.
</para>
</listitem>
<listitem>
<para>
More support of the <abbrev>AWT</abbrev> and
<abbrev>SWING</abbrev> packages have been added.
</para>
</listitem>
</itemizedlist>
<itemizedlist>
<title>FORTRAN</title>
<listitem>
<para>
The <abbrev>GNU</abbrev> <application>FORTRAN 77</application>
front end has been replaced by a new <application>FORTRAN
90/95</application> recognizer.
</para>
</listitem>
</itemizedlist>
<itemizedlist>
<title>Eclipse Development Environment</title>
<listitem>
<para>
Eclipse 3.1M6 has been compiled as a native application.
</para>
</listitem>
<listitem>
<para>
The C Development Tool (<abbrev>CDT</abbrev>) has been
included.
</para>
</listitem>
</itemizedlist>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE feedback-en.xml ---
<section id="sn-test" os="test">
<title>Release Notes Feedback Procedure</title>
<para>(This section will disappear when the final &DISTRO; release is
created.)</para>
<para>If you feel that these release notes could be improved in some way,
you can provide feedback directly to the author. If you see a URL in the
release notes that looks like this:</para>
<para>%%% https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=<replaceable><bug-number></replaceable> %%% </para>
<para>You can click on the URL and submit feedback on that particular
section of the release notes. Your feedback will be added as a comment to
an existing bug report.</para>
<para>If the section of the release notes that you have feedback for does
not have one of these URLs (or you are submitting a request for entirely
new content), you can click on the following link (this only works for the
HTML version, of course — the URL is much too long to include in the
text):</para>
<para><ulink
url="https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Core&...">Click
here to submit new release notes feedback</ulink></para>
<para>If you would like to review the changes that have been already
submitted for this document, use the following link:</para>
<para><ulink
url="http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398">http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398</ulink></para>
<para>As bugs are posted for the various parts of the release notes,
subsequent test versions of these release notes will contain links similar
to the one described earlier.</para>
<para>Thank you (in advance) for your feedback!</para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE file-servers-en.xml ---
<section id="sn-file-servers">
<title>File Servers</title>
<para>This section refers to file transfer and sharing servers. Please
refer to the &WEB-SERVERS; and &SAMBA; sections for information on HTTP (Web) file
transfer and Samba (Windows) file sharing.</para>
<section id="sn-file-servers-netatalk-suite">
<title>Netatalk (Macintosh Compatibility)</title>
<para>This section contains information related to Netatalk, a suite of
software that enables Linux to interact with Macintosh systems using
the AppleTalk network protocols.</para>
<section id="sn-file-servers-netatalk-package">
<title><filename>netatalk</filename></title>
<para>&DISTRO; &DISTROVER; includes version 2 of Netatalk. <emphasis>Upgrading
from Netatalk version 1 to version 2 may result in data
loss</emphasis>. Version 2 of Netatalk uses a different
method to store file resource forks from the previous version,
and may require a different file name encoding scheme. Please
read the documentation and plan your migration before upgrading.</para>
<para>Upgrade information is available directly from the Netatalk site:</para>
<para>
<ulink url="http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html">http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html</ulink>
</para>
<para>The documentation is also included in the
<filename>netatalk</filename> package. Refer to either
<filename>/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html</filename>,
or
<filename>/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf</filename>
(numbered page 25, document page 33).</para>
</section>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE file-systems-en.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE hardware-reqs-en.xml ---
<section id="sn-hardware-reqs">
<title>Hardware Requirements</title>
<para>
The following information represents the minimum hardware
requirements necessary to successfully install &DISTRO; &DISTROVER;.
</para>
<note>
<title>Note</title>
<para>
The compatibility/availability of other hardware components (such
as video and network cards) may be required for specific
installation modes and/or post-installation usage.
</para>
</note>
<!-- Something like this needs to be said, but this really needs a -->
<!-- better treatment and probably a new section devoted to help resources.
<para>
This section does not address hardware compatability. To find out
about using a specific piece of hardware with &FC; &LOCALVER;
</para>
-->
<section>
<title>CPU Requirements</title>
<para>This section lists the CPU specifications required by &DISTRO;
&DISTROVER;.</para>
<note arch="x86">
<title><!-- <remark os="test">(x86)</remark>--> Note</title>
<para><!-- <remark os="test">(x86)</remark> --> The following CPU
specifications are stated in terms of Intel processors. Other
processors (notably, offerings from AMD, Cyrix, and VIA) that
are compatible with and equivalent to the following Intel
processors may also be used with &DISTRO;.</para>
</note>
<itemizedlist arch="x86">
<listitem>
<para><!-- <remark os="test">(x86)</remark> --> Minimum:
Pentium-class — &FC; &LOCALVER; is optimized for Pentium
4 CPUs, but also supports earlier CPUs (such as Pentium,
Pentium Pro, Pentium II, Pentium III, and including AMD and
VIA variants). This approach has been taken because
Pentium-class optimizations actually result in reduced
performance for non-Pentium-class processors, and Pentium 4
scheduling is sufficiently different (while making up the bulk
of today's processors) to warrant this change. <!-- <remark
os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254</ulink>
%%%</remark> -->
</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86)</remark> --> Recommended for
text-mode: 200 MHz Pentium-class or better</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86)</remark> --> Recommended for
graphical: 400 MHz Pentium II or better</para>
</listitem>
</itemizedlist>
<itemizedlist arch="x86_64">
<listitem>
<para><!-- <remark os="test">(x86_64)</remark> --> AMD64
processors (both Athlon64 and Opteron)</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86_64)</remark> --> Intel
processors with <trademark
class="registered">Intel</trademark> Extended Memory 64
Technology (<trademark class="registered">Intel</trademark>
EM64T)</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Hard Disk Space Requirements</title>
<para>This section lists the disk space required to install &DISTRO;
&DISTROVER;.</para>
<note>
<title>Note</title>
<para>The disk space requirements listed below represent the disk
space taken up by &DISTRO; &DISTROVER;
<emphasis>after</emphasis> the installation is complete.
However, additional disk space is required during the
installation to support the installation environment. This
additional disk space corresponds to the size of
<filename>/Fedora/base/stage2.img</filename> (on CD-ROM 1) plus
the size of the files in <filename>/var/lib/rpm</filename> on
the installed system.</para>
<!-- Update these figures every release -->
<para>In practical terms, this means that as little as an
additional 90MB can be required for a minimal installation,
while as much as an additional 175MB can be required for an
"everything" installation.</para>
<para>Also, keep in mind that additional space will be required
for any user data, and at least 5% free space should be
maintained for proper system operation.</para>
</note>
<!-- Get actual numbers from installer, multiply by 1.1, and round -->
<!-- up to the nearest 10MB or .1GB -->
<para>
This list is for 32-bit x86 systems:
</para>
<itemizedlist arch="x86">
<listitem>
<para><!-- <remark os="test">(x86)</remark> --> Custom
Installation (Minimal): 620MB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86)</remark> --> Server:
1.1GB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86)</remark> --> Personal
Desktop: 2.3GB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86)</remark> --> Workstation:
3.0GB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86)</remark> --> Custom
Installation (Everything): 6.9GB</para>
</listitem>
</itemizedlist>
<para>
This list is for 64-bit x86_64 systems:
</para>
<itemizedlist arch="x86_64">
<listitem>
<para><!-- <remark os="test">(x86_64)</remark> --> Custom
Installation (Minimal): 900MB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86_64)</remark> --> Server:
1.5GB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86_64)</remark> --> Personal
Desktop: 2.7GB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86_64)</remark> --> Workstation:
3.4GB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86_64)</remark> --> Custom
Installation: (Everything) 7.5GB</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Memory Requirements</title>
<para>This section lists the memory required to install &DISTRO;
&DISTROVER;.</para>
<para>
This list is for 32-bit x86 systems:
</para>
<itemizedlist arch="x86">
<listitem>
<para><!-- <remark os="test">(x86)</remark> --> Minimum for
text-mode: 64MB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86)</remark> --> Minimum for
graphical: 192MB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86)</remark> --> Recommended for
graphical: 256MB</para>
</listitem>
</itemizedlist>
<para>
This list is for 64-bit x86_64 systems:
</para>
<itemizedlist arch="x86_64">
<listitem>
<para><!-- <remark os="test">(x86_64)</remark> --> Minimum for
text-mode: 128MB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86_64)</remark> --> Minimum for
graphical: 256MB</para>
</listitem>
<listitem>
<para><!-- <remark os="test">(x86_64)</remark> --> Recommended
for graphical: 512MB</para>
</listitem>
</itemizedlist>
</section>
<section id="sn-hardware-reqs-ppc">
<title>PPC Hardware Requirements</title>
<para>
This section lists the minimum PowerPC (PPC) hardware needed to
install &FC; &LOCALVER;.
</para>
<itemizedlist>
<listitem>
<para>
<!--<remark os="test">(ppc)</remark> --> Minimum: PowerPC G3 /
POWER4
</para>
</listitem>
<listitem>
<para>
<!--<remark os="test">(ppc)</remark> --> &FC; &LOCALVER;
supports only the <quote>New World</quote> generation of
<trademark class="registered">Apple</trademark> Power
Macintosh, shipped circa 1999 onwards. It also supports the
64-bit G5 processor and, POWER processors in <trademark
class="registered">IBM</trademark>
<trademark>eServer</trademark> <trademark>pSeries</trademark>.
Currently 32-bit <trademark class="registered">IBM</trademark>
<trademark>RS/6000</trademark> machines are not supported.
</para>
</listitem>
<listitem>
<para>
<!--<remark os="test">(x86)</remark> --> Recommended for
text-mode: 233 MHz G3 or better
</para>
</listitem>
<listitem>
<para>
<!-- <remark os="test">(ppc)</remark> --> Recommended for
graphical: 400 MHz G3 or better
</para>
</listitem>
</itemizedlist>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE install-notes-en.xml ---
<section id="sn-anaconda">
<title>Installation-Related Notes</title>
<para>
This section outlines those issues that are related to Anaconda
(the &DISTRO; installation program) and installing &DISTRO;
&DISTROVER; in general.
</para>
<note>
<title>Note</title>
<para>
If you intend to download the &DISTRO; &DISTROVER; DVD ISO
image, keep in mind that not all file downloading tools can
accommodate files larger than 2GB in size. For example,
<command>wget</command> will exit with a <computeroutput>File size
limit exceeded</computeroutput> error.
</para>
<para>
The <command>curl</command> and <command>ncftpget</command>
file downloading tools do not have this limitation, and can
successfully download files larger than 2GB.
</para>
<para>
Bittorrent is another method for downloading large files. For
information about obtaining and using the torrent file refer to
this website:
</para>
<para>
<ulink
url="http://torrent.fedoraproject.org/">http://torrent.fedoraproject.org/</ulink>
</para>
</note>
<section id="sn-install-notes-ppc">
<title>PPC Installation Notes</title>
<para>
<!--<remark os="test">(ppc)</remark>--> The DVD or first CD of the
installation set of &FC; is set to be bootable on the <trademark
class="registered">Apple</trademark> Macintosh and should boot
the appropriate 32-bit or 64-bit installer. In addition, bootable
CD images can be found in the <filename>images/</filename>
directory of the DVD or first CD. Choose the appropriate
<filename>boot.iso</filename> according to the hardware:
</para>
<itemizedlist>
<listitem>
<para><filename>images/mac/boot.iso</filename> - 32-bit
<trademark class="registered">Apple</trademark> Macintosh
(G3/G4)
</para>
</listitem>
<listitem>
<para>
<filename>images/mac64/boot.iso</filename> - 64-bit <trademark
class="registered">Apple</trademark> Macintosh (G5)
</para>
</listitem>
<listitem>
<para><filename>images/pseries/boot.iso</filename> - 64-bit
<trademark class="registered">IBM</trademark>
<trademark>eServer</trademark> <trademark>pSeries</trademark>
(POWER4/POWER5)
</para>
</listitem>
<listitem>
<para>
<!-- <remark os="test">(ppc)</remark> --> Power management
support, including sleep and backlight level management, is
present in the <command>apmud</command> package, which is in
&FEX;. &FEX; for &FC; is configured by default for
<command>yum</command>. Following installation,
<command>apmud</command> can be installed by running
<command>yum install apmud</command>.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Anaconda Notes</title>
<itemizedlist>
<listitem>
<para>
The &DISTRO; installation program has the ability to test
the integrity of the installation media. It works with the CD,
DVD, hard drive ISO, and NFS ISO installation methods. &RH;
recommends that you test all installation media before
starting the installation process, and before reporting any
installation-related bugs (many of the bugs reported are
actually due to improperly-burned CDs). To use this test, type
<command>linux mediacheck</command> at the
<prompt>boot:</prompt> prompt.
</para>
<para>
The <command>mediacheck</command> function is highly
sensitive, and may report some usable discs as faulty. This
result is often caused by disc writing software that does not
include padding when creating discs from ISO files. For best
results with the <command>mediacheck</command>, boot with the
option:
</para>
<screen>
linux ide=nodma
</screen>
<para>
Use the <command>sha1sum</command> utility to verify discs
before carrying out an installation. This test accurately
identifies discs that are not valid or identical to the ISO
image files.
</para>
</listitem>
<listitem arch="x86">
<!-- <remark os="test">%%% <ulink
url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654</ulink>
%%%</remark>
-->
<para>
<!-- <remark os="test">(x86)</remark> --> Memory testing may be
performed prior to installing &DISTRO; by entering
<command>memtest86</command> at the <prompt>boot:</prompt>
prompt. This causes the Memtest86 standalone memory testing
software to run. Memtest86 memory testing continues until the
<keycap>Esc</keycap> key is pressed.
</para>
<para>
<!-- <remark os="test">(x86)</remark> --> NOTE: You must boot from
CD-ROM 1 (or a rescue CD-ROM) in order to use this
feature.
</para>
</listitem>
<listitem>
<!-- <remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627</ulink>
%%%</remark>
-->
<para>
&DISTRO; &DISTROVER; supports graphical FTP and HTTP
installations. However, due to the necessity of containing
the installer image in RAM, only systems with more than 128MB
of RAM (or systems booted from CD-ROM 1, which contains the
installer image) can use the graphical installer. Systems
with 128MB or less will continue to use the text-based
installer.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Installation-Related Issues</title>
<itemizedlist>
<listitem>
<para>
Certain hardware configurations (particularly those with
LCD displays) may experience problems while starting the
&DISTRO; installation program. In these instances, restart
the installation, and add the "<command>nofb</command>" option
to the boot command line.
</para>
<note>
<title>Note</title>
<para>
Chinese, Japanese, and Korean graphical installations
started using the "<command>nofb</command>" option will
start in English, and then switch to the appropriate
language once the graphical phase of the installation
process begins.
</para>
</note>
</listitem>
<listitem arch="x86">
<para>
<!-- <remark os="test">(x86)</remark> --> Some Sony <trademark
class="registered">VAIO</trademark> notebook systems may
experience problems installing &DISTRO; from CD-ROM. If this
happens, restart the installation process and add the
following option to the boot command line:
</para>
<screen>
<!-- <remark os="test">(x86)</remark> -->
<command>pci=off ide1=0x180,0x386</command>
</screen>
<para>
<!-- <remark os="test">(x86)</remark> --> This option allows the
installation to proceed normally; any devices not detected due
to the use of this option will be configured the first time
&DISTRO; is booted.
</para>
</listitem>
<listitem>
<para>
Serial mice are known to be inoperative during
installation. However, there are indications that serial mice
work properly in X after the installation has completed.
Refer to bug 119474 for more information:
</para>
<para>
<ulink
url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474</ulink>
</para>
</listitem>
<listitem arch="x86">
<para>
<!-- <remark os="test">(x86)</remark> --> There have been
issues observed when upgrading &RHL;
7.<replaceable><x></replaceable>, 8.0, 9, and &FC; 1, 2,
and 3 systems where third party packages are installed that
conflict with packages provided by &FP;. One example is
Ximian GNOME.
</para>
<para>
The issue with Ximian GNOME is caused by version overlap
between the official &RHL; RPMs (or the ones from the &PROJ;)
and the Ximian RPMs. This configuration is not supported. You
have several choices in resolving this particular issue:
</para>
<orderedlist numeration="loweralpha">
<listitem>
<para>
<!-- <remark os="test">(x86)</remark> -->You may remove
Ximian GNOME from your system prior to upgrading to
&DISTRO;.
</para>
</listitem>
<listitem>
<para>
<!-- <remark os="test">(x86)</remark> -->You may upgrade
your system, and then immediately reinstall Ximian GNOME.
</para>
</listitem>
<listitem>
<para>
<!-- <remark os="test">(x86)</remark> -->You may upgrade
your system, and then immediately remove all remaining
Ximian RPMs, replacing them with the corresponding
&DISTRO; RPMs.
</para>
</listitem>
</orderedlist>
<para>
<!-- <remark os="test">(x86)</remark> -->You
<emphasis>must</emphasis> resolve the version overlap using
one of the above choices. Failure to do so will result in an
unstable GNOME configuration.
</para>
</listitem>
</itemizedlist>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE intro-en.xml ---
<section id="sn-intro">
<title>Introduction and Technical Release Notes</title>
<para>
The &PROJ; is an openly-developed project designed by &RH;, open for
general participation, led by a meritocracy, and following a set of
project objectives. The results from this project include &DISTRO;,
which is a complete, general-purpose operating system built
exclusively from open source software.
</para>
<note>
<title>Note</title>
<para>
&FC; is a community supported project.
</para>
<para>
&FC; is not a commercially supported product of &FORMAL-RHI;.
</para>
</note>
<para>
For more information, refer to <xref linkend="sn-overview"/>.
</para>
<para>
Additional important information about this release may be made
available at <ulink
url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>.
Users are advised to check this link regularly for updates.
</para>
<para>
For reporting errors or other requests about these release notes,
file a bug report using this <ulink url="&BUG-URL;">pre-filled
bugzilla template</ulink>.
</para>
<!-- This is just to tweaky to HTML and will make people think it's b0rked
<para>
<ulink
url="&BUG-URL;">&BUG-URL;</ulink>
</para>
-->
<para>
This <ulink url="&TINY-BUG-URL;">&TINY-BUG-URL;</ulink> will take
you to the same pre-filled bugzilla template.
</para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE java-package-en.xml ---
<section>
<title>Java Package Recommendations</title>
<para>
&FC; &LOCALVER; users are advised not to use the Java RPM provided
by Sun. It contains <computeroutput>Provides</computeroutput> that
conflict with names used in packages provided as part of &FC;
&LOCALVER;. Because of this, Sun Java might disappear from an
installed system during package upgrade operations.
</para>
<para>
&FC; &LOCALVER; users should use either the RPM from jpackage.org or
manually install the Sun Java tarball into
/opt<filename></filename>. Sun Java 1.5+ is recommended for
stability purposes.
</para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE kernel-en.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY BOILERPLATE "These FAKE ENTITIES are just to make editing easier" >
<!ENTITY FC "FC" >
<!ENTITY LOCALVER "LOCALVER" >
<!ENTITY DISTRO "DISTRO" >
<!ENTITY DISTROVER "DISTROVER" >
]>
-->
<section id="sn-kernel">
<title>
Linux Kernel
</title>
<section id="sn-kernel-lotsa">
<title>Version</title>
<para>
The &DISTRO; is based on a 2.6.11 kernel. &FC; may include
additional patches for improvements, bug fixes, or additional
features. For this reason, the &FC; kernel may not be
line-for-line equivalent to the so-called vanilla kernel from the
<ulink
url="http://www.kernel.org"><filename>kernel.org</filename></ulink>
web site.
</para>
<para>
You may obtain a list of any such patches by using the command on the &FC; package:
</para>
<screen width="56">
<command>rpm <parameter class="option">-qpl</parameter> <filename>kernel-<replaceable><version></replaceable>.src.rpm</filename></command>
</screen>
</section>
<section id="sn-kernel-flavors">
<title>Kernel Flavors</title>
<para>
&FC; includes the following kernel builds:
</para>
<itemizedlist>
<listitem>
<para>
Native kernel, in both uniprocessor and <abbrev>SMP</abbrev>
varieties.
</para>
<para>
Configured sources are available in the
<filename>kernel-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
package.
</para>
</listitem>
<listitem>
<para>
Virtual kernel for use with the <wordasword>Xen</wordasword> emulator package.
</para>
<para>
Configured sources are available in the
<filename>kernel-xen0-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
package.
</para>
</listitem>
</itemizedlist>
<para>
Sources for both kernel flavors may be installed at the same time.
The files will be installed into the
<filename>/usr/src/kernels/<replaceable><version></replaceable>[-xen0]-<replaceable><arch></replaceable>/</filename>
tree. Use the command:
</para>
<screen width="56">
<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-devel[-xen0]-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename></command>
</screen>
<para>
as appropriate.
</para>
<tip>
<title>Following Generic Textbooks</title>
<para>
Many of the tutorials, examples, and textbooks about Linux
kernel development assume the kernel sources are installed under
the <filename>/usr/src/linux</filename> directory. If you make a
symbolic link, as shown below, you should be able to use those
learning materials with the &FC; packages. Install the
appropriate kernel sources, as shown earlier, and then:
</para>
<screen width="56">
<command>ln <parameter class="option">-s</parameter> <filename>/usr/src/kernels/kernel-<replaceable><all-the-rest></replaceable></filename> <filename>/usr/src/linux</filename></command>
</screen>
</tip>
</section>
<!--
<tip>
<title>Using <command>yum</command> to Remove Kernel
Packages</title>
<para>
&FC; &LOCALVER; contains support for clustering systems using CMAN and GFS.
These kernels require assistance from some user-space packages.
These packages are not removed when using <command>rpm
-e</command> to remove older versions of the kernel packages.
</para>
<para>
When using <command>rpm -e kernel-<replaceable><version></replaceable> </command> to remove the kernel, you must also remove the assisting user-space packages. You may wish to consider a dependency resolving tool such as <command>yum remove kernel-<replaceable><version></replaceable> </command>.
This automatically removes any dependent packages.
</para>
</tip>
-->
<section id="sn-kernel-exploding">
<title>
Preparing for Kernel Development
</title>
<para>
&DISTRO; &DISTROVER; does not include the
<filename>kernel-source</filename> package provided by older
versions. Instead, configured sources are available as described
in <xref
linkend="sn-kernel-flavors"/>. Users that require access to &FC;
original kernel sources can find them in the
<filename>kernel</filename> <filename>.src.rpm</filename> package.
To create an exploded source tree from this file, perform the
following steps:
</para>
<important>
<title>These Instructions Refer to the Currently-running Kernel!</title>
<para>
To simplify the following directions, we have assumed that you
want to configure the kernel sources to match your
currently-running kernel. In the steps below, you must
understand that the phrase
<replaceable><version></replaceable> refers to the kernel
version shown by this command:
</para>
<screen width="56">
<command>uname <parameter class="option">-r</parameter></command>
</screen>
</important>
<procedure id="sn-kernel-exploding-steps">
<step>
<para>
Obtain the
<filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
file from one of the following sources:
</para>
<itemizedlist>
<listitem>
<para>
The <filename>SRPMS</filename> directory on the
appropriate <wordasword>SRPMS</wordasword>
<abbrev>CD</abbrev> <filename>iso</filename> image.
</para>
</listitem>
<listitem>
<para>
The FTP site where you got the kernel package.
</para>
</listitem>
<listitem>
<para>
By running the following command:
</para>
<screen width="56">
<command>up2date <parameter class="option">--get-source</parameter> <filename>kernel</filename></command>
</screen>
</listitem>
</itemizedlist>
</step>
<step>
<para>
Install
<filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
using the command:
</para>
<screen width="56">
<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-<replaceable><version></replaceable>.src.rpm</filename></command>
</screen>
<para>
This writes the <abbrev>RPM</abbrev> contents into
<filename>/usr/src/redhat/SOURCES</filename> and
<filename>/usr/src/redhat/SPECS</filename>.
</para>
</step>
<step>
<para>
Prepare the kernel sources using the commands:
</para>
<screen width="56">
<command>cd <filename>/usr/src/redhat/SPECS</filename></command>
<command>rpmbuild <parameter class="option">-bp --target $(arch)</parameter> <filename>kernel-2.6.spec</filename></command>
</screen>
<para>
The kernel source tree will be located in the
<filename>/usr/src/redhat/BUILD/kernel-</filename><replaceable><version></replaceable>
directory. It is common practice to move the resulting
<filename>linux-</filename><replaceable><version></replaceable>
directory to the <filename>/usr/src</filename> tree; while not
strictly necessary, we suggest that you do this to match the
generally-available documentation.
</para>
<screen width="56">
<command>cd <filename>/usr/src/redhat/BUILD/kernel-<replaceable><version></replaceable></filename> <filename>/usr/src/</filename></command>
<command>mv <filename>linux-<replaceable><version></replaceable></filename> <filename>/usr/src/</filename></command>
<command>cd <filename>/usr/src</filename></command>
<command>ln <parameter class="option">-s</parameter> <filename>./linux-<replaceable><version></replaceable></filename> <filename>linux</filename></command>
<command>cd <filename>/usr/src/linux</filename></command>
</screen>
</step>
<step>
<para>
The configurations for the specific kernels shipped in
&DISTRO; &DISTROVER; are in the <filename>configs/</filename>
directory. For example, the i686 SMP configuration file is
named
<filename>configs/kernel-<replaceable><version></replaceable>-i686-smp.config</filename>.
Issue the following command to place the desired configuration
file in the proper place for building:
</para>
<screen width="56">
<command>cp <filename>configs/<replaceable><desired-config-file></replaceable></filename> <filename>.config</filename></command>
</screen>
<para>
You can also find the <filename>.config</filename> file that matches your current kernel configuration in the <filename>/lib/modules/</filename><replaceable><version></replaceable><filename>/build/.config</filename> file.
</para>
</step>
<step>
<para>
Every kernel gets a name based on its version number.
This is the value the <command>uname -r</command> command displays.
The kernel name is defined by the first four lines of the kernel <filename>Makefile</filename>.
To protect the innocent, the <filename>Makefile</filename> has been changed to generate a kernel with a different name from that of the running kernel.
Before a module can be accepted by the running kernel, that
module must have been compiled for a kernel with the correct
name. To do this, you must edit the kernel <filename>Makefile</filename>
</para>
<para>
For example, if the <command>uname -r</command> returns the string <systemitem class="osname">2.6.11-1.234_FC4</systemitem>, change the <systemitem class="macro">EXTRAVERSION</systemitem> definition from this:
</para>
<screen width="60">EXTRAVERSION = -prep</screen>
<para>to this:</para>
<screen width="60">EXTRAVERSION = -1.234_FC4</screen>
<para>
that is, substitute everything from the final dash onward.
</para>
</step>
<step>
<para>
Issue the following command:
</para>
<screen width="56">
<command>make oldconfig</command>
</screen>
</step>
</procedure>
<para>
You can then proceed as usual.
</para>
</section>
<section id="sn-kernel-3rdparty">
<title>Building Only Kernel Modules</title>
<para>
An exploded source tree is <emphasis>not</emphasis> required to
build a kernel module, such as your own device driver, against the
currently in-use kernel.
</para>
<para>
For example, to build the <filename>foo.ko</filename> module,
create the following <filename>Makefile</filename> in the
directory containing the <filename>foo.c</filename> file:
</para>
<programlisting width="56">
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) M=$(PWD) modules
</programlisting>
<para>
Issue the <command>make</command> command to build the
<filename>foo.ko</filename> module.
</para>
</section>
<section id="sn-kernel-coop">
<title>User Space Dependencies on the Kernel</title>
<para>
&DISTRO; adds support for clustered systems. This requires a
special kernel that works in conjunction with some user-space
utilities, such as management daemons. Consequently, to remove
such a kernel, perhaps after an update, you
<emphasis>cannot</emphasis> simply use the <command>rpm -e
kernel-<replaceable><version></replaceable></command>
command as in earlier distributions because these user space
packages depend on the kernel package. You may either list both
the kernel package and its user space dependent packages on the
<command>rpm -e</command> command, or you may wish to use the
<command>yum remove
kernel-<replaceable><version></replaceable></command>
command instead since <command>yum</command> automatically removes
dependent packages if necessary.
</para>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE misc-server-en.xml ---
<section id="sn-misc-server-notes">
<title>Miscellaneous Notes</title>
<para>
This section contains information related to packages that do not
fit in any of the preceeding categories.
</para>
<section id="sn-misc-notes-openoffice">
<title>OpenOffice and upgrading from test releases</title>
<para>
If you choose to go counter to the recommendation to
<emphasis>not</emphasis> upgrade from a previous test release, you
may encounter a problem with OpenOffice following the upgrade.
</para>
<para>
To resolve this, you must do the following command
<emphasis>before</emphasis> doing the upgrade:
</para>
<para>
<command>rm -rf
/usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
</para>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE multimedia-en.xml ---
<section id="sn-multimedia">
<title>Multimedia</title>
<para>
This section contains information related to multimedia
applications.
</para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE networking-en.xml ---
<section id="sn-networking">
<title>Networking</title>
<para>
This section contains information relating to network connectivity.
</para>
<section id="sn-networking-networkmanager">
<title><filename>NetworkManager</filename></title>
<para>
The <command>NetworkManager</command> service allows computers
such as laptops to automatically manage changing network
connections. It includes support for wireless networking.
</para>
<para>
You must manually enable the <command>NetworkManager</command>
service. To do so, type the following in a terminal window:
</para>
<screen>
su -c '/sbin/chkconfig --level 345 NetworkManager on; /sbin/service NetworkManager start'
su -c '/sbin/chkconfig --level 345 NetworkManagerDispatcher on; /sbin/service NetworkManagerDispatcher start'
</screen>
<para>
Enter the root password when prompted.
</para>
<para>
Use the <application>Network Monitor</application> desktop applet
to monitor and configure <command>NetworkManager</command>. To load the
applet in GNOME, right-click on the panel and select:
</para>
<para>
<guimenuitem>Add to Panel...</guimenuitem><guimenuitem>Network
Monitor</guimenuitem>
</para>
<para>
<command>NetworkManager</command> uses BIND to proxy DNS requests.
Enabling the <command>NetworkManager</command> service also loads the
<command>named</command> service as well. By default BIND is
configured as a cacheing service for the local system, and does
not accept connections from other systems.
</para>
<para>
Note that some wireless network cards require drivers or firmware
that cannot be included with &DISTRO;. This software must be
installed separately for <command>NetworkManager</command> to function.
</para>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE overview-en.xml ---
<section id="sn-overview">
<title>Overview of This Release</title>
<para>
The following list includes brief summaries of some of the more
significant aspects of &DISTRO; &DISTROVER;:
</para>
<itemizedlist>
<listitem>
<para>
&DISTRO; &DISTROVER; contains the following changes:
</para>
<itemizedlist>
<listitem>
<para>
Support for the PowerPC (PPC) architecture.
</para>
</listitem>
<listitem>
<para>
GCC 4.0
</para>
</listitem>
<listitem>
<para>
GNOME 2.10
</para>
</listitem>
<listitem>
<para>
KDE 3.4 — includes new accessibility features. You
can manage these new features in <guimenu>KDS Control
Center</guimenu><guisubmenu>Regional &
Accessibility</guisubmenu><guisubmenu>Accessibility</guisubmenu>.
</para>
</listitem>
<listitem>
<para>
Native Eclipse 3.1M6 (part of a free Java stack)
</para>
</listitem>
<listitem>
<para>
MySQL 4.1
</para>
</listitem>
<listitem>
<para>
PHP 5.0
</para>
</listitem>
<listitem>
<para>
Xen 2 (virtualization to run multiple versions of an OS)
</para>
</listitem>
<listitem>
<para>
GFS 6.1-0.pre22 (cluster file system)
</para>
</listitem>
<listitem>
<para>
Evince 0.2.1 (universal document viewer)
</para>
</listitem>
<listitem>
<para>
GDM 2.6 - Includes early login capability
</para>
</listitem>
<listitem>
<!-- <remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136251">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136251</ulink>
%%%</remark>-->
<para>
&SEL; — This release includes coverage for 80 new
daemons by the targeted policy. There are changes to the
handling of Booleans. The targeted policy is enabled by
default. For more information, refer to: <ulink
url="http://fedora.redhat.com/docs/selinux-faq/">http://fedora.redhat.com/docs/selinux-faq/</ulink>.
This is the complete list of daemons covered by the targeted
policy:
</para>
<itemizedlist>
<listitem>
<para>
<command>NetworkManager</command>
</para>
</listitem>
<listitem>
<para>
<command>amanda</command>
</para>
</listitem>
<listitem>
<para>
<command>apache</command>
</para>
</listitem>
<listitem>
<para>
<command>apmd</command>
</para>
</listitem>
<listitem>
<para>
<command>arpwatch</command>
</para>
</listitem>
<listitem>
<para>
<command>auditd</command>
</para>
</listitem>
<listitem>
<para>
<command>bluetooth</command>
</para>
</listitem>
<listitem>
<para>
<command>canna</command>
</para>
</listitem>
<listitem>
<para>
<command>cardmgr</command>
</para>
</listitem>
<listitem>
<para>
<command>checkpolicy</command>
</para>
</listitem>
<listitem>
<para>
<command>chkpwd</command>
</para>
</listitem>
<listitem>
<para>
<command>compat</command>
</para>
</listitem>
<listitem>
<para>
<command>comsat</command>
</para>
</listitem>
<listitem>
<para>
<command>consoletype</command>
</para>
</listitem>
<listitem>
<para>
<command>cpucontrol</command>
</para>
</listitem>
<listitem>
<para>
<command>cpuspeed</command>
</para>
</listitem>
<listitem>
<para>
<command>crond</command>
</para>
</listitem>
<listitem>
<para>
<command>cups</command>
</para>
</listitem>
<listitem>
<para>
<command>cvs</command>
</para>
</listitem>
<listitem>
<para>
<command>cyrus</command>
</para>
</listitem>
<listitem>
<para>
<command>dbskkd</command>
</para>
</listitem>
<listitem>
<para>
<command>dbusd</command>
</para>
</listitem>
<listitem>
<para>
<command>dhcpc</command>
</para>
</listitem>
<listitem>
<para>
<command>dhcpd</command>
</para>
</listitem>
<listitem>
<para>
<command>dictd</command>
</para>
</listitem>
<listitem>
<para>
<command>dmidecode</command>
</para>
</listitem>
<listitem>
<para>
<command>dovecot</command>
</para>
</listitem>
<listitem>
<para>
<command>fingerd</command>
</para>
</listitem>
<listitem>
<para>
<command>fsadm</command>
</para>
</listitem>
<listitem>
<para>
<command>ftpd</command>
</para>
</listitem>
<listitem>
<para>
<command>getty</command>
</para>
</listitem>
<listitem>
<para>
<command>hald</command>
</para>
</listitem>
<listitem>
<para>
<command>hostname</command>
</para>
</listitem>
<listitem>
<para>
<command>hotplug</command>
</para>
</listitem>
<listitem>
<para>
<command>howl</command>
</para>
</listitem>
<listitem>
<para>
<command>hwclock</command>
</para>
</listitem>
<listitem>
<para>
<command>i18n_input</command>
</para>
</listitem>
<listitem>
<para>
<command>ifconfig</command>
</para>
</listitem>
<listitem>
<para>
<command>inetd</command>
</para>
</listitem>
<listitem>
<para>
<command>init</command>
</para>
</listitem>
<listitem>
<para>
<command>initrc</command>
</para>
</listitem>
<listitem>
<para>
<command>innd</command>
</para>
</listitem>
<listitem>
<para>
<command>kerberos</command>
</para>
</listitem>
<listitem>
<para>
<command>klogd</command>
</para>
</listitem>
<listitem>
<para>
<command>ktalkd</command>
</para>
</listitem>
<listitem>
<para>
<command>kudzu</command>
</para>
</listitem>
<listitem>
<para>
<command>ldconfig</command>
</para>
</listitem>
<listitem>
<para>
<command>load_policy</command>
</para>
</listitem>
<listitem>
<para>
<command>login</command>
</para>
</listitem>
<listitem>
<para>
<command>lpd</command>
</para>
</listitem>
<listitem>
<para>
<command>mailman</command>
</para>
</listitem>
<listitem>
<para>
<command>modutil</command>
</para>
</listitem>
<listitem>
<para>
<command>mta</command>
</para>
</listitem>
<listitem>
<para>
<command>mysqld</command>
</para>
</listitem>
<listitem>
<para>
<command>named</command>
</para>
</listitem>
<listitem>
<para>
<command>netutils</command>
</para>
</listitem>
<listitem>
<para>
<command>nscd</command>
</para>
</listitem>
<listitem>
<para>
<command>ntpd</command>
</para>
</listitem>
<listitem>
<para>
<command>portmap</command>
</para>
</listitem>
<listitem>
<para>
<command>postgresql</command>
</para>
</listitem>
<listitem>
<para>
<command>ppd</command>
</para>
</listitem>
<listitem>
<para>
<command>privoxy</command>
</para>
</listitem>
<listitem>
<para>
<command>radius</command>
</para>
</listitem>
<listitem>
<para>
<command>radvd</command>
</para>
</listitem>
<listitem>
<para>
<command>restorecon</command>
</para>
</listitem>
<listitem>
<para>
<command>rlogind</command>
</para>
</listitem>
<listitem>
<para>
<command>rpcd</command>
</para>
</listitem>
<listitem>
<para>
<command>rpm</command>
</para>
</listitem>
<listitem>
<para>
<command>rshd</command>
</para>
</listitem>
<listitem>
<para>
<command>rsync</command>
</para>
</listitem>
<listitem>
<para>
<command>samba</command>
</para>
</listitem>
<listitem>
<para>
<command>saslauthd</command>
</para>
</listitem>
<listitem>
<para>
<command>sendmail</command>
</para>
</listitem>
<listitem>
<para>
<command>setfiles</command>
</para>
</listitem>
<listitem>
<para>
<command>slapd</command>
</para>
</listitem>
<listitem>
<para>
<command>snmpd</command>
</para>
</listitem>
<listitem>
<para>
<command>squid</command>
</para>
</listitem>
<listitem>
<para>
<command>ssh</command>
</para>
</listitem>
<listitem>
<para>
<command>stunnel</command>
</para>
</listitem>
<listitem>
<para>
<command>syslogd</command>
</para>
</listitem>
<listitem>
<para>
<command>telnetd</command>
</para>
</listitem>
<listitem>
<para>
<command>tftpd</command>
</para>
</listitem>
<listitem>
<para>
<command>udev</command>
</para>
</listitem>
<listitem>
<para>
<command>updfstab</command>
</para>
</listitem>
<listitem>
<para>
<command>uucpd</command>
</para>
</listitem>
<listitem>
<para>
<command>webalizer</command>
</para>
</listitem>
<listitem>
<para>
<command>winbind</command>
</para>
</listitem>
<listitem>
<para>
<command>xdm</command>
</para>
</listitem>
<listitem>
<para>
<command>ypbind</command>
</para>
</listitem>
<listitem>
<para>
<command>ypserv</command>
</para>
</listitem>
<listitem>
<para>
<command>zebra</command>
</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<!--
<note>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136774">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136774</ulink>
%%%</remark>
<title>Note</title>
<para>
VMware WS 4.5.2 is known to work on &DISTRO; &DISTROVER; after
the following workarounds are used:</para>
<itemizedlist>
<listitem>
<para>You must upgrade the kernel modules and configuration
using the unofficial <filename>vmware-any-any-*</filename>
toolkit available from:</para>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137378">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137378</ulink>
%%%</remark>
<para><ulink
url="http://platan.vc.cvut.cz/ftp/pub/vmware/">http://platan.vc.cvut.cz/ftp/pub/vmware/</ulink></para>
</listitem>
<listitem>
<para>After <filename>vmware-config.pl</filename> is run and the
VMware modules are loaded, the following command creates the
<filename>/sys/class/*</filename> nodes needed for
udev:</para>
<para><command>cp -rp /dev/vm*
/etc/udev/devices/</command></para>
</listitem>
</itemizedlist>
</note>
-->
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE package-movement-en.xml ---
<section id="sn-package-movement">
<title>Packages Movement</title>
<!--
FIXME
Needs updating of entire contents for FC4.
-->
<section id="sn-packages-moved">
<title>Packages Moved to &FEX;</title>
<para>
These are some of the packages that have moved from &CORE; to
&FEX;. These are active packages that are maintained and
supported by the &FP;. If you are looking for information about
&EX;, refer to this URL:
</para>
<para>
<ulink
url="http://fedoraproject.org/wiki/Extras">http://fedoraproject.org/wiki/Extras</ulink>
</para>
<note>
<title>List is Incomplete</title>
<para>
This list highlights some of the major packages that moved from
&CORE; to &EX; between &FC; 3 and &FC; &LOCALVER;. This is not
a complete list.
</para>
</note>
<itemizedlist>
<listitem>
<para>
abiword
</para>
</listitem>
<listitem>
<para>
aiksaurus
</para>
</listitem>
<listitem>
<para>
balsa
</para>
</listitem>
<listitem>
<para>
bzflag
</para>
</listitem>
<listitem>
<para>
cyrus-imapd
</para>
</listitem>
<listitem>
<para>
dbh
</para>
</listitem>
<listitem>
<para>
dietlibc
</para>
</listitem>
<listitem>
<para>
exim
</para>
</listitem>
<listitem>
<para>
freeciv
</para>
</listitem>
<listitem>
<para>
gnuchess
</para>
</listitem>
<listitem>
<para>
gnumeric
</para>
</listitem>
<listitem>
<para>
grip
</para>
</listitem>
<listitem>
<para>
jed
</para>
</listitem>
<listitem>
<para>
lapack
</para>
</listitem>
<listitem>
<para>
libgda
</para>
</listitem>
<listitem>
<para>
libgnomedb
</para>
</listitem>
<listitem>
<para>
libtabe
</para>
</listitem>
<listitem>
<para>
libxfce4mcs
</para>
</listitem>
<listitem>
<para>
libxfce4util
</para>
</listitem>
<listitem>
<para>
libxfcegui
</para>
</listitem>
<listitem>
<para>
Maelstrom
</para>
</listitem>
<listitem>
<para>
ncftp
</para>
</listitem>
<listitem>
<para>
ots
</para>
</listitem>
<listitem>
<para>
recode
</para>
</listitem>
<listitem>
<para>
SDL_image
</para>
</listitem>
<listitem>
<para>
SDL_mixer
</para>
</listitem>
<listitem>
<para>
SDL_net
</para>
</listitem>
<listitem>
<para>
sylpheed
</para>
</listitem>
<listitem>
<para>
system-switch-im
</para>
</listitem>
<listitem>
<para>
xboard
</para>
</listitem>
<listitem>
<para>
xcin
</para>
</listitem>
<listitem>
<para>
xemacs
</para>
</listitem>
<listitem>
<para>
xemacs-sumo
</para>
</listitem>
<listitem>
<para>
xfce4-iconbox
</para>
</listitem>
<listitem>
<para>
[...2192 lines suppressed...]
<para><remark os="test">(x86;x86_64)</remark> raidtools</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> redhat-java-rpm-scripts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> rep-gtk</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> samba (i386)</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> sawfish</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> servletapi</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> servletapi-devel</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> shapecfg</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> struts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> struts-webapps</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> system-config-proc</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> tomcat</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> tomcat-devel</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> tomcat-libs</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> tomcat-test</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> unarj</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xalan-j</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xalan-j-devel</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xalan-j-xsltc</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xerces-j</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xerces-j-devel</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xffm-icons</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-100dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-75dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-14-100dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-14-75dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-15-100dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-15-75dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-2-100dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-2-75dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-9-100dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-9-75dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-base-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-cyrillic-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-libs-data</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-syriac-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-truetype-fonts</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Packages Deprecated</title>
<para>The following packages have been deprecated, and may be removed from
a future release of &DISTRO;:</para>
<itemizedlist>
<listitem>
<para>dbskkd-cdb — Only used by deprecated package
skkinput</para>
</listitem>
<listitem>
<para>FreeWnn — Only used by deprecated package
kinput2-canna-wnn6</para>
</listitem>
<listitem arch="x86">
<para><remark os="test">(x86)</remark> lilo — GRUB is the
recommended bootloader</para>
</listitem>
<listitem>
<para>miniChinput — IIIMF is the recommended input method</para>
</listitem>
<listitem>
<para>nabi — IIIMF is the recommended input method</para>
</listitem>
<listitem>
<para>ncpfs — No longer part of &DISTRO; profile</para>
</listitem>
<listitem>
<para>skkinput — IIIMF is the recommended input method</para>
</listitem>
<listitem>
<para>xcin — IIIMF is the recommended input method</para>
</listitem>
</itemizedlist>
</section>
-->
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE package-notes-en.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY BOILERPLATE "This header makes editing XML easier" >
<!ENTITY DISTRO "DISTRO">
<!ENTITY DISTROVER "DISTROVER">
<!ENTITY FEX "FEX">
<!ENTITY FP "FP">
<!ENTITY FC "FC" >
<!ENTITY LOCALVER "LOCALVER">
<!ENTITY RHL "RHL">
<!ENTITY SERVER-TOOLS SYSTEM "/dev/null">
<!ENTITY KERNEL SYSTEM "/dev/null">
<!ENTITY SECURITY SYSTEM "/dev/null">
<!ENTITY SEL SYSTEM "/dev/null">
<!ENTITY PRINTING SYSTEM "/dev/null">
<!ENTITY DATABASE-SERVERS SYSTEM "/dev/null">
<!ENTITY MULTIMEDIA SYSTEM "/dev/null">
<!ENTITY WEB-SERVERS SYSTEM "/dev/null">
<!ENTITY SAMBA SYSTEM "/dev/null">
<!ENTITY XORG SYSTEM "/dev/null">
<!ENTITY DEVELOPMENT-TOOLS SYSTEM "./development-tools.xml">
]>
-->
<section id="sn-package-notes">
<title>Package-Specific Notes</title>
<!--
FIXME
Needs updating of entire contents for FC4.
-->
<para>
The following sections contain information regarding packages that
have undergone significant changes for &DISTRO; &DISTROVER;. For
easier access, they are generally organized using the same groups
used in Anaconda.
</para>
<section id="sn-basic-components">
<title>Basic Components</title>
<para>
This section contains information related to basic system
components.
</para>
<section>
<title>&FEX; Repository</title>
<para>
&FEX; is part of the larger &FP; and is a volunteer-based
community effort to create a repository of packages that
compliment &FC;. The &FEX; repository is enabled by default from
&FC; &LOCALVER; onwards.
</para>
<para>
You can lean more about &FEX; from:
</para>
<para>
<ulink
url="http://fedoraproject.org/wiki/Extras">http://fedoraproject.org/wiki/Extras</ulink>
</para>
<para>
If you would like to install any software available from
Fedora extras you can use <command>yum</command>.
</para>
<screen>
<command>yum install <replaceable><packagename></replaceable></command>
</screen>
<para>
Where <replaceable><packagename></replaceable> is the name
of the package you want to install. For example, if you wanted
to install the <filename>abiword</filename> package, the command
<command>yum install abiword</command> automatically installs
the package and all dependencies.
</para>
</section>
<section id="sn-audit-daemon">
<title>Audit Daemon <command>auditd</command> and Log
Files</title>
<para>
The audit daemon, auditd, is now enabled by default. When
auditd is running, the kernel directs audit messages to
<filename>/var/log/audit/audit.log</filename>. The location of this file is
specified in <filename>/etc/auditd.conf</filename>.
</para>
<para>
AVC messages for &SEL; are sent using the audit infrastructure.
These messages are now in
<filename>/var/log/audit/audit.log</filename>.
</para>
<para>
When auditd is not running, the kernel passes audit messages to
syslog. These logs are typically kept in <filename>/var/log/messages</filename> and
are viewable using <command>dmesg</command>.
</para>
<para>
Audit extensions are now compiled into PAM. All programs that
do grant entry to the system or change user account attributes
will generate an audit message.
</para>
<para>
To enable auditing within the kernel, you must pass the
parameter <parameter>audit=1</parameter> to the kernel during
boot. Otherwise, you can use this command to enable auditing
during run time:
</para>
<screen>
<command>auditctl -e 1</command>
</screen>
</section>
<section id="sn-nptl">
<title>LinuxThreads versus NPTL</title>
<para>
As the next step in removing support for the obsolete
LinuxThreads library, code compiled and linked on &FC;
&LOCALVER; now automatically uses the NPTL headers and
libraries.
</para>
<para>
In previous releases since &RHL; 9, the default threading was
LinuxThreads since the interface is mostly forward compatible.
The advantages of the NPTL interface is that the cancellation
handling is faster (when <parameter>-fexception</parameter> is
used, even in C code) and that the additional interfaces are now
available without special compiler and linker parameters. In
other words, you do not need to use
<option>-I/usr/include/nptl</option> and
<option>-L/usr/lib{,64}/nptl</option> any longer. Note that
<parameter>lib{,64}</parameter> is to be interpreted as lib64 on
platforms which place DSOs in <filename>lib64/</filename>
directories, and <filename>lib/</filename> otherwise.
</para>
<para>
In &FC; &LOCALVER; it is still possible to create code using the
LinuxThreads definitions. For this the
<filename>linuxthreads-devel</filename> package must be
installed and
</para>
<screen>
<option>-I/usr/include/linuxthreads -L/usr/lib{,64}/linuxthreads</option>
</screen>
<para>
must be passed to the compiler.
</para>
<para>
Previously, you could select the version of glibc and the
libpgthread DSH using run time environment variables. You now
need to also specify this variable in the environment:
</para>
<screen>
<envar>LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads</envar>
</screen>
<para>
This additional variable is required because the run/time
libraries have been moved out of the way. There may be programs
that will not work if the program uses an unfortunate
<envar>DT_RPATH</envar> (which overwrites the
<envar>LD_LIBRARY_PATH</envar> setting).
</para>
<para>
All this makes it more cumbersome to run programs which depend
on LinuxThreads. But this is intentional.
</para>
<important>
<title>Important</title>
<para>
FC5 will not have LinuxThreads support and all programs have
to be converted to use NPTL by then.
</para>
</important>
<para>
In general, conversion to using NPTL has not been an issue.
</para>
</section>
<section>
<title>Enabling the <filename>slocate</filename> Database</title>
<para>
The database needed by the <command>locate</command> utility is
no longer created by default. Enable the database creation by
setting <computeroutput>DAILY_UPDATE</computeroutput> to
<option>yes</option> in <filename>/etc/updatedb.conf</filename>
if you want to use <command>locate</command>.
</para>
</section>
<section>
<title>Stricter Controls in <filename>openssh</filename></title>
<para>
The version of OpenSSH in &FC; &LOCALVER; is based on OpenSSH
3.9 and includes strict permission and ownership checks for the
user configuration file <filename>~/.ssh/config</filename>. If
this file does not have appropriate ownership and permissions,
<command>ssh</command> will exit.
</para>
<para>
Check that <filename>~/.ssh/config</filename> is owned by the
owner of <filename>~/</filename>, and that its permissions are
set to mode 600.
</para>
<screen>
ls -l ~/.ssh/config
-rw------- 1 username username 400 May 5 18:44 /home/username/.ssh/config
</screen>
<para>
The directory <filename>~/</filename> is command-line shorthand
for the logged in user's home directory, usually
<filename>/home/username/</filename>.
</para>
<para>
In addition, OpenSSH is no longer configured to request X11
forwarding by default when connecting to servers. To enable X11
forwarding, the <option>-X</option> or <option>-Y</option>
option must be specified, or the <option>ForwardX11</option>
option must be enabled in the <filename>~/.ssh/config</filename>
file.
</para>
<para>
The behavior of <command>ssh</command> clients that are invoked
with the <option>-X</option> option has changed. In OpenSSH 3.8
and later, X11 forwarding is performed in a way that
applications run as untrusted clients by default. Previously,
X11 forwarding was performed so that applications always ran as
trusted clients. Some applications may not function properly
when run as untrusted clients. To forward X11 so that
applications are run as trusted clients, invoke ssh with the
<option>-Y</option> option instead of the <option>-X</option>
option, or set <option>ForwardX11Trusted</option> in the
<option>~/.ssh/config</option> file.
</para>
</section>
<section id="sn-perl">
<title>Perl Binary Compat Symlinks</title>
<para>
Binary compat symlinks for <filename>perl-5.8.0</filename>,
<filename>perl-5.8.1</filename>, and
<filename>perl-5.8.2</filename> have been removed. If you have
perl modules built with those older versions of perl, you need
to rebuild using the <filename>perl-5.8.6</filename> contained
in &FC; &LOCALVER;.
</para>
</section>
&SERVER-TOOLS;
&JAVA-PACKAGE;
</section>
<!-- Saving these just in case ...
<section os="bogus">
<title>Administration Tools</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Authoring and Publishing</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Compatibility Arch Development Support</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Compatibility Arch Support</title>
<para>*** Enter group description here ***</para>
</section>
-->
<section id="sn-packages-core">
<title>Core</title>
<para>
This section contains the most elemental components of &DISTRO;,
including the kernel.
</para>
<section>
<title>yum</title>
<para>
The sqllite database is now used by yum, and makes performance
noticeably faster.
</para>
<para>
The Fedora Extras repository is now enabled by default.
</para>
</section>
&KERNEL;
&SECURITY;
</section>
<!--
<section>
<title><filename>e2fsprogs</filename></title>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131918">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131918</ulink>
%%%</remark>
<para>The <filename>ext2online</filename> utility has been added for
online growing of existing ext3 file systems.</para>
<note>
<title>Note</title>
<para>It is important to keep in mind that
<filename>ext2online</filename> does not grow the underlying block
device itself — there must be sufficient unused space already
present on the device. The easiest way to ensure this is to use LVM
volumes and to run <filename>lvresize</filename> or
<filename>lvextend</filename> to extend the device.</para>
</note>
<para>In addition, file systems must be specially prepared in order to
be resized past a certain point. The preparation involves reserving a
small amount of space into which on-disk tables can grow. For
newly-created file systems, <filename>mke2fs</filename> reserves such
space automatically; the space reserved is sufficient to grow the file
system by a factor of 1000. The creation of this reserved space can
be disabled by the following command:</para>
<para><command>mke2fs -O ^resize_inode</command></para>
<para>Future releases of &DISTRO; will allow the creation of this
reserved space on existing file systems.</para>
</section>
<section>
<title><filename>glibc</filename></title>
<itemizedlist>
<listitem>
<remark os="test">%%% <ulink
url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133267">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133267</ulink>
%%%</remark>
<para>The version of <filename>glibc</filename> provided with
&DISTRO; &DISTROVER; performs additional internal sanity checks to
prevent and detect data corruption as early as possible. By
default, should corruption be detected, a message similar to the
following will be displayed on standard error (or logged via
syslog if stderr is not open):</para>
<para><computeroutput>*** glibc detected *** double free or
corruption: 0x0937d008 ***</computeroutput></para>
<para>By default, the program that generated this error will also be
killed; however, this (and whether or not an error message is
generated) can be controlled via the <envar>MALLOC_CHECK_</envar>
environment variable. The following settings are
supported:</para>
<itemizedlist>
<listitem>
<para>0 — Do not generate an error message, and do not
kill the program</para>
</listitem>
<listitem>
<para>1 — Generate an error message, but do not kill the
program</para>
</listitem>
<listitem>
<para>2 — Do not generate an error message, but kill the
program</para>
</listitem>
<listitem>
<para>3 — Generate an error message and kill the
program</para>
</listitem>
</itemizedlist>
<note>
<title>Note</title>
<para>If MALLOC_CHECK_ is explicitly set a value other than 0,
this causes <filename>glibc</filename> to perform more tests
that are more extensive than the default, and may impact
performance.</para>
</note>
<para>Should you have a program from a third party ISV that triggers
these corruption checks and displays a message, you should file a
defect report with the application's vendor, since this indicates
a serious bug.</para>
</listitem>
</itemizedlist>
</section>
<section>
<title><filename>hotplug</filename></title>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136348">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136348</ulink>
%%%</remark>
<para>The location where <filename>hotplug</filename> expects firmware
to be loaded into (for example, firmware for Cardbus cards) has
changed from <filename>/usr/lib/hotplug/firmware</filename> to
<filename>/lib/firmware</filename>. Existing firmware files must be
moved into the new directory.</para>
</section>
-->
<!--
<section os="bogus">
<title>DNS Name Server</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Development Libraries</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Development Tools</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Dialup Networking Support</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Editors</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Emacs</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Engineering and Scientific</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>FTP Server</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>GNOME</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>GNOME Desktop Environment</title>
<para>*** Enter group description here ***</para>
</section>
-->
&DEVELOPMENT-TOOLS;
<!--
<section os="bogus">
<title>Games and Entertainment</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Graphical Internet</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Graphics</title>
<para>This section includes packages that help you manipulate and scan
images.</para>
</section>
<section os="bogus">
<title>ISO8859-2 Support</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>ISO8859-9 Support</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>KDE</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>KDE Desktop Environment</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>KDE Software Development</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Kernel Development</title>
<para>*** Enter group description here ***</para>
</section>
-->
<section>
<title>Language Support</title>
<para>
This section includes information related to the support of various
languages under &DISTRO;.
</para>
<section>
<title>The IIIMF Input System</title>
<para>
IIIMF is the Internet/Intranet Input Method Framework. In &FC;
&LOCALVER; the <filename>iiimf</filename> package is updated to
version 12.2.
</para>
<variablelist>
<varlistentry>
<term>File Path Changes</term>
<listitem>
<para>
The names and locations of some files in the
<filename>iiimf</filename> packages have changed.
</para>
<para>
The IIIMF server has been renamed from
<filename>/usr/sbin/htt</filename> to
<filename>/usr/bin/iiimd</filename>, and the XIM bridge
client renamed from <filename>httx</filename> to
<filename>iiimx</filename>. The
<filename>init.d</filename> script name has not changed:
it is still called <filename>iiim</filename>. All the
global system configuration files are now located under
<filename>/etc/iiim/</filename>.
</para>
<para>
Language Engine (LE) developers should note that LE
modules and their data now live under
<filename>${libdir}/iiim/le/<filename><LE_NAME></filename>/</filename>,
while runtime data is stored under
<filename>/var/lib/iiim/le/<replaceable><LE_NAME></replaceable>/</filename>.
</para>
<para>
For more information on the exact path and file location
changes, please refer to Fedora IIIMF FAQ:
</para>
<para>
<ulink
url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Hotkeys</term>
<listitem>
<para>
Trigger keys, such as
<keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>
used to activate Input Methods, are now configurable with
the command-line tool <command>iiimf-le-tools</command>.
This feature is only supported by GTK2 applications
currently. For other applications using XIM the trigger
key can be changed using an X resource. Refer to the
IIIMF FAQ at <ulink
url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>
for more details on how to change trigger hotkeys.
</para>
<para>
Note that the keyname refers to the X key symbol name. For
example, if you want to activate with
<keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>,
you need to specify '<Control>at' as the keyname not
'<Control>@'.
</para>
<para>
The per-user configuration of hotkeys does not work
currently with &SEL; in enforcing mode due to lack of
&SEL; policy. In this case, the hotkey can only be
changed in the system-wide configuration.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Qt Support</term>
<listitem>
<para>
A Qt immodule for <filename>iiimf</filename> is now
included. This immodule works but lacks a status window
and is considered experimental. Therefore, the default
for Qt applications is to continue using XIM for IIMF
input.
</para>
<para>
If you wish to try the immodule in a Qt application, first
install the <filename>iiimf-qt</filename> package, start
the application, then click mouse button-3 in an input
area and select <guimenuitem>iiimqcf</guimenuitem> from
the <guisubmenu>Select Input Method</guisubmenu>' submenu.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
</section>
<!-- keeping for historical informative purpose as a resource
<itemizedlist>
<listitem>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136409">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136409</ulink>
%%%</remark>
<para>The default Input Method (IM) for Chinese (Simplified and
Traditional), Japanese, and Korean has been changed to IIIMF
— the Internet/Intranet Input Method Framework. IIIMF is
supported as a native GTK2 IM module, and also through XIM using
the httx client. IIIMF supports the use of multiple Language
Engines (LEs) at the same time; using the GNOME Input Method
Language Engine Tool (<application>GIMLET</application> — an
applet) it is possible to switch between LEs of different
languages inside GTK2 applications.</para>
<para>IIIMF currently defaults to using
<keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>
or
<keycombo><keycap>Shift</keycap><keycap>Space</keycap></keycombo>
for toggling the input method on and off
(<application>Emacs</application> users can use
<keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>
instead of
<keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>
to set the mark.)</para>
<para>Depending on your selection at the language support screen
during installation, one or more IIIMF language engines may be
installed. The IIIMF server package
(<filename>iiimf-server</filename>) will also be installed if a
language engine has been selected. The language to language
engine (LE) package mappings are as follows:</para>
<itemizedlist>
<listitem>
<para>ja_JP — <filename>iiimf-le-canna</filename></para>
</listitem>
<listitem>
<para>zh_CN — <filename>iiimf-le-chinput</filename></para>
</listitem>
<listitem>
<para>zh_TW — <filename>iiimf-le-xcin</filename></para>
</listitem>
<listitem>
<para>ko_KR — <filename>iiimf-le-hangul</filename></para>
</listitem>
<listitem>
<para>{bn,gu,pa,ta,hi}_IN —
<filename>iiimf-le-unit</filename></para>
</listitem>
</itemizedlist>
<para>Accordingly, input via IIIMF will be enabled if you have
chosen one of the following as your default locale:</para>
<itemizedlist>
<listitem>
<para>ja_JP</para>
</listitem>
<listitem>
<para>zh_CN</para>
</listitem>
<listitem>
<para>zh_TW</para>
</listitem>
<listitem>
<para>ko_KR</para>
</listitem>
<listitem>
<para>{bn,gu,pa,ta,hi}_IN</para>
</listitem>
</itemizedlist>
<para>To aid your use of IIIMF, if you have selected one of the
above locales and you are using the GNOME Desktop, when you first
login the <application>GIMLET</application> utility (part of the
<filename>iiimf-gnome-im-switcher</filename> package) will
automatically be added to your panel.</para>
<para><application>GIMLET</application> is a utility for switching
between the different LEs that are installed on your system.
Using a different language engine allows you to enter text in
different languages. Alternatively you may add
<application>GIMLET</application> manually to your panel by right
clicking on the panel and selecting:</para>
<para><guimenuitem>Add to Panel</guimenuitem> ->
<guimenuitem>GIMLET</guimenuitem></para>
<para>Should you wish to switch between IIIMF or the legacy input
method framework XIM, you can use the
<application>system-switch-im</application> application. After
changing the input method framework your changes will be reflected
when you next start the X Window System.</para>
</listitem>
</itemizedlist>
</section>
<section os="bogus">
<title>Legacy Software Development</title>
<para>*** Enter group description here ***</para>
</section>
<section>
<title>Mail Server</title>
<para>This section contains information related to the mail transport
agents included with &DISTRO;.</para>
<section>
<title><filename>mailman</filename></title>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134015">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134015</ulink>
%%%</remark>
<para>Earlier <filename>mailman</filename> RPMs installed all files
under the <filename>/var/mailman/</filename> directory.
Unfortunately, this did not conform to the Filesystem Hierarchy
Standard (FHS) and also created security violations when &SEL; was
enabled.</para>
<para>If you previously had <filename>mailman</filename> installed and
had edited files in <filename>/var/mailman/</filename> (such as
<filename>mm_cfg.py</filename>) you must move those changes to their
new location, as documented in the following file:</para>
<para><filename>/usr/share/doc/mailman-*/INSTALL.REDHAT</filename></para>
</section>
<section>
<title><filename>sendmail</filename></title>
<itemizedlist>
<listitem>
<para>By default, the Sendmail mail transport agent (MTA) does not
accept network connections from any host other than the local
computer. If you want to configure Sendmail as a server for other
clients, you must edit <filename>/etc/mail/sendmail.mc</filename>
and change the <parameter>DAEMON_OPTIONS</parameter> line to also
listen on network devices (or comment out this option entirely using
the <command>dnl</command> comment delimiter). You must then
regenerate <filename>/etc/mail/sendmail.cf</filename> by running the
following command (as root):</para>
<para><command>make -C /etc/mail</command></para>
<para>Note that you must have the <filename>sendmail-cf</filename>
package installed for this to work.</para>
</listitem>
</itemizedlist>
</section>
</section>
<section os="bogus">
<title>Network Servers</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>News Server</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Office/Productivity</title>
<para>*** Enter group description here ***</para>
</section>
-->
&PRINTING;
<!--
<section os="bogus">
<title>Ruby</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Server</title>
<para>*** Enter group description here ***</para>
</section>
-->
<!-- not content for this release
&DATABASE-SERVERS;
&MULTIMEDIA; -->
<!--
<section os="bogus">
<title>Supported Packages</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>System Tools</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Text-based Internet</title>
<para>*** Enter group description here ***</para>
</section>
-->
&WEB-SERVERS;
&SAMBA;
&XORG;
<!-- <section os="bogus">
<title>Workstation Common</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>X Software Development</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>XEmacs</title>
<para>*** Enter group description here ***</para>
</section>
-->
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE printing-en.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE project-overview-en.xml ---
<section id="sn-whatitis">
<title>An Overview of the &PROJ;</title>
<para>
The goal of the &PROJ; is to work with the Linux community to
build a complete, general-purpose operating system exclusively
from open source software. Development is done in a public forum.
The project produces time-based releases of &DISTRO; approximately
2-3 times a year, with a public release schedule. The &RH;
engineering team continues to participate in building &DISTRO;
and invites and encourages more outside participation than was
possible in the past. By using this more open process, we hope to
provide an operating system more in line with the ideals of free
software and more appealing to the open source community.
</para>
<para>
For more information, refer to the &PROJ; website:
</para>
<para>
<ulink
url="http://fedora.redhat.com/">http://fedora.redhat.com/</ulink>
</para>
<para>
In addition to the website, the following mailing lists are
available:
</para>
<itemizedlist>
<listitem>
<para>
fedora-list(a)redhat.com — For users of &DISTRO; releases
</para>
</listitem>
<listitem>
<para>
fedora-test-list(a)redhat.com — For testers of &DISTRO;
test releases
</para>
</listitem>
<listitem>
<para>
fedora-devel-list(a)redhat.com — For developers,
developers, developers
</para>
</listitem>
<listitem>
<para>
fedora-docs-list(a)redhat.com — For participants of the
Documentation Project
</para>
</listitem>
</itemizedlist>
<para>
To subscribe to any of these lists, send an email with the word
"subscribe" in the subject to
<computeroutput><replaceable><listname></replaceable>-request</computeroutput>
(where
<computeroutput><replaceable><listname></replaceable></computeroutput>
is one of the above list names.)
</para>
<para>
Alternately, you can subscribe through the Web interface:
</para>
<para>
<ulink url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
</para>
<para>
If you have subscribed in the past to rhl-list, rhl-beta-list,
rhl-devel-list, or rhl-docs-list, your subscriptions have been
retained.
</para>
<para>
The &PROJ; also includes an IRC (Internet Relay Chat) channel. IRC is
a real-time, text-based form of communication. With it, you can have
conversations with multiple people in an open channel or chat with someone
privately one-on-one.
</para>
<para>
To talk with other &PROJ; participants via IRC, access freenode IRC
network. Initially, you can use <filename>irc.freenode.net</filename> as
the IRC server, although you may decide to select a server that is
geographically closer to you. Refer to the freenode website (<ulink
url="http://www.freenode.net/">http://www.freenode.net/</ulink>) for more
information. &PROJ; participants frequent the
<filename>#fedora</filename> channel, while &PROJ; developers can often be
found on the <filename>#fedora-devel</filename> channel. Some of the
larger projects may have their own channels as well; this information can
be found on the project pages.
</para>
<para>
In order to talk on the <filename>#fedora</filename> channel, you
will need to register your nickname (<firstterm>nick</firstterm>).
Instructions are given when you <command>/join</command> the
channel.
</para>
<note>
<title>Note</title>
<para>
&RH; has no control over the &PROJ; IRC channels or their
content.
</para>
</note>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE samba-en.xml ---
<section id="sn-samba">
<title>Samba (Windows File System Compatibility)</title>
<para>
This section contains information related to Samba, the suite
of software that enables Linux to interact with Microsoft Windows
systems.
</para>
<para>
Browsing of Windows shares (also known as SMB browsing) fails
on &DISTRO; &DISTROVER; systems that have the standard firewall
configured. This is most easily noticed in the failure of the
desktop to display shares.
</para>
<para>
The firewall disrupts the broadcast mode of SMB browsing, which is the
default. There are two workarounds:
</para>
<itemizedlist>
<listitem>
<para>
Configure a WINS server on the network, and set the "wins
server" option in smb.conf to the address of the WINS server.
</para>
</listitem>
<listitem>
<para>
Disable the firewall.
</para>
</listitem>
</itemizedlist>
<warning>
<title>Disabling the firewall may make your system vulnerable</title>
<para>
Make sure you fully understand the risks before undertaking this
step.
</para>
</warning>
<para>
For additional information, refer to the following bug report:
</para>
<para>
<ulink url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478</ulink>
</para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE security-en.xml ---
<section id="sn-security">
<title>Security</title>
<para>
This section highlights various security items from &FC;.
</para>
<section id="sn-security-digital-certs">
<title>Digital Certificates Consolidated</title>
<para>
Digital certificates are now centralised in directories under
<filename>/etc/pki/</filename>. Users performing an upgrade must
relocate their digital certificates.
</para>
<para>
OpenSSL: the <filename>/usr/share/ssl</filename> contents have
moved to <filename>/etc/pki/tls</filename> and
<filename>/etc/pki/CA</filename>.
</para>
<para>
Dovecot: A <filename>dovecot-openssl.cnf</filename> file is
automatically installed in <filename>/etc/pki/dovecot/</filename>.
</para>
<para>
For information about &SEL;, refer to <xref
linkend="sn-overview"/>.
</para>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE server-tools-en.xml ---
<section id="sn-server-sys-config">
<title>Server and System Configuration Tools</title>
<para>
This section highlights changes and additions to the various GUI server
and system configuration tools in &FC;.
</para>
<section id="sn-system-config-lvm">
<title><application>system-config-lvm</application></title>
<para>
The new LVM tool <application>system-config-lvm</application>
assists you in managing logical volumes.
</para>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE splash-en.xml ---
<section id="sn-splash">
<title>Welcome to &FC; &LOCALVER;</title>
<para>
&FC; is a completely free, user friendly, and secure general purpose
platform based on Linux. The &FP; is an open source project that
pioneers leading edge technology and concepts sponsored by &RH; and
supported by the &FED; community.
</para>
<tip>
<title>Latest Release Notes on the Web</title>
<para>
These release notes may be updated. Visit <ulink
url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>
to view the latest release notes for &DISTRO; &DISTROVER;.
</para>
</tip>
<!-- save for when the FIG is actually updated
<note>
<title>Installation Guide Updated</title>
<para>
New for this release is the <citetitle>&FC; &LOCALVER;
&IG;</citetitle>. This guide is useful for users of all levels
and can be found at this URL:
</para>
<para>
<ulink url="http://fedora.redhat.com/docs/fedora-install-guide-en/">http://fedora.redhat.com/docs/fedora-install-guide-en/</ulink>
</para>
</note>
-->
<para>
Refer to these webpages to find out more information about &FED;:
</para>
<itemizedlist>
<listitem>
<para>
<xref linkend="sn-new-in-fc"/>
</para>
</listitem>
<listitem>
<para>
<xref linkend="sn-intro"/> — Technical release notes
</para>
</listitem>
<listitem>
<para>
Help and Support (<ulink
url="http://fedora.redhat.com/participate/communicate/">http://fedora.redhat.com/participate/communicate/</ulink>)
</para>
</listitem>
<listitem>
<para>
Participate in the &FP; (<ulink
url="http://fedora.redhat.com/participate/">http://fedora.redhat.com/participate/</ulink>)
</para>
</listitem>
<listitem>
<para>
About the &FP; (<ulink
url="http://fedora.redhat.com/about/">http://fedora.redhat.com/about/</ulink>)
</para>
</listitem>
</itemizedlist>
<section id="sn-new-in-fc">
<title>New in &FC; &LOCALVER;</title>
<para>
&FC; &LOCALVER; is the latest version of the free and popular &FC;
platform with a number of unique features and significant
improvements over previous versions. This section provides an
overview of the major highlights in this release.
</para>
<itemizedlist>
<listitem>
<para>
Desktop Enhancements — The &FED; desktop brings to you
the latest software such as GNOME 2.10 and KDE 3.4 with a new
look and feel. GNOME has the new simple and elegant Clearlooks
default theme that is inspired by the classic Red Hat
Bluecurve theme, as shown in <xref
linkend="ex-desktop-screenshot-clearlooks"/>.
</para>
<example id="ex-desktop-screenshot-clearlooks">
<title>New desktop featuring Clearlooks and Evince</title>
<mediaobject id="txt-fedora-desktop-screenshot">
<imageobject>
<imagedata fileref="./figs/Fedora_Desktop.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata fileref="./figs/Fedora_Desktop.png" format="PNG"/>
</imageobject>
<textobject>
<para>
Screenshot of Fedora desktop showing Firefox in the
background and the new universal document viewer Evince
in the foreground. Evince is displaying Lawrence
Lessig's Free Culture.
</para>
</textobject>
</mediaobject>
</example>
</listitem>
<listitem>
<para>
Improved Productivity
</para>
<itemizedlist>
<listitem>
<para>
Evince (<ulink
url="http://www.gnome.org/projects/evince/">http://www.gnome.org/projects/evince/</ulink>)
is a document viewer for multiple document formats such as
pdf, postscript, and many others. Evince replaces a whole
category of document viewers with a single simple
application.
</para>
</listitem>
<listitem>
<para>
OpenOffice.org 2.0 (<ulink
url="http://www.openoffice.org/product2/index.html">http://www.openoffice.org/product2/index.html</ulink>)
is an office productivity suite. This latest version
includes several enhancements such as improved Microsoft
Office compatibility, completely revamped Impress
presentation software, and native support for the
OpenDocument format. This version also introduces Base, a
fully integrated database management software. You can
find the extensive list of new features at <ulink
url="http://marketing.openoffice.org/2.0/featureguide.html">http://marketing.openoffice.org/2.0/featureguide.html</ulink>.</para>
</listitem>
<listitem>
<para>
Eclipse 3.1 is an open and extensible software development
platform that is an Integrated Development Environment
(<acronym>IDE</acronym>) useful for programming in any
language.
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
Support for PowerPC (PPC) Architecture — Refer to <xref
linkend="sn-hardware-reqs-ppc"/> and <xref
linkend="sn-install-notes-ppc"/>.
</para>
</listitem>
<listitem>
<para>
Improved Security — &SEL; is a security architecture
that protects applications and users through finely grained
mandatory security controls. The default targeted policy has
been improved to cover 80 additional daemons. You can read
more in the technical release notes
<xref linkend="sn-overview"/>.
</para>
</listitem>
<listitem>
<para>
Integrated Clustering Technology — Global File System
(<acronym>GFS</acronym>) is an open source clustering file
system that allows a cluster of Linux servers to share a
common storage pool. &FC; &LOCALVER; has integrated GFS within
the system to manage your storage in an efficient way. You
can read more at <ulink
url="http://www.redhat.com/software/rha/gfs/">http://www.redhat.com/software/rha/gfs/</ulink>
and <ulink
url="http://www.redhat.com/docs/manuals/enterprise/">http://www.redhat.com/docs/manuals/enterprise/</ulink>.
</para>
</listitem>
<listitem>
<para>
Built-in Virtualization — Xen is a virtual machine that
can securely run multiple operating systems in their own
sandboxed domains. Xen has been integrated into &FC; to work
in a seamless fashion. You can read more about Xen at <ulink
url="http://fedora.redhat.com/projects/virtualization/">http://fedora.redhat.com/projects/virtualization/</ulink>.
</para>
</listitem>
<listitem>
<para>
Solid Platform — &FC; &LOCALVER; includes and integrates
the latest 4.0 version of GNU Compiler Collection, which has a
rewritten optimization infrastructure and improved support for
a native open source Java software stack. This stack includes
parts of OpenOffice.org 2.0., Eclipse, and Apache Jakarta,
among others.
</para>
</listitem>
</itemizedlist>
</section>
<section id="sn-why-no-mp3">
<title>MP3 Codecs and Other Patented or Closed Source Software</title>
<para>
This section is a brief explanation of why certain software is not
included in &FC; or &FEX;. This information was drawn directly
from the canonical wiki page:
</para>
<para>
<ulink
url="http://fedoraproject.org/wiki/ForbiddenItems">http://fedoraproject.org/wiki/ForbiddenItems</ulink>
</para>
<para>
A frequent question of the &FP; is why certain items are not
included in &FC; or &FEX;. This briefly explains some of the
reasons.
</para>
<para>
Other items, such as file systems support, requires community
participation. For more information, refer to <ulink
url="http://fedoraproject.org/wiki/Wishlist">http://fedoraproject.org/wiki/Wishlist</ulink>
</para>
<variablelist>
<varlistentry>
<term>NTFS</term>
<listitem>
<para>
NTFS Support is not included in the &FC; kernel because of
patent concerns. Using a file system natively supported by
Linux such as ext3 is a better option. If you must share
files between Windows and Linux on a single system, use
FAT/FAT32 (vfat) instead. For sharing across a network,
Samba is a good option.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>MP3 encode/decode functionality</term>
<listitem>
<para>
MP3 support is not included in any &FC; application because
MP3 is heavily patented in several regions including the
United States. The patent holder is unwilling to give an
unrestricted patent grant, as required by the GPL. Other
platforms might have paid the royalty and/or included
proprietary software. Other Linux distributions not based in
a region affected by the patent might ship MP3
decoders/encoders. However, &FC; cannot and does not ship
MP3 decoders/encoders in order to serve the goal of shipping
only free and open source software. Using other open source
formats such as Ogg Vorbis (a lossy codec that has better
quality than MP3) or FLAC (a lossless codec) is highly
recommended.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>NVIDIA 3D drivers</term>
<listitem>
<para>
The NVIDIA 3D drivers are closed source. &FC; does not
include proprietary binaries. Consider using an Intel or any
other manufacturer that supports open source cards with full
specifications and/or source code.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>ATI 3D drivers</term>
<listitem>
<para>
The ATI 3D drivers are closed source. &FC; does not include
proprietary binaries. Consider using an Intel or any other
manufacturer that supports open source cards with full
specifications and/or source code.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RealPlayer</term>
<listitem>
<para>
RealPlayer is a closed source application. &FC; does not
include proprietary binaries. Consider using open source
codecs that do not have patent restrictions.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>DVD video playback</term>
<listitem>
<para>
DVD video playback (of CSS encrypted DVDs) may violate the
US DMCA (refer to <ulink
url="http://en.wikipedia.org/wiki/DMCA">http://en.wikipedia.org/wiki/DMCA</ulink>)
because it may be considered circumventing an encryption
mechanism. Additionally, MPEG2 is a patented codec, so even
DVDs without encryption cannot be played. Consider using
open source unencrypted mediums such as Ogg Theora formats.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Mono</term>
<listitem>
<para>
Mono packages are not currently included due to potential
legal issues. (Pending more input.) Applications can be
written in other languages that are open source, such as
Python, Perl, or Ruby. Java is cross-platform and GCJ is a
relatively mature open source implementation of it. These
are not direct one-to-one equivalents with .NET but might
serve your purpose.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Cryptology (mcrypt)</term>
<listitem>
<para>
Some cryptology related packages such as mcrypt are not
included within &FC; due to US export restrictions. Consider
using non-restricted cryptographical methods instead.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>szip</term>
<listitem>
<para>
The szip license is too restrictive for inclusion in &FEX;.
Use other open source alternatives.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
In conclusion:
</para>
<itemizedlist>
<listitem>
<para> If it is proprietary, it cannot be included in &FED;.
</para>
</listitem>
<listitem>
<para>
If it is legally encumbered, it cannot be included in &FED;.
</para>
</listitem>
<listitem>
<para>
If it violates US Federal law, it cannot be included in &FED;.
</para>
</listitem>
</itemizedlist>
<para>
Of course, the logical followup is: "But I want to get foo and do
bar, how can I do one of the items listed above?"
</para>
<para>
The unofficial <ulink
url="http://fedorafaq.org">http://fedorafaq.org</ulink> provides
useful answers on commonly asked questions. However, these are
completely unsupported by the &FP;. The &FP; encourages using free
and open source software.
</para>
<para>
The binary only drivers can be acquired from the vendors. You can
find many interesting things with Google.
</para>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE web-servers-en.xml ---
<section id="sn-web-servers">
<title>Web Servers</title>
<para>
This section contains information on Web-related
applications.
</para>
<section id="sn-web-servers-modperl">
<title><filename>mod_perl</filename></title>
<para>
The RC5 release of mod_perl 2.0 is now included. The API provided
by this release is incompatible with previous 1.99_xx releases.
Please refer to the following document for a discussion of how to
adapt code to use the new API:
</para>
<para>
<ulink
url="http://perl.apache.org/docs/2.0/rename.html">http://perl.apache.org/docs/2.0/rename.html</ulink>
</para>
</section>
<section id="sn-web-servers-php">
<title><filename>php</filename></title>
<para>
Version 5.0 of PHP is now included, which includes a number of
changes to the language along with significant performance
improvements. Please refer to the PHP documentation for more
information on migrating from PHP 4.3 to PHP 5.0:
</para>
<para>
<ulink
url="http://www.php.net/manual/en/migration5.php">http://www.php.net/manual/en/migration5.php</ulink>
</para>
<para>
The <filename>/usr/bin/php</filename> binary is now built using
the CLI command-line SAPI, rather than the CGI SAPI. Use
<filename>/usr/bin/php-cgi</filename> for CGI SAPI. The
<command>php-cgi</command> also includes FastCGI support.
</para>
<para>
The following extensions have been added:
</para>
<itemizedlist>
<listitem>
<para>
The <command>mysqli</command> extension, a new interface
designed specifically for MySQL 4.1. This is included in the
<filename>php-mysql</filename> package.
</para>
</listitem>
<listitem>
<para>
The <command>soap</command> extension, for implementing SOAP
clients and servers.
</para>
</listitem>
</itemizedlist>
<para>
The following extensions are now available as optional loadable
extensions, rather than being built in to the PHP binaries:
</para>
<itemizedlist>
<listitem>
<para>
The <command>dba</command> extension, now available in the
<filename>php-dba</filename> package
</para>
</listitem>
<listitem>
<para>
The <command>bcmath</command> extension, now available in the
<filename>php-bcmath</filename> package
</para>
</listitem>
</itemizedlist>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE xorg-en.xml ---
<section id="sn-xwindows">
<title>X Window System (Graphics)</title>
<para>
This section contains information related to the X Window System
implementation provided with &DISTRO;.
</para>
<section id="sn-xwindows-xorg">
<title><filename>xorg-x11</filename></title>
<para>
Users new to the X.org X11 implementation should take note of a
few differences between it and the XFree86.org X11 implementation
which shipped in previous &RH; and &FED; operating systems. In
particular, the names of some files have changed:
</para>
<para>
X Server Binary:
</para>
<itemizedlist>
<listitem>
<para>XFree86 X11: <filename>XFree86</filename></para>
</listitem>
<listitem>
<para>X.org X11: <filename>Xorg</filename></para>
</listitem>
</itemizedlist>
<para>
X Server Configuration File:
</para>
<itemizedlist>
<listitem>
<para>XFree86 X11:
<filename>/etc/X11/XF86Config</filename></para>
</listitem>
<listitem>
<para>X.org X11: <filename>/etc/X11/xorg.conf</filename></para>
</listitem>
</itemizedlist>
<para>
X Server Log File:
</para>
<itemizedlist>
<listitem>
<para>XFree86 X11:
<filename>/var/log/XFree86.<replaceable>$DISPLAY</replaceable>.log</filename></para>
</listitem>
<listitem>
<para>X.org X11:
<filename>/var/log/Xorg.<replaceable>$DISPLAY</replaceable>.log</filename></para>
</listitem>
</itemizedlist>
<para>
When configuring or troubleshooting your X server
configuration, be sure that you are using the correct
files.
</para>
<para>
There has been some confusion regarding font-related issues
under the X Window System in recent versions of &DISTRO; (and
versions of &RHL; before it.) At the present time, there are two
font subsystems, each with different characteristics:
</para>
<itemizedlist>
<listitem>
<para>The original (15+ year old) subsystem is referred to as
the <firstterm>core X font subsystem</firstterm>. Fonts
rendered by this subsystem are not anti-aliased, are handled
by the X server, and have names such as:
<computeroutput>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</computeroutput>
</para>
</listitem>
<listitem>
<para>
The newer font subsystem is known as
<firstterm>fontconfig</firstterm>, and allows applications
direct access to the font files. Fontconfig is often used
along with the <filename>Xft</filename> library, which allows
applications to render fontconfig fonts to the screen with
antialiasing. Fontconfig uses more human-friendly names such
as: <computeroutput>Luxi Sans-10</computeroutput>
</para>
</listitem>
</itemizedlist>
<para>
Over time, fontconfig and <filename>Xft</filename> will replace
the core X font subsystem. At the present time, applications
using the Qt 3 or GTK 2 toolkits (which would include KDE and
GNOME applications) use the fontconfig and Xft font subsystem;
almost everything else uses the core X fonts.
</para>
<para>
In the future, &FC; may support only fontconfig/Xft in
place of the XFS font server as the default local font access
method.
</para>
<note>
<title>Note</title>
<para>
An exception to the font subsystem usage outlined above is
OpenOffice.org, which uses its own font rendering technology.
</para>
</note>
<para>
The steps to add new fonts to &DISTRO; &DISTROVER; depend on the
fonts subsystem this is going to use the new fonts. For the core X
font subsystem:
</para>
<procedure>
<step>
<para>
Create the <filename>/usr/share/fonts/local/</filename>
directory (if it doesn't already exist):
</para>
<screen>
<command>mkdir /usr/share/fonts/local/</command>
</screen>
</step>
<step>
<para>
Copy the new font file into
<filename>/usr/share/fonts/local/</filename>
</para>
</step>
<step>
<para>
Update the font information by issuing the following commands
(note that, due to formatting restrictions, the following
commands may appear on more than one line; in use, each
command should be entered on a single line):
</para>
<screen>
<command>ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</command>
<command>mkfontdir /usr/share/fonts/local/</command>
</screen>
</step>
<step>
<para>
If you had to create
<filename>/usr/share/fonts/local/</filename>, you must then
add it to the X font server (<command>xfs</command>) path:
</para>
<screen>
<command>chkfontpath --add /usr/share/fonts/local/</command>
</screen>
</step>
</procedure>
<para>
Adding new fonts to the fontconfig font subsystem is more
straightforward; the new font file only needs to be copied into
the <filename>/usr/share/fonts/</filename> directory (individual
users can modify their personal font configuration by copying the
font file into the <filename>~/.fonts/</filename> directory).
</para>
<para>
After the new font has been copied, use
<command>fc-cache</command> to update the font information cache:
</para>
<screen>
<command>fc-cache <replaceable><directory></replaceable></command>
</screen>
<para>
(Where
<command><replaceable><directory></replaceable></command>
would be either the <filename>/usr/share/fonts/</filename> or
<filename>~/.fonts/</filename> directories.)
</para>
<para>
Individual users may also install fonts graphically, by browsing
<command>fonts:///</command> in
<application>Nautilus</application>, and dragging the new font
files there.
</para>
<note>
<title>Note</title>
<para>
If the font filename ends with "<filename>.gz</filename>", it
has been compressed with <command>gzip</command>, and must be
decompressed (with the <command>gunzip</command> command) before
the fontconfig font subsystem can use the font.
</para>
</note>
<para>
Due to the transition to the new font system based on
fontconfig/Xft, GTK+ 1.2 applications are not affected by any
changes made via the <guilabel>Font Preferences</guilabel> dialog.
For these applications, a font can be configured by adding the
following lines to the file <filename>~/.gtkrc.mine</filename>:
</para>
<screen>
<computeroutput>style "user-font" {
fontset = "<replaceable><font-specification></replaceable>"
}
widget_class "*" style "user-font"</computeroutput>
</screen>
<para>
(Where
<command><replaceable><font-specification></replaceable></command>
represents a font specification in the style used by traditional X
applications, such as
"<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>".)
</para>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
Index: fedora.css
===================================================================
RCS file: /cvs/docs/release-notes/fedora.css,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora.css 24 Oct 2005 13:13:33 -0000 1.1
+++ fedora.css 25 Oct 2005 02:48:50 -0000 1.2
@@ -39,8 +39,8 @@
div.note table, div.tip table, div.important table, div.caution table, div.warning table {
width: 95%;
- border: 2px solid #B0C4DE;
- background-color: #F0F8FF;
+ border: 2px solid #D0D0B0;
+ background-color: #FAF9E0;
color: #000000;
/* padding inside table area */
padding: 0.5em;
@@ -72,21 +72,31 @@
h1, h2, h3, h4 {
font-family: luxi sans,sans-serif;
- color: #990000;
+ color: #22437f;
font-weight: bold;
}
h1 {
font-size: 1.75em;
}
-
+
h2 {
font-size: 1.25em;
}
-
+
h3 {
font-size: 1.1em;
}
+a:link {
+ color: #900;
+}
+a:visited {
+ color: #48468f;
+}
+a:hover {
+ color: #f20;
+}
+
code.screen, pre.screen {
font-family: monospace;
font-size: 1em;
@@ -108,9 +118,17 @@
}
.procedure ol li {
- margin-bottom: 1.5em;
+ margin-bottom: 0.5em;
}
-/* prevent inheritance */
.procedure ol li li {
+ /* prevent inheritance */
+ margin-bottom: 0em;
+}
+
+.itemizedlist ul li {
+ margin-bottom: 0.5em;
+}
+.itemizedlist ul li li {
+ /* prevent inheritance */
margin-bottom: 0em;
}
--- daemons.xml DELETED ---
--- database-servers.xml DELETED ---
--- desktop.xml DELETED ---
--- development-tools.xml DELETED ---
--- feedback.xml DELETED ---
--- file-servers.xml DELETED ---
--- file-systems.xml DELETED ---
--- hardware-reqs.xml DELETED ---
--- install-notes.xml DELETED ---
--- intro.xml DELETED ---
--- java-package.xml DELETED ---
--- kernel.xml DELETED ---
--- misc-server.xml DELETED ---
--- multimedia.xml DELETED ---
--- networking.xml DELETED ---
--- overview.xml DELETED ---
--- package-movement.xml DELETED ---
--- package-notes.xml DELETED ---
--- printing.xml DELETED ---
--- project-overview.xml DELETED ---
--- samba.xml DELETED ---
--- security.xml DELETED ---
--- server-tools.xml DELETED ---
--- splash.xml DELETED ---
--- web-servers.xml DELETED ---
--- xorg.xml DELETED ---
18 years, 6 months
rpm-guide rpm-guide-intro-rpm-en.xml,1.1,1.2
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/rpm-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7619
Modified Files:
rpm-guide-intro-rpm-en.xml
Log Message:
Tagging and minor style edits
Index: rpm-guide-intro-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-intro-rpm-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-intro-rpm-en.xml 4 Oct 2005 01:53:01 -0000 1.1
+++ rpm-guide-intro-rpm-en.xml 25 Oct 2005 00:32:57 -0000 1.2
@@ -1,62 +1,53 @@
-<!-- $Id: -->
-<chapter id="ch-intro-rpm">
-<title>Introduction to RPM</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para/>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Examining the history of package management
- </para>
-
- <para>
- *Introducing RPM features
- </para>
+<!-- $Id: -->
+<chapter id="ch-intro-rpm">
+ <title>Introduction to RPM</title>
<para>
- *Getting acquainted with RPM terminology
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Examining the history of package management
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Introducing RPM features
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Getting acquainted with RPM terminology
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
- Several package managers���software that tracks and manipulates the
- applications installed on the system���are available for Linux. The
- most widely used of these Linux package managers is the RPM Package
- Manager (formerly the Red Hat Package Manager), or RPM for short,
- the subject of this book
+ Several package managers are available for Linux to track and
+ manipulate the applications installed on the system. The most widely
+ used of these Linux package managers is the RPM Package Manager
+ (formerly the Red Hat Package Manager), or RPM for short, the
+ subject of this book
</para>
-
<para>
- Although RPM was initially developed for Red Hat Linux, a
- combination of technical features and good timing has resulted in
- RPM���s becoming the de facto standard for packaging software on
- most Linux distributions. The fact that Red Hat released the source
- code to the RPM software under an open-source license also helped
- its adoption.
+ Although RPM was initially developed for &RHL;, a combination of
+ technical features and good timing has resulted in RPM���s becoming
+ the de facto standard for packaging software on most Linux
+ distributions. The fact that &RH; released the source code to the
+ RPM software under an open-source license also helped its adoption.
</para>
-
<para>
More recently, the RPM package file format has been adopted as the
official standard for Linux as part of the Linux Standards Base, or
- LSB. Described at www.linuxbase.org/, the Linux Standards Base is an
- attempt to set a baseline that all Linux distributions should
- follow. Some vendors have been pulled in kicking and screaming, but
- the LSB for the most part has really helped the job of system
- administrators by providing some commonality across distributions,
- as in the location of certain files. The history of Linux package
- managers is largely intertwined with the history of Linux
- distributions.
+ LSB. Described at <ulink url="http://www.linuxbase.org/"/>, the
+ Linux Standards Base is an attempt to set a baseline that all Linux
+ distributions should follow. Some vendors have been pulled in
+ kicking and screaming, but the LSB for the most part has really
+ helped the job of system administrators by providing some
+ commonality across distributions, as in the location of certain
+ files. The history of Linux package managers is largely intertwined
+ with the history of Linux distributions.
</para>
-
<para>
Strictly speaking, Linux refers to a single piece of software, the
Unix-like kernel that Linus Torvalds and cohorts have scattered all
@@ -69,7 +60,6 @@
such as watches and PDAs, to desktop and server systems, all the way
up to mainframes and supercomputing clusters.
</para>
-
<sect1>
<title>The Need for Linux Package Management Systems</title>
<para>
@@ -83,16 +73,18 @@
Despite this controversy, it is clear that most users of Linux
require both the Linux kernel and a large suite of accompanying
software (a shared C library; traditional Unix utilities such as
- grep, awk, and sed; an editor, such as vi; a shell, such as the
- Bourne-Again "bash" shell; and so forth) to complete the various
- tasks for which they typically employ Linux.
+ <command>grep</command>, <command>awk</command>, and
+ <command>sed</command>; an editor, such as <command>vi</command>;
+ a shell, such as the Bourne-Again <command>bash</command> shell;
+ and so forth) to complete the various tasks for which they
+ typically employ Linux.
</para>
<para>
Users expect Linux to include server software such as the Apache
Web server, desktop software such as the OpenOffice.org office
productivity suite, and a host of other packages. In fact, most
Linux users don���t make the distinction between the kernel
- (technically the only part that is ���Linux���) and all the extra
+ (technically the only part that is Linux) and all the extra
packages (technically ���everything else���) that comes with a
Linux distribution. Most users simply refer to the whole thing as
���Linux.���
@@ -175,25 +167,27 @@
related applications, but what was really needed was installation
and uninstallation on an application-by-application basis.
</para>
+<!-- SE: Note that "Red Hat" should not replaced by entities when part of abbreviations -->
<para>
In late 1993, Rik Faith, Doug Hoffman, and Kevin Martin began
releasing the first public betas of the BOGUS Linux distribution.
- BOGUS was notable for the package management system (pms) software
- that was used with it for installation and uninstallation of all
- software on an application-by-application basis. Shortly
- thereafter, in the summer of 1994, the first public betas of Red
- Hat Commercial Linux were released. Red Hat initially used Red Hat
- Software Program Packages (RPP) as the basis of its Linux
- distribution. Like pms, RPP was a system-management tool that
+ BOGUS was notable for the package management system
+ (<command>pms</command>) software that was used with it for
+ installation and uninstallation of all software on an
+ application-by-application basis. Shortly thereafter, in the
+ summer of 1994, the first public betas of Red Hat Commercial Linux
+ were released. &RH; initially used Red Hat Software Program
+ Packages (RPP) as the basis of its Linux distribution. Like
+ <command>pms</command>, RPP was a system-management tool that
allowed for easy installation and uninstallation of applications.
In late 1993, Ian Murdock founded the Debian Gnu/Linux
- distribution. He began seriously developing its dpkg
- application-management software by the summer of 1994. Like pms
- and RPP, dpkg made it possible to manage each application on the
- system.
+ distribution. He began seriously developing its
+ <command>dpkg</command> application-management software by the
+ summer of 1994. Like <command>pms</command> and RPP,
+ <command>dpkg</command> made it possible to manage each
+ application on the system.
</para>
</sect1>
-
<sect1>
<title>RPM Design Goals</title>
<para>
@@ -215,42 +209,60 @@
</para>
<para>
Because of these concerns, after their initial releases of
- RPP-based distributions, Red Hat looked closely at both their own
- RPP software and other software such as BOGUS's pms software.
- Developers at Red Hat, particularly Marc Ewing and Erik Troan, set
- out to develop what they initially called the Red Hat Package
- Manager (RPM). Based on experiences with earlier Linux packaging
- software and knowledge about packaging tools used on other
- platforms, Red Hat had several design goals in mind when they
+ RPP-based distributions, &RH; looked closely at both their own RPP
+ software and other software such as BOGUS's <command>pms</command>
+ software. Developers at &RH;, particularly Marc Ewing and Erik
+ Troan, set out to develop what they initially called the Red Hat
+ Package Manager (RPM). Based on experiences with earlier Linux
+ packaging software and knowledge about packaging tools used on
+ other platforms, &RH; had several design goals in mind when they
developed RPM. These design points include the following features:
</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Ease of use
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Package-oriented focus
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Upgradability of packages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Tracking of package interdependencies
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Query capabilities
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Verification
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Support for multiple architectures
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use of pristine sources
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
- *Ease of use
- </para>
- <para>
- *Package-oriented focus
- </para>
- <para>
- *Upgradability of packages
- </para>
- <para>
- *Tracking of package interdependencies
- </para>
- <para>
- *Query capabilities
- </para>
- <para>
- *Verification
- </para>
- <para>
- *Support for multiple architectures
- </para>
- <para>
- *Use of pristine sources
- </para>
- <para>
- The following sections demonstrate how Red Hat incorporated each
- of these design goals into RPM.
+ The following sections demonstrate how &RH; incorporated each of
+ these design goals into RPM.
</para>
<sect2>
<title>Ease of use</title>
@@ -259,38 +271,55 @@
to use. Manual software installation has been the primary method
of putting software onto Unix boxes for over 30 years now and
has worked very well for those three decades. To offer a
- compelling reason to use the new software, Red Hat's RPM must be
+ compelling reason to use the new software, RPM must be
significantly easier to use than other Linux package-management
tools. For that reason, most tasks that can be handled using RPM
were designed to be carried out via a single command. For
example, software installation using RPM requires a single
- command (rpm -U software_package), while manual software
- installation using older manual methods typically requires at
- least six steps to complete the same task:
- </para>
- <para>
- 1.tar zxf software_package
- </para>
- <para>
- 2.cd software_package
- </para>
- <para>
- 3../configure
- </para>
- <para>
- 4.make
- </para>
- <para>
- 5.su
- </para>
- <para>
- 6.make install
- </para>
+ command (<userinput>rpm -U software_package</userinput>), while
+ manual software installation using older manual methods
+ typically requires at least six steps to complete the same task:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ <command>tar zxf
+ <replaceable>software_package</replaceable></command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command>cd
+ <replaceable>software_package</replaceable></command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command>./configure</command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command>make</command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command>su</command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command>make install</command>
+ </para>
+ </listitem>
+ </orderedlist>
<para>
Similarly, removal of applications installed using RPM requires
- a single command (rpm -e software_package); manual removal of an
- installed application requires that each file associated with
- that application be manually deleted.
+ a single command (<userinput>rpm -e
+ <replaceable>software_package</replaceable></userinput>); manual
+ removal of an installed application requires that each file
+ associated with that application be manually deleted.
</para>
</sect2>
<sect2>
@@ -330,11 +359,12 @@
Apache's configuration information, which specifies things such
as which files on the system should be made available as Web
pages and who should be able to access those Web pages, is
- stored in a text file, typically /etc/httpd/conf/httpd.conf.
- Suppose Apache has been installed using RPM and that you have
- then customized httpd.conf to specify its configuration. If you
- upgrade Apache using RPM, as part of the upgrade procedure, the
- RPM application will take precautions to preserve the
+ stored in a text file, typically
+ <filename>/etc/httpd/conf/httpd.conf</filename>. Suppose Apache
+ has been installed using RPM and that you have then customized
+ <filename>httpd.conf</filename> to specify its configuration. If
+ you upgrade Apache using RPM, as part of the upgrade procedure,
+ the RPM application will take precautions to preserve the
customizations you have made to the Apache configuration. In
contrast, manual upgrades of applications often overwrite any
existing configuration files, losing all site customizations the
@@ -347,12 +377,12 @@
Software that manages the applications installed on the system
on an application level (such as RPM) does have one potential
drawback in comparison with system-wide software management
- systems (such as PC operating systems like Microsoft's Windows
- or IBM's OS/2, which allow the entire system to be upgraded but
- do not generally allow individual components to be upgraded,
- added, or removed). Software applications often have
- interdependencies; some applications work only when other
- applications are installed.
+ systems (such as PC operating systems like Microsoft Windows or
+ OS/2, which allow the entire system to be upgraded but do not
+ generally allow individual components to be upgraded, added, or
+ removed). Software applications often have interdependencies;
+ some applications work only when other applications are
+ installed.
</para>
<para>
The Postfix and Sendmail mail transfer agent (MTA) applications
@@ -379,35 +409,39 @@
components, ensuring that all can still interoperate. On
Microsoft Windows 2000, IIS (the application used on Windows to
serve Web pages) requires several other applications such as
- EventLog (the Windows application that records system events,
- much like the Linux syslogd and klogd software) to be present.
- Since Windows is managed on a system level, not a package level,
- this dependency is guaranteed to be satisfied. On Linux systems
- using RPM, however, the situation is different. On Linux, for
- example, the Postfix application requires the syslogd
- application, which records system events. However, RPM provides
- the flexibility to install some applications but not install
- others or to uninstall others later. When you install Postfix,
- you have no guarantee that syslogd is already installed. If
- syslogd is not installed, Postfix will not work correctly.
- </para>
- <para>
- To avoid problems, Red Hat developers realized that RPMs must
- also track dependency information about what software they
- require for correct functionality, and that the RPM install and
+ <command>EventLog</command> (the Windows application that
+ records system events, much like the Linux
+ <command>syslogd</command> and <command>klogd</command>
+ software) to be present. Since Windows is managed on a system
+ level, not a package level, this dependency is guaranteed to be
+ satisfied. On Linux systems using RPM, however, the situation is
+ different. On Linux, for example, the Postfix application
+ requires the <command>syslogd</command> application, which
+ records system events. However, RPM provides the flexibility to
+ install some applications but not install others or to uninstall
+ others later. When you install Postfix, you have no guarantee
+ that <command>syslogd</command> is already installed. If
+ <command>syslogd</command> is not installed, Postfix will not
+ work correctly.
+ </para>
+ <para>
+ To avoid problems, &RH; developers realized that RPMs must also
+ track dependency information about what software they require
+ for correct functionality, and that the RPM install and
uninstall applications must use this dependency information.
Because of dependencies, installing Postfix using RPM on a
- system without syslogd installed generates a warning that
- syslogd must also be installed. Similarly, attempting to
- uninstall syslogd from a system that already has Postfix
- installed generates a warning that installed applications
- require the software that is being deleted. These warnings can
- be overridden if necessary, but by default RPM enforces these
- dependencies (refusing, for example, to let you uninstall
- syslogd without also uninstalling applications that require it,
- such as Postfix), preventing you from accidentally breaking
- applications by inadvertently uninstalling other software that
- they require to operate.
+ system without <command>syslogd</command> installed generates a
+ warning that <command>syslogd</command> must also be installed.
+ Similarly, attempting to uninstall <command>syslogd</command>
+ from a system that already has Postfix installed generates a
+ warning that installed applications require the software that is
+ being deleted. These warnings can be overridden if necessary,
+ but by default RPM enforces these dependencies (refusing, for
+ example, to let you uninstall <command>syslogd</command> without
+ also uninstalling applications that require it, such as
+ Postfix), preventing you from accidentally breaking applications
+ by inadvertently uninstalling other software that they require
+ to operate.
</para>
</sect2>
<sect2>
@@ -429,21 +463,21 @@
<para>
RPM also maintains a variety of information about each installed
file in this system database, such as what permissions each file
- should have and what size each file should be. Red Hat
- developers designed this database to be useful for software
- verification. Over time, installed software will fail to work
- for reasons as mundane as the system administrator setting
- incorrect permissions on files or as exotic as nuclear decay of
- one of the computer's atoms releasing an alpha particle that can
- affect the computer's memory, corrupting that bit of memory and
- causing errors. Although RPM cannot prevent all errors that
- cause installed software to fail (obviously, there's not a
- single thing any software can do to prevent nuclear decay), it
- can be used to eliminate common errors. When an application
- fails, you can use the RPM database to make sure that all files
- associated with that application still have correct Unix file
- permissions and that no files associated with that application
- have become altered or corrupted.
+ should have and what size each file should be. &RH; developers
+ designed this database to be useful for software verification.
+ Over time, installed software will fail to work for reasons as
+ mundane as the system administrator setting incorrect
+ permissions on files or as exotic as nuclear decay of one of the
+ computer's atoms releasing an alpha particle that can affect the
+ computer's memory, corrupting that bit of memory and causing
+ errors. Although RPM cannot prevent all errors that cause
+ installed software to fail (obviously, there's not a single
+ thing any software can do to prevent nuclear decay), it can be
+ used to eliminate common errors. When an application fails, you
+ can use the RPM database to make sure that all files associated
+ with that application still have correct Unix file permissions
+ and that no files associated with that application have become
+ altered or corrupted.
</para>
</sect2>
<sect2>
@@ -468,8 +502,8 @@
series of processors were among the first additional CPUs that
Linux supported. These days, Linux supports dozens of CPU
architectures.) This posed a problem for distribution developers
- such as Red Hat and Debian and for application vendors who
- desired to package their software for use on Linux. Because the
+ such as &RH; and Debian, and for application vendors who desired
+ to package their software for use on Linux. Because the
available packaging methods could not produce packages for
multiple architectures, packagers making software for multiple
CPUs had to do extra work to prepare their packages.
@@ -481,7 +515,7 @@
machine types they could install the packages.
</para>
<para>
- Red Hat decided to overcome these limitations by incorporating
+ &RH; decided to overcome these limitations by incorporating
architecture support into RPM, adding features so that the basic
setup a packager performs to create a package could be leveraged
to produce packages that would run on various CPUs, and so that
@@ -492,19 +526,19 @@
<sect2>
<title>Pristine sources</title>
<para>
- The BOGUS distribution's pms packaging system introduced the use
- of pristine source code to prepare packages. With Red Hat's
- early RPP package system and other similar early efforts,
- software packagers would compile software manually, then run
- commands to produce a package of that compiled software. Any
- changes made to the application's original source code were not
- recorded and would have to be recreated by the next person to
- package that software. Furthermore, end users wanting to know
- what changes had been made to the software they were running had
- no method of accessing that information.
+ The BOGUS distribution's <command>pms</command> packaging system
+ introduced the use of pristine source code to prepare packages.
+ With Red Hat's early RPP package system and other similar early
+ efforts, software packagers would compile software manually,
+ then run commands to produce a package of that compiled
+ software. Any changes made to the application's original source
+ code were not recorded and would have to be recreated by the
+ next person to package that software. Furthermore, end users
+ wanting to know what changes had been made to the software they
+ were running had no method of accessing that information.
</para>
<para>
- With RPM, Red Hat developed a package system that produced two
+ With RPM, &RH; developed a package system that produced two
types of packages: binary and source. Binary packages are
compiled software that can be installed and used. Source
packages contain the source code for that software, along with a
@@ -523,7 +557,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>RPM Terminology</title>
<para>
@@ -540,82 +573,102 @@
</para>
<para>
To help in installation and management, all package files are
- labeled with highly identifiable names. Red Hat Linux package
- files have four-part names, which typically look something like:
- </para>
- <para>
- kernel-smp-2.4.18-3.athlon.rpm
- </para>
- <para>
- kernel-smp-2.4.18-3.i586.rpm
- </para>
- <para>
- kernel-smp-2.4.18-3.i686.rpm
- </para>
- <para>
- kernel-source-2.4.18-3.i386.rpm
- </para>
- <para>
- rootfiles-7.2-1.noarch.rpm
+ labeled with highly identifiable names. Package files have
+ four-part names, which typically look something like:
</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>kernel-smp-2.4.18-3.athlon.rpm</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>kernel-smp-2.4.18-3.i586.rpm</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>kernel-smp-2.4.18-3.i686.rpm</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>kernel-source-2.4.18-3.i386.rpm</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>rootfiles-7.2-1.noarch.rpm</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
Here, the four parts of each name are separated from each other by
dashes or periods. The structure of the package file name is
</para>
<para>
- name-version-release.architecture.rpm
+ <filename>name-version-release.architecture.rpm</filename>
</para>
<para>
The name identifies what software is contained within the archive
file. Typically, this is a name of an application or package that
- the archive installs on the system. For example, kernel-smp can be
- installed to provide a very important application, the SMP
- (symmetric multiprocessing, meaning it supports systems with more
- than one CPU in them) version of the Linux kernel, on the system.
- Sometimes, rather than an application, the software is a
- collection of other files needed on the system. The rootfiles
- package, for example, is not an application but is a collection of
- basic environmental configuration files for the root user's
- account (such as /root/.bashrc, the root user's Bash configuration
- file) that provides a usable, preconfigured working environment
- for the root user on Red Hat Linux systems.
- </para>
- <para>
- The second field in every Red Hat Linux package file's name is the
- version field. This field identifies the version number of the
- software that is contained in the package file. For example,
- kernel-smp-2.4.18 indicates the RPM holds the 2.4.18 release of
- the SMP version of the Linux kernel, and rootfiles-7.2 is the 7.2
- release of the rootfiles configuration files.
- </para>
- <para>
- Every Red Hat Linux package file name also has a third component:
- the release field. This field identifies which release of that
- version of the software the package file contains. Package files
- contain both software and instructions about how to install that
- software. As packages of a particular version of software are
- being prepared, mistakes are sometimes made in these instruction
- files, or bugs are sometimes fixed within a software version; more
- recent package files of that software version need to be prepared
- that correct the problem. The ���1 in the rootfiles-7.2-1 package
- shows this is the first release of the 7.2 version of the
- rootfiles software. The packager of rootfiles version 7.2 got
- everything right on the first try and had no need to prepare more
- than one release. The ���3 in the kernel-smp-2.4.18-3 package, on
- the other hand, is the third release of the 2.4.18 version of the
- SMP-capable Linux kernel. This release incorporates new patches to
- fix bugs present in older releases of the 2.4.18 version of the
- Linux SMP kernel. The software packager increased the release
- number so that end users could distinguish the more recent,
- bug-fixed package file from the older, less bug-free package file.
- </para>
- <para>
- The final field in Red Hat Linux package file names is the
- architecture, which identifies the system types for which the
- package file is appropriate. For example, the
- kernel-smp-2.4.18-3.athlon package is intended for use on machines
- with an AMD Athlon CPU, and kernel-smp-2.4.18-3.i586 is intended
- for use on machines with an i586 (Pentium-class) CPU or better. An
+ the archive installs on the system. For example,
+ <filename>kernel-smp</filename> can be installed to provide a very
+ important application, the SMP (symmetric multiprocessing, meaning
+ it supports systems with more than one CPU in them) version of the
+ Linux kernel, on the system. Sometimes, rather than an
+ application, the software is a collection of other files needed on
+ the system. The <filename>rootfiles</filename> package, for
+ example, is not an application but is a collection of basic
+ environmental configuration files for the
+ <systemitem class="username">root</systemitem> user's account
+ (such as <filename>/root/.bashrc</filename>, the
+ <systemitem class="username">root</systemitem> user's Bash
+ configuration file) that provides a usable, preconfigured working
+ environment for the <systemitem class="username">root</systemitem>
+ user.
+ </para>
+ <para>
+ The second field in every package file's name is the version
+ field. This field identifies the version number of the software
+ that is contained in the package file. For example,
+ <filename>kernel-smp-2.4.18</filename> indicates the RPM holds the
+ 2.4.18 release of the SMP version of the Linux kernel, and
+ <filename>rootfiles-7.2</filename> is the 7.2 release of the
+ <filename>rootfiles</filename> configuration files.
+ </para>
+ <para>
+ Every package file name also has a third component: the release
+ field. This field identifies which release of that version of the
+ software the package file contains. Package files contain both
+ software and instructions about how to install that software. As
+ packages of a particular version of software are being prepared,
+ mistakes are sometimes made in these instruction files, or bugs
+ are sometimes fixed within a software version; more recent package
+ files of that software version need to be prepared that correct
+ the problem. The ���1 in the <filename>rootfiles-7.2-1</filename>
+ package shows this is the first release of the 7.2 version of the
+ <filename>rootfiles</filename> software. The packager of
+ <filename>rootfiles</filename> version 7.2 got everything right on
+ the first try and had no need to prepare more than one release.
+ The ���3 in the <filename>kernel-smp-2.4.18-3</filename> package,
+ on the other hand, is the third release of the 2.4.18 version of
+ the SMP-capable Linux kernel. This release incorporates new
+ patches to fix bugs present in older releases of the 2.4.18
+ version of the Linux SMP kernel. The software packager increased
+ the release number so that end users could distinguish the more
+ recent, bug-fixed package file from the older, less bug-free
+ package file.
+ </para>
+ <para>
+ The final field in package file names is the architecture, which
+ identifies the system types for which the package file is
+ appropriate. For example, the
+ <filename>kernel-smp-2.4.18-3.athlon</filename> package is
+ intended for use on machines with an AMD Athlon CPU, and
+ <filename>kernel-smp-2.4.18-3.i586</filename> is intended for use
+ on machines with an i586 (Pentium-class) CPU or better. An
architecture name of noarch indicates this is a special
architecture such that the files in the package work on any
architecture. Typically, this is because the files are all
@@ -627,7 +680,7 @@
4.1.
</para>
<para>
- Table 2-1Supported Architectures
+ Table 2-1 Supported Architectures
</para>
<informaltable frame="all">
<tgroup cols="2">
@@ -792,32 +845,32 @@
</tbody>
</tgroup>
</informaltable>
- <para>
- Tip
- </para>
- <para>
- When choosing an appropriate architecture for your machine, be
- aware that more recent architectures typically run software that
- targets older architectures within the same family; the reverse,
- however, is not true. For example, within the 32-bit
- Intel-compatible architectures, a 686-class (Pentium II / III /
- IV) machine runs files within i386, i486, i586, and i686 RPM
- package files, but a 386-class (80386) machine runs files within
- i386 RPM package files only. Similarly, for the Alpha
- architecture, more recent Alpha EV68 CPUs can run programs from
- RPM package files with alphaev67, alphaev6, alphaev56, alphaev5,
- and alpha architectures, but an older Alpha EV56 machine can run
- programs from RPM package files with alpha, alphaev5, or alphaev56
- architectures only.
- </para>
+ <tip>
+ <title>Architecture Compatibility</title>
+ <para>
+ When choosing an appropriate architecture for your machine, be
+ aware that more recent architectures typically run software that
+ targets older architectures within the same family; the reverse,
+ however, is not true. For example, within the 32-bit
+ Intel-compatible architectures, a 686-class (Pentium II / III /
+ IV) machine runs files within i386, i486, i586, and i686 RPM
+ package files, but a 386-class (80386) machine runs files within
+ i386 RPM package files only. Similarly, for the Alpha
+ architecture, more recent Alpha EV68 CPUs can run programs from
+ RPM package files with alphaev67, alphaev6, alphaev56, alphaev5,
+ and alpha architectures, but an older Alpha EV56 machine can run
+ programs from RPM package files with alpha, alphaev5, or
+ alphaev56 architectures only.
+ </para>
+ </tip>
<para>
Notice that the four fields in RPM package file names are
separated from each other by punctuation, either a dash (-) or a
period (.). Periods and dashes, however, are also allowed within
- fields. 7.2 is a valid version number, just as kernel-source is a
- valid software name. Finally, keep in mind that all RPM package
- files use an .rpm file-name extension to denote that they are
- RPMs.
+ fields. 7.2 is a valid version number, just as
+ <filename>kernel-source</filename> is a valid software name.
+ Finally, keep in mind that all RPM package files use an .rpm
+ file-name extension to denote that they are RPMs.
</para>
<para>
Once installed, package names are slightly different from package
@@ -825,24 +878,28 @@
Internet, copied off of CDs, and otherwise easily transferred
between machines, always have names that looks like
name-version-release.architecture.rpm. Installed packages,
- however, have names that look like name-version-release. Once
- installed, packages are referred to without the architecture field
- and the .rpm extension. Furthermore, installed packages consist of
- lots of files, not a single RPM file. For example, the package
- file kernel-smp-2.4.18-3.i686.rpm after installation is referred
- to as kernel-smp-2.4.18-3. To simplify usage even further,
- installed packages can be referred to by their name field only, so
- this file would become simply kernel-smp.
- </para>
- <para>
- Warning
- </para>
- <para>
- Once installed, the name of the package does not have to be the
- same as the name portion of the original package file. By
- convention though, the package name matches the name, version, and
- release part of the file name.
+ however, have names that look like
+ <filename>name-version-release</filename>. Once installed,
+ packages are referred to without the architecture field and the
+ .rpm extension. Furthermore, installed packages consist of lots of
+ files, not a single RPM file. For example, the package file
+ <filename>kernel-smp-2.4.18-3.i686.rpm</filename> after
+ installation is referred to as
+ <filename>kernel-smp-2.4.18-3</filename>. To simplify usage even
+ further, installed packages can be referred to by their name field
+ only, so this file would become simply
+ <filename>kernel-smp</filename>.
</para>
+ <warning>
+ <title>Software Names May Differ from Package Names</title>
+
+ <para>
+ Once installed, the name of the package does not have to be the
+ same as the name portion of the original package file. By
+ convention though, the package name matches the name, version,
+ and release part of the file name.
+ </para>
+ </warning>
<para>
Usage of the name field by itself to name packages assumes that
multiple versions or releases of that particular software are not
@@ -852,42 +909,47 @@
uses an SMP-capable Linux kernel. On it, I have the following
Linux SMP kernels installed:
</para>
- <para>
- $ rpm -q kernel-smp
- </para>
- <para>
- kernel-smp-2.4.18-4
- </para>
- <para>
- kernel-smp-2.4.18-3
- </para>
- <para>
- kernel-smp-2.5.21-4
- </para>
- <para>
- $
- </para>
- <para>
- This example uses the rpm ���q command to query for all installed
- versions of the given package, kernel-smp.
- </para>
- <para>
- Cross Reference
- </para>
- <para>
- Chapter 5 covers querying the RPM database in depth.
+ <itemizedlist>
+ <listitem>
+ <para>
+ kernel-smp-2.4.18-4
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ kernel-smp-2.4.18-3
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ kernel-smp-2.5.21-4
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ This example uses the <command>rpm <option>���q</option></command>
+ command to query for all installed versions of the given package,
+ <filename>kernel-smp</filename>.
</para>
+ <note>
+ <title>The RPM Database</title>
+
+ <para>
+ <xref linkend="ch-using-rpm-db"/> covers querying the RPM
+ database in depth.
+ </para>
+ </note>
<para>
I have two different package file releases (release 3 and release
4) of the 2.4.18 version of the Linux kernel, and I have a
development kernel, version 2.5.21, installed. On this system,
- since I have multiple packages installed of the kernel-smp
- software, I have to use the full package name (such as
- kernel-smp-2.4.18-4) whenever I want to work with my installed
- kernel-smp packages.
+ since I have multiple packages installed of the
+ <filename>kernel-smp</filename> software, I have to use the full
+ package name (such as <filename>kernel-smp-2.4.18-4</filename>)
+ whenever I want to work with my installed
+ <filename>kernel-smp</filename> packages.
</para>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
@@ -909,7 +971,7 @@
include nearly so many applications. From the OpenOffice.org
office suite to the Apache Web server, Linux distributions are
literally packed with applications. As a final point, most other
- operating systems provide mostly closed-source applications.
+ operating systems provide mainly closed-source applications.
Linux, on the other hand, includes thousands of open-source
applications.
</para>
@@ -919,22 +981,43 @@
for end users, the solution to these problems helps make the RPM
system better able to manage user systems:
</para>
- <para>
- *The RPM system tags each package with the processor architecture
- and allows for multiple versions of the same package to be
- installed on the same system. RPM also packs all the files in a
- package into one file, called an RPM file, for easy transfer to
- other systems.
- </para>
- <para>
- *Most RPM operations such as installing or removing packages
- require only a single command to run.
- </para>
- <para>
- *The RPM system supports building RPM packages from a pristine set
- of sources. This means you can reproduce the commands required to
- build an application, improving quality.
- </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Supports Multiple Architectures — The RPM system tags
+ each package with the processor architecture.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Permits Multiple Software Versions in Parallel — RPM
+ allows for multiple versions of the same package to be
+ installed on the same system.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ One File Per Program — RPM packs all of the files in a
+ package into one file, called an RPM file, for easy transfer
+ to other systems.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Requires Only One Command Per Action — Most RPM
+ operations such as installing or removing packages require
+ only a single command to run.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Uses Pristine Sourcecode — The RPM system supports
+ building RPM packages from a pristine set of sources. This
+ means you can reproduce the commands required to build an
+ application, improving quality.
+ </para>
+ </listitem>
+ </orderedlist>
<para>
This chapter introduced the RPM system and the history behind it.
The next chapter delves into the RPM basics, including files,
18 years, 6 months
rpm-guide rpm-guide-intro-packaging-en.xml,1.1,1.2
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/rpm-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32657
Modified Files:
rpm-guide-intro-packaging-en.xml
Log Message:
Tagging and trivial edits
Index: rpm-guide-intro-packaging-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-intro-packaging-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-guide-intro-packaging-en.xml 4 Oct 2005 01:52:28 -0000 1.1
+++ rpm-guide-intro-packaging-en.xml 24 Oct 2005 20:34:34 -0000 1.2
@@ -1,30 +1,27 @@
<!-- $Id: -->
-<preface id="ch-intro-packaging">
-<title>Introducing Package Management</title>
-
- <para>
- Copyright (c) 2005 by Eric Foster-Johnson. This material may be
- distributed only subject to the terms and conditions set forth in
- the Open Publication License, v1.0 or later (the latest version is
- presently available at http://www.opencontent.org/openpub/).
- </para>
-
- <para>
- In This Chapter
- </para>
-
- <para>
- *Issues in software management
- </para>
-
- <para>
- *Examining Linux management tools
- </para>
+<preface id="ch-intro-packaging">
+ <title>Introducing Package Management</title>
<para>
- *Introducing the package concept
+ This chapter covers:
</para>
-
+ <itemizedlist>
+ <listitem>
+ <para>
+ Issues in software management
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Examining Linux management tools
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Introducing the package concept
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
In 1991, a young Finnish graduate student started a new personal
hobby. He had acquired an Intel 386 computer and had spent a few
@@ -35,16 +32,14 @@
exploring Minix, a feature-limited teaching operating system, he
decided he needed a full-featured OS.
</para>
-
<para>
At that time, no full-featured PC operating systems were freely
available, so he decided to write his own operating system. Today,
that small hobby OS that Linus Torvalds started almost as a whim has
- become Linux (www.linux.com), a significant new variant of Unix that
- runs millions of the world's network servers and, increasingly,
- desktop computers and embedded processors.
+ become Linux, a significant new variant of Unix that runs millions
+ of the world's network servers and, increasingly, desktop computers
+ and embedded processors.
</para>
-
<para>
Linux has grown up, successfully making the transition from a
one-man personal project to a functional, full-featured operating
@@ -57,7 +52,6 @@
other installed packages? And how can you safely upgrade packages?
Answering these questions is what this book is all about.
</para>
-
<sect1>
<title>Installing, Removing, and Upgrading Applications</title>
<para>
@@ -104,14 +98,14 @@
distributed as source code. To install a new application, such as
the Apache Web server, you download the source code for that
application���in this case, from the Apache Project's Web page
- (http://httpd.apache.org). Typically, the source code is provided
- in some sort of archive (such as the Zip archival and compression
- format often used in the Windows world or the tar archive format
- typically used in the Unix world) that you must then unpack. After
- unpacking this source code, you have to configure it to support
- the options and systems you want, compiling it to produce an
- executable program that can run on your particular operating
- system (CPU combination).
+ (<ulink url="http://httpd.apache.org"/>). Typically, the source
+ code is provided in some sort of archive (such as the Zip archival
+ and compression format often used in the Windows world or the tar
+ archive format typically used in the Unix world) that you must
+ then unpack. After unpacking this source code, you have to
+ configure it to support the options and systems you want,
+ compiling it to produce an executable program that can run on your
+ particular operating system (CPU combination).
</para>
<para>
After compiling the source code, you still have to install the
@@ -171,19 +165,18 @@
is.
</para>
</sect1>
-
<sect1>
<title>Overcoming the Installation Obstacles</title>
<para>
None of the tasks you must perform to install, upgrade, or
uninstall applications are especially difficult. However, these
steps quickly become daunting when you consider all the files that
- must be managed. A full Red Hat Linux 7.3 installation provides
- around 3,000 executable commands and over 160,000 total files
- (some other Linux distributions are even larger!). Obviously,
- managing all these files by hand, although theoretically possible,
- is not technically feasible. On a smaller scale, even management
- of single applications is not practical. The Postfix e-mail server
+ must be managed. A full &RHL; 7.3 installation provides around
+ 3,000 executable commands and over 160,000 total files (some other
+ Linux distributions are even larger!). Obviously, managing all
+ these files by hand, although theoretically possible, is not
+ technically feasible. On a smaller scale, even management of
+ single applications is not practical. The Postfix e-mail server
application, for example, consists of around 275 files scattered
in a dozen or so different directories. Imagine trying to remember
and manually remove all of those files (and only those files) to
@@ -219,13 +212,14 @@
perform the upgrade. Otherwise, the software must be manually
upgraded using the procedure described previously.
</para>
- <para>
- Note
- </para>
- <para>
- Current versions of Windows, such as Windows XP, though, have a
- central database of installed applications.
- </para>
+ <note>
+ <title>Current Windows Versions</title>
+
+ <para>
+ Current versions of Windows, such as Windows XP, have a
+ central database of installed applications.
+ </para>
+ </note>
</sect2>
<sect2>
<title>Built-in system utilities</title>
@@ -297,12 +291,13 @@
and permissions. This single archive file can then be
transferred to other machines, where a System V
software-management command can be used to install it. This
- System V installation command (typically called pkgadd) unpacks
- the archive, copies the files into their final destinations
- based on the enclosed listing, and sets permissions and
- ownerships on the files as specified by the listing. Finally,
- this pkgadd command registers the list of freshly installed
- files into a system-wide database of installed files.
+ System V installation command (typically called
+ <command>pkgadd</command>) unpacks the archive, copies the files
+ into their final destinations based on the enclosed listing, and
+ sets permissions and ownerships on the files as specified by the
+ listing. Finally, this <command>pkgadd</command> command
+ registers the list of freshly installed files into a system-wide
+ database of installed files.
</para>
<para>
Such a system offers several advantages over manual software
@@ -317,7 +312,6 @@
</para>
</sect2>
</sect1>
-
<sect1>
<title>Linux Software Management Tools: Packages</title>
<para>
@@ -334,24 +328,26 @@
used by various distributions.
</para>
<para>
- The Gentoo Linux (www.gentoo.org) distribution, for example, uses
- a software-management system called Portage, which is very similar
- to the FreeBSD ports system. Like ports, Portage provides great
- control over software compilation and installation, providing a
- collection of scripts that automate much of the basic work of
- downloading and compiling software.
+ The Gentoo Linux (<ulink url="http://www.gentoo.org/"/>)
+ distribution, for example, uses a software-management system
+ called Portage, which is very similar to the FreeBSD ports system.
+ Like ports, Portage provides great control over software
+ compilation and installation, providing a collection of scripts
+ that automate much of the basic work of downloading and compiling
+ software.
</para>
<para>
At the other end of the spectrum, the now-defunct deepLinux
- distribution used a software-management system called deep-package
- (still available from
- www2.cddc.vt.edu/linux/distributions/deeplinux/tools. deep-package
- was intended to be a complete reimplementation of the Solaris
- pkgadd utility and its helpers. Like the Solaris pkgadd software,
- deep-package paid no attention to half of the question of how to
- manage software, focusing entirely on software installation and
- tracking issues while entirely ignoring the initial compilation of
- the software.
+ distribution used a software-management system called
+ <command>deep-package</command> (still available from
+ <ulink url="http://www2.cddc.vt.edu/linux/distributions/deeplinux/tools"/>).
+ <command>deep-package</command> was intended to be a complete
+ reimplementation of the Solaris <command>pkgadd</command> utility
+ and its helpers. Like the Solaris <command>pkgadd</command>
+ software, <command>deep-package</command> paid no attention to
+ half of the question of how to manage software, focusing entirely
+ on software installation and tracking issues while entirely
+ ignoring the initial compilation of the software.
</para>
<para>
More typically, however, Linux software-management tools use an
@@ -383,7 +379,7 @@
software.
</para>
<para>
- In the case of my full Red Hat Linux 7.3 installation, this
+ In the case of a full &RHL; 7.3 installation, this
package-management software maintains a database of information
regarding all 160,000 files on the system; as applications are
installed on the system, this database is updated with information
@@ -402,23 +398,24 @@
focuses on one of these tools, the RPM Package Management
software, or RPM.
</para>
+ <note>
+ <title>Change of Name</title>
+<!-- SE: Don't replace "Red Hat" with an entity here: we don't want the text to change -->
+ <para>
+ RPM was originally called Red Hat Package Manager. After
+ adoption by other Linux distributions, the name has changed to
+ simply the RPM Package Manager. The RPM initials remain the
+ same.
+ </para>
+ </note>
<para>
- Note
- </para>
- <para>
- RPM was originally called Red Hat Package Manager. After adoption
- by other Linux distributions, the name has changed to simply the
- RPM Package Manager. The RPM initials remain the same.
- </para>
- <para>
- As the original name implies, RPM was developed by Red Hat, Inc.,
+ As the original name implies, RPM was developed by &FORMAL-RHI;,
the major Linux distributor in the United States. Even though the
- original name seems to point to a Red Hat-only solution, most
- Linux distributions use the RPM software. The RPM software
- provides a foundation needed by Linux system administrators
- throughout the world. You can even use RPM on other operating
- systems, both Linux and non-Linux, as covered in Chapters 19 and
- 20, respectively.
+ original name seems to point to a &RH;-only solution, most Linux
+ distributions use the RPM software. The RPM software provides a
+ foundation needed by Linux system administrators throughout the
+ world. You can even use RPM on other operating systems, both Linux
+ and non-Linux, as covered in Chapters 19 and 20, respectively.
</para>
<para>
The RPM system provides all of the features needed to manage
@@ -432,50 +429,69 @@
with RPM packages and the commands you need to work with the RPM
system:
</para>
- <para>
- *Chapter 2 provides an overview of the RPM system, exploring what
- it was designed for and where it has weaknesses.
- </para>
- <para>
- *Chapter 3 discusses the technical details of how the RPM system
- works, where the database of packages gets stored, and what
- commands should be available for working with RPM packages.
- </para>
- <para>
- *Chapter 4 continues the discussion by covering the three major
- tasks you need to perform with RPM packages: installing software,
- removing software, and upgrading software you have already
- installed.
- </para>
- <para>
- *Chapter 5 covers the RPM database, how it works, where it
- resides, and how you can use it to better manage your system.
- </para>
- <para>
- *Chapter 6 delves into package dependencies, a very important
- concept. Most major applications depend on a number of other
- packages. Sometimes these dependencies get very complex, with one
- package depending on particular versions of other packages. With
- thousands of packages on your system, this can lead to a big mess.
- Chapter 6 helps you sort through the issues.
- </para>
- <para>
- *Chapter 7 covers the important issue of transactions, so that you
- can ensure your system gets updated in an orderly manner and so
- that you can roll back changes if something does not work out.
- </para>
- <para>
- *Chapter 8 introduces a host of tools that can help you find RPM
- packages as well as manage the packages on your system. This
- includes graphical interfaces on top of the RPM system and special
- Internet search sites devoted just to RPM packages.
- </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Chapter 2 provides an overview of the RPM system, exploring
+ what it was designed for and where it has weaknesses.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Chapter 3 discusses the technical details of how the RPM
+ system works, where the database of packages gets stored, and
+ what commands should be available for working with RPM
+ packages.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Chapter 4 continues the discussion by covering the three major
+ tasks you need to perform with RPM packages: installing
+ software, removing software, and upgrading software you have
+ already installed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Chapter 5 covers the RPM database, how it works, where it
+ resides, and how you can use it to better manage your system.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Chapter 6 delves into package dependencies, a very important
+ concept. Most major applications depend on a number of other
+ packages. Sometimes these dependencies get very complex, with
+ one package depending on particular versions of other
+ packages. With thousands of packages on your system, this can
+ lead to a big mess. Chapter 6 helps you sort through the
+ issues.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Chapter 7 covers the important issue of transactions, so that
+ you can ensure your system gets updated in an orderly manner
+ and so that you can roll back changes if something does not
+ work out.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Chapter 8 introduces a host of tools that can help you find
+ RPM packages as well as manage the packages on your system.
+ This includes graphical interfaces on top of the RPM system
+ and special Internet search sites devoted just to RPM
+ packages.
+ </para>
+ </listitem>
+ </orderedlist>
<para>
Later chapters cover creating RPM packages, programming with RPM,
and extending the functionality provided by the base RPM system.
</para>
</sect1>
-
<sect1>
<title>Summary</title>
<para>
18 years, 6 months