release-notes/FC4 RELEASE-NOTES-en.xml, 1.4, 1.5 package-movement.xml, 1.3, 1.4 package-notes.xml, 1.5, 1.6 samba.xml, 1.5, 1.6 splash.xml, 1.2, 1.3 web-servers.xml, 1.7, 1.8
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Mon May 30 14:41:48 UTC 2005
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21855
Modified Files:
RELEASE-NOTES-en.xml package-movement.xml package-notes.xml
samba.xml splash.xml web-servers.xml
Log Message:
Interim check-in that includes >90% of the package notes, a few changes to fix builds in web-servers.xml and samba.xml, and starts using the new common entities file.
Index: RELEASE-NOTES-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/RELEASE-NOTES-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- RELEASE-NOTES-en.xml 29 May 2005 19:35:08 -0000 1.4
+++ RELEASE-NOTES-en.xml 30 May 2005 14:41:46 -0000 1.5
@@ -1,3 +1,4 @@
+<!-- $Id$ -->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
@@ -30,7 +31,7 @@
<!-- *************** COMMON FDP entities *************** -->
-<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../../common/fedora-entities-en.xml">
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../../common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
<!ENTITY LEGALNOTICE SYSTEM "../../common/legalnotice-en.xml">
@@ -66,9 +67,10 @@
&PACKAGE-NOTES;
&PACKAGE-MOVEMENT;
&PROJECT-OVERVIEW;
-
+ <!--
<ackno>(
<emphasis arch="x86">x86</emphasis>
<emphasis arch="x86_64">x86_64</emphasis>
)</ackno>
+ -->
</article>
Index: package-movement.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/package-movement.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- package-movement.xml 29 May 2005 16:37:44 -0000 1.3
+++ package-movement.xml 30 May 2005 14:41:46 -0000 1.4
@@ -4,6 +4,199 @@
FIXME
Needs updating of entire contents for FC4.
-->
+ <section id="sn-packages-moved">
+ <title>Packages Moved to &FEX;</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ abiword
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ aiksaurus
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ bzflag
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ cyrus-imapd
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ dbh
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ dietlibc
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ exim
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ freeciv
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ gnuchess
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ gnumeric
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ grip
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ jed
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ lapack
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ libgda
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ libgnomedb
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ libxfce4mcs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ libxfce4util
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ libxfcegui
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ ncftp
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ ots
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ sylpheed
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ system-switch-im
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xcin
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xemacs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xemacs-sumo
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xfce4-iconbox
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xfce4-panel
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xfce4-systray
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xfce-mcs-manager
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xfce-mcs-plugins
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xfce-utils
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xfdesktop
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xffm
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xffm-icons
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xfprint
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xfwm4
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ xmms
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+<!-- keeping this old structure for the time being
+
<para>This section contains lists of packages that fit into the following
categories:</para>
@@ -2286,7 +2479,6 @@
</listitem>
</itemizedlist>
</section>
-
<section>
<title>Packages Deprecated</title>
@@ -2330,7 +2522,8 @@
</listitem>
</itemizedlist>
</section>
- </section>
+-->
+</section>
<!--
Local variables:
mode: xml
Index: package-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/package-notes.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- package-notes.xml 29 May 2005 18:15:06 -0000 1.5
+++ package-notes.xml 30 May 2005 14:41:46 -0000 1.6
@@ -1,212 +1,205 @@
- <section>
- <title>Package-Specific Notes</title>
+<section>
+ <title>Package-Specific Notes</title>
<!--
FIXME
Needs updating of entire contents for FC4.
-->
- <para>The following sections contain information regarding packages that
- 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 -FIXEM-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 -FIXME-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.
-
-
--->
-
+ <para>
+ The following sections contain information regarding packages that
+ have undergone significant changes for &DISTRO; &DISTROVER;. For
+ easier access, they are organized using the same groups used in
+ Anaconda.
+ </para>
+
+ <section id="sn-basic-components">
+ <title>Basic Components</title>
+ <para>
+ This section contains information related to basic system
+ components.
+ </para>
+ <section>
+ <title>&FEX; Repository</title>
+ <para>
+ &FEX; is part of the larger &FP; and is a
+ volunteer-based community effort to create a repository of
+ packages that compliment &FC;. The &FEX; repository
+ is enabled by default from &FC; &LOCALVER; onwards.
+ </para>
+ <para>
+ You can lean more about &FEX; from:
+ </para>
+ <para>
+ <ulink url="http://fedoraproject.org/wiki/Extras">http://fedoraproject.org/wiki/Extras</ulink>
+ </para>
+ <para>If you would like to install any software available from Fedora extras you can
+ use <command>yum</command>.
+ </para>
+ <para>
+ <command>yum install <replaceable><packagename></replaceable></command>
+ </para>
+ <para>
+ Where <replaceable><packagename></replaceable> is the name
+ of the package you want to install. For example, if you wanted
+ to install the <filename>abiword</filename> package, the command
+ <command>yum install abiword</command> automatically installs
+ the package and all dependencies.
+ </para>
+ </section>
+ <section id="sn-audit-daemon">
+ <title>Audit Daemon <command>auditd</command> and Log
+ Files</title>
+ <para>
+ 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.
+ </para>
+ <para>
+ AVC messages for SELinux are sent using the audit
+ infrastructure. These messages are now in
+ /var/log/audit/audit.log.
+ </para>
+ <para>
+ 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.
+ </para>
+ <para>
+ 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.
+ </para>
+ <para>
+ 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:
+ </para>
+ <para>
+ <command>auditctl -e 1</command>
+ </para>
+ </section>
+ <section id="sn-nptl">
+ <title>LinuxThreads versus NPTL</title>
+ <para>
+ As the next step in removing support for the obsolete
+ LinuxThreads library, code compiled and linked on &FC;
+ &LOCALVER; now automatically uses the NPTL headers and
+ libraries.
+ </para>
+ <para>
+ In previous releases since &RHL; 9, the default threading was
+ LinuxThreads since the interface is mostly forward compatible.
+ The advantages of the NPTL interface is that the cancellation
+ handling is faster (when <parameter>-fexception</parameter> 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
+ <option>-I/usr/include/nptl</option> and
+ <option>-L/usr/lib{,64}/nptl</option> any longer. Note
+ that <parameter>lib{,64}</parameter> is to be interpreted as
+ lib64 on platforms which place DSOs in
+ <filename>lib64/</filename> directories, and
+ <filename>lib/</filename> otherwise.
+ </para>
+ <para>
+ In &FC; &LOCALVER; it is still possible to create code using the
+ LinuxThreads definitions. For this the
+ <filename>linuxthreads-devel</filename> package must be
+ installed and
+ </para>
+ <para>
+ <option>-I/usr/include/linuxthreads
+ -L/usr/lib{,64}/linuxthreads</option>
+ </para>
+ <para>
+ must be passed to the compiler.
+ </para>
+ <para>
+ Previously, you could select the version of glibc and the
+ libpgthread DSH using run time environment variables. You now
+ need to also specify this variable in the environment:
+ </para>
+ <para>
+ <envar>LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads</envar>
+ </para>
+ <para>
+ This additional variables is required because the run/time
+ libraries have 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).
+ </para>
+ <para>
+ All this makes it more cumbersome to run programs which depend
+ on LinuxThreads. But this is intentional.
+ </para>
+ <important>
+- <title>Important</title>
+ <para>
+ FC5 will not have LinuxThreads support and all programs have
+ to be converted to use NPTL by then.
+ </para>
+ </important>
+ <para>
+ In general, conversion to using NPTL has not been an issue.
+ </para>
+ </section>
+ <section>
+ <title>Enabling the <filename>slocate</filename> Database</title>
+ <para>
+ The database needed by the locate utility is no longer created
+ by default. Enable the database creation by setting
+ <computeroutput>DAILY_UPDATE</computeroutput> to
+ <option>yes</option> in <filename>/etc/updatedb.conf</filename>
+ if you want to use locate.
+ </para>
+ </section>
+ <section>
+ <title>Stricter Controls in <filename>openssh</filename></title>
+ <para>
+ The version of OpenSSH in &FC; &LOCALVER; is based on OpenSSH
+ 3.9 and includes strict permission and ownership checks for the
+ user configuration file <filename>~/.ssh/config</filename>. If
+ this file does not have appropriate ownership and permissions,
+ <command>ssh</command> will exit.
+ </para>
+ <para>
+ Check that <filename>~/.ssh/config</filename> is owned by the
+ owner of <filename>~/</filename>, and that its permissions are
+ set to mode 600.
+ </para>
+<screen>
+ls -l ~/.ssh/config
+-rw------- 1 username username 400 May 5 18:44 /home/username/.ssh/config
+</screen>
+ <para>
+ The directory <filename>~/</filename> is command-line shorthand
+ for the logged in user's home directory, usually
+ <filename>/home/username/</filename>.
+ </para>
+ <para>
+ In addition, OpenSSH is no longer configured to request X11
+ forwarding by default when connecting to servers. To enable X11
+ forwarding, the <option>-X</option> or <option>-Y</option>
+ option must be specified, or the <option>ForwardX11</option>
+ option must be enabled in the <filename>~/.ssh/config</filename>
+ file.
+ </para>
+ <para>
+ The behavior of <command>ssh</command> clients that are invoked
+ with the <option>-X</option> option 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
+ <option>-Y</option> option instead of the <option>-X</option>
+ option, or set <option>ForwardX11Trusted</option> in the
+ <option>~/.ssh/config</option> file.
+ </para>
+ </section>
+</section>
+<!-- Saving these just in case ...
<section os="bogus">
<title>Administration Tools</title>
@@ -221,48 +214,6 @@
</section>
- <section>
- <title>Base</title>
-
- <para>This section contains information related to basic system
- components.</para>
-
- <section>
- <title><filename>openssh</filename></title>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131544">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131544</ulink>
- %%%</remark>
-
- <para>&DISTRO; &DISTROVER; contains OpenSSH 3.9, which includes strict
- permission and ownership checks for the
- <filename>~/.ssh/config</filename> file. These checks mean that
- <command>ssh</command> will exit if this file does not have
- appropriate ownership and permissions.</para>
-
- <para>Therefore, make sure that <filename>~/.ssh/config</filename> is
- owned by the owner of <filename>~/</filename>, and that its
- permissions are set to mode 600.</para>
-
- <para>In addition, OpenSSH is no longer configured to request X11
- forwarding by default when connecting to servers. To enable X11
- forwarding, the <command>-X</command> or <command>-Y</command> option
- must be specified, or the <command>ForwardX11</command> option must be
- enabled in the <filename>~/.ssh/config</filename> file.</para>
-
- <para>The behavior of ssh clients that are invoked with the
- <command>-X</command> 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
- <command>-Y</command> flag instead of the <command>-X</command> flag,
- or set <command>ForwardX11Trusted</command> in the
- <filename>~/.ssh/config</filename> file.</para>
- </section>
- </section>
-
<section os="bogus">
<title>Compatibility Arch Development Support</title>
@@ -276,13 +227,24 @@
<para>*** Enter group description here ***</para>
</section>
-
+-->
+ <section>
+ <title>Core</title>
+ <para>
+ This section contains the most elemental components of &DISTRO;,
+ including the kernel.
+ </para>
<section>
- <title>Core</title>
-
- <para>This section contains the most elemental components of &DISTRO;,
- including the kernel.</para>
-
+ <title>yum</title>
+ <para>
+ The sqllite database is now used by yum, and makes performance
+ noticeably faster.
+ </para>
+ <para>
+ The Fedora Extras repository is now enabled by default.
+ </para>
+</section>
+<!--
<section>
<title><filename>e2fsprogs</filename></title>
@@ -395,148 +357,127 @@
<filename>/lib/firmware</filename>. Existing firmware files must be
moved into the new directory.</para>
</section>
-
+ -->
<section>
<title><filename>kernel</filename></title>
-
- <itemizedlist>
- <listitem>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135586">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135586</ulink>
- %%%</remark>
-
- <para>In the past, the process of updating the kernel did not change
- the default kernel in the system's boot loader
- configuration.</para>
-
- <para>&DISTRO; &DISTROVER; changes this behavior to set
- newly-installed kernels as the default. This behavior applies to
- all installation methods (including <command>rpm
- -i</command>).</para>
-
- <para>This behavior is controlled by two lines in the
- <filename>/etc/sysconfig/kernel</filename> file:</para>
-
- <itemizedlist>
- <listitem>
- <para><command>UPDATEDEFAULT</command> — Controls whether
- new kernels will be booted by default (default value:
- <command>yes</command>)</para>
- </listitem>
-
- <listitem>
- <para><command>DEFAULTKERNEL</command> — kernel RPMs whose
- names match this value will be booted by default (default
- value: depends on hardware configuration)</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
-
+<!-- still don't entirely grok the use of these sections, leaving them -->
+<!-- for now commented out but available.
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135269">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135269</ulink>
%%%</remark>
-
- <para>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 <filename>.src.rpm</filename> file,
- &DISTRO; &DISTROVER; no longer includes the
- <filename>kernel-source</filename> package. Users that require
- access to the kernel sources can find them in the
- <filename>kernel</filename> <filename>.src.rpm</filename> file.
- To create an exploded source tree from this file, perform the
- following steps (note that
- <filename><replaceable><version></replaceable></filename>
- refers to the version specification for your currently-running
- kernel):</para>
-
- <orderedlist>
- <listitem>
- <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 "SRPMS" CD iso image</para>
- </listitem>
-
- <listitem>
- <para>The FTP site where you got the kernel package</para>
- </listitem>
-
- <listitem>
- <para>By running the following command:</para>
-
- <para><command>up2date --get-source kernel</command></para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>Install
- <filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
- (given the default RPM configuration, the files this package
- contains will be written to
- <filename>/usr/src/redhat/</filename>)</para>
- </listitem>
-
- <listitem>
- <para>Change directory to
- <filename>/usr/src/redhat/SPECS/</filename>, and issue the
- following command:</para>
-
- <para><command>rpmbuild -bp
- --target=<replaceable><arch></replaceable>
- kernel.spec</command></para>
-
- <para>(Where
- <command><replaceable><arch></replaceable></command> is
- the desired target architecture.)</para>
-
- <para>On a default RPM configuration, the kernel tree will be
- located in <filename>/usr/src/redhat/BUILD/</filename>.</para>
-
- </listitem>
-
- <listitem>
- <para>In resulting tree, 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
- <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>
-
- <para><command>cp
- <replaceable><desired-file></replaceable>
- ./.config</command></para>
- </listitem>
-
- <listitem>
- <para>Issue the following command:</para>
-
- <para><command>make oldconfig</command></para>
- </listitem>
- </orderedlist>
-
- <para>You can then proceed as usual.</para>
-
- <note>
- <title>Note</title>
-
- <para>An exploded source tree is <emphasis>not</emphasis> required
- to build kernel modules against the currently in-use kernel.</para>
-
- <para>For example, to build the <filename>foo.ko</filename>
- module, create the following file (named
- <filename>Makefile</filename>) in the directory containing the
- <filename>foo.c</filename> file:</para>
-
- <screen>
+-->
+ <para>
+ 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 <filename>.src.rpm</filename> file,
+ &DISTRO; &DISTROVER; no longer includes the
+ <filename>kernel-source</filename> package. Users that require
+ access to the kernel sources can find them in the
+ <filename>kernel</filename> <filename>.src.rpm</filename> file. To
+ create an exploded source tree from this file, perform the
+ following steps (note that
+ <filename><replaceable><version></replaceable></filename>
+ refers to the version specification for your currently-running
+ kernel):
+ </para>
+ <orderedlist>
+ <listitem>
+ <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 "SRPMS" CD iso image
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The FTP site where you got the kernel package
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ By running the following command:
+ </para>
+ <para>
+ <command>up2date --get-source kernel</command>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ Install
+ <filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
+ (given the default RPM configuration, the files this package
+ contains will be written to
+ <filename>/usr/src/redhat/</filename>)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Change directory to
+ <filename>/usr/src/redhat/SPECS/</filename>, and issue the
+ following command:
+ </para>
+ <para>
+ <command>rpmbuild -bp
+ --target=<replaceable><arch></replaceable>
+ kernel.spec</command>
+ </para>
+ <para>
+ (Where
+ <command><replaceable><arch></replaceable></command> is
+ the desired target architecture.)
+ </para>
+ <para>
+ On a default RPM configuration, the kernel tree will be
+ located in <filename>/usr/src/redhat/BUILD/</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In the resulting tree, 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
+ <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>
+ <para>
+ <command>cp <replaceable><desired-file></replaceable>
+ ./.config</command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Issue the following command:
+ </para>
+ <para>
+ <command>make oldconfig</command>
+ </para>
+ </listitem>
+ </orderedlist>
+ <para>
+ You can then proceed as usual.
+ </para>
+ <tip>
+ <title>Source not required to build kernel modules</title>
+ <para>
+ An exploded source tree is <emphasis>not</emphasis> required to
+ build kernel modules against the currently in-use kernel.
+ </para>
+ <para>
+ For example, to build the <filename>foo.ko</filename> module,
+ create the following file (named <filename>Makefile</filename>)
+ in the directory containing the <filename>foo.c</filename> file:
+ </para>
+<screen>
<computeroutput>
obj-m := foo.o
@@ -546,46 +487,15 @@
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
</computeroutput>
- </screen>
-
- <para>Issue the <command>make</command> command to build the
- <filename>foo.ko</filename> module.</para>
- </note>
- </listitem>
-
- <listitem>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136770">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136770</ulink>
- %%%</remark>
-
- <para>I<subscript>2</subscript>O SCSI RAID adapters from
- manufacturers such as Adaptec now use the
- <filename>i2o_block</filename> driver, rather than the
- <filename>dpt_i2o</filename> driver used by &DISTRO; 1 and earlier
- distributions.</para>
-
- <para>Be aware that block devices used by the
- <filename>i2o_block</filename> driver are
- <filename>/dev/i2o/hd*</filename> rather than the
- <filename>/dev/sd*</filename> SCSI devices. This may be
- problematic for those upgrading from older distributions that used
- the <filename>dpt_i2o</filename> driver. Therefore, after an
- upgrade to &DISTRO; &DISTROVER;, you may need to boot using a
- rescue disk and edit your <filename>/etc/fstab</filename> file to
- use the new devices.</para>
-
- <para>For more information about the new I<subscript>2</subscript>O
- device layer and &DISTRO;-specific notes, visit the
- I<subscript>2</subscript>O homepage:</para>
-
- <para><ulink
- url="http://i2o.shadowconnect.com/">http://i2o.shadowconnect.com/</ulink></para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
-
+</screen>
+ <para>
+ Issue the <command>make</command> command to build the
+ <filename>foo.ko</filename> module.
+ </para>
+ </tip>
+ </section>
+</section>
+<!--
<section os="bogus">
<title>DNS Name Server</title>
@@ -726,17 +636,107 @@
<para>*** Enter group description here ***</para>
</section>
-
+-->
+ <section>
+ <title>Language Support</title>
+ <para>
+ This section includes information related to the support of various
+ languages under &DISTRO;.
+ </para>
<section>
- <title>Language Support</title>
-
- <para>This section includes information related to the support of various
- languages under &DISTRO;.</para>
-
-
- <section>
- <title><filename>iiimf</filename></title>
-
+ <title>The IIIMF Input System</title>
+ <para>
+ IIIMF is the Internet/Intranet Input Method Framework. In &FC;
+ &LOCALVER; the <filename>iiimf</filename> package is updated to
+ version 12.2.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Filepath Changes</term>
+ <listitem>
+ <para>
+ The name 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>
+<!-- keeping for historical informative purpose as a resource
<itemizedlist>
<listitem>
@@ -844,8 +844,9 @@
</listitem>
</itemizedlist>
</section>
+ -->
</section>
-
+<!--
<section os="bogus">
<title>Legacy Software Development</title>
@@ -903,7 +904,6 @@
</itemizedlist>
</section>
</section>
-
<section os="bogus">
<title>Network Servers</title>
@@ -924,192 +924,51 @@
<para>*** Enter group description here ***</para>
</section>
-
- <section os="bogus">
- <title>Printing Support</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
+-->
+ &PRINTING;
+<!--
<section os="bogus">
<title>Ruby</title>
<para>*** Enter group description here ***</para>
</section>
-
- <section os="bogus">
- <title>SQL Database Server</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
<section os="bogus">
<title>Server</title>
<para>*** Enter group description here ***</para>
</section>
-
- <section>
- <title>Server Configuration Tools</title>
-
- <para>This section contains information related to various server
- configuration tools.</para>
-
- <section>
- <title><filename>system-config-securitylevel</filename></title>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135621">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135621</ulink>
- %%%</remark>
-
- <para>The firewall constructed by the
- <command>system-config-securitylevel</command> configuration tool now
- allows CUPS and Multicast DNS (mDNS) browsing. Note that, at the
- present time, these services cannot be disabled by
- <command>system-config-securitylevel</command>.</para>
- </section>
- </section>
-
- <section>
- <title>Sound and Video</title>
-
- <para>This section contains information related to multimedia
- applications.</para>
-
- <section>
- <title><filename>k3b</filename></title>
-
- <para>Past users of the CD/DVD burning application
- <application>k3b</application> may notice that the program
- <command>k3bsetup</command> is missing. This is because
- <command>k3bsetup</command> is not necessary under &DISTRO;
- &DISTROVER;.</para>
- </section>
- </section>
-
- <section os="bogus">
- <title>Supported Packages</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section os="bogus">
- <title>System Tools</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
+-->
+ &DATABASE-SERVERS;
+ &SERVER-TOOLS;
+ &MULTIMEDIA;
+<!--
+ <section os="bogus">
+ <title>Supported Packages</title>
+
+ <para>*** Enter group description here ***</para>
+
+ </section>
+
<section os="bogus">
- <title>Text-based Internet</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
- <section>
- <title>Web Server</title>
-
- <para>This section contains information related to Web-related
- tools.</para>
-
- <section>
- <title><filename>crypto-utils</filename></title>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136312">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136312</ulink>
- %%%</remark>
-
- <para>The <command>certwatch(1)</command> tool has been added to the
- <filename>crypto-utils</filename> package. This tool is used to send
- warning mail to root when any configured SSL certificates have expired
- or are approaching the expiration date. By default, the tool checks
- any certificates that are enabled in the <filename>mod_ssl</filename>
- configuration.</para>
- </section>
-
- <section>
- <title><filename>httpd</filename></title>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136469">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136469</ulink>
- %%%</remark>
-
- <para>By default, the <command>httpd</command> daemon is now started
- using the C locale, rather than using the configured system locale
- setting. This behavior can be changed by setting the
- <envar>HTTPD_LANG</envar> variable in the
- <filename>/etc/sysconfig/httpd</filename> file.</para>
- </section>
-
- <section>
- <title><filename>php</filename></title>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131440">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131440</ulink>
- %%%</remark>
-
- <para>The gd, mbstring, and ncurses extensions have been moved to the
- <filename>php-gd</filename>, <filename>php-mbstring</filename>, and
- <filename>php-ncurses</filename> packages, respectively. Note that
- you will need to install these packages manually (if required) when
- upgrading from an earlier release.</para>
-
- </section>
- </section>
-
- <section>
- <title>Windows File Server</title>
-
- <para>This section contains information related to Samba, software that
- makes it possible to share files between Linux and Windows
- systems.</para>
-
- <section>
- <title><filename>samba</filename></title>
-
- <para>Browsing of Windows shares (also known as SMB browsing) fails on
- &DISTRO; &DISTROVER; systems that have the standard firewall
- configured. This is most easily noticed in the failure of Nautilus to
- display shares. The failure is due to the firewall disrupting the
- broadcast mode of SMB browsing, which is Samba's default setting.
- There are two workarounds:</para>
-
- <itemizedlist>
- <listitem>
- <para>Configure a WINS server on the network, and set the "wins
- server" option in <filename>smb.conf</filename> to the address of
- the WINS server.</para>
- </listitem>
-
- <listitem>
- <para>Disable the firewall</para>
- </listitem>
- </itemizedlist>
-
- <warning>
- <title>Warning</title>
-
- <para>Depending on your system and network configurations, disabling
- the firewall can greatly increase the chance of your system being
- attacked and compromised. Make sure you <emphasis>fully</emphasis>
- understand the risks before undertaking this step.</para>
- </warning>
-
- <para>For additional information, refer to the following bug
- report:</para>
-
- <para><ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478</ulink></para>
- </section>
- </section>
+ <title>System Tools</title>
+
+ <para>*** Enter group description here ***</para>
+
+ </section>
+
+ <section os="bogus">
+ <title>Text-based Internet</title>
+
+ <para>*** Enter group description here ***</para>
- <section os="bogus">
+ </section>
+ -->
+ &WEB-SERVERS;
+ &SAMBA;
+ &XORG;
+<!-- <section os="bogus">
<title>Workstation Common</title>
<para>*** Enter group description here ***</para>
@@ -1123,317 +982,15 @@
</section>
- <section>
- <title>X Window System</title>
-
- <para>This section contains information related to the X Window System
- implementation provided with &DISTRO;.</para>
-
- <section>
- <title><filename>xorg-x11</filename></title>
-
- <itemizedlist>
- <listitem>
- <para>Users new to the X.org X11 implementation should take note of
- a few differences between it and the XFree86.org X11
- implementation which shipped in previous &RH; operating systems.
- In particular, the names of some files have changed:</para>
-
- <para>X Server Binary:</para>
-
- <itemizedlist>
- <listitem>
- <para>XFree86 X11: <filename>XFree86</filename></para>
- </listitem>
-
- <listitem>
- <para>X.org X11: <filename>Xorg</filename></para>
- </listitem>
- </itemizedlist>
-
- <para>X Server Configuration File:</para>
-
- <itemizedlist>
- <listitem>
- <para>XFree86 X11:
- <filename>/etc/X11/XF86Config</filename></para>
- </listitem>
-
- <listitem>
- <para>X.org X11: <filename>/etc/X11/xorg.conf</filename></para>
- </listitem>
- </itemizedlist>
-
- <para>X Server Log File</para>
-
- <itemizedlist>
- <listitem>
- <para>XFree86 X11:
- <filename>/var/log/XFree86.<replaceable>$DISPLAY</replaceable>.log</filename></para>
- </listitem>
-
- <listitem>
- <para>X.org X11:
- <filename>/var/log/Xorg.<replaceable>$DISPLAY</replaceable>.log</filename></para>
- </listitem>
- </itemizedlist>
-
- <para>When configuring or troubleshooting your X server
- configuration, be sure that you are using the correct
- files.</para>
- </listitem>
-
- <listitem>
- <para>There has been some confusion regarding font-related issues
- under the X Window System in recent versions of &DISTRO; (and
- versions of &RHL; before it.) At the present time, there are two
- font subsystems, each with different characteristics:</para>
-
- <para>- The original (15+ year old) subsystem is referred to as the
- "core X font subsystem". Fonts rendered by this subsystem are not
- anti-aliased, are handled by the X server, and have names
- like:</para>
-
- <para>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</para>
-
- <para>The newer font subsystem is known as "fontconfig", and allows
- applications direct access to the font files. Fontconfig is often
- used along with the "Xft" library, which allows applications to
- render fontconfig fonts to the screen with antialiasing.
- Fontconfig uses more human-friendly names like:</para>
-
- <para>Luxi Sans-10</para>
-
- <para>Over time, fontconfig/Xft will replace the core X font
- subsystem. At the present time, applications using the Qt 3 or
- GTK 2 toolkits (which would include KDE and GNOME applications)
- use the fontconfig and Xft font subsystem; most everything else
- uses the core X fonts.</para>
-
- <para>In the future, &DISTRO; may support only fontconfig/Xft in
- place of the XFS font server as the default local font access
- method.</para>
-
- <para>NOTE: An exception to the font subsystem usage outlined above
- is OpenOffice.org (which uses its own font rendering
- technology).</para>
-
- <para>If you wish to add new fonts to your &DISTRO; &DISTROVER;
- system, you must be aware that the steps necessary depend on which
- font subsystem is to use the new fonts. For the core X font
- subsystem, you must:</para>
-
- <para>1. Create the <filename>/usr/share/fonts/local/</filename>
- directory (if it doesn't already exist):</para>
-
- <para><command>mkdir /usr/share/fonts/local/</command></para>
-
- <para>2. Copy the new font file into
- <filename>/usr/share/fonts/local/</filename></para>
-
- <para>3. Update the font information by issuing the following
- commands (note that, due to formatting restrictions, the following
- commands may appear on more than one line; in use, each command
- should be entered on a single line):</para>
-
- <para><command>ttmkfdir -d /usr/share/fonts/local/ -o
- /usr/share/fonts/local/fonts.scale</command></para>
-
- <para><command>mkfontdir /usr/share/fonts/local/</command></para>
-
- <para>4. If you had to create
- <filename>/usr/share/fonts/local/</filename>, you must then add it
- to the X font server (xfs) path:</para>
-
- <para><command>chkfontpath --add
- /usr/share/fonts/local/</command></para>
-
- <para>Adding new fonts to the fontconfig font subsystem is more
- straightforward; the new font file only needs to be copied into
- the <filename>/usr/share/fonts/</filename> directory (individual
- users can modify their personal font configuration by copying the
- font file into the <filename>~/.fonts/</filename>
- directory).</para>
-
- <para>After the new font has been copied, use
- <command>fc-cache</command> to update the font information
- cache:</para>
-
- <para><command>fc-cache
- <replaceable><directory></replaceable></command></para>
-
- <para>(Where
- <command><replaceable><directory></replaceable></command>
- would be either the <filename>/usr/share/fonts/</filename> or
- <filename>~/.fonts/</filename> directories.)</para>
-
- <para>Individual users may also install fonts graphically, by
- browsing <command>fonts:///</command> in
- <application>Nautilus</application>, and dragging the new font
- files there.</para>
-
- <para>NOTE: If the font filename ends with
- "<filename>.gz</filename>", it has been compressed with
- <command>gzip</command>, and must be decompressed (with the
- <command>gunzip</command> command) before the fontconfig font
- subsystem can use the font.</para>
- </listitem>
-
- <listitem>
- <para>Due to the transition to the new font system based on
- fontconfig/Xft, GTK+ 1.2 applications are not affected by any
- changes made via the <guilabel>Font Preferences</guilabel> dialog.
- For these applications, a font can be configured by adding the
- following lines to the file
- <filename>~/.gtkrc.mine</filename>:</para>
-
- <para><command>style "user-font" {</command></para>
- <para><command>fontset =
- "<replaceable><font-specification></replaceable>"</command></para>
- <para><command>}</command></para>
- <para><computeroutput> </computeroutput></para>
- <para><computeroutput>widget_class "*" style "user-font"</computeroutput></para>
-
- <para>(Where
- <command><replaceable><font-specification></replaceable></command>
- represents a font specification in the style used by traditional X
- applications, such as
- "<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>".)</para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
-
<section os="bogus">
<title>XEmacs</title>
<para>*** Enter group description here ***</para>
</section>
-
- <section>
- <title>Miscellaneous Notes</title>
-
- <para>This section contains information related to packages that do not
- fit in any of the proceeding categories.</para>
-
- <section>
- <title><filename>compat-db</filename></title>
-
- <remark os="test">%%% <ulink
- url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133553">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133553</ulink>
- %%%</remark>
-
- <para>C++ and TCL bindings are no longer contained in the
- <filename>compat-db</filename> package. Applications requiring these
- bindings must be ported to the currently-shipping DB library.</para>
- </section>
-
- <section>
- <title><filename>nscd</filename></title>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131389">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131389</ulink>
- %%%</remark>
-
- <para>The nscd name service cache daemon may now maintain a persistent
- cache across restarts or system reboots. Each database (user, group,
- and host, respectively) can be made selected to be persistent by
- setting the appropriate line in <filename>/etc/nscd.conf</filename> to
- "yes". Entries are not removed from the cache until they are proven
- to be no longer of interest. All entries whose time-to-live expires
- but are otherwise interesting are automatically reloaded, which helps
- in situations where the directory and name services become temporarily
- unavailable.</para>
-
- <para>The nscd name service daemon is also able to communicate faster
- with client programs. This feature must be enabled explicitly by
- setting the "shared" entry for the appropriate database in
- <filename>/etc/nscd.conf</filename> to "yes".</para>
- </section>
-
- <section>
- <title><filename>udev</filename></title>
-
- <remark os="test">%%% <ulink
- url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133269">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133269</ulink>
- %%%</remark>
-
- <para>&DISTRO; &DISTROVER; has switched from a static
- <filename>/dev/</filename> directory to one that is dynamically
- managed via <filename>udev</filename>. This allows device nodes to be
- created on demand as drivers are loaded.</para>
-
- <para>For more information on <filename>udev</filename>, refer to the
- <command>udev(8)</command> man page and the following link:</para>
-
- <para><ulink
- url="http://people.redhat.com/~harald/udev.html">http://people.redhat.com/~harald/udev.html</ulink></para>
-
- <para>Additional rules for <filename>udev</filename> should be placed in
- a separate file in the <filename>/etc/udev/rules.d/</filename>
- directory.</para>
-
- <para>Additional permission rules for <filename>udev</filename> should
- be placed in a separate file in the
- <filename>/etc/udev/permissions.d/</filename> directory.</para>
-
- <para>Systems upgraded to &DISTRO; &DISTROVER; using Anaconda will
- automatically be reconfigured to use <filename>udev</filename>.
- However (although <emphasis>NOT</emphasis> recommended) it is possible
- to perform a "live" upgrade to <filename>udev</filename> using the
- following steps:</para>
-
- <orderedlist>
- <listitem>
- <para>Ensure that you are running a 2.6 kernel</para>
- </listitem>
-
- <listitem>
- <para>Ensure that <filename>/sys/</filename> is mounted</para>
- </listitem>
-
- <listitem>
- <para>Install the <filename>initscripts</filename> RPM supplied with
- &DISTRO; &DISTROVER;</para>
- </listitem>
-
- <listitem>
- <para>Install the new <filename>udev</filename> RPM supplied with
- &DISTRO; &DISTROVER;</para>
- </listitem>
-
- <listitem>
- <para>Execute <command>/sbin/start_udev</command></para>
- </listitem>
-
- <listitem>
- <para>Install the new <filename>mkinitrd</filename> RPM supplied
- with &DISTRO; &DISTROVER;</para>
- </listitem>
-
- <listitem>
- <para>Perform one of the following steps:</para>
-
- <para>· Install the new <filename>kernel</filename> RPM
- supplied with &DISTRO; &DISTROVER;</para>
-
- <para>OR:</para>
-
- <para>· Re-run <command>mkinitrd</command> for your existing
- kernel(s)</para>
- </listitem>
- </orderedlist>
-
- <warning>
- <title>Warning</title>
-
- <para>Improperly performing these steps can result in a system
- configuration that will not boot properly.</para>
- </warning>
- </section>
- </section>
+ -->
</section>
+</section>
<!--
Local variables:
mode: xml
Index: samba.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/samba.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- samba.xml 29 May 2005 19:22:20 -0000 1.5
+++ samba.xml 30 May 2005 14:41:46 -0000 1.6
@@ -1,6 +1,6 @@
<section id="sn-samba">
- <title>Samba (Windows Compatibility)</title>
-
+ <title>Samba (Windows Compatibility)</title>
+
<para>
This section contains information related to Samba, the suite
of software that enables Linux to interact with Microsoft Windows
@@ -19,32 +19,36 @@
default. There are two workarounds:
</para>
- <itemizedlist>
- <listitem>
- <para>Configure a WINS server on the network, and set the "wins server"
- option in smb.conf to the address of the WINS server.</para>
- </listitem>
- <listitem>
- <para>Disable the firewall.</para>
- </listitem>
- </itemizedlist>
-
- <warning>
- <title>Disabling the firewall may make your system vulnerable</title>
+ <itemizedlist>
+ <listitem>
<para>
- Make sure you fully understand the risks before undertaking this
- step.
- </para>
- </warning>
-
- <para>
- For additional information, refer to the following bug report:
- </para>
+ Configure a WINS server on the network, and set the "wins
+ server" option in smb.conf to the address of the WINS server.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Disable the firewall.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <warning>
+ <title>Disabling the firewall may make your system vulnerable</title>
<para>
- <ulink url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478</ulink>
+ Make sure you fully understand the risks before undertaking this
+ step.
</para>
+ </warning>
+ <para>
+ For additional information, refer to the following bug report:
+ </para>
+
+ <para>
+ <ulink url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478</ulink>
+ </para>
+</section>
<!--
Local variables:
mode: xml
Index: splash.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/splash.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- splash.xml 29 May 2005 19:43:11 -0000 1.2
+++ splash.xml 30 May 2005 14:41:46 -0000 1.3
@@ -10,7 +10,7 @@
<itemizedlist>
<listitem>
<para>
- <xref linkend="sn-what-is-new"/>
+ <xref linkend="sn-new-in-fc"/>
</para>
</listitem>
<listitem>
@@ -43,8 +43,8 @@
</para>
</listitem>
</itemizedlist>
- <section id="sn-what-is-new">
- <title>What is New in &FC; &LOCALVER;</title>
+ <section id="sn-new-in-fc">
+ <title>New in &FC; &LOCALVER;</title>
<para>
&FC; &LOCALVER; is the latest version of the free and popular &FC;
platform with a number of unique features and significant
Index: web-servers.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/web-servers.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- web-servers.xml 29 May 2005 20:05:27 -0000 1.7
+++ web-servers.xml 30 May 2005 14:41:46 -0000 1.8
@@ -16,62 +16,63 @@
<ulink
url="http://perl.apache.org/docs/2.0/rename.html">http://perl.apache.org/docs/2.0/rename.html</ulink>
</para>
- <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. Please refer to the PHP documentation for more
- 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>dba</command> extension, now available in the
- <filename>php-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>
+ <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. Please refer to the PHP documentation for more
+ 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>dba</command> extension, now available in the
+ <filename>php-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