release-notes/devel/en_US Installer.xml, 1.10, 1.11 Java.xml, 1.9, 1.10 Kernel.xml, 1.13, 1.14 Legacy.xml, 1.9, 1.10 Multimedia.xml, 1.9, 1.10 OverView.xml, 1.12, 1.13 PackageNotes.xml, 1.7, 1.8 ProjectOverview.xml, 1.8, 1.9 Security.xml, 1.10, 1.11 Virtualization.xml, 1.9, 1.10 WebServers.xml, 1.8, 1.9 Welcome.xml, 1.8, 1.9 Xorg.xml, 1.10, 1.11
Paul W. Frields (pfrields)
fedora-docs-commits at redhat.com
Tue Sep 26 01:27:18 UTC 2006
Author: pfrields
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30916
Modified Files:
Installer.xml Java.xml Kernel.xml Legacy.xml Multimedia.xml
OverView.xml PackageNotes.xml ProjectOverview.xml Security.xml
Virtualization.xml WebServers.xml Welcome.xml Xorg.xml
Log Message:
Fixed these beats to be as close to FC6 test3 version as possible.
Index: Installer.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Installer.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- Installer.xml 25 Sep 2006 08:30:32 -0000 1.10
+++ Installer.xml 26 Sep 2006 01:27:15 -0000 1.11
@@ -5,94 +5,94 @@
<section id="sn-Installer">
<title>Installation Notes</title>
-<!--RAW HTML: <h2>Installation Notes</h2>-->
-
<para>
- <emphasis role='strong'>Anaconda</emphasis> is the name of the
+ <application>Anaconda</application> is the name of the
Fedora Installer. This section outlines those issues that are
- related to <emphasis role='strong'>Anaconda</emphasis> (the Fedora
- Core installation program) and installing Fedora Core
-<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
- 6.
+ related to <application>Anaconda</application> (the Fedora
+ Core installation program) and installing Fedora Core 6.
</para>
<para>
<note>
<title>Downloading Large Files</title>
<para>
- If you intend to download the Fedora Core 6 DVD ISO image, keep in mind
- that not all file downloading tools can accommodate files larger than 2
- GiB in size. <command>wget</command> 1.9.1-16 and above,
- <command>curl</command> and <command>ncftpget</command> do not have this
- limitation, and can successfully download files larger than 2 GiB.
- BitTorrent is another method for downloading large files. For
- information about obtaining and using the torrent file, refer to
- http://torrent.fedoraproject.org/.
+ If you intend to download the Fedora Core 6 DVD ISO image, keep
+ in mind that not all file downloading tools can accommodate
+ files larger than 2 GiB in size. <command>wget</command>
+ 1.9.1-16 and above, <command>curl</command> and
+ <command>ncftpget</command> do not have this limitation, and can
+ successfully download files larger than 2 GiB.
+ <application>BitTorrent</application> is another method for
+ downloading large files. For information about obtaining and
+ using the torrent file, refer to <ulink
+ url="http://torrent.fedoraproject.org/"/>.
</para>
</note>
</para>
<para>
- <emphasis role='strong'>Anaconda</emphasis> tests the integrity of
+ <application>Anaconda</application> tests the integrity of
installation media by default. This function works with the CD, DVD,
hard drive ISO, and NFS ISO installation methods. The Fedora Project
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 <code>linux
- mediacheck</code> at the <prompt>boot:</prompt> prompt presented at the
- start of installation.
+ improperly-burned CDs. To use this test, type <userinput>linux
+ mediacheck</userinput> at the
+ <computeroutput>boot:</computeroutput> prompt presented at the start
+ of installation.
</para>
<para>
- The <code>mediacheck</code> 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 <code>mediacheck</code>,
- boot with the following option:
+ The <option>mediacheck</option> 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
+ <option>mediacheck</option>, boot with the following option:
</para>
<screen><![CDATA[linux ide=nodma
]]></screen>
<para>
- After you complete the <code>mediacheck</code> function
+ After you complete the <option>mediacheck</option> function
successfully, reboot to return DMA mode to its normal state. On many
systems this results in a faster installation process from disc. You
- may skip the <code>mediacheck</code> option when rebooting.
+ may skip the <option>mediacheck</option> option when rebooting.
</para>
<para>
- Use the <code>sha1sum</code> 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.
+ 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>
<para>
<important>
- <title>BitTorrent Automatically Verifies File Integrity</title>
+ <title><application>BitTorrent</application> Automatically
+ Verifies File Integrity</title>
<para>
- If you use '''BitTorrent''', any files you download are
- automatically validated. If your file completes downloading, you
- do not need to check it. Once you burn your CD, however, you
- should still use <command>mediacheck</command>.
+ If you use <application>BitTorrent</application>, any files you
+ download are automatically validated. If your file completes
+ downloading, you do not need to check it. Once you burn your CD,
+ however, you should still use <option>mediacheck</option>.
</para>
</important>
</para>
<para>
You may perform memory testing before you install Fedora Core by
- entering <code>memtest86</code> at the <code>boot:</code> prompt.
- This option runs the <emphasis role='strong'>Memtest86</emphasis>
- standalone memory testing software in place of
- <emphasis role='strong'>Anaconda</emphasis>.
- <emphasis role='strong'>Memtest86</emphasis> memory testing
- continues until the <code>Esc</code> key is pressed.
+ entering <userinput>memtest86</userinput> at the
+ <computeroutput>boot:</computeroutput> prompt. This option runs the
+ <application>Memtest86</application> standalone memory testing
+ software in place of <application>Anaconda</application>.
+ <application>Memtest86</application> memory testing continues until
+ the <keycap function="escape">Esc</keycap> key is pressed.
</para>
<para>
<note>
- <title>Memtest86 Availability</title>
+ <title><application>Memtest86</application> Availability</title>
<para>
You must boot from Installation Disc 1 or a rescue CD in order
to use this feature.
@@ -101,16 +101,15 @@
</para>
<para>
- Fedora Core
-<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
- 6 supports graphical FTP and HTTP installations. However, the
- installer image must either fit in RAM or appear on local storage
- such as Installation Disc 1. Therefore, only systems with more than
- 192MiB of RAM, or which boot from Installation Disc 1, can use the
- graphical installer. Systems with 192MiB RAM or less fall back
- to using the text-based installer automatically. If you prefer to
- use the text-based installer, type <code>linux text</code> at the
- <code>boot:</code> prompt.
+ Fedora Core 6 supports graphical FTP and HTTP installations.
+ However, the installer image must either fit in RAM or appear on
+ local storage such as Installation Disc 1. Therefore, only systems
+ with more than 192MiB of RAM, or which boot from Installation Disc
+ 1, can use the graphical installer. Systems with 192MiB RAM or less
+ fall back to using the text-based installer automatically. If you
+ prefer to use the text-based installer, type <userinput>linux
+ text</userinput> at the <computeroutput>boot:</computeroutput>
+ prompt.
</para>
<section>
@@ -118,11 +117,11 @@
<itemizedlist>
<listitem>
<para>
- <emphasis role='strong'>Anaconda</emphasis> now features the
- ability to install packages from Fedora Extras or any custom
- <code>yum</code>-compatible software repository. Fedora Extras
- is available by default on interactive installs with network
- connectivity.
+ <application>Anaconda</application> now features the ability
+ to install packages from Fedora Extras or any custom
+ <command>yum</command>-compatible software repository. Fedora
+ Extras is available by default on interactive installs with
+ network connectivity.
</para>
</listitem>
</itemizedlist>
@@ -146,34 +145,34 @@
</listitem>
<listitem>
<para>
- <emphasis role='strong'>Anaconda</emphasis> uses SquashFS to
- compress and store packages on images.
+ <application>Anaconda</application> uses SquashFS to compress
+ and store packages on images.
</para>
</listitem>
<listitem>
<para>
- <emphasis role='strong'>Anaconda</emphasis> now supports
- installation using IPv6.
+ <application>Anaconda</application> now supports installation
+ using IPv6.
</para>
</listitem>
<listitem>
<para>
- <emphasis role='strong'>Anaconda</emphasis> now supports
- installation from
- <ulink url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/FireWire'>FireWire</ulink>
- and USB storage devices.
+ <application>Anaconda</application> now supports installation
+ from <ulink
+ url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/FireWire'>FireWire</ulink>
+ and USB storage devices.
</para>
</listitem>
<listitem>
<para>
- <emphasis role='strong'>Anaconda's</emphasis> backend,
- <code>yum</code>, has been updated to 2.9.x.
+ <application>Anaconda's</application> backend,
+ <command>yum</command>, has been updated to 2.9.x.
</para>
</listitem>
<listitem>
<para>
- The installer provides enhanced support for the
- <code>ppc64</code> architecture.
+ The installer provides enhanced support for the ppc64
+ architecture.
</para>
</listitem>
<listitem>
@@ -206,45 +205,55 @@
<section>
<title>Kickstart Changes</title>
<para>
- Three new <code>kickstart</code> keywords have been added.
- </para>
- <para>
- <code>repo --name=<repoid>
- [--baseurl=<url>|--mirrorlist=<url></code>
- </para>
- <para>
- <code>repo</code> specifies additional package repositories to use
- for installation. <code>baseurl</code> specifies the URL for the
- repository, while <code>mirrorlist</code> specifies a list of
- mirrors. One and only one of these options may be specified per
- repository definition.
- </para>
- <para>
- <code>services [--disabled=<list>] [--enabled=<list>]
- </code>
+ Three new <systemitem>kickstart</systemitem> keywords have been
+ added.
</para>
- <para>
- <code>services</code> modifies the default set of services that
- are started in the default runlevel. <code>enabled</code> and
- <code>disabled</code> take comma-separated lists, with
- <code>enabled</code> services taking priority.
- </para>
- <para>
- <code>user --name=<username> [--groups=<list>]
- [--homedir=<homedir>] [--password=<password>] [--iscrypted]
- [--shell=<shell>] [--uid=<uid>] </code>
- </para>
- <para>
- <code>user</code> creates a new user with the specified
- parameters. <code>name</code> is required; all other parameters
- are optional.
- </para>
- <para>
- More documentation on <code>kickstart</code> is available in the
- <code>anaconda</code> package. To install it, run the command
- <code>su -c 'yum install anaconda'</code> and read the
- <code>/usr/share/doc/anaconda*/kickstart-docs.txt</code> file for
- more information.
+ <variablelist>
+ <varlistentry>
+ <term><code><![CDATA[repo --name=<repoid> [--baseurl=<url>|--mirrorlist=<url>]]></code></term>
+ <listitem>
+ <para>
+ <option>repo</option> specifies additional package
+ repositories to use for installation.
+ <option>baseurl</option> specifies the URL for the
+ repository, while <option>mirrorlist</option> specifies a
+ list of mirrors. One and only one of these options may be
+ specified per repository definition.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><code><![CDATA[services [--disabled=<list>] [--enabled=<list>] ]]></code></term>
+ <listitem>
+ <para>
+ <option>services</option> modifies the default set of
+ services that are started in the default runlevel.
+ <option>enabled</option> and <option>disabled</option> take
+ comma-separated lists, with <option>enabled</option>
+ services taking priority.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><code><![CDATA[user --name=<username> [--groups=<list>]
+[--homedir=<homedir>] [--password=<password>] [--iscrypted]
+[--shell=<shell>] [--uid=<uid>] ]]></code></term>
+ <listitem>
+ <para>
+ <option>user</option> creates a new user with the specified
+ parameters. <option>name</option> is required; all other
+ parameters are optional.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ More documentation on <systemitem>kickstart</systemitem> is
+ available in the <package>anaconda</package> package. To install
+ it, run the command <command>su -c 'yum install
+ anaconda'</command> and read the
+ <filename>/usr/share/doc/anaconda*/kickstart-docs.txt</filename>
+ file for more information.
</para>
</section>
@@ -269,20 +278,21 @@
<title>IDE RAID</title>
<para>
Not all IDE RAID controllers are supported. If your RAID
- controller is not yet supported by <code>dmraid</code>, you may
- combine drives into RAID arrays by configuring Linux software
- RAID. For supported controllers, configure the RAID functions in
- the computer BIOS.
+ controller is not yet supported by <option>dmraid</option>, you
+ may combine drives into RAID arrays by configuring Linux
+ software RAID. For supported controllers, configure the RAID
+ functions in the computer BIOS.
</para>
</section>
<section>
<title>Multiple NICs and PXE Installation</title>
<para>
Some servers with multiple network interfaces may not assign
- <computeroutput>eth0</computeroutput> to the first network interface as
- BIOS knows it, which can cause the installer to try using a different
- network interface than was used by PXE. To change this behavior, use the
- following in pxelinux.cfg/* config files:
+ <systemitem>eth0</systemitem> to the first network interface as
+ BIOS knows it, which can cause the installer to try using a
+ different network interface than was used by PXE. To change this
+ behavior, use the following in
+ <filename>pxelinux.cfg/*</filename> config files:
</para>
<screen><![CDATA[IPAPPEND 2
APPEND ksdevice=bootif
@@ -319,13 +329,16 @@
<itemizedlist>
<listitem>
<para>
- Before you upgrade, back up the system completely. In particular,
- preserve <code>/etc</code>, <code>/home</code>, and possibly
- <code>/opt</code> and <code>/usr/local</code> if customized packages
- are installed there. You may wish to use a multi-boot approach with a
- <firstterm>clone</firstterm> of the old installation on alternate
- partition(s) as a fallback. In that case, create alternate boot
- media such as a GRUB boot floppy.
+ Before you upgrade, back up the system completely. In
+ particular, preserve <filename
+ class="directory">/etc</filename>, <filename
+ class="directory">/home</filename>, and possibly <filename
+ class="directory">/opt</filename> and <filename
+ class="directory">/usr/local</filename> if customized
+ packages are installed there. You may wish to use a multi-boot
+ approach with a "clone" of the old installation on alternate
+ partition(s) as a fallback. In that case, create alternate
+ boot media such as a GRUB boot floppy.
</para>
</listitem>
</itemizedlist>
@@ -333,8 +346,9 @@
<important>
<title>System Configuration Backups</title>
<para>
- Backups of configurations in <filename>/etc</filename> are also useful
- in reconstructing system settings after a fresh installation.
+ Backups of configurations in <filename
+ class="directory">/etc</filename> are also useful in
+ reconstructing system settings after a fresh installation.
</para>
</important>
</para>
@@ -358,3 +372,9 @@
</itemizedlist>
</section>
</section>
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
Index: Java.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Java.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- Java.xml 25 Sep 2006 08:56:19 -0000 1.9
+++ Java.xml 26 Sep 2006 01:27:15 -0000 1.10
@@ -9,10 +9,11 @@
<para>
This release of Fedora Core includes a free and open source Java
- environment called <code>java-gcj-compat</code>. The
- <code>java-gcj-compat</code> collection includes a tool suite and
- execution environment that is capable of building and running many
- useful programs that are written in the Java programming language.
+ environment called <systemitem>java-gcj-compat</systemitem>. The
+ <systemitem>java-gcj-compat</systemitem> collection includes a tool
+ suite and execution environment that is capable of building and
+ running many useful programs that are written in the Java
+ programming language.
</para>
<para>
@@ -20,33 +21,34 @@
<title>Fedora Core Does Not Include Java</title>
<para>
Java is a trademark of Sun Microsystems.
- <package>java-gcj-compat</package> is an entirely free software stack
- that is <emphasis>not</emphasis> Java, but may run Java software.
+ <systemitem>java-gcj-compat</systemitem> is an entirely free
+ software stack that is <emphasis>not</emphasis> Java, but may
+ run Java software.
</para>
</note>
</para>
<para>
- The
-<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
- <package>java-gcj-compat</package> infrastructure has three key components: a
- <emphasis role='strong'>GNU Java</emphasis> runtime
- (<code>libgcj</code>), the <emphasis role='strong'>Eclipse
- Java</emphasis> compiler (<code>ecj</code>), and a set of wrappers
- and links (<code>java-gcj-compat</code>) that present the runtime
- and compiler to the user in a manner similar to other Java
- environments.
+ The <!--GetVal-macro not supported by the docbook formatter, but
+ giving it a shot anyway--> <systemitem>java-gcj-compat</systemitem>
+ infrastructure has three key components: a <application>GNU
+ Java</application> runtime (<systemitem
+ class="library">libgcj</systemitem>), the <application>Eclipse
+ Java</application> compiler (<systemitem>ecj</systemitem>), and a
+ set of wrappers and links (<systemitem>java-gcj-compat</systemitem>)
+ that present the runtime and compiler to the user in a manner
+ similar to other Java environments.
</para>
<para>
The Java software packages in this Fedora release use the
- <code>java-gcj-compat</code> environment. These packages include
- <emphasis role='strong'>OpenOffice.org Base</emphasis>,
- <emphasis role='strong'>Eclipse</emphasis>, and
- <emphasis role='strong'>Apache Tomcat</emphasis>. Refer to the Java
- FAQ at <ulink url='http://www.fedoraproject.org/wiki/JavaFAQ'/> for
- more information on the <code>java-gcj-compat</code> free Java
- environment in Fedora.
+ <systemitem>java-gcj-compat</systemitem> environment. These packages
+ include <application>OpenOffice.org Base</application>,
+ <application>Eclipse</application>, and <application>Apache
+ Tomcat</application>. Refer to the Java FAQ at <ulink
+ url='http://www.fedoraproject.org/wiki/JavaFAQ'/> for more
+ information on the <systemitem>java-gcj-compat</systemitem> free
+ Java environment in Fedora.
</para>
<para>
@@ -65,15 +67,17 @@
<section>
<title>Handling Java and Java-like Packages</title>
<para>
- In addition to the <code>java-gcj-compat</code> free software
- stack, Fedora Core lets you install multiple Java implementations
- and switch between them using the <code>alternatives</code>
- command line tool. However, every Java system you install must be
- packaged using the JPackage Project packaging guidelines to take
- advantage of <code>alternatives</code>. Once these packages are
- installed properly, the <code>root</code> user may switch between
- <code>java</code> and <code>javac</code> implementations using the
- <code>alternatives</code> command:
+ In addition to the <systemitem>java-gcj-compat</systemitem> free
+ software stack, Fedora Core lets you install multiple Java
+ implementations and switch between them using the
+ <command>alternatives</command> command line tool. However, every
+ Java system you install must be packaged using the JPackage
+ Project packaging guidelines to take advantage of
+ <command>alternatives</command>. Once these packages are installed
+ properly, the <systemitem class="username">root</systemitem> user
+ may switch between <systemitem>java</systemitem> and
+ <systemitem>javac</systemitem> implementations using the
+ <command>alternatives</command> command:
</para>
<screen><![CDATA[alternatives --config java
alternatives --config javac
@@ -104,19 +108,20 @@
<title>Handling Java Applets</title>
<para>
This release of Fedora Core includes a preview release of
- <code>gcjwebplugin</code>, a <application>Firefox</application> plugin for
- Java applets.
- <code>gcjwebplugin</code> is not enabled by default.
- Although the security implementation in <code>GNU Classpath</code>
- is being actively developed, it is not mature enough to run
- untrusted applets safely. That said, the AWT and Swing
- implementations in <code>GNU Classpath</code> are now sufficiently
- mature that they can run many applets deployed on the web.
- Adventurous users who want to try <code>gcjwebplugin</code> can
- read
- <code>/usr/share/doc/libgcj-4.1.1/README.libgcjwebplugin.so</code>,
- as installed by the <code>gcc</code> rpm. The README explains how
- to enable the plugin and the risks associated with doing so.
+ <systemitem>gcjwebplugin</systemitem>, a
+ <application>Firefox</application> plugin for Java applets.
+ <systemitem>gcjwebplugin</systemitem> is not enabled by default.
+ Although the security implementation in <application>GNU
+ Classpath</application> is being actively developed, it is not
+ mature enough to run untrusted applets safely. That said, the AWT
+ and Swing implementations in <application>GNU
+ Classpath</application> are now sufficiently mature that they
+ can run many applets deployed on the web. Adventurous users who
+ want to try <systemitem>gcjwebplugin</systemitem> can read
+ <filename>/usr/share/doc/libgcj-4.1.1/README.libgcjwebplugin.so</filename>,
+ as installed by the <package>gcc</package> rpm. The README
+ explains how to enable the plugin and the risks associated with
+ doing so.
</para>
</section>
@@ -182,26 +187,33 @@
</para>
<para>
Fedora also includes plugins and features that are particularly
- useful to FOSS hackers:
- <ulink url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/ChangeLog'>ChangeLog</ulink>
- editing with <code>eclipse-changelog</code> and Bugzilla
- interaction with <code>eclipse-bugzilla</code>. Our CDT package
- also includes work-in-progress support for the GNU Autotools. The
+ useful to FOSS hackers: <ulink
+ url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/ChangeLog'>ChangeLog</ulink>
+ editing with <systemitem>eclipse-changelog</systemitem> and
+ Bugzilla interaction with
+ <systemitem>eclipse-bugzilla</systemitem>. Our CDT package also
+ includes work-in-progress support for the GNU Autotools. The
latest information regarding these projects can be found at the
<ulink url='http://sourceware.org/eclipse/'>Fedora Eclipse
- Project</ulink> page.
+ Project</ulink> page.
</para>
<section>
<title>Non-packaged Plugins/Feature</title>
<para>
Fedora Eclipse contains a patch to allow non-root users to make
- use of the Update Manager functionality for installing
- non-packaged plugins and features. Such plugins are installed in
- the user's home directory under the <code>.eclipse</code>
- directory. Please note, however, that these plugins do not have
- associated GCJ-compiled bits and may therefore run slower than
- expected.
+ use of the Update Manager functionality for installing
+ non-packaged plugins and features. Such plugins are installed in
+ the user's home directory under the <filename
+ class="directory">.eclipse</filename> directory. Please note,
+ however, that these plugins do not have associated GCJ-compiled
+ bits and may therefore run slower than expected.
</para>
</section>
</section>
</section>
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
Index: Kernel.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Kernel.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- Kernel.xml 25 Sep 2006 11:33:14 -0000 1.13
+++ Kernel.xml 26 Sep 2006 01:27:15 -0000 1.14
@@ -5,13 +5,9 @@
<section id="sn-Kernel">
<title>Linux Kernel</title>
-<!--RAW HTML: <h2>Linux Kernel</h2>-->
-
<para>
This section covers changes and important information regarding the
- 2.6.18 based kernel in Fedora Core
-<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
- 6. The 2.6.18 kernel includes:
+ 2.6.18 based kernel in Fedora Core 6. The 2.6.18 kernel includes:
</para>
<itemizedlist>
@@ -58,8 +54,8 @@
<listitem>
<para>
A new per-packet access control for SELinux called
- <code>secmark</code>
- (<ulink url='http://james-morris.livejournal.com/11010.html'/>)
+ <option>secmark</option> (<ulink
+ url='http://james-morris.livejournal.com/11010.html'/>)
</para>
</listitem>
<listitem>
@@ -96,8 +92,7 @@
To obtain a list of these patches, download the source RPM package
and run the following command against it:
</para>
-<screen><![CDATA[rpm -qpl kernel-<version>.src.rpm
-]]></screen>
+ <screen>rpm -qpl kernel-<replaceable><version></replaceable>.src.rpm</screen>
</section>
<section>
@@ -106,8 +101,7 @@
To retrieve a log of changes to the package, run the following
command:
</para>
-<screen><![CDATA[rpm -q --changelog kernel-<version>
-]]></screen>
+ <screen>rpm -q --changelog kernel-<replaceable><version></replaceable></screen>
<para>
If you need a user friendly version of the changelog, refer to
<ulink url='http://wiki.kernelnewbies.org/LinuxChanges'/>. A short
@@ -128,16 +122,15 @@
<anchor id='Kernel_Flavors'/>
</para>
<para>
- Fedora Core
-<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
- 6 includes the following kernel builds:
+ Fedora Core 6 includes the following kernel builds:
</para>
<itemizedlist>
<listitem>
<para>
Native kernel, for use in most systems. Configured sources are
- available in the
- <code>kernel-devel-<version>.<arch>.rpm</code> package.
+ available in the
+ <filename>kernel-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
+ package.
</para>
</listitem>
<listitem>
@@ -150,31 +143,32 @@
<listitem>
<para>
Virtualization kernel for use with the Xen emulator package.
- Configured sources are available in the
- <code>kernel-xen-devel-<version>.<arch>.rpm</code>
- package.
+ Configured sources are available in the
+ <filename>kernel-xen-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
+ package.
</para>
</listitem>
<listitem>
<para>
- Kdump kernel for use with kexec/kdump capabilities. Configured
- sources are available in the
- <code>kernel-kdump-devel-<version>.<arch>.rpm</code>
- package.
+ Kdump kernel for use with
+ <systemitem>kexec</systemitem>/<systemitem>systemitem</kdump>
+ capabilities. Configured sources are available in the
+ <filename>kernel-kdump-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
+ package.
</para>
</listitem>
</itemizedlist>
<para>
You may install kernel headers for all kernel flavors at the same
time. The files are installed in the
- <code>/usr/src/kernels/<version>-[xen|kdump]-<arch>/</code>
+ <filename>/usr/src/kernels/<replaceable><version></replaceable>-[xen|kdump]-<replaceable><arch></replaceable>/</filename>
tree. Use the following command:
</para>
-<screen><![CDATA[su -c 'yum install kernel-{PAE,xen,kdump}-devel'
-]]></screen>
+<screen>su -c 'yum install kernel-{PAE,xen,kdump}-devel'</screen>
<para>
Select one or more of these flavors, separated by commas and no
- spaces, as appropriate. Enter the root password when prompted.
+ spaces, as appropriate. Enter the <systemitem
+ class="username">root</systemitem> password when prompted.
</para>
<para>
<note>
@@ -214,222 +208,181 @@
<para>
Many of the tutorials, examples, and textbooks about Linux kernel
development assume the kernel sources are installed under the
- <code>/usr/src/linux/</code> directory. If you make a symbolic
- link, as shown below, you should be able to use those learning
- materials with the Fedora Core packages. Install the appropriate
- kernel sources, as shown earlier, and then run the following
- command:
+ <filename class="directory">/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 Fedora Core packages.
+ Install the appropriate kernel sources, as shown earlier, and then
+ run the following command:
</para>
-<screen><![CDATA[su -c 'ln -s /usr/src/kernels/<version>.<release>-<arch> /usr/src/linux'
-]]></screen>
+ <screen>su -c 'ln -s /usr/src/kernels/<replaceable><version></replaceable>.<replaceable><release></replaceable>-<replaceable><arch></replaceable> /usr/src/linux'</screen>
<para>
- Enter the <code>root</code> password when prompted.
+ Enter the <systemitem class="username">root</systemitem> password
+ when prompted.
</para>
</section>
<section>
<title>Preparing for Kernel Development</title>
<para>
- Fedora Core
-<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
- 6 does not include the kernel-source package provided by older
- versions since only the kernel-devel package is required now to
- build external modules. Configured sources are available, as
- described in this kernel flavors section.
+ Fedora Core 6 does not include the
+ <filename>kernel-source</filename> package provided by older
+ versions since only the <filename>kernel-devel</filename> package
+ is required now to build external modules. Configured sources are
+ available, as described in this kernel flavors section.
</para>
<note>
<title>Instructions Refer to Current 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, the expression <version> refers to the kernel
- version shown by the command: <code>uname -r</code>.
+ 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, the expression
+ <literal><replaceable><version></replaceable></literal>
+ refers to the kernel version shown by the command: <command>uname
+ -r</command>.
</para>
</note>
<para>
Users who require access to Fedora Core original kernel sources
- can find them in the kernel .src.rpm package. To create an
+ can find them in the kernel <filename
+ class="extension">.src.rpm</filename> package. To create an
exploded source tree from this file, perform the following steps:
</para>
<note>
<title>Do Not Build Packages as Super-user (root)</title>
<para>
- Building packages as the superuser is inherently dangerous and is not
- required, even for the kernel. These instructions allow you to install
- the kernel source as a normal user. Many general information sites refer
- to <code>/usr/src/linux</code> in their kernel instructions. If you use
- these instructions, simply substitute
- <code>~/rpmbuild/BUILD/kernel-<version>/linux-<version>.<arch></code>."]]
+ Building packages as the superuser is inherently dangerous and
+ is not required, even for the kernel. These instructions allow
+ you to install the kernel source as a normal user. Many general
+ information sites refer to <filename
+ class="directory">/usr/src/linux</filename> in their kernel
+ instructions. If you use these instructions, simply substitute
+ <filename class="directory">~/rpmbuild/BUILD/kernel-<replaceable><version></replaceable>/linux-<replaceable><version></replaceable>.<replaceable><arch></replaceable></filename>."]]
</para>
</note>
- <orderedlist numeration='arabic'>
- <listitem>
+ <procedure>
+ <step>
<para>
Prepare a RPM package building environment in your home
directory. Run the following commands:
</para>
- </listitem>
- </orderedlist>
-<screen><![CDATA[su -c 'yum install rpmdevtools yum-utils'
-rpmdev-setuptree
-]]></screen>
- <itemizedlist>
- <listitem override='none'>
- <para>
- Enter the <code>root</code> password when prompted.
- </para>
- </listitem>
- </itemizedlist>
- <orderedlist numeration='arabic'>
- <listitem>
- <para>
- Download the <code>kernel-<version>.src.rpm</code> file.
- Enable any appropriate source repositories, such as Core,
- Updates, or Testing, with the <code>-e</code> switch:
- </para>
- </listitem>
- </orderedlist>
-<screen><![CDATA[yumdownloader -e core-source -e updates-source --source kernel
-]]></screen>
- <itemizedlist>
- <listitem override='none'>
- <para>
- Enter the <code>root</code> password when prompted.
- </para>
- </listitem>
- </itemizedlist>
- <orderedlist numeration='arabic'>
- <listitem>
- <para>
- Install <code>kernel-<version>.src.rpm</code> using the
- command:
- </para>
- </listitem>
- </orderedlist>
-<screen><![CDATA[rpm -Uvh kernel-<version>.src.rpm
-]]></screen>
- <itemizedlist>
- <listitem override='none'>
- <para>
- This command writes the RPM contents into
- <code>${HOME}/rpmbuild/SOURCES</code> and
- <code>${HOME}/rpmbuild/SPECS</code>, where
- <code>${HOME}</code> is your home directory.
- </para>
- </listitem>
- </itemizedlist>
- <note>
- <title>Space Required</title>
- <para>
- The full kernel building process may require several gigabytes of extra
- space on the file system containing your home directory.
- </para>
- </note>
- <orderedlist numeration='arabic'>
- <listitem>
+<screen>su -c 'yum install rpmdevtools yum-utils' rpmdev-setuptree</screen>
+ </step>
+ <step>
+ <para>
+ Enter the <systemitem class="username">root</systemitem> password when prompted.
+ </para>
+ </step>
+ <step>
+ <para>
+ Download the
+ <filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
+ file. Enable any appropriate source repositories, such as
+ Core, Updates, or Testing, with the <option>-e</option>
+ switch:
+ </para>
+<screen>yumdownloader -e core-source -e updates-source --source kernel</screen>
+ </step>
+ <step>
+ <para>
+ Enter the <systemitem class="username">root</systemitem>
+ password when prompted.
+ </para>
+ </step>
+ <step>
+ <para>
+ Install
+ <filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
+ using the command:
+ </para>
+ <screen>rpm -Uvh kernel-<replaceable><version></replaceable>.src.rpm</screen>
+ </step>
+ <step>
+ <para>
+ This command writes the RPM contents into <filename
+ class="directory">${HOME}/rpmbuild/SOURCES</filename> and
+ <filename class="directory">${HOME}/rpmbuild/SPECS</filename>,
+ where <varname>${HOME}</varname> is your home directory.
+ </para>
+ <note>
+ <title>Space Required</title>
+ <para>
+ The full kernel building process may require several
+ gigabytes of extra space on the file system containing your
+ home directory.
+ </para>
+ </note>
+ </step>
+ <step>
<para>
Prepare the kernel sources using the commands:
</para>
- </listitem>
- </orderedlist>
<screen><![CDATA[cd ~/rpmbuild/SPECS
-rpmbuild -bp --target $(uname -m) kernel-2.6.spec
-]]></screen>
- <itemizedlist>
- <listitem override='none'>
- <para>
- The kernel source tree is located in the
- <code>~/rpmbuild/BUILD/kernel-<version>/linux-<version>.<arch></code>
- directory.
+rpmbuild -bp --target $(uname -m) kernel-2.6.spec]]></screen>
+ </step>
+ <step>
+ <para>
+ The kernel source tree is located in the <filename
+ class="directory">~/rpmbuild/BUILD/kernel-<replaceable><version></replaceable>/linux-<replaceable><version></replaceable>.<replaceable><arch></replaceable></filename>
+ directory.
</para>
- </listitem>
- </itemizedlist>
- <orderedlist numeration='arabic'>
- <listitem>
<para>
The configurations for the specific kernels shipped in Fedora
- Core
-<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
- 6 are in the
- <code>~/rpmbuild/BUILD/kernel-<version>/linux-<version>.<arch>/configs</code>
- directory. For example, the i686 configuration file is named
- <code>~/rpmbuild/BUILD/kernel-<version>/linux-<version>.<arch>/configs/kernel-<version>-i686.config</code>.
- Issue the following command to place the desired configuration
- file in the proper place for building:
- </para>
- </listitem>
- </orderedlist>
-<screen><![CDATA[cp configs/<desired-config-file> .config
-]]></screen>
- <orderedlist numeration='arabic'>
- <listitem>
- <para>
+ Core 6 are in the <filename
+ class="directory">~/rpmbuild/BUILD/kernel-<replaceable><version></replaceable>/linux-<replaceable><version></replaceable>.<replaceable><arch></replaceable>/configs</filename>
+ directory. For example, the i686 configuration file is named
+ <filename
+ class="directory">~/rpmbuild/BUILD/kernel-<replaceable><version></replaceable>/linux-<replaceable><version></replaceable>.<replaceable><arch></replaceable>/configs/kernel-<replaceable><version></replaceable>-i686.config</filename>.
+ Issue the following command to place the desired configuration
+ file in the proper place for building:
+ </para>
+ <screen>cp configs/<replaceable><desired-config-file></replaceable> .config</screen>
+ </step>
+ <step>
+ <para>
Every kernel gets a name based on its version number. This is
- the value the <code>uname -r</code> command displays. The
- kernel name is defined by the first four lines of the kernel
- <code>Makefile</code>. The <code>Makefile</code> has been
- changed to generate a kernel with a
- <emphasis>different</emphasis> name from that of the running
- kernel. To be accepted by the running kernel, a module must be
- compiled for a kernel with the correct name. To do this, you
- must edit the kernel <code>Makefile</code>.
- </para>
- <itemizedlist>
- <listitem override='none'>
- <para>
- For example, if the <code>uname -r</code> returns the
- string <code>2.6.17-1.2345_FC6</code>, change the
- <code>EXTRAVERSION</code> definition from this:
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </orderedlist>
-<screen><![CDATA[EXTRAVERSION = -prep
-]]></screen>
- <itemizedlist>
- <listitem override='none'>
+ 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>. The
+ <filename>Makefile</filename> has been changed to generate a
+ kernel with a <emphasis>different</emphasis> name from that of
+ the running kernel. To be accepted by the running kernel, a
+ module must be 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 <code>uname -r</code> returns the string
+ <code>2.6.17-1.2345_FC6</code>, change the
+ <code>EXTRAVERSION</code> definition from this:
+ </para>
+ <screen><![CDATA[EXTRAVERSION = -prep ]]></screen>
<para>
to this:
</para>
- </listitem>
- </itemizedlist>
-<screen><![CDATA[EXTRAVERSION = -1.2345_FC6
-]]></screen>
- <itemizedlist>
- <listitem override='none'>
+<screen><![CDATA[EXTRAVERSION = -1.2345_FC6]]></screen>
<para>
That is, substitute everything from the final dash onward.
</para>
- </listitem>
- </itemizedlist>
- <orderedlist numeration='arabic'>
- <listitem>
+ </step>
+ <step>
<para>
Run the following command:
</para>
- </listitem>
- </orderedlist>
-<screen><![CDATA[make oldconfig
-]]></screen>
- <itemizedlist>
- <listitem override='none'>
+<screen><![CDATA[make oldconfig]]></screen>
<para>
You may then proceed as usual.
</para>
- </listitem>
- </itemizedlist>
- <para>
- <note>
- <title>Building Kernel Binary RPMs</title>
- <para>
- Normally, kernels for Fedora are built using the
- <command>rpmbuild</command> utility and a specfile. Your results may
- vary if you use the kernel's built-in <command>make rpm</command>
- target.
- </para>
- </note>
- </para>
+ </step>
+ </procedure>
+ <note>
+ <title>Building Kernel Binary RPMs</title>
+ <para>
+ Normally, kernels for Fedora are built using the
+ <command>rpmbuild</command> utility and a specfile. Your results
+ may vary if you use the kernel's built-in <command>make
+ rpm</command> target.
+ </para>
+ </note>
</section>
<section>
@@ -437,32 +390,40 @@
<para>
An exploded source tree is not required to build a kernel module,
such as your own device driver, against the currently in-use
- kernel. Only the <code>kernel-devel</code> package is required to
- build external modules. If you did not select it during
- installation, use <emphasis role='strong'>Pirut</emphasis> to
- install it, going to <emphasis>Applications >
- Add/Remove</emphasis> software or use <code>yum</code> to install
- it. Run the following command to install the
- <code>kernel-devel</code> package using <code>yum</code>.
+ kernel. Only the <filename>kernel-devel</filename> package is
+ required to build external modules. If you did not select it
+ during installation, use <application>Pirut</application> to
+ install it, going to <menuchoice>
+ <guimenu>Applications</guimenu>
+ <guimenuitem>Add/Remove Software</guimenuitem></menuchoice> or
+ use <command>yum</command> to install it. Run the following
+ command to install the <filename>kernel-devel</filename> package
+ using <filename>yum</filename>.
</para>
<screen><![CDATA[su -c 'yum install kernel-devel'
]]></screen>
<para>
- For example, to build the <code>foo.ko</code> module, create the
- following <code>Makefile</code> in the directory containing the
- <code>foo.c</code> file:
+ 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>
<screen><![CDATA[obj-m := foo.o
-]]><![CDATA[
+
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
-]]><![CDATA[
+
default:
$(MAKE) -C $(KDIR) M=$(PWD) modules
]]></screen>
<para>
- Issue the <code>make</code> command to build the
- <code>foo.ko</code> module.
+ Issue the <command>make</command> command to build the
+ <filename>foo.ko</filename> module.
</para>
</section>
</section>
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
Index: Legacy.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Legacy.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- Legacy.xml 25 Sep 2006 11:35:05 -0000 1.9
+++ Legacy.xml 26 Sep 2006 01:27:15 -0000 1.10
@@ -78,3 +78,9 @@
<ulink url='http://fedoraproject.org/wiki/HelpWanted'/>.
</para>
</section>
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
Index: Multimedia.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Multimedia.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- Multimedia.xml 25 Sep 2006 11:41:42 -0000 1.9
+++ Multimedia.xml 26 Sep 2006 01:27:15 -0000 1.10
@@ -5,8 +5,6 @@
<section id="sn-Multimedia">
<title>Multimedia</title>
-<!--RAW HTML: <h2>Multimedia</h2>-->
-
<para>
Fedora Core includes applications for assorted multimedia functions,
including playback, recording and editing. Additional packages are
@@ -20,13 +18,12 @@
<title>Multimedia Players</title>
<para>
The default installation of Fedora Core includes
- <emphasis role='strong'>Rhythmbox</emphasis> and
- <emphasis role='strong'>Totem</emphasis> for media playback. The
- Fedora Core and Fedora Extras repositories include many other
- popular programs such as the
- <emphasis role='strong'>XMMS</emphasis> player and KDE's
- <emphasis role='strong'>amaroK</emphasis>. Both GNOME and KDE have
- a selection of players that can be used with a variety of formats.
+ <application>Rhythmbox</application> and
+ <application>Totem</application> for media playback. The Fedora
+ Core and Fedora Extras repositories include many other popular
+ programs such as the <application>XMMS</application> player and
+ KDE's <application>amaroK</application>. Both GNOME and KDE have a
+ selection of players that can be used with a variety of formats.
Third parties may offer additional programs to handle other
formats.
</para>
@@ -43,13 +40,12 @@
users may not be able to use the sound hardware simultaneously.
</para>
<para>
- <emphasis role='strong'>Helix Player</emphasis> has been removed
- from this release since it duplicates the functionality of
- <emphasis role='strong'>Totem</emphasis>.
- <emphasis role='strong'>Totem</emphasis> also uses the
- <emphasis role='strong'>GStreamer</emphasis> media framework,
- which is used by other multimedia applications in Fedora Core.
- With <emphasis role='strong'>GStreamer</emphasis>, users can
+ <application>Helix Player</application> has been removed from this
+ release since it duplicates the functionality of
+ <application>Totem</application>. <application>Totem</application>
+ also uses the <application>GStreamer</application> media
+ framework, which is used by other multimedia applications in
+ Fedora Core. With <application>GStreamer</application>, users can
easily add support for additional codecs to all included
applications.
</para>
@@ -101,15 +97,16 @@
<section>
<title>CD and DVD Authoring and Burning</title>
<para>
- Fedora Core and Fedora Extras software repositories includes a variety of
- tools for easily mastering and burning CDs and DVDs. GNOME users can burn
- directly from the <application>Nautilus</application> file manager, or
- choose the <code>gnomebaker</code> or <code>graveman</code> packages from
- Fedora Extras, or the older <code>xcdroast</code> package from Fedora
- Core. KDE users can use the robust <code>k3b</code> package, available in
- Fedora Extras, for these tasks. Console tools include
- <code>cdrecord</code>, <code>readcd</code>, <code>mkisofs</code>, and
- other popular applications.
+ Fedora Core and Fedora Extras software repositories includes a
+ variety of tools for easily mastering and burning CDs and DVDs.
+ GNOME users can burn directly from the Nautilus file manager, or
+ choose the <filename>gnomebaker</filename> or
+ <filename>graveman</filename> packages from Fedora Extras, or the
+ older <filename>xcdroast</filename> package from Fedora Core. KDE
+ users can use the robust <filename>k3b</filename> package,
+ available in Fedora Extras, for these tasks. Console tools include
+ <filename>cdrecord</filename>, <filename>readcd</filename>,
+ <filename>mkisofs</filename>, and other popular applications.
</para>
</section>
@@ -117,15 +114,15 @@
<title>Screencasts</title>
<para>
You can use Fedora to create and play back
- <emphasis>screencasts</emphasis>, which are recorded desktop
+ <firstterm>screencasts</firstterm>, which are recorded desktop
sessions, using open technologies. Fedora Extras software
- repository includes <code>istanbul</code>, which creates
+ repository includes <filename>istanbul</filename>, which creates
screencasts using the Theora video format. These videos can be
played back using one of several players included in Fedora Core.
This is the preferred way to submit screencasts to the Fedora
Project for either developer or end-user use. For a more
- comprehensive how-to, refer to
- <ulink url='http://fedoraproject.org/wiki/ScreenCasting'/>.
+ comprehensive how-to, refer to <ulink
+ url='http://fedoraproject.org/wiki/ScreenCasting'/>.
</para>
</section>
@@ -135,11 +132,19 @@
Most of the media players in Fedora Core and Fedora Extras
software repositories can use plugins to add support for
additional media formats and sound output systems. Some use
- powerful multimedia frameworks, such as the <code>gstreamer</code>
- package, to handle media format support and sound output. Fedora
- Core and Fedora Extras software repositories offer plugin packages
- for these backends and for individual applications. Third parties
- may provide additional plugins to add even greater capabilities.
+ powerful multimedia frameworks, such as the
+ <filename>gstreamer</filename> package, to handle media format
+ support and sound output. Fedora Core and Fedora Extras software
+ repositories offer plugin packages for these backends and for
+ individual applications. Third parties may provide additional
+ plugins to add even greater capabilities.
</para>
</section>
</section>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
Index: OverView.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/OverView.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- OverView.xml 25 Sep 2006 11:48:40 -0000 1.12
+++ OverView.xml 26 Sep 2006 01:27:15 -0000 1.13
@@ -5,8 +5,6 @@
<section id="sn-OverView">
<title>Release Highlights</title>
-<!--RAW HTML: <h2>Release Highlights</h2>-->
-
<section>
<title>Fedora Core 6 Tour</title>
<para>
@@ -37,7 +35,7 @@
</listitem>
<listitem>
<para>
- The <emphasis role='strong'>Compiz</emphasis> window manager
+ The <application>Compiz</application> window manager
provides better visual feedback and a variety of desktop
effects by using the AIGLX framework. More information is
available from the
@@ -48,9 +46,10 @@
<listitem>
<para>
This release features an update applet called
- <code>puplet</code> that provides user notifications when
- software updates are available. For more information, refer
- to <ulink url='http://fedoraproject.org/wiki/YumApplet'/>.
+ <application>puplet</application> that provides user
+ notifications when software updates are available. For more
+ information, refer to <ulink
+ url='http://fedoraproject.org/wiki/YumApplet'/>.
</para>
</listitem>
<listitem>
@@ -99,9 +98,9 @@
</listitem>
<listitem>
<para>
- <emphasis role='strong'>Helix Player</emphasis> has been
+ <application>Helix Player</application> has been
moved to Fedora Extras, since the included
- <emphasis role='strong'>Totem</emphasis> media player
+ <application>Totem</application> media player
provides similar functionality.
</para>
</listitem>
@@ -122,33 +121,35 @@
<listitem>
<para>
IMAP support for the
- <emphasis role='strong'>Evolution</emphasis> personal
+ <application>Evolution</application> personal
information manager is much improved in this release.
</para>
</listitem>
<listitem>
<para>
This release improves performance and manageability by
- splitting up package dependencies in a much more granular
- way. Affected packages include <code>beagle</code>,
- <code>evince</code>, and <code>NetworkManager</code>. For
- more information on these and other related changes, refer
- to <xref linkend="sn-PackageNotes"/>.
+ splitting up package dependencies in a much more granular
+ way. Affected packages include <package>beagle</package>,
+ <package>evince</package>, and
+ <package>NetworkManager</package>. For more information on
+ these and other related changes, refer to <xref
+ linkend="sn-PackageNotes"/>.
</para>
</listitem>
<listitem>
<para>
- In this release, the performance of <code>yum</code>,
- <emphasis role='strong'>Pirut</emphasis>, and
- <emphasis role='strong'>Pup</emphasis> has been
- significantly improved.
+ In this release, the performance of <command>yum</command>,
+ <application>Pirut</application>, and
+ <application>Pup</application> has been significantly
+ improved.
</para>
</listitem>
<listitem>
<para>
- <ulink url='http://fontconfig.org/wiki/2_2e4_20release_20notes'>Fontconfig
- 2.4</ulink> improves startup performance and memory
- footprint significantly.
+ <ulink
+ url='http://fontconfig.org/wiki/2_2e4_20release_20notes'><application>Fontconfig
+ 2.4</application></ulink> improves startup performance
+ and memory footprint significantly.
</para>
</listitem>
<listitem>
@@ -182,7 +183,7 @@
<listitem>
<para>
The Fedora installer,
- <emphasis role='strong'>Anaconda</emphasis>, can now connect
+ <application>Anaconda</application>, can now connect
to additional repositories such as Updates and Fedora
Extras, and users can install applications from these
repositories directly. Support for Fedora Extras is included
@@ -197,18 +198,19 @@
</listitem>
<listitem>
<para>
- This release features a new virtualization manager,
- <ulink url='http://virt-manager.et.redhat.com/'>virt-manager</ulink>,
- which adds a graphical management interface layer on top of
- <emphasis role='strong'>Xen</emphasis>.
+ This release features a new virtualization manager, <ulink
+ url='http://virt-manager.et.redhat.com/'><application>virt-manager</application></ulink>,
+ which adds a graphical management interface layer on top of
+ <application>Xen</application>.
</para>
</listitem>
<listitem>
<para>
This release increases usability of SELinux by providing a
- <ulink url='http://fedoraproject.org/wiki/SELinux/setroubleshoot'>graphical
- troubleshooting tool</ulink> and enhancements to the
- <emphasis role='strong'>Nautilus</emphasis> file manager.
+ <ulink
+ url='http://fedoraproject.org/wiki/SELinux/setroubleshoot'>graphical
+ troubleshooting tool</ulink> and enhancements to the
+ <application>Nautilus</application> file manager.
</para>
</listitem>
<listitem>
@@ -222,8 +224,8 @@
<listitem>
<para>
This release introduces a new tool,
- <code>lvm2-cluster</code>, for intuitively managing cluster
- volumes.
+ <application>lvm2-cluster</application>, for intuitively
+ managing cluster volumes.
</para>
</listitem>
</itemizedlist>
@@ -241,7 +243,7 @@
</listitem>
<listitem>
<para>
- <emphasis role='strong'>X.org 7.1</emphasis> now dynamically
+ <application>X.org 7.1</application> now dynamically
configures monitor resolution and refresh rates to limit the
amount of required user configuration.
</para>
@@ -256,18 +258,17 @@
<listitem>
<para>
This release includes better i18n support using the default
- <emphasis role='strong'>SCIM</emphasis> input method,
+ <application>SCIM</application> input method,
including more languages such as Sinhalase (Sri Lanka) and
Oriya, Kannada, and Malayalam (India). Fedora now provides
an easy interface to switch the input methods using
- <code>im-chooser</code>.
+ <command>im-chooser</command>.
</para>
</listitem>
<listitem>
<para>
- The <emphasis role='strong'>GNOME 1.x</emphasis> legacy
- stack has been removed from Fedora Core, and added to Fedora
- Extras.
+ The <application>GNOME 1.x</application> legacy stack has
+ been removed from Fedora Core, and added to Fedora Extras.
</para>
</listitem>
</itemizedlist>
@@ -282,3 +283,10 @@
</para>
</section>
</section>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
Index: PackageNotes.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/PackageNotes.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- PackageNotes.xml 25 Sep 2006 11:51:31 -0000 1.7
+++ PackageNotes.xml 26 Sep 2006 01:27:15 -0000 1.8
@@ -5,13 +5,10 @@
<section id="sn-PackageNotes">
<title>Package Notes</title>
-<!--RAW HTML: <h2>Package Notes</h2>-->
-
<para>
The following sections contain information regarding software
- packages that have undergone significant changes for Fedora Core
-<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
- 6. For easier access, they are generally organized using the same
+ packages that have undergone significant changes for Fedora Core 6.
+ For easier access, they are generally organized using the same
groups that are shown in the installation system.
</para>
@@ -24,25 +21,26 @@
<itemizedlist>
<listitem>
<para>
- <code>gnome-utils</code>
+ <package>gnome-utils</package>
</para>
</listitem>
<listitem>
<para>
- <code>beagle</code>, which no longer depends on
- <emphasis role='strong'>Evolution</emphasis>
+ <package>beagle</package>, which no longer depends on
+ <application>Evolution</application>
</para>
</listitem>
<listitem>
<para>
- <code>evince</code>, which no longer depends on
- <emphasis role='strong'>Nautilus</emphasis>
+ <package>evince</package>, which no longer depends on
+ <application>Nautilus</application>
</para>
</listitem>
<listitem>
<para>
- <code>NetworkManager</code>, which no longer depends on
- <code>bind</code> and <code>caching-nameserver</code>
+ <package>NetworkManager</package>, which no longer depends on
+ <package>bind</package> and
+ <package>caching-nameserver</package>
</para>
</listitem>
</itemizedlist>
@@ -51,7 +49,7 @@
<section>
<title>Web Server</title>
<para>
- The <code>php</code> package has been split to separate the
+ The <package>php</package> package has been split to separate the
command line binary from the CGI executable.
</para>
</section>
@@ -59,11 +57,11 @@
<section>
<title>Ext3 File System Utilities</title>
<para>
- A new version of <code>e2fsprogs</code> included in this
+ A new version of <package>e2fsprogs</package> included in this
release has a number of bug fixes. The
- <code>ext2online</code> feature has been integrated into
- <code>resize2fs</code>, so the <code>ext2online</code> program has
- been removed from this package.
+ <command>ext2online</command> feature has been integrated into
+ <command>resize2fs</command>, so the <command>ext2online</command>
+ program has been removed from this package.
</para>
</section>
@@ -71,63 +69,63 @@
<title>Licensing Audit</title>
<para>
The <ulink url='http://fedoraproject.org/wiki/Board'>Fedora
- Project Board</ulink> initiated a
- <ulink url='http://fedoraproject.org/wiki/FreeSoftwareAnalysis'>licensing
- audit</ulink> to ensure all software included in Fedora Core is
+ Project Board</ulink> initiated a <ulink
+ url='http://fedoraproject.org/wiki/FreeSoftwareAnalysis'>licensing
+ audit</ulink> to ensure all software included in Fedora Core is
compliant with the package licensing guidelines. This process is
now complete, and several changes were made as a result:
</para>
<itemizedlist>
<listitem>
<para>
- The <code>openmotif</code> package has been
- <ulink url='https://www.redhat.com/archives/fedora-devel-list/2006-August/msg01314.html'>dropped</ulink>
- due to a non-free license. Software packages previously
- dependent on the <code>openmotif</code> library have been
- rebuilt to use <code>lesstif</code>.
+ The <package>openmotif</package> package has been <ulink
+ url='https://www.redhat.com/archives/fedora-devel-list/2006-August/msg01314.html'>dropped</ulink>
+ due to a non-free license. Software packages previously
+ dependent on the <package>openmotif</package> library have
+ been rebuilt to use <package>lesstif</package>.
</para>
</listitem>
<listitem>
<para>
- The <code>macutils</code> pakcage has been
- <ulink url='https://www.redhat.com/archives/fedora-maintainers/2006-August/msg00021.html'>dropped</ulink>
- due to a non-free license.
+ The <package>macutils</package> package has been <ulink
+ url='https://www.redhat.com/archives/fedora-maintainers/2006-August/msg00021.html'>dropped</ulink>
+ due to a non-free license.
</para>
</listitem>
<listitem>
<para>
- The <code>ckermit</code> package has been
- <ulink url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.html'>dropped</ulink>
- due to a non-free license.
+ The <package>ckermit</package> package has been <ulink
+ url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.html'>dropped</ulink>
+ due to a non-free license.
</para>
</listitem>
<listitem>
<para>
- The <code>cleanfeed</code> package has been
- <ulink url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00401.html'>dropped</ulink>
- due to a non-free license.
+ The <package>cleanfeed</package> package has been <ulink
+ url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00401.html'>dropped</ulink>
+ due to a non-free license.
</para>
</listitem>
<listitem>
<para>
- The <code>aspell-nl</code> package has been
- <ulink url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.html'>changed</ulink>
- to include GPL licensed data.
+ The <package>aspell-nl</package> package has been <ulink
+ url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.html'>changed</ulink>
+ to include GPL licensed data.
</para>
</listitem>
<listitem>
<para>
- The <code>crypto-utils</code> package has been
- <ulink url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.html'>changed</ulink>
- to remove PGP licensed code in favor of new GPL licensed code.
+ The <package>crypto-utils</package> package has been <ulink
+ url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.html'>changed</ulink>
+ to remove PGP licensed code in favor of new GPL licensed code.
</para>
</listitem>
<listitem>
<para>
- The <code>netpbm</code> package has been
- <ulink url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.html'>changed</ulink>
- to remove all unlicensed or improper files from the source
- tarball.
+ The <package>netpbm</package> package has been <ulink
+ url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.html'>changed</ulink>
+ to remove all unlicensed or improper files from the source
+ tarball.
</para>
</listitem>
</itemizedlist>
@@ -139,8 +137,15 @@
The process of generating kernel headers has been <ulink
url='http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d730cfb50cc77da6d00f941daef440918a1922f'>changed</ulink>,
which provides several <ulink
- url='http://lkml.org/lkml/2006/7/2/24'>benefits</ulink> included easier
- maintenance and consistency.
+ url='http://lkml.org/lkml/2006/7/2/24'>benefits</ulink> included
+ easier maintenance and consistency.
</para>
</section>
</section>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
Index: ProjectOverview.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/ProjectOverview.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- ProjectOverview.xml 25 Sep 2006 11:55:16 -0000 1.8
+++ ProjectOverview.xml 26 Sep 2006 01:27:15 -0000 1.9
@@ -5,8 +5,6 @@
<section id="sn-ProjectOverview">
<title>Fedora Project - Freedom to the Core</title>
-<!--RAW HTML: <h2>Fedora Project - Freedom to the Core</h2>-->
-
<para>
The goal of the Fedora Project is to work with the Linux community
to build a complete, general-purpose operating system exclusively
@@ -26,12 +24,12 @@
<para>
The Fedora Project is driven by the individuals that contribute to
- it. As a tester, developer, documenter, or translator, you can make a
- difference. Refer to
- <ulink url='http://fedoraproject.org/wiki/HelpWanted'/> for details.
- For information on the channels of communication for Fedora users
- and contributors, refer to
- <ulink url='http://fedoraproject.org/wiki/Communicate'/>.
+ it. As a tester, developer, documenter, or translator, you can make
+ a difference. Refer to <ulink
+ url='http://fedoraproject.org/wiki/HelpWanted'/> for details. For
+ information on the channels of communication for Fedora users and
+ contributors, refer to <ulink
+ url='http://fedoraproject.org/wiki/Communicate'/>.
</para>
<para>
@@ -69,11 +67,11 @@
<para>
To subscribe to any of these lists, send an email with the word
"subscribe" in the subject to
- <emphasis><listname>-request</emphasis>, where
- <emphasis><listname></emphasis> is one of the above list names.
- Alternately, you can subscribe to Fedora mailing lists through the
- Web interface at
- <ulink url='http://www.redhat.com/mailman/listinfo/'/>.
+ <email><replaceable><listname></replaceable>-request</email>,
+ where <replaceable><listname></replaceable> is one of the
+ above list names. Alternately, you can subscribe to Fedora mailing
+ lists through the Web interface at <ulink
+ url='http://www.redhat.com/mailman/listinfo/'/>.
</para>
<para>
@@ -88,18 +86,20 @@
</para>
<para>
- Fedora Project participants frequent the <code>#fedora</code>
- channel on the Freenode network, while Fedora Project developers may
- often be found on the <code>#fedora-devel</code> channel. Some of
- the larger projects may have their own channels as well. This
- information may be found on the webpage for the project, and at
- <ulink url='http://fedoraproject.org/wiki/Communicate'/>.
+ Fedora Project participants frequent the
+ <systemitem>#fedora</systemitem> channel on the Freenode network,
+ while Fedora Project developers may often be found on the
+ <systemitem>#fedora-devel</systemitem> channel. Some of the larger
+ projects may have their own channels as well. This information may
+ be found on the webpage for the project, and at <ulink
+ url='http://fedoraproject.org/wiki/Communicate'/>.
</para>
<para>
- In order to talk on the <code>#fedora</code> channel, you need
- to register your nickname, or <emphasis>nick</emphasis>.
- Instructions are given when you <code>/join</code> the channel.
+ In order to talk on the <systemitem>#fedora</systemitem> channel,
+ you need to register your nickname, or <firstterm>nick</firstterm>.
+ Instructions are given when you <command>/join</command> the
+ channel.
</para>
<para>
@@ -112,3 +112,10 @@
</note>
</para>
</section>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
Index: Security.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Security.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- Security.xml 25 Sep 2006 11:57:56 -0000 1.10
+++ Security.xml 26 Sep 2006 01:27:15 -0000 1.11
@@ -5,8 +5,6 @@
<section id="sn-Security">
<title>Security</title>
-<!--RAW HTML: <h2>Security</h2>-->
-
<para>
This section highlights various security items from Fedora Core.
</para>
@@ -23,14 +21,13 @@
<title>SELinux</title>
<para>
This release increases usability of SELinux by providing a
- graphical troubleshooting tool,
- <ulink url='http://fedoraproject.org/wiki/SELinux/setroubleshoot'>setroubleshoot</ulink>.
- SELinux developer Dan Walsh explains the tool and its usage in
- his
- <ulink url='http://danwalsh.livejournal.com/7212.html'>blog</ulink>.
- The <emphasis role='strong'>Nautilus</emphasis> file manager
- has also been improved in GNOME 2.16 to display SELinux
- contexts.
+ graphical troubleshooting tool, <ulink
+ url='http://fedoraproject.org/wiki/SELinux/setroubleshoot'>setroubleshoot</ulink>.
+ SELinux developer Dan Walsh explains the tool and its usage in his
+ <ulink
+ url='http://danwalsh.livejournal.com/7212.html'>blog</ulink>.
+ The <application>Nautilus</application> file manager has also been
+ improved in GNOME 2.16 to display SELinux contexts.
</para>
<para>
The SELinux project pages have troubleshooting tips,
@@ -71,3 +68,10 @@
</itemizedlist>
</section>
</section>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
Index: Virtualization.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Virtualization.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- Virtualization.xml 25 Sep 2006 12:01:30 -0000 1.9
+++ Virtualization.xml 26 Sep 2006 01:27:15 -0000 1.10
@@ -5,8 +5,6 @@
<section id="sn-Virtualization">
<title>Virtualization</title>
-<!--RAW HTML: <h2>Virtualization</h2>-->
-
<para>
Virtualization in Fedora Core is based on Xen 3.0.2, and is
integrated within the Fedora Core 6 installer. Refer to
@@ -45,30 +43,31 @@
<para>
In Fedora Core 6 a single kernel supports both the host and the
guest operating systems. In previous versions, there was one
- kernel, <code>kernel-xenU</code>, for the host or hypervisor and a
- separate kernel, <code>kernel-xen0</code>, for the guests. In
- Fedora Core 6 the <code>kernel-xen</code> package is the only
- kernel needed.
+ kernel, <package>kernel-xenU</package>, for the host or hypervisor
+ and a separate kernel, <package>kernel-xen0</package>, for the
+ guests. In Fedora Core 6 the <package>kernel-xen</package> package
+ is the only kernel needed.
</para>
<para>
- Fedora Core 6 introduces <code>virt-manager</code>, a GUI
+ Fedora Core 6 introduces <command>virt-manager</command>, a GUI
application for installing and managing virtual machines. Features
- of <code>virt-manager</code> include:
+ of <command>virt-manager</command> include:
</para>
<itemizedlist>
<listitem>
<para>
Integrated graphical framebuffer. Both the GUI installer and
- the guest operating system's graphical environment can be
- accessed from <code>virt-manager</code> without the need for
- VNC.
+ the guest operating system's graphical environment can be
+ accessed from <application>virt-manager</application> without
+ the need for VNC.
</para>
</listitem>
<listitem>
<para>
An embedded serial console viewer. The console can now be
- accessed from <code>virt-manager</code> without opening a
- separate terminal and using <code>xm console</code>.
+ accessed from <application>virt-manager</application> without
+ opening a separate terminal and using <command>xm
+ console</command>.
</para>
</listitem>
<listitem>
@@ -80,15 +79,17 @@
<listitem>
<para>
Extended RFB protocol handler. If the guest operating system
- changes screen resolution, the <code>virt-manager</code>
- graphical console adjusts its size accordingly.
+ changes screen resolution, the
+ <application>virt-manager</application> graphical console
+ adjusts its size accordingly.
</para>
</listitem>
</itemizedlist>
<para>
In Fedora Core 6 there are two methods to install a guest OS: via
- the command line using the <code>xenguest-install</code> program,
- or via the GUI application <code>virt-manager</code>.
+ the command line using the <command>xenguest-install</command>
+ program, or via the GUI application
+ <application>virt-manager</application>.
</para>
<itemizedlist>
<listitem override='none'>
@@ -102,8 +103,9 @@
</listitem>
</itemizedlist>
<para>
- Xen log messages are stored under <code>/var/log/xen</code>, which
- separates Xen related log messages from other system messages.
+ Xen log messages are stored under <filename
+ class="directory">/var/log/xen</filename>, which separates Xen
+ related log messages from other system messages.
</para>
<itemizedlist>
<listitem override='none'>
@@ -118,3 +120,10 @@
</itemizedlist>
</section>
</section>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
Index: WebServers.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/WebServers.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- WebServers.xml 25 Sep 2006 12:18:37 -0000 1.8
+++ WebServers.xml 26 Sep 2006 01:27:15 -0000 1.9
@@ -8,10 +8,18 @@
<!--RAW HTML: <h2>Web Servers</h2>-->
<para>
- Fedora Core 6 includes version 2.2 of the Apache HTTP Server. Users
- upgrading from version 2.0 (included in Fedora Core 4 and earlier) need to
- make changes to their <command>httpd</command> configuration; refer to
- <ulink url='http://httpd.apache.org/docs/2.2/upgrading.html'/> for more
+ Fedora Core 6 includes version 2.2 of the <application>Apache HTTP
+ Server</application>. Users upgrading from version 2.0 (included
+ in Fedora Core 4 and earlier) need to make changes to their
+ <command>httpd</command> configuration; refer to <ulink
+ url='http://httpd.apache.org/docs/2.2/upgrading.html'/> for more
details.
</para>
</section>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
Index: Welcome.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Welcome.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- Welcome.xml 24 Sep 2006 20:41:50 -0000 1.8
+++ Welcome.xml 26 Sep 2006 01:27:15 -0000 1.9
@@ -5,11 +5,9 @@
<section id="sn-Welcome">
<title>Welcome to Fedora Core</title>
-<!--RAW HTML: <h2>Welcome to Fedora Core</h2>-->
-
<itemizedlist>
<listitem override='none'>
-<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
+
<para>
Fedora is a set of projects sponsored by Red Hat and guided by
the contributors. These projects are developed by a large
@@ -26,9 +24,9 @@
<tip>
<title>Latest Release Notes on the Web</title>
<para>
- These release notes may be updated. Visit
- http://fedora.redhat.com/docs/release-notes/ to view the latest
- release notes for Fedora Core 6.
+ These release notes may be updated. Visit <ulink
+ url="http://fedora.redhat.com/docs/release-notes/"/> to view the
+ latest release notes for Fedora Core 6.
</para>
</tip>
</para>
Index: Xorg.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Xorg.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- Xorg.xml 25 Sep 2006 12:04:57 -0000 1.10
+++ Xorg.xml 26 Sep 2006 01:27:15 -0000 1.11
@@ -15,12 +15,12 @@
<section>
<title>X Configuration Changes</title>
<para>
- The <emphasis role='strong'>X.org 7.1</emphasis> X server has been
+ The <application>X.org 7.1</application> X server has been
modified to automatically detect and configure most hardware,
eliminating the need for users or administrators to modify the
- <code>/etc/X11/xorg.conf</code> configuration file. The only
- hardware configured by default in the <code>xorg.conf</code> file
- written by anaconda is:
+ <filename>/etc/X11/xorg.conf</filename> configuration file. The
+ only hardware configured by default in the
+ <filename>xorg.conf</filename> file written by anaconda is:
</para>
<itemizedlist>
<listitem>
@@ -42,54 +42,72 @@
The X server queries the attached monitor for supported
resolution ranges, and attempts to pick the highest resolution
available with the correct aspect ratio for the display. Users can
- set their preferred resolution in <emphasis>System > Preferences
- > Screen Resolution</emphasis>, and the default resolution for
- the system can be changed with <emphasis>System > Administration
- > Display</emphasis>.
+ set their preferred resolution in <menuchoice>
+ <guimenu>System</guimenu>
+ <guisubmenu>Preferences</guisubmenu>
+ <guimenuitem>Screen Resolution</guimenuitem></menuchoice>,
+ and the default resolution for
+ the system can be changed with <menuchoice>
+ <guimenu>System</guimenu>
+ <guisubmenu>Administration</guisubmenu>
+ <guimenuitem>Display</guimenuitem></menuchoice>.
</para>
<para>
- If the <code>/etc/X11/xorg.conf</code> configuration file is not
- present, X also automatically detects the appropriate driver,
- and assumes a 105-key US keyboard layout.
+ If the <filename>/etc/X11/xorg.conf</filename> configuration file
+ is not present, X also automatically detects the appropriate
+ driver, and assumes a 105-key US keyboard layout.
</para>
</section>
<section>
<title>Intel Driver notes</title>
<para>
- Fedora Core
-<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
- 6 contains two drivers for Intel integrated graphics controllers:
+ Fedora Core 6 contains two drivers for Intel integrated graphics
+ controllers:
</para>
<itemizedlist>
<listitem>
<para>
- The default <code>i810</code> driver, which contains support
- for Intel graphics chipsets up to and including i945 and i965
+ The default <systemitem>i810</systemitem> driver, which
+ contains support for Intel graphics chipsets up to and
+ including i945 and i965
</para>
</listitem>
<listitem>
<para>
- The experimental <code>intel</code> driver, which contains
- support for Intel graphics chipsets up to and including i945
+ The experimental <systemitem>intel</systemitem> driver, which
+ contains support for Intel graphics chipsets up to and
+ including i945
</para>
</listitem>
</itemizedlist>
<para>
- The <code>i810</code> driver is limited to resolutions available
- in the BIOS. If you need support for non-standard resolutions,
- such as those used in some widescreen displays, you may want to
- switch to the <code>intel</code> driver. You may switch drivers by
- using <code>system-config-display</code>, available in the menus
- under <emphasis>System > Administration > Display</emphasis>.
- </para>
- <para>
- We welcome feedback on the experimental <code>intel</code> driver.
- Please report success in
- <ulink url='http://bugzilla.redhat.com/bugzilla/'>Bugzilla</ulink>,
- attaching the full output of <code>lspci -vn</code> for your
+ The <systemitem>i810</systemitem> driver is limited to resolutions
+ available in the BIOS. If you need support for non-standard
+ resolutions, such as those used in some widescreen displays, you
+ may want to switch to the <systemitem>intel</systemitem> driver.
+ You may switch drivers by using
+ <systemitem>system-config-display</systemitem>, available in the
+ menus under <menuchoice>
+ <guimenu>System</guimenu>
+ <guisubmenu>Administration</guisubmenu>
+ <guimenuitem>Display</guimenuitem></menuchoice>.
+ </para>
+ <para>
+ We welcome feedback on the experimental
+ <systemitem>intel</systemitem> driver. Please report success in
+ <ulink
+ url='http://bugzilla.redhat.com/bugzilla/'>Bugzilla</ulink>,
+ attaching the full output of <command>lspci -vn</command> for your
machine. Given success reports, various chipsets may be switched
- to use the <code>intel</code> driver by default.
+ to use the <systemitem>intel</systemitem> driver by default.
</para>
</section>
</section>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
More information about the Fedora-docs-commits
mailing list