release-notes desktop-en.xml, 1.2, 1.3 development-tools-en.xml, 1.2, 1.3 entertainment-en.xml, 1.1, 1.2 fedora.css, 1.2, 1.3 file-servers-en.xml, 1.2, 1.3 i18n-en.xml, 1.1, 1.2 install-notes-en.xml, 1.3, 1.4 kernel-en.xml, 1.2, 1.3 multimedia-en.xml, 1.3, 1.4 project-overview-en.xml, 1.1, 1.2
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Wed Nov 23 05:38:33 UTC 2005
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8043
Modified Files:
desktop-en.xml development-tools-en.xml entertainment-en.xml
fedora.css file-servers-en.xml i18n-en.xml
install-notes-en.xml kernel-en.xml multimedia-en.xml
project-overview-en.xml
Log Message:
Past the kernel beat, in alpha order, snapshot of what has been updated from the wiki for fc5test1.
Index: desktop-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/desktop-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- desktop-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ desktop-en.xml 23 Nov 2005 05:38:24 -0000 1.3
@@ -3,70 +3,88 @@
<itemizedlist>
<title>Notes</title>
<listitem>
- <para>GNOME 2.12 and KDE 3.4.2 Major highlight
+ <para>GNOME 2.12 and KDE 3.4.2 are included in &FC; &FCVER;.
</para>
</listitem>
<listitem>
- <para>The current test release has GNOME 2.12.1, together with
- some previews of technology from the forthcoming GNOME 2.14:
+ <para>This test release has GNOME 2.12.1, together with some
+ previews of technology from the forthcoming GNOME 2.14. Feedback
+ on these packages is especially appreciated.
</para>
<itemizedlist>
<listitem>
- <para>gnome-power-manager: brings the Hardware Abstraction
- Layer to the world of laptop batteries and UPS units - these
- things should "Just Work", with a simple UI (naturally, in
- a test release, they might not)
+ <para><filename>gnome-power-manager</filename>:
+ <application>GNOME Power Manager </application> is a session
+ daemon for the GNOME desktop environment that makes it easy
+ to manage power on your laptop or desktop system. It takes
+ advantage of HAL (which provides a hardware abstraction
+ layer) and DBUS (Inter Process Communication software)
+ written and maintained by &FC; developers.
</para>
</listitem>
<listitem>
- <para>gnome-screensaver: giving a fresh UI to screensavers and
- the <guilabel>Lock Screen</guilabel> dialog
+ <para><filename>gnome-screensaver</filename>: Provides a
+ integrated user interface to screensavers and the lock
+ screen dialog.
</para>
</listitem>
<listitem>
- <para>Memory optimizations in the fontconfig and
- shared-mime-info packages (these now use shared
- memory-mapped caches for this data). Both of these caches
- are still somewhat experimental.
+ <para>Memory optimizations in the
+ <filename>fontconfig</filename> and
+ <filename>shared-mime-info</filename> packages. These now
+ use shared memory-mapped caches for this data.
</para>
</listitem>
</itemizedlist>
</listitem>
- <para>
- Test feedback on these experimental packages is especially
- appreciated.
- </para>
- <para>
- GNOME 2.12 has removed the terminal option from the desktop root
- menu. nautilus-open-terminal in Fedora Extras repository provides a
- enhanced replacement. It is also mentioned in the GNOME 2.12 release
- notes itself but we might highlight it since the package is provided
- with the extras repository.
- </para>
- <para>
- Screensavers not installed by default anymore. Should explain why
- and provide commands to install them.
- </para>
- <para>MCS SELinux is in rawhide. Major highlight
- (<emphasis>tentative</emphasis> - not sure about classification of
- this change)
- </para>
- <caution>
- <title>OpenOffice and upgrading from test releases</title>
- <para>
- If you choose to go counter to the recommendation to <emphasis
- role='strong'>not</emphasis> upgrade from a previous test
- release, you may encounter a problem with <ulink
- url='/OpenOffice'>OpenOffice</ulink> following the upgrade.
- </para>
- <para>
- To resolve this, you must do the following command <emphasis
- role='strong'>before</emphasis> doing the upgrade:
- </para>
+ <listitem>
+ <para>GNOME 2.12 has removed the
+ <guimenuitem>terminal</guimenuitem> option from the desktop
+ context menu. The package
+ <filename>nautilus-open-terminal</filename> in &FEX;
+ repository provides an enhanced replacement for those who require
+ it. You can install it using the following command:
+ </para>
<screen>
-<command>rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
+<command>yum install nautilus-open-terminal</command>
</screen>
- </caution>
+ </listitem>
+ <listitem>
+ <para>Only the blank screensavers is installed by default, since
+ &FC; 4.
+ </para>
+ <para>
+ The primary issue is that some screensavers are known to not
+ work correctly or abruptly terminate the graphical interface.
+ This is particularly true for some of the OpenGL animated ones
+ provided within <filename></filename>xscreensaver-gl-extras
+ package.
+ </para>
+ <para>
+ In addition, the material content of the screensavers is
+ sometimes controversial or causes strong reactions. It is
+ better, for the user experience, to not be surprised by the
+ nature of the screensavers.
+ </para>
+ <para>
+ Users who want the screensavers package can install it using the following
+ command.
+ </para>
+<screen>
+<command>yum install xscreensaver-extras xscreensaver-gl-extras</command>
+</screen>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <title>Mouse configuration utility has changed</title>
+ <para>
+ The configuration utility
+ <application>system-config-mouse</application> has been dropped
+ from this release since synaptic and 3 button mouse configuration
+ is being done automatically during installation. Serial mice are
+ not formally supported in &FC; anymore.
+ </para>
+ </note>
</section>
<!--
Local variables:
Index: development-tools-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/development-tools-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- development-tools-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ development-tools-en.xml 23 Nov 2005 05:38:24 -0000 1.3
@@ -9,11 +9,39 @@
]>
-->
-<!-- Content commented out, no update performed by beat writer yet.
<section id="sn-devel">
<title>
Development Tools
</title>
+ <section id="sn-java-development">
+ <title>Java-like Environment</title>
+ <para>A Java-like free and open source environment is available
+ within the &FC; &FCVER; release.
+ </para>
+ <para>
+ It has three components: GNU Java runtime
+ (<filename>libgcj</filename>), the Eclipse Java compiler
+ (<command>ecj</command>), and a set of wrappers and links
+ (<filename>java-gcj-compat</filename>) that present the runtime
+ and compiler to the user in the same way as other Java
+ environments are presented.
+ </para>
+ <para>
+ Several major software packages such as Openoffice.org Base,
+ Eclipse, and Apache Tomcat, as well as several other Java software
+ packages included in this release, are compatible with this
+ environment.
+ </para>
+ <para>
+ For more information, refer to the FAQ:
+ </para>
+ <para>
+ <ulink
+ url='http://www.fedoraproject.org/wiki/JavaFAQ'>http://www.fedoraproject.org/wiki/JavaFAQ</ulink>
+ </para>
+ </section>
+
+<!-- Content commented out, no update performed by beat writer yet.
<section id="sn-devel-gcc">
<title>GCC Compiler Collection</title>
<para>
@@ -176,8 +204,9 @@
</listitem>
</itemizedlist>
</section>
-</section>
-->
+</section>
+
<!--
Local variables:
Index: entertainment-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/entertainment-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- entertainment-en.xml 25 Oct 2005 08:34:00 -0000 1.1
+++ entertainment-en.xml 23 Nov 2005 05:38:24 -0000 1.2
@@ -2,7 +2,7 @@
<title>Games and Entertainment</title>
<para>
&FC; and &FEX; provide a selection of games that cover a variety of
- genres. By default, &FC;includes a small package of games for GNOME
+ genres. By default, &FC; includes a small package of games for GNOME
(called <filename>gnome-games</filename>). For a list of other
games that are available for installation through
<command>yum</command>, open a terminal and enter the following
Index: fedora.css
===================================================================
RCS file: /cvs/docs/release-notes/fedora.css,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora.css 25 Oct 2005 02:48:50 -0000 1.2
+++ fedora.css 23 Nov 2005 05:38:24 -0000 1.3
@@ -132,3 +132,7 @@
/* prevent inheritance */
margin-bottom: 0em;
}
+
+p.title {
+ text-align: center;
+}
Index: file-servers-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/file-servers-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- file-servers-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ file-servers-en.xml 23 Nov 2005 05:38:24 -0000 1.3
@@ -24,12 +24,18 @@
<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>
+ <caution>
+ <title>Take care when upgrading Netatalk versions</title>
+ <para>
+ Upgrading from Netatalk version 1 to version 2 may result in
+ data loss.
+ </para>
+ </caution>
+ <para>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. Read the documentation and
+ plan your migration before upgrading.
</para>
<para>
Upgrade information is available directly from the Netatalk
Index: i18n-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/i18n-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- i18n-en.xml 25 Oct 2005 08:34:00 -0000 1.1
+++ i18n-en.xml 23 Nov 2005 05:38:24 -0000 1.2
@@ -9,100 +9,13 @@
This section includes information related to the support of
various languages under &DISTRO;.
</para>
- <section>
- <title>The IIIMF Input System</title>
+ <note>
+ <title>IIIMF replaced</title>
<para>
- IIIMF is the Internet/Intranet Input Method Framework. In &FC;
- &LOCALVER; the <filename>iiimf</filename> package is updated to
- version 12.2.
+ SCIM has replaced IIIMF in Fedora Core in this
+ release.
</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>
+ </note>
</section>
</section>
<!--
Index: install-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- install-notes-en.xml 25 Oct 2005 09:07:12 -0000 1.3
+++ install-notes-en.xml 23 Nov 2005 05:38:24 -0000 1.4
@@ -8,16 +8,17 @@
<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.
+ 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 2GiB in size. For example,
+ <command>wget</command> before version 1.9.1.16 in exits 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.
+ The <command>wget</command> version 1.9.1-16 and lter,
+ <command>curl</command> and <command>ncftpget</command> file
+ downloading tools do not have this limitation, and can
+ successfully download files larger than 2GiB.
</para>
<para>
Bittorrent is another method for downloading large files. For
@@ -31,7 +32,7 @@
</note>
<section id="sn-install-notes-ppc">
<title>PPC Installation Notes</title>
- <section>
+ <section id="sn-ppc-hardware-reqs">
<title>PPC Hardware Requirements</title>
<para>
This section lists the minimum PowerPC (PPC) hardware needed
@@ -42,8 +43,9 @@
<para>Minimum: PowerPC G3 / POWER4 </para>
</listitem>
<listitem>
- <para>&DISTRO; &DISTROVER; supports only the “New World†generation
- of Apple Power Macintosh, shipped circa 1999 onwards.
+ <para>&DISTRO; &DISTROVER; supports only the “New Worldâ€
+ generation of <trademark class="trade">Apple</trademark>
+ Power Macintosh, shipped circa 1999 onwards.
</para>
</listitem>
<listitem>
@@ -51,11 +53,11 @@
RS/6000, and Genesi Pegasos II machines.</para>
</listitem>
<listitem>
- <para>Recommended for text-mode: 233 MHz G3 or better, 64MB
+ <para>Recommended for text-mode: 233 MHz G3 or better, 64MiB
RAM.</para>
</listitem>
<listitem>
- <para>Recommended for graphical: 400 MHz G3 or better, 128MB
+ <para>Recommended for graphical: 400 MHz G3 or better, 128MiB
RAM.</para>
</listitem>
</itemizedlist>
@@ -63,23 +65,22 @@
The DVD or first CD of the installation set of &FC; is set to be
bootable on supported hardware. In addition, bootable CD images
can be found in the <filename>images/</filename> directory of
- the DVD or first CD. These will behave differently according to
- the hardware:
+ the DVD or first CD. These behave differently according to the
+ hardware:
</para>
<variablelist>
<title>Boot Image Behavior by Hardware</title>
<varlistentry>
<term>Apple Macintosh </term>
<listitem>
- <para>The bootloader should automatically boot the
- appropriate 32-bit or 64-bit installer. Power management
- support, including sleep and backlight level management,
- is present in the <filename>apmud</filename> package,
- which is in &FEX;. &FEX; for &FC; is configured by default
- for yum. Following installation,
- <filename>apmud</filename> can be installed by running the
- command <command>yum install apmud</command> in a
- terminal.
+ <para>The bootloader automatically boots the appropriate
+ 32-bit or 64-bit installer. Power management support,
+ including sleep and backlight level management, is present
+ in the <filename>apmud</filename> package, which is in
+ &FEX;. &FEX; for &FC; is configured by default for yum.
+ Following installation, <filename>apmud</filename> can be
+ installed by running the command <command>yum install
+ apmud</command> in a terminal.
</para>
</listitem>
</varlistentry>
@@ -87,8 +88,8 @@
<term>64-bit IBM eServer pSeries (POWER4/POWER5)</term>
<listitem>
<para>After using OpenFirmware to boot the CD, the
- bootloader (<command>yaboot</command>) should
- automatically boot the 64-bit installer.
+ bootloader (<command>yaboot</command>) automatically boots
+ the 64-bit installer.
</para>
</listitem>
</varlistentry>
@@ -114,11 +115,11 @@
<command>boot cd: /images/netboot/ppc32.img</command>
</screen>
<para>
- You will also need to configure OpenFirmware on the
- Pegasos manually to make the installed &FC; system
- bootable. To do this, you need to set the
- <envar>boot-device</envar> and <envar>boot-file</envar>
- environment variables appropriately.
+ You also need to configure OpenFirmware on the Pegasos
+ manually to make the installed &FC; system bootable. To do
+ this, you need to set the <envar>boot-device</envar> and
+ <envar>boot-file</envar> environment variables
+ appropriately.
</para>
</listitem>
</varlistentry>
@@ -126,12 +127,13 @@
<term>Network booting</term>
<listitem>
<para>There are combined images containing the installer
- kernel and ramdisk in the images/netboot/ directory of the
+ kernel and ramdisk in the
+ <filename>images/netboot/</filename> directory of the
install tree. These are intended for network booting with
TFTP, but can be used in many ways.
</para>
<para>
- The command <command>yaboot</command> supports tftp
+ The command <command>yaboot</command> supports TFTP
booting for IBM eServer pSeries and Apple Macintosh. &FED;
recommends using yaboot over the netboot images.
</para>
@@ -140,7 +142,7 @@
</variablelist>
</section>
</section>
- <section>
+ <section id="sn-anaconda-notes">
<title>Anaconda Notes</title>
<itemizedlist>
@@ -175,10 +177,6 @@
</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
@@ -201,16 +199,70 @@
<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
+ the installer image in RAM, only systems with more than 128MiB
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
+ with 128MiB of RAM or less must continue to use the text-based
installer.
</para>
</listitem>
</itemizedlist>
</section>
- <section>
+ <section id="sn-installer-changes">
+ <title>Changes In The Installer</title>
+ <itemizedlist>
+ <listitem>
+ <para>Support has been added for <command>yum</command> as the
+ dependancy solver backend for software packages has been
+ added. Additional repositories are expected to be supported
+ during installation in a future release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>In this release, the installer checks the hardware
+ capability and installs either the uniprocessor or SMP
+ (Symmetric Multi Processor) kernel, as appropriate. Previous
+ releases installed both the variants and used the appropriate
+ one as default.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Partition setting has been reworked to be more user
+ friendly.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Remote logging via <command>syslog</command> is supported
+ in this release. To enable, pass
+ <option>syslog=host:port</option> at the boot prompt.
+ Specifying the port is optional.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Firewall/SELinux configuration has been moved to the final
+ installation phase called
+ <application>firstboot</application>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Rendering of HTML pages during install is now done using
+ the <command>gtkhtml</command> widget for better capability.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Kickstart has been refactored into its own package -
+ <filename>pykickstart</filename> - containing parser and
+ writers. As a result of this change, validation and extension
+ of kickstart is now much easier.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Serial mice are no long formally supported in the
+ installer nor in &FC;. </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="sn-install-related-issues">
<title>Installation-Related Issues</title>
<itemizedlist>
<listitem>
@@ -221,7 +273,6 @@
the installation, and add the "<command>nofb</command>" option
to the boot command line.
</para>
-
<note>
<title>Note</title>
<para>
Index: kernel-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/kernel-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- kernel-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ kernel-en.xml 23 Nov 2005 05:38:24 -0000 1.3
@@ -12,298 +12,258 @@
]>
-->
<section id="sn-kernel">
- <title>
- Linux Kernel
- </title>
- <section id="sn-kernel-lotsa">
+ <title>Linux Kernel</title>
+ <section id="sn-kernel-version">
<title>Version</title>
<para>
- The distribution is based on the 2.6 series of the Linux kernel. &FC; may include
- additional patches for improvements, bug fixes, or additional
- features. For this reason, the &FC; kernel may not be
- line-for-line equivalent to the vanilla<firstterm></firstterm> kernel from the
- <ulink
- url="http://www.kernel.org"><filename>kernel.org</filename></ulink>
+ This distribution is based on the 2.6 series of the Linux kernel.
+ &FC; may include patches for improvements, bug fixes, or
+ additional features. For this reason, the &FCl kernel may not be
+ line-for-line equivalent to the <firstterm>vanilla
+ kernel</firstterm> from the <ulink
+ url='http://www.kernel.org/'>http://www.kernel.org/</ulink>
website.
</para>
<para>
- You may obtain a list of any such patches by using the command on the &FC; package:
- </para>
-<screen width="56">
-<command>rpm <parameter class="option">-qpl</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
+ You may obtain a list of any such patches by using this command
+ on the &FC; package:</para>
+<screen>
+<command>rpm -qpl kernel-<version>.src.rpm</command>
</screen>
</section>
<section id="sn-kernel-flavors">
<title>Kernel Flavors</title>
- <para>
- &FC; includes the following kernel builds:
- </para>
+ <para>&FC; includes the following kernel builds: </para>
<itemizedlist>
<listitem>
- <para>Native kernel, in both uniprocessor and
- <abbrev>SMP</abbrev> varieties. Configured sources are
- available in the
+ <para>Native kernel, in both uniprocessor and SMP (Symmetric
+ Multi Processor) varieties. Configured sources are available
+ in the
<filename>kernel-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>
- package.
- </para>
+ package.
+ </para>
</listitem>
<listitem>
- <para>
- Virtual kernel for use with the <application>Xen</application>
- emulator package. Configured sources are available in the
+ <para>Virtual kernel for use with the Xen emulator package.
+ Configured sources are available in the
<filename>kernel-xen0-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>
- package.
- </para>
+ package. </para>
</listitem>
</itemizedlist>
<para>
Sources for both kernel flavors may be installed at the same time.
The files are installed into the
- <filename>/usr/src/kernels/<replaceable>version</replaceable>[-xen0]-<replaceable>arch</replaceable>/</filename>
- tree. Use the command:
- </para>
-<screen width="56">
-<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename></command>
-</screen>
- <para>
+ <filename>/usr/src/kernels/<replaceable>version</replaceable>[-xen0]-<replaceable>arch</replaceable>/</filename>
+ tree. Use the command <command>rpm -Uvh
+ kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</command>
as appropriate.
</para>
- <tip>
- <title>Following Generic Textbooks About the Linux Kernel</title>
+ <note>
+ <title>No separate SMP kernel for x86_64</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:
+ The default kernels in x86_64 architecture provide the SMP
+ capability. There is no seperate SMP kernel available for this
+ architecture in &FC; &FCVER;.
</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>
+ </note>
</section>
- <!--
- <tip>
- <title>Using <command>yum</command> to Remove Kernel
- Packages</title>
+ <section>
+ <title>Following Generic Textbooks</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.
+ 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 do this:
</para>
+<screen>
+<command>ln -s /usr/src/kernels/kernel-<replaceable>version</replaceable>-<replaceable>arch</replaceable> /usr/src/linux</command>
+</screen>
+ </section>
+ <section id="sn-kernel-dev">
+ <title>Preparing for Kernel Development</title>
<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.
+ &FC; &FCVER; 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 kernel <filename>.src.rpm</filename> package.
</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, the assumption is that you
+ <tip>
+ <title>Instructions refer to currently-running kernel</title>
+ <para>
+ To simplify the following directions, it is 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:
+ currently-running kernel. In the steps below, the phrase
+ <replaceable>version</replaceable> refers to the kernel version
+ shown by the command <command>uname -r</command>.
</para>
-<screen width="56">
-<command>uname <parameter class="option">-r</parameter></command>
-</screen>
- </important>
- <procedure id="sn-kernel-exploding-steps">
+ </tip>
+ <procedure>
<step>
- <para>
- Obtain the
+ <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>
-<!-- FIXME up2date is sorta deprecated for FC, how to do this with yum? -->
-<screen width="56">
-<command>up2date <parameter class="option">--get-source</parameter> <filename>kernel</filename></command>
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>The SRPMS directory on the appropriate SRPMS CD iso
+ image.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The FTP site where you got the kernel package.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Install by running this command:
+ </para>
+<screen>
+<command>yum install yum-utils yumdownloader --source kernel</command>
</screen>
- </listitem>
- </itemizedlist>
</step>
<step>
- <para>
- Install
+ <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
+ using the command <command>rpm -Uvh
+ kernel-<replaceable>version</replaceable>.src.rpm</command>.
+ </para>
+ <para>
+ This writes the RPM contents into
<filename>/usr/src/redhat/SOURCES</filename> and
<filename>/usr/src/redhat/SPECS</filename>.
- </para>
+ </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 is located in the
- <filename>/usr/src/redhat/BUILD/kernel-</filename><replaceable>version</replaceable>
+ <para>Prepare the kernel sources with these commands:
+ </para>
+<screen>
+<command>cd /usr/src/redhat/SPECS
+rpmbuild -bp --target $(arch) kernel-2.6.spec</command>
+</screen>
+ <para>
+ The kernel source tree is then located in the
+ <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable>/</filename>
directory. It is common practice to move the resulting
- <filename>linux-<replaceable>version</replaceable></filename>
- directory to the <filename>/usr/src</filename> tree; while not
- strictly necessary, doing so matches you with the
- generally-available documentation.
- </para>
-<screen width="56">
-<command>cd <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
-<command>mv <filename>linux-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
-<command>cd <filename>/usr/src</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>
+ <filename>linux-<replaceable>version</replaceable></filename> directory to the
+ <filename>/usr/src/</filename> tree; while not strictly
+ necessary, you can do this to match the generally-available kernel
+ documentation.
+ </para>
+<screen>
+<command>cd /usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable>
+mv linux-<replaceable>version</replaceable> /usr/src/
+cd /usr/src\
+ln -s ./linux-<replaceable>version</replaceable> linux
+cd /usr/src/linux</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
+ <para>
+ The configurations for the specific kernels shipped in &FC;
+ 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
+ file in the proper place for building: <command>cp
+ configs/<replaceable>desired-config-file</replaceable>
+ .config</command>
+ </para>
+ <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>
+ <filename>/lib/modules/<replaceable>version</replaceable>/build/.config</filename>
file.
- </para>
+ </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">
+ <para>
+ Every kernel gets a name based on its version number. This is
+ the value displayed by the command <command>uname
+ -r</command>. The kernel name is defined by the first four
+ lines of the kernel Makefile. To protect from mistakes, the
+ Makefile 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 Makefile.
+ </para>
+ <para>For example, if <command>uname -r</command> returns the string
+ <computeroutput>2.6.11-1.234_FC4</computeroutput>, change the
+ <envar>EXTRAVERSION</envar> definition from this:
+ </para>
+<screen>
EXTRAVERSION = -prep
</screen>
- <para>
+ <para>
to this:
</para>
-<screen width="60">
+<screen>
EXTRAVERSION = -1.234_FC4
</screen>
- <para>
- That is, substitute everything from the final dash onward.
- </para>
- </step>
+ <para>This represents everything from the final dash onward in the
+ package name.
+ </para>
+ </step>
<step>
- <para>
- Issue the following command:
- </para>
-<screen width="56">
+ <para>
+ Issue the following command:
+ </para>
+<screen>
<command>make oldconfig</command>
</screen>
- </step>
+ <para>You can then proceed as usual. </para></step>
</procedure>
- <para>
- You can then proceed as usual.
- </para>
</section>
- <section id="sn-kernel-3rdparty">
+ <section id="sn-kernel-modules-building">
<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
+ An exploded source tree is not required to build a kernel module,
+ such as your own device driver, against the currently in-use
+ kernel. 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">
+<screen>
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
+ndefault:
+ $(MAKE) -C $(KDIR) M=$(PWD) modules
+</screen>
+ <para>Issue the <command>make</command> command to build the
<filename>foo.ko</filename> module.
- </para>
+</para>
</section>
- <section id="sn-kernel-coop">
+ <section id="kernel-user-space-depencies">
<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
+ &PROD; &PRODVER; has support for clustered storage through the Red
+ Hat GFS file system. 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 cannot 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.
+ on the kernel package.
+ </para>
+ <para>
+ 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>
Index: multimedia-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/multimedia-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- multimedia-en.xml 25 Oct 2005 09:07:12 -0000 1.3
+++ multimedia-en.xml 23 Nov 2005 05:38:24 -0000 1.4
@@ -69,12 +69,8 @@
<para>
Several programs are excluded from &FC; and &FEX; due to licensing
issues. These include programs that provide MP3 and DVD support,
- Flash Player and Real Player. Users who wish to use these
- programs or restricted formats have to acquire additional
- packages from third-party repositories. Many of the multimedia
- applications in the Fedora repositories support plugins, so
- support for new formats can be easily added or removed. For more
- on this subject, please see:
+ Flash Player and Real Player. For more on this subject, please
+ refer to:
</para>
<para>
<ulink url='http://fedoraproject.org/wiki/ForbiddenItems'>http://fedoraproject.org/wiki/ForbiddenItems</ulink>
Index: project-overview-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/project-overview-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project-overview-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ project-overview-en.xml 23 Nov 2005 05:38:24 -0000 1.2
@@ -47,27 +47,35 @@
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>
+ <listitem>
+ <para>
+ fedora-ambassadors-list at redehat.com — For community
+ members who represent the &PROJ; in public.
+ </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>
+ <!-- Aren't we quite past this? Saving just in case we are not.
<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>
+ -->
+ <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
@@ -88,7 +96,7 @@
<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
+ Instructions are given when you first <command>/join</command> the
channel.
</para>
<note>
More information about the docs-commits
mailing list