release-notes hardware-reqs-en.xml, 1.2, 1.3 install-notes-en.xml, 1.4, 1.5 splash-en.xml, 1.5, 1.6 xorg-en.xml, 1.4, 1.5
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14398
Modified Files:
hardware-reqs-en.xml install-notes-en.xml splash-en.xml
xorg-en.xml
Log Message:
- Updated PPC section in Hardware Requirements
- Removed additional Hardware Requirements section in PPC Installation Notes
- Set mailing list references as links in Welcome section
Index: hardware-reqs-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/hardware-reqs-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- hardware-reqs-en.xml 25 Oct 2005 09:07:12 -0000 1.2
+++ hardware-reqs-en.xml 24 Nov 2005 01:09:11 -0000 1.3
@@ -230,11 +230,8 @@
<listitem>
<para>
<!--<remark os="test">(ppc)</remark> --> &FC; &LOCALVER;
- supports only the <quote>New World</quote> generation of Apple
- Power Macintosh, shipped circa 1999 onwards. It also supports
- the 64-bit G5 processor and, POWER processors in IBM eServer
- pSeries. Currently 32-bit IBM RS/6000 machines are not
- supported.
+ supports the <quote>New World</quote> generation of Apple
+ Power Macintosh (shipped circa 1999 onwards), Genesi Pegasos II, and IBM 32-bit RS/6000 machines. It also supports the 64-bit G5 processor, and POWER processors in the IBM eServer pSeries.
</para>
</listitem>
<listitem>
Index: install-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- install-notes-en.xml 23 Nov 2005 05:38:24 -0000 1.4
+++ install-notes-en.xml 24 Nov 2005 01:09:11 -0000 1.5
@@ -32,35 +32,6 @@
</note>
<section id="sn-install-notes-ppc">
<title>PPC Installation Notes</title>
- <section id="sn-ppc-hardware-reqs">
- <title>PPC Hardware Requirements</title>
- <para>
- This section lists the minimum PowerPC (PPC) hardware needed
- to install &DISTRO; &DISTROVER;.
- </para>
- <itemizedlist>
- <listitem>
- <para>Minimum: PowerPC G3 / POWER4 </para>
- </listitem>
- <listitem>
- <para>&DISTRO; &DISTROVER; supports only the ���New World���
- generation of <trademark class="trade">Apple</trademark>
- Power Macintosh, shipped circa 1999 onwards.
- </para>
- </listitem>
- <listitem>
- <para>&DISTRO; &DISTROVER; also supports IBM eServer pSeries, IBM
- RS/6000, and Genesi Pegasos II machines.</para>
- </listitem>
- <listitem>
- <para>Recommended for text-mode: 233 MHz G3 or better, 64MiB
- RAM.</para>
- </listitem>
- <listitem>
- <para>Recommended for graphical: 400 MHz G3 or better, 128MiB
- RAM.</para>
- </listitem>
- </itemizedlist>
<para>
The DVD or first CD of the installation set of &FC; is set to be
bootable on supported hardware. In addition, bootable CD images
@@ -141,7 +112,6 @@
</varlistentry>
</variablelist>
</section>
- </section>
<section id="sn-anaconda-notes">
<title>Anaconda Notes</title>
Index: splash-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- splash-en.xml 23 Nov 2005 23:58:24 -0000 1.5
+++ splash-en.xml 24 Nov 2005 01:09:11 -0000 1.6
@@ -15,7 +15,7 @@
users.
</para>
<para>
- Subscribe to the fedora-test and fedora-devel mailings lists to
+ Subscribe to the <ulink url="https://www.redhat.com/mailman/listinfo/fedora-test-list/">fedora-test</ulink> and <ulink url="https://www.redhat.com/mailman/listinfo/fedora-devel-list">fedora-devel</ulink> mailing lists to
keep track of important changes in the current development
versions and provide feedback to the developers. &FP; requests you
to file bug reports and enhancements to provide a improved final
@@ -66,6 +66,11 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://fedoraproject.org/wiki/FAQ/">Fedora FAQ</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
Help and Support (<ulink
url="http://fedora.redhat.com/participate/communicate/">http://fedora.redhat.com/participate/communicate/</ulink>)
</para>
Index: xorg-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/xorg-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- xorg-en.xml 23 Nov 2005 23:58:24 -0000 1.4
+++ xorg-en.xml 24 Nov 2005 01:09:11 -0000 1.5
@@ -1,10 +1,6 @@
<section id="sn-xwindows">
<title>X Window System (Graphics)</title>
<section>
- <title>Docs/Beats/Xorg</title>
- <para/>
- </section>
- <section>
<title>X Window System (Graphics)</title>
<para>This section contains information related to the X Window
System implementation provided with &FED;.
18 years, 5 months
release-notes desktop-en.xml, 1.3, 1.4 development-tools-en.xml, 1.3, 1.4 java-package-en.xml, 1.2, 1.3 kernel-en.xml, 1.3, 1.4 package-movement-en.xml, 1.4, 1.5 package-notes-en.xml, 1.5, 1.6 security-en.xml, 1.3, 1.4 splash-en.xml, 1.4, 1.5 xorg-en.xml, 1.3, 1.4
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11155
Modified Files:
desktop-en.xml development-tools-en.xml java-package-en.xml
kernel-en.xml package-movement-en.xml package-notes-en.xml
security-en.xml splash-en.xml xorg-en.xml
Log Message:
- Replaced &FCVER; entities with &LOCALVER; to provide correct version numbers in text and headers
- Removed "Update for Fedora Core test1" notices, since it's now too late...
- Commented out Package Changes section, which is marked as lasted updated in September. See bug #173777 for argument that this should be dropped.
Index: desktop-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/desktop-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- desktop-en.xml 23 Nov 2005 05:38:24 -0000 1.3
+++ desktop-en.xml 23 Nov 2005 23:58:24 -0000 1.4
@@ -3,7 +3,7 @@
<itemizedlist>
<title>Notes</title>
<listitem>
- <para>GNOME 2.12 and KDE 3.4.2 are included in &FC; &FCVER;.
+ <para>GNOME 2.12 and KDE 3.4.2 are included in &FC; &LOCALVER;.
</para>
</listitem>
<listitem>
Index: development-tools-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/development-tools-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- development-tools-en.xml 23 Nov 2005 05:38:24 -0000 1.3
+++ development-tools-en.xml 23 Nov 2005 23:58:24 -0000 1.4
@@ -16,7 +16,7 @@
<section id="sn-java-development">
<title>Java-like Environment</title>
<para>A Java-like free and open source environment is available
- within the &FC; &FCVER; release.
+ within the &FC; &LOCALVER; release.
</para>
<para>
It has three components: GNU Java runtime
Index: java-package-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/java-package-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- java-package-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ java-package-en.xml 23 Nov 2005 23:58:24 -0000 1.3
@@ -1,12 +1,5 @@
<section id="sn-java-packages">
<title>Java Package Recommendations</title>
- <caution>
- <title>Information Out-of-Date</title>
- <para>
- The content in this section needs to be updated for &DISTRO;
- &DISTROVER;
- </para>
- </caution>
<para>
&FC; &LOCALVER; users are advised not to use the Java RPM provided
by Sun. It contains <computeroutput>Provides</computeroutput> that
Index: kernel-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/kernel-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- kernel-en.xml 23 Nov 2005 05:38:24 -0000 1.3
+++ kernel-en.xml 23 Nov 2005 23:58:24 -0000 1.4
@@ -18,7 +18,7 @@
<para>
This distribution is based on the 2.6 series of the Linux kernel.
&FC; may include patches for improvements, bug fixes, or
- additional features. For this reason, the &FCl kernel may not be
+ additional features. For this reason, the &FC; kernel may not be
line-for-line equivalent to the <firstterm>vanilla
kernel</firstterm> from the <ulink
url='http://www.kernel.org/'>http://www.kernel.org/</ulink>
@@ -63,7 +63,7 @@
<para>
The default kernels in x86_64 architecture provide the SMP
capability. There is no seperate SMP kernel available for this
- architecture in &FC; &FCVER;.
+ architecture in &FC; &LOCALVER;.
</para>
</note>
</section>
@@ -84,7 +84,7 @@
<section id="sn-kernel-dev">
<title>Preparing for Kernel Development</title>
<para>
- &FC; &FCVER; does not include the <filename>kernel-source</filename>
+ &FC; &LOCALVER; does not include the <filename>kernel-source</filename>
package provided by older versions. Instead, configured sources
are available as described in <xref linkend="sn-kernel-flavors"/>.
Users that require access to &FC; original kernel sources
@@ -248,7 +248,7 @@
<section id="kernel-user-space-depencies">
<title>User Space Dependencies on the Kernel</title>
<para>
- &PROD; &PRODVER; has support for clustered storage through the Red
+ &FC; &LOCALVER; has support for clustered storage through the Red
Hat GFS file system. This requires a special kernel that works in
conjunction with some user-space utilities, such as management
daemons. Consequently, to remove such a kernel, perhaps after an
Index: package-movement-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-movement-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- package-movement-en.xml 25 Oct 2005 19:40:56 -0000 1.4
+++ package-movement-en.xml 23 Nov 2005 23:58:24 -0000 1.5
@@ -2,8 +2,8 @@
<title>Packages Movement</title>
<!--
FIXME
- Needs updating of entire contents for FC4.
- -->
+ Needs updating of entire contents for FC5.
+
<para>
This command was used to generate the list of package changes. The
backslash <computeroutput>\</computeroutput> is used to artificially
@@ -932,6 +932,7 @@
<para>[111033] ncpfs-2.2.4-8 -> [115462] ncpfs-2.2.4-9 </para>
<para>[106079] prelink-0.3.4-3 -> [117615] prelink-0.3.6-1 </para>
<para>[110767] netpbm-10.27-3 -> [116518] netpbm-10.29-1 </para>
+-->
<section id="sn-packages-added">
<title>Packages Added</title>
<para>
@@ -1060,8 +1061,6 @@
</para>
-->
</section>
-
-</section>
<!--
Local variables:
mode: xml
Index: package-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- package-notes-en.xml 23 Nov 2005 06:55:57 -0000 1.5
+++ package-notes-en.xml 23 Nov 2005 23:58:24 -0000 1.6
@@ -37,13 +37,6 @@
easier access, they are generally organized using the same groups
used in Anaconda.
</para>
- <caution>
- <title>Information Out-of-Date</title>
- <para>
- The content in this section needs to be updated for &DISTRO;
- &DISTROVER;
- </para>
- </caution>
<section id="sn-basic-components">
<title>Basic Components</title>
<para>
Index: security-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/security-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- security-en.xml 23 Nov 2005 06:55:57 -0000 1.3
+++ security-en.xml 23 Nov 2005 23:58:24 -0000 1.4
@@ -16,10 +16,8 @@
<para>
This section highlights various security items from &FC;.
</para>
- <variablelist>
- <varlistentry>
- <term>Buffer Overflow detection and variable reordering</term>
- <listitem>
+ <section>
+ <title>Buffer Overflow detection and variable reordering</title>
<para>For this release, all of the software in the &FC; and
&FEX; software repositories is compiled using a security
feature called <firstterm>fstack-protecter</firstterm>.
@@ -32,14 +30,13 @@
application is started and makes it impossible to guess
remotely. This is a security feature that has been
backported from GCC 4.1 to the version of the GCC compiler
- used in &FC; &FCVER;.
+ used in &FC; &LOCALVER;.
</para>
<para>
This is in addition to using <envar>FORTIFY_SOURCE</envar>
from &FC; 4 onwards.
</para>
- </listitem>
- </varlistentry>
+ </section>
<section>
<para>
@@ -53,21 +50,20 @@
<filename>/etc/pki/CA/</filename>.
</para>
<para>
- Dovecot: A dovecot-openssl.cnf file is automatically installed in
- <filename>/etc/pki/dovecot/</filename>.
+ Dovecot: A <filename>dovecot-openssl.cnf</filename> file is automatically installed in <filename>/etc/pki/dovecot/</filename>.
</para>
</section>
<section id="sn-security-selinux-changes">
<title>SELinux Changes</title>
<para>
- MCS SELinux is in somewhere. Major highlight. For more
- information, read this informative article:
+ Mult-Category Security (MCS) SELinux is included in &FC; &LOCALVER;. For more information, read this informative article:
</para>
<para>
<ulink
url="http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/m...">http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/m...</ulink>
</para>
</section>
+ </section>
</section>
<!--
Local variables:
Index: splash-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- splash-en.xml 23 Nov 2005 06:55:57 -0000 1.4
+++ splash-en.xml 23 Nov 2005 23:58:24 -0000 1.5
@@ -84,10 +84,10 @@
</listitem>
</itemizedlist>
<section id="sn-new-in-fc">
- <title>What's New In &FC; &FCVER;</title>
+ <title>What's New In &FC; &LOCALVER;</title>
<itemizedlist>
<listitem>
- <para>Xen Virtualisation software and yum package manager are
+ <para>Xen virtualisation software and yum package manager are
now well integrated within the &FED; installer. The installer
interface is more streamlined. Remote logging and improved
support for tracebacks is included.
Index: xorg-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/xorg-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- xorg-en.xml 23 Nov 2005 06:55:57 -0000 1.3
+++ xorg-en.xml 23 Nov 2005 23:58:24 -0000 1.4
@@ -82,7 +82,7 @@
<para>The system app-defaults directory for X resources, is now
<filename>%{_datadir}/X11/app-defaults</filename>, which
expands to <filename>/usr/share/X11/app-defaults</filename> on
- &FC; &FCVER; and for future &RHEL; systems. </para>
+ &FC; &LOCALVER; and for future &RHEL; systems. </para>
</section>
<section id="sn-xorg-xft-config">
<title><filename>xft-config</filename> can't be found</title>
18 years, 5 months
docs-common/images watermark.png,1.1,1.2 watermark.svg,1.1,1.2
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/docs-common/images
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20060
Modified Files:
watermark.png watermark.svg
Log Message:
Minor correction: "NOT FOR REFERENCE" instead of "Not for reference". It
looks more imposing that way...
Index: watermark.svg
===================================================================
RCS file: /cvs/docs/docs-common/images/watermark.svg,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- watermark.svg 23 Nov 2005 06:30:23 -0000 1.1
+++ watermark.svg 23 Nov 2005 11:26:07 -0000 1.2
@@ -10,7 +10,7 @@
<g fill="&bgColor;" font-family="Helvetica" font-size="1in" stroke="&bgColor;" stroke-width="10" text-anchor="start" transform="translate( 1, 1 )">
<g transform="translate( 512, 384 ) rotate( -45 )">
<text font-stretch="wider" text-anchor="middle" x="0" y="0">DRAFT</text>
- <text fill="&fgColor;" font-size="0.6in" font-stretch="wider" stroke="rgb( 230, 200, 200 )" stroke-width="1.5" text-anchor="middle" x="0" y="1in">Not for reference.</text>
+ <text fill="&fgColor;" font-size="0.6in" font-stretch="wider" font-variant="small-caps" stroke="rgb( 230, 200, 200 )" stroke-width="1.5" text-anchor="middle" x="0" y="1in">NOT FOR REFERENCE</text>
</g>
</g>
</svg>
18 years, 5 months
release-notes legacy-en.xml, 1.1, 1.2 package-notes-en.xml, 1.4, 1.5 security-en.xml, 1.2, 1.3 splash-en.xml, 1.3, 1.4 web-servers-en.xml, 1.2, 1.3 xorg-en.xml, 1.2, 1.3
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10120
Modified Files:
legacy-en.xml package-notes-en.xml security-en.xml
splash-en.xml web-servers-en.xml xorg-en.xml
Log Message:
Last of the transfer of content from the Wiki, time to tag, build, and post.
Index: legacy-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/legacy-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legacy-en.xml 25 Oct 2005 08:34:00 -0000 1.1
+++ legacy-en.xml 23 Nov 2005 06:55:57 -0000 1.2
@@ -1,3 +1,50 @@
+<section id="sn-legacy">
+ <title>Legacy Information</title>
+
+ <note>
+ <title><command>Slocate</command> has been replaced with
+ <command>mlocate</command> in this release.</title>
+ <para>
+ The <command>/usr/bin/{locate,updatedb}</command>
+ implementation <command>slocate</command> was replaced by mlocate.
+ </para>
+ </note>
+ <itemizedlist>
+ <listitem>
+ <para>The <command>locate</command> command should be completely
+ compatible.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <listitem>
+ <para><filename>/etc/updatedb.conf</filename> is compatible for correct
+ configuration files
+ </para>
+ </listitem>.
+ <listitem>
+ <para>Syntax errors that <command>slocate</command> would not
+ detect are now reported.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The <envar>DAILY_UPDATE</envar> variable is not
+ supported.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The <command>updatedb</command> command is not compatible, custom
+ scripts using <command>updatedb</command> might have to be
+ changed.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ The LinuxThreads library, which has been deprecated in &FC; 4, is no
+ longer available in this release. NPTL has been the default
+ threading library since Red Hat Linux 9.
+ </para>
+</section>
<!--
Local variables:
mode: xml
Index: package-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- package-notes-en.xml 25 Oct 2005 19:40:56 -0000 1.4
+++ package-notes-en.xml 23 Nov 2005 06:55:57 -0000 1.5
@@ -114,6 +114,7 @@
<command>auditctl -e 1</command>
</screen>
</section>
+<!--
<section id="sn-nptl">
<title>LinuxThreads versus NPTL</title>
<para>
@@ -178,6 +179,7 @@
In general, conversion to using NPTL has not been an issue.
</para>
</section>
+ -->
<section>
<title>Enabling the <filename>slocate</filename> Database</title>
<para>
@@ -233,18 +235,7 @@
<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;.
- </para>
- </section>
- &SERVER-TOOLS;
+<!-- &SERVER-TOOLS; -->
&JAVA-PACKAGE;
</section>
<section id="sn-packages-core">
@@ -253,16 +244,6 @@
This section contains the most elemental components of &DISTRO;,
including the kernel.
</para>
- <section>
- <title>yum</title>
- <para>
- The sqllite database is now used by yum, and makes performance
- noticeably faster.
- </para>
- <para>
- The Fedora Extras repository is now enabled by default.
- </para>
- </section>
&KERNEL;
&SECURITY;
</section>
Index: security-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/security-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- security-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ security-en.xml 23 Nov 2005 06:55:57 -0000 1.3
@@ -4,15 +4,44 @@
This section highlights various security items from &FC;.
</para>
<para>
- <computeroutput>Pam_stack</computeroutput> is deprecated. More
- details available from fedora-test-list (<ulink
- url="http://www.redhat.com/mailman/listinfo/fedora-test-list">http://www.redhat.com/mailman/listinfo/fedora-test-list</ulink>
+ <computeroutput>Pam_stack</computeroutput> is deprecated. Linux-PAM
+ 0.78 and later contain the include directive that obsoletes the
+ <computeroutput>pam_stack</computeroutput> module.
+ <computeroutput>pam_stack</computeroutput> module usage is logged
+ with a deprecation warning. It might be removed in a future
+ release.
</para>
<section id="sn-security-highlights">
<title>Security Highlights</title>
<para>
This section highlights various security items from &FC;.
</para>
+ <variablelist>
+ <varlistentry>
+ <term>Buffer Overflow detection and variable reordering</term>
+ <listitem>
+ <para>For this release, all of the software in the &FC; and
+ &FEX; software repositories is compiled using a security
+ feature called <firstterm>fstack-protecter</firstterm>.
+ fstack-protector puts a canary value on the stack of
+ <computeroutput>key</computeroutput> functions. Just before
+ the return address and just before returning from that
+ value, that canary value is verified. If there was a buffer
+ overflow, the canary no longer matches and the program
+ aborts. The canary value is random for each time the
+ application is started and makes it impossible to guess
+ remotely. This is a security feature that has been
+ backported from GCC 4.1 to the version of the GCC compiler
+ used in &FC; &FCVER;.
+ </para>
+ <para>
+ This is in addition to using <envar>FORTIFY_SOURCE</envar>
+ from &FC; 4 onwards.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <section>
<para>
Digital certificates are now centralised in directories
under <filename>/etc/pki/</filename>. Users performing an upgrade must
Index: splash-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- splash-en.xml 25 Oct 2005 09:07:12 -0000 1.3
+++ splash-en.xml 23 Nov 2005 06:55:57 -0000 1.4
@@ -1,18 +1,33 @@
<section id="sn-splash">
<title>Welcome to &FC; &LOCALVER;</title>
- <caution>
- <title>Information Out-of-Date</title>
- <para>
- The content in this section needs to be updated for &DISTRO;
- &DISTROVER;
- </para>
- </caution>
<para>
&FC; is a completely free, user friendly, and secure general purpose
- platform based on Linux. The &FP; is an open source project that
- pioneers leading edge technology and concepts sponsored by &RH; and
+ platform based on Linux that is always free for anyone to use,
+ modify, and distribute, now and forever. The &FP; is an open source project that
+ pioneers leading edge technology and concepts, which is sponsored by &RH; and
supported by the &FED; community.
</para>
+ <caution>
+ <title>This is a test release, not intended for end-users</title>
+ <para>
+ This is a test release and is provided for developers and testers
+ to participate and provide feedback. It is not meant for end
+ users.
+ </para>
+ <para>
+ Subscribe to the fedora-test and fedora-devel mailings lists to
+ keep track of important changes in the current development
+ versions and provide feedback to the developers. &FP; requests you
+ to file bug reports and enhancements to provide a improved final
+ release to end users. For more information on this, refer to the
+ following document:
+ </para>
+ <para>
+ <ulink
+ url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'>http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink>.
+
+ </para>
+ </caution>
<tip>
<title>Latest Release Notes on the Web</title>
<para>
@@ -39,13 +54,11 @@
Refer to these webpages to find out more information about &FED;:
</para>
<itemizedlist>
-<!-- FIXME Return when the section is updated
<listitem>
<para>
<xref linkend="sn-new-in-fc"/>
</para>
</listitem>
--->
<listitem>
<para>
<xref linkend="sn-intro"/> — Technical release notes
@@ -70,6 +83,67 @@
</para>
</listitem>
</itemizedlist>
+ <section id="sn-new-in-fc">
+ <title>What's New In &FC; &FCVER;</title>
+ <itemizedlist>
+ <listitem>
+ <para>Xen Virtualisation software and yum package manager are
+ now well integrated within the &FED; installer. The installer
+ interface is more streamlined. Remote logging and improved
+ support for tracebacks is included.
+ </para>
+ </listitem>
+ <listitem>
+ <para><application>Pup</application>, a graphical updater using
+ yum, has replaced <application>rhn-applet</application>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>GNOME 2.12 and KDE 3.4 desktop environments are
+ available.
+ </para>
+ </listitem>
+ <listitem>
+ <para>GNOME Power Manager and GNOME Screensaver are available as
+ a technology preview within this release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ OpenOffice.org 2.0 final release is included. OpenOffice.org
+ now uses system versions for many of the libraries leading to
+ increased performance and efficiency.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Xorg X11R7 release candidate 2 has been included in this
+ release. This is the first modular version, which helps in
+ providing additional features and bug fixes at a faster pace.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Kernel 2.6.14 is included. Software suspend is enabled in this
+ release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>SCIM has replaced IIMF in &FC; in this release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>There are changes in the animated mouse cursor theme.
+ </para>
+ </listitem>
+ <listitem>
+ <para>&FP; now has a new logo.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>The proposed plans for Fedora in this version are available
+ from <ulink
+ url='http://fedoraproject.org/wiki/RoadMap'>http://fedoraproject.org/wiki/RoadMap</ulink>.
+ </para>
+ </section>
<!-- commented out until the content can be updated
<section id="sn-new-in-fc">
<title>New in &FC; &LOCALVER;</title>
Index: web-servers-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/web-servers-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- web-servers-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ web-servers-en.xml 23 Nov 2005 06:55:57 -0000 1.3
@@ -6,7 +6,7 @@
<section>
<title><command>httpd</command></title>
<para>
- The following changes have been made to the default <command></command>httpd
+ The following changes have been made to the default <command>httpd</command>
configuration:
</para>
<itemizedlist>
@@ -18,7 +18,7 @@
</listitem>
<listitem>
<para>The <computeroutput>mod_ext_filter</computeroutput> module
- is now loaded by default
+ is now loaded by default.
</para>
</listitem>
</itemizedlist>
Index: xorg-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/xorg-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- xorg-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ xorg-en.xml 23 Nov 2005 06:55:57 -0000 1.3
@@ -1,211 +1,162 @@
<section id="sn-xwindows">
<title>X Window System (Graphics)</title>
- <caution>
- <title>Information Out-of-Date</title>
- <para>
- The content in this section needs to be updated for &DISTRO;
- &DISTROVER;
- </para>
- </caution>
- <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; and &FED; 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 <firstterm>core X font subsystem</firstterm>. Fonts
- rendered by this subsystem are not anti-aliased, are handled
- by the X server, and have names such as:
- <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
- <firstterm>fontconfig</firstterm>, and allows applications
- direct access to the font files. Fontconfig is often used
- along with the <filename>Xft</filename> 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 <filename>Xft</filename> 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;
- almost 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>
+ <section>
+ <title>Docs/Beats/Xorg</title>
+ <para/>
+ </section>
+ <section>
+ <title>X Window System (Graphics)</title>
+ <para>This section contains information related to the X Window
+ System implementation provided with &FED;.
+ </para>
+ <section id="sn-xorg-x11">
+ <title>xorg-x11</title>
+ <para>X.org X11 is an open source implementation of the X Window
+ System. It provides the basic low level functionality that full
+ fledged graphical user interfaces (GUIs) such as GNOME and KDE
+ are designed upon. </para>
+ <para>For more information about Xorg refer to <ulink
+ url='http://xorg.freedesktop.org/wiki/'>http://xorg.freedesktop.org/wiki/</ulink>
+ </para>
+ <para>You can use
+ <guimenu>Applications</guimenu><guimenuitem>System
+ Settings</guimenuitem><guimenuitem>Display</guimenuitem> or
+ run <command>system-config-display</command> to configure the
+ settings. The configuration file for Xorg is located in
+ <filename>/etc/X11/xorg.conf</filename>.
+ </para>
<para>
- An exception to the font subsystem usage outlined above is
- OpenOffice.org, which uses its own font rendering technology.
+ Modular X.Org X11R7 RC2 was released into &FED; development
+ (<firstterm>rawhide</firstterm>) on November 16, 2005. This is
+ the first modular release of Xorg. Among several benefits,
+ modular Xorg enables users to receive updates at a faster pace,
+ while helping developers to develop and release specific
+ components in a rapid fashion.
</para>
- </note>
- <para>
- The steps to add new fonts to &DISTRO; &DISTROVER; depend on the
- fonts subsystem this is going to use the new fonts. For the core X
- font subsystem:
- </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>
-<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 (<command>xfs</command>) 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.
+ More information on the current status of the Xorg
+ modularization effort in &FED; is available from <ulink
+ url='/Xorg/Modularization'>http://fedoraproject.org/wiki/Xorg/Modularization</ulink>
</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 id="sn-xorg-x11r7-dev">
+ <title>Xorg X11R7 Developer Notes</title>
+ <para>X11R7 RC2 is included in this release and there are a number
+ of things that software developers, and packagers in &FED;
+ repositories, need to be aware of in order to ensure that their
+ software or software packages properly compile and work with
+ X11R7. Some are simple changes, while others may be more
+ involved. Here is a summary of issues that may arise and where
+ possible, suggestions on how to fix them.
+ </para>
+ <section>
+ <title>The <filename>/usr/X11R6</filename> directory hierarchy</title>
+ <para>
+ X11R7 installs into <filename>/usr</filename> directly now,
+ and no longer uses the <filename>/usr/X11R6</filename>
+ hierarchy. Applications that rely on files being present at
+ fixed paths under <filename>/usr/X11R6</filename> at compile
+ time or at run time, must be updated to use the system
+ <envar>PATH</envar>, or some other mechanism, to dynamically
+ determine where the files reside, or alternatively to hard
+ code the new locations, possibly with fallbacks.
+ </para>
+ </section>
+ <section>
+ <title><command>Imake</command></title>
+ <para><command>Imake</command> is no longer used to build the X
+ Window System, and as such is now officially deprecated.
+ <command>Imake</command>, <command>xmkmf</command> and other
+ utilities previously supplied by the X Window System, are
+ still supplied in X11R7, however X.Org highly recommends that
+ people migrate from Imake to using GNU autotools and
+ <filename>pkg-config</filename>. Support for
+ <command>imake</command> may vanish in a future X Window
+ System release, so developers are strongly encouraged to
+ transition away from it, and not to use it for any new
+ software projects.
+ </para>
+ </section>
+ <section>
+ <title>The systemwide app-defaults directory</title>
+ <para>The system app-defaults directory for X resources, is now
+ <filename>%{_datadir}/X11/app-defaults</filename>, which
+ expands to <filename>/usr/share/X11/app-defaults</filename> on
+ &FC; &FCVER; and for future &RHEL; systems. </para>
+ </section>
+ <section id="sn-xorg-xft-config">
+ <title><filename>xft-config</filename> can't be found</title>
+ <para>Modular X now uses GNU autotools, and
+ <command>pkg-config</command> for its buildsystem
+ configuration, etc. <command>xft-config</command> has been
+ deprecated for two to three years, and
+ <command>pkgconfig</command> <filename>*.pc</filename> files
+ have been provided for most of this time. Applications that
+ previously used <command>xft-config</command> to obtain the
+ <option>Cflags</option> or libs options for building with,
+ must now be updated to use <command>pkg-config</command>.
+ </para>
+ </section>
+ </section>
+ <section id="sn-xorg-devel-overview">
+ <title>Xorg X11R7 Developer Overview</title>
+ <para>Here is a short list of some of the more developer/package
+ visible changes that are present in X11R7: </para>
+ <itemizedlist>
+ <listitem>
+ <para>The entire buildsystem has changed from
+ <command>Imake</command> to the GNU autotools collection.
+ </para>
+ </listitem>
+ <listitem>
+ <para>All of the libraries now install
+ <command>pkgconfig</command> <filename>*.pc</filename>
+ files, which should now always be used by software that
+ depends on these libraries, instead of hard coding paths to
+ them in <filename>/usr/X11R6/lib</filename> or elsewhere.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Everything is now installed directly into
+ <filename>/usr</filename> instead of
+ <filename>/usr/X11R6</filename>. All software that hard
+ codes paths to anything in <filename>/usr/X11R6</filename>,
+ must now be changed preferably to dynamically detect the
+ proper location of the object, or to hard code the new paths
+ that X11R7 uses by default. It is strongly advised to use
+ autodetection methods rather than to hard code paths.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Every library has its own, private source package now,
+ which creates a runtime binary subpackage, and a -devel
+ subpackage.
+ </para>
+ <para>
+ Any software package that previously picked up the
+ development headers, etc. for X libraries by using
+ <computeroutput>BuildRequires:
+ (XFree86-devel|xorg-x11-devel)</computeroutput>, must now
+ individually list each library dependency individually. When
+ doing this, it is greatly preferred and strongly recommended
+ to use <firstterm>virtual</firstterm> build dependencies instead of hard coding
+ the library package names of the Xorg implementation.
+ </para>
+ <para>
+ This means you should use: <computeroutput>BuildRequires:
+ libXft-devel</computeroutput> instead of using:
+ <filename>BuildRequires: xorg-x11-Xft-devel</filename>. If
+ your software truly does depend on the X.Org X11
+ implementation of a specific library, and there is no other
+ clean/safe way to state the dependency, then use the
+ <filename>xorg-x11--devel</filename> form. By sticking to
+ the virtual provides/requires mechanism, this makes it
+ painless if and when the libraries move to another location
+ in the future.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
</section>
</section>
18 years, 5 months
docs-common/bin use-draft-css,NONE,1.1
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10007
Added Files:
use-draft-css
Log Message:
Shell script to switch to the "DRAFT" CSS stylesheet in an HTML directory.
--- NEW FILE use-draft-css ---
#!/bin/bash
########################################################################
# Tommy.Reynolds <Tommy.Reynolds(a)MegaCoder.com>
# International copyright secured (C) 2005, All rights reserved.
# This software is licensed under the GPL.
########################################################################
# Do surgery on the *.html files to reference the draft CSS stylesheet
#
# Use like this:
#
# use-draft-css /path/to/docdir
#
########################################################################
# You will need to manually copy "../css/fedora-draft.css" and
# "../images/watermark.png" into the HTML's top-level directory.
########################################################################
USAGE="usage: $(basename $0) /path/to/docdir"
SILENT=yes
while getopts v c
do
case "${c}" in
v ) SILENT="";;
* ) echo "${USAGE}" >&2; exit 1;;
esac
done
shift $(expr ${OPTIND} - 1)
if [ $# -gt 1 ]; then
echo "${USAGE}" >&2
exit 1
fi
find ${1:-.} -iname '*.html' -print |
while read f; do
[ "${SILENT}" ] || echo ${f}
sed 's/href="fedora.css"/href="fedora-draft.css"/' ${f} >${f}.tmp
mv ${f}.tmp ${f}
done
18 years, 5 months
docs-common/css fedora-draft.css,NONE,1.1 fedora.css,1.8,1.9
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/docs-common/css
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9963
Modified Files:
fedora.css
Added Files:
fedora-draft.css
Log Message:
FDP stylesheet for DRAFT versions. Needs "/watermark.png" in top level
HTML directory, get from "../images".
--- NEW FILE fedora-draft.css ---
/*
CSS for Red Hat Linux Project docs from the Documentation Project
Written by Tammy Fox and Garrett LeSage
Copyright 2003 Tammy Fox, Garrett LeSage, and Red Hat, Inc.
Copywight 2005 Tommy Reynolds <Tommy.Reynolds(a)MegaCoder.com>
License: GPL
*/
body {
background-attachment scroll;
background-color: #FEFEFF;
background-image: url('watermark.png');
background-position: top center;
background-repeat: repeat;
}
li p {
display: inline;
}
div.table table {
width: 95%;
background-color: #DCDCDC;
color: #000000;
border-spacing: 0;
}
div.table table th {
border: 1px solid #A9A9A9;
background-color: #A9A9A9;
color: #000000;
}
div.table table td {
border: 1px solid #A9A9A9;
background-color: #DCDCDC;
color: #000000;
padding: 0.5em;
margin-bottom: 0.5em;
margin-top: 2px;
}
div.note table, div.tip table, div.important table, div.caution table, div.warning table {
width: 95%;
border: 2px solid #D0D0B0;
background-color: #FAF9E0;
color: #000000;
/* padding inside table area */
padding: 0.5em;
margin-bottom: 0.5em;
margin-top: 0.5em;
}
.qandaset table {
border-collapse: collapse;
}
.qandaset {
}
.qandaset tr.question {
}
.qandaset tr.question td {
font-weight: bold;
padding: 1em 1em 0;
}
.qandaset tr.answer td {
padding: 0.25em 1em 1.5em;
}
.qandaset tr.question td, .qandaset tr.answer td {
}
hr {
border: 0;
border-bottom: 1px solid #ccc;
}
h1, h2, h3, h4 {
font-family: luxi sans,sans-serif;
color: #22437f;
font-weight: bold;
}
h1 {
font-size: 1.75em;
}
h2 {
font-size: 1.25em;
}
h3 {
font-size: 1.1em;
}
a:link {
color: #900;
}
a:visited {
color: #48468f;
}
a:hover {
color: #f20;
}
code.screen, pre.screen {
font-family: monospace;
font-size: 1em;
display: block;
padding: 10px;
border: 1px solid #bbb;
background-color: #eee;
color: #000;
overflow: auto;
border-radius: 2.5px;
-moz-border-radius: 2.5px;
margin: 0.5em 2em;
}
div.example {
padding: 10px;
border: 1px solid #bbb;
margin: 0.5em 2em;
}
.procedure ol li {
margin-bottom: 0.5em;
}
.procedure ol li li {
/* prevent inheritance */
margin-bottom: 0em;
}
.itemizedlist ul li {
margin-bottom: 0.5em;
}
.itemizedlist ul li li {
/* prevent inheritance */
margin-bottom: 0em;
}
p.title {
text-align: center;
}
Index: fedora.css
===================================================================
RCS file: /cvs/docs/docs-common/css/fedora.css,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora.css 3 Nov 2005 15:31:40 -0000 1.8
+++ fedora.css 23 Nov 2005 06:37:03 -0000 1.9
@@ -10,6 +10,17 @@
*/
+/*
+This "body" section is included for reference. Diff with fedora-draft.css
+body {
+ background-attachment scroll;
+ background-color: #FEFEFF;
+ background-image: url('watermark.png');
+ background-position: top center;
+ background-repeat: repeat;
+}
+*/
+
li p {
display: inline;
}
18 years, 5 months
docs-common/images Makefile, NONE, 1.1 watermark.png, NONE, 1.1 watermark.svg, NONE, 1.1
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/docs-common/images
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9927
Added Files:
Makefile watermark.png watermark.svg
Log Message:
Sample DRAFT watermark image, SVG source, and a Makefile to rule them all.
--- NEW FILE Makefile ---
.SUFFIXES: .png .svg
%.png: %.svg
batik -m image/png -h 768 -w 1024 -d `pwd`/$@ file://`pwd`/$<
SVGFILES=watermark.svg
PNGFILES=${SVGFILES:.svg=.png}
all: ${PNGFILES}
clean:
distclean clobber: clean
${RM} ${PNGFILES}
check: ${PNGFILES}
xv ${PNGFILES}
--- NEW FILE watermark.svg ---
<?xml version="1.0"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
"http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"[
<!ENTITY bgColor "rgb( 200, 200, 200 )" >
<!ENTITY fgColor "rgb( 255, 100, 100 )" >
]>
<svg viewBox="0 0 1023 767" xmlns="http://www.w3.org/2000/svg" version="1.1">
<title>Fedora Doc Project Watermark</title>
<desc>The word DRAFT rendered in grey at 45 degrees</desc>
<g fill="&bgColor;" font-family="Helvetica" font-size="1in" stroke="&bgColor;" stroke-width="10" text-anchor="start" transform="translate( 1, 1 )">
<g transform="translate( 512, 384 ) rotate( -45 )">
<text font-stretch="wider" text-anchor="middle" x="0" y="0">DRAFT</text>
<text fill="&fgColor;" font-size="0.6in" font-stretch="wider" stroke="rgb( 230, 200, 200 )" stroke-width="1.5" text-anchor="middle" x="0" y="1in">Not for reference.</text>
</g>
</g>
</svg>
18 years, 5 months
docs-common/images - New directory
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/docs-common/images
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9902/images
Log Message:
Directory /cvs/docs/docs-common/images added to the repository
18 years, 5 months
release-notes desktop-en.xml, 1.2, 1.3 development-tools-en.xml, 1.2, 1.3 entertainment-en.xml, 1.1, 1.2 fedora.css, 1.2, 1.3 file-servers-en.xml, 1.2, 1.3 i18n-en.xml, 1.1, 1.2 install-notes-en.xml, 1.3, 1.4 kernel-en.xml, 1.2, 1.3 multimedia-en.xml, 1.3, 1.4 project-overview-en.xml, 1.1, 1.2
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8043
Modified Files:
desktop-en.xml development-tools-en.xml entertainment-en.xml
fedora.css file-servers-en.xml i18n-en.xml
install-notes-en.xml kernel-en.xml multimedia-en.xml
project-overview-en.xml
Log Message:
Past the kernel beat, in alpha order, snapshot of what has been updated from the wiki for fc5test1.
Index: desktop-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/desktop-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- desktop-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ desktop-en.xml 23 Nov 2005 05:38:24 -0000 1.3
@@ -3,70 +3,88 @@
<itemizedlist>
<title>Notes</title>
<listitem>
- <para>GNOME 2.12 and KDE 3.4.2 Major highlight
+ <para>GNOME 2.12 and KDE 3.4.2 are included in &FC; &FCVER;.
</para>
</listitem>
<listitem>
- <para>The current test release has GNOME 2.12.1, together with
- some previews of technology from the forthcoming GNOME 2.14:
+ <para>This test release has GNOME 2.12.1, together with some
+ previews of technology from the forthcoming GNOME 2.14. Feedback
+ on these packages is especially appreciated.
</para>
<itemizedlist>
<listitem>
- <para>gnome-power-manager: brings the Hardware Abstraction
- Layer to the world of laptop batteries and UPS units - these
- things should "Just Work", with a simple UI (naturally, in
- a test release, they might not)
+ <para><filename>gnome-power-manager</filename>:
+ <application>GNOME Power Manager </application> is a session
+ daemon for the GNOME desktop environment that makes it easy
+ to manage power on your laptop or desktop system. It takes
+ advantage of HAL (which provides a hardware abstraction
+ layer) and DBUS (Inter Process Communication software)
+ written and maintained by &FC; developers.
</para>
</listitem>
<listitem>
- <para>gnome-screensaver: giving a fresh UI to screensavers and
- the <guilabel>Lock Screen</guilabel> dialog
+ <para><filename>gnome-screensaver</filename>: Provides a
+ integrated user interface to screensavers and the lock
+ screen dialog.
</para>
</listitem>
<listitem>
- <para>Memory optimizations in the fontconfig and
- shared-mime-info packages (these now use shared
- memory-mapped caches for this data). Both of these caches
- are still somewhat experimental.
+ <para>Memory optimizations in the
+ <filename>fontconfig</filename> and
+ <filename>shared-mime-info</filename> packages. These now
+ use shared memory-mapped caches for this data.
</para>
</listitem>
</itemizedlist>
</listitem>
- <para>
- Test feedback on these experimental packages is especially
- appreciated.
- </para>
- <para>
- GNOME 2.12 has removed the terminal option from the desktop root
- menu. nautilus-open-terminal in Fedora Extras repository provides a
- enhanced replacement. It is also mentioned in the GNOME 2.12 release
- notes itself but we might highlight it since the package is provided
- with the extras repository.
- </para>
- <para>
- Screensavers not installed by default anymore. Should explain why
- and provide commands to install them.
- </para>
- <para>MCS SELinux is in rawhide. Major highlight
- (<emphasis>tentative</emphasis> - not sure about classification of
- this change)
- </para>
- <caution>
- <title>OpenOffice and upgrading from test releases</title>
- <para>
- If you choose to go counter to the recommendation to <emphasis
- role='strong'>not</emphasis> upgrade from a previous test
- release, you may encounter a problem with <ulink
- url='/OpenOffice'>OpenOffice</ulink> following the upgrade.
- </para>
- <para>
- To resolve this, you must do the following command <emphasis
- role='strong'>before</emphasis> doing the upgrade:
- </para>
+ <listitem>
+ <para>GNOME 2.12 has removed the
+ <guimenuitem>terminal</guimenuitem> option from the desktop
+ context menu. The package
+ <filename>nautilus-open-terminal</filename> in &FEX;
+ repository provides an enhanced replacement for those who require
+ it. You can install it using the following command:
+ </para>
<screen>
-<command>rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
+<command>yum install nautilus-open-terminal</command>
</screen>
- </caution>
+ </listitem>
+ <listitem>
+ <para>Only the blank screensavers is installed by default, since
+ &FC; 4.
+ </para>
+ <para>
+ The primary issue is that some screensavers are known to not
+ work correctly or abruptly terminate the graphical interface.
+ This is particularly true for some of the OpenGL animated ones
+ provided within <filename></filename>xscreensaver-gl-extras
+ package.
+ </para>
+ <para>
+ In addition, the material content of the screensavers is
+ sometimes controversial or causes strong reactions. It is
+ better, for the user experience, to not be surprised by the
+ nature of the screensavers.
+ </para>
+ <para>
+ Users who want the screensavers package can install it using the following
+ command.
+ </para>
+<screen>
+<command>yum install xscreensaver-extras xscreensaver-gl-extras</command>
+</screen>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <title>Mouse configuration utility has changed</title>
+ <para>
+ The configuration utility
+ <application>system-config-mouse</application> has been dropped
+ from this release since synaptic and 3 button mouse configuration
+ is being done automatically during installation. Serial mice are
+ not formally supported in &FC; anymore.
+ </para>
+ </note>
</section>
<!--
Local variables:
Index: development-tools-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/development-tools-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- development-tools-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ development-tools-en.xml 23 Nov 2005 05:38:24 -0000 1.3
@@ -9,11 +9,39 @@
]>
-->
-<!-- Content commented out, no update performed by beat writer yet.
<section id="sn-devel">
<title>
Development Tools
</title>
+ <section id="sn-java-development">
+ <title>Java-like Environment</title>
+ <para>A Java-like free and open source environment is available
+ within the &FC; &FCVER; release.
+ </para>
+ <para>
+ It has three components: GNU Java runtime
+ (<filename>libgcj</filename>), the Eclipse Java compiler
+ (<command>ecj</command>), and a set of wrappers and links
+ (<filename>java-gcj-compat</filename>) that present the runtime
+ and compiler to the user in the same way as other Java
+ environments are presented.
+ </para>
+ <para>
+ Several major software packages such as Openoffice.org Base,
+ Eclipse, and Apache Tomcat, as well as several other Java software
+ packages included in this release, are compatible with this
+ environment.
+ </para>
+ <para>
+ For more information, refer to the FAQ:
+ </para>
+ <para>
+ <ulink
+ url='http://www.fedoraproject.org/wiki/JavaFAQ'>http://www.fedoraproject.org/wiki/JavaFAQ</ulink>
+ </para>
+ </section>
+
+<!-- Content commented out, no update performed by beat writer yet.
<section id="sn-devel-gcc">
<title>GCC Compiler Collection</title>
<para>
@@ -176,8 +204,9 @@
</listitem>
</itemizedlist>
</section>
-</section>
-->
+</section>
+
<!--
Local variables:
Index: entertainment-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/entertainment-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- entertainment-en.xml 25 Oct 2005 08:34:00 -0000 1.1
+++ entertainment-en.xml 23 Nov 2005 05:38:24 -0000 1.2
@@ -2,7 +2,7 @@
<title>Games and Entertainment</title>
<para>
&FC; and &FEX; provide a selection of games that cover a variety of
- genres. By default, &FC;includes a small package of games for GNOME
+ genres. By default, &FC; includes a small package of games for GNOME
(called <filename>gnome-games</filename>). For a list of other
games that are available for installation through
<command>yum</command>, open a terminal and enter the following
Index: fedora.css
===================================================================
RCS file: /cvs/docs/release-notes/fedora.css,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora.css 25 Oct 2005 02:48:50 -0000 1.2
+++ fedora.css 23 Nov 2005 05:38:24 -0000 1.3
@@ -132,3 +132,7 @@
/* prevent inheritance */
margin-bottom: 0em;
}
+
+p.title {
+ text-align: center;
+}
Index: file-servers-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/file-servers-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- file-servers-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ file-servers-en.xml 23 Nov 2005 05:38:24 -0000 1.3
@@ -24,12 +24,18 @@
<title><filename>netatalk</filename></title>
<para>
&DISTRO; &DISTROVER; includes version 2 of Netatalk.
- <emphasis>Upgrading from Netatalk version 1 to version 2 may
- result in data loss</emphasis>. Version 2 of Netatalk uses
- a different method to store file resource forks from the
- previous version, and may require a different file name encoding
- scheme. Please read the documentation and plan your migration
- before upgrading.
+ </para>
+ <caution>
+ <title>Take care when upgrading Netatalk versions</title>
+ <para>
+ Upgrading from Netatalk version 1 to version 2 may result in
+ data loss.
+ </para>
+ </caution>
+ <para>Version 2 of Netatalk uses a different method to store file
+ resource forks from the previous version, and may require a
+ different file name encoding scheme. Read the documentation and
+ plan your migration before upgrading.
</para>
<para>
Upgrade information is available directly from the Netatalk
Index: i18n-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/i18n-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- i18n-en.xml 25 Oct 2005 08:34:00 -0000 1.1
+++ i18n-en.xml 23 Nov 2005 05:38:24 -0000 1.2
@@ -9,100 +9,13 @@
This section includes information related to the support of
various languages under &DISTRO;.
</para>
- <section>
- <title>The IIIMF Input System</title>
+ <note>
+ <title>IIIMF replaced</title>
<para>
- IIIMF is the Internet/Intranet Input Method Framework. In &FC;
- &LOCALVER; the <filename>iiimf</filename> package is updated to
- version 12.2.
+ SCIM has replaced IIIMF in Fedora Core in this
+ release.
</para>
- <variablelist>
- <varlistentry>
- <term>File Path Changes</term>
- <listitem>
- <para>
- The names and locations of some files in the
- <filename>iiimf</filename> packages have changed.
- </para>
- <para>
- The IIIMF server has been renamed from
- <filename>/usr/sbin/htt</filename> to
- <filename>/usr/bin/iiimd</filename>, and the XIM bridge
- client renamed from <filename>httx</filename> to
- <filename>iiimx</filename>. The
- <filename>init.d</filename> script name has not changed:
- it is still called <filename>iiim</filename>. All the
- global system configuration files are now located under
- <filename>/etc/iiim/</filename>.
- </para>
- <para>
- Language Engine (LE) developers should note that LE
- modules and their data now live under
- <filename>${libdir}/iiim/le/<filename><LE_NAME></filename>/</filename>,
- while runtime data is stored under
- <filename>/var/lib/iiim/le/<replaceable><LE_NAME></replaceable>/</filename>.
- </para>
- <para>
- For more information on the exact path and file location
- changes, please refer to Fedora IIIMF FAQ:
- </para>
- <para>
- <ulink
- url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Hotkeys</term>
- <listitem>
- <para>
- Trigger keys, such as
- <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>
- used to activate Input Methods, are now configurable with
- the command-line tool <command>iiimf-le-tools</command>.
- This feature is only supported by GTK2 applications
- currently. For other applications using XIM the trigger
- key can be changed using an X resource. Refer to the
- IIIMF FAQ at <ulink
- url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>
- for more details on how to change trigger hotkeys.
- </para>
- <para>
- Note that the keyname refers to the X key symbol name. For
- example, if you want to activate with
- <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>,
- you need to specify '<Control>at' as the keyname not
- '<Control>@'.
- </para>
- <para>
- The per-user configuration of hotkeys does not work
- currently with &SEL; in enforcing mode due to lack of
- &SEL; policy. In this case, the hotkey can only be
- changed in the system-wide configuration.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Qt Support</term>
- <listitem>
- <para>
- A Qt immodule for <filename>iiimf</filename> is now
- included. This immodule works but lacks a status window
- and is considered experimental. Therefore, the default
- for Qt applications is to continue using XIM for IIMF
- input.
- </para>
- <para>
- If you wish to try the immodule in a Qt application, first
- install the <filename>iiimf-qt</filename> package, start
- the application, then click mouse button-3 in an input
- area and select <guimenuitem>iiimqcf</guimenuitem> from
- the <guisubmenu>Select Input Method</guisubmenu>' submenu.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
+ </note>
</section>
</section>
<!--
Index: install-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- install-notes-en.xml 25 Oct 2005 09:07:12 -0000 1.3
+++ install-notes-en.xml 23 Nov 2005 05:38:24 -0000 1.4
@@ -8,16 +8,17 @@
<note>
<title>Note</title>
<para>
- If you intend to download the &DISTRO; &DISTROVER; DVD ISO
- image, keep in mind that not all file downloading tools can
- accommodate files larger than 2GB in size. For example,
- <command>wget</command> will exit with a <computeroutput>File size
- limit exceeded</computeroutput> error.
+ If you intend to download the &DISTRO; &DISTROVER; DVD ISO image,
+ keep in mind that not all file downloading tools can accommodate
+ files larger than 2GiB in size. For example,
+ <command>wget</command> before version 1.9.1.16 in exits with a
+ <computeroutput>File size limit exceeded</computeroutput> error.
</para>
<para>
- The <command>curl</command> and <command>ncftpget</command>
- file downloading tools do not have this limitation, and can
- successfully download files larger than 2GB.
+ The <command>wget</command> version 1.9.1-16 and lter,
+ <command>curl</command> and <command>ncftpget</command> file
+ downloading tools do not have this limitation, and can
+ successfully download files larger than 2GiB.
</para>
<para>
Bittorrent is another method for downloading large files. For
@@ -31,7 +32,7 @@
</note>
<section id="sn-install-notes-ppc">
<title>PPC Installation Notes</title>
- <section>
+ <section id="sn-ppc-hardware-reqs">
<title>PPC Hardware Requirements</title>
<para>
This section lists the minimum PowerPC (PPC) hardware needed
@@ -42,8 +43,9 @@
<para>Minimum: PowerPC G3 / POWER4 </para>
</listitem>
<listitem>
- <para>&DISTRO; &DISTROVER; supports only the ���New World��� generation
- of Apple Power Macintosh, shipped circa 1999 onwards.
+ <para>&DISTRO; &DISTROVER; supports only the ���New World���
+ generation of <trademark class="trade">Apple</trademark>
+ Power Macintosh, shipped circa 1999 onwards.
</para>
</listitem>
<listitem>
@@ -51,11 +53,11 @@
RS/6000, and Genesi Pegasos II machines.</para>
</listitem>
<listitem>
- <para>Recommended for text-mode: 233 MHz G3 or better, 64MB
+ <para>Recommended for text-mode: 233 MHz G3 or better, 64MiB
RAM.</para>
</listitem>
<listitem>
- <para>Recommended for graphical: 400 MHz G3 or better, 128MB
+ <para>Recommended for graphical: 400 MHz G3 or better, 128MiB
RAM.</para>
</listitem>
</itemizedlist>
@@ -63,23 +65,22 @@
The DVD or first CD of the installation set of &FC; is set to be
bootable on supported hardware. In addition, bootable CD images
can be found in the <filename>images/</filename> directory of
- the DVD or first CD. These will behave differently according to
- the hardware:
+ the DVD or first CD. These behave differently according to the
+ hardware:
</para>
<variablelist>
<title>Boot Image Behavior by Hardware</title>
<varlistentry>
<term>Apple Macintosh </term>
<listitem>
- <para>The bootloader should automatically boot the
- appropriate 32-bit or 64-bit installer. Power management
- support, including sleep and backlight level management,
- is present in the <filename>apmud</filename> package,
- which is in &FEX;. &FEX; for &FC; is configured by default
- for yum. Following installation,
- <filename>apmud</filename> can be installed by running the
- command <command>yum install apmud</command> in a
- terminal.
+ <para>The bootloader automatically boots the appropriate
+ 32-bit or 64-bit installer. Power management support,
+ including sleep and backlight level management, is present
+ in the <filename>apmud</filename> package, which is in
+ &FEX;. &FEX; for &FC; is configured by default for yum.
+ Following installation, <filename>apmud</filename> can be
+ installed by running the command <command>yum install
+ apmud</command> in a terminal.
</para>
</listitem>
</varlistentry>
@@ -87,8 +88,8 @@
<term>64-bit IBM eServer pSeries (POWER4/POWER5)</term>
<listitem>
<para>After using OpenFirmware to boot the CD, the
- bootloader (<command>yaboot</command>) should
- automatically boot the 64-bit installer.
+ bootloader (<command>yaboot</command>) automatically boots
+ the 64-bit installer.
</para>
</listitem>
</varlistentry>
@@ -114,11 +115,11 @@
<command>boot cd: /images/netboot/ppc32.img</command>
</screen>
<para>
- You will also need to configure OpenFirmware on the
- Pegasos manually to make the installed &FC; system
- bootable. To do this, you need to set the
- <envar>boot-device</envar> and <envar>boot-file</envar>
- environment variables appropriately.
+ You also need to configure OpenFirmware on the Pegasos
+ manually to make the installed &FC; system bootable. To do
+ this, you need to set the <envar>boot-device</envar> and
+ <envar>boot-file</envar> environment variables
+ appropriately.
</para>
</listitem>
</varlistentry>
@@ -126,12 +127,13 @@
<term>Network booting</term>
<listitem>
<para>There are combined images containing the installer
- kernel and ramdisk in the images/netboot/ directory of the
+ kernel and ramdisk in the
+ <filename>images/netboot/</filename> directory of the
install tree. These are intended for network booting with
TFTP, but can be used in many ways.
</para>
<para>
- The command <command>yaboot</command> supports tftp
+ The command <command>yaboot</command> supports TFTP
booting for IBM eServer pSeries and Apple Macintosh. &FED;
recommends using yaboot over the netboot images.
</para>
@@ -140,7 +142,7 @@
</variablelist>
</section>
</section>
- <section>
+ <section id="sn-anaconda-notes">
<title>Anaconda Notes</title>
<itemizedlist>
@@ -175,10 +177,6 @@
</para>
</listitem>
<listitem arch="x86">
-<!-- <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
performed prior to installing &DISTRO; by entering
@@ -201,16 +199,70 @@
<para>
&DISTRO; &DISTROVER; supports graphical FTP and HTTP
installations. However, due to the necessity of containing
- the installer image in RAM, only systems with more than 128MB
+ the installer image in RAM, only systems with more than 128MiB
of RAM (or systems booted from CD-ROM 1, which contains the
installer image) can use the graphical installer. Systems
- with 128MB or less will continue to use the text-based
+ with 128MiB of RAM or less must continue to use the text-based
installer.
</para>
</listitem>
</itemizedlist>
</section>
- <section>
+ <section id="sn-installer-changes">
+ <title>Changes In The Installer</title>
+ <itemizedlist>
+ <listitem>
+ <para>Support has been added for <command>yum</command> as the
+ dependancy solver backend for software packages has been
+ added. Additional repositories are expected to be supported
+ during installation in a future release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>In this release, the installer checks the hardware
+ capability and installs either the uniprocessor or SMP
+ (Symmetric Multi Processor) kernel, as appropriate. Previous
+ releases installed both the variants and used the appropriate
+ one as default.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Partition setting has been reworked to be more user
+ friendly.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Remote logging via <command>syslog</command> is supported
+ in this release. To enable, pass
+ <option>syslog=host:port</option> at the boot prompt.
+ Specifying the port is optional.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Firewall/SELinux configuration has been moved to the final
+ installation phase called
+ <application>firstboot</application>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Rendering of HTML pages during install is now done using
+ the <command>gtkhtml</command> widget for better capability.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Kickstart has been refactored into its own package -
+ <filename>pykickstart</filename> - containing parser and
+ writers. As a result of this change, validation and extension
+ of kickstart is now much easier.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Serial mice are no long formally supported in the
+ installer nor in &FC;. </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="sn-install-related-issues">
<title>Installation-Related Issues</title>
<itemizedlist>
<listitem>
@@ -221,7 +273,6 @@
the installation, and add the "<command>nofb</command>" option
to the boot command line.
</para>
-
<note>
<title>Note</title>
<para>
Index: kernel-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/kernel-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- kernel-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ kernel-en.xml 23 Nov 2005 05:38:24 -0000 1.3
@@ -12,298 +12,258 @@
]>
-->
<section id="sn-kernel">
- <title>
- Linux Kernel
- </title>
- <section id="sn-kernel-lotsa">
+ <title>Linux Kernel</title>
+ <section id="sn-kernel-version">
<title>Version</title>
<para>
- The distribution is based on the 2.6 series of the Linux kernel. &FC; may include
- additional patches for improvements, bug fixes, or additional
- features. For this reason, the &FC; kernel may not be
- line-for-line equivalent to the vanilla<firstterm></firstterm> kernel from the
- <ulink
- url="http://www.kernel.org"><filename>kernel.org</filename></ulink>
+ This distribution is based on the 2.6 series of the Linux kernel.
+ &FC; may include patches for improvements, bug fixes, or
+ additional features. For this reason, the &FCl kernel may not be
+ line-for-line equivalent to the <firstterm>vanilla
+ kernel</firstterm> from the <ulink
+ url='http://www.kernel.org/'>http://www.kernel.org/</ulink>
website.
</para>
<para>
- You may obtain a list of any such patches by using the command on the &FC; package:
- </para>
-<screen width="56">
-<command>rpm <parameter class="option">-qpl</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
+ You may obtain a list of any such patches by using this command
+ on the &FC; package:</para>
+<screen>
+<command>rpm -qpl kernel-<version>.src.rpm</command>
</screen>
</section>
<section id="sn-kernel-flavors">
<title>Kernel Flavors</title>
- <para>
- &FC; includes the following kernel builds:
- </para>
+ <para>&FC; includes the following kernel builds: </para>
<itemizedlist>
<listitem>
- <para>Native kernel, in both uniprocessor and
- <abbrev>SMP</abbrev> varieties. Configured sources are
- available in the
+ <para>Native kernel, in both uniprocessor and SMP (Symmetric
+ Multi Processor) varieties. Configured sources are available
+ in the
<filename>kernel-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>
- package.
- </para>
+ package.
+ </para>
</listitem>
<listitem>
- <para>
- Virtual kernel for use with the <application>Xen</application>
- emulator package. Configured sources are available in the
+ <para>Virtual kernel for use with the Xen emulator package.
+ Configured sources are available in the
<filename>kernel-xen0-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>
- package.
- </para>
+ package. </para>
</listitem>
</itemizedlist>
<para>
Sources for both kernel flavors may be installed at the same time.
The files are installed into the
- <filename>/usr/src/kernels/<replaceable>version</replaceable>[-xen0]-<replaceable>arch</replaceable>/</filename>
- tree. Use the command:
- </para>
-<screen width="56">
-<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename></command>
-</screen>
- <para>
+ <filename>/usr/src/kernels/<replaceable>version</replaceable>[-xen0]-<replaceable>arch</replaceable>/</filename>
+ tree. Use the command <command>rpm -Uvh
+ kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</command>
as appropriate.
</para>
- <tip>
- <title>Following Generic Textbooks About the Linux Kernel</title>
+ <note>
+ <title>No separate SMP kernel for x86_64</title>
<para>
- Many of the tutorials, examples, and textbooks about Linux
- kernel development assume the kernel sources are installed under
- the <filename>/usr/src/linux</filename> directory. If you make a
- symbolic link, as shown below, you should be able to use those
- learning materials with the &FC; packages. Install the
- appropriate kernel sources, as shown earlier, and then:
+ The default kernels in x86_64 architecture provide the SMP
+ capability. There is no seperate SMP kernel available for this
+ architecture in &FC; &FCVER;.
</para>
-<screen width="56">
-<command>ln <parameter class="option">-s</parameter> <filename>/usr/src/kernels/kernel-<replaceable>all-the-rest</replaceable></filename> <filename>/usr/src/linux</filename></command>
-</screen>
- </tip>
+ </note>
</section>
- <!--
- <tip>
- <title>Using <command>yum</command> to Remove Kernel
- Packages</title>
+ <section>
+ <title>Following Generic Textbooks</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 remove older versions of the kernel packages.
+ Many of the tutorials, examples, and textbooks about Linux
+ kernel development assume the kernel sources are installed under
+ the <filename>/usr/src/linux/</filename> directory. If you make a symbolic
+ link, as shown below, you should be able to use those learning
+ materials with the &FC; packages. Install the appropriate
+ kernel sources, as shown earlier, and then do this:
</para>
+<screen>
+<command>ln -s /usr/src/kernels/kernel-<replaceable>version</replaceable>-<replaceable>arch</replaceable> /usr/src/linux</command>
+</screen>
+ </section>
+ <section id="sn-kernel-dev">
+ <title>Preparing for Kernel Development</title>
<para>
- When using <command>rpm -e kernel-<replaceable>version</replaceable> </command> to remove the kernel, you must also remove the assisting user-space packages. You may wish to consider a dependency resolving tool such as <command>yum remove kernel-<replaceable>version</replaceable> </command>.
- This automatically removes any dependent packages.
+ &FC; &FCVER; does not include the <filename>kernel-source</filename>
+ package provided by older versions. Instead, configured sources
+ are available as described in <xref linkend="sn-kernel-flavors"/>.
+ Users that require access to &FC; original kernel sources
+ can find them in the kernel <filename>.src.rpm</filename> package.
</para>
- </tip>
- -->
- <section id="sn-kernel-exploding">
- <title>
- Preparing for Kernel Development
- </title>
<para>
- &DISTRO; &DISTROVER; does not include the
- <filename>kernel-source</filename> package provided by older
- versions. Instead, configured sources are available as described
- in <xref
- linkend="sn-kernel-flavors"/>. Users that require access to &FC;
- original kernel sources can find them in the
- <filename>kernel</filename> <filename>.src.rpm</filename> package.
To create an exploded source tree from this file, perform the
following steps:
</para>
- <important>
- <title>These Instructions Refer to the Currently-running Kernel!</title>
- <para>
- To simplify the following directions, the assumption is that you
+ <tip>
+ <title>Instructions refer to currently-running kernel</title>
+ <para>
+ To simplify the following directions, it is assumed that you
want to configure the kernel sources to match your
- currently-running kernel. In the steps below, you must
- understand that the phrase
- <replaceable>version</replaceable> refers to the kernel
- version shown by this command:
+ currently-running kernel. In the steps below, the phrase
+ <replaceable>version</replaceable> refers to the kernel version
+ shown by the command <command>uname -r</command>.
</para>
-<screen width="56">
-<command>uname <parameter class="option">-r</parameter></command>
-</screen>
- </important>
- <procedure id="sn-kernel-exploding-steps">
+ </tip>
+ <procedure>
<step>
- <para>
- Obtain the
+ <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 <wordasword>SRPMS</wordasword>
- <abbrev>CD</abbrev> <filename>ISO</filename> image.
- </para>
- </listitem>
- <listitem>
- <para>The FTP site where you got the kernel package.
- </para>
- </listitem>
- <listitem>
- <para>By running the following command:
- </para>
-<!-- FIXME up2date is sorta deprecated for FC, how to do this with yum? -->
-<screen width="56">
-<command>up2date <parameter class="option">--get-source</parameter> <filename>kernel</filename></command>
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>The SRPMS directory on the appropriate SRPMS CD iso
+ image.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The FTP site where you got the kernel package.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Install by running this command:
+ </para>
+<screen>
+<command>yum install yum-utils yumdownloader --source kernel</command>
</screen>
- </listitem>
- </itemizedlist>
</step>
<step>
- <para>
- Install
+ <para>
+ Install
<filename>kernel-<replaceable>version</replaceable>.src.rpm</filename>
- using the command:
- </para>
-<screen width="56">
-<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
-</screen>
- <para>
- This writes the <abbrev>RPM</abbrev> contents into
+ using the command <command>rpm -Uvh
+ kernel-<replaceable>version</replaceable>.src.rpm</command>.
+ </para>
+ <para>
+ This writes the RPM contents into
<filename>/usr/src/redhat/SOURCES</filename> and
<filename>/usr/src/redhat/SPECS</filename>.
- </para>
+ </para>
</step>
<step>
- <para>
- Prepare the kernel sources using the commands:
- </para>
-<screen width="56">
-<command>cd <filename>/usr/src/redhat/SPECS</filename></command>
-<command>rpmbuild <parameter class="option">-bp --target $(arch)</parameter> <filename>kernel-2.6.spec</filename></command>
-</screen>
- <para>
- The kernel source tree is located in the
- <filename>/usr/src/redhat/BUILD/kernel-</filename><replaceable>version</replaceable>
+ <para>Prepare the kernel sources with these commands:
+ </para>
+<screen>
+<command>cd /usr/src/redhat/SPECS
+rpmbuild -bp --target $(arch) kernel-2.6.spec</command>
+</screen>
+ <para>
+ The kernel source tree is then located in the
+ <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable>/</filename>
directory. It is common practice to move the resulting
- <filename>linux-<replaceable>version</replaceable></filename>
- directory to the <filename>/usr/src</filename> tree; while not
- strictly necessary, doing so matches you with the
- generally-available documentation.
- </para>
-<screen width="56">
-<command>cd <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
-<command>mv <filename>linux-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
-<command>cd <filename>/usr/src</filename></command>
-<command>ln <parameter class="option">-s</parameter> <filename>./linux-<replaceable>version</replaceable></filename> <filename>linux</filename></command>
-<command>cd <filename>/usr/src/linux</filename></command>
+ <filename>linux-<replaceable>version</replaceable></filename> directory to the
+ <filename>/usr/src/</filename> tree; while not strictly
+ necessary, you can do this to match the generally-available kernel
+ documentation.
+ </para>
+<screen>
+<command>cd /usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable>
+mv linux-<replaceable>version</replaceable> /usr/src/
+cd /usr/src\
+ln -s ./linux-<replaceable>version</replaceable> linux
+cd /usr/src/linux</command>
</screen>
</step>
<step>
- <para>
- 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
+ <para>
+ The configurations for the specific kernels shipped in &FC;
+ 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>
-<screen width="56">
-<command>cp <filename>configs/<replaceable>desired-config-file</replaceable></filename> <filename>.config</filename></command>
-</screen>
- <para>
- You can also find the <filename>.config</filename> file that
+ file in the proper place for building: <command>cp
+ configs/<replaceable>desired-config-file</replaceable>
+ .config</command>
+ </para>
+ <para>
+ You can also find the <filename>.config</filename> file that
matches your current kernel configuration in the
- <filename>/lib/modules/</filename><replaceable>version</replaceable><filename>/build/.config</filename>
+ <filename>/lib/modules/<replaceable>version</replaceable>/build/.config</filename>
file.
- </para>
+ </para>
</step>
<step>
- <para>
- Every kernel gets a name based on its version number. This is
- the value the <command>uname -r</command> command displays.
- The kernel name is defined by the first four lines of the
- kernel <filename>Makefile</filename>. To protect the innocent,
- the <filename>Makefile</filename> has been changed to generate
- a kernel with a different name from that of the running
- kernel. Before a module can be accepted by the running kernel,
- that module must have been compiled for a kernel with the
- correct name. To do this, you must edit the kernel
- <filename>Makefile</filename>
- </para>
- <para>
- For example, if the <command>uname -r</command> returns the
- string <systemitem
- class="osname">2.6.11-1.234_FC4</systemitem>, change the
- <systemitem class="macro">EXTRAVERSION</systemitem> definition
- from this:
- </para>
-<screen width="60">
+ <para>
+ Every kernel gets a name based on its version number. This is
+ the value displayed by the command <command>uname
+ -r</command>. The kernel name is defined by the first four
+ lines of the kernel Makefile. To protect from mistakes, the
+ Makefile has been changed to generate a kernel with a
+ different name from that of the running kernel. Before a
+ module can be accepted by the running kernel, that module must
+ have been compiled for a kernel with the correct name. To do
+ this, you must edit the kernel Makefile.
+ </para>
+ <para>For example, if <command>uname -r</command> returns the string
+ <computeroutput>2.6.11-1.234_FC4</computeroutput>, change the
+ <envar>EXTRAVERSION</envar> definition from this:
+ </para>
+<screen>
EXTRAVERSION = -prep
</screen>
- <para>
+ <para>
to this:
</para>
-<screen width="60">
+<screen>
EXTRAVERSION = -1.234_FC4
</screen>
- <para>
- That is, substitute everything from the final dash onward.
- </para>
- </step>
+ <para>This represents everything from the final dash onward in the
+ package name.
+ </para>
+ </step>
<step>
- <para>
- Issue the following command:
- </para>
-<screen width="56">
+ <para>
+ Issue the following command:
+ </para>
+<screen>
<command>make oldconfig</command>
</screen>
- </step>
+ <para>You can then proceed as usual. </para></step>
</procedure>
- <para>
- You can then proceed as usual.
- </para>
</section>
- <section id="sn-kernel-3rdparty">
+ <section id="sn-kernel-modules-building">
<title>Building Only Kernel Modules</title>
<para>
- An exploded source tree is <emphasis>not</emphasis> required to
- build a kernel module, such as your own device driver, against the
- currently in-use kernel.
- </para>
- <para>
- For example, to build the <filename>foo.ko</filename> module,
- create the following <filename>Makefile</filename> in the
+ 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 <filename>foo.ko</filename>
+ module, create the following <filename>Makefile</filename> in the
directory containing the <filename>foo.c</filename> file:
</para>
-<programlisting width="56">
+<screen>
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
-default:
- $(MAKE) -C $(KDIR) M=$(PWD) modules
-</programlisting>
- <para>
- Issue the <command>make</command> command to build the
+ndefault:
+ $(MAKE) -C $(KDIR) M=$(PWD) modules
+</screen>
+ <para>Issue the <command>make</command> command to build the
<filename>foo.ko</filename> module.
- </para>
+</para>
</section>
- <section id="sn-kernel-coop">
+ <section id="kernel-user-space-depencies">
<title>User Space Dependencies on the Kernel</title>
<para>
- &DISTRO; adds support for clustered systems. This requires a
- special kernel that works in conjunction with some user-space
- utilities, such as management daemons. Consequently, to remove
- such a kernel, perhaps after an update, you
- <emphasis>cannot</emphasis> simply use the <command>rpm -e
+ &PROD; &PRODVER; has support for clustered storage through the Red
+ Hat GFS file system. This requires a special kernel that works in
+ conjunction with some user-space utilities, such as management
+ daemons. Consequently, to remove such a kernel, perhaps after an
+ update, you cannot simply use the <command>rpm -e
kernel-<replaceable>version</replaceable></command> command as
in earlier distributions because these user space packages depend
- on the kernel package. You may either list both the kernel package
- and its user space dependent packages on the <command>rpm
- -e</command> command, or you may wish to use the <command>yum
- remove kernel-<replaceable>version</replaceable></command>
- command instead since <command>yum</command> automatically removes
- dependent packages if necessary.
+ on the kernel package.
+ </para>
+ <para>
+ You may either list both the kernel package and its user space
+ dependent packages on the <command>rpm -e</command> command, or
+ you may wish to use the <command>yum remove
+ kernel-<replaceable>version</replaceable></command> command
+ instead since <command>yum</command> automatically removes
+ dependent packages if necessary.
</para>
</section>
</section>
Index: multimedia-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/multimedia-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- multimedia-en.xml 25 Oct 2005 09:07:12 -0000 1.3
+++ multimedia-en.xml 23 Nov 2005 05:38:24 -0000 1.4
@@ -69,12 +69,8 @@
<para>
Several programs are excluded from &FC; and &FEX; due to licensing
issues. These include programs that provide MP3 and DVD support,
- Flash Player and Real Player. Users who wish to use these
- programs or restricted formats have to acquire additional
- packages from third-party repositories. Many of the multimedia
- applications in the Fedora repositories support plugins, so
- support for new formats can be easily added or removed. For more
- on this subject, please see:
+ Flash Player and Real Player. For more on this subject, please
+ refer to:
</para>
<para>
<ulink url='http://fedoraproject.org/wiki/ForbiddenItems'>http://fedoraproject.org/wiki/ForbiddenItems</ulink>
Index: project-overview-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/project-overview-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project-overview-en.xml 25 Oct 2005 02:48:50 -0000 1.1
+++ project-overview-en.xml 23 Nov 2005 05:38:24 -0000 1.2
@@ -47,27 +47,35 @@
Documentation Project
</para>
</listitem>
- </itemizedlist>
- <para>
- To subscribe to any of these lists, send an email with the word
- "subscribe" in the subject to
- <computeroutput><replaceable><listname></replaceable>-request</computeroutput>
- (where
- <computeroutput><replaceable><listname></replaceable></computeroutput>
- is one of the above list names.)
- </para>
- <para>
- Alternately, you can subscribe through the Web interface:
- </para>
- <para>
- <ulink url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
- </para>
+ <listitem>
+ <para>
+ fedora-ambassadors-list(a)redehat.com — For community
+ members who represent the &PROJ; in public.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ To subscribe to any of these lists, send an email with the word
+ "subscribe" in the subject to
+ <computeroutput><replaceable><listname></replaceable>-request</computeroutput>
+ (where
+ <computeroutput><replaceable><listname></replaceable></computeroutput>
+ is one of the above list names.)
+ </para>
+ <para>
+ Alternately, you can subscribe through the Web interface:
+ </para>
+ <para>
+ <ulink url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
+ </para>
+ <!-- Aren't we quite past this? Saving just in case we are not.
<para>
If you have subscribed in the past to rhl-list, rhl-beta-list,
rhl-devel-list, or rhl-docs-list, your subscriptions have been
retained.
</para>
- <para>
+ -->
+ <para>
The &PROJ; also includes an IRC (Internet Relay Chat) channel. IRC is
a real-time, text-based form of communication. With it, you can have
conversations with multiple people in an open channel or chat with someone
@@ -88,7 +96,7 @@
<para>
In order to talk on the <filename>#fedora</filename> channel, you
will need to register your nickname (<firstterm>nick</firstterm>).
- Instructions are given when you <command>/join</command> the
+ Instructions are given when you first <command>/join</command> the
channel.
</para>
<note>
18 years, 5 months
release-notes colophon-relnotes-it.xml,NONE,1.1
by fedora-docs-commits@redhat.com
Author: tombo
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19976/release-notes
Added Files:
colophon-relnotes-it.xml
Log Message:
italian translation added to cvs
--- NEW FILE colophon-relnotes-it.xml ---
<section id="sn-colophon">
<title>&FC; Release Notes Colophon</title>
<note>
<title>Colophon preliminare</title>
<para>
E' preliminare, perci�� incompleta ed imperfetta.
</para>
</note>
<para>Per come lo intendiamo noi, colophon significa: </para>
<itemizedlist>
<listitem>
<para> Un modo per dare riconoscenza ai contributori, e nel contempo
le responsabilit��. </para>
</listitem>
<listitem>
<para> Spiegazione degli strumenti e dei metodi di produzione. </para>
</listitem>
</itemizedlist>
<section>
<title>Contributori</title>
<itemizedlist>
<listitem>
<para>
Andrew Martynov (translator, Russian) </para>
</listitem>
<listitem>
<para>
Anthony Green (beat writer)
</para>
</listitem>
<listitem>
<para>
Bob Jensen
</para>
</listitem>
<listitem>
<para>
Dave Malcolm (beat writer)
</para>
</listitem>
<listitem>
<para>
David Woodhouse (beat writer) </para>
</listitem>
<listitem>
<para>
Francesco Tombolini (translator, Italian) </para>
</listitem>
<listitem>
<para>
Gavin Henry (beat writer)
</para>
</listitem>
<listitem>
<para>
Jens Petersen (beat writer)
</para>
</listitem>
<listitem>
<para>
Joe Orton (beat writer) </para>
</listitem>
<listitem>
<para>
Josh Bressers (beat writer)
</para>
</listitem>
<listitem>
<para>
Karsten Wade (beat writer, editor-in-chief, publisher) </para>
</listitem>
<listitem>
<para>
LuyaTshimbalanga (beat writer) </para>
</listitem>
<listitem>
<para>
PatrickBarnes (beat writer, editor) </para>
</listitem>
<listitem>
<para>
Rahul Sundaram (beat writer, editor) </para>
</listitem>
<listitem>
<para>
Sekine Tatsuo (translator, Japanese) </para>
</listitem>
<listitem>
<para>
Steve Dickson (beat writer)
</para>
</listitem>
<listitem>
<para>
Stuar tElliss (editor)
</para>
</listitem>
<listitem>
<para>
Thomas Graf (beat writer)
</para>
</listitem>
<listitem>
<para>
Tommy Reynolds (tools)
</para>
</listitem>
<listitem>
<para>
Yoshinari Takaoka (translator, tools) </para>
</listitem>
<listitem>
<para>
Yuan Yijun (translator, Simplified Chinese) </para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Production Methods</title>
</section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
18 years, 5 months