release-notes/en Installer-en.xml, 1.1, 1.2 Kernel-en.xml, 1.1, 1.2 Legacy-en.xml, 1.1, 1.2 PackageChanges-en.xml, 1.1, 1.2 PackageNotesJava-en.xml, 1.1, 1.2 Security-en.xml, 1.1, 1.2
Paul W. Frields (pfrields)
fedora-docs-commits at redhat.com
Sat Feb 11 18:33:40 UTC 2006
Author: pfrields
Update of /cvs/docs/release-notes/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31840/en
Modified Files:
Installer-en.xml Kernel-en.xml Legacy-en.xml
PackageChanges-en.xml PackageNotesJava-en.xml Security-en.xml
Log Message:
Table sed hacks... these need to be checked for content formatting, but they should be valid
Index: Installer-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Installer-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Installer-en.xml 6 Feb 2006 20:35:09 -0000 1.1
+++ Installer-en.xml 11 Feb 2006 18:33:31 -0000 1.2
@@ -9,10 +9,10 @@
<para>This section outlines those issues that are related to Anaconda (the Fedora Core installation program) and installing Fedora Core in general. </para>
<itemizedlist>
<listitem>
- <table>
- <caption/>
- <tr>
- <td>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -24,31 +24,31 @@
</inlinemediaobject>
<emphasis role='strong'>Note</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para> If you intend to download the Fedora Core 5 Test 2 DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2GB in size. For example, wget before version 1.9.1-16 in Fedora will exit with a File size limit exceeded error. </para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para> Wget 1.9.1-16 and above, curl and ncftpget file downloading tools do not have this limitation, and can successfully download files larger than 2GB. </para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para>Bittorrent is another method for downloading large files. For information about obtaining and using the torrent file refer to this website: </para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para>
<ulink url='http://torrent.fedoraproject.org/'>http://torrent.fedoraproject.org/</ulink>
</para>
- </td>
- </tr>
- </table>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
</listitem>
</itemizedlist>
</section>
@@ -69,10 +69,10 @@
<para> Memory testing may be performed prior to installing Fedora Core by entering memtest86 at the boot: prompt. This causes the Memtest86 standalone memory testing software to run. Memtest86 memory testing continues until the Esc key is pressed. </para>
<itemizedlist>
<listitem>
- <table>
- <caption/>
- <tr>
- <td>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -84,14 +84,14 @@
</inlinemediaobject>
<emphasis role='strong'>Note</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para> You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to use this feature.</para>
- </td>
- </tr>
- </table>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
</listitem>
</itemizedlist>
</listitem>
@@ -144,10 +144,10 @@
<para> Certain hardware configurations (particularly those with LCD displays) may experience problems while starting the Fedora Core installation program. In these instances, restart the installation, and add the "nofb" option to the boot command line. </para>
<itemizedlist>
<listitem>
- <table>
- <caption/>
- <tr>
- <td>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -159,14 +159,14 @@
</inlinemediaobject>
<emphasis role='strong'>Note</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para> Chinese, Japanese, and Korean graphical installations started using the "nofb" option will start in English, and then switch to the appropriate language once the graphical phase of the installation process begins. </para>
- </td>
- </tr>
- </table>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
</listitem>
</itemizedlist>
</listitem>
@@ -190,10 +190,10 @@
<para> Before upgrading (or installing), back up the system completely. In particular, preserve <emphasis>/etc</emphasis>, <emphasis>/home</emphasis>, and possibly <emphasis>/opt</emphasis> and <emphasis>/usr/local</emphasis> if customized packages are installed there. Using a multi-boot approach with a "clone" of the old installation on alternate partition[s] as a fall-back might be considered. Creating alternate boot media, such as GRUB floppy would be advisable. </para>
<itemizedlist>
<listitem>
- <table>
- <caption/>
- <tr>
- <td>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -205,14 +205,14 @@
</inlinemediaobject>
<emphasis role='strong'>Note</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para> Backups of configurations in <emphasis>/etc</emphasis> are also very useful in reconstructing system settings after a fresh install.</para>
- </td>
- </tr>
- </table>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
</listitem>
</itemizedlist>
</listitem>
Index: Kernel-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Kernel-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Kernel-en.xml 6 Feb 2006 20:35:09 -0000 1.1
+++ Kernel-en.xml 11 Feb 2006 18:33:31 -0000 1.2
@@ -6,7 +6,7 @@
</articleinfo>
<section>
<title>Linux Kernel</title>
- <para>This section is for content related to the kernel. If you have a contribution for this release notes beat for Fedora Core, add it to this page or create a sub-page. If you have any questions about what content might be appropriate for this page or if a sub-page is needed, please contact <ulink url='/SamFolkWilliams'>SamFolkWilliams</ulink> or email the Fedora Documentation Project at <code>fedora-docs-list at redhat.com</code>. </para>
+ <para>This section is for content related to the kernel. If you have a contribution for this release notes beat for Fedora Core, add it to this page or create a sub-page. If you have any questions about what content might be appropriate for this page or if a sub-page is needed, please contact <ulink url='/SamFolkWilliams'>SamFolkWilliams</ulink> or email the Fedora Documentation Project at <command>fedora-docs-list at redhat.com</command>. </para>
<section>
<title>Version</title>
<para>This distribution is based on the 2.6 series of the Linux kernel. Fedora Core may include additional patches for improvements, bug fixes, or additional features. For this reason, the Fedora Core kernel may not be line-for-line equivalent to the so-called <emphasis>vanilla kernel</emphasis> from the kernel.org web site: </para>
@@ -39,19 +39,19 @@
<para>Fedora Core includes the following kernel builds: </para>
<itemizedlist>
<listitem>
- <para> Native kernel, in both uni-processor and SMP (Symmetric Multi-Processor) varieties. SMP kernels provide support for multiple CPU's or processors. Configured sources are available in the <code>kernel-[smp-]devel-<version>.<arch>.rpm</code> package. </para>
+ <para> Native kernel, in both uni-processor and SMP (Symmetric Multi-Processor) varieties. SMP kernels provide support for multiple CPU's or processors. Configured sources are available in the <command>kernel-[smp-]devel-<version>.<arch>.rpm</command> package. </para>
</listitem>
<listitem>
- <para> Virtual kernel hypervisor for use with the Xen emulator package. Configured sources are available in the <code>kernel-xen-hypervisor-devel-<version>.<arch>.rpm</code> package. </para>
+ <para> Virtual kernel hypervisor for use with the Xen emulator package. Configured sources are available in the <command>kernel-xen-hypervisor-devel-<version>.<arch>.rpm</command> package. </para>
</listitem>
<listitem>
- <para> Virtual kernel guest for use with the Xen emulator package. Configured sources are available in the <code>kernel-xen-guest-devel-<version>.<arch>.rpm</code> package. </para>
+ <para> Virtual kernel guest for use with the Xen emulator package. Configured sources are available in the <command>kernel-xen-guest-devel-<version>.<arch>.rpm</command> 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. </para>
+ <para> Kdump kernel for use with kexec/kdump capabilities. Configured sources are available in the <command>kernel-kdump-devel-<version>.<arch>.rpm</command> package. </para>
</listitem>
</itemizedlist>
- <para>Sources for all kernel flavors may be installed at the same time. The files will be installed into the <code>/usr/src/kernels/<version>[-xen-hypervisor/xen-guest/kdump]-<arch>/</code> tree. Use the command: </para>
+ <para>Sources for all kernel flavors may be installed at the same time. The files will be installed into the <command>/usr/src/kernels/<version>[-xen-hypervisor/xen-guest/kdump]-<arch>/</command> tree. Use the command: </para>
<itemizedlist>
<listitem>
<screen>rpm -Uvh kernel-[xen-hypervisor/xen-guest/kdump]-devel-<version>.<arch>.rpm</screen>
@@ -60,10 +60,10 @@
<para>as appropriate. </para>
<itemizedlist>
<listitem>
- <table>
- <caption/>
- <tr>
- <td>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -75,20 +75,20 @@
</inlinemediaobject>
<emphasis role='strong'>The default kernels in x86_64 architecture provide the SMP capability</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para> There is no separate SMP kernel available for this architecture in Fedora Core . </para>
- </td>
- </tr>
- </table>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
</listitem>
</itemizedlist>
</section>
<section>
<title>Following Generic Textbooks</title>
- <para>Many of the tutorials, examples, and textbooks about Linux kernel development assume the kernel sources are installed under the <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: </para>
+ <para>Many of the tutorials, examples, and textbooks about Linux kernel development assume the kernel sources are installed under the <command>/usr/src/linux/</command> 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: </para>
<itemizedlist>
<listitem>
<screen>ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src/linux</screen>
@@ -102,10 +102,10 @@
<para>To create an exploded source tree from this file, perform the following steps: </para>
<itemizedlist>
<listitem>
- <table>
- <caption/>
- <tr>
- <td>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -117,14 +117,14 @@
</inlinemediaobject>
<emphasis role='strong'>These Instructions Refer to the Currently-running Kernel</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
- <para> To simplify the following directions, we have assumed that you want to configure the kernel sources to match your currently-running kernel. In the steps below, you must understand that the phrase <version> refers to the kernel version shown by the command: <code>uname -r</code>. </para>
- </td>
- </tr>
- </table>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> To simplify the following directions, we have assumed that you want to configure the kernel sources to match your currently-running kernel. In the steps below, you must understand that the phrase <version> refers to the kernel version shown by the command: <command>uname -r</command>. </para>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
</listitem>
</itemizedlist>
<para>1. Obtain the kernel-<version>.src.rpm file from one of the following sources: </para>
@@ -140,34 +140,34 @@
<screen>yum install yum-utilsyumdownloader --source kernel</screen>
</listitem>
</itemizedlist>
- <para>2. Install <code>kernel-<version>.src.rpm</code> using the command: </para>
+ <para>2. Install <command>kernel-<version>.src.rpm</command> using the command: </para>
<itemizedlist>
<listitem>
<screen>rpm -Uvh kernel-<version>.src.rpm`</screen>
</listitem>
</itemizedlist>
- <para>This writes the RPM contents into <code>/usr/src/redhat/SOURCES</code> and <code>/usr/src/redhat/SPECS</code>. </para>
+ <para>This writes the RPM contents into <command>/usr/src/redhat/SOURCES</command> and <command>/usr/src/redhat/SPECS</command>. </para>
<para>3. Prepare the kernel sources using the commands: </para>
<itemizedlist>
<listitem>
<screen>cd /usr/src/redhat/SPECSrpmbuild -bp --target $(arch) kernel-2.6.spec</screen>
</listitem>
</itemizedlist>
- <para>The kernel source tree is then located in the <code>/usr/src/redhat/BUILD/kernel-<version>/</code> directory. It is common practice to move the resulting linux-<version> directory to the <code>/usr/src/</code> tree; while not strictly necessary, do this to match the generally-available documentation. </para>
+ <para>The kernel source tree is then located in the <command>/usr/src/redhat/BUILD/kernel-<version>/</command> directory. It is common practice to move the resulting linux-<version> directory to the <command>/usr/src/</command> tree; while not strictly necessary, do this to match the generally-available documentation. </para>
<itemizedlist>
<listitem>
<screen>cd /usr/src/redhat/BUILD/kernel-<version>mv linux-<version> /usr/src/cd /usr/srcln -s ./linux-<version> linuxcd /usr/src/linux</screen>
</listitem>
</itemizedlist>
- <para>4. The configurations for the specific kernels shipped in Fedora Core are in the configs/ directory. For example, the i686 SMP configuration file is named <code>configs/kernel-<version>-i686-smp.config</code>. Issue the following command to place the desired configuration file in the proper place for building: </para>
+ <para>4. The configurations for the specific kernels shipped in Fedora Core are in the configs/ directory. For example, the i686 SMP configuration file is named <command>configs/kernel-<version>-i686-smp.config</command>. Issue the following command to place the desired configuration file in the proper place for building: </para>
<itemizedlist>
<listitem>
<screen>cp configs/<desired-config-file> .config</screen>
</listitem>
</itemizedlist>
- <para>You can also find the <code>.config</code> file that matches your current kernel configuration in the <code>/lib/modules/<version>/build/.config</code> file. </para>
- <para>5. 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 Makefile. To protect the innocent, 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 the <code>uname -r</code> returns the string <code>2.6.11-1.234_FC4</code>, change the <code>EXTRAVERSION</code> definition from this: </para>
+ <para>You can also find the <command>.config</command> file that matches your current kernel configuration in the <command>/lib/modules/<version>/build/.config</command> file. </para>
+ <para>5. 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 Makefile. To protect the innocent, 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 the <command>uname -r</command> returns the string <command>2.6.11-1.234_FC4</command>, change the <command>EXTRAVERSION</command> definition from this: </para>
<itemizedlist>
<listitem>
<screen>EXTRAVERSION = -prep</screen>
@@ -190,17 +190,17 @@
</section>
<section>
<title>Building Only Kernel Modules</title>
- <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. For example, to build the <code>foo.ko</code> module, create the following Makefile in the directory containing the <code>foo.c</code> file: </para>
+ <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. For example, to build the <command>foo.ko</command> module, create the following Makefile in the directory containing the <command>foo.c</command> file: </para>
<itemizedlist>
<listitem>
<screen>obj-m := foo.oKDIR := /lib/modules/$(shell uname -r)/buildPWD := $(shell pwd)default:$(MAKE) -C $(KDIR) M=$(PWD) modules</screen>
</listitem>
</itemizedlist>
- <para>Issue the <code>make</code> command to build the <code>foo.ko</code> module. </para>
+ <para>Issue the <command>make</command> command to build the <command>foo.ko</command> module. </para>
</section>
<section>
<title>User Space Dependencies on the Kernel</title>
- <para>Fedora Core release has support for clustered storage through the Global File System (GFS). 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 <code>rpm -e kernel-<version></code> command as in earlier distributions because these user space packages depend on the kernel package. You may either list both the kernel package and all of its user space dependent packages on the <code>rpm -e</code> command, or you can use the <code>yum remove kernel-<version></code> command instead. The <code>yum</code> command automatically removes dependent packages, if necessary. </para>
+ <para>Fedora Core release has support for clustered storage through the Global File System (GFS). 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-<version></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 all of its user space dependent packages on the <command>rpm -e</command> command, or you can use the <command>yum remove kernel-<version></command> command instead. The <command>yum</command> command automatically removes dependent packages, if necessary. </para>
</section>
</section>
</article>
Index: Legacy-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Legacy-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Legacy-en.xml 6 Feb 2006 20:35:09 -0000 1.1
+++ Legacy-en.xml 11 Feb 2006 18:33:31 -0000 1.2
@@ -10,10 +10,10 @@
<title>Systemwide Search Changes</title>
<itemizedlist>
<listitem>
- <table>
- <caption/>
- <tr>
- <td>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -24,37 +24,37 @@
</textobject>
</inlinemediaobject>
<emphasis role='strong'>
- <code>Slocate</code> has been replaced with <code>mlocate</code> in this release</emphasis>
+ <command>Slocate</command> has been replaced with <command>mlocate</command> in this release</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
- <para> The <code>/usr/bin/{locate,updatedb}</code> implementation <code>slocate</code> was replaced by <code>mlocate</code>. </para>
- </td>
- </tr>
- </table>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para> The <command>/usr/bin/{locate,updatedb}</command> implementation <command>slocate</command> was replaced by <command>mlocate</command>. </para>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
</listitem>
<listitem>
- <para> The <code>locate</code> command should be completely compatible </para>
+ <para> The <command>locate</command> command should be completely compatible </para>
</listitem>
<listitem>
<para>
- <code>/etc/updatedb.conf</code> is compatible for correct configuration files </para>
+ <command>/etc/updatedb.conf</command> is compatible for correct configuration files </para>
</listitem>
<listitem>
- <para> Syntax errors that <code>slocate</code> would not detect are now reported </para>
+ <para> Syntax errors that <command>slocate</command> would not detect are now reported </para>
</listitem>
<listitem>
- <para> The <code>DAILY_UPDATE</code> variable is not supported </para>
+ <para> The <command>DAILY_UPDATE</command> variable is not supported </para>
</listitem>
<listitem>
- <para> The <code>updatedb</code> command is not compatible, custom scripts using <code>updatedb</code> might have to be changed. </para>
+ <para> The <command>updatedb</command> command is not compatible, custom scripts using <command>updatedb</command> might have to be changed. </para>
</listitem>
</itemizedlist>
<section>
<title>LinuxThreads No Longer Available</title>
- <para>The <code>LinuxThreads</code> library, which was deprecated in Fedora Core 4, is no longer available in this release. <code>NPTL</code> has been the default threading library since Red Hat Linux 9. </para>
+ <para>The <command>LinuxThreads</command> library, which was deprecated in Fedora Core 4, is no longer available in this release. <command>NPTL</command> has been the default threading library since Red Hat Linux 9. </para>
</section>
<section>
<title>Legacy Compatability Libraries</title>
Index: PackageChanges-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/PackageChanges-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- PackageChanges-en.xml 6 Feb 2006 20:35:09 -0000 1.1
+++ PackageChanges-en.xml 11 Feb 2006 18:33:31 -0000 1.2
@@ -14,10 +14,10 @@
<title>Package Change Details</title>
<itemizedlist>
<listitem>
- <table>
- <caption/>
- <tr>
- <td>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -28,17 +28,17 @@
</textobject>
</inlinemediaobject>
<emphasis role='strong'>
- <code>LinuxThreads</code> library is no longer available</emphasis>
+ <command>LinuxThreads</command> library is no longer available</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para>
- <code>LinuxThreads</code> was been deprecated in Fedora Core 4 and is no longer available in this release. NPTL, which has been the default threading library since Red Hat Linux 9, has replaced this completely. </para>
- </td>
- </tr>
- </table>
+ <command>LinuxThreads</command> was been deprecated in Fedora Core 4 and is no longer available in this release. NPTL, which has been the default threading library since Red Hat Linux 9, has replaced this completely. </para>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
</listitem>
</itemizedlist>
</section>
Index: PackageNotesJava-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/PackageNotesJava-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- PackageNotesJava-en.xml 6 Feb 2006 20:35:09 -0000 1.1
+++ PackageNotesJava-en.xml 11 Feb 2006 18:33:31 -0000 1.2
@@ -7,15 +7,15 @@
<section>
<title>Handling Java and Java-like Packages</title>
<para>Fedore Core includes a tool suite and execution environment based on free software technologies that is capable of building and running many useful programs written in the Java programming language, including the Eclipse IDE, Tomcat, and Open<emphasis role='strong'/>Office.org. </para>
- <para>In addition to the free software stack, Fedora Core is designed to let 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 <ulink url='http://www.jpackage.org'>JPackage Project's</ulink> packaging guidelines to take advantage of <code>alternatives</code>. </para>
- <para>Once installed properly, the root user should be able to switch between <code>java</code> and <code>javac</code> implementations using the <code>alternatives</code> command: </para>
+ <para>In addition to the free software stack, Fedora Core is designed to let 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 <ulink url='http://www.jpackage.org'>JPackage Project's</ulink> packaging guidelines to take advantage of <command>alternatives</command>. </para>
+ <para>Once installed properly, the root user should be able to switch between <command>java</command> and <command>javac</command> implementations using the <command>alternatives</command> command: </para>
<itemizedlist>
<listitem>
<screen>alternatives --config java alternatives --config javac</screen>
- <table>
- <caption/>
- <tr>
- <td>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -27,18 +27,18 @@
</inlinemediaobject>
<emphasis role='strong'>Fedora Core does not include the proprietary Sun Microsystems Java implementation</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para> Java is a trademark of Sun Microsystems. This entirely free software stack is <emphasis role='strong'>not</emphasis> Java but can run many programs written in Java. For more information, refer to the Java FAQ at <ulink url='http://fedoraproject.org/wiki/JavaFAQ'>http://fedoraproject.org/wiki/JavaFAQ</ulink>. </para>
- </td>
- </tr>
- </table>
- <table>
- <caption/>
- <tr>
- <td>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -50,18 +50,18 @@
</inlinemediaobject>
<emphasis role='strong'>When to use the JPackage Project RPM repository</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para> Fedora Core includes many packages derived from the excellent JPackage Project, which provides a Java software repository. Refer to <ulink url='http://jpackage.org'>http://jpackage.org</ulink> for more information on the Jpackage Project.These packages have been modified in Fedora to remove proprietary software dependencies and to make use of GCJ's ahead-of-time compilation feature. Fedora users should use the Fedora repositories for updates to these packages, and may use the JPackage repository for packages not provided by Fedora. </para>
- </td>
- </tr>
- </table>
- <table>
- <caption/>
- <tr>
- <td>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -71,16 +71,16 @@
<phrase>/!\</phrase>
</textobject>
</inlinemediaobject>
- <emphasis role='strong'>Do not simply add the JPackage repo to your <code>yum</code> configuration</emphasis>
+ <emphasis role='strong'>Do not simply add the JPackage repo to your <command>yum</command> configuration</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para> Understand better what you are doing if you plan on mixing packages from the Fedora and JPackage repos. Doing so may leave your system in a state that cannot be easily fixed. Be careful, and do research before you proceed. </para>
- </td>
- </tr>
- </table>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
</listitem>
</itemizedlist>
</section>
Index: Security-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Security-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Security-en.xml 6 Feb 2006 20:35:09 -0000 1.1
+++ Security-en.xml 11 Feb 2006 18:33:31 -0000 1.2
@@ -1,4 +1,4 @@
-||<?xml version='1.0' encoding='UTF-8'?>
+<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
@@ -9,10 +9,10 @@
<para>This section highlights various security items from Fedora Core. </para>
<itemizedlist>
<listitem>
- <table>
- <caption/>
- <tr>
- <td>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -25,15 +25,15 @@
<emphasis role='strong'>Comment for beat writer <ulink url='/JoshBressers'>JoshBressers</ulink>
</emphasis>
</para>
- </td>
- </tr>
- <tr>
- <td>
+ </entry>
+ </row>
+ <row>
+ <entry>
<para> fstack-protecter information was provided by Arjan. I will add more information on fortify source after reading up the relevant material. Should also add introductory information on SELinux, link to SELinux FAQ. Write about the various security features like /dev/mem restriction, Exec Shield, PIE, ELF hardening in <ulink url='/Security/Features'> Security Features</ulink> page and link from this section to provide a comprehensive overview of the security features available in addition to others like firewall or network services like sendmail only listening to localhost - <ulink url='/RahulSundaram'>RahulSundaram</ulink>
</para>
- </td>
- </tr>
- </table>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
</listitem>
</itemizedlist>
<section>
@@ -48,14 +48,14 @@
<section>
<title>PAM module Deprecation</title>
<para>
- <code>Pam_stack</code> is deprecated in this release. </para>
- <para>Linux-PAM 0.78 and later contains the include directive which obsoletes the <code>pam_stack</code> module. <code>pam_stack</code> module usage is logged with a deprecation warning. It might be removed in a future release. It must not be used in individual service configurations anymore. All packages in Fedora Core using PAM were modified so they do not use it. </para>
+ <command>Pam_stack</command> is deprecated in this release. </para>
+ <para>Linux-PAM 0.78 and later contains the include directive which obsoletes the <command>pam_stack</command> module. <command>pam_stack</command> module usage is logged with a deprecation warning. It might be removed in a future release. It must not be used in individual service configurations anymore. All packages in Fedora Core using PAM were modified so they do not use it. </para>
<itemizedlist>
<listitem>
- <table>
- <caption/>
- <tr>
- <td>
+ <table><title>FIXME</title><tgroup cols="1"><tbody>
+
+ <row>
+ <entry>
<para>
<inlinemediaobject>
<imageobject>
@@ -67,10 +67,10 @@
</inlinemediaobject>
<emphasis role='strong'>Upgraded installations using older PAM stacks need manual intervention</emphasis>
</para>
- </td>
- </tr>
- </table>
- <para> When a system is upgraded from previous Fedora Core releases and the system admininstrator previously modified some service configurations, those modified configuration files are not replaced when new packages are installed. Instead, the new configuration fiels are created as <code>.rpmnew</code> files. Such service configurations must be fixed so the <code>pam_stack</code> module is not used. Refer to the <code>.rpmnew</code> files for the actual changes needed. </para>
+ </entry>
+ </row>
+ </tbody></tgroup></table>
+ <para> When a system is upgraded from previous Fedora Core releases and the system admininstrator previously modified some service configurations, those modified configuration files are not replaced when new packages are installed. Instead, the new configuration fiels are created as <command>.rpmnew</command> files. Such service configurations must be fixed so the <command>pam_stack</command> module is not used. Refer to the <command>.rpmnew</command> files for the actual changes needed. </para>
<screen>diff -u /etc/pam.d/foo /etc/pam.d/foo.rpmnew</screen>
</listitem>
</itemizedlist>
@@ -83,8 +83,8 @@
</section>
<section>
<title>Buffer Overflow detection and variable reordering</title>
- <para>All of the software in Fedora Core and Extras software repository for this release is compiled using a security feature called <code>fstack-protecter</code>. <code>fstack-protector</code> puts a canary value on the stack of <emphasis>key</emphasis> functions, just before the return address and just before returning from that value. Then the canary value is verified, and if there was a buffer overflow, the canary will no longer match and the program aborts. The canary value is random for each time the application is started and makes it impossible to guess remotely. This is a security feature written by Red Hat developers as a rewritten implementation of the IBM <ulink url='http://www.research.ibm.com/trl/projects/security/ssp/'>ProPolice/SSP</ulink> feature and available as part of GCC 4.1 compiler used in Fedora Core . </para>
- <para>This is in addition to using <code>FORTIFY_SOURCE</code> from Fedora Core 4 onwards. </para>
+ <para>All of the software in Fedora Core and Extras software repository for this release is compiled using a security feature called <command>fstack-protecter</command>. <command>fstack-protector</command> puts a canary value on the stack of <emphasis>key</emphasis> functions, just before the return address and just before returning from that value. Then the canary value is verified, and if there was a buffer overflow, the canary will no longer match and the program aborts. The canary value is random for each time the application is started and makes it impossible to guess remotely. This is a security feature written by Red Hat developers as a rewritten implementation of the IBM <ulink url='http://www.research.ibm.com/trl/projects/security/ssp/'>ProPolice/SSP</ulink> feature and available as part of GCC 4.1 compiler used in Fedora Core . </para>
+ <para>This is in addition to using <command>FORTIFY_SOURCE</command> from Fedora Core 4 onwards. </para>
<para>
</para>
<para>
More information about the Fedora-docs-commits
mailing list