release-notes/devel/en_US Feedback.xml,1.10,1.11
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20073
Modified Files:
Feedback.xml
Log Message:
Good for FC6
Index: Feedback.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Feedback.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- Feedback.xml 24 Sep 2006 20:41:49 -0000 1.10
+++ Feedback.xml 25 Sep 2006 07:38:42 -0000 1.11
@@ -53,8 +53,7 @@
Fill out a bug request using this template:
<ulink url='http://tinyurl.com/nej3u'/> -
<emphasis role='strong'>This link is ONLY for feedback on the
- release notes themselves.</emphasis> Refer to the admonition
- above for details.
+ release notes themselves</emphasis>
</para>
</listitem>
<listitem>
17 years, 8 months
release-notes/devel/en_US Extras.xml,1.9,1.10
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18710
Modified Files:
Extras.xml
Log Message:
Good for FC6
Index: Extras.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Extras.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- Extras.xml 24 Sep 2006 20:41:49 -0000 1.9
+++ Extras.xml 25 Sep 2006 07:29:49 -0000 1.10
@@ -11,7 +11,7 @@
<listitem override='none'>
<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
<para>
- Fedora Extras is an extension of Fedora Core which provides many
+ Fedora Extras is an extension of Fedora Core that provides many
additional packages for users of the Fedora distribution.
</para>
</listitem>
@@ -202,7 +202,7 @@
review to Fedora Extras. After a successful review, import it to
Extras and you can maintain it there. If you don't know how to
create RPM packages, there are many other ways to get involved in
- Fedora Extras and help drive it forward.
+ Fedora Extras and help the project.
</para>
<para>
To learn more about how to use Fedora Extras or how to get
@@ -214,7 +214,7 @@
<section>
<title>Package Updates</title>
<para>
- This section discusses changes in Fedora Extras packages which
+ This section discusses changes in Fedora Extras packages that
affect this release of Fedora Core.
</para>
<section>
@@ -224,8 +224,8 @@
provided in Fedora Extras 6. It was the original implementation
of
<ulink url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/SpamAssassin'>SpamAssassin</ulink>
- integration with Exim, and was functionally similar to sendmail
- 'milters' or postfix filters. However, that functionality is
+ integration with Exim, and was functionally similar to <code>sendmail</code>
+ milters or <code>postfix</code> filters. However, that functionality is
rather limited, and Exim now has far better support for content
checking, fully integrated into its general-purpose Access
Control Lists.
17 years, 8 months
release-notes/devel/en_US Desktop.xml,1.7,1.8 Xorg.xml,1.8,1.9
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15788
Modified Files:
Desktop.xml Xorg.xml
Log Message:
Updating to match the actual standards.
Index: Desktop.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Desktop.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- Desktop.xml 25 Sep 2006 06:51:21 -0000 1.7
+++ Desktop.xml 25 Sep 2006 07:14:12 -0000 1.8
@@ -34,7 +34,7 @@
<orderedlist numeration='arabic'>
<listitem>
<para>
- <emphasis>System => Preferences => More => Desktop
+ <emphasis>System > Preferences > More > Desktop
Effects</emphasis>
</para>
</listitem>
Index: Xorg.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Xorg.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- Xorg.xml 24 Sep 2006 20:41:50 -0000 1.8
+++ Xorg.xml 25 Sep 2006 07:14:12 -0000 1.9
@@ -42,10 +42,10 @@
The X server will query the attached monitor for supported
resolution ranges, and attempt to pick the highest resolution
available with the correct aspect ratio for the display. Users can
- set their preferred resolution in <emphasis>System => Preferences
- => Screen Resolution</emphasis>, and the default resolution for
- the system can be changed with <emphasis>System => Administration
- => Display</emphasis>.
+ set their preferred resolution in <emphasis>System > Preferences
+ > Screen Resolution</emphasis>, and the default resolution for
+ the system can be changed with <emphasis>System > Administration
+ > Display</emphasis>.
</para>
<para>
If the <code>/etc/X11/xorg.conf</code> configuration file is not
@@ -81,7 +81,7 @@
such as those used in some widescreen displays, you may want to
switch to the <code>intel</code> driver. You may switch drivers by
using <code>system-config-display</code>, available in the menus
- under <emphasis>System => Administration => Display</emphasis>.
+ under <emphasis>System > Administration > Display</emphasis>.
</para>
<para>
We welcome feedback on the experimental <code>intel</code> driver.
17 years, 8 months
release-notes/devel/en_US Devel.xml,1.1,1.2
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10719
Modified Files:
Devel.xml
Log Message:
Good for FC6
Index: Devel.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Devel.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Devel.xml 24 Sep 2006 21:16:38 -0000 1.1
+++ Devel.xml 25 Sep 2006 07:00:27 -0000 1.2
@@ -5,297 +5,296 @@
<section id="sn-Devel">
<title>Development</title>
-<!--RAW HTML: <h2>Development</h2>-->
-
+ <!--RAW HTML: <h2>Development</h2>-->
+
<para>
This section covers various development tools and features.
</para>
+ <section>
+ <title>Runtime</title>
+ <para>
+ These are the new features in <code>glibc</code>:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Support for priority inheriting and priority protecting
+ mutexes. These are two features described in the POSIX
+ standards.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Priority inheriting mutexes automatically prevent
+ priority inversion caused by waiting for the
+ availability of mutexes. The kernel automatically boosts
+ the priority of the thread holding the mutex until it
+ unlocks the mutex.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Priority protection allows to specify a priority that
+ all threads that acquire the mutex will run with until
+ the mutex is unlocked. This feature is not available for
+ robust mutexes.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ The destination address sorting performed by the
+ <code>getaddrinfo()</code> interface for hostname lookup can
+ now be customized by rules in the <code>/etc/gai.conf</code>
+ file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Significant speed-ups in NIS and NIS+ processing.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ RFC 3542 support completed (advanced socket APIs for IPv6).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Significant speed-ups of dynamic symbol lookup.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section>
+ <title>Tools</title>
+ <para>
+ The linker includes support for the new ELF symbol hash table
+ format. Use the <code>--hash-style</code> option of the linker
+ to select the format(s).
+ </para>
<section>
- <title>Runtime</title>
+ <title>Kernel header files</title>
<para>
- These are the new features in <code>glibc</code>:
+ This release of Fedora has been built using Linux kernel
+ headers exported directly from the kernel, using the new
+ <code>headers_install</code> feature of the 2.6.18 kernel.
+ Thus, the <code>glibc-kernheaders</code> package has been
+ removed and replaced with <code>kernel-headers</code>, a
+ subpackage of <code>kernel</code>.
+ </para>
+ <para>
+ Developers may notice some changes between these new kernel
+ headers and what was present before, including but not limited
+ to the following:
</para>
<itemizedlist>
- <listitem>
- <para>
- Support for priority inheriting and priority protecting
- mutexes. These are two features described in the POSIX
- standards.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Priority inheriting mutexes automatically prevent
- priority inversion caused by waiting for the
- availability of mutexes. The kernel automatically boosts
- the priority of the thread holding the mutex until it
- unlocks the mutex.
- </para>
- </listitem>
- <listitem>
- <para>
- Priority protection allows to specify a priority that
- all threads that acquire the mutex will run with until
- the mutex is unlocked. This feature is not available for
- robust mutexes.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
- The destination address sorting performed by the
- <code>getaddrinfo()</code> interface for hostname lookup can
- now be customized by rules in the <code>/etc/gai.conf</code>
- file.
- </para>
- </listitem>
- <listitem>
- <para>
- Significant speed-ups in NIS and NIS+ processing.
- </para>
- </listitem>
- <listitem>
- <para>
- RFC 3542 support completed (advanced socket APIs for IPv6).
- </para>
- </listitem>
- <listitem>
- <para>
- Significant speed-ups of dynamic symbol lookup.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The <code><linux/compiler.h></code> header file has
+ been removed, since it contains nothing of use to
+ userspace.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <code>_syscallX()</code> macros are removed. Userspace
+ should use <code>syscall()</code> from the C library
+ instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <code>PAGE_SIZE</code> macro is removed from some
+ architectures, since the page size is variable. Userspace
+ should be using <code>sysconf(_SC_PAGE_SIZE)</code> or
+ <code>getpagesize()</code> instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <code><asm/atomic.h></code> and
+ <code><asm/bitops.h></code> header files have been
+ removed. These were not designed for use in userspace, and
+ would fail to compile on some architectures while silently
+ giving non-atomic behaviour on others. The C compiler
+ provides its own
+ <ulink url='http://gcc.gnu.org/onlinedocs/gcc-4.1.1/gcc/Atomic-Builtins.html#Atomic-B...'>atomic
+ builtin functions</ulink> that are suitable for use in
+ userspace programs instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Content that was previously protected with <code>#ifdef
+ __KERNEL__</code> is now elided completely with the
+ <code>unifdef</code> tool. Defining
+ <code>__KERNEL___</code> in order to see parts that
+ should not be visible to userspace is no longer effective.
+ </para>
+ </listitem>
</itemizedlist>
+ <para>
+ In addition, some other header files that xare not suitable
+ for use in userspace have been removed, and still more headers
+ have been edited to remove unsuitable content.
+ </para>
+ <para>
+ <note>
+ <title>Kernel header changes are not Fedora-specific</title>
+ <para>
+ These changes are inherited from the upstream kernel and
+ are not specific to Fedora. Any distribution using the
+ current officially-exported kernel headers would be the
+ same.
+ </para>
+ </note>
+ </para>
</section>
-
<section>
- <title>Tools</title>
+ <title>GCC Compiler Collection</title>
<para>
- The linker includes support for the new ELF symbol hash table
- format. Use the <code>--hash-style</code> option of the linker
- to select the format(s).
+ This release of Fedora has been built with GCC 4.1, which
+ is included with the distribution.
</para>
<section>
- <title>Kernel header files</title>
- <para>
- This release of Fedora has been built using Linux kernel
- headers exported directly from the kernel, using the new
- <code>headers_install</code> feature of the 2.6.18 kernel.
- Thus, the <code>glibc-kernheaders</code> package has been
- removed and replaced with <code>kernel-headers</code>, a
- subpackage of <code>kernel</code>.
- </para>
- <para>
- Developers may notice some changes between these new kernel
- headers and what was present before, including but not limited
- to the following:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- The <code><linux/compiler.h></code> header file has
- been removed, since it contains nothing of use to
- userspace.
- </para>
- </listitem>
- <listitem>
- <para>
- The <code>_syscallX()</code> macros are removed. Userspace
- should use <code>syscall()</code> from the C library
- instead.
- </para>
- </listitem>
- <listitem>
- <para>
- The <code>PAGE_SIZE</code> macro is removed from some
- architectures, since the page size is variable. Userspace
- should be using <code>sysconf(_SC_PAGE_SIZE)</code> or
- <code>getpagesize()</code> instead.
- </para>
- </listitem>
- <listitem>
- <para>
- The <code><asm/atomic.h></code> and
- <code><asm/bitops.h></code> header files have been
- removed. These were not designed for use in userspace, and
- would fail to compile on some architectures while silently
- giving non-atomic behaviour on others. The C compiler
- provides its own
- <ulink url='http://gcc.gnu.org/onlinedocs/gcc-4.1.1/gcc/Atomic-Builtins.html#Atomic-B...'>atomic
- builtin functions</ulink> which are suitable for use in
- userspace programs instead.
- </para>
- </listitem>
- <listitem>
- <para>
- Content which was previously protected with <code>#ifdef
- __KERNEL__</code> is now elided completely with the
- <code>unifdef</code> tool. Defining
- <code>__KERNEL___</code> in order to see parts which
- should not be visible to userspace is no longer effective.
- </para>
- </listitem>
- </itemizedlist>
- <para>
- In addition, some other header files which are not suitable
- for use in userspace have been removed, and still more headers
- have been edited to remove unsuitable content.
- </para>
- <para>
- <note>
- <title>Kernel header changes are not Fedora-specific</title>
- <para>
- These changes are inherited from the upstream kernel and
- are not specific to Fedora. Any distribution using the
- current officially-exported kernel headers would be the
- same.
- </para>
- </note>
- </para>
+ <title>Caveats</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Fedora developers have introduced changes in the ELF
+ <code>.hash</code> section that provides symbols for dynamic
+ linking. This new <code>.gnu.hash</code> section, which is
+ produced with the new default
+ <code>--hash-style=gnu</code> option for
+ <code>gcc</code>, serves the same purpose as
+ previous hash sections. It provides, however, an
+ approximately 50% increase in dynamic linking speed.
+ Binaries and libraries produced with the new hashing
+ function are incompatible with older
+ <code>glibc</code> and dynamic linker releases. To
+ use the old-style hashing routines for compatibility
+ with older <code>glibc</code>-based systems, pass
+ the <code>--hash-style=sysv</code> option instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ You need GDB 6.1 or newer to debug binaries, unless
+ they are compiled using the
+ <code>-fno-var-tracking</code> compilation option.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <code>-fwritable-strings</code> option is no
+ longer accepted.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ English-language diagnostic messages now use Unicode
+ quotes. If you cannot read this, set your
+ <code>LC_CTYPE</code> environment variable to
+ <code>C</code> or change your terminal emulator.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <code>specs</code> file is no longer installed
+ on most systems. Ordinary users will not notice, but
+ developers who need to alter the file can use the
+ <code>-dumpspecs</code> option to generate the file
+ for editing.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section>
+ <title>Code Generation</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The SSA code optimizer is now included and brings
+ with it better constant propagation, partial
+ redundancy elimination, load and store code motion,
+ strength reduction, dead storage elimination, better
+ detection of unreachable code, and tail recursion by
+ accumulation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Autovectorization is supported. This technique
+ achieves higher performance for repetitive loop
+ code, in some circumstances.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section>
+ <title>Language Extensions</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The new sentinel attribute causes the compiler to
+ issue a warning if a function such as
+ <code>execl(char *path, const char *arg,
+ ...)</code>, which requires a NULL list terminator,
+ is missing the NULL.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <code>cast-as-lvalue</code>,
+ <code>conditional-expression-as-lvalue</code>, and
+ <code>compund-expression-as-lvalue</code> extensions
+ have been removed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <code>#pragma pack()</code> semantics are now
+ closer to those used by other compilers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Taking the address of a variable declared with the register
+ modifier now generates an error instead of a warning.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Arrays of incomplete element types now generate an
+ error. This implies no forward reference to
+ structure definitions.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The basic compiler, without any optimization
+ (<code>-O0</code>), has been measured as much as 25%
+ faster in real-world code.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Libraries may now contain function-scope static
+ variables in multi-threaded programs. Embedded
+ developers can use the
+ <code>-fno-threadsafe-statics</code> to turn off
+ this feature, but ordinary users should never do
+ this.
+ </para>
+ </listitem>
+ </itemizedlist>
</section>
- <section>
- <title>GCC Compiler Collection</title>
- <para>
- This release of Fedora has been built with GCC 4.1, which
- is included with the distribution.
- </para>
- <section>
- <title>Caveats</title>
- <itemizedlist>
- <listitem>
- <para>
- Fedora developers have introduced changes in the ELF
- .hash section that provides symbols for dynamic
- linking. This new .gnu.hash section, which is
- produced with the new default
- <code>--hash-style=gnu</code> option for
- <code>gcc</code>, serves the same purpose as
- previous hash sections. It provides, however, an
- approximately 50% increase in dynamic linking speed.
- Binaries and libraries produced with the new hashing
- function are incompatible with older
- <code>glibc</code> and dynamic linker releases. To
- use the old-style hashing routines for compatibility
- with older <code>glibc</code>-based systems, pass
- the <code>--hash-style=sysv</code> option instead.
- </para>
- </listitem>
- <listitem>
- <para>
- You need GDB 6.1 or newer to debug binaries, unless
- they are compiled using the
- <code>-fno-var-tracking</code> compilation option.
- </para>
- </listitem>
- <listitem>
- <para>
- The <code>-fwritable-strings</code> option is no
- longer accepted.
- </para>
- </listitem>
- <listitem>
- <para>
- English-language diagnostic messages now use Unicode
- quotes. If you cannot read this, set your
- <code>LC_CTYPE</code> environment variable to
- <code>C</code> or change your terminal emulator.
- </para>
- </listitem>
- <listitem>
- <para>
- The <code>specs</code> file is no longer installed
- on most systems. Ordinary users will not notice, but
- developers who need to alter the file can use the
- <code>-dumpspecs</code> option to generate the file
- for editing.
- </para>
- </listitem>
- </itemizedlist>
- </section>
- <section>
- <title>Code Generation</title>
- <itemizedlist>
- <listitem>
- <para>
- The SSA code optimizer is now included and brings
- with it better constant propagation, partial
- redundancy elimination, load and store code motion,
- strength reduction, dead storage elimination, better
- detection of unreachable code, and tail recursion by
- accumulation.
- </para>
- </listitem>
- <listitem>
- <para>
- Autovectorization is supported. This technique
- achieves higher performance for repetitive loop
- code, in some circumstances.
- </para>
- </listitem>
- </itemizedlist>
- </section>
- <section>
- <title>Language Extensions</title>
- <itemizedlist>
- <listitem>
- <para>
- The new sentinel attribute causes the compiler to
- issue a warning if a function such as
- <code>execl(char *path, const char *arg,
- ...)</code>, which requires a NULL list terminator,
- is missing the NULL.
- </para>
- </listitem>
- <listitem>
- <para>
- The <code>cast-as-lvalue</code>,
- <code>conditional-expression-as-lvalue</code>, and
- <code>compund-expression-as-lvalue</code> extensions
- have been removed.
- </para>
- </listitem>
- <listitem>
- <para>
- The <code>#pragma pack()</code> semantics are now
- closer to those used by other compilers.
- </para>
- </listitem>
- <listitem>
- <para>
- Taking the address of a variable declared with the
- register modifier now generates an error instead of
- a warning.
- </para>
- </listitem>
- <listitem>
- <para>
- Arrays of incomplete element types now generate an
- error. This implies no forward reference to
- structure definitions.
- </para>
- </listitem>
- <listitem>
- <para>
- The basic compiler, without any optimization
- (<code>-O0</code>), has been measured as much as 25%
- faster in real-world code.
- </para>
- </listitem>
- <listitem>
- <para>
- Libraries may now contain function-scope static
- variables in multi-threaded programs. Embedded
- developers can use the
- <code>-fno-threadsafe-statics</code> to turn off
- this feature, but ordinary users should never do
- this.
- </para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
</section>
+ </section>
<section>
<title>Ruby</title>
@@ -336,7 +335,7 @@
the release of Fedora Core 8. Build Ruby RPM packages in
accordance with
<ulink url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/Packaging/Ruby'>the
- packaging guidelines</ulink>. In particular, Ruby libraries should
+ packaging guidelines</ulink>. In particular, Ruby libraries should
only be installed into <code>sitelibdir</code> and
<code>sitearchdir</code>. You should also follow this rule for
Ruby code that is not packaged as an RPM.
17 years, 8 months
release-notes/devel/en_US Desktop.xml,1.6,1.7
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9325
Modified Files:
Desktop.xml
Log Message:
good for FC6
Index: Desktop.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Desktop.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- Desktop.xml 24 Sep 2006 20:41:49 -0000 1.6
+++ Desktop.xml 25 Sep 2006 06:51:21 -0000 1.7
@@ -34,7 +34,7 @@
<orderedlist numeration='arabic'>
<listitem>
<para>
- <emphasis>System -> Preferences -> More -> Desktop
+ <emphasis>System => Preferences => More => Desktop
Effects</emphasis>
</para>
</listitem>
@@ -50,7 +50,7 @@
</listitem>
</orderedlist>
<para>
- If you get stuck, please refer to the following thread:
+ If you get stuck, refer to the following thread:
</para>
<itemizedlist>
<listitem>
@@ -123,27 +123,29 @@
<section>
<title>Web Browsers</title>
<para>
- There is no longer a "browser suite" package contained in Fedora
- Core 6. The <code>mozilla</code> package has been removed. For
- equivalent functionality, use <code>firefox</code> as a web
+ There is no longer a <firstterm>browser suite</firstterm> package
+ contained in Fedora Core 6. The <code>mozilla</code> package has been
+ removed. For equivalent functionality, use <code>firefox</code> as a web
browser and <code>thunderbird</code> as a mail client, or use
- <code>seamonkey</code>, a browser suite distributed in Fedora
- Extras.
+ <code>seamonkey</code>, a browser suite distributed in Fedora Extras.
</para>
<para>
- To better support certain scripts (such as Indic and some CJK
- scripts), Fedora builds its
- <emphasis role='strong'>Firefox</emphasis>, with permission from
- the Mozilla Corporation, with the Pango system as its text
- renderer. This change may negatively impact performance on some
- pages. To disable the use of Pango, set
- <code>MOZ_DISABLE_PANGO=1</code> in your environment before
- launching <emphasis role='strong'>Firefox</emphasis>.
- </para>
+ To better support certain scripts (such as Indic and some CJK scripts),
+ Fedora builds its <emphasis role='strong'>Firefox</emphasis> using the
+ Pango system as its text renderer. Pango is used with the permission of
+ the Mozilla Corporation. This change may negatively impact performance on
+ some pages. To disable the use of Pango, set
+ <code>MOZ_DISABLE_PANGO=1</code> in your environment before launching
+ <emphasis role='strong'>Firefox</emphasis>.
+ </para>
+<screen>
+export MOZ_DISABLE_PANGO=1
+/usr/bin/firefox
+</screen>
<para>
Gecko based browsers <emphasis role='strong'>Firefox</emphasis>
and <emphasis role='strong'>Epiphany</emphasis> now properly
- render MathML when using the pango text backend. Additionally,
+ render MathML when using the Pango text backend. Additionally,
several issues with the rendering and behavior of text when using
the Pango text backend have been resolved.
<emphasis role='strong'>Epiphany</emphasis> now renders using
@@ -161,5 +163,9 @@
<code>MOZ_DISABLE_PANGO=1</code> in your environment before
launching <emphasis role='strong'>Thunderbird</emphasis>.
</para>
+<screen>
+export MOZ_DISABLE_PANGO=1
+/usr/bin/thunderbird
+</screen>
</section>
</section>
17 years, 8 months
release-notes/devel/en_US DatabaseServers.xml,1.8,1.9
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25695
Modified Files:
DatabaseServers.xml
Log Message:
good foir FC6
Index: DatabaseServers.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/DatabaseServers.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- DatabaseServers.xml 24 Sep 2006 20:41:49 -0000 1.8
+++ DatabaseServers.xml 25 Sep 2006 05:24:56 -0000 1.9
@@ -30,13 +30,15 @@
information on this new version, refer to
<ulink url='http://www.postgresql.org/docs/whatsnew'/>.
</para>
- <para>
- [[Admonition("important", "Upgrading Databases", "Fedora Core 4
- provided version 8.0 of PostgreSQL. If you upgrade an existing
- Fedora system with a PostgreSQL database, you must upgrade the
- database to access the data. To upgrade a database from a previous
- version of PostgreSQL, follow the procedure described at
- <ulink url='http://www.postgresql.org/docs/8.1/interactive/install-upgrading.html'/>"]]
- </para>
+ <important>
+ <title>Upgrading Databases</title>
+ <para>
+ Fedora Core 4 provided version 8.0 of PostgreSQL. If you upgrade an
+ existing Fedora system with a PostgreSQL database, you must upgrade the
+ database to access the data. To upgrade a database from a previous
+ version of PostgreSQL, follow the procedure described at <ulink
+ url='http://www.postgresql.org/docs/8.1/interactive/install-upgrading.html'/>
+ </para>
+ </important>
</section>
</section>
17 years, 8 months
release-notes/devel/en_US Colophon.xml,1.9,1.10
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27466
Modified Files:
Colophon.xml
Log Message:
ready for FC6; missing some translators for test releases and some that come this week; will update all that for Web-updated version
Index: Colophon.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Colophon.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- Colophon.xml 24 Sep 2006 20:41:49 -0000 1.9
+++ Colophon.xml 25 Sep 2006 00:19:33 -0000 1.10
@@ -47,12 +47,24 @@
</listitem>
<listitem>
<para>
+ <ulink url='http://fedoraproject.org/wiki/ChrisLennert'>Chris
+ Lennert</ulink> (beat writer)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url='http://fedoraproject.org/wiki/DaveMalcolm'>Dave
Malcolm</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
+ <ulink url='http://fedoraproject.org/wiki/DavidEisenstein'>David
+ Eisenstein</ulink> (beat writer)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url='http://fedoraproject.org/wiki/DavidWoodhouse'>David
Woodhouse</ulink> (beat writer)
</para>
@@ -131,20 +143,20 @@
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/SekineTatsuo'>Sekine
- Tatsuo</ulink> (translator, Japanese)
+ <ulink url='http://fedoraproject.org/wiki/SamFolkWilliams'>Sam
+ Folk-Williams</ulink> (beat writer, editor)
</para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/SteveDickson'>Steve
- Dickson</ulink> (beat writer)
+ <ulink url='http://fedoraproject.org/wiki/SekineTatsuo'>Sekine
+ Tatsuo</ulink> (translator, Japanese)
</para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/StuartEllis'>Stuart
- Ellis</ulink> (editor)
+ <ulink url='http://fedoraproject.org/wiki/SteveDickson'>Steve
+ Dickson</ulink> (beat writer)
</para>
</listitem>
<listitem>
@@ -178,6 +190,13 @@
</para>
</listitem>
</itemizedlist>
+ <para>
+ ... and many more translators. Refer to the Web-updated version of these
+ release notes as we add translators after release:
+ </para>
+ <para>
+ <ulink url="http://fedora.redhat.com/docs/release-notes/"/>
+ </para>
</section>
<section>
17 years, 8 months
release-notes/devel/en_US BackwardsCompatibility.xml,1.7,1.8
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12217
Modified Files:
BackwardsCompatibility.xml
Log Message:
ready to go for FC6
Index: BackwardsCompatibility.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/BackwardsCompatibility.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- BackwardsCompatibility.xml 24 Sep 2006 20:41:49 -0000 1.7
+++ BackwardsCompatibility.xml 24 Sep 2006 23:13:36 -0000 1.8
@@ -15,7 +15,7 @@
functionality may select this group either during installation, or
after the installation process is complete. To install the package
group on a Fedora system, use <emphasis>Applications=>Add/Remove
- Software</emphasis>, <emphasis role='strong'>Pirut</emphasis> or
+ Software</emphasis>, <emphasis role='strong'>Pirut</emphasis>, or
enter the following command in a terminal window:
</para>
@@ -30,9 +30,10 @@
<title>Compiler Compatibility</title>
<para>
The <code>compat-gcc-34</code> package has been included in this
- release for
- <ulink url='https://www.redhat.com/archives/fedora-devel-list/2006-August/msg00409.html'>compatibility</ulink>
- reasons.
+ release for compatibility reasons:
+ </para>
+ <para>
+ <ulink url='https://www.redhat.com/archives/fedora-devel-list/2006-August/msg00409.html'/>
</para>
</section>
</section>
17 years, 8 months
release-notes/devel/en_US ArchSpecific.xml,1.9,1.10
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11248
Modified Files:
ArchSpecific.xml
Log Message:
Good to go for FC6
Index: ArchSpecific.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/ArchSpecific.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- ArchSpecific.xml 24 Sep 2006 21:13:18 -0000 1.9
+++ ArchSpecific.xml 24 Sep 2006 23:08:53 -0000 1.10
@@ -4,7 +4,7 @@
<section id="sn-ArchSpecific">
<title>Architecture Specific Notes</title>
-
+
<!--RAW HTML: <h2>Architecture Specific Notes</h2>-->
<para>
@@ -15,14 +15,13 @@
<section>
<title>RPM Multiarch Support on 64-bit platforms (x86_64, ppc64)</title>
<para>
- <emphasis role='strong'>RPM</emphasis> supports parallel
- installation of multiple architectures of the same package. A
- default package listing such as <code>rpm -qa</code> might appear
- to include duplicate packages, since the architecture is not
- displayed. Instead, use the <code>repoquery</code> command, part
- of the <code>yum-utils</code> package in Fedora Extras, which
- displays architecture by default. To install
- <code>yum-utils</code>, run the following command:
+ <emphasis role='strong'>RPM</emphasis> supports parallel installation of
+ multiple architectures of the same package. A default package listing such
+ as <code>rpm -qa</code> might appear to include duplicate packages, since
+ the architecture is not displayed. Instead, use the <code>repoquery</code>
+ command, part of the <code>yum-utils</code> package in Fedora Extras,
+ which displays architecture by default. To install <code>yum-utils</code>,
+ run the following command:
</para>
<screen><![CDATA[su -c 'yum install yum-utils'
]]></screen>
@@ -40,343 +39,333 @@
<screen><![CDATA[%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
]]></screen>
</section>
+ <section>
+ <title>PPC Specifics for Fedora</title>
+ <para>
+ This section covers any specific information you may need to know about
+ Fedora Core and the PPC hardware platform.
+ </para>
+ <section>
+ <title>PPC Hardware Requirements</title>
+ <section>
+ <title>Processor and Memory</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Minimum CPU: PowerPC G3 / POWER3
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fedora Core 6 supports only the ���New World��� generation of Apple
+ Power Macintosh, shipped from circa 1999 onward.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fedora Core 6 also supports IBM pSeries, IBM iSeries,
+ IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband
+ Engine machines.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Recommended for text-mode: 233 MHz G3 or better,
+ 128MiB RAM.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Recommended for graphical: 400 MHz G3 or better,
+ 256MiB RAM.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
<section>
- <title>PPC Specifics for Fedora</title>
- <para>
- This section covers any specific information you may need to
- know about Fedora Core and the PPC hardware platform.
- </para>
- <section>
- <title>PPC Hardware Requirements</title>
- <section>
- <title>Processor and Memory</title>
- <itemizedlist>
- <listitem>
- <para>
- Minimum CPU: PowerPC G3 / POWER3
- </para>
- </listitem>
- <listitem>
- <para>
- Fedora Core 6 supports only the ���New World���
- generation of Apple Power Macintosh, shipped from
- circa 1999 onward.
- </para>
- </listitem>
- <listitem>
- <para>
- Fedora Core 6 also supports IBM pSeries, IBM iSeries,
- IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband
- Engine machines.
- </para>
- </listitem>
- <listitem>
- <para>
- Recommended for text-mode: 233 MHz G3 or better,
- 128MiB RAM.
- </para>
- </listitem>
- <listitem>
- <para>
- Recommended for graphical: 400 MHz G3 or better,
- 256MiB RAM.
- </para>
- </listitem>
- </itemizedlist>
- </section>
- <section>
- <title>Hard Disk Space Requirements</title>
- <para>
- The disk space requirements listed below represent the
- disk space taken up by Fedora Core 6 after installation is
- complete. However, additional disk space is required
- during installation to support the installation
- environment. This additional disk space corresponds to the
- size of <code>/Fedora/base/stage2.img</code> (on
- Installtion Disc 1) plus the size of the files in
- <code>/var/lib/rpm</code> on the installed system.
- </para>
- <para>
- In practical terms, additional space requirements may
- range from as little as 90 MiB for a minimal installation
- to as much as an additional 175 MiB for an "everything"
- installation. The complete packages can occupy over 9 GB
- of disk space.
- </para>
- <para>
- Additional space is also required for any user data, and
- at least 5% free space should be maintained for proper
- system operation.
- </para>
- </section>
- </section>
- <section>
- <title>The Apple keyboard</title>
- <para>
- The <code>Option</code> key on Apple systems is equivalent
- to the <code>Alt</code> key on the PC. Where documentation
- and the installer refer to the <code>Alt</code> key, use the
- <code>Option</code> key. For some key combinations you may
- need to use the <code>Option</code> key in conjunction with
- the <code>Fn</code> key, such as
- <code>Option</code>-<code>Fn</code>-<code>F3</code> to
- switch to virtual terminal tty3.
- </para>
- </section>
- <section>
- <title>PPC Installation Notes</title>
- <para>
- Fedora Core Installation Disc 1 is bootable on supported
- hardware. In addition, a bootable CD image appears in the
- <code>images/</code> directory of this disc. These images
- behave differently according to your system hardware:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Apple Macintosh The bootloader automatically boots the
- appropriate 32-bit or 64-bit installer.
- </para>
- <para>
- The default <code>gnome-power-manager</code> package
- includes power management support, including sleep and
- backlight level management. Users with more complex
- requirements can use the <code>apmud</code> package in
- Fedora Extras. To install <code>apmud</code> after
- installation, use the following command:
- </para>
- </listitem>
- </itemizedlist>
+ <title>Hard Disk Space Requirements</title>
+ <para>
+ The disk space requirements listed below represent the disk space
+ taken up by Fedora Core 6 after installation is complete. However,
+ additional disk space is required during installation to support the
+ installation environment. This additional disk space corresponds to
+ the size of <code>/Fedora/base/stage2.img</code> (on Installation Disc
+ 1) plus the size of the files in <code>/var/lib/rpm</code> on the
+ installed system.
+ </para>
+ <para>
+ In practical terms, additional space requirements may range from as
+ little as 90 MiB for a minimal installation to as much as an
+ additional 175 MiB for an installation that includes nearly all the
+ packages. The complete installed packages can occupy over 9 GB of disk
+ space.
+ </para>
+ <para>
+ Additional space is also required for any user data, and
+ at least 5% free space should be maintained for proper
+ system operation.
+ </para>
+ </section>
+ </section>
+ <section>
+ <title>The Apple keyboard</title>
+ <para>
+ The <code>Option</code> key on Apple systems is equivalent
+ to the <code>Alt</code> key on the PC. Where documentation
+ and the installer refer to the <code>Alt</code> key, use the
+ <code>Option</code> key. For some key combinations you may
+ need to use the <code>Option</code> key in conjunction with
+ the <code>Fn</code> key, such as
+ <code>Option</code>-<code>Fn</code>-<code>F3</code> to
+ switch to virtual terminal tty3.
+ </para>
+ </section>
+ <section>
+ <title>PPC Installation Notes</title>
+ <para>
+ Fedora Core Installation Disc 1 is bootable on supported
+ hardware. In addition, a bootable CD image appears in the
+ <code>images/</code> directory of this disc. These images
+ behave differently according to your system hardware:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Apple Macintosh The bootloader automatically boots the
+ appropriate 32-bit or 64-bit installer.
+ </para>
+ <para>
+ The default <code>gnome-power-manager</code> package includes power
+ management support, including sleep and backlight level management.
+ Users with more complex requirements can use the <code>apmud</code>
+ package in Fedora Extras. To install <code>apmud</code> after
+ installation, use the following command:
+ </para>
+ </listitem>
+ </itemizedlist>
<screen>su -c 'yum install apmud'
</screen>
- <itemizedlist>
- <listitem>
- <para>
- 64-bit IBM pSeries (POWER4/POWER5), current iSeries
- models
- </para>
- <para>
- After using Open<emphasis role='strong'/>Firmware to
- boot the CD, the bootloader, <code>yaboot</code>,
- automatically boots the 64-bit installer.
- </para>
- </listitem>
- <listitem>
- <para>
- IBM "Legacy" iSeries (POWER4)
- </para>
- <para>
- So-called "Legacy" iSeries models, which do not use
- Open<emphasis role='strong'/>Firmware, require use of
- the boot image located in the 'images/iSeries' directory
- of the installation tree.
- </para>
- </listitem>
- <listitem>
- <para>
- 32-bit CHRP (IBM RS/6000 and others)
- </para>
- <para>
- After using Open<emphasis role='strong'/>Firmware to
- boot the CD, select the <code>linux32</code> boot image
- at the <code>boot:</code> prompt to start the 32-bit
- installer. Otherwise, the 64-bit installer starts and
- fails.
- </para>
- </listitem>
- <listitem>
- <para>
- Genesi Pegasos II
- </para>
- <para>
- At the time of writing, firmware with full support for
- ISO9660 file systems has not yet been released for the
- Pegasos. You can use the network boot image, however. At
- the Open<emphasis role='strong'/>Firmware prompt, enter
- the following command:
- </para>
- </listitem>
- </itemizedlist>
+ <itemizedlist>
+ <listitem>
+ <para>
+ 64-bit IBM pSeries (POWER4/POWER5), current iSeries
+ models
+ </para>
+ <para>
+ After using Open<emphasis role='strong'/>Firmware to
+ boot the CD, the bootloader, <code>yaboot</code>,
+ automatically boots the 64-bit installer.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ IBM "Legacy" iSeries (POWER4)
+ </para>
+ <para>
+ So-called "Legacy" iSeries models, which do not use Open<emphasis
+ role='strong'/>Firmware, require use of the boot image located in
+ the <code>images/iSeries</code> directory of the installation tree.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 32-bit CHRP (IBM RS/6000 and others)
+ </para>
+ <para>
+ After using Open<emphasis role='strong'/>Firmware to boot the CD,
+ select the <code>linux32</code> boot image at the <code>boot:</code>
+ prompt to start the 32-bit installer. Otherwise, the 64-bit
+ installer starts and fails.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Genesi Pegasos II
+ </para>
+ <para>
+ At the time of writing, firmware with full support for ISO9660 file
+ systems has not yet been released for the Pegasos. You can use the
+ network boot image, however. At the Open<emphasis
+ role='strong'/>Firmware prompt, enter the following command:
+ </para>
+ </listitem>
+ </itemizedlist>
<screen>boot cd: /images/netboot/ppc32.img
</screen>
- <itemizedlist>
- <listitem override='none'>
- <para>
- You must also configure
- Open<emphasis role='strong'/>Firmware on the Pegasos
- manually to make the installed Fedora Core system
- bootable. To do this, set the <code>boot-device</code>
- and <code>boot-file</code> environment variables
- appropriately.
- </para>
- </listitem>
- <listitem>
- <para>
- Network booting
- </para>
- <para>
- Combined images containing the installer kernel and
- ramdisk are located in the <code>images/netboot/</code>
- directory of the installation tree. They are intended
- for network booting with TFTP, but can be used in many
- ways.
- </para>
- <para>
- The <code>yaboot</code> loader supports TFTP booting for
- IBM pSeries and Apple Macintosh. The Fedora Project
- encourages the use of <code>yaboot</code> over the
- <code>netboot</code> images.
- </para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
+ <itemizedlist>
+ <listitem override='none'>
+ <para>
+ You must also configure Open<emphasis role='strong'/>Firmware on the
+ Pegasos manually to make the installed Fedora Core system bootable.
+ To do this, set the <code>boot-device</code> and
+ <code>boot-file</code> environment variables appropriately.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Network booting
+ </para>
+ <para>
+ Combined images containing the installer kernel and ramdisk are
+ located in the <code>images/netboot/</code> directory of the
+ installation tree. They are intended for network booting with TFTP,
+ but can be used in many ways.
+ </para>
+ <para>
+ The <code>yaboot</code> loader supports TFTP booting for IBM pSeries
+ and Apple Macintosh. The Fedora Project encourages the use of
+ <code>yaboot</code> over the <code>netboot</code> images.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+ <section>
+ <title>x86 Specifics for Fedora</title>
+ <para>
+ This section covers any specific information you may need to
+ know about Fedora Core and the x86 hardware platform.
+ </para>
+ <section>
+ <title>x86 Hardware Requirements</title>
+ <para>
+ In order to use specific features of Fedora Core 6 during or
+ after installation, you may need to know details of other
+ hardware components such as video and network cards.
+ </para>
+ <section>
+ <title>Processor and Memory Requirements</title>
+ <para>
+ The following CPU specifications are stated in terms of
+ Intel processors. Other processors, such as those from
+ AMD, Cyrix, and VIA that are compatible with and
+ equivalent to the following Intel processors, may also be
+ used with Fedora Core.
+ </para>
+ <para>
+ Fedora Core 6 requires an Intel Pentium or better
+ processor, and is optimized for Pentium 4 and later
+ processors.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Recommended for text-mode: 200 MHz Pentium-class or
+ better
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Recommended for graphical: 400 MHz Pentium II or
+ better
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Minimum RAM for text-mode: 128MiB
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Minimum RAM for graphical: 192MiB
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Recommended RAM for graphical: 256MiB
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
<section>
- <title>x86 Specifics for Fedora</title>
- <para>
- This section covers any specific information you may need to
- know about Fedora Core and the x86 hardware platform.
- </para>
- <section>
- <title>x86 Hardware Requirements</title>
- <para>
- In order to use specific features of Fedora Core 6 during or
- after installation, you may need to know details of other
- hardware components such as video and network cards.
- </para>
- <section>
- <title>Processor and Memory Requirements</title>
- <para>
- The following CPU specifications are stated in terms of
- Intel processors. Other processors, such as those from
- AMD, Cyrix, and VIA that are compatible with and
- equivalent to the following Intel processors, may also be
- used with Fedora Core.
- </para>
- <para>
- Fedora Core 6 requires an Intel Pentium or better
- processor, and is optimized for Pentium 4 and later
- processors.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Recommended for text-mode: 200 MHz Pentium-class or
- better
- </para>
- </listitem>
- <listitem>
- <para>
- Recommended for graphical: 400 MHz Pentium II or
- better
- </para>
- </listitem>
- <listitem>
- <para>
- Minimum RAM for text-mode: 128MiB
- </para>
- </listitem>
- <listitem>
- <para>
- Minimum RAM for graphical: 192MiB
- </para>
- </listitem>
- <listitem>
- <para>
- Recommended RAM for graphical: 256MiB
- </para>
- </listitem>
- </itemizedlist>
- </section>
- <section>
- <title>Hard Disk Space Requirements</title>
- <para>
- The disk space requirements listed below represent the
- disk space taken up by Fedora Core 6 after the
- installation is complete. However, additional disk space
- is required during the installation to support the
- installation environment. This additional disk space
- corresponds to the size of
- <code>/Fedora/base/stage2.img</code> on Installation Disc
- 1 plus the size of the files in <code>/var/lib/rpm</code>
- on the installed system.
- </para>
- <para>
- In practical terms, additional space requirements may
- range from as little as 90 MiB for a minimal installation
- to as much as an additional 175 MiB for an "everything"
- installation. The complete packages can occupy over 9 GB
- of disk space.
- </para>
- <para>
- Additional space is also required for any user data, and
- at least 5% free space should be maintained for proper
- system operation.
- </para>
- </section>
- </section>
+ <title>Hard Disk Space Requirements</title>
+ <para>
+ The disk space requirements listed below represent the
+ disk space taken up by Fedora Core 6 after the
+ installation is complete. However, additional disk space
+ is required during the installation to support the
+ installation environment. This additional disk space
+ corresponds to the size of
+ <code>/Fedora/base/stage2.img</code> on Installation Disc
+ 1 plus the size of the files in <code>/var/lib/rpm</code>
+ on the installed system.
+ </para>
+ <para>
+ In practical terms, additional space requirements may range from as
+ little as 90 MiB for a minimal installation to as much as an
+ additional 175 MiB for an installation that includes nearly all the
+ packages. The complete installed packages can occupy over 9 GB of disk
+ space.
+ </para>
+ <para>
+ Additional space is also required for any user data, and
+ at least 5% free space should be maintained for proper
+ system operation.
+ </para>
</section>
+ </section>
+ </section>
+ <section>
+ <title>x86_64 Specifics for Fedora</title>
+ <para>
+ This section covers any specific information you may need to
+ know about Fedora Core and the x86_64 hardware platform.
+ </para>
+ <section>
+ <title>x86_64 Hardware Requirements</title>
+ <para>
+ In order to use specific features of Fedora Core 6 during or
+ after installation, you may need to know details of other
+ hardware components such as video and network cards.
+ </para>
<section>
- <title>x86_64 Specifics for Fedora</title>
- <para>
- This section covers any specific information you may need to
- know about Fedora Core and the x86_64 hardware platform.
- </para>
- <section>
- <title>x86_64 Hardware Requirements</title>
- <para>
- In order to use specific features of Fedora Core 6 during or
- after installation, you may need to know details of other
- hardware components such as video and network cards.
- </para>
- <section>
- <title>x86_64 Memory Requirements</title>
- <itemizedlist>
- <listitem>
- <para>
- Minimum RAM for text-mode: 128MiB
- </para>
- </listitem>
- <listitem>
- <para>
- Minimum RAM for graphical: 256MiB
- </para>
- </listitem>
- <listitem>
- <para>
- Recommended RAM for graphical: 512MiB
- </para>
- </listitem>
- </itemizedlist>
- </section>
- <section>
- <title>Hard Disk Space Requirements</title>
- <para>
- The disk space requirements listed below represent the
- disk space taken up by Fedora Core 6 after the
- installation is complete. However, additional disk space
- is required during the installation to support the
- installation environment. This additional disk space
- corresponds to the size of
- <code>/Fedora/base/stage2.img</code> on Installation Disc
- 1 plus the size of the files in <code>/var/lib/rpm</code>
- on the installed system.
- </para>
- <para>
- In practical terms, additional space requirements may
- range from as little as 90 MiB for a minimal installation
- to as much as an additional 175 MiB for an "everything"
- installation. The complete packages can occupy over 9 GB
- of disk space.
- </para>
- <para>
- Additional space is also required for any user data, and
- at least 5% free space should be maintained for proper
- system operation.
- </para>
- </section>
- </section>
+ <title>x86_64 Memory Requirements</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Minimum RAM for text-mode: 128MiB
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Minimum RAM for graphical: 256MiB
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Recommended RAM for graphical: 512MiB
+ </para>
+ </listitem>
+ </itemizedlist>
</section>
+ <section>
+ <title>Hard Disk Space Requirements</title>
+ <para>
+ The disk space requirements listed below represent the
+ disk space taken up by Fedora Core 6 after the
+ installation is complete. However, additional disk space
+ is required during the installation to support the
+ installation environment. This additional disk space
+ corresponds to the size of
+ <code>/Fedora/base/stage2.img</code> on Installation Disc
+ 1 plus the size of the files in <code>/var/lib/rpm</code>
+ on the installed system.
+ </para>
+ <para>
+ In practical terms, additional space requirements may range from as
+ little as 90 MiB for a minimal installation to as much as an
+ additional 175 MiB for an installation that includes nearly all the
+ packages. The complete installed packages can occupy over 9 GB of disk
+ space.
+ </para>
+ <para>
+ Additional space is also required for any user data, and
+ at least 5% free space should be maintained for proper
+ system operation.
+ </para>
+ </section>
+ </section>
+ </section>
</section>
17 years, 8 months
release-notes/devel/en_US Security.xml,1.8,1.9
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17592
Modified Files:
Security.xml
Log Message:
Promoted SELinux section for better flow
Index: Security.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Security.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- Security.xml 24 Sep 2006 20:41:49 -0000 1.8
+++ Security.xml 24 Sep 2006 21:18:22 -0000 1.9
@@ -18,6 +18,7 @@
Fedora, current status and policies is available at
<ulink url='http://fedoraproject.org/wiki/Security'/>.
</para>
+ </section>
<section>
<title>SELinux</title>
<para>
@@ -69,5 +70,4 @@
</listitem>
</itemizedlist>
</section>
- </section>
</section>
17 years, 8 months