release-notes/FC4 daemons.xml, NONE, 1.1 database-servers.xml, NONE, 1.1 desktop.xml, NONE, 1.1 development-tools.xml, NONE, 1.1 feedback.xml, NONE, 1.1 file-servers.xml, NONE, 1.1 file-systems.xml, NONE, 1.1 hardware-reqs.xml, NONE, 1.1 install-notes.xml, NONE, 1.1 intro.xml, NONE, 1.1 java.xml, NONE, 1.1 kernel.xml, NONE, 1.1 misc-server.xml, NONE, 1.1 multimedia.xml, NONE, 1.1 networking.xml, NONE, 1.1 overview.xml, NONE, 1.1 package-movement.xml, NONE, 1.1 package-notes.xml, NONE, 1.1 printing.xml, NONE, 1.1 project-overview.xml, NONE, 1.1 samba.xml, NONE, 1.1 security.xml, NONE, 1.1 server-tools.xml, NONE, 1.1 web-servers.xml, NONE, 1.1 xorg.xml, NONE, 1.1 RELEASE-NOTES-master-en.xml, 1.1, 1.2
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Mon May 23 05:28:34 UTC 2005
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31593
Modified Files:
RELEASE-NOTES-master-en.xml
Added 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.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 web-servers.xml xorg.xml
Log Message:
New structure with sections separated into files for easier collaboration. Makefile hopefully coming soon.
--- NEW FILE daemons.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE database-servers.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE desktop.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE development-tools.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE feedback.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&op_sys=Linux&version=devel&component=fedora-release&component_text=&rep_platform=All&priority=normal&bug_severity=normal&bug_status=NEW&assigned_to=&cc=&estimated_time=0.0&bug_file_loc=http%3A%2F%2F&short_desc=FC3%20release%20notes%20--%20&comment=Please%20add%20a%20descriptive%20phrase%20to%20the%20summary%2C%20and%20more%20in-depth%0D%0Adescription%20here%20%28be%20sure%20to%20note%20any%20arch-specific%20issues%29%3A%0D%0A%0D%0A&keywords=&dependson=&blocked=114398&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug">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-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE file-servers.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE file-systems.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE hardware-reqs.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>
<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</para>
<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><remark os="test">(x86)</remark> &DISTRO; &DISTROVER; 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.</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 -->
<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>
<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>
<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>
<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>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE install-notes.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>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134508">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134508</ulink>
%%%</remark>
<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>
</note>
<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>
</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>
<para>NOTE: 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>
</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>
<para><remark os="test">(x86)</remark> <command>pci=off
ide1=0x180,0x386</command></para>
<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 &DISTRO; 1 systems running Ximian GNOME. The issue 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 issue:</para>
<para><remark os="test">(x86)</remark> 1) You may remove Ximian GNOME
from your system prior to upgrading to &DISTRO;.</para>
<para><remark os="test">(x86)</remark> 2) You may upgrade your system,
and then immediately reinstall Ximian GNOME.</para>
<para><remark os="test">(x86)</remark> 3) You may upgrade your system,
and then immediately remove all remaining Ximian RPMs, replacing
them with the corresponding &DISTRO; RPMs.</para>
<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-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE intro.xml ---
<section id="sn-intro">
<title>Introduction</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;, a
complete, general-purpose operating system built exclusively from open
source software.</para>
<note>
<title>Note</title>
<para>&DISTRO; is not a supported product of &FORMAL-RHI;</para>
</note>
<para>For more information, refer to the &PROJ; overview later in this
document.</para>
<para>The following topics related to &DISTRO; &DISTROVER; are covered in
this document:</para>
<itemizedlist>
<listitem os="test">
<para>Release notes feedback procedure</para>
</listitem>
<listitem>
<para>Introduction (this section)</para>
</listitem>
<listitem>
<para>Hardware requirements</para>
</listitem>
<listitem>
<para>Overview of this release</para>
</listitem>
<listitem>
<para>Installation-related notes</para>
</listitem>
<listitem>
<para>Package-specific notes</para>
</listitem>
<listitem>
<para>Packages added/removed/deprecated</para>
</listitem>
<listitem>
<para>An overview of the &PROJ;</para>
</listitem>
</itemizedlist>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE java.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE kernel.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE misc-server.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE multimedia.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE networking.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE overview.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>GCC 3.4</para>
</listitem>
<listitem>
<para>GNOME 2.8</para>
</listitem>
<listitem>
<para>KDE 3.3</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 includes a new "targeted" policy that
monitors specific daemons with less intrusion than the strict
policy in use before. This policy is enabled by default. For
more information, refer to:</para>
<para><ulink
url="http://fedora.redhat.com/docs/selinux-faq/">http://fedora.redhat.com/docs/selinux-faq/</ulink></para>
</listitem>
<listitem>
<para>Indic language support</para>
</listitem>
<listitem>
<para>Firefox and Mozilla can be enabled with pango rendering
support, which enables many text layout features, including the
rendering of CTL (Complex Text Layout) such as Indic languages. To
enable this, set the following environment variable when running
Firefox or Mozilla:</para>
<para><command>MOZ_ENABLE_PANGO=1</command></para>
</listitem>
<listitem>
<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>Kernel and <filename>e2fsprogs</filename> support for online
growing of ext3 file systems</para>
</listitem>
<listitem>
<para>Various desktop-related features, including, but not limited
to:</para>
<itemizedlist>
<listitem>
<para>Remote desktops using VNC (<ulink
url="http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html"></ulink>)</para>
</listitem>
<listitem>
<para>Printing improvements (<ulink
url="http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html">http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html</ulink>)</para>
</listitem>
<listitem>
<para>Evolution 2.0</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-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE package-movement.xml ---
<section id="sn-package-movement">
<title>Packages Added/Removed/Deprecated</title>
<para>This section contains lists of packages that fit into the following
categories:</para>
<itemizedlist>
<listitem>
<para>Packages that have been added to &DISTRO; &DISTROVER;</para>
</listitem>
<listitem>
<para>Packages that have been removed from &DISTRO; &DISTROVER;</para>
</listitem>
<listitem>
<para>Packages that have been deprecated, and may be removed from a
future release of &DISTRO;</para>
</listitem>
</itemizedlist>
<section>
<title>Packages Added</title>
<para>The following packages have been added to &DISTRO;
&DISTROVER;:</para>
<itemizedlist>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> Canna-libs (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> FreeWnn-libs (i386)</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> HelixPlayer</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> ImageMagick (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> ImageMagick-c++ (i386)</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> NetworkManager</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> NetworkManager-gnome</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> Omni (i386)</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> Pyrex</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> SDL (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> SDL_image (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> SDL_mixer (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> SDL_net (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> VFlib2 (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> Xaw3d (i386)</para>
</listitem>
<listitem arch="x86">
<para><remark os="test">(x86)</remark> aiksaurus</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> aiksaurus (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> aiksaurus (x86_64)</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aiksaurus-devel</para>
</listitem>
<listitem arch="x86">
<para><remark os="test">(x86)</remark> aiksaurus-gtk</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> aiksaurus-gtk (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> aiksaurus-gtk (x86_64)</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aiksaurus-gtk-devel</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> alchemist (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> alsa-lib (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> apr (i386)</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> arptables_jf</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> arts (i386)</para>
</listitem>
<listitem arch="x86_64">
<para><remark os="test">(x86_64)</remark> aspell (i386)</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-af</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-bg</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-br</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-ca</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-cs</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-cy</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-el</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-fo</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-ga</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-gd</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-gl</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-hr</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-ia</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> aspell-id</para>
</listitem>
[...1938 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-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE package-notes.xml ---
<section>
<title>Package-Specific Notes</title>
<para>The following sections contain information regarding packages that
have undergone significant changes for &DISTRO; &DISTROVER;. For easier
access, they are organized using the same groups used in Anaconda.</para>
<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>
<title>Base</title>
<para>This section contains information related to basic system
components.</para>
<section>
<title><filename>openssh</filename></title>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131544">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131544</ulink>
%%%</remark>
<para>&DISTRO; &DISTROVER; contains OpenSSH 3.9, which includes strict
permission and ownership checks for the
<filename>~/.ssh/config</filename> file. These checks mean that
<command>ssh</command> will exit if this file does not have
appropriate ownership and permissions.</para>
<para>Therefore, make sure that <filename>~/.ssh/config</filename> is
owned by the owner of <filename>~/</filename>, and that its
permissions are set to mode 600.</para>
<para>In addition, OpenSSH is no longer configured to request X11
forwarding by default when connecting to servers. To enable X11
forwarding, the <command>-X</command> or <command>-Y</command> option
must be specified, or the <command>ForwardX11</command> option must be
enabled in the <filename>~/.ssh/config</filename> file.</para>
<para>The behavior of ssh clients that are invoked with the
<command>-X</command> flag 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
<command>-Y</command> flag instead of the <command>-X</command> flag,
or set <command>ForwardX11Trusted</command> in the
<filename>~/.ssh/config</filename> file.</para>
</section>
</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>
<title>Core</title>
<para>This section contains the most elemental components of &DISTRO;,
including the kernel.</para>
<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>
<title><filename>kernel</filename></title>
<itemizedlist>
<listitem>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135586">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135586</ulink>
%%%</remark>
<para>In the past, the process of updating the kernel did not change
the default kernel in the system's boot loader
configuration.</para>
<para>&DISTRO; &DISTROVER; changes this behavior to set
newly-installed kernels as the default. This behavior applies to
all installation methods (including <command>rpm
-i</command>).</para>
<para>This behavior is controlled by two lines in the
<filename>/etc/sysconfig/kernel</filename> file:</para>
<itemizedlist>
<listitem>
<para><command>UPDATEDEFAULT</command> — Controls whether
new kernels will be booted by default (default value:
<command>yes</command>)</para>
</listitem>
<listitem>
<para><command>DEFAULTKERNEL</command> — kernel RPMs whose
names match this value will be booted by default (default
value: depends on hardware configuration)</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135269">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135269</ulink>
%%%</remark>
<para>In order to eliminate the redundancy inherent in providing a
separate package for the kernel source code when that source code
already exists in the kernel's <filename>.src.rpm</filename> file,
&DISTRO; &DISTROVER; no longer includes the
<filename>kernel-source</filename> package. Users that require
access to the kernel sources can find them in the
<filename>kernel</filename> <filename>.src.rpm</filename> file.
To create an exploded source tree from this file, perform the
following steps (note that
<filename><replaceable><version></replaceable></filename>
refers to the version specification for your currently-running
kernel):</para>
<orderedlist>
<listitem>
<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 "SRPMS" CD iso image</para>
</listitem>
<listitem>
<para>The FTP site where you got the kernel package</para>
</listitem>
<listitem>
<para>By running the following command:</para>
<para><command>up2date --get-source kernel</command></para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Install
<filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
(given the default RPM configuration, the files this package
contains will be written to
<filename>/usr/src/redhat/</filename>)</para>
</listitem>
<listitem>
<para>Change directory to
<filename>/usr/src/redhat/SPECS/</filename>, and issue the
following command:</para>
<para><command>rpmbuild -bp
--target=<replaceable><arch></replaceable>
kernel.spec</command></para>
<para>(Where
<command><replaceable><arch></replaceable></command> is
the desired target architecture.)</para>
<para>On a default RPM configuration, the kernel tree will be
located in <filename>/usr/src/redhat/BUILD/</filename>.</para>
</listitem>
<listitem>
<para>In resulting tree, 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>
<para><command>cp
<replaceable><desired-file></replaceable>
./.config</command></para>
</listitem>
<listitem>
<para>Issue the following command:</para>
<para><command>make oldconfig</command></para>
</listitem>
</orderedlist>
<para>You can then proceed as usual.</para>
<note>
<title>Note</title>
<para>An exploded source tree is <emphasis>not</emphasis> required
to build kernel modules against the currently in-use kernel.</para>
<para>For example, to build the <filename>foo.ko</filename>
module, create the following file (named
<filename>Makefile</filename>) in the directory containing the
<filename>foo.c</filename> file:</para>
<screen>
<computeroutput>
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
</computeroutput>
</screen>
<para>Issue the <command>make</command> command to build the
<filename>foo.ko</filename> module.</para>
</note>
</listitem>
<listitem>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136770">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136770</ulink>
%%%</remark>
<para>I<subscript>2</subscript>O SCSI RAID adapters from
manufacturers such as Adaptec now use the
<filename>i2o_block</filename> driver, rather than the
<filename>dpt_i2o</filename> driver used by &DISTRO; 1 and earlier
distributions.</para>
<para>Be aware that block devices used by the
<filename>i2o_block</filename> driver are
<filename>/dev/i2o/hd*</filename> rather than the
<filename>/dev/sd*</filename> SCSI devices. This may be
problematic for those upgrading from older distributions that used
the <filename>dpt_i2o</filename> driver. Therefore, after an
upgrade to &DISTRO; &DISTROVER;, you may need to boot using a
rescue disk and edit your <filename>/etc/fstab</filename> file to
use the new devices.</para>
<para>For more information about the new I<subscript>2</subscript>O
device layer and &DISTRO;-specific notes, visit the
I<subscript>2</subscript>O homepage:</para>
<para><ulink
url="http://i2o.shadowconnect.com/">http://i2o.shadowconnect.com/</ulink></para>
</listitem>
</itemizedlist>
</section>
</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>
<section os="bogus">
<title>GNOME Software Development</title>
<para>*** Enter group description here ***</para>
</section>
<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><filename>iiimf</filename></title>
<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>
<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>
<section os="bogus">
<title>Printing Support</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Ruby</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>SQL Database Server</title>
<para>*** Enter group description here ***</para>
</section>
<section os="bogus">
<title>Server</title>
<para>*** Enter group description here ***</para>
</section>
<section>
<title>Server Configuration Tools</title>
<para>This section contains information related to various server
configuration tools.</para>
<section>
<title><filename>system-config-securitylevel</filename></title>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135621">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135621</ulink>
%%%</remark>
<para>The firewall constructed by the
<command>system-config-securitylevel</command> configuration tool now
allows CUPS and Multicast DNS (mDNS) browsing. Note that, at the
present time, these services cannot be disabled by
<command>system-config-securitylevel</command>.</para>
</section>
</section>
<section>
<title>Sound and Video</title>
<para>This section contains information related to multimedia
applications.</para>
<section>
<title><filename>k3b</filename></title>
<para>Past users of the CD/DVD burning application
<application>k3b</application> may notice that the program
<command>k3bsetup</command> is missing. This is because
<command>k3bsetup</command> is not necessary under &DISTRO;
&DISTROVER;.</para>
</section>
</section>
<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>
<section>
<title>Web Server</title>
<para>This section contains information related to Web-related
tools.</para>
<section>
<title><filename>crypto-utils</filename></title>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136312">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136312</ulink>
%%%</remark>
<para>The <command>certwatch(1)</command> tool has been added to the
<filename>crypto-utils</filename> package. This tool is used to send
warning mail to root when any configured SSL certificates have expired
or are approaching the expiration date. By default, the tool checks
any certificates that are enabled in the <filename>mod_ssl</filename>
configuration.</para>
</section>
<section>
<title><filename>httpd</filename></title>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136469">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136469</ulink>
%%%</remark>
<para>By default, the <command>httpd</command> daemon is now started
using the C locale, rather than using the configured system locale
setting. This behavior can be changed by setting the
<envar>HTTPD_LANG</envar> variable in the
<filename>/etc/sysconfig/httpd</filename> file.</para>
</section>
<section>
<title><filename>php</filename></title>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131440">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131440</ulink>
%%%</remark>
<para>The gd, mbstring, and ncurses extensions have been moved to the
<filename>php-gd</filename>, <filename>php-mbstring</filename>, and
<filename>php-ncurses</filename> packages, respectively. Note that
you will need to install these packages manually (if required) when
upgrading from an earlier release.</para>
</section>
</section>
<section>
<title>Windows File Server</title>
<para>This section contains information related to Samba, software that
makes it possible to share files between Linux and Windows
systems.</para>
<section>
<title><filename>samba</filename></title>
<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 Nautilus to
display shares. The failure is due to the firewall disrupting the
broadcast mode of SMB browsing, which is Samba's default setting.
There are two workarounds:</para>
<itemizedlist>
<listitem>
<para>Configure a WINS server on the network, and set the "wins
server" option in <filename>smb.conf</filename> to the address of
the WINS server.</para>
</listitem>
<listitem>
<para>Disable the firewall</para>
</listitem>
</itemizedlist>
<warning>
<title>Warning</title>
<para>Depending on your system and network configurations, disabling
the firewall can greatly increase the chance of your system being
attacked and compromised. Make sure you <emphasis>fully</emphasis>
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>
</section>
<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>
<title>X Window System</title>
<para>This section contains information related to the X Window System
implementation provided with &DISTRO;.</para>
<section>
<title><filename>xorg-x11</filename></title>
<itemizedlist>
<listitem>
<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; 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>
</listitem>
<listitem>
<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>
<para>- The original (15+ year old) subsystem is referred to as the
"core X font subsystem". Fonts rendered by this subsystem are not
anti-aliased, are handled by the X server, and have names
like:</para>
<para>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</para>
<para>The newer font subsystem is known as "fontconfig", and allows
applications direct access to the font files. Fontconfig is often
used along with the "Xft" library, which allows applications to
render fontconfig fonts to the screen with antialiasing.
Fontconfig uses more human-friendly names like:</para>
<para>Luxi Sans-10</para>
<para>Over time, fontconfig/Xft 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; most everything else
uses the core X fonts.</para>
<para>In the future, &DISTRO; may support only fontconfig/Xft in
place of the XFS font server as the default local font access
method.</para>
<para>NOTE: An exception to the font subsystem usage outlined above
is OpenOffice.org (which uses its own font rendering
technology).</para>
<para>If you wish to add new fonts to your &DISTRO; &DISTROVER;
system, you must be aware that the steps necessary depend on which
font subsystem is to use the new fonts. For the core X font
subsystem, you must:</para>
<para>1. Create the <filename>/usr/share/fonts/local/</filename>
directory (if it doesn't already exist):</para>
<para><command>mkdir /usr/share/fonts/local/</command></para>
<para>2. Copy the new font file into
<filename>/usr/share/fonts/local/</filename></para>
<para>3. 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>
<para><command>ttmkfdir -d /usr/share/fonts/local/ -o
/usr/share/fonts/local/fonts.scale</command></para>
<para><command>mkfontdir /usr/share/fonts/local/</command></para>
<para>4. If you had to create
<filename>/usr/share/fonts/local/</filename>, you must then add it
to the X font server (xfs) path:</para>
<para><command>chkfontpath --add
/usr/share/fonts/local/</command></para>
<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>
<para><command>fc-cache
<replaceable><directory></replaceable></command></para>
<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>
<para>NOTE: 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>
</listitem>
<listitem>
<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>
<para><command>style "user-font" {</command></para>
<para><command>fontset =
"<replaceable><font-specification></replaceable>"</command></para>
<para><command>}</command></para>
<para><computeroutput> </computeroutput></para>
<para><computeroutput>widget_class "*" style "user-font"</computeroutput></para>
<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>
</listitem>
</itemizedlist>
</section>
</section>
<section os="bogus">
<title>XEmacs</title>
<para>*** Enter group description here ***</para>
</section>
<section>
<title>Miscellaneous Notes</title>
<para>This section contains information related to packages that do not
fit in any of the proceeding categories.</para>
<section>
<title><filename>compat-db</filename></title>
<remark os="test">%%% <ulink
url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133553">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133553</ulink>
%%%</remark>
<para>C++ and TCL bindings are no longer contained in the
<filename>compat-db</filename> package. Applications requiring these
bindings must be ported to the currently-shipping DB library.</para>
</section>
<section>
<title><filename>nscd</filename></title>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131389">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131389</ulink>
%%%</remark>
<para>The nscd name service cache daemon may now maintain a persistent
cache across restarts or system reboots. Each database (user, group,
and host, respectively) can be made selected to be persistent by
setting the appropriate line in <filename>/etc/nscd.conf</filename> to
"yes". Entries are not removed from the cache until they are proven
to be no longer of interest. All entries whose time-to-live expires
but are otherwise interesting are automatically reloaded, which helps
in situations where the directory and name services become temporarily
unavailable.</para>
<para>The nscd name service daemon is also able to communicate faster
with client programs. This feature must be enabled explicitly by
setting the "shared" entry for the appropriate database in
<filename>/etc/nscd.conf</filename> to "yes".</para>
</section>
<section>
<title><filename>udev</filename></title>
<remark os="test">%%% <ulink
url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133269">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133269</ulink>
%%%</remark>
<para>&DISTRO; &DISTROVER; has switched from a static
<filename>/dev/</filename> directory to one that is dynamically
managed via <filename>udev</filename>. This allows device nodes to be
created on demand as drivers are loaded.</para>
<para>For more information on <filename>udev</filename>, refer to the
<command>udev(8)</command> man page and the following link:</para>
<para><ulink
url="http://people.redhat.com/~harald/udev.html">http://people.redhat.com/~harald/udev.html</ulink></para>
<para>Additional rules for <filename>udev</filename> should be placed in
a separate file in the <filename>/etc/udev/rules.d/</filename>
directory.</para>
<para>Additional permission rules for <filename>udev</filename> should
be placed in a separate file in the
<filename>/etc/udev/permissions.d/</filename> directory.</para>
<para>Systems upgraded to &DISTRO; &DISTROVER; using Anaconda will
automatically be reconfigured to use <filename>udev</filename>.
However (although <emphasis>NOT</emphasis> recommended) it is possible
to perform a "live" upgrade to <filename>udev</filename> using the
following steps:</para>
<orderedlist>
<listitem>
<para>Ensure that you are running a 2.6 kernel</para>
</listitem>
<listitem>
<para>Ensure that <filename>/sys/</filename> is mounted</para>
</listitem>
<listitem>
<para>Install the <filename>initscripts</filename> RPM supplied with
&DISTRO; &DISTROVER;</para>
</listitem>
<listitem>
<para>Install the new <filename>udev</filename> RPM supplied with
&DISTRO; &DISTROVER;</para>
</listitem>
<listitem>
<para>Execute <command>/sbin/start_udev</command></para>
</listitem>
<listitem>
<para>Install the new <filename>mkinitrd</filename> RPM supplied
with &DISTRO; &DISTROVER;</para>
</listitem>
<listitem>
<para>Perform one of the following steps:</para>
<para>· Install the new <filename>kernel</filename> RPM
supplied with &DISTRO; &DISTROVER;</para>
<para>OR:</para>
<para>· Re-run <command>mkinitrd</command> for your existing
kernel(s)</para>
</listitem>
</orderedlist>
<warning>
<title>Warning</title>
<para>Improperly performing these steps can result in a system
configuration that will not boot properly.</para>
</warning>
</section>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE printing.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE project-overview.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 will be done in a public forum. The project will
produce time-based releases of &DISTRO; about 2-3 times a year, with a
public release schedule. The &RH; engineering team will continue to
participate in building &DISTRO; and will invite and encourage 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 at redhat.com — For users of &DISTRO;
releases</para>
</listitem>
<listitem>
<para>fedora-test-list at redhat.com — For testers of &DISTRO; test
releases</para>
</listitem>
<listitem>
<para>fedora-devel-list at redhat.com — For developers, developers,
developers</para>
</listitem>
<listitem>
<para>fedora-docs-list at redhat.com — For participants of the docs
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>NOTE: 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>NOTE: &RH; has no control over the Fedora IRC channels or their
content.</para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE samba.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE security.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE server-tools.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE web-servers.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE xorg.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-master-en.xml" "article" "section")
fill-column: 72
End:
-->
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.1 -r 1.2 RELEASE-NOTES-master-en.xml
Index: RELEASE-NOTES-master-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/RELEASE-NOTES-master-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- RELEASE-NOTES-master-en.xml 20 May 2005 21:55:11 -0000 1.1
+++ RELEASE-NOTES-master-en.xml 23 May 2005 05:28:31 -0000 1.2
@@ -1,4264 +1,70 @@
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+ "/usr/share/sgml/docbook/xml-dtd-4.3-1.0-25/docbookx.dtd" [
-<!ENTITY RH "Red Hat"> <!-- The generic term "Red Hat" -->
-<!ENTITY RHL "&RH; Linux"> <!-- The generic term "Red Hat Linux" -->
-<!ENTITY FORMAL-RHI "&RH;, Inc."> <!-- Formal version -->
+<!-- *************** Section files *************** -->
+<!ENTITY FEEDBACK SYSTEM "./feedback.xml">
+<!ENTITY HARDWARE-REQS SYSTEM "./hardware-reqs.xml">
+<!ENTITY INSTALL-NOTES SYSTEM "./install-notes.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 SYSTEM "./java.xml">
+<!ENTITY NETWORKING SYSTEM "./networking.xml">
+<!ENTITY XORG SYSTEM "./xorg.xml">
+
+
+<!-- *************** COMMON FDP entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../../common/fedora-entities-en.xml">
+%FEDORA-ENTITIES-EN;
+<!ENTITY LEGALNOTICE SYSTEM "../../common/legalnotice-en.xml">
+
+<!-- *************** Local entities *************** -->
+
+<!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-05-22-T16:20-0800)"> <!-- 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 BUG-URL "http://tinyurl.com/">
<!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
-<!ENTITY PROJ "&NAME; Project"> <!-- The project's name -->
-<!ENTITY DISTRO "&NAME; Core"> <!-- The software's name -->
+<!ENTITY PROJ "&FP;"> <!-- The project's name -->
+<!ENTITY DISTRO "&FC;"> <!-- The software's name -->
<!ENTITY DISTROVER "@VERSION@"> <!-- The software's version -->
-<!-- *************** Local entities for SELinux sect *************** -->
-<!ENTITY SEL "SELinux"> <!-- -->
-
]>
<article id="index" lang="en" arch="x86;x86_64" os="test;final">
<articleinfo>
<title>&DISTRO; &DISTROVER; Release Notes</title>
<copyright>
- <year>2004</year>
+ <year>2005</year>
<holder>&FORMAL-RHI;</holder>
</copyright>
- <legalnotice id="legalnotice">
-
- <para>Permission is granted to copy, distribute, and/or modify this
- document under the terms of the GNU Free Documentation License, Version
- 1.2 or any later version published by the Free Software Foundation; with
- no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
- copy of the license is available at <ulink
- url="http://www.gnu.org/licenses/fdl.html">http://www.gnu.org/licenses/fdl.html</ulink>.</para>
-
- <para>This document may be copied and distributed in any medium, either
- commercially or non-commercially, provided that the GNU Free
- Documentation License (FDL), the copyright notices, and the license
- notice saying the GNU FDL applies to the document are reproduced in all
- copies, and that you add no other conditions whatsoever to those of the
- GNU FDL.</para>
-
- <para>&RH;, &RH; Network, the &RH; "Shadow Man" logo, RPM, Maximum RPM,
- the RPM logo, Linux Library, PowerTools, Linux Undercover, RHmember,
- RHmember More, Rough Cuts, Rawhide and all &RH;-based trademarks and
- logos are trademarks or registered trademarks of &FORMAL-RHI; in the
- United States and other countries.</para>
-
- <para>The Fedora trademark is a trademark of &FORMAL-RHI; in the United
- States and other countries.</para>
-
- <para>Linux is a registered trademark of Linus Torvalds.</para>
-
- <para>All other trademarks and copyrights referred to are the property of
- their respective owners.</para>
-
- <para>The GPG fingerprint of the <computeroutput>"Fedora Project
- <fedora at redhat.com>"</computeroutput> key is:</para>
-
- <para>CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2</para>
- </legalnotice>
+ &LEGALNOTICE;
</articleinfo>
- <sect1 id="s1-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&op_sys=Linux&version=devel&component=fedora-release&component_text=&rep_platform=All&priority=normal&bug_severity=normal&bug_status=NEW&assigned_to=&cc=&estimated_time=0.0&bug_file_loc=http%3A%2F%2F&short_desc=FC3%20release%20notes%20--%20&comment=Please%20add%20a%20descriptive%20phrase%20to%20the%20summary%2C%20and%20more%20in-depth%0D%0Adescription%20here%20%28be%20sure%20to%20note%20any%20arch-specific%20issues%29%3A%0D%0A%0D%0A&keywords=&dependson=&blocked=114398&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug">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>
-
- </sect1>
-
- <sect1 id="s1-intro">
- <title>Introduction</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;, a
- complete, general-purpose operating system built exclusively from open
- source software.</para>
-
- <note>
- <title>Note</title>
-
- <para>&DISTRO; is not a supported product of &FORMAL-RHI;</para>
- </note>
-
- <para>For more information, refer to the &PROJ; overview later in this
- document.</para>
-
- <para>The following topics related to &DISTRO; &DISTROVER; are covered in
- this document:</para>
-
- <itemizedlist>
- <listitem os="test">
- <para>Release notes feedback procedure</para>
- </listitem>
-
- <listitem>
- <para>Introduction (this section)</para>
- </listitem>
-
- <listitem>
- <para>Hardware requirements</para>
- </listitem>
-
- <listitem>
- <para>Overview of this release</para>
- </listitem>
-
- <listitem>
- <para>Installation-related notes</para>
- </listitem>
-
- <listitem>
- <para>Package-specific notes</para>
- </listitem>
-
- <listitem>
[...3925 lines suppressed...]
- <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>
- </sect2>
-
- <sect2>
- <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>
- </sect2>
- </sect1>
-
- <sect1 id="s1-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 will be done in a public forum. The project will
- produce time-based releases of &DISTRO; about 2-3 times a year, with a
- public release schedule. The &RH; engineering team will continue to
- participate in building &DISTRO; and will invite and encourage 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 at redhat.com — For users of &DISTRO;
- releases</para>
- </listitem>
-
- <listitem>
- <para>fedora-test-list at redhat.com — For testers of &DISTRO; test
- releases</para>
- </listitem>
-
- <listitem>
- <para>fedora-devel-list at redhat.com — For developers, developers,
- developers</para>
- </listitem>
-
- <listitem>
- <para>fedora-docs-list at redhat.com — For participants of the docs
- 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>NOTE: 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>
+ &FEEDBACK;
+ &INTRO;
+ &HARDWARE-REQS;
+ &OVERVIEW;
+ &INSTALL-NOTES;
+ &PACKAGE-NOTES;
+ &PACKAGE-MOVEMENT;
+ &PROJECT-OVERVIEW;
- <para>NOTE: &RH; has no control over the Fedora IRC channels or their
- content.</para>
- </sect1>
<ackno>(
<emphasis arch="x86">x86</emphasis>
<emphasis arch="x86_64">x86_64</emphasis>
More information about the Fedora-docs-commits
mailing list