release-notes/FC4 multimedia.xml, 1.2, 1.3 package-notes.xml, 1.3, 1.4 web-servers.xml, 1.3, 1.4
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Sun May 29 16:57:33 UTC 2005
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25853
Modified Files:
multimedia.xml package-notes.xml web-servers.xml
Log Message:
Parsing more content from the FC4test3 notes into the files, including visual diffing for the web-servers.xml content. This merges in the content from Joe Orton <jorton at redhat.com> submitted during the test process. Reorganized the web-servers.xml file.
Index: multimedia.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/multimedia.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- multimedia.xml 28 May 2005 16:10:31 -0000 1.2
+++ multimedia.xml 29 May 2005 16:57:31 -0000 1.3
@@ -1,3 +1,10 @@
+<section>
+ <title>Multimedia</title>
+ <para>
+ This section contains information related to multimedia
+ applications.
+ </para>
+</section>
<!--
Local variables:
mode: xml
Index: package-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/package-notes.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- package-notes.xml 29 May 2005 16:37:44 -0000 1.3
+++ package-notes.xml 29 May 2005 16:57:31 -0000 1.4
@@ -8,6 +8,205 @@
have undergone significant changes for &DISTRO; &DISTROVER;. For easier
access, they are organized using the same groups used in Anaconda.</para>
+<!--
+This is content from the FC4 test relnotes, needing formatting:
+
+=== Base ===
+
+This section contains information related to basic system components.
+
+
+auditd and log files
+
+The audit daemon, auditd, is now enabled by default. When auditd is
+running, the kernel directs audit messages to
+/var/log/audit/audit.log. The location of this file is specified in
+/etc/auditd.conf.
+
+AVC messages for SELinux are sent using the audit infrastructure.
+These messages are now in /var/log/audit/audit.log.
+
+When auditd is not running, the kernel passes audit messages to
+syslog. These logs are typically kept in /var/log/messages and are
+viewable using dmesg.
+
+Audit extensions are now compiled into PAM. All programs that do
+grant entry to the system or change user account attributes will
+generate an audit message.
+
+To enable auditing within the kernel, you must pass the parameter
+audit=1 to the kernel during boot. Otherwise, you can use this
+command to enable auditing during run time:
+
+ 'auditctl -e 1'
+
+
+LinuxThreads v. NPTL
+
+As the next step in removing support for the obsolete LinuxThreads
+library, code compiled and linked on FC4 now automatically uses the NPTL
+headers and libraries.
+
+In previous releases, since Red Hat Linux 9, the default was to use
+LinuxThreads since the interface is mostly forward compatible. The
+advantages of the NPTL interface is that the cancellation handling is
+faster (when -fexception is used, even in C code) and that the
+additional interfaces are now available without special compiler and
+linker parameters. In other words, you do not need to use
+-I/usr/include/nptl and -L/usr/lib{,64}/nptl any longer. Note that
+lib{,64} is to be interpreted as lib64 on platforms which place DSOs
+in lib64 directories, and lib otherwise.
+
+In FC4 it is still possible to create code using the LinuxThreads
+definitions. For this the linuxthreads-devel package must be
+installed and
+
+ -I/usr/include/linuxthreads -L/usr/lib{,64}/linuxthreads
+
+must be passed to the compiler.
+
+At runtime, it used to be possible to use the LD_ASSUME_KERNEL
+environment variable to select the appropriate version of glibc and the
+libpthread DSO. Now it is additionally necessary to specify
+
+ LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads
+
+in the environment. This is because the runtime libraries have also
+been moved out of the way. There might programs that will not work if
+the program uses an unfortunate DT_RPATH (which overwrites the
+LD_LIBRARY_PATH setting).
+
+All this makes it more cumbersome to run programs which depend on
+LinuxThreads. But this is intentional.
+
+ Important
+
+ FC5 will not have LinuxThreads support and all programs have to be
+ converted to use NPTL by then.
+
+In general, conversion to using NPTL has not been an issue.
+
+
+slocate database
+
+The database needed by the locate utility is no longer created by default.
+Enable the database creation by setting DAILY_UPDATE to "yes" in
+/etc/updatedb.conf if you want to use locate.
+
+
+openssh
+
+The version of OpenSSH in Fedora Core 4 contains OpenSSH 3.9
+includes strict permission and ownership checks for the ~/.ssh/config
+file. These checks mean that ssh will exit if this file does not have
+appropriate ownership and permissions.
+
+Therefore, make sure that ~/.ssh/config is owned by the owner of ~/,
+and that its permissions are set to mode 600.
+
+In addition, OpenSSH is no longer configured to request X11 forwarding
+by default when connecting to servers. To enable X11 forwarding, the
+-X or -Y option must be specified, or the ForwardX11 option must be
+enabled in the ~/.ssh/config file.
+
+The behavior of ssh clients that are invoked with the -X flag has
+changed. In OpenSSH 3.8 and later, X11 forwarding is performed in a
+way that applications run as untrusted clients by default. Previously,
+X11 forwarding was performed so that applications always ran as
+trusted clients. Some applications may not function properly when run
+as untrusted clients. To forward X11 so that applications are run as
+trusted clients, invoke ssh with the -Y flag instead of the -X flag,
+or set ForwardX11Trusted in the ~/.ssh/config file.
+
+=== Core ===
+
+This section contains the most elemental components of Fedora Core,
+including the kernel.
+
+
+yum
+
+The sqllite database is now used by yum, and makes performance
+noticeably faster.
+
+The Fedora Extras repository is now enabled by default.
+
+
+kernel source
+
+In order to eliminate the redundancy inherent in providing a separate
+package for the kernel source code when that source code already
+exists in the kernel's .src.rpm file, Fedora Core 4 no longer
+includes the kernel-source package. Users that require access to the
+kernel sources can find them in the kernel .src.rpm file. To create an
+exploded source tree from this file, perform the following steps (note
+that <version> refers to the version specification for your
+currently-running kernel):
+
+ 1. Obtain the kernel-<version>.src.rpm file from one of the
+ following sources:
+
+ * The SRPMS directory on the appropriate "SRPMS" CD iso image
+
+ * The FTP site where you got the kernel package
+
+ * By running the following command:
+
+ up2date --get-source kernel
+
+ 2. Install kernel-<version>.src.rpm (given the default RPM
+ configuration, the files this package contains will be written to
+ /usr/src/redhat/)
+
+ rpm -ivh kernel-<version>.src.rpm
+
+ 3. Change directory to /usr/src/redhat/SPECS/, and issue the
+ following command:
+
+ rpmbuild -bp --target=<arch> kernel.spec
+
+ (Where <arch> is the desired target architecture.)
+
+ On a default RPM configuration, the kernel tree will be located
+ in /usr/src/redhat/BUILD/.
+
+ 4. In resulting tree, the configurations for the specific kernels
+ shipped in Fedora Core 4 are in the /configs/
+ directory. For example, the i686 SMP configuration file is named
+ /configs/kernel-<version>-i686-smp.config. Issue the following
+ command to place the desired configuration file in the proper
+ place for building:
+
+ cp <desired-file> ./.config
+
+ 5. Issue the following command:
+
+ make oldconfig
+
+You can then proceed as usual.
+
+Note
+
+An exploded source tree is not required to build kernel modules
+against the currently in-use kernel.
+
+For example, to build the foo.ko module, create the following file
+(named Makefile) in the directory containing the foo.c file:
+
+obj-m := foo.o
+
+KDIR := /lib/modules/$(shell uname -r)/build
+PWD := $(shell pwd)
+
+default:
+$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
+
+
+Issue the make command to build the foo.ko module.
+
+
+-->
+
<section os="bogus">
<title>Administration Tools</title>
Index: web-servers.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/web-servers.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- web-servers.xml 29 May 2005 14:41:24 -0000 1.3
+++ web-servers.xml 29 May 2005 16:57:31 -0000 1.4
@@ -1,68 +1,37 @@
<section id="sn-web-servers">
<title>Web Servers</title>
-
- <para>This section contains information related to Web-related applications.</para>
-
-
+ <para>
+ This section contains information related to Web-related
+ applications.
+ </para>
<section id="sn-web-servers-modperl">
- <title><filename>mod_perl</filename></title>
-
- <para>The RC5 release of mod_perl 2.0 is now included. The API provided by
-this release is incompatible with previous 1.99_xx releases. Please
-refer to the following document for a discussion of how to adapt code to
-use the new API:</para>
-
+ <title><filename>mod_perl</filename></title>
+ <para>
+ The RC5 release of mod_perl 2.0 is now included. The API provided
+ by this release is incompatible with previous 1.99_xx releases.
+ Please refer to the following document for a discussion of how to
+ adapt code to use the new API:
+ </para>
<para>
<ulink url="http://perl.apache.org/docs/2.0/rename.html">http://perl.apache.org/docs/2.0/rename.html</ulink>
</para>
-
- </section>
-
-
- <section id="sn-web-servers-php">
- <title><filename>php</filename></title>
-
- <para>Version 5.0 of PHP is now included. A number of changes have been
- made to the PHP language as part of this version. Please refer to
- the PHP documentation for information on migrating from PHP 4.3 to PHP 5.0:</para>
-
- <para>
- <ulink url="http://www.php.net/manual/en/migration5.php">http://www.php.net/manual/en/migration5.php</ulink>
- </para>
-
- <para>The <filename>/usr/bin/php</filename> binary is now built using
- the CLI command-line SAPI, rather than the CGI SAPI. Use
- <filename>/usr/bin/php-cgi</filename> for CGI SAPI. The
- <command>php-cgi</command> also includes FastCGI support.</para>
-
- <para>The following extensions have been added:</para>
-
- <itemizedlist>
- <listitem>
- <para>The <command>mysqli</command> extension, a new interface designed specifically for
- MySQL 4.1. This is included in the <filename>php-mysql</filename> package.</para>
- </listitem>
- <listitem>
- <para>The <command>soap</command> extension, for implementing SOAP clients and servers.</para>
- </listitem>
- </itemizedlist>
-
- <para>The following extensions are now available as optional
- loadable extensions, rather than being built in to the PHP binaries:</para>
-
- <itemizedlist>
- <listitem>
- <para>The <command>mysqli</command> extension, a new interface designed specifically for
- MySQL 4.1. This is included in the <filename>php-mysql</filename> package.</para>
- </listitem>
- <listitem>
- The <command>bcmath</command> extension, now available in the <filename>php-bcmath</filename> package.
- </listitem>
- </itemizedlist>
-
+ <section id="sn-web-servers-php">
+ <title><filename>php</filename></title>
+ <para>
+ Version 5.0 of PHP is now included, which includes a number of
+ changes to the language along with significant performance
+ improvements. dba</filename> package
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <command>bcmath</command> extension, now available in
+ the <filename>php-bcmath</filename> package
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
</section>
-
-
<!--
Local variables:
mode: xml
More information about the Fedora-docs-commits
mailing list