release-notes/FC4 package-notes.xml,1.15,1.16
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Tue Jun 7 08:23:42 UTC 2005
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22916
Modified Files:
package-notes.xml
Log Message:
Snapshot interim of this file because of all the whitespace changes for reindenting. There is some meat in this check-in, sorry for burying it. Next commit will be purely editing.
Index: package-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/package-notes.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- package-notes.xml 1 Jun 2005 00:02:35 -0000 1.15
+++ package-notes.xml 7 Jun 2005 08:23:40 -0000 1.16
@@ -34,8 +34,8 @@
<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.
+ easier access, they are generally organized using the same groups
+ used in Anaconda.
</para>
<section id="sn-basic-components">
@@ -47,193 +47,194 @@
<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.
+ &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:
+ 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>.
+ <ulink
+ url="http://fedoraproject.org/wiki/Extras">http://fedoraproject.org/wiki/Extras</ulink>
</para>
<para>
- <command>yum install <replaceable><packagename></replaceable></command>
+ If you would like to install any software available from
+ Fedora extras you can use <command>yum</command>.
</para>
+<screen>
+<command>yum install <replaceable><packagename></replaceable></command>
+</screen>
<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.
+ 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>
+ Files</title>
<para>
- AVC messages for SELinux are sent using the audit
- infrastructure. These messages are now in
- /var/log/audit/audit.log.
+ The audit daemon, auditd, is now enabled by default. When
+ auditd is running, the kernel directs audit messages to
+ <filename>/var/log/audit/audit.log</filename>. The location of this file is
+ specified in <filename>/etc/auditd.conf</filename>.
</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.
+ AVC messages for &SEL; are sent using the audit infrastructure.
+ These messages are now in
+ <filename>/var/log/audit/audit.log</filename>.
</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.
+ When auditd is not running, the kernel passes audit messages to
+ syslog. These logs are typically kept in <filename>/var/log/messages</filename> and
+ are viewable using <command>dmesg</command>.
</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:
+ 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>
- <command>auditctl -e 1</command>
+ To enable auditing within the kernel, you must pass the
+ parameter <parameter>audit=1</parameter> to the kernel during
+ boot. Otherwise, you can use this command to enable auditing
+ during run time:
</para>
+<screen>
+<command>auditctl -e 1</command>
+</screen>
</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>
+ 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>
+<screen>
+<option>-I/usr/include/linuxthreads -L/usr/lib{,64}/linuxthreads</option>
+</screen>
<para>
- must be passed to the compiler.
+ 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>
+ 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>
+<screen>
+<envar>LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads</envar>
+</screen>
<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).
+ This additional variable is required because the run/time
+ libraries have been moved out of the way. There may be 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.
+ 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>
+ <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.
+ 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.
+ The database needed by the <command>locate</command> 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 <command>locate</command>.
</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.
+ 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.
+ 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.
+ 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 id="sn-perl">
<title>Perl Binary Compat Symlinks</title>
<para>
- Binary compat symlinks for <filename>perl-5.8.0</filename>,
- <filename>perl-5.8.1</filename>, and
- <filename>perl-5.8.2</filename> have been removed. If you have
- perl modules built with those older versions of perl, you need
- to rebuild using the <filename>perl-5.8.6</filename> contained
- in &FC; &LOCALVER;.
+ Binary compat symlinks for <filename>perl-5.8.0</filename>,
+ <filename>perl-5.8.1</filename>, and
+ <filename>perl-5.8.2</filename> have been removed. If you have
+ perl modules built with those older versions of perl, you need
+ to rebuild using the <filename>perl-5.8.6</filename> contained
+ in &FC; &LOCALVER;.
</para>
</section>
&SERVER-TOOLS;
@@ -277,11 +278,11 @@
<section>
<title>yum</title>
<para>
- The sqllite database is now used by yum, and makes performance
- noticeably faster.
+ The sqllite database is now used by yum, and makes performance
+ noticeably faster.
</para>
<para>
- The Fedora Extras repository is now enabled by default.
+ The Fedora Extras repository is now enabled by default.
</para>
</section>
&KERNEL;
More information about the Fedora-docs-commits
mailing list