Author: pfrields
Update of /cvs/docs/release-notes/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2270/en
Modified Files:
ArchSpecificx86_64.xml BackwardsCompatibility.xml Desktop.xml
Extras.xml I18n.xml Java.xml Kernel.xml Networking.xml
PackageChanges.xml Security.xml ServerTools.xml
Log Message:
Clean up screen elements, removing unnecessary itemizedlists, and truncate package change
lists to look good on screens not a mile wide
Index: ArchSpecificx86_64.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/ArchSpecificx86_64.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- ArchSpecificx86_64.xml 28 Feb 2006 21:45:48 -0000 1.5
+++ ArchSpecificx86_64.xml 28 Feb 2006 22:38:45 -0000 1.6
@@ -35,19 +35,9 @@
<title>RPM Multiarch Support on x86_64</title>
<para>
<emphasis role='strong'>RPM</emphasis> supports parallel
installation of multiple architectures of the same package. A default package listing
such as <code>rpm -qa</code> might appear to include duplicate packages, since
the architecture is not displayed. Instead, use the <code>repoquery</code>
command, part of the <code>yum-utils</code> package in Fedora Extras, which
displays architecture by default. To install <code>yum-utils</code>, run the
following command: </para>
- <itemizedlist>
- <listitem>
- <screen>su -c 'yum install yum-utils' </screen>
- </listitem>
- </itemizedlist>
+ <screen>su -c 'yum install yum-utils' </screen>
<para>To list all packages with their architecture using
<code>rpm</code>, run the following command: </para>
- <itemizedlist>
- <listitem>
- <screen>rpm -qa --queryformat
"%{name}-%{version}-%{release}.%{arch}\n" </screen>
- <para>
- </para>
- </listitem>
- </itemizedlist>
+ <screen>rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n"
</screen>
</section>
</section>
</section>
Index: BackwardsCompatibility.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/BackwardsCompatibility.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- BackwardsCompatibility.xml 28 Feb 2006 21:45:48 -0000 1.4
+++ BackwardsCompatibility.xml 28 Feb 2006 22:38:45 -0000 1.5
@@ -9,11 +9,7 @@
<section>
<title>Backwards Compatibility</title>
<para>Fedora Core provides legacy system libraries for compatibility with
older software. This software is part of the <emphasis role='strong'>Legacy
Software Development</emphasis> group, which is not installed by default. Users who
require this functionality may select this group either during installation, or after the
installation process is complete. To install the package group on a Fedora system, use
<emphasis>Applications=>Add/Remove Software</emphasis>, <emphasis
role='strong'>Pirut</emphasis> or enter the following command in a
terminal window: </para>
- <itemizedlist>
- <listitem>
- <screen>su -c 'yum groupinstall "Legacy Software
Development"'</screen>
- </listitem>
- </itemizedlist>
+ <screen>su -c 'yum groupinstall "Legacy Software
Development"'</screen>
<para>Enter the password for the <code>root</code> account when
prompted. </para>
</section>
</section>
Index: Desktop.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Desktop.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- Desktop.xml 28 Feb 2006 21:45:48 -0000 1.6
+++ Desktop.xml 28 Feb 2006 22:38:45 -0000 1.7
@@ -33,19 +33,11 @@
</listitem>
<listitem>
<para> Starting with GNOME 2.12, the terminal option has been removed from
the desktop context menu. The <code>nautilus-open-terminal</code> package in
Fedora Extras provides a enhanced replacement for those who require it. You can install it
with the following command. </para>
- <itemizedlist>
- <listitem>
- <screen>su -c 'yum install
nautilus-open-terminal'</screen>
- </listitem>
- </itemizedlist>
+ <screen>su -c 'yum install nautilus-open-terminal'</screen>
</listitem>
<listitem>
<para> In Fedora Core 5, only a small assortment of screensavers is
installed by default. Some users find certain screensavers unpleasant, and other
screensavers may abruptly terminate the graphical interface. This tends to happen more
often with OpenGL animated screensavers provided within the
<code>xscreensaver-gl-extras</code> package, when used with poorly-supported
video hardware. To install these extra screensavers, run the following command:
</para>
- <itemizedlist>
- <listitem>
- <screen>su -c 'yum install xscreensaver-extras
xscreensaver-gl-extras'</screen>
- </listitem>
- </itemizedlist>
+ <screen>su -c 'yum install xscreensaver-extras
xscreensaver-gl-extras'</screen>
</listitem>
</itemizedlist>
</section>
Index: Extras.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Extras.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Extras.xml 28 Feb 2006 21:45:48 -0000 1.4
+++ Extras.xml 28 Feb 2006 22:38:45 -0000 1.5
@@ -16,11 +16,7 @@
</tip>
<para>To install software from either the Core or Extras repositories, choose
<emphasis>Applications > Add/Remove Software</emphasis>. Enter the
<code>root</code> password when prompted. Select the software you require from
the list, and choose <emphasis>Apply</emphasis>. </para>
<para>Alternatively, you may install software with the
<code>yum</code> command-line utility. For example, this command automatically
installs the <code>abiword</code> package, and all of the dependencies that
are required: </para>
- <itemizedlist>
- <listitem>
- <screen>su -c 'yum install abiword' </screen>
- </listitem>
- </itemizedlist>
+ <screen>su -c 'yum install abiword' </screen>
<para>Enter the <code>root</code> password when prompted.
</para>
</section>
<section>
Index: I18n.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/I18n.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- I18n.xml 28 Feb 2006 21:45:48 -0000 1.5
+++ I18n.xml 28 Feb 2006 22:38:45 -0000 1.6
@@ -13,11 +13,7 @@
<section>
<title>Installation</title>
<para>SCIM should be installed and run by default for Asian language
desktops. Otherwise the required packages can be installed using the language support
section of the package manager or running: </para>
- <itemizedlist>
- <listitem>
- <screen>su -c 'yum install <SCIM-IMEs>'
</screen>
- </listitem>
- </itemizedlist>
+ <screen>su -c 'yum install <SCIM-IMEs>' </screen>
<para>where <code><SCIM-IMEs></code> should be
replaced by one or more of the following: </para>
<itemizedlist>
<listitem>
@@ -35,14 +31,8 @@
</itemizedlist>
<para>You also need fonts for the language. The font packages are named
<code>fonts-<language></code>, where
<code><language></code> is one of <code>arabic</code>,
<code>bengali</code>, <code>chinese</code>,
<code>gujarati</code>, <code>hebrew</code>,
<code>hindi</code>, <code>japanese</code>,
<code>korean</code>, <code>punjabi</code>,
<code>tamil</code>. </para>
<para>If your desktop is not running in an Asian locale, to activate it in
your user account, run these commands, then logout and login again to your desktop.
</para>
- <itemizedlist>
- <listitem>
- <screen>
-mkdir ~/.xinput.d
-ln -s /etc/X11/xinit/xinput.d/scim ~/.xinput.d/default
- </screen>
- </listitem>
- </itemizedlist>
+ <screen>mkdir ~/.xinput.d
+ln -s /etc/X11/xinit/xinput.d/scim ~/.xinput.d/default</screen>
</section>
<section>
<title>SCIM applet and toolbar</title>
@@ -81,11 +71,7 @@
<section>
<title>gtk2 IM submenu</title>
<para>The Gtk2 context menu IM submenu no longer appears by default. You can
enable it on the command line with the following command: </para>
- <itemizedlist>
- <listitem>
- <screen>gconftool-2 --type bool --set
'/desktop/gnome/interface/show_input_method_menu' true </screen>
- </listitem>
- </itemizedlist>
+ <screen>gconftool-2 --type bool --set
'/desktop/gnome/interface/show_input_method_menu' true </screen>
</section>
</section>
</article>
Index: Java.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Java.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Java.xml 28 Feb 2006 21:45:48 -0000 1.4
+++ Java.xml 28 Feb 2006 22:38:45 -0000 1.5
@@ -28,11 +28,7 @@
<title>Handling Java and Java-like Packages</title>
<para>In addition to the <package>java-gcj-compat</package> free
software stack, Fedora Core is designed to let you install multiple Java implementations
and switch between them using the <code>alternatives</code> command line tool.
However, every Java system you install must be packaged using the JPackage Project
packaging guidelines to take advantage of <code>alternatives</code>.
</para>
<para>Once installed properly, the <code>root</code> user should
be able to switch between <code>java</code> and <code>javac</code>
implementations using the <code>alternatives</code> command: </para>
- <itemizedlist>
- <listitem>
- <screen>alternatives --config java alternatives --config
javac</screen>
- </listitem>
- </itemizedlist>
+ <screen>alternatives --config java alternatives --config
javac</screen>
</section>
<section>
<title>Fedora and the JPackage Java Packages</title>
Index: Kernel.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Kernel.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- Kernel.xml 28 Feb 2006 21:45:48 -0000 1.7
+++ Kernel.xml 28 Feb 2006 22:38:45 -0000 1.8
@@ -14,20 +14,12 @@
<ulink
url='http://www.kernel.org/'>http://www.kernel.org/</ulink>
</para>
<para>To obtain a list of these patches, download the source RPM package and
run the following command against it: </para>
- <itemizedlist>
- <listitem>
- <screen>rpm -qpl kernel-<version>.src.rpm</screen>
- </listitem>
- </itemizedlist>
+ <screen>rpm -qpl kernel-<version>.src.rpm</screen>
</section>
<section>
<title>Changelog</title>
<para>To retrieve a log of changes to the package, run the following command:
</para>
- <itemizedlist>
- <listitem>
- <screen>rpm -q --changelog kernel-<version></screen>
- </listitem>
- </itemizedlist>
+ <screen>rpm -q --changelog kernel-<version></screen>
<para>If you need a user friendly version of the changelog, refer to
<ulink
url='http://wiki.kernelnewbies.org/LinuxChanges'>http://wiki.k...;.
A short and full diff of the kernel is available from <ulink
url='http://kernel.org/git'>http://kernel.org/git</ulink>. The Fedora
version kernel is based on the Linus tree. </para>
<para>Customizations made for the Fedora version are available from <ulink
url='http://cvs.fedora.redhat.com'>http://cvs.fedora.redhat.com</ulink> .
</para>
</section>
@@ -52,11 +44,7 @@
</listitem>
</itemizedlist>
<para>You may install sources for all kernel flavors at the same time. The
files are installed in the
<code>/usr/src/kernels/<version>-[xen-hypervisor|xen-guest|kdump]-<arch>/</code>
tree. Use the following command: </para>
- <itemizedlist>
- <listitem>
- <screen>su -c 'yum install
kernel-{xen,hypervisor,xen-guest,kdump}-devel'</screen>
- </listitem>
- </itemizedlist>
+ <screen>su -c 'yum install
kernel-{xen,hypervisor,xen-guest,kdump}-devel'</screen>
<para>Select one or more of these flavors, separated by commas and no spaces,
as appropriate. Enter the root password when prompted. </para>
<note>
<title>x86_64 Default Kernel Provides SMP</title>
@@ -74,11 +62,7 @@
<section>
<title>Following Generic Textbooks</title>
<para>Many of the tutorials, examples, and textbooks about Linux kernel
development assume the kernel sources are installed under the
<code>/usr/src/linux/</code> directory. If you make a symbolic link, as shown
below, you should be able to use those learning materials with the Fedora Core packages.
Install the appropriate kernel sources, as shown earlier, and then run the following
command: </para>
- <itemizedlist>
- <listitem>
<screen>su -c 'ln -s /usr/src/kernels/kernel-<all-the-rest>
/usr/src/linux'</screen>
- </listitem>
- </itemizedlist>
<para>Enter the <code>root</code> password when prompted.
</para>
</section>
<section>
@@ -96,15 +80,9 @@
<orderedlist numeration='arabic'>
<listitem>
<para>Prepare a RPM package building environment in your home directory.
Run the following commands: </para>
- <itemizedlist>
- <listitem>
- <screen>
-su -c 'yum install fedora-rpmdevtools'
-fedora-buildrpmtree
- </screen>
- <para>Enter the <code>root</code> password when prompted.
</para>
- </listitem>
- </itemizedlist>
+ <screen>su -c 'yum install fedora-rpmdevtools'
+fedora-buildrpmtree</screen>
+ <para>Enter the <code>root</code> password when prompted.
</para>
</listitem>
<listitem>
<para>Obtain the
<code>kernel-<version>.src.rpm</code> file from one of the following
sources: </para>
@@ -117,81 +95,51 @@
</listitem>
<listitem>
<para> by running the following command: </para>
- <itemizedlist>
- <listitem>
- <screen>
-su -c 'yum install yum-utils'
-su -c 'yumdownloader --source kernel'
- </screen>
- </listitem>
- </itemizedlist>
+ <screen>su -c 'yum install yum-utils'
+su -c 'yumdownloader --source kernel'</screen>
<para>Enter the <code>root</code> password when prompted.
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Install <code>kernel-<version>.src.rpm</code>
using the command: </para>
- <itemizedlist>
- <listitem>
- <screen>rpm -Uvh kernel-<version>.src.rpm`</screen>
- <para>This command writes the RPM contents into
<code>${HOME}/rpmbuild/SOURCES</code> and
<code>${HOME}/rpmbuild/SPECS</code>, where <code>${HOME}</code> is
your home directory. </para>
- <tip>
- <title>Space Required</title>
- <para> The full kernel building process may require several
gigabytes of extra space on the file system containing your home directory. </para>
- </tip>
- </listitem>
- <listitem>
+ <screen>rpm -Uvh kernel-<version>.src.rpm`</screen>
+ <para>This command writes the RPM contents into
<code>${HOME}/rpmbuild/SOURCES</code> and
<code>${HOME}/rpmbuild/SPECS</code>, where <code>${HOME}</code> is
your home directory. </para>
+ <tip>
+ <title>Space Required</title>
+ <para> The full kernel building process may require several gigabytes of extra
space on the file system containing your home directory. </para>
+ </tip>
+ </listitem>
+ <listitem>
<para>Prepare the kernel sources using the commands: </para>
- <itemizedlist>
- <listitem>
- <screen>
-cd ~/rpmbuild/SPECS
-rpmbuild -bp --target $(uname -m) kernel-2.6.spec
- </screen>
- <para>The kernel source tree is located in the
<code>${HOME}/rpmbuild/BUILD/kernel-<version>/</code> directory.
</para>
- </listitem>
- </itemizedlist>
+ <screen>cd ~/rpmbuild/SPECS
+rpmbuild -bp --target $(uname -m) kernel-2.6.spec</screen>
+ <para>The kernel source tree is located in the
<code>${HOME}/rpmbuild/BUILD/kernel-<version>/</code> directory.
</para>
</listitem>
<listitem>
<para>The configurations for the specific kernels shipped in Fedora Core
5 are in the <code>configs/</code> directory. For example, the i686 SMP
configuration file is named
<code>configs/kernel-<version>-i686-smp.config</code>. Issue the
following command to place the desired configuration file in the proper place for
building: </para>
- <itemizedlist>
- <listitem>
- <screen>cp configs/<desired-config-file>
.config</screen>
- <para>You can also find the <code>.config</code> file
that matches your current kernel configuration in the
<code>/lib/modules/<version>/build/.config</code> file.
</para>
- </listitem>
- </itemizedlist>
+ <screen>cp configs/<desired-config-file> .config</screen>
+ <para>You can also find the <code>.config</code> file that matches
your current kernel configuration in the
<code>/lib/modules/<version>/build/.config</code> file.
</para>
</listitem>
<listitem>
<para>Every kernel gets a name based on its version number. This is the
value the <code>uname -r</code> command displays. The kernel name is defined
by the first four lines of the kernel <code>Makefile</code>. The
<code>Makefile</code> has been changed to generate a kernel with a
<emphasis>different</emphasis> name from that of the running kernel. To be
accepted by the running kernel, a module must be compiled for a kernel with the correct
name. To do this, you must edit the kernel <code>Makefile</code>.
</para>
- <itemizedlist>
- <listitem>
- <para>For example, if the <code>uname -r</code> returns
the string <code>2.6.15-1.1948_FC5</code>, change the
<code>EXTRAVERSION</code> definition from this: </para>
- <screen>EXTRAVERSION = -prep</screen>
- <para>to this: </para>
- <screen>EXTRAVERSION = -1.1948_FC5</screen>
- <para>That is, substitute everything from the final dash onward.
</para>
- </listitem>
- </itemizedlist>
+ <para>For example, if the <code>uname -r</code> returns the string
<code>2.6.15-1.1948_FC5</code>, change the
<code>EXTRAVERSION</code> definition from this: </para>
+ <screen>EXTRAVERSION = -prep</screen>
+ <para>to this: </para>
+ <screen>EXTRAVERSION = -1.1948_FC5</screen>
+ <para>That is, substitute everything from the final dash onward. </para>
</listitem>
<listitem>
<para>Run the following command: </para>
- <itemizedlist>
- <listitem>
- <screen>make oldconfig</screen>
- <para>You may then proceed as usual. </para>
- </listitem>
- </itemizedlist>
+ <screen>make oldconfig</screen>
+ <para>You may then proceed as usual. </para>
</listitem>
- </itemizedlist>
- </listitem>
- </orderedlist>
+ </orderedlist>
</section>
<section>
<title>Building Only Kernel Modules</title>
<para>An exploded source tree is not required to build a kernel module, such
as your own device driver, against the currently in-use kernel. For example, to build the
<code>foo.ko</code> module, create the following
<code>Makefile</code> in the directory containing the
<code>foo.c</code> file: </para>
- <itemizedlist>
- <listitem>
- <screen>
+ <screen>
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
@@ -199,9 +147,7 @@
default:
$(MAKE) -C $(KDIR) M=$(PWD) modules
- </screen>
- </listitem>
- </itemizedlist>
+ </screen>
<para>Issue the <code>make</code> command to build the
<code>foo.ko</code> module. </para>
</section>
<section>
Index: Networking.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Networking.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- Networking.xml 28 Feb 2006 21:45:48 -0000 1.7
+++ Networking.xml 28 Feb 2006 22:38:45 -0000 1.8
@@ -81,28 +81,20 @@
<section>
<title>User Tools</title>
<para>The IPv4 address deletion algorithm did not take the prefix length into
account up to kernel version 2.6.12. Since this has changed, the
<code>iproute2</code> tool now issues a warning if no prefix length is
provided, to warn about possible unintended deletions: </para>
- <itemizedlist>
- <listitem>
- <screen><![CDATA[
+ <screen><![CDATA[
ip addr list dev eth0
4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
inet 10.0.0.3/24 scope global eth0
- ]]></screen>
- <screen>
+ ]]></screen>
+ <screen>
su -c 'ip addr del 10.0.0.3 dev eth0'
Warning: Executing wildcard deletion to stay compatible with old
scripts. Explicitly specify the prefix length (10.0.0.3/32) to
avoid this warning. This special behaviour is likely to disappear
in further releases, fix your scripts!
- </screen>
- </listitem>
- </itemizedlist>
+ </screen>
<para>The correct method of deleting the address and thus avoiding the
warning is: </para>
- <itemizedlist>
- <listitem>
- <screen>su -c 'ip addr del 10.0.0.3/24 dev eth0'</screen>
- </listitem>
- </itemizedlist>
+ <screen>su -c 'ip addr del 10.0.0.3/24 dev eth0'</screen>
<para>Previously, it was not possible to tell if an interface was down
administratively or because no carrier was found, such as if a cable were unplugged. The
new flag <code>NO-CARRIER</code> now appears as a link flag if the link is
administratively up but no carrier can be found. </para>
<para>The <code>ip</code> command now supports a batch mode via
the argument <code>-batch</code>, which works similar to the
<code>tc</code> command to speed up batches of tasks. </para>
</section>
Index: PackageChanges.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/PackageChanges.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- PackageChanges.xml 28 Feb 2006 21:45:48 -0000 1.4
+++ PackageChanges.xml 28 Feb 2006 22:38:45 -0000 1.5
@@ -71,7 +71,8 @@
A real mode 80x86 assembler and linker.
New package dhcdbd
- DHCP D-BUS daemon (dhcdbd) controls dhclient sessions with D-BUS, stores and presents
DHCP options.
+ DHCP D-BUS daemon (dhcdbd) controls dhclient sessions
+ with D-BUS, stores and presents DHCP options.
New package ekiga
A Gnome based SIP/H323 teleconferencing application
@@ -104,7 +105,8 @@
Library for creating and parsing MIME messages
New package gnome-applet-vm
- Simple virtual domains monitor which embed themselves in the GNOME panel
+ Simple virtual domains monitor which embed themselves
+ in the GNOME panel
New package gnome-mount
Mount replacement which uses HAL to do the mounting
@@ -113,7 +115,8 @@
GNOME Power Manager
New package gnome-python2-desktop
- The sources for additional PyGNOME Python extension modules for the GNOME desktop.
+ The sources for additional PyGNOME Python extension modules
+ for the GNOME desktop.
New package gnome-screensaver
GNOME Sreensaver
@@ -296,7 +299,8 @@
X.Org X11 libXxf86vm runtime library
New package libchewing
- Intelligent phonetic input method library for Traditional Chinese
+ Intelligent phonetic input method library for Traditional
+ Chinese
New package libdaemon
library for writing UNIX daemons
@@ -320,7 +324,8 @@
Library to access the contents of an iPod
New package libgssapi
- Generic Security Services Application Programming Interface Library
+ Generic Security Services Application Programming Interface
+ Library
New package libiec61883
Streaming library for IEEE1394
@@ -488,7 +493,8 @@
squashfs utilities
New package system-config-cluster
- system-config-cluster is a utility which allows you to manage cluster configuration in a
graphical setting.
+ system-config-cluster is a utility which allows you to manage
+ cluster configuration in a graphical setting.
New package systemtap
Instrumentation System
Index: Security.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Security.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- Security.xml 28 Feb 2006 21:45:48 -0000 1.7
+++ Security.xml 28 Feb 2006 22:38:45 -0000 1.8
@@ -30,9 +30,7 @@
</tip>
<screen>diff -u /etc/pam.d/foo /etc/pam.d/foo.rpmnew</screen>
<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>
- <screen>
+ <screen>
#%PAM-1.0
auth required pam_securetty.so
auth required pam_stack.so service=system-auth
@@ -46,8 +44,8 @@
session optional pam_console.so
# pam_selinux.so open should be the last session rule
session required pam_selinux.so open
- </screen>
- <screen>
+ </screen>
+ <screen>
#%PAM-1.0
auth required pam_securetty.so
auth include system-auth
@@ -67,9 +65,7 @@
session optional pam_console.so
# pam_selinux.so open should be the last session rule
session required pam_selinux.so open
- </screen>
- </listitem>
- </itemizedlist>
+ </screen>
</section>
<section>
<title>Buffer Overflow detection and variable reordering</title>
Index: ServerTools.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/ServerTools.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- ServerTools.xml 28 Feb 2006 21:45:48 -0000 1.4
+++ ServerTools.xml 28 Feb 2006 22:38:45 -0000 1.5
@@ -16,11 +16,7 @@
<section>
<title>Kerberos Support for SMB Printers</title>
<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: </para>
- <itemizedlist>
- <listitem>
- <screen>su -c 'system-config-printer' </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. </para>
</section>
</section>
@@ -33,11 +29,7 @@
<section>
<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>: </para>
- <itemizedlist>
- <listitem>
- <screen>A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp
--dport 6881:6999 -j ACCEPT </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>