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, NONE, 1.1 package-notes-en.xml, NONE, 1.1 printing-en.xml, NONE, 1.1 project-overview-en.xml, NONE, 1.1 samba-en.xml, NONE, 1.1 security-en.xml, NONE, 1.1 server-tools-en.xml, NONE, 1.1 splash-en.xml, NONE, 1.1 web-servers-en.xml, NONE, 1.1 xorg-en.xml, NONE, 1.1 fedora.css, 1.1, 1.2 daemons.xml, 1.1, NONE database-servers.xml, 1.1, NONE desktop.xml, 1.1, NONE development-tools.xml, 1.1, NONE feedback.xml, 1.1, NONE file-servers.xml, 1.1, NONE file-systems.xml, 1.1, NONE hardware-reqs.xml, 1.1, NONE install-notes.xml, 1.1, NONE intro.xm! l, 1.1, NONE java-package.xml, 1.1, NONE kernel.xml, 1.1, NONE misc-server.xml, 1.1, NONE multimedia.xml, 1.1, NONE networking.xml, 1.1, NONE overview.xml, 1.1, NONE package-movement.xml, 1.1, NONE package-notes.xml, 1.1, NONE printing.xml, 1.1, NONE project-overview.xml, 1.1, NONE samba.xml, 1.1, NONE security.xml, 1.1, NONE server-tools.xml, 1.1, NONE splash.xml, 1.1, NONE web-servers.xml, 1.1, NONE xorg.xml, 1.1, NONE
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Tue Oct 25 02:48:52 UTC 2005
- Previous message (by thread): rpm-guide rpm-guide-intro-rpm-en.xml,1.1,1.2
- Next message (by thread): 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, 1.1, 1.2 splash-en.xml, 1.1, 1.2 web-servers-en.xml, 1.1, 1.2 xorg-en.xml, 1.1, 1.2
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
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&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-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 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
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 ---
- Previous message (by thread): rpm-guide rpm-guide-intro-rpm-en.xml,1.1,1.2
- Next message (by thread): 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, 1.1, 1.2 splash-en.xml, 1.1, 1.2 web-servers-en.xml, 1.1, 1.2 xorg-en.xml, 1.1, 1.2
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Fedora-docs-commits
mailing list