release-notes/en_US I18n.xml, 1.1, 1.2 Installer.xml, 1.2, 1.3 Security.xml, 1.1, 1.2 SecuritySELinux.xml, 1.1, 1.2 ServerTools.xml, 1.1, 1.2 SystemDaemons.xml, 1.1, 1.2 Virtualization.xml, 1.1, 1.2 WebServers.xml, 1.1, 1.2 Welcome.xml, 1.1, 1.2 Xorg.xml, 1.1, 1.2
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Sat Apr 15 01:02:22 UTC 2006
- Previous message: example-tutorial/en_US doc-entities.ent,1.1,NONE
- Next message: docs-common/common/entities entities-pl.ent, NONE, 1.1 entities-pl.xml, NONE, 1.1 pl.po, NONE, 1.1 Makefile, 1.19, 1.20
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Author: kwade
Update of /cvs/docs/release-notes/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22496
Modified Files:
I18n.xml Installer.xml Security.xml SecuritySELinux.xml
ServerTools.xml SystemDaemons.xml Virtualization.xml
WebServers.xml Welcome.xml Xorg.xml
Log Message:
The last of the fixes from the Wiki output plus a few typo fixes on my part; these now build en_US just fine.
Index: I18n.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/I18n.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- I18n.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ I18n.xml 15 Apr 2006 01:02:18 -0000 1.2
@@ -181,8 +181,6 @@
gconftool-2 --type bool --set \
'/desktop/gnome/interface/show_input_method_menu' true
</screen>
- </listitem>
- </itemizedlist>
</section>
<section>
Index: Installer.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/Installer.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Installer.xml 12 Apr 2006 13:34:18 -0000 1.2
+++ Installer.xml 15 Apr 2006 01:02:18 -0000 1.3
@@ -7,7 +7,7 @@
<title>Temp</title>
</articleinfo>
- <section>
+ <section id="sn-Installer">
<title>Installation-Related Notes</title>
<para>
Index: Security.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/Security.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Security.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ Security.xml 15 Apr 2006 01:02:18 -0000 1.2
@@ -7,7 +7,7 @@
<title>Temp</title>
</articleinfo>
- <section>
+ <section id="sn-Security">
<title>Security</title>
<para>
@@ -31,124 +31,108 @@
<title>PAM module Deprecation</title>
<para>
- <code>Pam_stack</code>
- is deprecated in this release. Linux-PAM 0.78 and later
- contains the
- <code>include</code>
- 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>
-
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/rightsidebar/img/idea.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase>(!)</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Upgrading and PAM
- Stacks</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <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 <emphasis>not</emphasis>
- replaced when new packages are installed. Instead,
- the new configuration files 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>
- </td>
- </tr>
- </table>\n<screen>diff -u /etc/pam.d/foo /etc/pam.d/foo.rpmnew\n</screen>
- </listitem>
- </itemizedlist>
-
- <para>
- The following example shows the
- <code>/etc/pam.d/login</code>
- configuration file in its original form using
- <code>pam_stack</code>
- , and then revised with the
- <code>include</code>
- directive.
- </para>
-
- <itemizedlist>
- <listitem>\n<screen>#%PAM-1.0\nauth required pam_securetty.so\nauth required pam_stack.so service=system-auth\nauth required pam_nologin.so\naccount required pam_stack.so service=system-auth\npassword required pam_stack.so service=system-auth\n# pam_selinux.so close should be the first session rule\nsession required pam_selinux.so close\nsession required pam_stack.so service=system-auth\nsession required pam_loginuid.so\nsession optional pam_console.so\n# pam_selinux.so open should be the last session rule\nsession required pam_selinux.so open\n</screen>\n<screen>#%PAM-1.0\nauth required pam_securetty.so\nauth include system-auth\n# no module should remain after 'include' if 'sufficient' might\n# be used in the included configuration file\n# pam_nologin moved to account phase - it's more appropriate there\n# other modules might be moved before the system-auth 'includ!
e'\naccount required pam_nologin.so\naccount include system-auth\npassword include system-auth\n# pam_selinux.so close should be the first session rule\nsession required pam_selinux.so close\nsession include system-auth\n# the system-auth config doesn't contain sufficient modules\n# in the session phase\nsession required pam_loginuid.so\nsession optional pam_console.so\n# pam_selinux.so open should be the last session rule\nsession required pam_selinux.so open\n</screen>
- </listitem>
- </itemizedlist>
+ <code>Pam_stack</code> is deprecated in this release. Linux-PAM 0.78
+ and later contains the <code>include</code> 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>
+
+ <tip>
+ <title>Upgrading and PAM Stacks</title>
+ <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
+ <emphasis>not</emphasis> replaced when new packages are installed.
+ Instead, the new configuration files 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>
+<screen>
+diff -u /etc/pam.d/foo /etc/pam.d/foo.rpmnew
+</screen>
+ </tip>
+
+ <para>
+ The following example shows the <code>/etc/pam.d/login</code>
+ configuration file in its original form using <code>pam_stack</code>,
+ and then revised with the <code>include</code> directive.
+ </para>
+
+<screen>#%PAM-1.0
+auth required pam_securetty.so
+auth required pam_stack.so service=system-auth
+auth required pam_nologin.so
+account required pam_stack.so service=system-auth
+password required pam_stack.so service=system-auth
+# pam_selinux.so close should be the first session rule
+session required pam_selinux.so close
+session required pam_stack.so service=system-auth
+session required pam_loginuid.so
+session optional pam_console.so
+# pam_selinux.so open should be the last session rule
+session required pam_selinux.so open
+</screen>
+<screen>
+#%PAM-1.0
+auth required pam_securetty.so
+auth include system-auth
+# no module should remain after 'include' if 'sufficient' might
+# be used in the included configuration file
+# pam_nologin moved to account phase - it's more appropriate there
+# other modules might be moved before the system-auth 'include'
+account required pam_nologin.so
+account include system-auth
+password include system-auth
+# pam_selinux.so close should be the first session rule
+session required pam_selinux.so close
+session include system-auth
+# the system-auth config doesn't contain sufficient modules
+# in the session phase
+session required pam_loginuid.so
+session optional pam_console.so
+# pam_selinux.so open should be the last session rule
+session required pam_selinux.so open
+</screen>
</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 a <emphasis>stack protector</emphasis>. This
- was using the compiler option
- <code>-fstack-protector</code>
- , which places a canary value on the stack of functions
- containing a local character array. Before returning from a
- protected function, the canary value is verified. If there was
- a buffer overflow, the canary will no longer match the
- expected value, aborting the program. The canary value is
- random each time the application is started, making remote
- exploitation very difficult. The stack protector feature does
- not protect against heap-based buffer overflows.
+ All of the software in Fedora Core and Extras software repository for
+ this release is compiled using a security feature called a
+ <emphasis>stack protector</emphasis>. This was using the compiler
+ option <code>-fstack-protector</code>, which places a canary value on
+ the stack of functions containing a local character array. Before
+ returning from a protected function, the canary value is verified. If
+ there was a buffer overflow, the canary will no longer match the
+ expected value, aborting the program. The canary value is random each
+ time the application is started, making remote exploitation very
+ difficult. The stack protector feature does not protect against
+ heap-based buffer overflows.
</para>
<para>
- This is a security feature written by Red Hat developers
- (<ulink url='http://gcc.gnu.org/ml/gcc-patches/2005-05/msg01193.html'>http://gcc.gnu.org/ml/gcc-patches/2005-05/msg01193.html</ulink>),
- reimplementing the IBM ProPolice/SSP feature. For more
- information about ProPolice/SSP, refer to
- <ulink url='http://www.research.ibm.com/trl/projects/security/ssp/'>http://www.research.ibm.com/trl/projects/security/ssp/</ulink>.
- This feature is available as part of the GCC 4.1 compiler used
- in Fedora Core .
+ This is a security feature written by Red Hat developers (<ulink
+ url='http://gcc.gnu.org/ml/gcc-patches/2005-05/msg01193.html'>http://gcc.gnu.org/ml/gcc-patches/2005-05/msg01193.html</ulink>),
+ reimplementing the IBM ProPolice/SSP feature. For more information
+ about ProPolice/SSP, refer to <ulink
+ url='http://www.research.ibm.com/trl/projects/security/ssp/'>http://www.research.ibm.com/trl/projects/security/ssp/</ulink>.
+ This feature is available as part of the GCC 4.1 compiler used in
+ Fedora Core 5.
</para>
<para>
- The
- <code>FORTIFY_SOURCE</code>
- security feature for
- <code>gcc</code>
- and
- <code>glibc</code>
- introduced in Fedora Core 4 remains available. For more
- information about security features in Fedora, refer to
- <ulink url='http://fedoraproject.org/wiki/Security/Features'>http://fedoraproject.org/wiki/Security/Features</ulink>.
- </para>
-
- <para></para>
-
- <para>
- <ulink url='/CategorySecurity'>CategorySecurity</ulink>
+ The <code>FORTIFY_SOURCE</code> security feature for <code>gcc</code>
+ and <code>glibc</code> introduced in Fedora Core 4 remains available.
+ For more information about security features in Fedora, refer to
+ <ulink
+ url='http://fedoraproject.org/wiki/Security/Features'>http://fedoraproject.org/wiki/Security/Features</ulink>.
</para>
</section>
</section>
Index: SecuritySELinux.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/SecuritySELinux.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- SecuritySELinux.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ SecuritySELinux.xml 15 Apr 2006 01:02:18 -0000 1.2
@@ -7,7 +7,7 @@
<title>Temp</title>
</articleinfo>
- <section>
+ <section id="sn-SecuritySELinux">
<title>SELinux</title>
<para>
@@ -53,39 +53,27 @@
<title>Multi Category Security (MCS)</title>
<para>
- MCS is a general-use implementation of the more stringent
- Multilevel Security (MLS). MCS is an enhancement to SELinux to
- allow users to label files with <emphasis>categories</emphasis>.
- Categories might include
- <code>Company_Confidential</code>
- ,
- <code>CEO_EYES_ONLY</code>
- , or
- <code>Sysadmin_Passwords</code>
- . For more information about MCS, refer to
- <ulink url='http://james-morris.livejournal.com/5583.html'>http://james-morris.livejournal.com/5583.html</ulink>,
- an article by the author.
+ MCS is a general-use implementation of the more stringent Multilevel
+ Security (MLS). MCS is an enhancement to SELinux to allow users to label
+ files with <emphasis>categories</emphasis>. Categories might include
+ <code>Company_Confidential</code>, <code>CEO_EYES_ONLY</code>, or
+ <code>Sysadmin_Passwords</code>. For more information about MCS, refer
+ to <ulink
+ url='http://james-morris.livejournal.com/5583.html'>http://james-morris.livejournal.com/5583.html</ulink>,
+ an article by the author of MCS.
</para>
<section>
<title>Multilevel Security (MLS)</title>
<para>
- MLS is a specific Mandatory Access Control (MAC) scheme that
- labels processes and objects with special security levels. For
- example, an object such as a document file can have the
- security level of
- <code>{ Secret, ProjectMeta }</code>
- , where
- <code>Secret</code>
- is the sensitivity level, and
- <code>ProjectMeta</code>
- is the category. For more information about MLS, refer to
- <ulink url='http://james-morris.livejournal.com/5020.html'>http://james-morris.livejournal.com/5020.html</ulink>.
- </para>
-
- <para>
- <ulink url='/CategorySecurity'>CategorySecurity</ulink>
+ MLS is a specific Mandatory Access Control (MAC) scheme that labels
+ processes and objects with special security levels. For example, an
+ object such as a document file can have the security level of <code>{
+ Secret, ProjectMeta }</code>, where <code>Secret</code> is the
+ sensitivity level, and <code>ProjectMeta</code> is the category. For
+ more information about MLS, refer to <ulink
+ url='http://james-morris.livejournal.com/5020.html'>http://james-morris.livejournal.com/5020.html</ulink>.
</para>
</section>
</section>
Index: ServerTools.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/ServerTools.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ServerTools.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ ServerTools.xml 15 Apr 2006 01:02:18 -0000 1.2
@@ -7,8 +7,8 @@
<title>Temp</title>
</articleinfo>
- <section>
- <title>Docs/Beats/ServerTools</title>
+ <section id="sn-ServerTools">
+ <title>Server Tools</title>
<para>
This section highlights changes and additions to the various GUI
@@ -22,10 +22,9 @@
<title>SMB Browsing Outside Local Network</title>
<para>
- You can now browse for Samba print shares across subnets. If
- you specify at least one WINS server in
- <code>/etc/samba/smb.conf</code>
- , the first address is used when browsing.
+ You can now browse for Samba print shares across subnets. If you
+ specify at least one WINS server in <code>/etc/samba/smb.conf</code>,
+ the first address is used when browsing.
</para>
</section>
@@ -34,25 +33,21 @@
<para>
The <emphasis role='strong'>system-config-printer</emphasis>
- application supports Kerberos authentication when adding a new
- SMB printer. To add the printer, the user must possess a valid
- Kerberos ticket and launch the printer configuration tool.
- Select
- <emphasis>System</emphasis>><emphasis>Administration</emphasis>><emphasis>Printing</emphasis>
- from the main menu, or use the following command:
+ application supports Kerberos authentication when adding a new SMB
+ printer. To add the printer, the user must possess a valid Kerberos
+ ticket and launch the printer configuration tool. Select
+ <emphasis>System > Administration > Printing</emphasis>
+ from the main menu, or use the following command:
</para>
- <itemizedlist>
- <listitem>
-<screen>su -c 'system-config-printer' \n</screen>
- </listitem>
- </itemizedlist>
+<screen>
+su -c 'system-config-printer'
+</screen>
<para>
No username and password is stored in
- <code>/etc/cups/printers.conf</code>
- . Printing is still possible if the SMB print queue permits
- anonymous printing.
+ <code>/etc/cups/printers.conf</code>. Printing is still possible if
+ the SMB print queue permits anonymous printing.
</para>
</section>
</section>
@@ -64,9 +59,8 @@
<title>Trusted Service Additions</title>
<para>
- Samba is now listed in the <emphasis>Trusted
- services</emphasis> list. To permit the firewall to pass SMB
- traffic, enable this option.
+ Samba is now listed in the <emphasis>Trusted services</emphasis> list.
+ To permit the firewall to pass SMB traffic, enable this option.
</para>
</section>
@@ -74,21 +68,17 @@
<title>Port Ranges</title>
<para>
- When you define <emphasis>Other Ports</emphasis> in the
- <emphasis role='strong'>system-config-securitylevel</emphasis>
- tool, you may now specify port ranges. For example, if you
- specify
- <code>6881-6999:tcp</code>
- , the following line is added to
- <code>/etc/sysconfig/iptables</code>
- :
+ When you define <emphasis>Other Ports</emphasis> in the <emphasis
+ role='strong'>system-config-securitylevel</emphasis> tool, you may
+ now specify port ranges. For example, if you specify
+ <code>6881-6999:tcp</code>, the following line is added to
+ <code>/etc/sysconfig/iptables</code>:
</para>
- <itemizedlist>
- <listitem>
-<screen>A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 6881:6999 -j ACCEPT \n</screen>
- </listitem>
- </itemizedlist>
+<screen>
+A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 6881:6999 \
+-j ACCEPT
+</screen>
</section>
</section>
</section>
Index: SystemDaemons.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/SystemDaemons.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- SystemDaemons.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ SystemDaemons.xml 15 Apr 2006 01:02:18 -0000 1.2
@@ -7,8 +7,8 @@
<title>Temp</title>
</articleinfo>
- <section>
- <title>Docs/Beats/SystemDaemons</title>
+ <section id="sn-SystemDaemons">
+ <title>System Daemons</title>
<table>
<caption/>
<tr>
Index: Virtualization.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/Virtualization.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Virtualization.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ Virtualization.xml 15 Apr 2006 01:02:18 -0000 1.2
@@ -7,7 +7,7 @@
<title>Temp</title>
</articleinfo>
- <section>
+ <section id="sn-Virtualization">
<title>Virtualization</title>
<para>
@@ -70,14 +70,14 @@
</listitem>
<listitem>
<para>
- Enough hard drive space to hold each guest OS (600MB-6GB
+ Enough hard drive space to hold each guest OS (600MiB-6GiB
per OS)
</para>
</listitem>
<listitem>
<para>
- At least 256 MB of RAM for each guest, plus at least 256
- MB ram for the host
+ At least 256 MiB of RAM for each guest, plus at least 256
+ MiB ram for the host
</para>
</listitem>
</itemizedlist>
@@ -103,36 +103,12 @@
<ulink url='http://fedoraproject.org/wiki/FedoraXenQuickstartFC5'>http://fedoraproject.org/wiki/FedoraXenQuickstartFC5</ulink>
</para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='16' fileref='/wiki/rightsidebar/img/icon-info.png' depth='16'/>
- </imageobject>
- <textobject>
- <phrase>{i}</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>No PowerPC Support</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- Xen is not supported on the PowerPC architecture in
- Fedora Core .
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <note>
+ <title>No PowerPC Support</title>
+ <para>
+ Xen is not supported on the PowerPC architecture in Fedora Core 5.
+ </para>
+ </note>
</section>
</section>
</article>
Index: WebServers.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/WebServers.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- WebServers.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ WebServers.xml 15 Apr 2006 01:02:18 -0000 1.2
@@ -7,7 +7,7 @@
<title>Temp</title>
</articleinfo>
- <section>
+ <section id="sn-WebServers">
<title>Web Servers</title>
<para>
@@ -18,147 +18,86 @@
<title>httpd</title>
<para>
- Fedora Core now includes version 2.2 of the Apache HTTP Server.
- This release brings a number of improvements over the 2.0
- series, including:
+ Fedora Core now includes version 2.2 of the Apache HTTP Server. This
+ release brings a number of improvements over the 2.0 series, including:
</para>
<itemizedlist>
<listitem>
<para>
- greatly improved caching modules (
- <code>mod_cache</code>
- ,
- <code>mod_disk_cache</code>
- ,
- <code>mod_mem_cache</code>
- )
+ greatly improved caching modules ( <code>mod_cache</code>,
+ <code>mod_disk_cache</code>, <code>mod_mem_cache</code> )
</para>
</listitem>
<listitem>
<para>
- a new structure for authentication and authorization
- support, replacing the security modules provided in previous
- versions
+ a new structure for authentication and authorization support,
+ replacing the security modules provided in previous versions
</para>
</listitem>
<listitem>
<para>
- support for proxy load balancing (
- <code>mod_proxy_balance</code>
- )
+ support for proxy load balancing (<code>mod_proxy_balance</code>)
</para>
</listitem>
<listitem>
<para>
- large file support for 32-bit platforms (including support
- for serving files larger than 2GB)
+ large file support for 32-bit platforms (including support for
+ serving files larger than 2GB)
</para>
</listitem>
<listitem>
<para>
- new modules
- <code>mod_dbd</code>
- and
- <code>mod_filter</code>
- , which bring SQL database support and enhanced filtering
+ new modules <code>mod_dbd</code> and <code>mod_filter</code>, which
+ bring SQL database support and enhanced filtering
</para>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/ntheme/img/star_on.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase>{*}</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Upgrading and Security
- Modules</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- If you upgrade from a previous version of
- <code>httpd</code>
- , update your server configuration to use the new
- authentication and authorization modules. Refer to the
- page listed below for more details.
- </para>
- </td>
- </tr>
- </table>
+ <important>
+ <title>Upgrading and Security Modules</title>
+ <para>
+ If you upgrade from a previous version of <code>httpd</code>,
+ update your server configuration to use the new authentication and
+ authorization modules. Refer to the page listed below for more
+ details.
+ </para>
+ </important>
</listitem>
</itemizedlist>
<para>
- The following changes have been made to the default
- <code>httpd</code>
- configuration:
+ The following changes have been made to the default <code>httpd</code>
+ configuration:
</para>
<itemizedlist>
<listitem>
<para>
- The
- <code>mod_cern_meta</code>
- and
- <code>mod_asis</code>
- modules are no longer loaded by default.
+ The <code>mod_cern_meta</code> and <code>mod_asis</code> modules are
+ no longer loaded by default.
</para>
</listitem>
<listitem>
<para>
- The
- <code>mod_ext_filter</code>
- module is now loaded by default.
- </para>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/ntheme/img/star_on.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase>{*}</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Third-party Modules</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- Any third-party modules compiled for
- <code>httpd</code>
- 2.0 must be rebuilt for
- <code>httpd</code>
- 2.2.
- </para>
- </td>
- </tr>
- </table>
+ The <code>mod_ext_filter</code> module is now loaded by default.
+ </para>
+ <important>
+ <title>Third-party Modules</title>
+ <para>
+ Any third-party modules compiled for <code>httpd</code> 2.0 must
+ be rebuilt for <code>httpd</code> 2.2.
+ </para>
+ </important>
</listitem>
</itemizedlist>
<para>
- The complete list of new features is available at
- <ulink url='http://httpd.apache.org/docs/2.2/new_features_2_2.html'>http://httpd.apache.org/docs/2.2/new_features_2_2.html</ulink>
+ The complete list of new features is available at <ulink
+ url='http://httpd.apache.org/docs/2.2/new_features_2_2.html'>http://httpd.apache.org/docs/2.2/new_features_2_2.html</ulink>
</para>
<para>
- For more information on upgrading existing installations, refer
- to
- <ulink url='http://httpd.apache.org/docs/2.2/upgrading.html'>http://httpd.apache.org/docs/2.2/upgrading.html</ulink>.
+ For more information on upgrading existing installations, refer to
+ <ulink
+ url='http://httpd.apache.org/docs/2.2/upgrading.html'>http://httpd.apache.org/docs/2.2/upgrading.html</ulink>.
</para>
</section>
@@ -166,8 +105,8 @@
<title>php</title>
<para>
- Version 5.1 of PHP is now included in Fedora Core. This release
- brings a number of improvements since PHP 5.0, including:
+ Version 5.1 of PHP is now included in Fedora Core. This release brings a
+ number of improvements since PHP 5.0, including:
</para>
<itemizedlist>
@@ -190,58 +129,35 @@
<itemizedlist>
<listitem>
<para>
- <code>date</code>
- ,
- <code>hash</code>
- , and
- <code>Reflection</code>
- (built-in with the
- <code>php</code>
- package)
+ <code>date</code>, <code>hash</code>, and <code>Reflection</code>
+ (built-in with the <code>php</code> package)
</para>
</listitem>
<listitem>
<para>
- <code>pdo</code>
- and
- <code>pdo_psqlite</code>
- (in the
- <code>php-pdo</code>
- package)
+ <code>pdo</code> and <code>pdo_psqlite</code> (in the
+ <code>php-pdo</code> package
</para>
</listitem>
<listitem>
<para>
- <code>pdo_mysql</code>
- (in the
- <code>php-mysql</code>
- package)
+ <code>pdo_mysql</code> (in the <code>php-mysql</code> package)
</para>
</listitem>
<listitem>
<para>
- <code>pdo_pgsql</code>
- (in the
- <code>php-pgsql</code>
- package)
+ <code>pdo_pgsql</code> (in the <code>php-pgsql</code> package)
</para>
</listitem>
<listitem>
<para>
- <code>pdo_odbc</code>
- (in the
- <code>php-odbc</code>
- package)
+ <code>pdo_odbc</code> (in the <code>php-odbc</code> package)
</para>
</listitem>
<listitem>
<para>
- <code>xmlreader</code>
- and
- <code>xmlwriter</code>
- (in the
- <code>php-xml</code>
- package)
+ <code>xmlreader</code> and <code>xmlwriter</code> (in the
+ <code>php-xml</code> package)
</para>
</listitem>
</itemizedlist>
@@ -272,10 +188,9 @@
<title>The PEAR framework</title>
<para>
- The PEAR framework is now packaged in the
- <code>php-pear</code>
- package. Only the following PEAR components are included in
- Fedora Core:
+ The PEAR framework is now packaged in the <code>php-pear</code>
+ package. Only the following PEAR components are included in Fedora
+ Core:
</para>
<itemizedlist>
Index: Welcome.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/Welcome.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Welcome.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ Welcome.xml 15 Apr 2006 01:02:18 -0000 1.2
@@ -10,39 +10,14 @@
<section id="sn-Welcome">
<title>Welcome to Fedora Core</title>
- <itemizedlist>
- <listitem>
- <para></para>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/ntheme/img/idea.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase>(!)</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Latest Release Notes on the
- Web</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- These release notes may be updated. Visit
- <ulink url='http://fedora.redhat.com/docs/release-notes/'>http://fedora.redhat.com/docs/release-notes/</ulink>
- to view the latest release notes for Fedora Core .
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <tip>
+ <title>Latest Release Notes on the Web</title>
+ <para>
+ These release notes may be updated. Visit <ulink
+ url='http://fedora.redhat.com/docs/release-notes/'>http://fedora.redhat.com/docs/release-notes/</ulink>
+ to view the latest release notes for Fedora Core 5.
+ </para>
+ </tip>
<para>
You can help the Fedora Project community continue to improve
Index: Xorg.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/Xorg.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Xorg.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ Xorg.xml 15 Apr 2006 01:02:18 -0000 1.2
@@ -7,7 +7,7 @@
<title>Temp</title>
</articleinfo>
- <section>
+ <section id="sn-Xorg">
<title>X Window System (Graphics)</title>
<para>
@@ -19,82 +19,50 @@
<title>xorg-x11</title>
<para>
- X.org X11 is an open source implementation of the X Window
- System. It provides the basic low-level functionality upon which
- full-fledged graphical user interfaces (GUIs) such as GNOME and
- KDE are designed. For more information about X.org, refer to
- <ulink url='http://xorg.freedesktop.org/wiki/'>http://xorg.freedesktop.org/wiki/</ulink>.
+ X.org X11 is an open source implementation of the X Window System. It
+ provides the basic low-level functionality upon which full-fledged
+ graphical user interfaces (GUIs) such as GNOME and KDE are designed. For
+ more information about X.org, refer to <ulink
+ url='http://xorg.freedesktop.org/wiki/'>http://xorg.freedesktop.org/wiki/</ulink>.
</para>
<para>
- You may use <emphasis>System > Administration >
- Display</emphasis> or
- <emphasis role='strong'>system-config-display</emphasis> to
- configure the settings. The configuration file for X.org is
- located in
- <code>/etc/X11/xorg.conf</code>
- .
+ You may use <emphasis>System > Administration > Display</emphasis> or
+ <emphasis role='strong'>system-config-display</emphasis> to configure
+ the settings. The configuration file for X.org is located in
+ <code>/etc/X11/xorg.conf</code>.
</para>
<para>
- X.org X11R7 is the first modular release of X.org, which, among
- several other benefits, promotes faster updates and helps
- programmers rapidly develop and release specific components.
- More information on the current status of the X.org
- modularization effort in Fedora is available at
- <ulink url='http://fedoraproject.org/wiki/Xorg/Modularization'>http://fedoraproject.org/wiki/Xorg/Modularization</ulink>.
+ X.org X11R7 is the first modular release of X.org, which, among several
+ other benefits, promotes faster updates and helps programmers rapidly
+ develop and release specific components. More information on the current
+ status of the X.org modularization effort in Fedora is available at
+ <ulink
+ url='http://fedoraproject.org/wiki/Xorg/Modularization'>http://fedoraproject.org/wiki/Xorg/Modularization</ulink>.
</para>
</section>
<section>
<title>X.org X11R7 End-User Notes</title>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/rightsidebar/img/attention.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase><!></phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Installing Third Party
- Drivers</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- Before you install any third party drivers from any
- vendor, including ATI or nVidia, please read
- <ulink url='http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers'>http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers</ulink>.
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
-
- <para>
- The
- <code>xorg-x11-server-Xorg</code>
- package install scripts automatically remove the
- <code>RgbPath</code>
- line from the
- <code>xorg.conf</code>
- file if it is present. You may need to reconfigure your keyboard
- differently from what you are used to. You are encouraged to
- subscribe to the upstream
- <ulink url='mailto:xorg at freedesktop.org'>xorg at freedesktop.org</ulink>
- mailing list if you do need assistance reconfiguring your
- keyboard.
+ <caution>
+ <title>Installing Third Party Drivers</title>
+ <para>
+ Before you install any third party drivers from any vendor, including
+ ATI or nVidia, please read <ulink
+ url='http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers'>http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers</ulink>.
+ </para>
+ </caution>
+
+ <para>
+ The <code>xorg-x11-server-Xorg</code> package install scripts
+ automatically remove the <code>RgbPath</code> line from the
+ <code>xorg.conf</code> file if it is present. You may need to
+ reconfigure your keyboard differently from what you are used to. You are
+ encouraged to subscribe to the upstream <ulink
+ url='mailto:xorg at freedesktop.org'>xorg at freedesktop.org</ulink> mailing
+ list if you do need assistance reconfiguring your keyboard.
</para>
</section>
@@ -103,54 +71,38 @@
<para>
The following list includes some of the more visible changes for
- developers in X11R7:
+ developers in X11R7:
</para>
<itemizedlist>
<listitem>
<para>
- The entire buildsystem has changed from
- <code>imake</code>
- to the GNU
- <code>autotools</code>
- collection.
+ The entire buildsystem has changed from <code>imake</code> to the
+ GNU <code>autotools</code> collection.
</para>
</listitem>
<listitem>
<para>
- Libraries now install
- <code>pkgconfig</code>
- <code>*.pc</code>
- files, which should now always be used by software that
- depends on these libraries, instead of hard coding paths to
- them in
- <code>/usr/X11</code>
- <code>R6/lib </code>
- or elsewhere.
+ Libraries now install <code>pkgconfig</code> <code>*.pc</code>
+ files, which should now always be used by software that depends on
+ these libraries, instead of hard coding paths to them in
+ <code>/usr/X11R6/lib </code> or elsewhere.
</para>
</listitem>
<listitem>
<para>
- Everything is now installed directly into
- <code>/usr</code>
- instead of
- <code>/usr/X11</code>
- <code>R6</code>
- . All software that hard codes paths to anything in
- <code>/usr/X11</code>
- <code>R6</code>
- must now be changed, preferably to dynamically detect the
- proper location of the object. Developers are
- <emphasis role='strong'>strongly</emphasis> advised against
- hard-coding the new X11R7 default paths.
+ Everything is now installed directly into <code>/usr</code> instead
+ of <code>/usr/X11R6</code>. All software that hard codes paths to
+ anything in <code>/usr/X11R6</code> must now be changed, preferably
+ to dynamically detect the proper location of the object. Developers
+ are <emphasis role='strong'>strongly</emphasis> advised against
+ hard-coding the new X11R7 default paths.
</para>
</listitem>
<listitem>
<para>
- Every library has its own private source RPM package, which
- creates a runtime binary subpackage and a
- <code>-devel</code>
- subpackage.
+ Every library has its own private source RPM package, which creates
+ a runtime binary subpackage and a <code>-devel</code> subpackage.
</para>
</listitem>
</itemizedlist>
@@ -160,30 +112,21 @@
<title>X.org X11R7 Developer Notes</title>
<para>
- This section includes a summary of issues of note for developers
- and packagers, and suggestions on how to fix them where
- possible.
+ This section includes a summary of issues of note for developers and
+ packagers, and suggestions on how to fix them where possible.
</para>
<section>
<title>The /usr/X11R6/ Directory Hierarchy</title>
<para>
- X11R7 files install into
- <code>/usr</code>
- directly now, and no longer use the
- <code>/usr/X11</code>
- <code>R6/</code>
- hierarchy. Applications that rely on files being present at
- fixed paths under
- <code>/usr/X11</code>
- <code>R6/</code>
- , either at compile time or run time, must be updated. They
- should now use the system
- <code>PATH</code>
- , or some other mechanism to dynamically determine where the
- files reside, or alternatively to hard code the new locations,
- possibly with fallbacks.
+ X11R7 files install into <code>/usr</code> directly now, and no longer
+ use the <code>/usr/X11R6/</code> hierarchy. Applications that rely on
+ files being present at fixed paths under <code>/usr/X11R6/</code>,
+ either at compile time or run time, must be updated. They should now
+ use the system <code>PATH</code>, or some other mechanism to
+ dynamically determine where the files reside, or alternatively to hard
+ code the new locations, possibly with fallbacks.
</para>
</section>
@@ -191,27 +134,16 @@
<title>Imake</title>
<para>
- The
- <code>imake</code>
- utility is no longer used to build the X Window System, and is
- now officially deprecated. X11R7 includes
- <code>imake</code>
- ,
- <code>xmkmf</code>
- , and other build utilities previously supplied by the X
- Window System. X.Org highly recommends, however, that people
- migrate from
- <code>imake</code>
- to use GNU
- <code>autotools</code>
- and
- <code>pkg-config</code>
- . Support for
- <code>imake</code>
- may be removed in a future X Window System release, so
- developers are <emphasis role='strong'>strongly</emphasis>
- encouraged to transition away from it, and not use it for any
- new software projects.
+ The <code>imake</code> xutility is no longer used to build the X
+ Window System, and is now officially deprecated. X11R7 includes
+ <code>imake</code>, <code>xmkmf</code>, and other build utilities
+ previously supplied by the X Window System. X.Org highly recommends,
+ however, that people migrate from <code>imake</code> to use GNU
+ <code>autotools</code> and <code>pkg-config</code>. Support for
+ <code>imake</code> may be removed in a future X Window System release,
+ so developers are <emphasis role='strong'>strongly</emphasis>
+ encouraged to transition away from it, and not use it for any new
+ software projects.
</para>
</section>
@@ -219,14 +151,10 @@
<title>The Systemwide app-defaults/ Directory</title>
<para>
- The system
- <code>app-defaults/</code>
- directory for X resources is now
- <code>%{_datadir}/X11/app-defaults</code>
- , which expands to
- <code>/usr/share/X11/app-defaults/</code>
- on Fedora Core and for future Red Hat Enterprise Linux
- systems.
+ The system <code>app-defaults/</code> directory for X resources is now
+ <code>%{_datadir}/X11/app-defaults</code>, which expands to
+ <code>/usr/share/X11/app-defaults/</code> on Fedora Core and for
+ future Red Hat Enterprise Linux systems.
</para>
</section>
@@ -234,27 +162,19 @@
<title>Correct Package Dependencies</title>
<para>
- Any software package that previously used
- <code>Build</code>
- <code>Requires: (XFree86-devel|xorg-x11-devel)</code>
- to satisfy build dependencies must now individually list each
- library dependency. The preferred and recommended method is to
- use <emphasis>virtual</emphasis> build dependencies instead of
- hard coding the library package names of the
- <code>xorg</code>
- implementation. This means you should use
- <code>Build</code>
- <code>Requires: libXft-devel</code>
- instead of
- <code>Build</code>
- <code>Requires: xorg-x11-Xft-devel</code>
- . If your software truly does depend on the X.Org X11
- implementation of a specific library, and there is no other
- clean or safe way to state the dependency, then use the
- <code>xorg-x11-devel</code>
- form. If you use the virtual provides/requires mechanism, you
- will avoid inconvenience if the libraries move to another
- location in the future.
+ Any software package that previously used <code>Build Requires:
+ (XFree86-devel|xorg-x11-devel)</code> to satisfy build dependencies
+ must now individually list each library dependency. The preferred and
+ recommended method is to use <emphasis>virtual</emphasis> build
+ dependencies instead of hard coding the library package names of the
+ <code>xorg</code> implementation. This means you should use
+ <code>Build Requires: libXft-devel</code> instead of <code>Build
+ Requires: xorg-x11-Xft-devel</code>. If your software truly does
+ depend on the X.Org X11 implementation of a specific library, and
+ there is no other clean or safe way to state the dependency, then use
+ the <code>xorg-x11-devel</code> form. If you use the virtual
+ provides/requires mechanism, you will avoid inconvenience if the
+ libraries move to another location in the future.
</para>
</section>
@@ -262,25 +182,14 @@
<title>xft-config</title>
<para>
- Modular X now uses GNU
- <code>autotools</code>
- and
- <code>pkg-config</code>
- for its buildsystem configuration and execution. The
- <code>xft-config</code>
- utility has been deprecated for some time, and
- <code>pkgconfig</code>
- <code>*.pc</code>
- files have been provided for most of this time. Applications
- that previously used
- <code>xft-config</code>
- to obtain the
- <code>Cflags</code>
- or
- <code>libs</code>
- build options must now be updated to use
- <code>pkg-config</code>
- .
+ Modular X now uses GNU <code>autotools</code> and
+ <code>pkg-config</code> for its buildsystem configuration and
+ execution. The <code>xft-config</code> utility has been deprecated for
+ some time, and <code>pkgconfig</code> <code>*.pc</code> files have
+ been provided for most of this time. Applications that previously used
+ <code>xft-config</code> to obtain the <code>Cflags</code> or
+ <code>libs</code> build options must now be updated to use
+ <code>pkg-config</code>.
</para>
</section>
</section>
- Previous message: example-tutorial/en_US doc-entities.ent,1.1,NONE
- Next message: docs-common/common/entities entities-pl.ent, NONE, 1.1 entities-pl.xml, NONE, 1.1 pl.po, NONE, 1.1 Makefile, 1.19, 1.20
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the docs-commits
mailing list