release-notes/FC4 hardware-reqs.xml, 1.3, 1.4 overview.xml, 1.3, 1.4 package-notes.xml, 1.11, 1.12 security.xml, 1.2, 1.3
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26645
Modified Files:
hardware-reqs.xml overview.xml package-notes.xml security.xml
Log Message:
All up2date now, misc small stuff.
Index: hardware-reqs.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/hardware-reqs.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- hardware-reqs.xml 30 May 2005 17:58:06 -0000 1.3
+++ hardware-reqs.xml 30 May 2005 18:33:21 -0000 1.4
@@ -1,199 +1,210 @@
- <section id="sn-hardware-reqs">
- <title>Hardware Requirements</title>
+<section id="sn-hardware-reqs">
+ <title>Hardware Requirements</title>
- <para>The following information represents the minimum hardware requirements
- necessary to successfully install &DISTRO; &DISTROVER;.</para>
+ <para>The following information represents the minimum hardware
+ requirements necessary to successfully install &DISTRO;
+ &DISTROVER;.</para>
+
+ <note>
+ <title>Note</title>
+
+ <para>The compatibility/availability of other hardware components
+ (such as video and network cards) may be required for specific
+ installation modes and/or post-installation usage.</para>
+ </note>
- <note>
- <title>Note</title>
+ <section>
+ <title>CPU Requirements</title>
- <para>The compatibility/availability of other hardware components (such as
- video and network cards) may be required for specific installation modes
- and/or post-installation usage.</para>
+ <para>This section lists the CPU specifications required by &DISTRO;
+ &DISTROVER;.</para>
+
+ <note arch="x86">
+ <title><!-- <remark os="test">(x86)</remark>--> Note</title>
+
+ <para><!-- <remark os="test">(x86)</remark> --> The following CPU
+ specifications are stated in terms of Intel processors. Other
+ processors (notably, offerings from AMD, Cyrix, and VIA) that
+ are compatible with and equivalent to the following Intel
+ processors may also be used with &DISTRO;.</para>
</note>
- <section>
- <title>CPU Requirements</title>
+ <itemizedlist arch="x86">
+ <listitem>
+ <para><!-- <remark os="test">(x86)</remark> --> Minimum:
+ Pentium-class</para>
- <para>This section lists the CPU specifications required by &DISTRO;
- &DISTROVER;.</para>
+ <!-- <remark os="test">%%% <ulink
+ url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254</ulink>
+ %%%</remark> -->
- <note arch="x86">
- <title><remark os="test">(x86)</remark> Note</title>
+ <para>
+ <!-- <remark os="test">(x86)</remark> --> &DISTRO; &DISTROVER;
+ is optimized for Pentium 4 CPUs, but also supports earlier
+ CPUs (such as Pentium, Pentium Pro, Pentium II, Pentium III,
+ and including AMD and VIA variants). This approach has been
+ taken because Pentium-class optimizations actually result in
+ reduced performance for non-Pentium-class processors, and
+ Pentium 4 scheduling is sufficiently different (while making
+ up the bulk of today's processors) to warrant this
+ change.</para>
+ </listitem>
- <para><remark os="test">(x86)</remark> The following CPU specifications
- are stated in terms of Intel processors. Other processors (notably,
- offerings from AMD, Cyrix, and VIA) that are compatible with and
- equivalent to the following Intel processors may also be used with
- &DISTRO;.</para>
- </note>
-
- <itemizedlist arch="x86">
- <listitem>
- <para><remark os="test">(x86)</remark> Minimum: Pentium-class</para>
+ <listitem>
+ <para><!-- <remark os="test">(x86)</remark> --> Recommended for
+ text-mode: 200 MHz Pentium-class or better</para>
+ </listitem>
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254</ulink>
- %%%</remark>
+ <listitem>
+ <para><!-- <remark os="test">(x86)</remark> --> Recommended for
+ graphical: 400 MHz Pentium II or better</para>
+ </listitem>
+ </itemizedlist>
- <para><remark os="test">(x86)</remark> &DISTRO; &DISTROVER; is
- optimized for Pentium 4 CPUs, but also supports earlier CPUs (such
- as Pentium, Pentium Pro, Pentium II, Pentium III, and including AMD
- and VIA variants). This approach has been taken because
- Pentium-class optimizations actually result in reduced performance
- for non-Pentium-class processors, and Pentium 4 scheduling is
- sufficiently different (while making up the bulk of today's
- processors) to warrant this change.</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86)</remark> Recommended for text-mode: 200
- MHz Pentium-class or better</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86)</remark> Recommended for graphical: 400
- MHz Pentium II or better</para>
- </listitem>
- </itemizedlist>
-
- <itemizedlist arch="x86_64">
- <listitem>
- <para><remark os="test">(x86_64)</remark> AMD64 processors (both
- Athlon64 and Opteron)</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86_64)</remark> Intel processors with
- <trademark class="registered">Intel</trademark> Extended Memory 64
- Technology (<trademark class="registered">Intel</trademark>
- EM64T)</para>
- </listitem>
- </itemizedlist>
- </section>
- <section>
- <title>Hard Disk Space Requirements</title>
-
- <para>This section lists the disk space required to install &DISTRO;
- &DISTROVER;.</para>
-
- <note>
- <title>Note</title>
-
- <para>The disk space requirements listed below represent the disk space
- taken up by &DISTRO; &DISTROVER; <emphasis>after</emphasis> the
- installation is complete. However, additional disk space is required
- during the installation to support the installation environment. This
- additional disk space corresponds to the size of
- <filename>/Fedora/base/stage2.img</filename> (on CD-ROM 1) plus the
- size of the files in <filename>/var/lib/rpm</filename> on the
- installed system.</para>
+ <itemizedlist arch="x86_64">
+ <listitem>
+ <para><!-- <remark os="test">(x86_64)</remark> --> AMD64
+ processors (both Athlon64 and Opteron)</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86_64)</remark> --> Intel
+ processors with <trademark
+ class="registered">Intel</trademark> Extended Memory 64
+ Technology (<trademark class="registered">Intel</trademark>
+ EM64T)</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section>
+ <title>Hard Disk Space Requirements</title>
+
+ <para>This section lists the disk space required to install &DISTRO;
+ &DISTROVER;.</para>
+
+ <note>
+ <title>Note</title>
+
+ <para>The disk space requirements listed below represent the disk
+ space taken up by &DISTRO; &DISTROVER;
+ <emphasis>after</emphasis> the installation is complete.
+ However, additional disk space is required during the
+ installation to support the installation environment. This
+ additional disk space corresponds to the size of
+ <filename>/Fedora/base/stage2.img</filename> (on CD-ROM 1) plus
+ the size of the files in <filename>/var/lib/rpm</filename> on
+ the installed system.</para>
<!-- Update these figures every release -->
- <para>In practical terms, this means that as little as an additional
- 90MB can be required for a minimal installation, while as much as an
- additional 175MB can be required for an "everything"
- installation.</para>
-
- <para>Also, keep in mind that additional space will be required for any
- user data, and at least 5% free space should be maintained for proper
- system operation.</para>
- </note>
+ <para>In practical terms, this means that as little as an
+ additional 90MB can be required for a minimal installation,
+ while as much as an additional 175MB can be required for an
+ "everything" installation.</para>
+
+ <para>Also, keep in mind that additional space will be required
+ for any user data, and at least 5% free space should be
+ maintained for proper system operation.</para>
+ </note>
<!-- Get actual numbers from installer, multiply by 1.1, and round -->
<!-- up to the nearest 10MB or .1GB -->
- <itemizedlist arch="x86">
- <listitem>
- <para><remark os="test">(x86)</remark> Custom Installation (Minimal):
- 620MB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86)</remark> Server: 1.1GB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86)</remark> Personal Desktop: 2.3GB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86)</remark> Workstation: 3.0GB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86)</remark> Custom Installation
- (Everything): 6.9GB</para>
- </listitem>
- </itemizedlist>
-
- <itemizedlist arch="x86_64">
- <listitem>
- <para><remark os="test">(x86_64)</remark> Custom Installation
- (Minimal): 900MB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86_64)</remark> Server: 1.5GB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86_64)</remark> Personal Desktop:
- 2.7GB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86_64)</remark> Workstation: 3.4GB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86_64)</remark> Custom Installation:
- (Everything) 7.5GB</para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Memory Requirements</title>
-
- <para>This section lists the memory required to install &DISTRO;
- &DISTROVER;.</para>
-
- <itemizedlist arch="x86">
- <listitem>
- <para><remark os="test">(x86)</remark> Minimum for text-mode:
- 64MB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86)</remark> Minimum for graphical:
- 192MB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86)</remark> Recommended for graphical:
- 256MB</para>
- </listitem>
- </itemizedlist>
-
- <itemizedlist arch="x86_64">
- <listitem>
- <para><remark os="test">(x86_64)</remark> Minimum for text-mode:
- 128MB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86_64)</remark> Minimum for graphical:
- 256MB</para>
- </listitem>
-
- <listitem>
- <para><remark os="test">(x86_64)</remark> Recommended for graphical:
- 512MB</para>
- </listitem>
- </itemizedlist>
- </section>
+ <itemizedlist arch="x86">
+ <listitem>
+ <para><!-- <remark os="test">(x86)</remark> --> Custom
+ Installation (Minimal): 620MB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86)</remark> --> Server:
+ 1.1GB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86)</remark> --> Personal
+ Desktop: 2.3GB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86)</remark> --> Workstation:
+ 3.0GB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86)</remark> --> Custom
+ Installation (Everything): 6.9GB</para>
+ </listitem>
+ </itemizedlist>
+
+ <itemizedlist arch="x86_64">
+ <listitem>
+ <para><!-- <remark os="test">(x86_64)</remark> --> Custom
+ Installation (Minimal): 900MB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86_64)</remark> --> Server:
+ 1.5GB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86_64)</remark> --> Personal
+ Desktop: 2.7GB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86_64)</remark> --> Workstation:
+ 3.4GB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86_64)</remark> --> Custom
+ Installation: (Everything) 7.5GB</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section>
+ <title>Memory Requirements</title>
+
+ <para>This section lists the memory required to install &DISTRO;
+ &DISTROVER;.</para>
+
+ <itemizedlist arch="x86">
+ <listitem>
+ <para><!-- <remark os="test">(x86)</remark> --> Minimum for
+ text-mode: 64MB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86)</remark> --> Minimum for
+ graphical: 192MB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86)</remark> --> Recommended for
+ graphical: 256MB</para>
+ </listitem>
+ </itemizedlist>
+
+ <itemizedlist arch="x86_64">
+ <listitem>
+ <para><!-- <remark os="test">(x86_64)</remark> --> Minimum for
+ text-mode: 128MB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86_64)</remark> --> Minimum for
+ graphical: 256MB</para>
+ </listitem>
+
+ <listitem>
+ <para><!-- <remark os="test">(x86_64)</remark> --> Recommended
+ for graphical: 512MB</para>
+ </listitem>
+ </itemizedlist>
+ </section>
<section>
<title>PPC Hardware Requirements</title>
<para>
@@ -222,8 +233,8 @@
</listitem>
<listitem>
<para>
- <!--<remark os="test">(x86)</remark> --> Recommended for text-mode:
- 233 MHz G3 or better
+ <!--<remark os="test">(x86)</remark> --> Recommended for
+ text-mode: 233 MHz G3 or better
</para>
</listitem>
<listitem>
Index: overview.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/overview.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- overview.xml 30 May 2005 17:40:09 -0000 1.3
+++ overview.xml 30 May 2005 18:33:21 -0000 1.4
@@ -22,7 +22,10 @@
</listitem>
<listitem>
<para>
- KDE 3.4
+ KDE 3.4 — includes new accessibility features. You
+ can manage these new features in <guimenu>KDS Control
+ Center</guimenu><guisubmenu>Regional &
+ Accessibility</guisubmenu><guisubmenu>Accessibility</guisubmenu>.
</para>
</listitem>
<listitem>
Index: package-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/package-notes.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- package-notes.xml 30 May 2005 18:16:22 -0000 1.11
+++ package-notes.xml 30 May 2005 18:33:21 -0000 1.12
@@ -211,7 +211,7 @@
</section>
&SERVER-TOOLS;
</section>
-<!-- Saving these just in case ...
+ <!-- Saving these just in case ...
<section os="bogus">
<title>Administration Tools</title>
@@ -255,8 +255,9 @@
<para>
The Fedora Extras repository is now enabled by default.
</para>
- </section>
+ </section>
&KERNEL;
+ &SECURITY;
</section>
<!--
<section>
@@ -613,6 +614,8 @@
</listitem>
</varlistentry>
</variablelist>
+ </section>
+ </section>
<!-- keeping for historical informative purpose as a resource
<itemizedlist>
<listitem>
@@ -721,9 +724,6 @@
</listitem>
</itemizedlist>
</section>
- -->
- </section>
-<!--
<section os="bogus">
<title>Legacy Software Development</title>
@@ -802,7 +802,7 @@
</section>
-->
- &PRINTING;
+ &PRINTING;
<!--
<section os="bogus">
<title>Ruby</title>
@@ -817,8 +817,8 @@
</section>
-->
- &DATABASE-SERVERS;
- &MULTIMEDIA;
+ &DATABASE-SERVERS;
+ &MULTIMEDIA;
<!--
<section os="bogus">
<title>Supported Packages</title>
@@ -841,10 +841,10 @@
</section>
-->
- &WEB-SERVERS;
- &SAMBA;
- &XORG;
-<!-- <section os="bogus">
+ &WEB-SERVERS;
+ &SAMBA;
+ &XORG;
+ <!-- <section os="bogus">
<title>Workstation Common</title>
<para>*** Enter group description here ***</para>
@@ -865,7 +865,6 @@
</section>
-->
- </section>
</section>
<!--
Local variables:
Index: security.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/security.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- security.xml 28 May 2005 16:10:32 -0000 1.2
+++ security.xml 30 May 2005 18:33:21 -0000 1.3
@@ -1,3 +1,26 @@
+<section id="sn-security">
+ <title>Security</title>
+ <para>
+ This section highlights various security items from &FC;.
+ </para>
+ <section id="sn-security-digital-certs">
+ <title>Digital Certificates Consolidated</title>
+ <para>
+ Digital certificates are now centralised in directories under
+ <filename>/etc/pki/</filename>. Users performing an upgrade must
+ relocate their digital certificates.
+ </para>
+ <para>
+ OpenSSL: the <filename>/usr/share/ssl</filename> contents have
+ moved to <filename>/etc/pki/tls</filename> and
+ <filename>/etc/pki/CA</filename>.
+ </para>
+ <para>
+ Dovecot: A <filename>dovecot-openssl.cnf</filename> file is
+ automatically installed in <filename>/etc/pki/dovecot/</filename>.
+ </para>
+ </section>
+</section>
<!--
Local variables:
mode: xml
18 years, 10 months
release-notes/FC4 kernel.xml,1.2,1.3 package-notes.xml,1.10,1.11
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26571
Modified Files:
kernel.xml package-notes.xml
Log Message:
A tip from bz#158394, misc. other fixes.
Index: kernel.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/kernel.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- kernel.xml 28 May 2005 16:10:31 -0000 1.2
+++ kernel.xml 30 May 2005 18:16:22 -0000 1.3
@@ -1,3 +1,157 @@
+<section id="sn-kernel">
+ <title><filename>kernel</filename></title>
+ <!-- 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>
+-->
+ <tip>
+ <title>Using <command>yum</command> to Uninstall Kernel
+ Packages</title>
+ <para>
+ &FC; &LOCALVER; contains support for clustering systems using CMAN
+ and GFS. These kernels require assistance from some user-space
+ packages. These packages are not removed when using <command>rpm
+ -e</command> to uninstall older versions of the kernel packages.
+ </para>
+ <para>
+ When using <command>rpm -e
+ kernel-<replaceable><version></replaceable></command> to
+ uninstall the kernel, you must also remove the assisting
+ user-space packages. You may wish to consider a dependecy
+ resolving tool such as <command>yum remove
+ kernel-<replaceable><version></replaceable></command>.
+ This automatically removes any dependant packages.
+ </para>
+ </tip>
+ <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>
+ <procedure>
+ <step>
+ <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>
+ </step>
+ <step>
+ <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>
+ </step>
+ <step>
+ <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>
+ </step>
+ <step>
+ <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>
+ </step>
+ <step>
+ <para>
+ Issue the following command:
+ </para>
+ <para>
+ <command>make oldconfig</command>
+ </para>
+ </step>
+ </procedure>
+ <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
+
+KDIR := /lib/modules/$(shell uname -r)/build
+PWD := $(shell pwd)
+
+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>
+ </tip>
+</section>
<!--
Local variables:
mode: xml
Index: package-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/package-notes.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- package-notes.xml 30 May 2005 17:40:09 -0000 1.10
+++ package-notes.xml 30 May 2005 18:16:22 -0000 1.11
@@ -240,7 +240,7 @@
</section>
-->
- <section>
+ <section id="sn-packages-core">
<title>Core</title>
<para>
This section contains the most elemental components of &DISTRO;,
@@ -255,7 +255,9 @@
<para>
The Fedora Extras repository is now enabled by default.
</para>
-</section>
+ </section>
+ &KERNEL;
+ </section>
<!--
<section>
<title><filename>e2fsprogs</filename></title>
@@ -370,143 +372,6 @@
moved into the new directory.</para>
</section>
-->
- <section>
- <title><filename>kernel</filename></title>
-<!-- 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 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
-
-KDIR := /lib/modules/$(shell uname -r)/build
-PWD := $(shell pwd)
-
-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>
- </tip>
- </section>
-</section>
<!--
<section os="bogus">
<title>DNS Name Server</title>
@@ -648,7 +513,7 @@
<para>*** Enter group description here ***</para>
</section>
--->
+ -->
<section>
<title>Language Support</title>
<para>
18 years, 10 months
release-notes/FC4 hardware-reqs.xml,1.2,1.3
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25547
Modified Files:
hardware-reqs.xml
Log Message:
PPC hardware requirements courtesy of bz#158322
Index: hardware-reqs.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/hardware-reqs.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- hardware-reqs.xml 28 May 2005 16:10:31 -0000 1.2
+++ hardware-reqs.xml 30 May 2005 17:58:06 -0000 1.3
@@ -194,8 +194,47 @@
</listitem>
</itemizedlist>
</section>
+ <section>
+ <title>PPC Hardware Requirements</title>
+ <para>
+ This section lists the minimum PowerPC (PPC) hardware needed to
+ install &FC; &LOCALVER;.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <!--<remark os="test">(ppc)</remark> --> Minimum: PowerPC G3 /
+ POWER4
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--<remark os="test">(ppc)</remark> --> &FC; &LOCALVER;
+ supports only the <quote>New World</quote> generation of
+ <trademark class="registered">Apple</trademark> Power
+ Macintosh, shipped circa 1999 onwards. It also supports the
+ 64-bit G5 processor and, POWER processors in <trademark
+ class="registered">IBM</trademark>
+ <trademark>eServer</trademark> <trademark>pSeries</trademark>.
+ Currently 32-bit <trademark class="registered">IBM</trademark>
+ <trademark>RS/6000</trademark> machines are not supported.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!--<remark os="test">(x86)</remark> --> Recommended for text-mode:
+ 233 MHz G3 or better
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!-- <remark os="test">(ppc)</remark> --> Recommended for
+ graphical: 400 MHz G3 or better
+ </para>
+ </listitem>
+ </itemizedlist>
</section>
-
+</section>
<!--
Local variables:
mode: xml
18 years, 10 months
release-notes/FC4 xorg.xml,1.4,1.5
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25510
Modified Files:
xorg.xml
Log Message:
Clean up to make it look good without all the bullets around it. Hoping to use nicer formatting in the future.
Index: xorg.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/xorg.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- xorg.xml 30 May 2005 17:40:09 -0000 1.4
+++ xorg.xml 30 May 2005 17:52:18 -0000 1.5
@@ -1,183 +1,206 @@
<section id="sn-xwindows">
- <title>X Window System (Graphics)</title>
-
- <para>This section contains information related to the X Window System
- implementation provided with &DISTRO;.</para>
-
- <section id="sn-xwindows-xorg">
- <title><filename>xorg-x11</filename></title>
-
-
-
- <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>
-
-
-
- <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 such as:</para>
-
- <para>Luxi Sans-10</para>
-
- <para>Over time, fontconfig and 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
+ <title>X Window System (Graphics)</title>
+ <para>
+ This section contains information related to the X Window System
+ implementation provided with &DISTRO;.
+ </para>
+ <section id="sn-xwindows-xorg">
+ <title><filename>xorg-x11</filename></title>
+ <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>
+ <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>
+ <itemizedlist>
+ <listitem>
+ <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: <computeroutput>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</computeroutput>
+ </para>
+ </listitem>
+ <listitem>
+ <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 such
+ as: <computeroutput>Luxi Sans-10</computeroutput>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Over time, fontconfig and 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, &FC; may support only fontconfig/Xft in
+ place of the XFS font server as the default local font access
+ method.
+ </para>
+ <note>
+ <title>Note</title>
+ <para>
+ An exception to the font subsystem usage outlined above
+ is OpenOffice.org (which uses its own font rendering
+ technology).
+ </para>
+ </note>
+ <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>
+
+ <procedure>
+ <step>
+ <para>
+ Create the <filename>/usr/share/fonts/local/</filename>
+ directory (if it doesn't already exist):
+ </para>
+<screen>
+<command>mkdir /usr/share/fonts/local/</command>
+</screen>
+ </step>
+ <step>
+ <para>
+ Copy the new font file into
+ <filename>/usr/share/fonts/local/</filename>
+ </para>
+ </step>
+ <step>
+ <para>
+ 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>
-
-
-
- <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>
-
-
- </section>
- </section>
+ should be entered on a single line):
+ </para>
+<screen>
+<command>ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</command>
+<command>mkfontdir /usr/share/fonts/local/</command>
+</screen>
+ </step>
+ <step>
+ <para>
+ If you had to create
+ <filename>/usr/share/fonts/local/</filename>, you must then
+ add it to the X font server (xfs) path:
+ </para>
+<screen>
+<command>chkfontpath --add /usr/share/fonts/local/</command>
+</screen>
+ </step>
+ </procedure>
+ <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>
+<screen>
+<command>fc-cache <replaceable><directory></replaceable></command>
+</screen>
+ <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>
+ <note>
+ <title>Note</title>
+ <para>
+ 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>
+ </note>
+ <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>
+<screen>
+<computeroutput>style "user-font" {
+fontset = "<replaceable><font-specification></replaceable>"
+}
+widget_class "*" style "user-font"</computeroutput>
+</screen>
+ <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>
+ </section>
+</section>
<!--
Local variables:
18 years, 10 months
release-notes/FC4 install-notes.xml, 1.5, 1.6 overview.xml, 1.2, 1.3 package-notes.xml, 1.9, 1.10 xorg.xml, 1.3, 1.4
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25489
Modified Files:
install-notes.xml overview.xml package-notes.xml xorg.xml
Log Message:
Removing the list elements because the multiple paras are not rendering through the HTML XSL. Will follow with some small clean-up of code formatting.
Index: install-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/install-notes.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- install-notes.xml 30 May 2005 17:19:33 -0000 1.5
+++ install-notes.xml 30 May 2005 17:40:09 -0000 1.6
@@ -181,11 +181,12 @@
</listitem>
<listitem arch="x86">
<para>
- <!-- <remark os="test">(x86)</remark> --> There have been issues
- observed when upgrading &RHL;
- 7.<replaceable><x></replaceable>, 8.0, 9, and &DISTRO; 1
- systems where third party packages are installed that conflict
- with packages provided by &FP;. One example is Ximian GNOME.
+ <!-- <remark os="test">(x86)</remark> --> There have been
+ issues observed when upgrading &RHL;
+ 7.<replaceable><x></replaceable>, 8.0, 9, and &FC; 1, 2,
+ and 3 systems where third party packages are installed that
+ conflict with packages provided by &FP;. One example is
+ Ximian GNOME.
</para>
<para>
The issue with Ximian GNOME is caused by version overlap
Index: overview.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/overview.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- overview.xml 28 May 2005 16:10:31 -0000 1.2
+++ overview.xml 30 May 2005 17:40:09 -0000 1.3
@@ -61,22 +61,22 @@
</para>
</listitem>
<listitem>
- <remark os="test">%%% <ulink
+<!-- <remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136251">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136251</ulink>
- %%%</remark>
+ %%%</remark>-->
<para>
- &SEL; — This release includes new daemons covered by
- the targeted policy and changes to the handling of
- Booleans. The targeted policy is enabled by default.
- For more information, refer to:
+ &SEL; — This release includes coverage for 80 new
+ daemons by the targeted policy. There are changes to the
+ handling of Booleans. The targeted policy is enabled by
+ default. For more information, refer to:
</para>
<para>
<ulink
url="http://fedora.redhat.com/docs/selinux-faq/">http://fedora.redhat.com/docs/selinux-faq/</ulink>
</para>
<para>
- This is the complete list of daemons covered by the targeted policy:
+ For This is the complete list of daemons covered by the targeted policy:
</para>
<itemizedlist>
<listitem>
Index: package-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/package-notes.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- package-notes.xml 30 May 2005 16:51:59 -0000 1.9
+++ package-notes.xml 30 May 2005 17:40:09 -0000 1.10
@@ -937,7 +937,7 @@
</section>
-->
- &PRINTING;
+ &PRINTING;
<!--
<section os="bogus">
<title>Ruby</title>
Index: xorg.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/xorg.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- xorg.xml 29 May 2005 19:05:19 -0000 1.3
+++ xorg.xml 30 May 2005 17:40:09 -0000 1.4
@@ -7,8 +7,8 @@
<section id="sn-xwindows-xorg">
<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.
@@ -39,7 +39,7 @@
</listitem>
</itemizedlist>
- <para>X Server Log File</para>
+ <para>X Server Log File:</para>
<itemizedlist>
<listitem>
@@ -56,9 +56,9 @@
<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
@@ -75,7 +75,7 @@
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>
+ Fontconfig uses more human-friendly names such as:</para>
<para>Luxi Sans-10</para>
@@ -152,9 +152,9 @@
<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.
@@ -174,8 +174,8 @@
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>
18 years, 10 months
release-notes/FC4 install-notes.xml,1.4,1.5
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25395
Modified Files:
install-notes.xml
Log Message:
PPC install notes bz#158322. Commenting out the various remarks and arch specific materials starts here and will continue, we are NOT building arch specific notes, people will just have to read the ToC for now. When this matters more, we can uncomment the remarks et al. These are vestiges of an old practice we aren't reviewing to use for FC4, and will have to consider for FC5test1 using the latest DocBook/XML methods.
Index: install-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/install-notes.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- install-notes.xml 30 May 2005 16:42:05 -0000 1.4
+++ install-notes.xml 30 May 2005 17:19:33 -0000 1.5
@@ -28,6 +28,50 @@
<ulink url="http://fedora.redhat.com/download/">http://fedora.redhat.com/download/</ulink>
</para>
</note>
+ <section id="sn-ppc-install-notes">
+ <title>PPC Installation Notes</title>
+ <para>
+ <!--<remark os="test">(ppc)</remark>--> The DVD or first CD of the
+ installation set of &FC; is set to be bootable on the <trademark
+ class="registered">Apple</trademark> Macintosh and should boot
+ the appropriate 32-bit or 64-bit installer. In addition, bootable
+ CD images can be found in the <filename>images/</filename>
+ directory of the DVD or first CD. Choose the appropriate
+ <filename>boot.iso</filename> according to the hardware:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><filename>images/mac/boot.iso</filename> - 32-bit
+ <trademark class="registered">Apple</trademark> Macintosh
+ (G3/G4)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>images/mac64/boot.iso</filename> - 64-bit <trademark
+ class="registered">Apple</trademark> Macintosh (G5)
+ </para>
+ </listitem>
+ <listitem>
+ <para><filename>images/pseries/boot.iso</filename> - 64-bit
+ <trademark class="registered">IBM</trademark>
+ <trademark>eServer</trademark> <trademark>pSeries</trademark>
+ (POWER4/POWER5)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!-- <remark os="test">(ppc)</remark> --> Power management
+ support, including sleep and backlight level management, is
+ present in the <command>apmud</command> package, which is in
+ &FEX;. &FEX; for &FC; is configured by default for
+ <command>yum</command>. Following installation,
+ <command>apmud</command> can be installed by running
+ <command>yum install apmud</command>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
<section>
<title>Anaconda Notes</title>
@@ -46,11 +90,12 @@
</para>
</listitem>
<listitem arch="x86">
- <remark os="test">%%% <ulink
+<!-- <remark os="test">%%% <ulink
url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654</ulink>
%%%</remark>
+-->
<para>
- <remark os="test">(x86)</remark> Memory testing may be
+ <!-- <remark os="test">(x86)</remark> --> Memory testing may be
performed prior to installing &DISTRO; by entering
<command>memtest86</command> at the <prompt>boot:</prompt>
prompt. This causes the Memtest86 standalone memory testing
@@ -58,15 +103,16 @@
<keycap>Esc</keycap> key is pressed.
</para>
<para>
- <remark os="test">(x86)</remark> NOTE: You must boot from
+ <!-- <remark os="test">(x86)</remark> --> NOTE: You must boot from
CD-ROM 1 (or a rescue CD-ROM) in order to use this
feature.
</para>
</listitem>
<listitem>
- <remark os="test">%%% <ulink
+<!-- <remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627</ulink>
%%%</remark>
+-->
<para>
&DISTRO; &DISTROVER; supports graphical FTP and HTTP
installations. However, due to the necessity of containing
@@ -104,18 +150,18 @@
</listitem>
<listitem arch="x86">
<para>
- <remark os="test">(x86)</remark> Some Sony <trademark
+<!-- <remark os="test">(x86)</remark> --> Some Sony <trademark
class="registered">VAIO</trademark> notebook systems may
experience problems installing &DISTRO; from CD-ROM. If this
happens, restart the installation process and add the
following option to the boot command line:
</para>
- <para><remark os="test">(x86)</remark>
- <command>pci=off
+ <para>
+ <!-- <remark os="test">(x86)</remark> --> <command>pci=off
ide1=0x180,0x386</command>
</para>
<para>
- <remark os="test">(x86)</remark> This option allows the
+ <!-- <remark os="test">(x86)</remark> --> This option allows the
installation to proceed normally; any devices not detected due
to the use of this option will be configured the first time
&DISTRO; is booted.
@@ -135,7 +181,7 @@
</listitem>
<listitem arch="x86">
<para>
- <remark os="test">(x86)</remark> There have been issues
+ <!-- <remark os="test">(x86)</remark> --> There have been issues
observed when upgrading &RHL;
7.<replaceable><x></replaceable>, 8.0, 9, and &DISTRO; 1
systems where third party packages are installed that conflict
@@ -150,26 +196,26 @@
<orderedlist>
<listitem>
<para>
- <remark os="test">(x86)</remark> 1) You may remove Ximian
+ <!-- <remark os="test">(x86)</remark> --> 1) You may remove Ximian
GNOME from your system prior to upgrading to &DISTRO;.
</para>
</listitem>
<listitem>
<para>
- <remark os="test">(x86)</remark> 2) You may upgrade your
+ <!-- <remark os="test">(x86)</remark> --> 2) You may upgrade your
system, and then immediately reinstall Ximian GNOME.
</para>
</listitem>
<listitem>
<para>
- <remark os="test">(x86)</remark> 3) You may upgrade your
+ <!-- <remark os="test">(x86)</remark> --> 3) You may upgrade your
system, and then immediately remove all remaining Ximian
RPMs, replacing them with the corresponding &DISTRO; RPMs.
</para>
</listitem>
</orderedlist>
<para>
- <remark os="test">(x86)</remark> You
+ <!-- <remark os="test">(x86)</remark> --> You
<emphasis>must</emphasis> resolve the version overlap using
one of the above choices. Failure to do so will result in an
unstable GNOME configuration.
18 years, 10 months
release-notes/FC4 intro.xml,1.2,1.3
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25329
Modified Files:
intro.xml
Log Message:
Clarifying support stance, removing introductory cruft that is replaced by a real ToC.
Index: intro.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/intro.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- intro.xml 28 May 2005 16:10:31 -0000 1.2
+++ intro.xml 30 May 2005 17:05:10 -0000 1.3
@@ -1,59 +1,25 @@
- <section id="sn-intro">
- <title>Introduction</title>
-
- <para>The &PROJ; is an openly-developed project designed by &RH;, open for
- general participation, led by a meritocracy, and following a set of
- project objectives. The results from this project include &DISTRO;, a
- complete, general-purpose operating system built exclusively from open
- source software.</para>
-
- <note>
- <title>Note</title>
-
- <para>&DISTRO; is not a supported product of &FORMAL-RHI;</para>
- </note>
-
- <para>For more information, refer to the &PROJ; overview later in this
- document.</para>
-
- <para>The following topics related to &DISTRO; &DISTROVER; are covered in
- this document:</para>
-
- <itemizedlist>
- <listitem os="test">
- <para>Release notes feedback procedure</para>
- </listitem>
-
- <listitem>
- <para>Introduction (this section)</para>
- </listitem>
-
- <listitem>
- <para>Hardware requirements</para>
- </listitem>
-
- <listitem>
- <para>Overview of this release</para>
- </listitem>
-
- <listitem>
- <para>Installation-related notes</para>
- </listitem>
-
- <listitem>
- <para>Package-specific notes</para>
- </listitem>
-
- <listitem>
- <para>Packages added/removed/deprecated</para>
- </listitem>
-
- <listitem>
- <para>An overview of the &PROJ;</para>
- </listitem>
- </itemizedlist>
-
- </section>
+<section id="sn-intro">
+ <title>Introduction</title>
+ <para>
+ The &PROJ; is an openly-developed project designed by &RH;, open for
+ general participation, led by a meritocracy, and following a set of
+ project objectives. The results from this project include &DISTRO;,
+ a complete, general-purpose operating system built exclusively from
+ open source software.
+ </para>
+ <note>
+ <title>Note</title>
+ <para>
+ &FC; is a community supported project.
+ </para>
+ <para>
+ &FC; is not a commercially supported product of &FORMAL-RHI;.
+ </para>
+ </note>
+ <para>
+ For more information, refer to <xref linkend="sn-overview"/>.
+ </para>
+</section>
<!--
Local variables:
mode: xml
18 years, 10 months
release-notes/FC4 package-notes.xml, 1.8, 1.9 server-tools.xml, 1.2, 1.3
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24334
Modified Files:
package-notes.xml server-tools.xml
Log Message:
A little bit more fussiness, actually for the RHEL toolchain, didn't like the extra - and removed some whitespace while at it. This also includes some blather about s-c-lvm.
Index: package-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/package-notes.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- package-notes.xml 30 May 2005 16:42:05 -0000 1.8
+++ package-notes.xml 30 May 2005 16:51:59 -0000 1.9
@@ -209,6 +209,7 @@
in &FC; &LOCALVER;.
</para>
</section>
+ &SERVER-TOOLS;
</section>
<!-- Saving these just in case ...
<section os="bogus">
@@ -701,8 +702,8 @@
<term>Hotkeys</term>
<listitem>
<para>
- Trigger keys, such as <keycombo>
- <keycap>Ctrl</keycap>-<keycap>Space</keycap></keycombo>
+ 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
@@ -715,8 +716,8 @@
<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
+ <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>,
+ you
need to specify '<Control>at' as the keyname not
'<Control>@'.
</para>
@@ -951,8 +952,7 @@
</section>
-->
- &DATABASE-SERVERS;
- &SERVER-TOOLS;
+ &DATABASE-SERVERS;
&MULTIMEDIA;
<!--
<section os="bogus">
Index: server-tools.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/server-tools.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- server-tools.xml 28 May 2005 16:10:32 -0000 1.2
+++ server-tools.xml 30 May 2005 16:51:59 -0000 1.3
@@ -1,3 +1,18 @@
+<section id="sn-server-sys-config">
+ <title>Server and System Configuration Tools</title>
+ <para>
+ This section highlights changes and additions to the various GUI server
+ and system configuration tools in &FC;.
+ </para>
+ <section id="sn-system-config-lvm">
+ <title><application>system-config-lvm</application></title>
+ <para>
+ The new GFS management tool
+ <application>system-config-lvm</application> assists you in
+ managing logical volumes.
+ </para>
+ </section>
+</section>
<!--
Local variables:
mode: xml
18 years, 10 months
release-notes/FC4 install-notes.xml, 1.3, 1.4 package-notes.xml, 1.7, 1.8
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24253
Modified Files:
install-notes.xml package-notes.xml
Log Message:
Fixes some breakage of the build in the rawhide toolchain, which is more sensitive to garbage in the admonition tagset apparently.
Index: install-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/install-notes.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- install-notes.xml 30 May 2005 15:49:00 -0000 1.3
+++ install-notes.xml 30 May 2005 16:42:05 -0000 1.4
@@ -6,9 +6,6 @@
&DISTROVER; in general.
</para>
<note>
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134508">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134508</ulink>
- %%%</remark>
<title>Note</title>
<para>
If you intend to download the &DISTRO; &DISTROVER; DVD ISO
Index: package-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/package-notes.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- package-notes.xml 30 May 2005 16:22:46 -0000 1.7
+++ package-notes.xml 30 May 2005 16:42:05 -0000 1.8
@@ -133,7 +133,7 @@
on LinuxThreads. But this is intentional.
</para>
<important>
-- <title>Important</title>
+ <title>Important</title>
<para>
FC5 will not have LinuxThreads support and all programs have
to be converted to use NPTL by then.
18 years, 10 months
release-notes/FC4 Makefile,1.3,1.4
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24187
Modified Files:
Makefile
Log Message:
This brings over the figs/ directory.
Index: Makefile
===================================================================
RCS file: /cvs/docs/release-notes/FC4/Makefile,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Makefile 30 May 2005 15:08:13 -0000 1.3
+++ Makefile 30 May 2005 16:25:57 -0000 1.4
@@ -12,7 +12,9 @@
${RM} -r $@ ${@:.html=}
xmlto html -x ${XSLHTML} -o ${@:.html=} $<
mkdir -p ${@:.html=}/stylesheet-images
+ mkdir -p ${@:.html=}/figs
cp ../../stylesheet-images/*.png ${@:.html=}/stylesheet-images
+ cp ./figs/*.png ${@:.html=}/figs
cp ../../css/fedora.css ${@:.html=}
ln -s ${@:.html=}/index.html $@
18 years, 10 months