release-notes Makefile, NONE, 1.1 README-en.xml, NONE, 1.1 RELEASE-NOTES-en.xml, NONE, 1.1 RELEASE-NOTES-master-en.xml, NONE, 1.1 announcement-release.txt, NONE, 1.1 daemons.xml, NONE, 1.1 database-servers.xml, NONE, 1.1 desktop.xml, NONE, 1.1 development-tools.xml, NONE, 1.1 eula.py, NONE, 1.1 eula.txt, NONE, 1.1 fedora-devel.repo, NONE, 1.1 fedora-release.spec, NONE, 1.1 fedora-updates-testing.repo, NONE, 1.1 fedora-updates.repo, NONE, 1.1 fedora.css, NONE, 1.1 fedora.repo, NONE, 1.1 feedback.xml, NONE, 1.1 file-servers.xml, NONE, 1.1 file-systems.xml, NONE, 1.1 hardware-reqs.xml, NONE, 1.1 install-notes.xml, NONE, 1.1 intro.xml, NONE, 1.1 java-package.xml, NONE, 1.1 kernel.xml, NONE, 1.1 main.xsl, NONE, 1.1 misc-server.xml, NONE, 1.1 multimedia.xml, NONE, 1.1 networking.xml, NONE, 1.1 overview.xml, NONE, 1.1 package-movement.xml, NONE, 1.1 package-notes.xml, NONE, 1.1 printing.xml, NONE, 1.1 project-overview.xml, NONE, 1.1 readmes.xsl, NONE, 1.1 samba.xml, NONE, 1.1 security.xml, NONE, 1.1 server-tools.xml, NONE, 1.1 sources, NONE, 1.1 spl! ash.xml,NONE,1.1 web-servers.xml,NONE,1.1 xorg.xml,NONE,1.1
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Mon Oct 24 13:13:37 UTC 2005
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16016
Added Files:
Makefile README-en.xml RELEASE-NOTES-en.xml
RELEASE-NOTES-master-en.xml announcement-release.txt
daemons.xml database-servers.xml desktop.xml
development-tools.xml eula.py eula.txt fedora-devel.repo
fedora-release.spec fedora-updates-testing.repo
fedora-updates.repo fedora.css fedora.repo feedback.xml
file-servers.xml file-systems.xml hardware-reqs.xml
install-notes.xml intro.xml java-package.xml kernel.xml
main.xsl misc-server.xml multimedia.xml networking.xml
overview.xml package-movement.xml package-notes.xml
printing.xml project-overview.xml readmes.xsl samba.xml
security.xml server-tools.xml sources splash.xml
web-servers.xml xorg.xml
Log Message:
EPOCH. Moving all essential release notes XML and related files to the root level for the module. This is done as part of FC5 test1 relnote construction. This is an epoch event because previously versioning was done with unique directories for each release. From this moment forward we are going to use CVS tagging and branching with files all within this directory. Sub-directories are therefore archive directories. It is important to note that this check-in perfectly mirrors the state of FC4 latest release notes, therefore this first check-in shall be tagged as FC4 so that we can return to this point for building FC4 notes in the future. *docs*
--- NEW FILE Makefile ---
LANG = en
DOCS_SETUP_PATH= ../../docs-common
XSLPDF = $(DOCS_SETUP_PATH)/xsl/main-pdf.xsl
XSLHTML = $(DOCS_SETUP_PATH)/xsl/main-html-nochunks-relnotes.xsl
XSLPDFCOMMONS = ${XSLPDF}
XSLHTMLCOMMONS = ${XSLHTML}
XMLCOMMONSPATH=${DOCS_SETUP_PATH}/common
XMLCOMMONS=${XMLCOMMONSPATH}/cvs-en.xml \
${XMLCOMMONSPATH}/draftnotice-en.xml \
${XMLCOMMONSPATH}/fedora-entities-en.ent \
${XMLCOMMONSPATH}/fedora-entities-en.xml \
${XMLCOMMONSPATH}/legacynotice-en.xml \
${XMLCOMMONSPATH}/legalnotice-en.xml \
${XMLCOMMONSPATH}/obsoletenotice-en.xml
.SUFFIXES:
.SUFFIXES: .html .pdf .xml
all: README-${LANG}.html \
RELEASE-NOTES-${LANG}.html \
RELEASE-NOTES-${LANG}.txt \
README-${LANG}.txt
#README-${LANG}.pdf RELEASE-NOTES-${LANG}.pdf
%.pdf: %.xml
xmlto pdf -x ${XSLPDF} $<
%.html: %.xml
${RM} -r ${@:.html=}
xmlto html -x ${XSLHTML} -o ${@:.html=} $<
mkdir -p ${@:.html=}/stylesheet-images
mkdir -p ${@:.html=}/figs
cp $(DOCS_SETUP_PATH)/stylesheet-images/*.png ${@:.html=}/stylesheet-images
cp ./figs/*.png ${@:.html=}/figs
cp $(DOCS_SETUP_PATH)/css/fedora.css ${@:.html=}
mv ${@:.html=}/${@:.html=.proc} ${@:.html=}/$@
ln -sf ${@:.html=}/$@ $@
%.txt: %.xml
xmlto txt $<
# mv $@ RELEASE-NOTES-${LANG}
# FIXME eula.txt: eula.py
# FIXME python -c "import py_compile; py_compile.compile('eula.py')"
# Note: keep "RELEASE-NOTES-en.xml" first, for now.
RNFILES=RELEASE-NOTES-en.xml 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
# README-${LANG}.pdf: README-en.xml
# README-${LANG}.html: README-en.xml
RELEASE-NOTES-${LANG}.pdf: ${RNFILES} ${XMLCOMMONS} ${XSLPDFCOMMONS}
RELEASE-NOTES-${LANG}.html: ${RNFILES} ${XMLCOMMONS} ${XSLHTMLCOMMONS}
RELEASE-NOTES-${LANG}.txt: ${RNFILES} ${XMLCOMMONS}
clean:
${RM} ChangeLog ChangeLog.xml
distclean clobber: clean
${RM} ChangeLog-${LANG}.html ChangeLog.txt
${RM} -r README-${LANG}.pdf README-${LANG}.html README-${LANG}.txt
${RM} -r RELEASE-NOTES-${LANG}.pdf RELEASE-NOTES-${LANG}.html \
RELEASE-NOTES-${LANG} RELEASE-NOTES-${LANG}.txt
# If you have the "cvs2cl" package installed, then you can make
# fancy HTML ChangeLogs
ChangeLogs:
${RM} ChangeLog*
${MAKE} ChangeLog.txt
${MAKE} ChangeLog-${LANG}.html
ChangeLog.txt:
LANG=C cvs2cl -f ChangeLog.txt
ChangeLog.xml:
LANG=C cvs2cl --xml --xml-encoding UTF-8 -f ChangeLog.xml
ChangeLog-${LANG}.html: ChangeLog.xml
xsltproc -o $@ /usr/share/xml/cvs2cl/cl2html.xslt $<
--- NEW FILE README-en.xml ---
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY % ALPHA "IGNORE">
<!ENTITY % X86 "INCLUDE">
<!ENTITY % IA64 "IGNORE">
<!ENTITY % S390 "IGNORE">
<!ENTITY % HA "IGNORE">
<!ENTITY % X86-64 "IGNORE">
<!ENTITY RH "Red Hat"> <!-- The generic term "Red Hat" -->
<!ENTITY RHL "&RH; Linux"> <!-- The generic term "Red Hat Linux" -->
<!ENTITY FORMAL-RHI "&RH;, Inc."> <!-- Formal version -->
<!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
<!ENTITY PROJ "&NAME; Project"> <!-- The project's name -->
<!ENTITY DISTRO "&NAME; Core"> <!-- The software's name -->
<!ENTITY DISTROVER "4"> <!-- The software's version -->
]>
<article id="index" lang="en" arch="x86;x86_64" os="test;final">
<articleinfo>
<title>&DISTRO; &DISTROVER; README</title>
<copyright>
<year>2005</year>
<holder>&FORMAL-RHI;</holder>
</copyright>
<legalnotice id="legalnotice">
<para>The contents of this CD-ROM are Copyright © 2005 &PROJ; and
others. Refer to the End User License Agreement and individual
copyright notices in each source package for distribution terms.</para>
<para>&NAME;, &RH;, &RH; Network, the &RH; "Shadow Man" logo, RPM, Maximum
RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover,
RHmember, RHmember More, Rough Cuts, Rawhide and all &RH;-based
trademarks and logos are trademarks or registered trademarks of
&FORMAL-RHI; in the United States and other countries.</para>
<para>Linux is a registered trademark of Linus Torvalds.</para>
<para>Motif and UNIX are registered trademarks of The Open Group.</para>
<para>Intel and Pentium are registered trademarks of Intel
Corporation. Itanium and Celeron are trademarks of Intel
Corporation.</para>
<para>AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of Advanced
Micro Devices, Inc.</para>
<para>Windows is a registered trademark of Microsoft Corporation.</para>
<para>SSH and Secure Shell are trademarks of SSH Communications Security,
Inc.</para>
<para>FireWire is a trademark of Apple Computer Corporation.</para>
<para>All other trademarks and copyrights referred to are the property of
their respective owners.</para>
<para>The GPG fingerprint of the <computeroutput>"Fedora Project
<fedora at redhat.com>"</computeroutput> key is:</para>
<para>CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2</para>
</legalnotice>
</articleinfo>
<section id="dir-org">
<title>DIRECTORY ORGANIZATION</title>
<para>&DISTRO; is delivered on multiple CD-ROMs consisting of installation
CD-ROMs and source code CD-ROMs.</para>
<para>The first installation CD-ROM can be directly booted into the
installation on most modern systems, and contains the following directory
structure (where <filename>/mnt/cdrom</filename> is the mount point of the
CD-ROM):</para>
<screen arch="x86">
<!-- <remark os="test">(x86)</remark> -->
<computeroutput>
/mnt/cdrom
|----> Fedora
| |----> RPMS -- binary packages
| `----> base -- information on this release of Fedora
| Core used by the installation process
|----> images -- boot and driver disk images
|----> isolinux -- files necessary to boot from CD-ROM
|----> README -- this file
|----> RELEASE-NOTES -- the latest information about this release
| of Fedora Core
`----> RPM-GPG-KEY -- GPG signature for packages from Red Hat
</computeroutput>
</screen>
<!-- repetitive for the moment
<screen arch="x86_64">
<remark os="test">(x86_64)</remark>
<computeroutput>
/mnt/cdrom
|- - - -> Fedora
| |- - - -> RPMS - - binary packages
| `- - - -> base - - information on this release of Fedora
| Core used by the installation process
|- - - -> images - - boot disk ISO image
|- - - -> isolinux - - files necessary to boot from CD-ROM
|- - - -> README - - this file
|- - - -> RELEASE-NOTES - - the latest information about this release
| of Fedora Core
`- - - -> RPM-GPG-KEY - - GPG signature for packages from Red Hat
</computeroutput>
</screen>
-->
<para>The remaining Installation CD-ROMs are similar to Installation CD-ROM
1, except that only the <filename>Fedora</filename> subdirectory is
present.</para>
<para>The directory layout of each source code CD-ROM is as follows:</para>
<screen>
<computeroutput>
/mnt/cdrom
|----> SRPMS -- source packages
`----> RPM-GPG-KEY -- GPG signature for packages from Red Hat
</computeroutput>
</screen>
<para>If you are setting up an installation tree for NFS, FTP, or HTTP
installations, you need to copy the <filename>RELEASE-NOTES</filename>
files and all files from the <filename>Fedora</filename> directory on
discs 1-3. On Linux and Unix systems, the following process will properly
configure the /target/directory on your server (repeat for each disc):</para>
<orderedlist>
<listitem>
<para>Insert disc</para>
</listitem>
<listitem>
<para><command>mount /mnt/cdrom</command></para>
</listitem>
<listitem>
<para><command>cp -a /mnt/cdrom/Fedora
/target/directory</command></para>
</listitem>
<listitem>
<para><command>cp /mnt/cdrom/RELEASE-NOTES* /target/directory</command>
(Do this only for disc 1)</para>
</listitem>
<listitem>
<para><command>umount /mnt/cdrom</command></para>
</listitem>
</orderedlist>
</section>
<section id="installing">
<title>INSTALLING</title>
<para>Many computers can now automatically boot from CD-ROMs. If you have
such a machine (and it is properly configured) you can boot the &DISTRO;
CD-ROM directly. After booting, the &DISTRO; installation program will
start, and you will be able to install your system from the CD-ROM.</para>
<para arch="x86;x86_64"><!-- <remark os="test">(x86;x86_64)</remark> --> The
<filename>images/</filename> directory contains the file
<filename>boot.iso</filename>. This file is an ISO image that can be used
to boot the &DISTRO; installation program. It is a handy way to start
network-based installations without having to use multiple diskettes. To
use <filename>boot.iso</filename>, your computer must be able to boot from
its CD-ROM drive, and its BIOS settings must be configured to do so. You
must then burn <filename>boot.iso</filename> onto a recordable/rewriteable
CD-ROM.</para>
<para arch="x86;x86_64"><!-- <remark os="test">(x86;x86_64)</remark> --> Another image
file contained in the <filename>images/</filename> directory is
<filename>diskboot.img</filename>. This file is designed for use with USB
pen drives (or other bootable media with a capacity larger than a diskette
drive). Use the <command>dd</command> command to write the image.</para>
<note arch="x86;x86_64">
<title>Note</title>
<!-- <remark os="test">(x86;x86_64)</remark> -->
<para>The ability to use this image file with a USB pen drive depends on
the ability of your system's BIOS to boot from a USB device.</para>
</note>
</section>
<section id="get-help">
<title>GETTING HELP</title>
<para>For those that have web access, see <ulink
url="http://fedora.redhat.com">http://fedora.redhat.com</ulink>. In
particular, access to &PROJ; mailing lists can be found at:</para>
<para><ulink
url="https://listman.redhat.com/mailman/listinfo/">https://listman.redhat.com/mailman/listinfo/</ulink></para>
</section>
<section id="export-ctl">
<title>EXPORT CONTROL</title>
<para>The communication or transfer of any information received with this
product may be subject to specific government export approval. User shall
adhere to all applicable laws, regulations and rules relating to the
export or re-export of technical data or products to any proscribed
country listed in such applicable laws, regulations and rules unless
properly authorized. The obligations under this paragraph shall survive
in perpetuity.</para>
</section>
<!--
<section id="s1-test" os="test">
<title>README Feedback Procedure</title>
<para>(This section will disappear when the final &DISTRO; release is
created.)</para>
<para>If you feel that this README could be improved in some way, submit a
bug report in &RH;'s bug reporting system:</para>
<para><ulink
url="https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi">https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi</ulink></para>
<para>When posting your bug, include the following information in the
specified fields:</para>
<itemizedlist>
<listitem>
<para><guilabel>Product:</guilabel> &DISTRO;</para>
</listitem>
<listitem>
<para><guilabel>Version:</guilabel> Not really important (I'm using
"devel")</para>
</listitem>
<listitem>
<para><guilabel>Component:</guilabel> fedora-release</para>
</listitem>
<listitem>
<para><guilabel>Summary:</guilabel> A short description of what could be
improved. If it includes the word "README", so much the
better.</para>
</listitem>
<listitem>
<para><guilabel>Description:</guilabel> A more in-depth description of
what could be improved.</para>
</listitem>
<listitem>
<para><guilabel>Blocks:</guilabel> 114406 (The README blocker bug
number)</para>
</listitem>
</itemizedlist>
<para>A quick way of seeing what sorts of bugs have been posted against the
README is to look at the bugs listed in the <guilabel>Bug 114406 depends
on:</guilabel> field of the &DISTRO; release notes blocker bug:</para>
<para><ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114406">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114406</ulink></para>
<para>If you are interested in following the discussion of any of these
bugs, feel free to add yourself to the bug's CC list. That way, you'll
get email whenever there are any changes to the bug.</para>
<para>As bugs are posted for the various parts of the README file,
subsequent test versions of these release notes will contain links similar
to this one:</para>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114408">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114408</ulink>
%%%</remark>
<para>These links point to Bugzilla entries for the information preceding
the link. This makes it easier for people to contribute — just
point your browser at the link, add your comments to the bug, and commit
your changes.</para>
</section>
-->
<!--
<ackno>(
<emphasis arch="x86">x86</emphasis>
<emphasis arch="x86_64">x86_64</emphasis>
)</ackno>
-->
</article>
***** Error reading new file: [Errno 2] No such file or directory: 'RELEASE-NOTES-en.xml'
--- NEW FILE RELEASE-NOTES-master-en.xml ---
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
[
<!ENTITY RH "Red Hat">
<!ENTITY FORMAL-RHI "&RH;, Inc.">
<!ENTITY RHN "&RH; Network">
<!ENTITY RHL "Red Hat Linux">
<!ENTITY RHEL "&RH; Enterprise Linux">
<!ENTITY PROD "&RHEL;">
<!ENTITY PRODVER "@VERSION@">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
]>
<!-- if you add an arch to build, you must add it to this master list also -->
<article id="index" lang="en" arch="i386;ia64;s390;s390x;x86_64;ppc">
<articleinfo>
<title>&PROD; @VARIANTUPPER@ &PRODVER; Release Notes</title>
<copyright>
<year>2003</year>
<holder>&FORMAL-RHI;</holder>
</copyright>
</articleinfo>
<sect1 id="s1-overview">
<title>Overview</title>
<para>The following topics are covered in these release notes:</para>
<itemizedlist>
<listitem>
<para>Booting Anaconda</para>
</listitem>
<listitem arch="s390;s390x">
<para>Parameter file notes</para>
</listitem>
<listitem>
<para>Installation-related notes</para>
</listitem>
<listitem>
<para>Notes on input methods</para>
</listitem>
<listitem>
<para>General notes</para>
</listitem>
<listitem>
<para>Kernel notes</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="booting-anaconda">
<title>Booting Anaconda</title>
<para>This section describes the process necessary to boot
<application>Anaconda</application>, the &PROD; installation
program.</para>
<para arch="ppc">For the <trademark class="registered">IBM</trademark>
<trademark>eServer</trademark> <trademark>pSeries</trademark>:</para>
<para arch="i386;ia64;x86_64;ppc">The first CD-ROM is bootable, and can
be used to start the installation process. If a CD-ROM-based installation
is not desired (for example, if you want to install &PROD; &PRODVER; over a
network connection), a CD-ROM image file containing only those files
required to start the installation process is also available as
<filename>boot.iso</filename> in the <filename>images/</filename>
directory on the first CD-ROM.</para>
<para arch="ppc">A network boot image (named
<filename>netboot.img</filename>) is available, and is located in the
<filename>images/</filename> directory on Installation CD 1. Consult the
documentation that came with your system for instructions on setting up
network boot. Kernel command line arguments (such as anaconda options)
must be passed from the Open Firmware prompt. For example, if there is a
devalias named <command>network</command> for the device that is
configured for network booting, the following command line would load a
driver disk from an HTTP server:</para>
<para arch="ppc"><command>boot network
dd=http://server.example.com/path/to/driverdisk.img</command></para>
<para arch="ppc">Additional documentation for configuring netboot on pSeries can be
found here:</para>
<para arch="ppc"><ulink
url="http://people.redhat.com/msw/mirror/penguinppc.org/~hollis/linux/rs6k-netboot.shtml">http://people.redhat.com/msw/mirror/penguinppc.org/~hollis/linux/rs6k-netboot.shtml</ulink></para>
<para arch="ppc">For the IBM eServer <trademark>iSeries</trademark>:</para>
<para arch="ppc">You must direct <trademark
class="registered">OS/400</trademark> to boot the stream file
<filename>ppc/iSeries/boot.img</filename>, which is located on the first
CD-ROM. You can either point directly at the CD-ROM or copy the file to a
location in IFS. When the installation is complete, it will boot from
side C, but this will only work until you vary off your LPAR. After
varying off your LPAR, you must change your IPL source to side B to
continue booting &PROD;.</para>
<para arch="s390;s390x">You must download the
<filename>kernel.img</filename> and <filename>initrd.img</filename> files
from the <filename>images/</filename> directory into CMS. You can then
use these with a parameter file (described in the following section) to
start your installation. Once the Linux kernel has booted, use ssh to
access your VM and start the installation process. When the installation
finishes, you must use a command similar to <command>#cp ipl
0200</command> to bootstrap (or IPL) the Linux installation on the DASD at
0200.</para>
</sect1>
<sect1 id="s1-parm-file-notes" arch="s390;s390x">
<title>Parameter File Notes</title>
<para>The IBM <trademark class="registered">S/390</trademark> and IBM
eServer <trademark class="registered">zSeries</trademark> architectures
use a special parameter file to set up networking before the
installation program (<application>anaconda</application>) can be
started. This section describes the contents of the parameter
file.</para>
<para>The parameter file should contain no more than 80 characters per
line.</para>
<para>The VM reader has a limit of 11 lines for the parameter file (for a
total of 880 characters).</para>
<para>The DASD and the tape IPL have a limit of 896 characters.</para>
<para>The following parameters are required, and should always be
present:</para>
<itemizedlist>
<listitem>
<para><command>DASD=<replaceable><dasd-list></replaceable></command></para>
<para>Where
<command><replaceable><dasd-list></replaceable></command>
represents the list of DASD devices to be used by &PROD;. The list
can consist of one or more DASD numbers separated by commas, and can
also contain ranges, which are specified by two DASD numbers separated
by a hyphen. Both constructs can be combined in a single list, as in
the following example:</para>
<para><command>DASD=10A8,10A9,10AA,10A3-10A6</command></para>
<para>NOTE: Although autoprobing for DASDs is done if this parameter is
omitted, &RH; highly recommend including the DASD= parameter as the
device numbers (and therefore the device names) can vary when new DASD
is added to the &PROD; guest. This can result in an unusable
system.</para>
</listitem>
<listitem>
<para><command>root=<replaceable><file-system></replaceable></command></para>
<para>Where
<command><replaceable><file-system></replaceable></command>
represents the device on which the root file system can be found. For
for installation purposes, it should be set to
<command>/dev/ram0</command>, which is the ramdisk containing the
&PROD; installation program.</para>
</listitem>
</itemizedlist>
<para>The following parameters are required to set up networking:</para>
<itemizedlist>
<listitem>
<para><command>CHANDEV=<replaceable><device></replaceable>,<replaceable><input></replaceable>,<replaceable><output></replaceable></command></para>
<para>where:</para>
<para>·
<command><replaceable><device></replaceable></command> is the
type of device (for example, <command>ctc0</command>,
<command>escon0</command>, or <command>lcs0</command>)</para>
<para>·
<command><replaceable><input></replaceable></command> is the
input port for this device</para>
<para>·
<command><replaceable><output></replaceable></command> is the
output port for this device</para>
<para>For example:</para>
<para><command>CHANDEV=ctc0,0x600,0x601</command></para>
<para><command>CHANDEV=escon0,0x605,0x608</command></para>
<para>To force a specific CTC protocol, additional parameters can be
added. For example:</para>
<para><command>CHANDEV=ctc0,0x600,0x601,0,<replaceable><n></replaceable></command></para>
<para>where <replaceable><n></replaceable> is one of the
following:</para>
<para>· <command>0</command> for compatibility mode (used with
non-Linux peers other than S/390 and zSeries operating systems)</para>
<para>· <command>1</command> for extended mode</para>
<para>· <command>2</command> for CTC-based tty (only supported on
Linux-to-Linux connections)</para>
<para>· <command>3</command> for compatibility mode with S/390
and zSeries operating systems</para>
</listitem>
<listitem>
<para><command>IUCV=<replaceable><userid></replaceable></command></para>
<para>Where <command><replaceable><userid></replaceable></command>
represents the ID of the guest machines you want to connect to. Note
that the ID must be written in capital letters. For example, an IUCV
connection to the VM TCP/IP service machine would be written
as:</para>
<para><command>IUCV=TCPIP</command></para>
</listitem>
</itemizedlist>
<para>The following parameters are optional:</para>
<itemizedlist>
<listitem>
<para><command>HOSTNAME=<replaceable><string></replaceable></command></para>
<para>where <command><replaceable><string></replaceable></command>
is the hostname of the newly-installed Linux guest.</para>
</listitem>
<listitem>
<para><command>NETTYPE=<replaceable><type></replaceable></command></para>
<para>where <command><replaceable><type></replaceable></command>
must be one of the following: <command>ctc</command>,
<command>escon</command>, <command>tr</command>,
<command>hsi</command>, <command>iucv</command>, or
<command>eth</command>.</para>
</listitem>
<listitem>
<para><command>IPADDR=<replaceable><IP></replaceable></command></para>
<para>where <command><replaceable><IP></replaceable></command> is
the IP address of the new Linux guest.</para>
</listitem>
<listitem>
<para><command>NETWORK=<replaceable><network></replaceable></command></para>
<para>where
<command><replaceable><network></replaceable></command> is the
address of your network.</para>
</listitem>
<listitem>
<para><command>NETMASK=<replaceable><netmask></replaceable></command></para>
<para>where
<command><replaceable><netmask></replaceable></command> is the
netmask.</para>
</listitem>
<listitem>
<para><command>BROADCAST=<replaceable><broadcast></replaceable></command></para>
<para>where
<command><replaceable><broadcast></replaceable></command> is the
broadcast address.</para>
</listitem>
<listitem>
<para><command>GATEWAY=<replaceable><gw></replaceable></command></para>
<para>where <command><replaceable><gw></replaceable></command> is
either the gateway-IP for your eth device or the IP address of the
ctc/escon/iucv point-to-point partner.</para>
</listitem>
<listitem>
<para><command>MTU=<replaceable><mtu></replaceable></command></para>
<para>where <command><replaceable><mtu></replaceable></command> is
the Maximum Transmission Unit (MTU) for this connection.</para>
</listitem>
<listitem>
<para><command>DNS=<replaceable><server1></replaceable>:<replaceable><server2></replaceable>:…:<replaceable><serverN></replaceable></command></para>
<para>where
<command><replaceable><server1></replaceable>:<replaceable><server2></replaceable>:…:<replaceable><serverN></replaceable></command>
is a list of DNS servers, separated by colons. For example:</para>
<para><command>DNS=10.0.0.1:10.0.0.2</command></para>
</listitem>
<listitem>
<para><command>SEARCHDNS=<replaceable><domain1></replaceable>:<replaceable><domain2></replaceable>:…:<replaceable><domainN></replaceable></command></para>
<para>where
<command><replaceable><domain1></replaceable>:<replaceable><domain2></replaceable>:…:<replaceable><domainN></replaceable></command>
is a list of the search domains, separated by colons. For
example:</para>
<para><command>SEARCHDNS=example.com:example.org</command></para>
</listitem>
</itemizedlist>
<para>The following parameter for installations using a qeth device is
optional:</para>
<itemizedlist>
<listitem>
<para><command>QETHPARM=</command></para>
<para>Use this option to specify additional parameters for your QETH
device (for CHANDEV) such as:</para>
<para><command>add_parms,0x10,{lo_devno,hi_devno},portname:<replaceable><port_name></replaceable></command></para>
</listitem>
</itemizedlist>
<para>The following parameter for kickstart installation is optional:</para>
<itemizedlist>
<listitem>
<para><command>RUNKS=<replaceable><value></replaceable></command></para>
<para>Where <command><replaceable><value></replaceable></command>
is <command>1</command> if you want to run the installation program in
non-interactive mode in the 3270 terminal, or <command>0</command>
otherwise.</para>
<para>NOTE: Make sure that your kickstart file contains all required
parameters before you use this option.</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="inst-notes">
<title>Installation-Related Notes</title>
<para>This section describes issues related to the &PROD; installation
program <application>Anaconda</application>.</para>
<itemizedlist>
<listitem>
<para>The sequence for processing CD-ROMs has changed for &PROD;
&PRODVER;. The first CD-ROM is required when booting the installation
program, and again after subsequent CD-ROMs have been
processed.</para>
</listitem>
<listitem>
<para>The &PROD; installation program has the ability to test the
integrity of the installation media. It works with the CD, hard
drive ISO, and NFS ISO installation methods. &RH; recommends that
you test all installation media before starting the installation
process, and before reporting any installation-related bugs (many of
the bugs reported are actually due to improperly-burned CDs). To use
this test, type <command>linux mediacheck</command> at the
<prompt>boot:</prompt> prompt.</para>
</listitem>
<listitem arch="s390;s390x">
<para>The Object-code-only (OCO) driver necessary to support the IBM
3590 Tape Drive on the IBM S/390(R) and IBM eServer zSeries(R)
architectures is available for download from IBM here:</para>
<para>http://www10.software.ibm.com/developerworks/opensource/linux390/special_oco_rh_2.4.shtml</para>
<para>NOTE: You must verify that the driver you download is the correct
one for the version of the kernel running on your system.</para>
</listitem>
<listitem arch="s390;s390x">
<para>A new storage option is available on the s390 and zSeries
architectures: a SCSI subsystem. To that end, generic SCSI support is
enabled and a driver (known as <command>zfcp</command>) is
supplied.</para>
<para>The generic SCSI subsystem on &PROD; &PRODVER; does not use the
REPORT LUNs command at this time; therefore use small LUN numbers for
virtual volumes. In addition, the following line must be supplied in
<filename>/etc/modules.conf</filename>:</para>
<para><command>options scsi_mod
max_scsi_luns=<replaceable><NNN></replaceable></command></para>
<para>(Where <command><replaceable><NNN></replaceable></command>
should be a number larger than the largest LUN number used.) NOTE:
Larger values slow the bootstrapping process somewhat.</para>
</listitem>
<listitem arch="i386">
<para>&PROD; &PRODVER; includes a new kernel known as the
<firstterm>hugemem</firstterm> kernel. This kernel supports a 4GB per
process user space (versus 3GB for the other kernels), and a 4GB
direct kernel space. Using this kernel allows &PROD; to run on systems
with up to 64GB of main memory. The hugemem kernel is required in
order to use all the memory in system configurations containing more
than 16GB of memory. The hugemem kernel can also benefit
configurations running with less memory (if running an application
that could benefit from the larger per process user space, for
example.)</para>
<para>To remind you of this issue, the &PROD; &PRODVER; kernel displays a
message at boot time if your system configuration contains more than
16GB of memory. After the system has booted, the following command
can be used to see if your system displayed the message:</para>
<para><command>dmesg | less</command></para>
<para>NOTE: To provide a 4GB address space for both kernel and user
space, the kernel must maintain two separate virtual memory address
mappings. This introduces overhead when transferring from user to
kernel space; for example, in the case of system calls and interrupts.
The impact of this overhead on overall performance is highly
application dependent.</para>
<para>Also note that, because some drivers were not originally written
to work well in large-memory environments, &RH; only supports a
validated subset of drivers when the hugemem kernel is used. Drivers
that have been validated by &RH; for use with the hugemem kernel are
contained in the <filename>kernel-hugemem</filename> package. Drivers
that have not been validated, but are still provided, are available in
the <filename>kernel-hugemem-unsupported</filename> RPM. To see the
list of drivers in these RPMs, use the following command:</para>
<para><command>rpm -qlp
<replaceable><kernel-rpm></replaceable></command></para>
<para>(Where <command><replaceable><
kernel-rpm></replaceable></command> is the complete filename of
the appropriate hugemem RPM. Note that these RPMs can be found on
CD-ROM #2, in the <filename>RedHat/RPMS/</filename>
directory.)</para>
<para>Should you decide that the hugemem kernel's additional overhead
and the subset of available drivers present no problem for your
hardware configuration and system environment, and you wish to use the
hugemem kernel, you must first install it. To install the hugemem
kernel, enter the following command while logged in as root:</para>
<para><command>rpm -ivh
<replaceable><kernel-rpm></replaceable></command></para>
<para>(Where
<command><replaceable><kernel-rpm></replaceable></command> is
the name of the hugemem kernel RPM file —
<filename>kernel-hugemem-2.4.21-3.EL.i686.rpm</filename>,
for example.)</para>
<para>After the installation is complete, reboot your system, making
sure to select the newly-installed hugemem kernel. After testing your
system for proper operation while running the hugemem kernel, you
should modify the <filename>/boot/grub/grub.conf</filename> file so
that the hugemem kernel is booted by default.</para>
</listitem>
<listitem arch="i386">
<para>&PROD; &PRODVER; can be installed on the IBM eServer <trademark
class="registered">xSeries</trademark> 440 and 445. However, the
installation process supports configurations containing no more than
one chassis, and no attached RXE-100 Remote Expansion Enclosures. If
your system configuration does not conform to these requirements, you
can remove any additional chassis and/or RXE-100s, and then perform
the installation. Once the installation is complete, the chassis
and/or RXE-100s can then be re-installed, and will operate normally
under &PROD;.</para>
</listitem>
<listitem arch="ppc">
<para>Support for some Input/Output Processors/Adapters (IOP/IOA)
present in some iSeries and pSeries systems require the use of the
IBMSIS driver. This driver can be found on the &PROD; &PRODVER;
Extras CD, and can be loaded as driver media when the &PROD;
installation process is started.</para>
<para>Loading the IBMSIS driver via CD-ROM using a non-IDE CD-ROM drive
(including the iSeries virtual CD-ROM drive) is possible by adding the
following command to the boot command line:</para>
<para><command>dd=cdrom</command></para>
<para>You will then be prompted if you have any driver media for
additional drivers after all drivers included on the CD-ROM are
loaded. Note that this is in addition to the other methods of using
driver media as described in the <citetitle>&PROD; &PRODVER;
Installation Guide for the IBM eServer iSeries and IBM eServer pSeries
Architectures</citetitle>.</para>
<para>After installation, IBMSIS users should install the
<filename>ibmsis</filename> and <filename>ibmsis-utils</filename>
packages from the &PROD; Extras CD.</para>
<para>After an upgrade to a new version of the kernel, the IBMSIS driver
must be rebuilt and installed. The <command>ibmsistool</command>
program (provided in the <filename>ibmsis</filename> package on the
&PROD; &PRODVER; Extras CD) largely automates this process. The
<filename>kernel-source</filename> package that corresponds to the new
kernel must be installed, as it provides the headers needed to build
IBMSIS. For example, after installing the 2.4.21-3.EL kernel and
corresponding <filename>kernel-source</filename> packages, the
following command would update the IBMSIS driver:
</para>
<para><command>/usr/sbin/ibmsistool -v 2.4.21-3.EL build
install</command></para>
</listitem>
<listitem>
<para>&PROD; &PRODVER; now includes support for <firstterm>Logical
Volume Management</firstterm> (LVM). LVM is a means of allocating disk
space into one or more logical volumes, which can then be used to
implement easily-resizable file systems.</para>
</listitem>
<listitem arch="i386">
<para>While most present-day computers are able to start the
installation process by booting directly from the first &PROD;
distribution CD, some hardware configurations require the use of a
boot diskette. If your hardware requires a boot diskette, you should
be aware of the following change.</para>
<para>&PROD; &PRODVER; uses a different boot diskette layout than
previous releases of &PROD;. There is now a single boot diskette
image file (<filename>bootdisk.img</filename>) that is used to boot
all systems requiring a boot diskette.</para>
<para>If you are performing anything other than an installation from an
IDE or USB device, you will be asked to insert a driver diskette
created from one of the following image files:</para>
<para>· <filename>drvnet.img</filename> — For network
installations</para>
<para>· <filename>drvblock.img</filename> — For SCSI
installations</para>
<para>· <filename>pcmciadd.img</filename> — For PCMCIA
installations</para>
<para>As with previous releases of &PROD;, these image files can be found
in the <filename>images/</filename> directory on the first installation
CD.</para>
</listitem>
<listitem arch="s390;s390x">
<para>Due to the page-oriented nature of the 3270-style console, output
to <filename>/dev/console</filename> can fill the screen. If the
screen is filled, the &PROD; environment stops operating until the
screen is cleared. The screen can be cleared using one of two
different methods:</para>
<para>· By issuing the keystrokes necessary to clear the screen
(For example,
<keycombo><keycap>Alt</keycap><keycap>C</keycap></keycombo> for the
<application>x3270</application> terminal emulator, and
<keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo> for the
<command>c3270</command> terminal emulator.)</para>
<para>· By waiting for the screen to be automatically cleared.
The default wait time is 60 seconds; however, this can be changed by
using the following command:</para>
<para><command>#cp term more
<replaceable><alarm-time></replaceable>
<replaceable><clear-time></replaceable></command></para>
<para>Where
<command><replaceable><alarm-time></replaceable></command>
represents the number of seconds between the time the screen fills
and the time the terminal alarm should be sounded, and
<command><replaceable><clear-time></replaceable></command> is
the number of seconds between the time the terminal alarm is sounded
and the screen is automatically cleared. Both the
<command><replaceable><alarm-time></replaceable></command> and
<command><replaceable><clear-time></replaceable></command>
parameters must be numbers between 0 and 255.</para>
<para>NOTE: This aspect of the 3270-style console is most likely to be
an issue whenever a large amount of output is sent to
<filename>/dev/console</filename>. Therefore, the console's screen is
most likely to fill at the following times:</para>
<para>· During the &PROD; installation process</para>
<para>· When &PROD; is booted</para>
<para>· <command>syslog</command> messages are sent to the
console</para>
</listitem>
<listitem arch="i386;ia64;x86_64;ppc">
<para>Text mode installations using a serial terminal work best when the
terminal supports UTF-8. Under UNIX and Linux, Kermit supports UTF-8.
For Windows, Kermit '95 works well. Non-UTF-8 capable terminals will
work as long as only English is used during installation. An enhanced
serial display can be used by passing "<command>utf8</command>" as a
boot-time option to the installation program. For example:</para>
<para><command>linux console=ttyS0 utf8</command></para>
</listitem>
<listitem>
<para>The firewall configuration screen in the &PROD; installation
program has been simplified. The previous
"<guilabel>High</guilabel>", "<guilabel>Medium</guilabel>", and
"<guilabel>No firewall</guilabel>" settings have been replaced by a
more straightforward on/off-style control. In addition, the default
firewall configuration is now stateful, making it more secure. The
new design also makes it possible for users of NIS authentication,
NFS, and DNS to deploy a firewall with no additional customization
required (although customization by specifying port and protocol is
still possible).</para>
<para>NOTE: This change also applies to the <application>Security Level
Configuration Tool</application>
(<command>redhat-config-securitylevel</command>).</para>
</listitem>
<listitem>
<para>Installation via VNC is now supported. To initiate a VNC-based
installation, pass <command>vnc</command> as a boot-time option. If
necessary, a password can be set by adding
"<command>vncpassword=<replaceable><password></replaceable></command>"
to the boot-time options. The VNC display will be
"<command><replaceable><host></replaceable>:1</command>", where
<command><replaceable><host></replaceable></command> is the
hostname or IP address of the system installing &PROD;.</para>
<para>It is also possible for the &PROD; installation program to
initiate a connection to a listening VNC client. This is done by
using the <command>vncconnect</command> boot-time option:</para>
<para><command>linux vnc
vncconnect=<replaceable><client></replaceable>[:<replaceable><port></replaceable>]</command></para>
<para>(Where
<command><replaceable><client></replaceable></command> is the
hostname or IP address of the system running the listening VNC client,
and <command><replaceable><port></replaceable></command> is an
optional port specification that may be specified if the VNC client is
not listening on port 5500, which the default port for this type of
connection). The following examples show the how the boot-time option
is specified for standard and non-standard ports:</para>
<para><command>linux vnc
vncconnect=pigdog.example.com</command></para>
<para><command>linux vnc
vncconnect=pigdog.example.com:27910</command></para>
<para>The system that is to run the listening VNC client must then
launch the appropriate software to run the VNC client in its listening
mode. For the VNC client supplied with &PROD; &PRODVER;, the
following command is sufficient:</para>
<para><command>vncviewer -listen</command></para>
<para>In addition, a new kickstart directive has been added to support
VNC-based installations:</para>
<para><command>vnc [--password
<replaceable><password></replaceable>] [--connect
<replaceable><host></replaceable>[:<replaceable><port></replaceable>]]</command></para>
<para>(Where <command>--password
<replaceable><password></replaceable></command> is an optional
parameter for specifying a VNC password, and <command>[--connect
<replaceable><host></replaceable>[:<replaceable><port></replaceable>]]</command>
is an optional parameter for specifying the host (and optionally,
port) of a system running a listening VNC client.</para>
<para>NOTE: If you specify any of the VNC-related boot-time options,
they will override the corresponding options present in the kickstart
file.</para>
<para arch="ppc">&PROD; &PRODVER; for the iSeries and pSeries
architectures includes support for installation using the VNC remote
display system, and support for accessing virtual consoles via telnet
for installation on iSeries. VNC and telnet clients for a variety of
platforms are available for download from:</para>
<para arch="ppc">http://www.ibm.com/servers/eserver/iseries/linux/products.html</para>
</listitem>
<listitem arch="i386">
<para>The XFree86 open source vmware video driver is provided as a
convenience to our customers and is not supported in any way by
&FORMAL-RHI; However, any problem reports with the XFree86 open source
vmware video driver received by &RH; will be forwarded to the
appropriate VMware staff, so that they can investigate. Bug fixes
that become available for this driver may be reviewed by &RH; for
potential inclusion in future errata and products as time
permits.</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="input-methods">
<title>Input Methods</title>
<para>This section contains general information related to the use of input
methods.</para>
<para>An input method allows users to enter non-Western characters into
common applications such as word-processing, email and instant messaging.
&PROD; comes with input method support for the following languages:</para>
<itemizedlist>
<listitem>
<para>Chinese (Simplified and Traditional)</para>
</listitem>
<listitem>
<para>Japanese</para>
</listitem>
<listitem>
<para>Korean</para>
</listitem>
</itemizedlist>
<para>The following entries describe the use of input methods for each of
these languages.</para>
<itemizedlist>
<listitem>
<para>Simplified Chinese</para>
<para>To enter Simplified Chinese characters, you use the miniChinput
input method. To activate the input method, press
<keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>.</para>
<para>The miniChinput input method supports the following
modules:</para>
<para>· intelligent pinyin input</para>
<para>· gbk pinyin input</para>
<para>· shuang pin input</para>
<para>· internal code (gb18030 code) input</para>
<para>The <filename>miniChinput</filename> package is installed by
default if Simplified Chinese language support is selected during
installation.</para>
</listitem>
<listitem>
<para>Traditional Chinese</para>
<para>To enter Traditional Chinese characters, you use the xcin input
method. To activate the input method, press
<keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>.
Pressing
<keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap></keycombo> or
<keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Num</keycap></keycombo>
allows you to change between input modules.</para>
<para>The xcin input method supports the following modules:</para>
<para>· CJ</para>
<para>· Simplex</para>
<para>· Phone</para>
<para>· CantonPing</para>
<para>· Bimsphone</para>
<para>· Bimspinyin</para>
<para>· Array30</para>
<para>· Cantonping (no intonation)</para>
<para>The <filename>xcin</filename> package is installed by default if
Traditional Chinese language support is selected during
installation.</para>
</listitem>
<listitem>
<para>Japanese</para>
<para>To enter Japanese characters, you use the Canna, FreeWnn or skk
input methods. To activate the input method, press
<keycombo><keycap>Shift</keycap><keycap>Space</keycap></keycombo>.</para>
<para>The following modules are supported:</para>
<para>· romaji</para>
<para>· kana (only Canna — depends on the configuration
file)</para>
<para>The <filename>Canna</filename>, <filename>FreeWnn</filename>, and
<filename>skkinput</filename> packages are installed by default if
Japanese language support is selected during installation.</para>
</listitem>
<listitem>
<para>Korean</para>
<para>To enter Korean characters, you use the ami input method. To
activate the input method, press
<keycombo><keycap>Shift</keycap><keycap>Space</keycap></keycombo>.</para>
<para>The <filename>ami</filename> package is installed by default if
Korean language support is selected during installation.</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="general-notes">
<title>General Notes</title>
<para>This section contains general notes relating to post-installation
issues.</para>
<itemizedlist>
<listitem arch="ia64">
<para>&PROD; &PRODVER; for the Itanium 2 Architecture contains the
<filename>fpswa.efi</filename> binary, which is an EFI (Extensible
Firmware Interface) driver invoked by the operating system's kernel
whenever the processor issues FPSWA (Floating-Point Software
Assistance) requests for floating-point operations that are not fully
implemented in hardware. The handler provides the result of the
operation in these cases. Presently, Itanium processors issue FPSWA
requests mainly when very small numbers (denormalized, or tiny
numbers) are consumed or produced by floating-point instructions. To
avoid the performance penalty caused by calls to the handler when tiny
numbers are produced, the flush-to-zero mode can be turned on, but at
the cost of a slightly less accurate computation.</para>
<para>FPSWA is licensed, patented and copyrighted protected material by
Intel or its supplier under the laws of the United states and other
countries and international treaty provisions. FPSWA is subject to the
applicable end user license agreement which can be accessed at
http://www.redhat.com/licenses/.</para>
</listitem>
<listitem>
<para>The Apache HTTP server has been updated to version 2.0. The
updated package replaces version 1.3 and has been renamed to
<filename>httpd</filename>.</para>
<para>· The <command>auth_ldap</command>,
<command>mod_put</command>, <command>mod_roaming</command>,
<command>mod_auth_any</command>, <command>mod_bandwidth</command>,
<command>mod_throttle</command>, and <command>mod_dav</command>
modules have been removed.</para>
<para>· WebDAV functionality is now included with the
<filename>httpd</filename> package.</para>
<para>NOTE: Some changes to existing configuration files are needed.
Third-party Apache modules may also require updating. Refer to the
migration guide at
<filename>/usr/share/doc/httpd-*/migration.html</filename> for more
details.</para>
</listitem>
<listitem arch="i386">
<para>&PROD; &PRODVER; supports booting over the network using the PXE
(Pre-Boot Execution Environment) protocol. As in previous releases it
is possible to configure &PROD; &PRODVER; as an installation server,
which makes kernels and image files available for the purpose of
starting network installations.</para>
<para>Also available in &PROD; &PRODVER; is support for diskless
environments. A diskless server (similar to an installation server)
makes kernels and image files available to diskless client systems.
After booting, the diskless client systems mount a root file system
via NFS, eliminating the need for locally-attached storage.</para>
<para>The <application>Network Booting Tool</application>
(<command>redhat-config-netboot</command>) is a graphical
configuration tool allows you to configure both environments.</para>
</listitem>
<listitem>
<para>The LPRng print spooler has been replaced by CUPS, and the
<application>Printer Configuration Tool</application>
(<command>redhat-config-printer</command>) is the recommended tool for
configuring it. It may be launched from the <guimenu>System
Settings</guimenu> menu, using the <guimenuitem>Printing</guimenuitem>
menu entry.</para>
</listitem>
<listitem>
<para>The <application>Security Level Configuration Tool</application>
(<command>redhat-config-securitylevel</command>) has been
simplified. The previous "<guilabel>High</guilabel>",
"<guilabel>Medium</guilabel>", and "<guilabel>No
firewall</guilabel>" settings have been replaced by a more
straightforward on/off-style control. In addition, the default
firewall configuration is now stateful, making it more secure. The
new design also makes it possible for users of NIS authentication,
NFS, and DNS to deploy a firewall with no additional customization
required (although customization by specifying port and protocol is
still possible).</para>
<para>NOTE: This change also applies to the &PROD; installation
program.</para>
</listitem>
<listitem>
<para><application>GNOME Print Manager</application>, a simple graphical
print queue management tool, is now included. It may be launched from
the <guimenu>System Tools</guimenu> menu, using the <guimenuitem>Print
Manager</guimenuitem> menu entry. In addition, when a print job is in
the queue, an icon will appear in the panel's system notification
area.</para>
</listitem>
<listitem arch="i386;ia64;x86_64;s390x;ppc">
<para>&PROD; &PRODVER; includes the setarch utility. Setarch makes it
possible to change the output produced by the <command>uname</command>
command. This is useful for a number of reasons, such as running
32-bit applications (those written to expect a particular value from
<command>uname -m</command>) in 64-bit environments.</para>
<para>The format for the setarch command is:</para>
<para><command>setarch <replaceable><arch></replaceable>
<replaceable><command></replaceable></command></para>
<para>(Where <command><replaceable><arch></replaceable></command>
represents the desired architecture string (such as
<command>i386</command>), and
<command><replaceable><command></replaceable></command>
represents the command to be run while the architecture has been
modified.) Note that
<command><replaceable><command></replaceable></command> can be
omitted, in which case <command>/bin/sh</command> is run.</para>
<para>In addition, some applications (such as older versions of Java)
are written to assume a 3GB virtual address space; when run on systems
with larger virtual address spaces (such as 64-bit AMD64-based
systems, or 32-bit systems running the hugemem kernel) such
applications can malfunction. The setarch utility makes it possible
to emulate a 3GB virtual address space, allowing such applications to
run properly:</para>
<para><command>setarch -3 java</command></para>
</listitem>
<listitem arch="ia64">
<para>Accelerated 3D rendering with DRI has been disabled in &PROD;
&PRODVER; for the IA64 architecture. On this architecture,the agpgart
kernel driver does not function properly; since the DRI subsystem
depends on this driver, no 3D acceleration is possible. Note,
however, that this does not affect unaccelerated 3D rendering or
third-party drivers that provide their own agpgart
implementation.</para>
</listitem>
<listitem>
<para>&PROD; &PRODVER; includes the Native POSIX Thread Library (NPTL),
a new implementation of POSIX threads for Linux. This library provides
performance improvements and increased scalability.</para>
<para>This thread library is designed to be binary compatible with the
old LinuxThreads implementation; however, applications that rely on
the places where the LinuxThreads implementation deviates from the
POSIX standard will need to be fixed. Notable differences include:</para>
<para>· Signal handling has changed from per-thread signal
handling to POSIX process signal handling.</para>
<para>· <command>getpid()</command> returns the same value in all
threads.</para>
<para>· Thread handlers registered with
<command>pthread_atfork</command> are not run if
<command>vfork()</command> is used.</para>
<para>· No manager thread.</para>
<para arch="i386">Applications that are known to have problems using
NPTL include:</para>
<para arch="i386">- Sun JRE prior to version 1.4.1</para>
<para arch="i386">- IBM JRE</para>
<para>If an application does not work properly with NPTL, it can be run
using the old LinuxThreads implementation by setting the following
environment variable:</para>
<para><envar>LD_ASSUME_KERNEL=<replaceable><kernel-version></replaceable></envar></para>
<para>The following versions are available:</para>
<para>· 2.4.19 — Linuxthreads with floating stacks</para>
<para arch="i386">· 2.2.5 — Linuxthreads without floating
stacks</para>
<para>Note that software using <command>errno</command>,
<command>h_errno</command>, and <command>_res</command> must
<command>#include</command> the appropriate header file
(<filename>errno.h</filename>, <filename>netdb.h</filename>, and
<filename>resolv.h</filename> respectively) before they are used.
However, <envar>LD_ASSUME_KERNEL=2.4.19</envar> can be used as a
workaround until the software can be fixed.</para>
</listitem>
<listitem>
<para>Multi-threaded C++ programs using thread cancellation might need
to be forced to use the LinuxThreads library using the
<envar>LD_ASSUME_KERNEL=2.4.19</envar> environment variable setting.
Otherwise, the program will terminate abnormally if the cancellation
is acted on (since the generated exception is not caught).</para>
<para>Newly-written C++ code that uses functions from the C runtime
environment might have to be adjusted to take the cancellation into
account. This can be done by one of the following methods:</para>
<para>· Not marking the C++ function with
<command>throw()</command> (so that callers are aware that an
exception might be thrown) and by compiling the code with exceptions.
This is the default compilation option; users should not specify
<command>-fno-exceptions</command> when compiling.</para>
<para>· Disabling cancellation completely before entering the
functions that call the cancel-able C runtime functions. This can be
done with the following call:</para>
<para><command>pthread_setcancelstate (PTHREAD_CANCEL_DISABLE,
&oldstate)</command></para>
<para>After the C functions are called cancellation can be enabled again
with the following call:</para>
<para><command>pthread_setcancelstate (oldstate, NULL)</command></para>
<para>NOTE: At this point the cancellations are acted upon and therefore
the function calling pthread_setcancelstate() must be compiled with
exceptions enabled and must be marked as throwing exceptions.</para>
</listitem>
<listitem>
<para>A new system message has been added to &PROD; &PRODVER;:</para>
<para><computeroutput>application bug:
<replaceable><app-name></replaceable>(<replaceable><app-pid></replaceable>)
has SIGCHLD set to SIG_IGN but calls wait(). (see the NOTES section
of 'man 2 wait'). Workaround activated.</computeroutput></para>
<para>This message (which is displayed on the system console and/or in
the system log files) indicates that the application is not completely
standards compliant with respect to its handling of child processes.
If you notice this message, you should alert the application's
developers.</para>
</listitem>
<listitem>
<para>&PROD; &PRODVER; includes the capability of producing Position
Independent Executables (PIE) for C, C++, and Java. This feature is
enabled with the <command>-fpie</command> and <command>-fPIE</command>
GCC options to compile, which are similar in usage to the
<command>-fpic</command> and <command>-fPIC</command> options,
respectively, and at link time with the <command>-pie</command>
option.</para>
</listitem>
<listitem>
<para>The <command>fileutils</command>, <command>textutils</command>,
<command>sh-utils</command>, and <command>stat</command> packages have
been replaced by the newer <command>coreutils</command> package.</para>
</listitem>
<listitem>
<para>The RPMs containing the <application>Network Administration
Tool</application> (<command>redhat-config-network</command>) have
changed names and functions. The
<filename>redhat-config-network</filename> RPM contains the tool's
graphical user interface, while
<filename>redhat-config-network-tui</filename> contains the tool
itself (along with its text-based user interface).</para>
</listitem>
<listitem>
<para>Support for XHTML1 — the reformulation of HTML in XML
— has been improved. This has been done by adding the
<command>xhtml1-dtd</command> package, installing the DTDs in the
system catalog, and adding native support in the
<command>libxml2</command> and <command>xsltproc</command>
tools.</para>
</listitem>
<listitem>
<para>The XML toolkit have been extended to support Relax-NG validation,
and streaming of large files.</para>
</listitem>
<listitem>
<para>The OProfile system-wide profiler has been added to &PROD;
&PRODVER;. OProfile is a programmer's tool for analyzing system
performance, using special hardware built into many modern computers.
Documentation for OProfile exists in the <command>oprofile</command>
package; after installing &PROD; &PRODVER;, issue the command
<command>rpm -qd oprofile</command> to obtain a listing of the
available documentation. Visit the OProfile website at
http://oprofile.sourceforge.net for more details.</para>
<para>NOTE: The kernel support for OProfile in &PROD; &PRODVER; is based
on the backported code from the 2.5 development kernel. Therefore, if
you refer to the OProfile documentation, keep in mind that features
listed as being 2.5-specific actually apply to the &PROD; kernel, even
though the kernel version is 2.4. Likewise, this means that features
listed as being specific to the 2.4 kernel do <emphasis>not</emphasis>
apply to the &PROD; kernel.</para>
</listitem>
<listitem>
<para>At the present time, the X Window System makes use of two font
subsystems, each with different characteristics:</para>
<para>· The original (15+ year old) subsystem is referred to as
the "core X font subsystem". Fonts rendered by this subsystem are not
anti-aliased, are handled by the X server, and have names like:</para>
<para>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</para>
<para>The newer font subsystem is known as "fontconfig", and allows
applications direct access to the font files. Fontconfig is often
used along with the "Xft" library, which allows applications to render
fontconfig fonts to the screen with antialiasing. Fontconfig uses
more human-friendly names like:</para>
<para>Luxi Sans-10</para>
<para>Over time, fontconfig/Xft will replace the core X font subsystem.
At the present time, applications using the Qt 3 or GTK 2 toolkits
(which would include KDE and GNOME applications) use the fontconfig
and Xft font subsystem; most everything else uses the core X
fonts.</para>
<para>In the future, &RH; may support only fontconfig/Xft in place of
the XFS font server as the default local font access method.</para>
<para>NOTE: One exception to the font subsystem usage outlined above is
OpenOffice.org, which uses its own font rendering technology.</para>
<para>If you wish to add new fonts to your &PROD; &PRODVER; system, you
must be aware that the steps necessary depend on which font subsystem
is to use the new fonts. For the core X font subsystem, you
must:</para>
<para>1. Create the <filename>/usr/share/fonts/local/</filename>
directory (if it does not already exist):</para>
<para><command>mkdir /usr/share/fonts/local/</command></para>
<para>2. Copy the new font file into
<filename>/usr/share/fonts/local/</filename></para>
<para>3. Update the font information by issuing the following commands
(note that, due to formatting restrictions, the following commands may
appear on more than one line; in use, each commands should be entered
on a single line):</para>
<para><command>ttmkfdir -d /usr/share/fonts/local/ -o
/usr/share/fonts/local/fonts.scale</command></para>
<para><command>mkfontdir /usr/share/fonts/local/</command></para>
<para>4. If you had to create
<filename>/usr/share/fonts/local/</filename>, you must then add it to
the X font server (xfs) path:</para>
<para><command>chkfontpath --add
/usr/share/fonts/local/</command></para>
<para>Adding new fonts to the fontconfig font subsystem is more
straightforward; the new font file only needs to be copied into the
<filename>/usr/share/fonts/</filename> directory (individual users can
modify their personal font configuration by copying the font file into
the <filename>~/.fonts/</filename> directory).</para>
<para>After the new font has been copied, use
<command>fc-cache</command> to update the font information cache:</para>
<para><command>fc-cache
<replaceable><directory></replaceable></command></para>
<para>(Where
<command><replaceable><directory></replaceable></command> would
be either the <filename>/usr/share/fonts/</filename> or
<filename>~/.fonts/</filename> directories.)</para>
<para>Individual users may also install fonts graphically, by browsing
<command>fonts:///</command> in <application>Nautilus</application>,
and dragging the new font files there.</para>
<para>NOTE: If the font filename ends with "<filename>.gz</filename>",
it has been compressed with <command>gzip</command>, and must be
decompressed (with the <command>gunzip</command> command) before the
fontconfig font subsystem can use the font.</para>
</listitem>
<listitem>
<para>Due to the transition to the new font system based on
fontconfig/Xft, GTK+ 1.2 applications are not affected by any changes
made via the <guilabel>Font Preferences</guilabel> dialog. For these
applications, a font can be configured by adding the following lines
to the file <filename>~/.gtkrc.mine</filename>:</para>
<para><command>style "user-font" {</command></para>
<para><command>fontset =
"<replaceable><font-specification></replaceable>"</command></para>
<para><command>}</command></para>
<para><computeroutput> </computeroutput></para>
<para><computeroutput>widget_class "*" style "user-font"</computeroutput></para>
<para>(Where
<command><replaceable><font-specification></replaceable></command>
represents a font specification in the style used by traditional X
applications, such as
"<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>".)</para>
</listitem>
<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>
<listitem>
<para>The default FTP server in &PROD; &PRODVER; is now
<command>vsftpd</command>, and runs as a SysV service.</para>
</listitem>
<listitem>
<para>Change to <command>fdisk</command>'s interpretation of partition
size multipliers</para>
<para>The <command>fdisk</command> command now has a different
interpretation of the size multipliers that may be used when creating
new disk partitions. The size suffixes <command>K</command>,
<command>M</command>, and <command>G</command> now refer to multiples
of thousands, millions, and billions of bytes, respectively. This is
more consistent with the disk size specifications provided by disk
drive manufacturers.</para>
<para>Therefore, if a user wants to create a 512MB partition, the size
value specified with an "M" suffix would be 512*1024*1024
(536,870,912), rounded up to a multiple of a million (537,000,000),
and then divided by a million (537), resulting in a size specification
of <command>+537M</command>.</para>
</listitem>
<listitem>
<para>While compatibility for executables and dynamic shared objects
(DSOs, also known as shared libraries) created on earlier &RHL; and
&PROD; is supported, the same does not apply to object
(<filename>.o</filename>) files. Object files created on earlier
versions can be used on &PROD; &PRODVER; to create new executables or
DSOs only if they were built without including any system header
files.</para>
<para>Otherwise, the only way to use these files is to link the object
files to the compatibility version of glibc (part of the
<filename>compat-glibc</filename> package). Any newly-generated
object file must use the headers from the compatibility package. For
example, to compile object files, add the following to the beginning
of the compiler command line:</para>
<para><command>-I/usr/lib/i386-redhat-linux7/include</command></para>
<para>To link the resulting executable or DSO add the following to the
command line:</para>
<para><command>-L/usr/lib/i386-redhat-linux7/lib</command></para>
<para>Any mixture of old object files and those compiled against the
current system headers can have negative results. Linking old object
files with the regular system libraries may result in completely
unusable executables or executables with subtle bugs (such as memory
corruption).</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="kernel-notes">
<title>Kernel Notes</title>
<para>This section contains notes relating to the &PROD; &PRODVER;
kernel.</para>
<itemizedlist>
<listitem>
<para>The &PROD; &PRODVER; kernel makes use of a new kernel packaging
technique. Due to the almost limitless variety of available hardware,
it is not possible for &RH; to fully support all hardware components.
Therefore, while kernel modules for fully-supported hardware remain in
the standard <filename>kernel</filename> packages, a series of new
<firstterm>unsupported</firstterm> kernel packages are included with
&PROD; &PRODVER;.</para>
<para>For each kernel package shipped there is a corresponding
unsupported kernel package. For example, the unsupported kernel
package for
<filename>kernel-smp-2.4.21-3.EL.i686.rpm</filename>
is
<filename>kernel-smp-unsupported-2.4.21-3.EL.i686.rpm</filename>.</para>
<para>NOTE: The unsupported kernel packages are not installed by the
&PROD; installation program; therefore, in order to use unsupported
kernel modules, you must manually install the unsupported kernel
package corresponding to the kernel your system uses.</para>
<para>After installing the appropriate unsupported kernel package, you
must use the following command to update the module dependency tree
and your initrd:</para>
<para><command>/sbin/new-kernel-pkg --mkinitrd --depmod --install
<replaceable><kernel-version></replaceable></command></para>
<para>(Where
<command><replaceable><kernel-version></replaceable></command>
represents the version of the installed kernel.)</para>
<para>Drivers contained within the unsupported kernel packages are
provided on a best-effort basis. This means that updates and upstream
fixes may or may not be incorporated over time, and are not covered by
the same support expectations as the fully supported drivers. Custom
support arrangements covering drivers in the unsupported package may
be worked out with Red Hat in some situations.</para>
</listitem>
<listitem>
<para>The &PROD; &PRODVER; kernel includes more accurate process timing
functionality. This new process timing mode uses timestamps to
provide more accurate timing of idle and process times. When enabled,
this information is available via the usual monitoring tools (such as
<command>top</command>, <command>vmstat</command>, and
<command>procinfo</command>), and the <command>getrusage</command>
system call.</para>
<para>To enable timestamp-based process timing, you must boot your
system using the following boot-time option:</para>
<para><command>process_timing=<replaceable><value></replaceable></command></para>
<para>Where <command><replaceable><value></replaceable></command>
can be one or more of the following, with multiple values separated by
commas:</para>
<para>· <command>irq</command> — Use timestamps to account
for IRQ interrupts</para>
<para>· <command>softirq</command> — Use timestamps to
account for softirq time in the kernel</para>
<para>· <command>process</command> — Allow processes to
enable timestamp-based process timing on themselves (It is then
disabled for all processes by default)</para>
<para>· <command>all_process</command> — Force
timestamp-based process timing on all processes (including the idle
tasks)</para>
<para>· <command>everything</command> — Same as specifying
<command>irq,softirq,all_process</command></para>
<para>If the system is booted with the <command>process</command>
option, no processes initially have timestamp-based process timing
enabled by default. However, processes can use the
<command>prctl()</command> system call to both determine and modify
their process timing mode. The system call to determine the process
timing mode is:</para>
<para><command>mode = prctl(PR_GET_TIMING, 0, 0, 0, 0);</command></para>
<para>The system call to set the process timing mode is:</para>
<para><command>status = prctl(PR_SET_TIMING,
<replaceable><mode></replaceable>, 0, 0, 0)</command></para>
<para>(Where <command><replaceable><mode></replaceable></command>
is <command>PR_TIMING_STATISTICAL</command> for enabling the
traditional process timing mode, or
<command>PR_TIMING_TIMESTAMP</command> for enabling timestamp-based
process timing mode .) Note that enabling one process timing mode
automatically disables the other.</para>
<para>NOTE: The <command>prctl()</command> system call can only be used
on systems booted with the <command>process</command> value.
Otherwise, the system call will return <command>-EINVAL</command>.
This includes attempts to disable timestamp-based process timing on
systems booted with the <command>all_process</command> option.</para>
<para>A child process's timing mode is inherited from its parent;
however, the child can use the <command>prctl()</command> system call
to modify its own process timing mode (subject to the conditions
outlined in the previous note).</para>
</listitem>
<listitem>
<para>The BusLogic driver (for certain Mylex SCSI host bus adapters) is
provided in the standard kernel packages, but it is only supported
when the kernel is a guest operating system within
<trademark>VMWare</trademark> virtual machine software. This is
because VMWare presents an emulated SCSI adapter to the BusLogic
driver, and this environment has been thoroughly tested and supported
by VMWare, Inc. The BusLogic driver is not supported on physical SCSI
host adapters because this driver has not been maintained in the
official Linux kernel for several years, and has not received
extensive testing in the &RHEL; kernel.</para>
</listitem>
<listitem>
<para>The qla1280 driver (for the Qlogic ISP1x80/1x160 SCSI adapters)
has not been maintained in the official Linux kernel for many years.
As a result, although this driver works correctly with the Intel x86
architecture, it does not work correctly with other architectures.
Therefore, &RH; only supports the qla1280 driver on Intel x86
platforms.</para>
</listitem>
<listitem arch="ia64;s390;s390x;x86_64;ppc">
<para>The netdump facility is currently disabled. The
<filename>netdump</filename> package is included so that, if the
netdump facility is enabled in a future kernel update, netdump
functionality will be available after the netdump-capable kernel is
installed.</para>
</listitem>
<listitem arch="i386">
<para>Systems based on the Intel I865/I875 chipsets and utilizing these
chipsets' ICH5 integrated AC97 audio functionality may experience a
failure to produce any sound when running &PROD; &PRODVER;.</para>
<para>The ICH5 integrated AC97 audio subsystem can be identified by
reviewing the output from the following command:</para>
<para><command>/sbin/lspci -n</command></para>
<para>The PCI vendor:device code for the ICH5 AC97 audio is
8086:24d5.</para>
</listitem>
<listitem arch="i386">
<para>Systems based on the Intel I865/I875 chipsets and utilizing these
chipsets' ICH5 Serial ATA (SATA) functionality should configure the
BIOS settings for their SATA devices to "enhanced" or "native" mode.
"Legacy" or "combined" mode SATA is supported, but discouraged.</para>
<para>NOTE: Not all BIOS implementations offer the ability to change
these settings.</para>
</listitem>
<listitem>
<para>New kernel support has been added to provide IPv6 capabilities.
This support is consistent with the upstream 2.6-based implementation
as of 2.6.0-test3.</para>
<para>Note that &RH; will not be implementing additional IPv6 features
(such as any of the draft standards for Mobile IP) for this release of
&PROD;; our goal is to focus exclusively on bugs in existing
features.</para>
</listitem>
<listitem>
<para>EA (Extended Attributes) and ACL (Access Control Lists)
functionality is now available for ext3 file systems. In
addition, ACL functionality is available for NFS.</para>
<para>&PROD; &PRODVER; contains a kernel providing EA and ACL support
for the ext3 file system. Protocol extensions were also added to NFS
to support ACL-related operations for NFS-exported file
systems.</para>
<para>To enable ACLs on a locally-mounted file system, the file system
must be mounted with the <command>-o acl</command> mount option. By
default, the NFS server makes use of ACLs if the underlying file
system supports them. To disable this feature, you must specify the
<command>no_acl</command> export option.</para>
<para>EAs are used intrinsically for ACL support. To use EAs
separately, the file system must be mounted with the <command>-o
user_xattr</command> mount option.</para>
<para>The support for this comes in several packages:</para>
<para>· kernel — Provides support for storing EAs and ACLs
on disk for ext3 file systems, as well the system calls to manipulate
EAs and ACLs. Finally, the kernel package provides the mechanisms to
enforce ACLs on file access.</para>
<para>· e2fsprogs — Includes knowledge of the new on-disk
extended attribute formats so that <command>fsck</command> can check
file systems using the new feature.</para>
<para>· attr, libattr — Provides access to extended
attributes attached to files.</para>
<para>· acl, libacl — Provides tools to set, modify, and
query the ACLs set on files.</para>
<para>· libattr-devel, libacl-devel — Libraries and include
files to build programs using the acl and attr libraries.</para>
<para>· star — An archiving tool which can create and
unpack both <command>tar</command> and <command>pax</command> format
archives, and which can backup and restore EAs and ACLs.</para>
<para>NOTE: The options available for <command>star</command> are not
completely equivalent with those available for <command>tar</command>;
therefore, make sure you review the <command>star</command> man
page.</para>
<para>· samba — Samba can export ACL functionality in this
release. Refer to the samba documentation for information on how to
enable this in your configuration.</para>
<para>In addition, the <command>coreutils</command> package has been
updated so that the <command>cp</command> and <command>mv</command>
commands copy the ACLs and EAs associated with a file.</para>
<para>For more information on setting and reading ACLs, refer to the
<command>setfacl</command> and <command>getfacl</command> man pages.
General information about ACLs can be found in the
<command>acl</command> man page.</para>
<para>NOTE: The normal <command>tar</command> and
<command>dump</command> commands will <emphasis>not</emphasis> backup
ACLs and EAs.</para>
<para>Compatibility with older systems:</para>
<para>Any ext3 file system that has not had any ACLs or EAs set on it
will work unchanged on older kernels, and can be checked using older
e2fsprogs utilities.</para>
<para>Once an EA or an ACL has been set on any file on a given file
system, that file system will acquire the <command>ext_attr</command>
attribute. This attribute can be observed by using the following
command:</para>
<para><command>tune2fs -l
<replaceable><filesystemdevice></replaceable></command></para>
<para>A file system that has acquired the <command>ext_attr</command>
attribute can be mounted with older kernels, but obviously those
kernels are incapable of enforcing any ACLs that have been set.</para>
<para>NOTE: Older versions of the file system checking program
<command>e2fsck</command> refuse to check any file system with the
<command>ext_attr</command> attribute. This corresponds to versions
of the <command>e2fsprogs</command> package prior to 1.22.</para>
</listitem>
<listitem>
<para>The &PROD; &PRODVER; kernel now includes support for NFS over TCP.
To use NFS over TCP, you must include the "<command>-o tcp</command>"
option to <command>mount</command> when mounting the NFS-exported file
system on the client system.</para>
<para>NOTE: The default transport protocol for NFS remains UDP. Use the
<command>mount</command> command with the "<command>-o tcp</command>"
option to mount an NFS-exported file system using TCP; otherwise, UDP
will be used by default.</para>
</listitem>
<listitem>
<para>In this kernel, the following command has been added to scan for
new devices on all attached SCSI host adapters:</para>
<para><command>echo "scsi scan-new-devices" >
/proc/scsi/scsi</command></para>
<para>This is currently a non-standard addition. In future kernels a
different parameter may be used to provide the same capability, or the
semantics of the same parameter
(<computeroutput>scan-new-devices</computeroutput>) may change, as
&RH; tracks the official Linux kernel in this area.</para>
</listitem>
<listitem arch="ppc">
<para>Logical Partitions on iSeries platforms that have been configured
to use more than one processor (either directly or from a shared pool)
may wish to share interrupt processing across all processors. Doing
so may improve performance for some workloads. By default, &PROD; will
only service interrupts on one processor in the LPAR. To change this
behavior, the following boot-time option must be entered:</para>
<para><command>spread_lpevents=<replaceable><N></replaceable></command></para>
<para>Where <command><replaceable><N></replaceable></command>
represents the number of processors in the LPAR that should process
interrupts. This number should be less than or equal to
either:</para>
<para>· The number of virtual processors (if a shared processor
pool is being used)</para>
<para>· The number of direct processors assigned to the LPAR</para>
</listitem>
<listitem>
<para>Change in permission semantics for user-mode memory locking</para>
<para>&PROD; &PRODVER; now allows non-root processes to use user-mode
memory locking system calls within the bounds of their
<command>RLIMIT_MEMLOCK</command> resource limit. The default limit
is one physical page per process. Limits can be reassigned by the
system administrator on a per user-id, per group-id, or system-wide
basis via the <filename>/etc/security/limits.conf</filename> file.
Root processes are no longer constrained by this resource
limit.</para>
<para>The system calls affected by this change in semantics are
<command>mlock(2)</command>, <command>munlock(2)</command>,
<command>mlockall(2)</command>, <command>munlockall(2)</command>, and
<command>shmctl(2)</command>.</para>
</listitem>
</itemizedlist>
</sect1>
<ackno>(
<emphasis arch="i386">x86</emphasis>
<emphasis arch="ia64">ia64</emphasis>
<emphasis arch="s390">s390</emphasis>
<emphasis arch="s390x">s390x</emphasis>
<emphasis arch="x86_64">amd64</emphasis>
<emphasis arch="ppc">ppc</emphasis>
)</ackno>
</article>
--- NEW FILE announcement-release.txt ---
# This file collects notes throughout the release that are
# used for the announcement and/or the splash.xml.
- newer/better/faster/more
- OpenOffice 2.0 pre
- GNOME 2.10
featuring Clearlooks
- KDE 3.4
- Eclipse & the java stack, in all its huge glory
- Extras by default at release time
- PPC now included
- OO.org 2.0
- Evince first release
- Newer, better GFS fun
- Virtualization available with built-in Xen
- GCC 4.0
- 80 new daemons covered by SELinux (up from a dozen)
Just part of Gnome 2.10, but since it's such a visible change, maybe
mention the new default theme.
--- NEW FILE daemons.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.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE desktop.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE development-tools.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 eula.py ---
from gtk import *
import string
import gtk
import gobject
import sys
import functions
import rhpl.iconv
import os
##
## I18N
##
import gettext
gettext.bindtextdomain ("firstboot", "/usr/share/locale")
gettext.textdomain ("firstboot")
_=gettext.gettext
class childWindow:
#You must specify a runPriority for the order in which you wish your module to run
runPriority = 15
moduleName = (_("License Agreement"))
def launch(self, doDebug = None):
self.doDebug = doDebug
if self.doDebug:
print "initializing eula module"
self.vbox = gtk.VBox()
self.vbox.set_size_request(400, 200)
msg = (_("License Agreement"))
title_pix = functions.imageFromFile("workstation.png")
internalVBox = gtk.VBox()
internalVBox.set_border_width(10)
internalVBox.set_spacing(5)
textBuffer = gtk.TextBuffer()
textView = gtk.TextView()
textView.set_editable(gtk.FALSE)
textSW = gtk.ScrolledWindow()
textSW.set_shadow_type(gtk.SHADOW_IN)
textSW.set_policy(gtk.POLICY_AUTOMATIC, gtk.POLICY_AUTOMATIC)
textSW.add(textView)
lang = os.environ["LANG"]
if len(string.split(lang, ".")) > 1:
lang = string.split(lang, ".")[0]
path = "/usr/share/eula/eula.%s" % lang
if not os.access(path, os.R_OK):
#Try to open the translated eula
lines = open("/usr/share/eula/eula.en_US").readlines()
else:
#If we don't have a translation for this locale, just open the English one
lines = open(path).readlines()
iter = textBuffer.get_iter_at_offset(0)
for line in lines:
textBuffer.insert(iter, line)
textView.set_buffer(textBuffer)
self.okButton = gtk.RadioButton(None, (_("_Yes, I agree to the License Agreement")))
self.noButton = gtk.RadioButton(self.okButton, (_("N_o, I do not agree")))
self.noButton.set_active(gtk.TRUE)
internalVBox.pack_start(textSW, gtk.TRUE)
internalVBox.pack_start(self.okButton, gtk.FALSE)
internalVBox.pack_start(self.noButton, gtk.FALSE)
self.vbox.pack_start(internalVBox, gtk.TRUE, 5)
return self.vbox, title_pix, msg
def apply(self, notebook):
if self.okButton.get_active() == gtk.TRUE:
return 0
else:
dlg = gtk.MessageDialog(None, 0, gtk.MESSAGE_QUESTION, gtk.BUTTONS_NONE,
(_("Do you want to reread or reconsider the Licence Agreement? "
"If not, please shut down the computer and remove this "
"product from your system. ")))
dlg.set_position(gtk.WIN_POS_CENTER)
dlg.set_modal(gtk.TRUE)
continueButton = dlg.add_button(_("_Reread license"), 0)
shutdownButton = dlg.add_button(_("_Shut down"), 1)
continueButton.grab_focus()
rc = dlg.run()
dlg.destroy()
if rc == 0:
return None
elif rc == 1:
if self.doDebug:
print "shut down system"
os.system("/sbin/halt")
return None
--- NEW FILE eula.txt ---
LICENSE AGREEMENT
FEDORA(TM) CORE 3
This agreement governs the download, installation or use of the
Software (as defined below) and any updates to the Software,
regardless of the delivery mechanism. The Software is a collective
work under U.S. Copyright Law. Subject to the following terms, Fedora
Project grants to the user ("User") a license to this collective work
pursuant to the GNU General Public License. By downloading,
installing or using the Software, User agrees to the terms of this
agreement.
1. THE SOFTWARE. Fedora Core (the "Software") is a modular Linux
operating system consisting of hundreds of software components.
The end user license agreement for each component is located in
the component's source code. With the exception of certain image
files containing the Fedora trademark identified in Section 2
below, the license terms for the components permit User to copy,
modify, and redistribute the component, in both source code and
binary code forms. This agreement does not limit User's rights
under, or grant User rights that supersede, the license terms of
any particular component.
2. INTELLECTUAL PROPERTY RIGHTS. The Software and each of its
components, including the source code, documentation, appearance,
structure and organization are copyrighted by Fedora Project and
others and are protected under copyright and other laws. Title to
the Software and any component, or to any copy, modification, or
merged portion shall remain with the aforementioned, subject to
the applicable license. The "Fedora" trademark is a trademark of
Red Hat, Inc. ("Red Hat") in the U.S. and other countries and is
used by permission. This agreement permits User to distribute
unmodified copies of Software using the Fedora trademark on the
condition that User follows Red Hat's trademark guidelines located
at http://fedora.redhat.com/legal. User must abide by these
trademark guidelines when distributing the Software, regardless of
whether the Software has been modified. If User modifies the
Software, then User must replace all images containing the
"Fedora" trademark. Those images are found in the anaconda-images
and the fedora-logos packages. Merely deleting these files may
corrupt the Software.
3. LIMITED WARRANTY. Except as specifically stated in this agreement
or a license for a particular component, TO THE MAXIMUM EXTENT
PERMITTED UNDER APPLICABLE LAW, THE SOFTWARE AND THE COMPONENTS
ARE PROVIDED AND LICENSED "AS IS" WITHOUT WARRANTY OF ANY KIND,
EXPRESSED OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF
MERCHANTABILITY, NON-INFRINGEMENT OR FITNESS FOR A PARTICULAR
PURPOSE. Neither the Fedora Project nor Red Hat warrants that the
functions contained in the Software will meet User's requirements
or that the operation of the Software will be entirely error free
or appear precisely as described in the accompanying
documentation. USE OF THE SOFTWARE IS AT USER'S OWN RISK.
4. LIMITATION OF REMEDIES AND LIABILITY. TO THE MAXIMUM EXTENT
PERMITTED BY APPLICABLE LAW, FEDORA PROJECT AND RED HAT WILL NOT
BE LIABLE TO USER FOR ANY DAMAGES, INCLUDING INCIDENTAL OR
CONSEQUENTIAL DAMAGES, LOST PROFITS OR LOST SAVINGS ARISING OUT OF
THE USE OR INABILITY TO USE THE SOFTWARE, EVEN IF FEDORA PROJECT
OR RED HAT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
5. EXPORT CONTROL. As required by U.S. law, User represents and
warrants that it: (a) understands that the Software is subject to
export controls under the U.S. Commerce Department's Export
Administration Regulations ("EAR"); (b) is not located in a
prohibited destination country under the EAR or U.S. sanctions
regulations (currently Cuba, Iran, Iraq, Libya, North Korea, Sudan
and Syria); (c) will not export, re-export, or transfer the
Software to any prohibited destination, entity, or individual
without the necessary export license(s) or authorizations(s) from
the U.S. Government; (d) will not use or transfer the Software for
use in any sensitive nuclear, chemical or biological weapons, or
missile technology end-uses unless authorized by the
U.S. Government by regulation or specific license; (e) understands
and agrees that if it is in the United States and exports or
transfers the Software to eligible end users, it will, as required
by EAR Section 741.17(e), submit semi-annual reports to the
Commerce Department's Bureau of Industry & Security (BIS), which
include the name and address (including country) of each
transferee; and (f) understands that countries other than the
United States may restrict the import, use, or export of
encryption products and that it shall be solely responsible for
compliance with any such import, use, or export restrictions.
6. GENERAL. If any provision of this agreement is held to be
unenforceable, that shall not affect the enforceability of the
remaining provisions. This agreement shall be governed by the
laws of the State of North Carolina and of the United States,
without regard to any conflict of laws provisions, except that the
United Nations Convention on the International Sale of Goods shall
not apply.
Copyright (C) 2003, 2004 Fedora Project. All rights reserved. "Red Hat"
and "Fedora" are trademarks of Red Hat, Inc. "Linux" is a registered
trademark of Linus Torvalds. All other trademarks are the property of
their respective owners.
--- NEW FILE fedora-devel.repo ---
[development]
name=Fedora Core $releasever - Development Tree
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/development/$basearch/
mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-rawhide
enabled=0
--- NEW FILE fedora-release.spec ---
%define builtin_release_version @VERSION@
%define builtin_release_name @RELNAME@
%define real_release_version %{?release_version}%{!?release_version:%{builtin_release_version}}
%define real_release_name %{?release_name}%{!?release_name:%{builtin_release_name}}
Summary: Fedora Core release file
Name: fedora-release
Version: %{real_release_version}
Release: 9
Copyright: GFDL
Group: System Environment/Base
Source: fedora-release-%{builtin_release_version}- at RELARCH@.tar.gz
Obsoletes: rawhide-release
Obsoletes: redhat-release
Obsoletes: indexhtml
Provides: redhat-release
Provides: indexhtml
BuildRoot: %{_tmppath}/fedora-release-root
ExclusiveArch: @RELARCH@
%description
Fedora Core release file
%prep
%setup -q -n fedora-release- at VERSION@- at RELARCH@
%build
python -c "import py_compile; py_compile.compile('eula.py')"
%install
rm -rf $RPM_BUILD_ROOT
mkdir -p $RPM_BUILD_ROOT/etc
echo "Fedora Core release %{real_release_version} (%{real_release_name})" > $RPM_BUILD_ROOT/etc/fedora-release
cp $RPM_BUILD_ROOT/etc/fedora-release $RPM_BUILD_ROOT/etc/issue
echo "Kernel \r on an \m" >> $RPM_BUILD_ROOT/etc/issue
cp $RPM_BUILD_ROOT/etc/issue $RPM_BUILD_ROOT/etc/issue.net
echo >> $RPM_BUILD_ROOT/etc/issue
ln -s fedora-release $RPM_BUILD_ROOT/etc/redhat-release
mkdir -p $RPM_BUILD_ROOT/usr/share/eula $RPM_BUILD_ROOT/usr/share/firstboot/modules
cp -f eula.txt $RPM_BUILD_ROOT/usr/share/eula/eula.en_US
cp -f eula.py $RPM_BUILD_ROOT/usr/share/firstboot/modules/eula.py
mkdir -p -m 755 $RPM_BUILD_ROOT/%{_defaultdocdir}/HTML
cp -ap img css \
$RPM_BUILD_ROOT/%{_defaultdocdir}/HTML
for file in indexhtml-*.html ; do
newname=`echo $file | sed 's|indexhtml-\(.*\)-\(.*\).html|index-\2.html|g'`
install -m 644 $file $RPM_BUILD_ROOT/%{_defaultdocdir}/HTML/$newname || :
done
mv -f $RPM_BUILD_ROOT/%{_defaultdocdir}/HTML/index-en.html \
$RPM_BUILD_ROOT/%{_defaultdocdir}/HTML/index.html || :
mkdir -p -m 755 $RPM_BUILD_ROOT/etc/sysconfig/rhn
mkdir -p -m 755 $RPM_BUILD_ROOT/etc/yum.repos.d
install -m 644 sources $RPM_BUILD_ROOT/etc/sysconfig/rhn/sources
for file in fedora*repo ; do
install -m 644 $file $RPM_BUILD_ROOT/etc/yum.repos.d
done
%clean
rm -rf $RPM_BUILD_ROOT
# If this is the first time a package containing /etc/issue
# is installed, we want the new files there. Otherwise, we
# want %config(noreplace) to take precedence.
%triggerpostun -- redhat-release < 7.1.93-1
for I in issue issue.net; do
if [ -f /etc/$I.rpmnew ] ; then
mv -f /etc/$I /etc/$I.rpmsave
mv -f /etc/$I.rpmnew /etc/$I
fi
done
%files
%defattr(-,root,root)
%attr(0644,root,root) /etc/fedora-release
/etc/redhat-release
%dir /etc/sysconfig/rhn
%dir /etc/yum.repos.d
%config(noreplace) /etc/sysconfig/rhn/sources
%config(noreplace) /etc/yum.repos.d/*
%doc R*
%doc eula.txt GPL autorun-template
%config %attr(0644,root,root) /etc/issue
%config %attr(0644,root,root) /etc/issue.net
/usr/share/firstboot/modules/eula.py
/usr/share/eula/eula.en_US
%{_defaultdocdir}/HTML
--- NEW FILE fedora-updates-testing.repo ---
[updates-testing]
name=Fedora Core $releasever - $basearch - Test Updates
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/$releasever/$basearch/
mirrorlist=http://fedora.redhat.com/download/mirrors/updates-testing-fc$releasever
enabled=0
gpgcheck=1
--- NEW FILE fedora-updates.repo ---
[updates-released]
name=Fedora Core $releasever - $basearch - Released Updates
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/$releasever/$basearch/
mirrorlist=http://fedora.redhat.com/download/mirrors/updates-released-fc$releasever
enabled=1
gpgcheck=1
--- NEW FILE fedora.css ---
/*
CSS for Red Hat Linux Project docs from the Documentation Project
Written by Tammy Fox and Garrett LeSage
Copyright 2003 Tammy Fox, Garrett LeSage, and Red Hat, Inc.
License: GPL
*/
li p {
display: inline;
}
div.table table {
width: 95%;
background-color: #DCDCDC;
color: #000000;
border-spacing: 0;
}
div.table table th {
border: 1px solid #A9A9A9;
background-color: #A9A9A9;
color: #000000;
}
div.table table td {
border: 1px solid #A9A9A9;
background-color: #DCDCDC;
color: #000000;
padding: 0.5em;
margin-bottom: 0.5em;
margin-top: 2px;
}
div.note table, div.tip table, div.important table, div.caution table, div.warning table {
width: 95%;
border: 2px solid #B0C4DE;
background-color: #F0F8FF;
color: #000000;
/* padding inside table area */
padding: 0.5em;
margin-bottom: 0.5em;
margin-top: 0.5em;
}
.qandaset table {
border-collapse: collapse;
}
.qandaset {
}
.qandaset tr.question {
}
.qandaset tr.question td {
font-weight: bold;
padding: 1em 1em 0;
}
.qandaset tr.answer td {
padding: 0.25em 1em 1.5em;
}
.qandaset tr.question td, .qandaset tr.answer td {
}
hr {
border: 0;
border-bottom: 1px solid #ccc;
}
h1, h2, h3, h4 {
font-family: luxi sans,sans-serif;
color: #990000;
font-weight: bold;
}
h1 {
font-size: 1.75em;
}
h2 {
font-size: 1.25em;
}
h3 {
font-size: 1.1em;
}
code.screen, pre.screen {
font-family: monospace;
font-size: 1em;
display: block;
padding: 10px;
border: 1px solid #bbb;
background-color: #eee;
color: #000;
overflow: auto;
border-radius: 2.5px;
-moz-border-radius: 2.5px;
margin: 0.5em 2em;
}
div.example {
padding: 10px;
border: 1px solid #bbb;
margin: 0.5em 2em;
}
.procedure ol li {
margin-bottom: 1.5em;
}
/* prevent inheritance */
.procedure ol li li {
margin-bottom: 0em;
}
--- NEW FILE fedora.repo ---
[base]
name=Fedora Core $releasever - $basearch - Base
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/os/
mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-$releasever
enabled=1
gpgcheck=1
--- NEW FILE feedback.xml ---
<section id="sn-test" os="test">
<title>Release Notes Feedback Procedure</title>
<para>(This section will disappear when the final &DISTRO; release is
created.)</para>
<para>If you feel that these release notes could be improved in some way,
you can provide feedback directly to the author. If you see a URL in the
release notes that looks like this:</para>
<para>%%% https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=<replaceable><bug-number></replaceable> %%% </para>
<para>You can click on the URL and submit feedback on that particular
section of the release notes. Your feedback will be added as a comment to
an existing bug report.</para>
<para>If the section of the release notes that you have feedback for does
not have one of these URLs (or you are submitting a request for entirely
new content), you can click on the following link (this only works for the
HTML version, of course — the URL is much too long to include in the
text):</para>
<para><ulink
url="https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Core&op_sys=Linux&version=devel&component=fedora-release&component_text=&rep_platform=All&priority=normal&bug_severity=normal&bug_status=NEW&assigned_to=&cc=&estimated_time=0.0&bug_file_loc=http%3A%2F%2F&short_desc=FC3%20release%20notes%20--%20&comment=Please%20add%20a%20descriptive%20phrase%20to%20the%20summary%2C%20and%20more%20in-depth%0D%0Adescription%20here%20%28be%20sure%20to%20note%20any%20arch-specific%20issues%29%3A%0D%0A%0D%0A&keywords=&dependson=&blocked=114398&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug">Click
here to submit new release notes feedback</ulink></para>
<para>If you would like to review the changes that have been already
submitted for this document, use the following link:</para>
<para><ulink
url="http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398">http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398</ulink></para>
<para>As bugs are posted for the various parts of the release notes,
subsequent test versions of these release notes will contain links similar
to the one described earlier.</para>
<para>Thank you (in advance) for your feedback!</para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE file-servers.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.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE hardware-reqs.xml ---
<section id="sn-hardware-reqs">
<title>Hardware Requirements</title>
<para>
The following information represents the minimum hardware
requirements necessary to successfully install &DISTRO; &DISTROVER;.
</para>
<note>
<title>Note</title>
<para>
The compatibility/availability of other hardware components (such
as video and network cards) may be required for specific
installation modes and/or post-installation usage.
</para>
</note>
<!-- 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.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.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.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.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 main.xsl ---
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:exsl="http://exslt.org/common"
version="1.0"
exclude-result-prefixes="exsl">
<xsl:import href="readmes.xsl"/>
<xsl:import href="/usr/share/sgml/docbook/xsl-stylesheets/html/chunk-common.xsl"/>
<xsl:include href="/usr/share/sgml/docbook/xsl-stylesheets/html/manifest.xsl"/>
<!-- Why is chunk-code now xsl:included?
Suppose you want to customize *both* the chunking algorithm used *and* the
presentation of some elements that may be chunks. In order to do that, you
must get the order of imports "just right". The answer is to make your own
copy of this file, where you replace the initial import of "docbook.xsl"
with an import of your own base.xsl (that does its own import of docbook.xsl).
Put the templates for changing the presentation of elements in your base.xsl.
Put the templates that control chunking after the include of chunk-code.xsl.
Voila! (Man I hope we can do this better in XSLT 2.0)
-->
<!-- don't show TOC for article because html viewer in anaconda doesn't support the dt and dl tags -->
<xsl:param name="generate.toc">
article nop
</xsl:param>
<xsl:include href="/usr/share/sgml/docbook/xsl-stylesheets/html/profile-docbook.xsl"/>
<xsl:param name="onechunk" select="1"/>
<xsl:output method="html" encoding="utf-8" indent="no"/>
</xsl:stylesheet>
--- NEW FILE misc-server.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.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.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.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.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.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>
<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.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
--- NEW FILE project-overview.xml ---
<section id="sn-whatitis">
<title>An Overview of the &PROJ;</title>
<para>
The goal of the &PROJ; is to work with the Linux community to
build a complete, general-purpose operating system exclusively
from open source software. Development 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 readmes.xsl ---
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fo="http://www.w3.org/1999/XSL/Format"
version='1.0'>
<xsl:output method="html" encoding="UTF-8" indent="no"/>
<!-- This sets the extension for HTML files to ".html". -->
<!-- (The stylesheet's default for XHTML files is ".xhtm".) -->
<xsl:param name="html.ext" select="'.html'"/>
<!-- This sets the filename based on the ID. -->
<xsl:param name="use.id.as.filename" select="'0'"/>
<xsl:param name="suppress.navigation" select="'1'"/>
<xsl:param name="generate.toc">
article nop
</xsl:param>
<xsl:param name="chapter.autolabel" select="'0'"/>
<xsl:template match="command">
<xsl:call-template name="inline.monoseq"/>
</xsl:template>
<xsl:template match="application">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guibutton">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guiicon">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guilabel">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guimenu">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guimenuitem">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guisubmenu">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="filename">
<xsl:call-template name="inline.monoseq"/>
</xsl:template>
</xsl:stylesheet>
--- NEW FILE samba.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.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.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 sources ---
### This describes the various package repositories (repos) that up2date will
### query for packages. It currently supports apt-rpm, yum, and "dir" repos.
### Format is one repository (repo) entry per line, # starts comments, the
### first word on each line is the type of repo.
### The default RHN (using "default" as the url means use the one in the
### up2date config file).
#up2date default
### Note: when a channel label is required for the non up2date repos,
### the label is solely used as an internal identifier and is not
### based on the url or any other info from the repos.
### An apt style repo (the example is arjan's 2.6 kernel repo).
### The format is:
### type channel-label service:server path repo name
#apt arjan-2.6-kernel-i386 http://people.redhat.com ~arjanv/2.5/ kernel
### Note: for apt repos, there can be multiple repo names specified (space
### seperated).
### A yum style repo. The format is:
### type channel-label url
yum fedora-core-3 http://download.fedora.redhat.com/pub/fedora/linux/core/3/$ARCH/os/
yum updates-released-fc3 http://download.fedora.redhat.com/pub/fedora/linux/core/updates/3/$ARCH/
yum-mirror fedora-core-3 http://fedora.redhat.com/download/up2date-mirrors/fedora-core-3
yum-mirror updates-released-fc3 http://fedora.redhat.com/download/up2date-mirrors/updates-released-fc3
#yum updates-testing http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/3/$ARCH/
#yum-mirror updates-testing http://fedora.redhat.com/download/up2date-mirrors/updates-testing-fc3
#yum development http://download.fedora.redhat.com/pub/fedora/linux/core/development/$ARCH/
#yum-mirror development http://fedora.redhat.com/download/up2date-mirrors/fedora-core-rawhide
### A local directory full of packages (a "dir" repo). For example:
#dir my-favorite-rpms /var/spool/RPMS/
# Multiple versions of all repos except "up2date" can be used. Dependencies
# can be resolved "cross-repo" if need be.
--- NEW FILE splash.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>New Installation Guide</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>
</tip>
<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.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.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:
-->
More information about the Fedora-docs-commits
mailing list