4 commits - en-US/Backwards_compatibility.xml en-US/Embedded.xml en-US/Fedora_10_boot-time.xml en-US/Fedora_10_overview.xml en-US/Fedora_desktop.xml en-US/Fedora_live_images.xml en-US/Fedora_Live_images.xml en-US/Fedora_overview.xml en-US/Fedora_Project.xml en-US/Feedback.xml en-US/File_servers.xml en-US/File_systems.xml en-US/Games_and_entertainment.xml en-US/Hardware_overview.xml en-US/How_are_Things_for_Developers.xml en-US/Installation_notes.xml en-US/International_language_support.xml en-US/Introduction_to_Fedora_Project_and_technical_release_notes.xml en-US/Java.xml en-US/KDE_4_development_platform.xml en-US/Legal_Stuff_and_Administrivia.xml en-US/Welcome_to_Fedora.xml
Karsten Wade
quaid at fedoraproject.org
Fri Oct 17 11:20:43 UTC 2008
en-US/Backwards_compatibility.xml | 60 -
en-US/Embedded.xml | 383 +++++-
en-US/Fedora_10_boot-time.xml | 147 +-
en-US/Fedora_10_overview.xml | 91 +
en-US/Fedora_Live_images.xml | 163 ++
en-US/Fedora_Project.xml | 106 +
en-US/Fedora_desktop.xml | 586 ++++++----
en-US/Fedora_live_images.xml | 80 -
en-US/Fedora_overview.xml | 62 -
en-US/Feedback.xml | 76 -
en-US/File_servers.xml | 55
en-US/File_systems.xml | 49
en-US/Games_and_entertainment.xml | 49
en-US/Hardware_overview.xml | 106 +
en-US/How_are_Things_for_Developers.xml | 46
en-US/Installation_notes.xml | 529 +++++----
en-US/International_language_support.xml | 437 ++++---
en-US/Introduction_to_Fedora_Project_and_technical_release_notes.xml | 60 -
en-US/Java.xml | 195 ++-
en-US/KDE_4_development_platform.xml | 35
en-US/Legal_Stuff_and_Administrivia.xml | 4
en-US/Welcome_to_Fedora.xml | 5
22 files changed, 2138 insertions(+), 1186 deletions(-)
New commits:
commit f91cc63b0aafa1adb735cbc74929ac48d487e924
Author: Karsten 'quaid' Wade <kwade at calliope.phig.org>
Date: Fri Oct 17 04:19:19 2008 -0700
Lots of XML edits to make files ready to publish.
diff --git a/en-US/Backwards_compatibility.xml b/en-US/Backwards_compatibility.xml
index 4e8c27b..32f8f52 100644
--- a/en-US/Backwards_compatibility.xml
+++ b/en-US/Backwards_compatibility.xml
@@ -1,30 +1,34 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/BackwardsCompatibility</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/BackwardsCompatibility</title>
- <section id="sn-">
- <title>Backwards Compatibility </title>
- <para>Fedora provides legacy system libraries for compatibility with older software. This software is part of the <emphasis>Legacy Software Development</emphasis> group, which is not installed by default. Users who require this functionality may select this group either during installation or after the installation process is complete. To install the package group on a Fedora system, use <emphasis>Applications > Add/Remove Software</emphasis> or enter the following command in a terminal window:</para><para />
- <programlisting>
-su -c 'yum groupinstall "Legacy Software Development"'
-</programlisting>
- <para />
- <para>Enter the password for the <programlisting format="linespecific">root</programlisting> account when prompted.</para><section id="sn-">
- <title>Compiler compatibility </title>
- <para>The <programlisting format="linespecific">compat-gcc-34</programlisting> package has been included for compatibility reasons:</para><para>
- <ulink url="https://www.redhat.com/archives/fedora-devel-list/2006-August/msg00409.html">https://www.redhat.com/archives/fedora-devel-list/2006-August/msg00409.html</ulink>
- </para>
- </section><section id="sn-">
- <title>KDE3 development </title>
- <para>Refer to <ulink url="http://fedoraproject.org/w/index.php?title=Docs/Beats/BackwardsCompatibility/KDE3">Docs/Beats/BackwardsCompatibility/KDE3</ulink>.</para>
- </section>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
+
+<section lang="en" id="sn-Backwards_compatibility">
+ <title>Backwards compatibility</title>
+ <para>Fedora provides legacy system libraries for compatibility with
+ older software. This software is part of the <menuchoice>Legacy
+ Software Development</menuchoice> group, which is not installed by
+ default. Users who require this functionality may select this group
+ either during installation or after the installation process is
+ complete. To install the package group on a Fedora system, use
+ <guimenu>Applications</guimenu><guimenuitem>Add/Remove
+ Software</guimenuitem> or enter the following command in a
+ terminal window:</para>
+ <screen>
+ <userinput>su -c 'yum groupinstall "Legacy Software
+ Development"'</userinput>
+ </screen>
+ <para>Enter the password for the root account when prompted.</para>
+ <section id="sn-Compiler_compatibility">
+ <title>Compiler compatibility</title>
+ <para>The <package>compat-gcc-34</package> package has been included
+ for compatibility reasons:</para>
+ <para>
+ <ulink
+ url="https://www.redhat.com/archives/fedora-devel-list/2006-August/msg00409.html"/>
+ </para>
+ </section><section id="sn-KDE_3_development">
+ <title>KDE 3 development</title>
+ <para>Refer to <xref
+ linkend="sn-KDE_3_development_platform_and_libraries"/>.</para>
+ </section>
+</section>
diff --git a/en-US/Embedded.xml b/en-US/Embedded.xml
index 6f9d404..9a9325c 100644
--- a/en-US/Embedded.xml
+++ b/en-US/Embedded.xml
@@ -1,91 +1,296 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
+
+<section lang="en" id="sn-Embedded">
+ <title>Embedded</title>
+ <para>Fedora 10 includes a number of applications to support embedded
+ development on a variety of targets. Included are assemblers,
+ compilers, debuggers, programmers, IDEs and assorted
+ utilities.</para>
+ <section id="sn-AVR">
+ <title>AVR</title>
+ <variablelist>
+ <varlistentry>
+ <term>
+ <package>avrdude</package>Software for programming Atmel AVR
+ microcontroller</term>
+ <listitem>
+ <para>AVRDUDE is a program for programming Atmel's AVR CPU's.
+ It can program the Flash and EEPROM, and where supported by
+ the serial programming protocol, it can program fuse and
+ lock bits. AVRDUDE also supplies a direct instruction mode
+ allowing one to issue any programming instruction to the AVR
+ chip regardless of whether AVRDUDE implements that specific
+ feature of a particular chip.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>avr-gcc</package>Cross Compiling GNU GCC targeted at
+ avr</term>
+ <listitem>
+ <para>This is a Cross Compiling version of GNU GCC, which can
+ be used to compile for the AVR platform, instead of for the
+ native i386 platform.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>avr-gcc-c++</package>Cross Compiling GNU GCC targeted
+ at avr</term>
+ <listitem>
+ <para>This package contains the Cross Compiling version of
+ g++, which can be used to compile c++ code for the AVR
+ platform, instead of for the native i386 platform.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>avr-libc</package>C library for use with GCC on Atmel
+ AVR microcontrollers</term>
+ <listitem>
+ <para>AVR Libc is a free software project with the goal to
+ provide a high quality C library for use with GCC on Atmel
+ AVR microcontrollers.</para>
+ <para>AVR Libc is licensed under a single unified license.
+ This so-called modified Berkeley license is intended to be
+ compatible with most free software licenses such as the GPL,
+ yet impose as little restrictions as possible for the use of
+ the library in closed-source commercial applications.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>avr-binutils</package>Cross Compiling GNU binutils
+ targeted at avr</term>
+ <listitem>
+ <para>This is a Cross Compiling version of GNU binutils, which
+ can be used to assemble and link binaries for the AVR
+ platform, instead of for the native i386 platform.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>avr-gdb</package>GDB for (remote) debugging avr
+ binaries</term>
+ <listitem>
+ <para>This is a special version of GDB, the GNU Project
+ debugger, for (remote) debugging AVR binaries. GDB allows
+ you to see what is going on inside another program while it
+ executes or what another program was doing at the moment it
+ crashed.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>avarice</package>Program for interfacing the Atmel
+ JTAG ICE to GDB</term>
+ <listitem>
+ <para>Program for interfacing the Atmel JTAG ICE to GDB to
+ allow users to debug their embedded AVR target</para>
+ </listitem>
+ </variablelist>
+ </section><section id="sn-">
+ <title>Microchip PIC</title>
+ <variablelist>
+ <varlistentry>
+ <term>
+ <package>gputils</package>Development utilities for Microchip
+ (TM) PIC (TM) microcontrollers</term>
+ <listitem>
+ <para>This is a collection of development tools for Microchip
+ (TM) PIC (TM) microcontrollers. This is ALPHA software:
+ there may be serious bugs in it, and it's nowhere near
+ complete. The <package>gputils</package> package currently
+ only implements a subset of the features available with
+ Microchip's tools. Refer to the documentation for an
+ up-to-date list of what <package>gputils</package> can
+ do.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><package>gpsim</package> A simulator for Microchip (TM)
+ PIC (TM) microcontrollers</term>
+ <listitem>
+ <para>The <package>gpsim</package> software is a simulator for
+ Microchip (TM) PIC (TM) microcontrollers. It supports most
+ devices in Microchip's 12-bit, 14bit, and 16-bit core
+ families. In addition, gpsim supports dynamically loadable
+ modules such as LED's, LCD's, resistors, and so forth, to
+ extend the simulation environment beyond the PIC.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><package>ktechlab</package> Development and simulation of
+ microcontrollers and electronic circuits</term>
+ <listitem>
+ <para><application>KTechlab</application> is a development and
+ simulation environment for microcontrollers and electronic
+ circuits, distributed under the GNU General Public License.
+ <application>KTechlab</application> consists of several
+ well-integrated components:</para>
+ <itemizedlist>
+ <listitem>
+ <para>A circuit simulator, capable of simulating logic,
+ linear devices and some nonlinear devices. </para>
+ </listitem><listitem>
+ <para>Integration with <command>gpsim</command>, allowing
+ PICs to be simulated in circuit. </para>
+ </listitem><listitem>
+ <para>A schematic editor, which provides a rich real-time
+ feedback of the simulation.</para>
+ </listitem><listitem>
+ <para>A flowchart editor, allowing PIC programs to be
+ constructed visually. </para>
+ </listitem><listitem>
+ <para>MicroBASIC; a BASIC-like compiler for PICs, written
+ as a companion program to
+ <application>KTechlab</application>. </para>
+ </listitem><listitem>
+ <para>An embedded <application>Kate</application> part,
+ which provides a powerful editor for PIC programs.
+ </para>
+ </listitem><listitem>
+ <para>Integrated assembler and disassembler via
+ <command>gpasm</command> and
+ <command>gpdasm</command>.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><package>pikdev</package> IDE for development of PICmicro
+ based application (under Linux/KDE)</term>
+ <listitem>
+ <para><application>PiKdev</application> is a simple IDE
+ dedicated to the development of PIC based applications under
+ KDE. Features:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Integrated editor</para>
+ </listitem><listitem>
+ <para>Project management</para>
+ </listitem><listitem>
+ <para>Integrated programming engine for 12, 14 and 16 bits
+ PIC (flash or EPROM technology)</para>
+ </listitem><listitem>
+ <para>Support for parallel and serial port programmers
+ </para>
+ </listitem><listitem>
+ <para>KDE compliant look-and-feel</para>
+ </listitem>
+ </itemizedlist>
+ <para>The system administrator must read
+ <filename>README.Fedora</filename> file located in the
+ <filename>/usr/share/doc/pikdev-0.9.2</filename> directory
+ to complete the full feature installation.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>piklab</package> Development environment for
+ applications based on PIC & dsPIC</term>
+ <listitem>
+ <para><application>Piklab</application> is a graphic
+ development environment for PIC and dsPIC microcontrollers.
+ It interfaces with various toochains for compiling and
+ assembling and it supports several Microchip and direct
+ programmers. The system administrator must refer to the
+ <filename>README.Fedora</filename> file located in the
+ <filename>/usr/share/doc/piklab-0.15.0</filename> directory
+ to complete full feature installation.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>pikloops</package> Code generator for PIC
+ delays</term>
+ <listitem>
+ <para><application>PiKLoop</application> generates code to
+ create delays for Microchip PIC microcontrollers. It is a
+ useful companion for <application>Pikdev</application> or
+ <application>Piklab</application> IDE.</para>
+ </listitem>
+ </variablelist>
+ </section>
+ <section id="sn-Others_and_processor_agnostic">
+ <title>Others and processor agnostic</title>
+ <variablelist>
+ <varlistentry>
+ <term>
+ <package>dfu-programmer</package> A device firmware update
+ based USB programmer for Atmel chips</term>
+ <listitem>
+ <para>A linux based command-line programmer for Atmel chips
+ with a USB bootloader supporting ISP. This is a mostly
+ Device Firmware Update (DFU) 1.0 compliant user-space
+ application. Currently supported chips: 8051, AVR,
+ at89c51snd1c, at90usb1287, at89c5130, at90usb1286,
+ at89c5131, at90usb647, at89c5132, at90usb646, at90usb162,
+ and at90usb82.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>sdcc</package> Small Device C Compiler</term>
+ <listitem>
+ <para>The <package>sdcc-2.6.0-12</package> package for SDCC is
+ a C compiler for 8051 class and similar microcontrollers.
+ The package includes the compiler, assemblers and linkers, a
+ device simulator, and a core library. The processors
+ supported (to a varying degree) include the 8051, ds390,
+ z80, hc08, and PIC.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>uisp</package> Universal In-System Programmer for
+ Atmel AVR and 8051</term>
+ <listitem>
+ <para>The <command>uisp</command> utility is for
+ downloading/uploading programs to AVR devices. It can also
+ be used for some Atmel 8051 type devices. In addition,
+ <command>uisp</command> can erase the device, write lock
+ bits, verify and set the active segment. For use with the
+ following hardware to program the devices: pavr, stk500,
+ Atmel STK500, dapa, Direct AVR Parallel Access, stk200,
+ Parallel Starter Kit, STK200, STK300, abb, Altera,
+ ByteBlasterMV Parallel Port Download Cable, avrisp, Atmel
+ AVR, bsd, fbprg (parallel), dt006 (parallel), dasa serial
+ (RESET=RTS SCK=DTR MOSI=TXD MISO=CTS), dasa2 serial
+ (RESET=!TXD SCK=RTS MOSI=DTR MISO=CTS)</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>simcoupe</package> SAM Coupe emulator (spectrum
+ compatible)</term>
+ <listitem>
+ <para><application>SimCoupe</application> emulates an 8bit Z80
+ based home computer, released in 1989 by Miles Gordon
+ Technology. The SAM Coupe was largely spectrum compatible,
+ with much improved hardware</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>sjasm</package> A z80 cross assembler</term>
+ <listitem>
+ <para>SjASM is a two pass macro Z80 cross assembler</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <package>z88dk</package> A Z80 cross compiler</term>
+ <listitem>
+ <para>The <command>z88dk</command> program is a Z80 cross
+ compiler capable of generating binary files for a variety of
+ Z80 based machines (such as the ZX81, Spectrum, Jupiter Ace,
+ and some TI calculators).</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+</section>
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/Embedded</title>
- </articleinfo><section id="sn-">
- <title>Embedded</title>
- <para>Fedora 10 includes a number of applications to support embedded development on a variety of targets. Included are assemblers, compilers, debuggers, programmers, IDEs and assorted utilities.</para>
- <section id="sn-">
- <title>AVR</title>
- <para>
- <emphasis>avrdude</emphasis> Software for programming Atmel AVR microcontroller</para><para>AVRDUDE is a program for programming Atmel's AVR CPU's. It can program the Flash and EEPROM, and where supported by the serial programming protocol, it can program fuse and lock bits. AVRDUDE also supplies a direct instruction mode allowing one to issue any programming instruction to the AVR chip regardless of whether AVRDUDE implements that specific feature of a particular chip.</para>
- <para>
- <emphasis>avr-gcc</emphasis> Cross Compiling GNU GCC targeted at avr</para><para>This is a Cross Compiling version of GNU GCC, which can be used to compile for the avr platform, instead of for the native i386 platform.</para>
- <para>
- <emphasis>avr-gcc-c++</emphasis> Cross Compiling GNU GCC targeted at avr</para><para>This package contains the Cross Compiling version of g++, which can be used to compile c++ code for the avr platform, instead of for the native i386 platform.</para>
- <para>
- <emphasis>avr-libc</emphasis> C library for use with GCC on Atmel AVR microcontrollers</para><para>AVR Libc is a Free Software project whose goal is to provide a high quality C library for use with GCC on Atmel AVR microcontrollers.</para>
- <para>AVR Libc is licensed under a single unified license. This so-called modified Berkeley license is intented to be compatible with most Free Software licenses like the GPL, yet impose as little restrictions for the use of the library in closed-source commercial applications as possible.</para>
- <para>
- <emphasis>avr-binutils</emphasis> Cross Compiling GNU binutils targeted at avr</para><para>This is a Cross Compiling version of GNU binutils, which can be used to assemble and link binaries for the avr platform, instead of for the native i386 platform.</para>
- <para>
- <emphasis>avr-gdb</emphasis> GDB for (remote) debugging avr binaries</para><para>This is a special version of GDB, the GNU Project debugger, for (remote) debugging avr binaries. GDB allows you to see what is going on inside another program while it executes or what another program was doing at the moment it crashed.</para>
- <para>
- <emphasis>avarice</emphasis> Program for interfacing the Atmel JTAG ICE to GDB</para><para>Program for interfacing the Atmel JTAG ICE to GDB to allow users to debug their embedded AVR target</para>
- </section><section id="sn-">
- <title>Microchip PIC</title>
- <para>
- <emphasis>gputils</emphasis> Development utilities for Microchip (TM) PIC (TM) microcontrollers</para><para>This is a collection of development tools for Microchip (TM) PIC (TM) microcontrollers. This is ALPHA software: there may be serious bugs in it, and it's nowhere near complete. gputils currently only implements a subset of the features available with Microchip's tools. See the documentation for an up-to-date list of what gputils can do.</para>
- <para>
- <emphasis>gpsim</emphasis> A simulator for Microchip (TM) PIC (TM) microcontrollers</para><para>gpsim is a simulator for Microchip (TM) PIC (TM) microcontrollers. It supports most devices in Microchip's 12-bit, 14bit, and 16-bit core families. In addition, gpsim supports dynamically loadable modules such as LED's, LCD's, resistors, etc. to extend the simulation environment beyond the PIC.</para>
- <para>
- <emphasis>ktechlab</emphasis> Development and simulation of microcontrollers and electronic circuits</para><para>KTechlab is a development and simulation environment for microcontrollers and electronic circuits, distributed under the GNU General Public License. KTechlab consists of several well-integrated components: </para>
- <itemizedlist>
- <listitem>
- <para> A circuit simulator, capable of simulating logic, linear devices and some nonlinear devices. </para>
- </listitem><listitem>
- <para> Integration with gpsim, allowing PICs to be simulated in circuit. </para>
- </listitem><listitem>
- <para> A schematic editor, which provides a rich real-time feedback of the simulation.</para>
- </listitem><listitem>
- <para> A flowchart editor, allowing PIC programs to be constructed visually. </para>
- </listitem><listitem>
- <para> MicroBASIC; a BASIC-like compiler for PICs, written as a companion program to KTechlab. </para>
- </listitem><listitem>
- <para> An embedded Kate part, which provides a powerful editor for PIC programs. </para>
- </listitem><listitem>
- <para> Integrated assembler and disassembler via gpasm and gpdasm.</para>
- </listitem>
- </itemizedlist><para />
- <para>
- <emphasis>pikdev</emphasis> IDE for development of PICmicro based application (under Linux/KDE)</para><para>PiKdev is a simple IDE dedicated to the development of PIC based applications under KDE. Features: </para>
- <itemizedlist>
- <listitem>
- <para> Integrated editor </para>
- </listitem><listitem>
- <para> Project management </para>
- </listitem><listitem>
- <para> Integrated programming engine for 12, 14 and 16 bits PIC (flash or EPROM technology) </para>
- </listitem><listitem>
- <para> Support for parallel and serial port programmers </para>
- </listitem><listitem>
- <para> KDE compliant look-and-feel</para>
- </listitem>
- </itemizedlist><para />
- <para>WARNING: Administrator have to see the README.Fedora file locate in the /usr/share/doc/pikdev-0.9.2 directory to complete full feature installation.</para>
- <para>
- <emphasis>piklab</emphasis> Development environment for applications based on PIC & dsPIC</para><para>Piklab is a graphic development environment for PIC and dsPIC microcontrollers. It interfaces with various toochains for compiling and assembling and it supports several Microchip and direct programmers. WARNING: Administrator have to see the README.Fedora file locate in the /usr/share/doc/piklab-0.15.0 directory to complete full feature installation.</para>
- <para>
- <emphasis>pikloops</emphasis> Code generator for PIC delays</para><para>PiKLoop generate for you code to create delays for Microchip PIC microcontrollers. It is an useful companion for Pikdev or Piklab IDE.</para>
- </section><section id="sn-">
- <title>Others/Processor agnostic</title>
- <para>
- <emphasis>dfu-programmer</emphasis> A device firmware update based USB programmer for Atmel chips</para><para>A linux based command-line programmer for Atmel chips with a USB bootloader supporting ISP. This is a mostly Device Firmware Update (DFU) 1.0 compliant user-space application. Currently supported chips: 8051, AVR, at89c51snd1c, at90usb1287, at89c5130, at90usb1286, at89c5131, at90usb647, at89c5132, at90usb646, at90usb162, and at90usb82.</para>
- <para>
- <emphasis>sdcc</emphasis> Small Device C Compiler</para><para>sdcc-2.6.0-12 SDCC is a C compiler for 8051 class and similar microcontrollers. The package includes the compiler, assemblers and linkers, a device simulator and a core library. The processors supported (to a varying degree) include the 8051, ds390, z80, hc08, and PIC.</para>
- <para>
- <emphasis>uisp</emphasis> Universal In-System Programmer for Atmel AVR and 8051</para><para>Uisp is utility for downloading/uploading programs to AVR devices. Can also be used for some Atmel 8051 type devices. In addition, uisp can erase the device, write lock bits, verify and set the active segment. For use with the following hardware to program the devices: pavr, stk500, Atmel STK500, dapa, Direct AVR Parallel Access, stk200, Parallel Starter Kit, STK200, STK300, abb, Altera, ByteBlasterMV Parallel Port Download Cable, avrisp, Atmel AVR, bsd, fbprg (parallel), dt006 (parallel), dasa serial (RESET=RTS SCK=DTR MOSI=TXD MISO=CTS), dasa2 serial (RESET=!TXD SCK=RTS MOSI=DTR MISO=CTS)</para>
- <para>
- <emphasis>simcoupe</emphasis> SAM Coupe emulator (spectrum compatible)</para><para>SimCoupe emulates an 8bit Z80 based home computer, released in 1989 by Miles Gordon Technology. The SAM Coupe was largely spectrum compatible, with much improved hardware</para>
- <para>
- <emphasis>sjasm</emphasis> A z80 cross assembler</para><para>SjASM is a two pass macro Z80 cross assembler</para>
- <para>
- <emphasis>z88dk</emphasis> A Z80 cross compiler</para><para>z88dk is a Z80 cross compiler capable of generating binary files for a variety of Z80 based machines (such as the ZX81, Spectrum, Jupiter Ace and some TI calculators).</para>
- </section>
- </section>
- </article>
-</book>
diff --git a/en-US/Fedora_10_boot-time.xml b/en-US/Fedora_10_boot-time.xml
index d253102..26ddf2e 100644
--- a/en-US/Fedora_10_boot-time.xml
+++ b/en-US/Fedora_10_boot-time.xml
@@ -1,56 +1,93 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
-
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/Boot</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/Boot</title>
- <section id="sn-">
- <title>Fedora 10 Boot-Time </title>
- <para>Fedora 10 includes multiple boot-time updates, including changes that allow for faster booting and graphic booting changes.</para>
- <section id="sn-">
- <title>Plymouth </title>
- <para>Plymouth is the graphical boot up system debuting with Fedora 10.</para>
- <itemizedlist>
- <listitem>
- <para> Adding <programlisting format="linespecific">rhgb</programlisting> on the <programlisting format="linespecific">grub</programlisting> command line directs Plymouth to load the appropriate plugin for your hardware.</para>
- </listitem><listitem>
- <para> The graphical boot splash screen that comes with Plymouth requires kernel mode setting drivers to work best. There are not kernel modesetting drivers available for all hardware yet. To see the graphical splash before the drivers are generally available, add <programlisting format="linespecific">vga=0x318</programlisting> to the kernel <programlisting format="linespecific">grub</programlisting> command line. This uses <programlisting format="linespecific">vesafb</programlisting>, which does not necessarily give the native resolution for a flat panel, and may cause flickering or other weird interactions with X. Without kernel modesetting drivers or <programlisting format="linespecific">vga=0x318</programlisting>, Plymouth uses a text-based plugin that is plain but functional.</para>
- </listitem><listitem>
- <para> Currently, only Radeon R500 and higher users get kernel modesetting by default. There is work in progress to provide modesetting for R100 and R200. Additionally, Intel kernel modesetting drivers are in development, but not turned on by default.</para>
- </listitem><listitem>
- <para> The kernel modesetting drivers are still in development and buggy. If you end up with nothing but a black screen during boot up, or a screen with nothing but random noise on it, then adding will <programlisting format="linespecific">nomodeset</programlisting> to the kernel boot prompt in grub disables modesetting.</para>
- </listitem><listitem>
- <para> Plymouth hides boot messages. To view boot messages, press the <emphasis>[Esc]</emphasis> key during boot, or view them in <programlisting format="linespecific">/var/log/boot.log</programlisting> after boot up. Alternatively, remove <programlisting format="linespecific">rhgb</programlisting> from the kernel command line and plymouth displays all boot messages. There is also a status icon on the login screen to view boot warnings.</para>
- </listitem>
- </itemizedlist>
- </section><section id="sn-">
- <title>Faster Booting </title>
- <para>Fedora 10 gets a faster boot from improvements in process start-up.</para>
- <itemizedlist>
- <listitem>
- <para> Readahead is started in parallel with the boot process.</para>
- </listitem><listitem>
- <para> Udev may appear to be slower but in fact readahead reads all disk buffers needed for the boot process in the background and shortens the whole boot process. Creation of the readahead file list is done monthly and can be triggered manually by touching <programlisting format="linespecific">/.readahead_collect</programlisting>. The configuration file <programlisting format="linespecific">/etc/sysconfig/readahead</programlisting> can be edited to turn off readahead-collector and/or readahead. </para>
- </listitem>
- </itemizedlist>
- </section><section id="sn-">
- <title>Kernel Modesetting </title>
- <para>Kernel modesetting (KMS) can default to either enabled or disabled in the DRM driver and it can be enabled or disabled at boot-time.</para>
- <itemizedlist>
- <listitem>
- <para> Both Plymouth and the DDX drivers detect whether KMS is present and enabled. If it is present and enabled, Plymouth and DDX drivers will take advantage of them. </para>
- </listitem><listitem>
- <para> If KMS is not present or it is present but disabled then Plymouth will automatically fall back to the text splash and the DDX driver will automatically fall back to user-space modesetting.</para>
- </listitem><listitem>
- <para> Allows for faster user switching, seamless X server switching and graphical panic messages.</para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
+
+<section lang="en" id="sn-Fedora_10_boot-time">
+ <title>Fedora 10 boot-time</title>
+ <para>Fedora 10 includes multiple boot-time updates, including changes
+ that allow for faster booting and graphic booting changes.</para>
+ <section id="sn-Plymouth">
+ <title>Plymouth</title>
+ <para>Plymouth is the graphical boot up system debuting with Fedora
+ 10.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Adding <command>rhgb</command> on the
+ <command>grub</command> command line directs Plymouth to load
+ the appropriate plugin for your hardware.</para>
+ </listitem><listitem>
+ <para>The graphical boot splash screen that comes with Plymouth
+ requires kernel mode setting drivers to work best. There are
+ not kernel modesetting drivers available for all hardware yet.
+ To see the graphical splash before the drivers are generally
+ available, add <userinput>vga=0x318</userinput> to the kernel
+ <command>grub</command> command line. This uses
+ <command>vesafb</command>, which does not necessarily give the
+ native resolution for a flat panel, and may cause flickering
+ or other weird interactions with X. Without kernel modesetting
+ drivers or <userinput>vga=0x318</userinput>, Plymouth uses a
+ text-based plugin that is plain but functional.</para>
+ </listitem><listitem>
+ <para>Currently, only Radeon R500 and higher users get kernel
+ modesetting by default. There is work in progress to provide
+ modesetting for R100 and R200. Additionally, Intel kernel
+ modesetting drivers are in development, but not turned on by
+ default.</para>
+ </listitem><listitem>
+ <para>The kernel modesetting drivers are still in development
+ and buggy. If you end up with nothing but a black screen
+ during boot up, or a screen with nothing but random noise on
+ it, then adding <userinput>nomodeset</userinput> to the kernel
+ boot prompt in grub disables modesetting.</para>
+ </listitem><listitem>
+ <para>Plymouth hides boot messages. To view boot messages, press
+ the <keycap>Esc</keycap> key during boot, or view them in
+ <filename>/var/log/boot.log</filename> after boot up.
+ Alternatively, remove <command>rhgb</command> from the kernel
+ command line and plymouth displays all boot messages. There is
+ also a status icon on the login screen to view boot
+ warnings.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="sn-Faster_booting">
+ <title>Faster booting</title>
+ <para>Fedora 10 gets a faster boot from improvements in process
+ start-up.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Readahead is started in parallel with the boot
+ process.</para>
+ </listitem><listitem>
+ <para>Udev may appear to be slower but in fact readahead reads
+ all disk buffers needed for the boot process in the background
+ and shortens the whole boot process. Creation of the readahead
+ file list is done monthly and can be triggered manually by
+ touching <filename>/.readahead_collect</filename>. The
+ configuration file
+ <filename>/etc/sysconfig/readahead</filename> can be edited to
+ turn off readahead-collector and/or readahead.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="sn-Kernel_modesetting">
+ <title>Kernel modesetting</title>
+ <para>Kernel modesetting (KMS) can default to either enabled or
+ disabled in the DRM driver and it can be enabled or disabled at
+ boot-time.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Both Plymouth and the DDX drivers detect whether KMS is
+ present and enabled. If it is present and enabled, Plymouth
+ and DDX drivers will take advantage of them. </para>
+ </listitem><listitem>
+ <para>If KMS is not present or it is present but disabled then
+ Plymouth will automatically fall back to the text splash and
+ the DDX driver will automatically fall back to user-space
+ modesetting.</para>
+ </listitem><listitem>
+ <para>Allows for faster user switching, seamless X server
+ switching, and graphical panic messages.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+</section>
diff --git a/en-US/Fedora_10_overview.xml b/en-US/Fedora_10_overview.xml
new file mode 100644
index 0000000..ef6c94a
--- /dev/null
+++ b/en-US/Fedora_10_overview.xml
@@ -0,0 +1,91 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
+
+<section lang="en" id="sn-Fedora_10_overview">
+ <title>Fedora 10 overview</title>
+ <para>As always, Fedora continues to develop (<ulink
+ url="http://www.fedoraproject.org/wiki/RedHatContributions"/>)
+ and integrate the latest free and open source software (<ulink
+ url="http://www.fedoraproject.org/wiki/Features"/>.)
+ The following sections provide a brief overview of major changes
+ from the last release of Fedora. For more details about other
+ features that are included in Fedora 10, refer to their individual
+ wiki pages that detail feature goals and progress:</para><para>
+ <ulink
+ url="http://www.fedoraproject.org/wiki/Releases/10/FeatureList"/>
+ </para>
+ <para>Throughout the release cycle, there are interviews with
+ the developers behind key features giving out the inside
+ story:</para>
+ <para>
+ <ulink
+ url="http://www.fedoraproject.org/wiki/Interviews"/>
+ </para>
+ <para>The following are major features for Fedora 10:</para>
+ <itemizedlist>
+ <listitem>
+ <para>Wireless connection sharing enables ad hoc network sharing
+ -- <ulink
+ url="http://www.fedoraproject.org/wiki/Features/ConnectionSharing"/>
+ </para>
+ </listitem><listitem>
+ <para>Better setup and use of printers through improved
+ management tools -- <ulink
+ url="http://www.fedoraproject.org/wiki/Features/BetterPrinting"/>
+ </para>
+ </listitem><listitem>
+ <para>Virtualization storage provisioning for local and remote
+ connections now simplified -- <ulink
+ url="http://www.fedoraproject.org/wiki/Features/VirtStorage"/>
+ </para>
+ </listitem><listitem>
+ <para>SecTool is a new security audit and intrusion detections
+ system -- <ulink
+ url="http://www.fedoraproject.org/wiki/Features/SecurityAudit"/>
+ </para>
+ </listitem><listitem>
+ <para>RPM 4.6 is a major update to the powerful, flexible
+ software management libraries -- <ulink
+ url="http://www.fedoraproject.org/wiki/Features/RPM4.6"/>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>Some other features in this release include:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Glitch free audio and better performance is achieved
+ through a rewrite of the PulseAudio sound server to use
+ timer-based audio scheduling -- <ulink
+ url="http://www.fedoraproject.org/wiki/Features/GlitchFreeAudio"/>
+ </para>
+ </listitem><listitem>
+ <para> Improved webcam support -- <ulink
+ url="http://www.fedoraproject.org/wiki/Features/BetterWebcamSupport"/>
+ </para>
+ </listitem><listitem>
+ <para> Better support for infrared remote controls makes them
+ easier to connect and work with many applications -- <ulink
+ url="http://www.fedoraproject.org/wiki/Features/BetterLIRCSupport"/>
+ </para>
+ </listitem><listitem>
+ <para> The paths
+ <computeroutput>/usr/local/sbin:/usr/sbin:/sbin</computeroutput>
+ have been added to the <envar>PATH</envar> for normal users, to
+ simplify command-line administration tasks -- <ulink
+ url="http://fedoraproject.org/wiki/Features/SbinSanity"/>
+ </para>
+ </listitem><listitem>
+ <para> The online account service provides applications with
+ credentials for online accounts listed on <ulink
+ url="http://online.gnome.org"/> or stored in GConf -- <ulink
+ url="http://www.fedoraproject.org/wiki/Features/OnlineAccountsService"/>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>Features for Fedora 10 are tracked on the feature list page:</para>
+ <para>
+ <ulink
+ url="http://www.fedoraproject.org/wiki/Releases/10/FeatureList"/>
+ </para>
+</section>
diff --git a/en-US/Fedora_Live_images.xml b/en-US/Fedora_Live_images.xml
index 480ee8b..ef90997 100644
--- a/en-US/Fedora_Live_images.xml
+++ b/en-US/Fedora_Live_images.xml
@@ -1,80 +1,163 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
+
+<section id="sn-Fedora_Live_images" lang="en">
+ <title>Fedora Live images</title>
+ <para>The Fedora 10 release includes several Fedora Live ISO images in
+ addition to the traditional installation images. These ISO images
+ are bootable, and you can burn them to media and use them to try out
+ Fedora. They also include a feature that allows you to install the
+ Fedora Live image content to your hard drive for persistence and
+ higher performance.</para>
+ <section id="sn-Available_images">
+ <title>Available images</title>
+ <para>For a complete list of current spins available, and
+ instructions for using them, refer to:</para>
+ <para>
+ <ulink url="http://fedoraproject.org/wiki/CustomSpins"/>
+ </para>
+ </section>
+ <section id="sn-Usage_information">
+ <title>Usage information</title>
+ <para>To boot from the Fedora Live image, insert it into your
+ computer and restart. To log in and use the desktop environment,
+ enter the username <systemitem
+ class="username">fedora</systemitem>. There is no password on
+ this account. The GNOME-based Fedora Live images automatically
+ login after one minute, so users have time to select a preferred
+ language. After logging in, if you wish to install the contents of
+ the live image to your hard drive, click on the <guiicon>Install
+ to Hard Drive</guiicon> icon on the desktop.</para>
+ </section>
+ <section id="sn-Text_mode_installation">
+ <title>Text mode installation</title>
+ <para>You can do a text mode installation of the Fedora Live images
+ using the <command>liveinst</command> command in the
+ console.</para>
+ </section>
+ <section id="sn-USB booting">
+ <title>USB booting</title>
+ <para>Another way to use these Fedora Live images is to put them on
+ a USB stick. To do this, use the
+ <package>liveusb-creator</package> graphical interface. Use
+ <guimenuitem>Add/Remove Software</guimenuitem>, search for, then
+ install <package>liveusb-creator</package>. To install using
+ <command>yum</command>:</para>
+ <screen>
+ <userinput>su -c 'yum install liveusb-creator'</userinput>
+ </screen>
+ <para>Instead of the graphical tool, you can use the command line
+ interface from the <package>livecd-tools</package> package. Then,
+ run the <command>livecd-iso-to-disk</command> script:</para>
+ <screen>
+ <userinput>/usr/bin/livecd-iso-to-disk /path/to/live.iso
+ /dev/sdb1</userinput>
+ </screen>
+ <para>Replace <filename>/dev/sdb1</filename> with the partition
+ where you want to put the image.</para>
+ <para>This is <emphasis>not</emphasis> a destructive process; any
+ data you currently have on your USB stick <emphasis>is
+ preserved</emphasis>.</para>
+ </section>
+ <section id="sn-Persistent_home_directory">
+ <title>Persistent home directory</title>
+ <para>Support for keeping a persistent <filename>/home</filename>
+ with the rest of the system stateless has been added for Fedora
+ 10. This includes support for encrypting
+ <filename>/home</filename> to protect your system in the case
+ where your USB stick is lost or stolen. To use this, download the
+ live image and run the following command:</para>
+ <screen>
+ <userinput>livecd-iso-to-disk --home-size-mb 512 /path/to/live.iso
+ /dev/sdb1</userinput>
+ </screen>
+ <para>Replace <filename>/dev/sdb1</filename> with the partition
+ where you want to put the image.</para>
+ <para>Replace <computeroutput>512</computeroutput> with the desired
+ size in megabytes of the persistent <filename>/home</filename>.
+ The <command>livecd-iso-to-disk</command> shell script is stored
+ in the <filename>LiveOS</filename> directory at the top level of
+ the CD image. The USB media must have sufficient free space for
+ the Fedora Live image, plus the <filename>/home</filename>, plus
+ any other data to be stored on the media. By default, this
+ encrypts your data and prompts for a passphrase to use. If you
+ want to have an unencrypted <filename>/home</filename>, then you
+ can specify <option>--unencrypted-home</option>.</para>
+ <para>Note that later runs of <command>livecd-iso-to-disk</command>
+ preserve the <filename>/home</filename> that is created on the USB
+ stick, continuing to use it even if you change your live
+ image.</para>
+ </section>
+ <section id="sn-Live_USB_persistence">
+ <title>Live USB persistence</title>
+ <para>Support for persistent changes with a Fedora Live image exists
+ for Fedora 9 and later. The primary use case is booting from a
+ Fedora Live image on a USB flash drive and storing changes to that
+ same device. To do this, download the Fedora Live image and then
+ run the following command:</para>
+ <screen>
+ <userinput>livecd-iso-to-disk --overlay-size-mb 512
+ /path/to/live.iso /dev/sdb1</userinput>
+ </screen>
+ <para>Replace <filename>/dev/sdb1</filename> with the partition
+ where you want to put the image.</para>
+ <para>Replace <computeroutput>512</computeroutput> with the desired
+ size in megabytes of the persistent data, or
+ <firstterm>overlay</firstterm>. The
+ <command>livecd-iso-to-disk</command> shell script is stored in
+ the <filename>LiveOS</filename> directory at the top level of the
+ CD image. The USB media must have sufficient free space for the
+ Fedora Live image, plus the overlay, plus any other data to be
+ stored on the media.</para>
+ </section>
+ <section id="sn-Booting_a_Fedora_Live_image_off_of_USB_on_Intel-based_Apple_hardware">
+ <title>Booting a Fedora Live image off of USB on Intel-based Apple
+ hardware</title>
+ <para>Fedora 10 includes support for putting the live image onto a
+ USB image and then booting it on Intel processor-based Apple
+ hardware. Unlike for most x86 machines, this unfortunately
+ requires reformatting the USB stick that you are using. To set up
+ a stick for this, you can run:</para>
+ <screen>
+ <userinput>/usr/bin/livecd-iso-to-disk --mactel /path/to/live.iso
+ /dev/sdb1</userinput>
+ </screen>
+ <para>Replace <filename>/dev/sdb1</filename> with the partition
+ where you want to put the image.</para>
+ <para>Note that all of the other arguments for the
+ <command>livecd-iso-to-disk</command> tool as described above can
+ be used here as well.</para>
+ </section>
+ <section id="sn-Differences_from_a_regular_Fedora_install">
+ <title>Differences from a regular Fedora install</title>
+ <para>The following items are different from a normal Fedora install
+ with the Fedora Live images.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Fedora Live images provide a subset of packages available
+ in the regular DVD image. Both connect to the same repository
+ that has all the packages.</para>
+ </listitem><listitem>
+ <para>The SSH daemon <systemitem
+ class="daemon">sshd</systemitem> is disabled by default. The
+ daemon is disabled because the default username in the Fedora
+ Live images does not have a password. However, installation to
+ hard disk prompts for creating a new username and
+ password.</para>
+ </listitem><listitem>
+ <para>Fedora Live image installations do not allow any package
+ selection or upgrade capability since they copy the entire
+ file system from media or USB disks to the hard disk. After
+ the installation is complete, and your system has been
+ rebooted, you can add and remove packages as desired with the
+ <guimenuitem>Add/Remove Packages</guimenuitem> tool,
+ <command>yum</command>, or the other software management
+ tools.</para>
+ </listitem><listitem>
+ <para>Fedora Live images do not work on i586
+ architecture.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+</section>
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/Live</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/Live</title>
- <section id="sn-">
- <title>Fedora Live Images </title>
- <para>The Fedora 10 release includes several Fedora Live ISO images in addition to the traditional installation images. These ISO images are bootable, and you can burn them to media and use them to try out Fedora. They also include a feature that allows you to install the Fedora Live image content to your hard drive for persistence and higher performance. </para>
- <section id="sn-">
- <title>Available Images </title>
- <para>For a complete list of current spins available, and instructions for using them, refer to:</para>
- <para>
- <ulink url="http://fedoraproject.org/wiki/CustomSpins">http://fedoraproject.org/wiki/CustomSpins</ulink>
- </para>
- </section><section id="sn-">
- <title>Usage Information </title>
- <para>To boot from the Fedora Live image, insert it into your computer and restart. To log in and use the desktop environment, enter the username <programlisting format="linespecific">fedora</programlisting>. There is no password on this account. The GNOME-based Fedora Live images automatically login after one minute, so users have time to select a preferred language. After logging in, if you wish to install the contents of the live image to your hard drive, click on the <emphasis>Install to Hard Drive</emphasis> icon on the desktop.</para>
- </section><section id="sn-">
- <title>Text Mode Installation </title>
- <para>You can do a text mode installation of the Fedora Live images using the <programlisting format="linespecific">liveinst</programlisting> command in the console.</para>
- </section><section id="sn-">
- <title>USB Booting </title>
- <para>Another way to use these Fedora Live images is to put them on a USB stick. To do this, you can use liveusb-creator graphical interface. You can use Add/Remove software, search and install liveusb-creator or install using yum:</para>
- <para />
- <programlisting>
-su -c 'yum install liveusb-creator'
-</programlisting>
- <para />
- <para>You can also use the command line interface, install the <programlisting format="linespecific">livecd-tools</programlisting> package from the repository. Then, run the <programlisting format="linespecific">livecd-iso-to-disk</programlisting> script:</para><para />
- <programlisting>/usr/bin/livecd-iso-to-disk /path/to/live.iso /dev/sdb1
-</programlisting>
- <para />
- <para>Replace <emphasis>/dev/sdb1</emphasis> with the partition where you want to put the image.</para><para>This is <emphasis>not</emphasis> a destructive process; any data you currently have on your USB stick <emphasis>is preserved</emphasis>.</para>
- </section><section id="sn-">
- <title>Persistent Home Directory </title>
- <para>Support for keeping a persistent <programlisting format="linespecific">/home</programlisting> with the rest of the system stateless has been added for Fedora 10. This includes support for encrypting <programlisting format="linespecific">/home</programlisting> to protect your system in the case where your USB stick is lost or stolen. To use this, download the live image and run the following command:</para><para />
- <programlisting>livecd-iso-to-disk --home-size-mb 512 /path/to/live.iso /dev/sdb1
-</programlisting>
- <para />
- <para>Replace <programlisting format="linespecific">/dev/sdb1</programlisting> with the partition where you want to put the image.</para><para>Replace <programlisting format="linespecific">512</programlisting> with the desired size in megabytes of the persistent <programlisting format="linespecific">/home</programlisting>. The <programlisting format="linespecific">livecd-iso-to-disk</programlisting> shell script is stored in the <programlisting format="linespecific">LiveOS</programlisting> directory at the top level of the CD image. The USB media must have sufficient free space for the Fedora Live image, plus the <programlisting format="linespecific">/home</programlisting>, plus any other data to be stored on the media. By default, this encrypts your data and prompts for a passphrase to use. If you want to have an unencrypted <programlisting format="linespecific">/home</programlisting>, then you can specify <programlisting format="linespecific">--unencrypted-hom
e</programlisting>.</para><para>Note that later runs of <programlisting format="linespecific">livecd-iso-to-disk</programlisting> preserve the <programlisting format="linespecific">/home</programlisting> that is created on the USB stick, continuing to use it even if you change your live image. </para>
- </section><section id="sn-">
- <title>Live USB Persistence </title>
- <para>Support for persistent changes with a Fedora Live image exists for Fedora 9 and later. The primary use case is booting from a Fedora Live image on a USB flash drive and storing changes to that same device. To do this, download the Fedora Live image and then run the following command:</para>
- <para />
- <programlisting>livecd-iso-to-disk --overlay-size-mb 512 /path/to/live.iso /dev/sdb1
-</programlisting>
- <para />
- <para>Replace <programlisting format="linespecific">/dev/sdb1</programlisting> with the partition where you want to put the image.</para><para>Replace <programlisting format="linespecific">512</programlisting> with the desired size in megabytes of the persistent data, or <programlisting format="linespecific">overlay</programlisting>. The <programlisting format="linespecific">livecd-iso-to-disk</programlisting> shell script is stored in the <programlisting format="linespecific">LiveOS</programlisting> directory at the top level of the CD image. The USB media must have sufficient free space for the Fedora Live image, plus the overlay, plus any other data to be stored on the media.</para>
- </section><section id="sn-">
- <title>Booting a Fedora Live Image Off of USB on Intel-based Apple Hardware </title>
- <para>Fedora 10 includes support for putting the live image onto a USB image and then booting it on Intel processor-based Apple hardware. Unlike for most x86 machines, this unfortunately requires reformatting the USB stick that you are using. To set up a stick for this, you can run</para>
- <para />
- <programlisting>/usr/bin/livecd-iso-to-disk --mactel /path/to/live.iso /dev/sdb1
-</programlisting>
- <para />
- <para>Replace <programlisting format="linespecific">/dev/sdb1</programlisting> with the partition where you want to put the image.</para><para>Note that all of the other arguments for the <programlisting format="linespecific">livecd-iso-to-disk</programlisting> tool as described above can be used here as well.</para>
- </section><section id="sn-">
- <title>Differences From a Regular Fedora Install </title>
- <para>The following items are different from a normal Fedora install with the Fedora Live images.</para>
- <itemizedlist>
- <listitem>
- <para> Fedora Live images provide a subset of packages available in the regular DVD image. Both connect to the same repository that has all the packages.</para>
- </listitem><listitem>
- <para> The SSH daemon <programlisting format="linespecific">sshd</programlisting> is disabled by default. The daemon is disabled because the default username in the Fedora Live images does not have a password. However, installation to hard disk prompts for creating a new username and password.</para>
- </listitem><listitem>
- <para> Fedora Live image installations do not allow any package selection or upgrade capability since they copy the entire file system from media or USB disks to the hard disk. After the installation is complete, and your system has been rebooted, you can add and remove packages as desired with the <emphasis>Add/Remove Packages</emphasis> tool, <programlisting format="linespecific">yum</programlisting>, or the other software management tools.</para>
- </listitem><listitem>
- <para> Fedora Live images do not work on <programlisting format="linespecific">i586</programlisting> architecture.</para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
diff --git a/en-US/Fedora_Project.xml b/en-US/Fedora_Project.xml
index 570d374..7421716 100644
--- a/en-US/Fedora_Project.xml
+++ b/en-US/Fedora_Project.xml
@@ -1,45 +1,65 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/ProjectOverview</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/ProjectOverview</title>
- <section id="sn-">
- <title>Fedora Project </title>
- <para> The goal of the Fedora Project is to work with the Linux community to build a complete, general-purpose operating system exclusively from free and open source software. The Fedora Project is driven by the individuals that contribute to it. As a tester, developer, documenter, or translator, you can make a difference. Refer to <ulink url="http://join.fedoraproject.org">http://join.fedoraproject.org</ulink> for details. For information on the channels of communication for Fedora users and contributors, refer to <ulink url="http://fedoraproject.org/wiki/Communicate.">http://fedoraproject.org/wiki/Communicate.</ulink>
- </para><para>In addition to the website, the following mailing lists are available:</para>
- <itemizedlist>
- <listitem>
- <para> fedora-list at redhat.com, for users of Fedora releases</para>
- </listitem><listitem>
- <para> fedora-test-list at redhat.com, for testers of Fedora test releases</para>
- </listitem><listitem>
- <para> fedora-devel-list at redhat.com, for developers, developers, developers</para>
- </listitem><listitem>
- <para> fedora-docs-list at redhat.com, for participants of the Documentation Project</para>
- </listitem>
- </itemizedlist><para>To subscribe to any of these lists, send an email with the word "subscribe" in the subject to <emphasis><listname>-request</emphasis>, where <emphasis><listname></emphasis> is one of the above list names. Alternately, you can subscribe to Fedora mailing lists through the Web interface at <ulink url="http://www.redhat.com/mailman/listinfo/.">http://www.redhat.com/mailman/listinfo/.</ulink>
- </para><para>The Fedora Project also uses several IRC (Internet Relay Chat) channels. IRC is a real-time, text-based form of communication, similar to Instant Messaging. With it, you may have conversations with multiple people in an open channel, or chat with someone privately one-on-one. To talk with other Fedora Project participants via IRC, access the Freenode IRC network. Refer to the Freenode website at <ulink url="http://www.freenode.net/">http://www.freenode.net/</ulink> for more information.</para><para>Fedora Project participants frequent the <programlisting format="linespecific">#fedora</programlisting> channel on the Freenode network, while Fedora Project developers may often be found on the <programlisting format="linespecific">#fedora-devel</programlisting> channel. Some of the larger projects may have their own channels as well. This information may be found on the webpage for the project, and at <ulink url="http://fedoraproject.org/w/index.php?title=
Communicate">Communicate</ulink>.</para><para>In order to talk on the <programlisting format="linespecific">#fedora</programlisting> channel, you need to register your nickname, or <emphasis>nick</emphasis>. Instructions are given when you <programlisting format="linespecific">/join</programlisting> the channel.</para><para>
- <para>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata contentwidth="35px" fileref="http://fedoraproject.org/w/uploads/c/cc/Note.png" scalefit="1" width="35px" />
- </imageobject><caption>
- <para />
- </caption>
- </inlinemediaobject>
- </para><para>
- <emphasis> IRC Channels </emphasis>
- <literallayout>
-</literallayout>The Fedora Project and Red Hat have no control over the Fedora Project IRC channels or their content.</para>
- </para>
- </para>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
+<section lang="en" id="sn-Fedora Project">
+ <title>Fedora Project</title>
+ <para>The goal of the Fedora Project is to work with the Linux
+ community to build a complete, general-purpose operating system
+ exclusively from free and open source software. The Fedora Project
+ is driven by the individuals that contribute to it. As a tester,
+ developer, documenter, or translator, you can make a difference.
+ Refer to <ulink url="http://join.fedoraproject.org"/> for details.
+ For information on the channels of communication for Fedora users
+ and contributors, refer to <ulink
+ url="http://fedoraproject.org/wiki/Communicate">.
+ </para>
+ <para>In addition to the website, the following mailing lists are
+ available:</para>
+ <itemizedlist>
+ <listitem>
+ <para><ulink url="mailto:fedora-list at redhat.com"/>, for users of
+ Fedora releases</para>
+ </listitem><listitem>
+ <para><ulink url="mailto:fedora-test-list at redhat.com"/>, for
+ testers of Fedora test releases</para>
+ </listitem><listitem>
+ <para><ulink url="mailto:fedora-devel-list at redhat.com"/>, for
+ developers, developers, developers</para>
+ </listitem><listitem>
+ <para><ulink url="mailto:fedora-docs-list at redhat.com"/>, for
+ participants of the Documentation Project</para>
+ </listitem>
+ </itemizedlist>
+ <para>To subscribe to any of these lists, send an email with the word
+ "subscribe" in the subject to
+ <replaceable><listname>-request</replaceable>, where
+ <replaceable><listname></replaceable> is one of the above list
+ names. Alternately, you can subscribe to Fedora mailing lists
+ through the Web interface at <ulink
+ url="http://www.redhat.com/mailman/listinfo/"/>.
+ </para>
+ <para>The Fedora Project also uses several IRC (Internet Relay Chat)
+ channels. IRC is a real-time, text-based form of communication,
+ similar to Instant Messaging. With it, you may have conversations
+ with multiple people in an open channel, or chat with someone
+ privately one-on-one. To talk with other Fedora Project
+ participants via IRC, access the Freenode IRC network. Refer to the
+ Freenode website at <ulink url="http://www.freenode.net/"/> for more
+ information.</para><para>Fedora Project participants frequent the
+ <computeroutput>#fedora</computeroutput> channel on the Freenode
+ network, while Fedora Project developers may often be found on the
+ <computeroutput>#fedora-devel</computeroutput> channel. Some of the
+ larger projects may have their own channels as well. This
+ information may be found on the webpage for the project, and at
+ <ulink
+ url="http://fedoraproject.org/w/index.php?title=Communicate"/>.</para>
+ <para>In order to talk on the <computeroutput>#fedora</computeroutput>
+ channel, you need to register your nickname, or
+ <firstterm>nick</firstterm>. Instructions are given when you
+ <userinput>/join</userinput> the channel.</para>
+ <note>
+ <title>IRC Channels</title>
+ <para>The Fedora Project and Red Hat have no control over the Fedora
+ Project IRC channels or their content.</para>
+ </note>
+</section>
diff --git a/en-US/Fedora_desktop.xml b/en-US/Fedora_desktop.xml
index 1b69106..c4c7b26 100644
--- a/en-US/Fedora_desktop.xml
+++ b/en-US/Fedora_desktop.xml
@@ -1,189 +1,401 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
-
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/Desktop</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/Desktop</title>
- <section id="sn-">
- <title>Fedora Desktop </title>
- <para>This section details changes that affect Fedora graphical desktop users.</para>
- <section id="sn-">
- <title>Better Webcam support </title>
- <para>Fedora 10 comes with improved support for webcams.</para>
- <para>This support follows on the improvements to the UVC driver first introduced in Fedora 9 that added support for any webcam with a Windows Vista compliant logo. Fedora 10 features a new v4l2 version of <programlisting format="linespecific">gspca</programlisting>, a USB webcam driver framework with support for many different USB webcam bridges and sensors.</para><para>Userspace support for webcams has also been improved by adding <programlisting format="linespecific">libv4l</programlisting> and updating all webcam using applications to use <programlisting format="linespecific">libv4l</programlisting>. This support, this makes these applications understand the often manufacturer specific and custom video formats emitted by many webcams, esp. by many of the webcams supported by gspca.</para><para>For a list of all webcams and applications with which Fedora-10's new webcam support has been tested see the <ulink url="https://fedoraproject.org/wiki/Features/BetterW
ebcamSupport"> BetterWebcamSupport feature page</ulink>, for a list of all cams supported by the original version of gspca see the <ulink url="http://mxhaard.free.fr/spca5xx.html"> original gspca website</ulink>. The v4l2 version of gspca in Fedora-10 supports all these webcams and more.</para>
- </section><section id="sn-">
- <title>Plymouth Graphical Boot </title>
- <para>For information about the new grapical boot mode read <ulink url="http://fedoraproject.org/w/index.php?title=Docs/Beats/Boot%23Plymouth_Graphical_Boot">Docs/Beats/Boot#Plymouth_Graphical_Boot</ulink>.</para>
- </section><section id="sn-">
- <title>Echo Icon Theme </title>
- <para>Echo is an icon theme developed for Fedora by the volunteer Fedora Art community. Echo inherits the isometric perspective from the classic Bluecurve theme while introducing a refreshing new look. It follows the freedesktop.org theme specification. The current version covers essential icons from the desktop menus and applications. Future revisions will bring broader coverage. </para>
- <para>Currently, both GNOME and Xfce use the Echo icon theme by default. KDE continues to use the Oxygen icon theme. The next release of Fedora may introduce Echo by default for KDE for a consistent look and feel across different desktop environments.</para>
- </section><section id="sn-">
- <title>Infrared remote support </title>
- <para>New to Fedora 10 is the <programlisting format="linespecific">gnome-lirc-properties</programlisting> package with a new graphical front-end for configuring LIRC to use with applications supporting the protocol. For more information refer to <ulink url="http://fedoraproject.org/w/index.php?title=Docs/Beats/Multimedia%23Infrared_remote_support">Docs/Beats/Multimedia#Infrared_remote_support</ulink>.</para><para>LIRC is routinely used in multimedia applications to implement support for infrared remote controls, and using it in <emphasis>Rhythmbox</emphasis> and <emphasis>Totem</emphasis> should be as easy as plugging the remote receiver into your computer, then selecting <emphasis>[Auto-detect]</emphasis> in the <emphasis>Infrared Remote Control</emphasis> preferences. Refer to the feature page for more information:</para><para>
- <ulink url="https://fedoraproject.org/wiki/Features/BetterLIRCSupport">https://fedoraproject.org/wiki/Features/BetterLIRCSupport</ulink>
- </para>
- </section><section id="sn-">
- <title>Bluetooth: BlueZ 4.0 </title>
- <para>The Bluetooth support stack, called BlueZ (<ulink url="http://www.bluez.org),">http://www.bluez.org),</ulink> has been updated to version 4.x in Fedora 10. Most changes in this version are useful for application developers, but users can notice the new, easier to use wizard for setting up keyboards, mice, and other supported Bluetooth devices. There is also the ability to turn-off the Bluetooth adapter on most brands of laptops through the preferences. This new version will also allow better support for audio devices in the future, through PulseAudio.</para><para>Note that the default Bluetooth kernel driver was also switched to <programlisting format="linespecific">btusb</programlisting>, which cuts down power consumption compared to its predecessor <programlisting format="linespecific">hci_usb</programlisting>.</para>
- </section><section id="sn-">
- <title>GNOME </title>
- <para>This release features GNOME 2.24. For more details refer to:</para>
- <para>
- <ulink url="http://www.gnome.org/start/2.24/">http://www.gnome.org/start/2.24/</ulink>
- </para><section id="sn-">
- <title>Empathy Instant Messenger </title>
- <para>
- <emphasis>Empathy</emphasis> instant messenger is the new default replacing <emphasis>Pidgin</emphasis> in this release. It has support for multiple protocols including IRC, XMPP(Jabber), Yahoo, MSN, and others via plugins. It also supports video and voice in the XMPP protocol, with support for other protocols under active development. Empathy uses the <programlisting format="linespecific">telepathy</programlisting> framework that has a number of additional plugins:</para><itemizedlist>
- <listitem>
- <para>
- <programlisting format="linespecific">telepathy-gabble</programlisting> - Jabber/XMPP lugin</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">telepathy-idle</programlisting> - IRC plugin</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">telepathy-butterfly</programlisting> - MSN plugin</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">telepathy-sofiasip</programlisting> - SIP plugin</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">telepathy-haze</programlisting> - Libpurple (Pidgin) library connection manager provides support for other protocols such as Yahoo</para>
- </listitem>
- </itemizedlist><para>
- <emphasis>Pidgin</emphasis> continues to be available in the Fedora software repository and is retained as the default for users upgrading from previous releases of Fedora. </para>
- </section><section id="sn-">
- <title>GNOME Display Manager </title>
- <para>The GNOME Display Manager (<programlisting format="linespecific">gdm</programlisting>) has been updated to the latest upstream code, which is a complete rewrite driven by Fedora developers. PolicyKit can be used to control shutdown and reboot. The configuration tool <programlisting format="linespecific">gdmsetup</programlisting> is missing currently, and is set to be replaced. For configuration changes, refer to:</para><para>
- <ulink url="http://live.gnome.org/GDM/2.22/Configuration">http://live.gnome.org/GDM/2.22/Configuration</ulink>
- </para>
- </section><section id="sn-">
- <title>Codec installation helper </title>
- <para>The GStreamer codec installation helper <programlisting format="linespecific">codeina</programlisting> was replaced by a PackageKit-based solution for Fedora 10. When Totem, Rhythmbox, or another GStreamer application require a plugin to read a film or song, a PackageKit dialogue appears, allowing the user to search for the necessary package in the configured repositories.</para><para>More details are available on the feature page:</para>
- <para>
- <ulink url="https://fedoraproject.org/wiki/Features/GStreamer_dependencies_in_RPM">https://fedoraproject.org/wiki/Features/GStreamer_dependencies_in_RPM</ulink>
- </para>
- </section>
- </section><section id="sn-">
- <title>KDE </title>
- <para>This release features KDE 4.1.2. As the <programlisting format="linespecific">kdevelop</programlisting> packages is not part of KDE 4.1 and <programlisting format="linespecific">kdewebdev</programlisting> is only partially available (no <emphasis>Quanta</emphasis>) in KDE 4.1, the KDE 3.5.10 versions of those packages are shipped. A <programlisting format="linespecific">kdegames3</programlisting> package containing the games not yet ported to KDE 4 is also available.</para><para>
- <ulink url="http://kde.org/announcements/announce-4.1.2.php">http://kde.org/announcements/announce-4.1.2.php</ulink>
- </para><para>KDE 4.1 is the latest release of KDE 4 and
- provides several new features, many usability improvements,
- and bugfixes over KDE 4.0, the first KDE 4 release series.
- This new release includes a folder view desktop applet
- (<firstterm>plasmoid</firstterm>), improvements to <emphasis>Dolphin</emphasis> and <emphasis>Konqueror</emphasis> and many new and improved applications. KDE 4.1.2 is a bugfix release from the KDE 4.1 release series.</para><para>Fedora 10 does <emphasis>not</emphasis> include the legacy KDE 3 Desktop. It does include a compatibility KDE 3 Development Platform, which can be used to build and run KDE 3 applications within KDE 4 or any other desktop environment. Refer to the <ulink url="http://fedoraproject.org/w/index.php?title=Docs/Beats/BackwardsCompatibility">Docs/Beats/BackwardsCompatibility</ulink> section for more details about what is included.</para><para>Fedora 10 includes a snapshot of <programlisting format="linespecific">knetworkmanager</programlisting>, which works with the prerelease of <emphasis>NetworkManager</emphasis> 0.7 in Fedora 10. As it was not considered ready for production use, the KDE Live images use <programlisting format="linespecific">n
m-applet</programlisting> from <programlisting format="linespecific">NetworkManager-gnome</programlisting> instead (as in Fedora 8 and 9). The <programlisting format="linespecific">gnome-keyring-daemon</programlisting> facility saves passwords for these encryption technologies. If you wish to try <programlisting format="linespecific">knetworkmanager</programlisting> can be installed from the repository.</para><para>As the native <emphasis>KWin</emphasis> window manager now optionally supports compositing and desktop effects, the KDE Live images no longer include <emphasis>Compiz/Beryl</emphasis> (since Fedora 9). The <emphasis>KWin</emphasis> compositing/effects mode is disabled by default, but can be enabled in <programlisting format="linespecific">systemsettings</programlisting>. <emphasis>Compiz</emphasis> (with KDE 4 integration) is available from the repository by installing the <programlisting format="linespecific">compiz-kde</programlisting> package.</para><section id
="sn-">
- <title>Enhancements </title>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis>Plasma</emphasis> is more mature and panel configuration has been extended. The new panel controller makes it easy to customize your panel providing direct visual feedback. The <emphasis>Plasma</emphasis> <command>folderview</command> applet provides a view of a directory and thus allows you to store files on the desktop. It is replaces other well known icons on the desktop.</para>
- </listitem>
- </itemizedlist>
- </section><section id="sn-">
- <title>Package and Application Changes </title>
- <itemizedlist>
- <listitem>
- <para> Fedora 10 ships <programlisting format="linespecific">kdepim</programlisting> 4.1.2 instead of 3.5.x.</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">libkipi</programlisting>, <programlisting format="linespecific">libkexiv2</programlisting>, and <programlisting format="linespecific">libkdcraw</programlisting> have been obsoleted by the KDE 4 versions in the <programlisting format="linespecific">kdegraphics</programlisting> package. Accordingly, <programlisting format="linespecific">kipi-plugins</programlisting>, <programlisting format="linespecific">digikam</programlisting>, and <programlisting format="linespecific">kphotoalbum</programlisting> have been updated to KDE 4 versions.</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">kpackagekit</programlisting>, a KDE frontend to PackageKit, is now available. (It may be made available as an update for Fedora 9 at a later time.)</para>
- </listitem>
- </itemizedlist><para>In addition, the following changes made since the Fedora 9 release, which have been backported to Fedora 9 updates, are also part of Fedora 10: </para>
- <itemizedlist>
- <listitem>
- <para> KDE has been upgraded from version 4.0.3 to 4.1.2.</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">qt</programlisting> and <programlisting format="linespecific">PyQt4</programlisting> have been upgraded from 4.3 to 4.4.</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">kdewebdev</programlisting>, <programlisting format="linespecific">kdevelop</programlisting>, <programlisting format="linespecific">kdegames3</programlisting>, and the KDE 3 backwards-compatibility libraries have been upgraded from KDE 3.5.9 to 3.5.10.</para>
- </listitem><listitem>
- <para>
- <emphasis>QtWebKit</emphasis> is now part of the <programlisting format="linespecific">qt</programlisting> package. The stand alone <programlisting format="linespecific">WebKit-qt</programlisting> package has been obsoleted.</para>
- </listitem><listitem>
- <para> The new package <programlisting format="linespecific">qgtkstyle</programlisting> contains a Qt 4 style using GTK+ for drawing, providing better integration of Qt 4 and KDE 4 applications into GNOME.</para>
- </listitem><listitem>
- <para> The <programlisting format="linespecific">phonon</programlisting> library, which was part of <programlisting format="linespecific">kdelibs</programlisting> in Fedora 9, is now a separate package. An optional <emphasis>GStreamer</emphasis> backend (<programlisting format="linespecific">phonon-backend-gstreamer</programlisting>) is now available, but the <emphasis>xine-lib</emphasis> backend, which is now packaged as <programlisting format="linespecific">phonon-backend-xine</programlisting>, is still the recommended default backend and is now required by the <programlisting format="linespecific">phonon</programlisting> package.</para>
- </listitem><listitem>
- <para> The <programlisting format="linespecific">kdegames3</programlisting> package no longer provides development support for the KDE 3 version of <programlisting format="linespecific">libkdegames</programlisting> because nothing in Fedora outside of <programlisting format="linespecific">kdegames3</programlisting> itself requires that library any longer.</para>
- </listitem><listitem>
- <para> The package <programlisting format="linespecific">okteta</programlisting> is now part of <programlisting format="linespecific">kdeutils</programlisting>.</para>
- </listitem><listitem>
- <para> The package <programlisting format="linespecific">dragonplayer</programlisting> is now part of <programlisting format="linespecific">kdemultimedia</programlisting>.</para>
- </listitem><listitem>
- <para> The program <programlisting format="linespecific">kaider</programlisting> has been renamed to <emphasis>Lokalize</emphasis> and is now part of <programlisting format="linespecific">kdesdk</programlisting>.</para>
- </listitem><listitem>
- <para> The package <programlisting format="linespecific">ksirk</programlisting> has been ported to KDE 4 and is now part of <programlisting format="linespecific">kdegames</programlisting>.</para>
- </listitem><listitem>
- <para> The package <programlisting format="linespecific">extragear-plasma</programlisting> has been renamed to <programlisting format="linespecific">kdeplasma-addons</programlisting>.</para>
- </listitem>
- </itemizedlist><para />
- </section>
- </section><section id="sn-">
- <title>Sugar Desktop </title>
- <para>The Sugar Desktop originated with the OLPC initiative. It allows for Fedora users and developers to do the following.</para>
- <itemizedlist>
- <listitem>
- <para> Build upon the collaborative environment.</para>
- </listitem><listitem>
- <para> Test out Sugar on an existing Fedora system by selecting the Sugar environment from their display manager.</para>
- </listitem><listitem>
- <para> Developers interested in working on the Sugar interface or writing activities can have a development platform without needing an XO laptop. </para>
- </listitem>
- </itemizedlist>
- </section><section id="sn-">
- <title>Web Browsers </title>
- <section id="sn-">
- <title>Enabling Flash Plugin </title>
- <para>Fedora includes <programlisting format="linespecific">swfdec</programlisting> and <programlisting format="linespecific">gnash</programlisting>, which are free and open source implementations of Flash. We encourage you to try either of them before seeking out Adobe's proprietary Flash Player plug-in software. The Adobe Flash Player plug-in uses a legacy sound framework that does not work correctly without additional support. Run the following command to enable this support:</para><para />
- <programlisting>
-su -c 'yum install libflashsupport'
-</programlisting>
- <para />
- <para>If you are using Flash 10, you do not need libflashsupport anymore as the usage of ALSA has been fixed in this version. </para>
- <para>Users of Fedora x86_64 must install the <programlisting format="linespecific">nspluginwrapper.i386</programlisting> package to enable the 32-bit Adobe Flash Player plug-in in <emphasis>Firefox</emphasis>, and the <programlisting format="linespecific">libflashsupport.i386</programlisting> package to enable sound from the plug-in.</para><para>Install the <programlisting format="linespecific">nspluginwrapper.i386</programlisting>, <programlisting format="linespecific">nspluginwrapper.x86_64</programlisting>, and <programlisting format="linespecific">libflashsupport.i386</programlisting> packages:</para><para />
- <programlisting>su -c 'yum install nspluginwrapper.{i386,x86_64} libflashsupport.i386'
-</programlisting>
- <para />
- <para>Install <programlisting format="linespecific">flash-plugin</programlisting> after <programlisting format="linespecific">nspluginwrapper.i386</programlisting> is installed:</para><para />
- <programlisting>su -c 'yum install libflashsupport'
-</programlisting>
- <para />
- <para>Run <programlisting format="linespecific">mozilla-plugin-config</programlisting> to register the flash plugin:</para><para />
- <programlisting>su -c "mozilla-plugin-config -i -g -v"
-</programlisting>
- <para />
- <para>Close all <emphasis>Firefox</emphasis> windows, and then relaunch <emphasis>Firefox</emphasis>. Type <emphasis>about:plugins</emphasis> in the URL bar to ensure the plugin is loaded.</para>
- </section>
- </section><section id="sn-">
- <title>Disabling PC Speaker </title>
- <para>PC speaker is enabled by default in Fedora. If you do not prefer this, there are two ways to circumvent the sounds:</para>
- <itemizedlist>
- <listitem>
- <para> Reduce its volume to a acceptable level or completely mute the PC speaker in <programlisting format="linespecific">alsamixer</programlisting> with the setting for <emphasis>PC Speak</emphasis>.</para>
- </listitem>
- </itemizedlist><itemizedlist>
- <listitem>
- <para> Disable the PC speaker system wide by running the following commands in a console.</para>
- </listitem>
- </itemizedlist><para />
- <programlisting>
-su -c 'modprobe -r pcspkr'
-su -c 'echo "install pcspkr :" >> /etc/modprobe.conf'
-</programlisting>
- <para />
- </section>
- </section>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
+
+<section lang="en" id="sn-Fedora_desktop">
+ <title>Fedora desktop</title>
+ <para>This section details changes that affect Fedora graphical
+ desktop users.</para>
+ <section id="sn-Better_webcam_support">
+ <title>Better webcam support</title>
+ <para>Fedora 10 comes with improved support for webcams.</para>
+ <para>This support follows on the improvements to the UVC driver
+ first introduced in Fedora 9 that added support for any webcam
+ with a Windows Vista compliant logo. Fedora 10 features a new
+ v4l2 version of <package>gspca</package>, a USB webcam driver
+ framework with support for many different USB webcam bridges and
+ sensors.</para>
+ <para>Userspace support for webcams has also been improved by adding
+ <systemitem class="library">libv4l</systemitem> and updating all
+ webcam using applications to use <systemitem
+ class="library">libv4l</systemitem>. This support makes these
+ applications understand the manufacturer specific and custom video
+ formats emitted by many webcams, especially by many of the webcams
+ supported by <package></package>gspca.</para>
+ <para>For a list of all webcams and applications where Fedora 10's
+ new webcam support has been tested refer to the <ulink
+ url="https://fedoraproject.org/wiki/Features/BetterWebcamSupport"/>.
+ For a list of all cams supported by the original version of
+ <package></package>gspca refer to the original gspca
+ website.</para>
+ <para><ulink url="http://mxhaard.free.fr/spca5xx.html"/></para>
+ <para>The v4l2 version of <package>gspca</package> in Fedora 10
+ supports all these webcams and more.</para>
+ </section>
+ <section id="sn-Plymouth_graphical_boot">
+ <title>Plymouth graphical boot</title>
+ <para>For information about the new graphical boot mode read <xref
+ linkend="sn-Fedora_10_boot-time"/>.</para>
+ </section>
+ <section id="sn-Echo_icon_theme">
+ <title>Echo icon theme</title>
+ <para>Echo is an icon theme developed for Fedora by the volunteer
+ Fedora Art community. Echo inherits the isometric perspective
+ from the classic Bluecurve theme while introducing a refreshing
+ new look. It follows the freedesktop.org theme specification. The
+ current version covers essential icons from the desktop menus and
+ applications. Future revisions will bring broader coverage.
+ </para>
+ <para>Currently, both GNOME and Xfce use the Echo icon theme by
+ default. KDE continues to use the Oxygen icon theme. The next
+ release of Fedora may introduce Echo by default for KDE for a
+ consistent look and feel across different desktop
+ environments.</para>
+ </section>
+ <section id="sn-Infrared_remote_support">
+ <title>Infrared remote support</title>
+ <para>New to Fedora 10 is the <package>gnome-lirc-properties</package>
+ package with a new graphical front-end for configuring LIRC to use
+ with applications supporting the protocol. For more information
+ refer to <xref linkend="sn-Infrared_remote_support"/>.</para>
+ <para>LIRC is routinely used in multimedia applications to implement
+ support for infrared remote controls, and using it in
+ <application>Rhythmbox</application> and <application>Totem</application>
+ should be as easy as plugging the remote receiver into your
+ computer, then selecting <guimenuitem>Auto-detect</guimenuitem> in the
+ <guimenu>Infrared Remote Control</guimenu> preferences. Refer to
+ the feature page for more information:</para>
+ <para>
+ <ulink
+ url="https://fedoraproject.org/wiki/Features/BetterLIRCSupport"/>
+ </para>
+ </section>
+ <section id="sn-Bluetooth_BlueZ_4.0">
+ <title>Bluetooth BlueZ 4.0</title>
+ <para>The Bluetooth support stack, called BlueZ (<ulink
+ url="http://www.bluez.org"/>,) has been updated to version 4.x
+ in Fedora 10. Most changes in this version are useful for
+ application developers, but users can notice the new, easier to
+ use wizard for setting up keyboards, mice, and other supported
+ Bluetooth devices. There is also the ability to turn-off the
+ Bluetooth adapter on most brands of laptops through the
+ preferences. This new version will also allow better support for
+ audio devices in the future, through PulseAudio.</para>
+ <para>Note that the default Bluetooth kernel driver was also
+ switched to <command>btusb</command>, which cuts down power
+ consumption compared to its predecessor
+ <command>hci_usb</command>.</para>
+ </section>
+ <section id="sn-GNOME">
+ <title>GNOME</title>
+ <para>This release features GNOME 2.24. For more details refer
+ to:</para>
+ <para>
+ <ulink
+ url="http://www.gnome.org/start/2.24/"/>
+ </para>
+ <section id="sn-Empathy_instant_messenger">
+ <title>Empathy instant messenger</title>
+ <para>
+ <application>Empathy</application> instant messenger is the new
+ default replacing <application>Pidgin</application> in this
+ release. It has support for multiple protocols including IRC,
+ XMPP(Jabber), Yahoo, MSN, and others via plugins. It also
+ supports video and voice in the XMPP protocol, with support for
+ other protocols under active development. Empathy uses the
+ <command>telepathy</command> framework that has a number of
+ additional plugins:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <command>telepathy-gabble</command> -
+ Jabber/XMPP plugin</para>
+ </listitem><listitem>
+ <para>
+ <command>telepathy-idle</command> -
+ IRC plugin</para>
+ </listitem><listitem>
+ <para>
+ <command>telepathy-butterfly</command>
+ - MSN plugin</para>
+ </listitem><listitem>
+ <para>
+ <command>telepathy-sofiasip</command>
+ - SIP plugin</para>
+ </listitem><listitem>
+ <para>
+ <command>telepathy-haze</command> -
+ Libpurple (Pidgin) library connection manager provides
+ support for other protocols such as Yahoo</para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ <application>Pidgin</application> continues to be available in the
+ Fedora software repository and is retained as the default for
+ users upgrading from previous releases of Fedora.
+ </para>
+ </section><section id="sn-GNOME_Display_Manager">
+ <title>GNOME Display Manager</title>
+ <para>The GNOME Display Manager (<systemitem
+ class="daemon">gdm</systemitem>) has been updated to the
+ latest upstream code, which is a complete rewrite driven by
+ Fedora developers. PolicyKit can be used to control shutdown and
+ reboot. The configuration tool <command>gdmsetup</command> is missing
+ currently, and is set to be replaced. For configuration changes,
+ refer to:</para>
+ <para>
+ <ulink
+ url="http://live.gnome.org/GDM/2.22/Configuration"/>
+ </para>
+ </section>
+ <section id="sn-Codec installation helper">
+ <title>Codec installation helper</title>
+ <para>The GStreamer codec installation helper
+ <command>codeina</command> was replaced by a PackageKit-based
+ solution for Fedora 10. When Totem, Rhythmbox, or another
+ GStreamer application require a plugin to read a film or song, a
+ PackageKit dialogue appears, allowing the user to search for the
+ necessary package in the configured
+ repositories.</para>
+ <para>More details are available on the feature page:</para>
+ <para>
+ <ulink
+ url="https://fedoraproject.org/wiki/Features/GStreamer_dependencies_in_RPM"/>
+ </para>
+ </section>
+ </section><section id="sn-KDE">
+ <title>KDE</title>
+ <para>This release features KDE 4.1.2. As the
+ <package>kdevelop</package> packages is not part of KDE 4.1 and
+ <package>kdewebdev</package> is only partially available (no
+ <application>Quanta</application>) in KDE 4.1, the KDE 3.5.10
+ versions of those packages are shipped. A
+ <package>kdegames3</package> package containing the games not yet
+ ported to KDE 4 is also available.</para>
+ <para>
+ <ulink
+ url="http://kde.org/announcements/announce-4.1.2.php"/>
+ </para>
+ <para>KDE 4.1 is the latest release of KDE 4 and provides
+ several new features, many usability improvements, and bugfixes
+ over KDE 4.0, the first KDE 4 release series. This new release
+ includes a folder view desktop applet
+ (<firstterm>Plasmoid</firstterm>), improvements to
+ <application>Dolphin</application> and <application>Konqueror</application>
+ and many new and improved applications. KDE 4.1.2 is a bugfix
+ release from the KDE 4.1 release series.</para>
+ <para>Fedora 10 does <emphasis>not</emphasis> include the legacy KDE
+ 3 Desktop. It does include a compatibility KDE 3 Development
+ Platform, which can be used to build and run KDE 3 applications
+ within KDE 4 or any other desktop environment. Refer to the <xref
+ linkend="sn-KDE_3_development_platform_and_libraries"/>
+ section for more details about what is
+ included.</para>
+ <para>Fedora 10 includes a snapshot of
+ <package>knetworkmanager</package>, which works with the
+ prerelease of <application>NetworkManager</application> 0.7 in
+ Fedora 10. As it was not considered ready for production use, the
+ KDE Live images use <command>nm-applet</command> from
+ <package>NetworkManager-gnome</package> instead (as in Fedora 8
+ and 9). The <systemitem
+ class="daemon">gnome-keyring-daemon</systemitem> facility saves
+ passwords for these encryption technologies. If you wish to try
+ <command>knetworkmanager</command> can be
+ installed from the repository.</para>
+ <para>As the native <application>KWin</application> window manager
+ now optionally supports compositing and desktop effects, the KDE
+ Live images no longer include
+ <application>Compiz/Beryl</application> (since Fedora 9). The
+ <application>KWin</application> compositing/effects mode is
+ disabled by default, but can be enabled in
+ <guimenuitem>systemsettings</guimenuitem>.
+ <application>Compiz</application> (with KDE 4 integration) is
+ available from the repository by installing the
+ <package>compiz-kde</package> package.</para>
+ <section id="sn-Enhancements">
+ <title>Enhancements</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <firstterm>Plasma</firstterm> is more mature and panel
+ configuration has been extended. The new panel controller
+ makes it easy to customize your panel providing direct
+ visual feedback. The Plasma <command>folderview</command>
+ applet provides a view of a directory and thus allows you to
+ store files on the desktop. It is replaces other well known
+ icons on the desktop.</para>
+ </listitem>
+ </itemizedlist>
+ </section><
+ section id="sn-Package_and_application_changes">
+ <title>Package and application changes</title>
+ <itemizedlist>
+ <listitem>
+ <para>Fedora 10 ships <package>kdepim</package> 4.1.2
+ instead of 3.5.x.</para>
+ </listitem><listitem>
+ <para>
+ <package>libkipi</package>,
+ <package>libkexiv2</package>, and
+ <package>libkdcraw</package> have been
+ obsoleted by the KDE 4 versions in the <package>kdegraphics</package>
+ package. Accordingly, <package>kipi-plugins</package>,
+ <package>digikam</package>, and
+ <package>kphotoalbum</package> have
+ been updated to KDE 4 versions.</para>
+ </listitem><listitem>
+ <para>
+ <package>kpackagekit</package>, a KDE
+ frontend to PackageKit, is now available. (It may be made
+ available as an update for Fedora 9 at a later time.)</para>
+ </listitem>
+ </itemizedlist><para>In addition, the following changes made since
+ the Fedora 9 release, which have been backported to Fedora 9
+ updates, are also part of Fedora 10:</para>
+ <itemizedlist>
+ <listitem>
+ <para>KDE has been upgraded from version 4.0.3 to
+ 4.1.2.</para>
+ </listitem><listitem>
+ <para>
+ <package>qt</package>
+ and <package>PyQt4</package> have been
+ upgraded from 4.3 to 4.4.</para>
+ </listitem><listitem>
+ <para>
+ <package>kdewebdev</package>,
+ <package>kdevelop</package>,
+ <package>kdegames3</package>, and the
+ KDE 3 backwards-compatibility libraries have been upgraded
+ from KDE 3.5.9 to 3.5.10.</para>
+ </listitem><listitem>
+ <para>
+ <emphasis>QtWebKit</emphasis> is now part of the
+ <package>qt</package> package. The stand alone
+ <package>WebKit-qt</package> package has been
+ obsoleted.</para>
+ </listitem><listitem>
+ <para>The new package <package>qgtkstyle</package> contains
+ a Qt 4 style using GTK+ for drawing, providing better
+ integration of Qt 4 and KDE 4 applications into
+ GNOME.</para>
+ </listitem><listitem>
+ <para>The <systemitem class="library">phonon</systemitem> library,
+ which was part of <package>kdelibs</package> in Fedora
+ 9, is now a separate package. An optional
+ <emphasis>GStreamer</emphasis> backend (<package>phonon-backend-gstreamer</package>)
+ is now available, but the <emphasis>xine-lib</emphasis>
+ backend, which is now packaged as <package>phonon-backend-xine</package>,
+ is still the recommended default backend and is now required
+ by the <package>phonon</package>
+ package.</para>
+ </listitem><listitem>
+ <para> The <package>kdegames3</package> package
+ no longer provides development support for the KDE 3 version
+ of <package>libkdegames</package> because
+ nothing in Fedora outside of <package>kdegames3</package> itself
+ requires that library any longer.</para>
+ </listitem><listitem>
+ <para> The package <package>okteta</package> is now part
+ of <package>kdeutils</package>.</para>
+ </listitem><listitem>
+ <para> The package <package>dragonplayer</package> is now
+ part of <package>kdemultimedia</package>.</para>
+ </listitem><listitem>
+ <para> The program <package>kaider</package> has been
+ renamed to <emphasis>Lokalize</emphasis> and is now part of
+ <package>kdesdk</package>.</para>
+ </listitem><listitem>
+ <para> The package <package>ksirk</package> has been
+ ported to KDE 4 and is now part of <package>kdegames</package>.</para>
+ </listitem><listitem>
+ <para> The package <package>extragear-plasma</package>
+ has been renamed to <package>kdeplasma-addons</package>.</para>
+ </listitem>
+ </itemizedlist>
</section>
- </article>
-</book>
+ </section><section id="sn-Sugar_Desktop">
+ <title>Sugar Desktop</title>
+ <para>The Sugar Desktop originated with the OLPC initiative. It
+ allows for Fedora users and developers to do the following.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Build upon the collaborative environment.</para>
+ </listitem><listitem>
+ <para>Test out Sugar on an existing Fedora system by selecting
+ the Sugar environment from their display manager.</para>
+ </listitem><listitem>
+ <para>Developers interested in working on the Sugar interface
+ or writing activities can have a development platform without
+ needing an XO laptop. </para>
+ </listitem>
+ </itemizedlist>
+ </section><section id="sn-Web_browsers">
+ <title>Web browsers</title>
+ <para />
+ <section id="sn-Enabling_Flash_plugin">
+ <title>Enabling Flash plugin</title>
+ <para>Fedora includes <command>swfdec</command> and
+ <command>gnash</command>, which are free and open source
+ implementations of Flash. We encourage you to try either of them
+ before seeking out Adobe's proprietary Flash Player plugin
+ software. The Adobe Flash Player plugin uses a legacy sound
+ framework that does not work correctly without additional support.
+ Run the following command to enable this support:</para>
+ <screen>
+ <userinput>su -c 'yum install libflashsupport'</userinput>
+ </screen>
+ <para>If you are using Flash 10, you do not need
+ <package>libflashsupport</package> anymore as the usage of ALSA
+ has been fixed in this version.
+ </para>
+ <para>Users of Fedora x86_64 must install the
+ <package>nspluginwrapper.i386</package> package to enable the
+ 32-bit Adobe Flash Player plug-in in
+ <application>Firefox</application>, and the
+ <package>libflashsupport.i386</package> package to enable sound
+ from the plugin.</para>
+ <para>Install the <package>nspluginwrapper.i386</package>,
+ <package>nspluginwrapper.x86_64</package>, and
+ <package>libflashsupport.i386</package> packages:</para>
+ <screen><userinput> <userinput>su -c 'yum install
+ nspluginwrapper.{i386,x86_64}
+ libflashsupport.i386'</userinput>
+ </screen>
+ <para>Install <package>flash-plugin</package> after
+ <package>nspluginwrapper.i386</package> is installed:</para>
+ <screen>
+ </userinput>su -c 'yum install libflashsupport'
+ </screen>
+ <para>Run <userinput>mozilla-plugin-config</userinput> to register
+ the flash plugin:</para>
+ <screen>
+ <userinput>su -c 'mozilla-plugin-config -i -g -v'</userinput>
+ </screen>
+ <para>Close all <application>Firefox</application> windows, and then
+ relaunch <application>Firefox</application>. Type
+ <userinput>about:plugins</userinput> in the URL bar to ensure the
+ plugin is loaded.</para>
+ </section>
+ <section id="sn-Disabling_PC_speaker">
+ <title>Disabling PC speaker</title>
+ <para>PC speaker is enabled by default in Fedora. If you do not
+ prefer this, there are two ways to circumvent the sounds:</para>
+ <itemizedlist>
+ <listitem>
+ <para>Reduce its volume to a acceptable level or completely
+ mute the PC speaker in <command>alsamixer</command> with the
+ setting for <menuchoice>PC Speak</menuchoice>.</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <listitem>
+ <para>Disable the PC speaker system wide by running the
+ following commands in a console:</para>
+ <screen>
+ <userinput>su -c 'modprobe -r pcspkr' su -c 'echo "install pcspkr :" >> /etc/modprobe.conf'</userinput>
+ </screen>
+ </listitem>
+ </itemizedlist>
+ </section>
+</section>
+
diff --git a/en-US/Fedora_live_images.xml b/en-US/Fedora_live_images.xml
deleted file mode 100644
index 480ee8b..0000000
--- a/en-US/Fedora_live_images.xml
+++ /dev/null
@@ -1,80 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
-
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/Live</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/Live</title>
- <section id="sn-">
- <title>Fedora Live Images </title>
- <para>The Fedora 10 release includes several Fedora Live ISO images in addition to the traditional installation images. These ISO images are bootable, and you can burn them to media and use them to try out Fedora. They also include a feature that allows you to install the Fedora Live image content to your hard drive for persistence and higher performance. </para>
- <section id="sn-">
- <title>Available Images </title>
- <para>For a complete list of current spins available, and instructions for using them, refer to:</para>
- <para>
- <ulink url="http://fedoraproject.org/wiki/CustomSpins">http://fedoraproject.org/wiki/CustomSpins</ulink>
- </para>
- </section><section id="sn-">
- <title>Usage Information </title>
- <para>To boot from the Fedora Live image, insert it into your computer and restart. To log in and use the desktop environment, enter the username <programlisting format="linespecific">fedora</programlisting>. There is no password on this account. The GNOME-based Fedora Live images automatically login after one minute, so users have time to select a preferred language. After logging in, if you wish to install the contents of the live image to your hard drive, click on the <emphasis>Install to Hard Drive</emphasis> icon on the desktop.</para>
- </section><section id="sn-">
- <title>Text Mode Installation </title>
- <para>You can do a text mode installation of the Fedora Live images using the <programlisting format="linespecific">liveinst</programlisting> command in the console.</para>
- </section><section id="sn-">
- <title>USB Booting </title>
- <para>Another way to use these Fedora Live images is to put them on a USB stick. To do this, you can use liveusb-creator graphical interface. You can use Add/Remove software, search and install liveusb-creator or install using yum:</para>
- <para />
- <programlisting>
-su -c 'yum install liveusb-creator'
-</programlisting>
- <para />
- <para>You can also use the command line interface, install the <programlisting format="linespecific">livecd-tools</programlisting> package from the repository. Then, run the <programlisting format="linespecific">livecd-iso-to-disk</programlisting> script:</para><para />
- <programlisting>/usr/bin/livecd-iso-to-disk /path/to/live.iso /dev/sdb1
-</programlisting>
- <para />
- <para>Replace <emphasis>/dev/sdb1</emphasis> with the partition where you want to put the image.</para><para>This is <emphasis>not</emphasis> a destructive process; any data you currently have on your USB stick <emphasis>is preserved</emphasis>.</para>
- </section><section id="sn-">
- <title>Persistent Home Directory </title>
- <para>Support for keeping a persistent <programlisting format="linespecific">/home</programlisting> with the rest of the system stateless has been added for Fedora 10. This includes support for encrypting <programlisting format="linespecific">/home</programlisting> to protect your system in the case where your USB stick is lost or stolen. To use this, download the live image and run the following command:</para><para />
- <programlisting>livecd-iso-to-disk --home-size-mb 512 /path/to/live.iso /dev/sdb1
-</programlisting>
- <para />
- <para>Replace <programlisting format="linespecific">/dev/sdb1</programlisting> with the partition where you want to put the image.</para><para>Replace <programlisting format="linespecific">512</programlisting> with the desired size in megabytes of the persistent <programlisting format="linespecific">/home</programlisting>. The <programlisting format="linespecific">livecd-iso-to-disk</programlisting> shell script is stored in the <programlisting format="linespecific">LiveOS</programlisting> directory at the top level of the CD image. The USB media must have sufficient free space for the Fedora Live image, plus the <programlisting format="linespecific">/home</programlisting>, plus any other data to be stored on the media. By default, this encrypts your data and prompts for a passphrase to use. If you want to have an unencrypted <programlisting format="linespecific">/home</programlisting>, then you can specify <programlisting format="linespecific">--unencrypted-hom
e</programlisting>.</para><para>Note that later runs of <programlisting format="linespecific">livecd-iso-to-disk</programlisting> preserve the <programlisting format="linespecific">/home</programlisting> that is created on the USB stick, continuing to use it even if you change your live image. </para>
- </section><section id="sn-">
- <title>Live USB Persistence </title>
- <para>Support for persistent changes with a Fedora Live image exists for Fedora 9 and later. The primary use case is booting from a Fedora Live image on a USB flash drive and storing changes to that same device. To do this, download the Fedora Live image and then run the following command:</para>
- <para />
- <programlisting>livecd-iso-to-disk --overlay-size-mb 512 /path/to/live.iso /dev/sdb1
-</programlisting>
- <para />
- <para>Replace <programlisting format="linespecific">/dev/sdb1</programlisting> with the partition where you want to put the image.</para><para>Replace <programlisting format="linespecific">512</programlisting> with the desired size in megabytes of the persistent data, or <programlisting format="linespecific">overlay</programlisting>. The <programlisting format="linespecific">livecd-iso-to-disk</programlisting> shell script is stored in the <programlisting format="linespecific">LiveOS</programlisting> directory at the top level of the CD image. The USB media must have sufficient free space for the Fedora Live image, plus the overlay, plus any other data to be stored on the media.</para>
- </section><section id="sn-">
- <title>Booting a Fedora Live Image Off of USB on Intel-based Apple Hardware </title>
- <para>Fedora 10 includes support for putting the live image onto a USB image and then booting it on Intel processor-based Apple hardware. Unlike for most x86 machines, this unfortunately requires reformatting the USB stick that you are using. To set up a stick for this, you can run</para>
- <para />
- <programlisting>/usr/bin/livecd-iso-to-disk --mactel /path/to/live.iso /dev/sdb1
-</programlisting>
- <para />
- <para>Replace <programlisting format="linespecific">/dev/sdb1</programlisting> with the partition where you want to put the image.</para><para>Note that all of the other arguments for the <programlisting format="linespecific">livecd-iso-to-disk</programlisting> tool as described above can be used here as well.</para>
- </section><section id="sn-">
- <title>Differences From a Regular Fedora Install </title>
- <para>The following items are different from a normal Fedora install with the Fedora Live images.</para>
- <itemizedlist>
- <listitem>
- <para> Fedora Live images provide a subset of packages available in the regular DVD image. Both connect to the same repository that has all the packages.</para>
- </listitem><listitem>
- <para> The SSH daemon <programlisting format="linespecific">sshd</programlisting> is disabled by default. The daemon is disabled because the default username in the Fedora Live images does not have a password. However, installation to hard disk prompts for creating a new username and password.</para>
- </listitem><listitem>
- <para> Fedora Live image installations do not allow any package selection or upgrade capability since they copy the entire file system from media or USB disks to the hard disk. After the installation is complete, and your system has been rebooted, you can add and remove packages as desired with the <emphasis>Add/Remove Packages</emphasis> tool, <programlisting format="linespecific">yum</programlisting>, or the other software management tools.</para>
- </listitem><listitem>
- <para> Fedora Live images do not work on <programlisting format="linespecific">i586</programlisting> architecture.</para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
diff --git a/en-US/Fedora_overview.xml b/en-US/Fedora_overview.xml
deleted file mode 100644
index 5ced28f..0000000
--- a/en-US/Fedora_overview.xml
+++ /dev/null
@@ -1,62 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
-
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/OverView</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/OverView</title>
- <section id="sn-">
- <title>Fedora Overview </title>
- <para>As always, Fedora continues to develop (<ulink url="http://www.fedoraproject.org/wiki/RedHatContributions)">http://www.fedoraproject.org/wiki/RedHatContributions)</ulink> and integrate the latest free and open source software (<ulink url="http://www.fedoraproject.org/wiki/Features).">http://www.fedoraproject.org/wiki/Features).</ulink> The following sections provide a brief overview of major changes from the last release of Fedora. For more details about other features that are included in Fedora 10, refer to their individual wiki pages that detail feature goals and progress:</para><para>
- <ulink url="http://www.fedoraproject.org/wiki/Releases/10/FeatureList">http://www.fedoraproject.org/wiki/Releases/10/FeatureList</ulink>
- </para><para>Throughout the release cycle, there are interviews with the developers behind key features giving out the inside story:</para>
- <para>
- <ulink url="http://www.fedoraproject.org/wiki/Interviews">http://www.fedoraproject.org/wiki/Interviews</ulink>
- </para><para>The following are major features for Fedora 10:</para>
- <itemizedlist>
- <listitem>
- <para> Wireless connection sharing enables ad hoc network sharing -- <ulink url="http://www.fedoraproject.org/wiki/Features/ConnectionSharing">http://www.fedoraproject.org/wiki/Features/ConnectionSharing</ulink>
- </para>
- </listitem><listitem>
- <para> Better setup and use of printers through improved management tools -- <ulink url="http://www.fedoraproject.org/wiki/Features/BetterPrinting">http://www.fedoraproject.org/wiki/Features/BetterPrinting</ulink>
- </para>
- </listitem><listitem>
- <para> Virtualization storage provisioning for local and remote connections now simplified -- <ulink url="http://www.fedoraproject.org/wiki/Features/VirtStorage">http://www.fedoraproject.org/wiki/Features/VirtStorage</ulink>
- </para>
- </listitem><listitem>
- <para> SecTool is a new security audit and intrusion detections system -- <ulink url="http://www.fedoraproject.org/wiki/Features/SecurityAudit">http://www.fedoraproject.org/wiki/Features/SecurityAudit</ulink>
- </para>
- </listitem><listitem>
- <para> RPM 4.6 is a major update to the powerful, flexible software management libraries -- <ulink url="http://www.fedoraproject.org/wiki/Features/RPM4.6">http://www.fedoraproject.org/wiki/Features/RPM4.6</ulink>
- </para>
- </listitem>
- </itemizedlist><para>Some other features in this release include: </para>
- <itemizedlist>
- <listitem>
- <para> Glitch free audio and better performance is achieved through a rewrite of the PulseAudio sound server to use timer-based audio scheduling -- <ulink url="http://www.fedoraproject.org/wiki/Features/GlitchFreeAudio">http://www.fedoraproject.org/wiki/Features/GlitchFreeAudio</ulink>
- </para>
- </listitem><listitem>
- <para> Improved webcam support -- <ulink url="http://www.fedoraproject.org/wiki/Features/BetterWebcamSupport">http://www.fedoraproject.org/wiki/Features/BetterWebcamSupport</ulink>
- </para>
- </listitem><listitem>
- <para> Better support for infrared remote controls makes them easier to connect and work with many applications -- <ulink url="http://www.fedoraproject.org/wiki/Features/BetterLIRCSupport">http://www.fedoraproject.org/wiki/Features/BetterLIRCSupport</ulink>
- </para>
- </listitem><listitem>
- <para> The paths <programlisting format="linespecific">/usr/local/sbin:/usr/sbin:/sbin</programlisting> have been added to the PATH for normal users, to simplify command-line administration tasks -- <ulink url="http://fedoraproject.org/wiki/Features/SbinSanity">http://fedoraproject.org/wiki/Features/SbinSanity</ulink>
- </para>
- </listitem><listitem>
- <para> The online account service provides applications with credentials for online accounts listed on <ulink url="http://online.gnome.org">http://online.gnome.org</ulink> or stored in GConf -- <ulink url="http://www.fedoraproject.org/wiki/Features/OnlineAccountsService">http://www.fedoraproject.org/wiki/Features/OnlineAccountsService</ulink>
- </para>
- </listitem>
- </itemizedlist><para />
- <para>Features for Fedora 10 tracked on the feature list page:</para>
- <para>
- <ulink url="http://www.fedoraproject.org/wiki/Releases/10/FeatureList">http://www.fedoraproject.org/wiki/Releases/10/FeatureList</ulink>
- </para>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
diff --git a/en-US/Feedback.xml b/en-US/Feedback.xml
index 6ef5241..6bb43e6 100644
--- a/en-US/Feedback.xml
+++ b/en-US/Feedback.xml
@@ -1,35 +1,43 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
-
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/Feedback</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/Feedback</title>
- <section id="sn-">
- <title>Feedback</title>
- <para>Thank you for taking the time to provide your comments, suggestions, and bug reports to the Fedora community; this helps improve the state of Fedora, Linux, and free software worldwide.</para>
- <section id="sn-">
- <title>Providing Feedback on Fedora Software </title>
- <para>To provide feedback on Fedora software or other system elements, please refer to <ulink url="http://fedoraproject.org/wiki/BugsAndFeatureRequests.">http://fedoraproject.org/wiki/BugsAndFeatureRequests.</ulink> A list of commonly reported bugs and known issues for this release is available from <ulink url="http://fedoraproject.org/wiki/Bugs/F10Common.">http://fedoraproject.org/wiki/Bugs/F10Common.</ulink>
- </para>
- </section><section id="sn-">
- <title>Providing Feedback on Release Notes </title>
- <para>If you feel these release notes could be improved in any way, you can provide your feedback directly to the beat writers. There are several ways to provide feedback, in order of preference:</para>
- <itemizedlist>
- <listitem>
- <para> If you have a Fedora account, edit content directly at <ulink url="http://fedoraproject.org/wiki/Docs/Beats.">http://fedoraproject.org/wiki/Docs/Beats.</ulink>
- </para>
- </listitem><listitem>
- <para> Fill out a bug request using this template: <ulink url="http://tinyurl.com/nej3u">http://tinyurl.com/nej3u</ulink> - <emphasis>This link is ONLY for feedback on the release notes themselves.</emphasis> Refer to the admonition above for details.</para>
- </listitem><listitem>
- <para> Email relnotes at fedoraproject.org.</para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
+
+<section lang="en" id="sn-Feedback">
+ <title>Feedback</title>
+ <para>Thank you for taking the time to provide your comments,
+ suggestions, and bug reports to the Fedora community; this helps
+ improve the state of Fedora, Linux, and free software
+ worldwide.</para>
+ <section id="sn-Providing_feedback_on_Fedora_software">
+ <title>Providing feedback on Fedora software</title>
+ <para>To provide feedback on Fedora software or other system
+ elements, please refer to <ulink
+ url="http://fedoraproject.org/wiki/BugsAndFeatureRequests"/>. A
+ list of commonly reported bugs and known issues for this release
+ is available from <ulink
+ url="http://fedoraproject.org/wiki/Bugs/F10Common">.
+ </para>
+ </section>
+ <section id="sn-Providing_feedback_on_release_notes">
+ <title>Providing feedback on release notes</title>
+ <para>If you feel these release notes could be improved in any way,
+ you can provide your feedback directly to the beat writers. There
+ are several ways to provide feedback, in order of
+ preference:</para>
+ <itemizedlist>
+ <listitem>
+ <para>If you have a Fedora account, edit content directly at
+ <ulink url="http://fedoraproject.org/wiki/Docs/Beats">.
+ </para>
+ </listitem><listitem>
+ <para>Fill out a bug request using this template: <ulink
+ url="http://tinyurl.com/nej3u"/> - <emphasis>This link is
+ ONLY for feedback on the release notes
+ themselves.</emphasis> Refer to the admonition above for
+ details.</para>
+ </listitem><listitem>
+ <para>Email <ulink
+ url="mailto:relnotes at fedoraproject.org"/>.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+</section>
diff --git a/en-US/File_servers.xml b/en-US/File_servers.xml
index 7d1a4f4..1f717fb 100644
--- a/en-US/File_servers.xml
+++ b/en-US/File_servers.xml
@@ -1,32 +1,27 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/FileServers</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/FileServers</title>
- <section id="sn-">
- <title>File Servers </title>
- <para>This section refers to file transfer and sharing servers. Refer to <ulink url="http://fedoraproject.org/wiki/Docs/Beats/WebServers">http://fedoraproject.org/wiki/Docs/Beats/WebServers</ulink> and <ulink url="http://fedoraproject.org/wiki/Docs/Beats/Samba">http://fedoraproject.org/wiki/Docs/Beats/Samba</ulink> for information on HTTP (Web) file transfer and Samba (Windows) file sharing services.</para><para>
- <para>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata contentwidth="35px" fileref="http://fedoraproject.org/w/uploads/a/a4/Idea.png" scalefit="1" width="35px" />
- </imageobject><caption>
- <para />
- </caption>
- </inlinemediaobject>
- </para><para>
- <emphasis>Maybe you know what should be on this page?</emphasis>
- <literallayout>
-</literallayout>The Fedora release notes are a collective effort of dozens of people. You can contribute by editing the wiki page that corresponds to this part of the release notes.</para>
- </para>
- </para><para>This section has not been updated for Fedora 10 by the beat writer (<ulink url="http://fedoraproject.org/wiki/Docs/Beats#Beat_Assignments).">http://fedoraproject.org/wiki/Docs/Beats#Beat_Assignments).</ulink> If you have some ideas or knowledge of what should be in this part of the release notes, you are encouraged to edit the wiki directly. Read <ulink url="https://fedoraproject.org/wiki/Docs/Beats/HowTo">https://fedoraproject.org/wiki/Docs/Beats/HowTo</ulink> for more information, then get an account and start writing.</para>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
+
+<section lang="en" id="sn-File_servers">
+ <title>File servers</title>
+ <para>This section refers to file transfer and sharing servers. Refer
+ to <ulink
+ url="http://fedoraproject.org/wiki/Docs/Beats/WebServers"/> and
+ <ulink url="http://fedoraproject.org/wiki/Docs/Beats/Samba"/> for
+ information on HTTP (Web) file transfer and Samba (Microsoft
+ Windows) file sharing services.</para><para>
+ <tip>
+ <title>Maybe you know what should be on this page?</title>
+ <para>The Fedora release notes are a collective effort of dozens
+ of people. You can contribute by editing the wiki page that
+ corresponds to this part of the release notes.</para>
+ </tip>
+ <para>This section has not been updated for Fedora 10 by the beat
+ writer (<ulink
+ url="http://fedoraproject.org/wiki/Docs/Beats#Beat_Assignments"/>.)
+ If you have some ideas or knowledge of what should be in this part
+ of the release notes, you are encouraged to edit the wiki directly.
+ Read <ulink url="https://fedoraproject.org/wiki/Docs/Beats/HowTo/">
+ for more information, then get an account and start
+ writing.</para>
+</section>
diff --git a/en-US/File_systems.xml b/en-US/File_systems.xml
index 010fd1a..c835a97 100644
--- a/en-US/File_systems.xml
+++ b/en-US/File_systems.xml
@@ -1,26 +1,27 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/FileSystems</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/FileSystems</title>
- <section id="sn-">
- <title>File Systems</title>
- <section id="sn-">
- <title>eCryptfs</title>
- <para> While Fedora 9 debuted encrypted fileystem support, F10 builds on that and fixes a number of problems that could have resulted in data corruption.</para>
- </section><section id="sn-">
- <title>EXT4</title>
- <para> Fedora 9 debuted a preview of ext4 support. F10 brings a fully ext4-compatible e2fsprogs. In addition Anaconda's partition screen has an ext4 filesystem option available if you launch the installer with the ext4 option. Fedora 10 also brings delayed allocation for ext4. However, ext4 in Fedora 10 doesn't currently support filesystems larger than 16 terabytes.</para>
- </section><section id="sn-">
- <title>XFS</title>
- <para>XFS is now a supported filesystem and an option with the the partitioning screen of Anaconda</para>
- </section>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
+
+<section lang="en" id="sn-File systems">
+ <title>File systems</title>
+ <section id="sn-eCryptfs">
+ <title>eCryptfs</title>
+ <para>While Fedora 9 debuted encrypted fileystem support, F10
+ builds on that and fixes a number of problems that could have
+ resulted in data corruption.</para>
+ </section>
+ <section id="sn-EXT4">
+ <title>EXT4</title>
+ <para>Fedora 9 debuted a preview of ext4 support. F10 brings a
+ fully ext4-compatible e2fsprogs. In addition Anaconda's partition
+ screen has an ext4 filesystem option available if you launch the
+ installer with the ext4 option. Fedora 10 also brings delayed
+ allocation for ext4. However, ext4 in Fedora 10 doesn't currently
+ support filesystems larger than 16 terabytes.</para>
+ </section>
+ <section id="sn-XFS">
+ <title>XFS</title>
+ <para>XFS is now a supported filesystem and an option with the the
+ partitioning screen of Anaconda</para>
+ </section>
+</section>
diff --git a/en-US/Games_and_entertainment.xml b/en-US/Games_and_entertainment.xml
index a749875..224848c 100644
--- a/en-US/Games_and_entertainment.xml
+++ b/en-US/Games_and_entertainment.xml
@@ -1,25 +1,28 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/Entertainment</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/Entertainment</title>
- <section id="sn-">
- <title>Games and Entertainment </title>
- <para>Fedora provides a selection of games that cover a variety of genres. Users can install a small package of games for GNOME (<programlisting format="linespecific">gnome-games</programlisting>) and KDE (<programlisting format="linespecific">kdegames</programlisting>). There are also many additional games that span every major genre available in the repositories.</para><para>The Fedora Project website features a section dedicated to games that details many of the available games, including overviews and installation instructions. For more information, refer to:</para>
- <para>
- <ulink url="http://fedoraproject.org/wiki/Games">http://fedoraproject.org/wiki/Games</ulink>
- </para><para>For a list of other games that are available for installation, select <emphasis>Applications > Add/Remove Software</emphasis>, or via the command line:</para><para />
- <programlisting> yum groupinfo "Games and Entertainment"</programlisting>
- <para />
- <para>For help using <programlisting format="linespecific">yum</programlisting> to install the assorted game packages, refer to the guide available at:</para><para>
- <ulink url="http://docs.fedoraproject.org/yum/">http://docs.fedoraproject.org/yum/</ulink>
- </para>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
+
+<section lang="en" id="sn-Games and entertainment">
+ <title>Games and entertainment</title>
+ <para>Fedora provides a selection of games that cover a variety of
+ genres. Users can install a small package of games for GNOME
+ (<package>gnome-games</package>) and KDE
+ (<package>kdegames</package>). There are also many additional games
+ that span every major genre available in the repositories.</para>
+ <para>The Fedora Project website features a section dedicated to games
+ that details many of the available games, including overviews and
+ installation instructions. For more information, refer to:</para>
+ <para>
+ <ulink url="http://fedoraproject.org/wiki/Games"/>
+ </para>
+ <para>For a list of other games that are available for installation,
+ select <guimenu>Applications</guimenu><guimenuitem>Add/Remove
+ Software</guimenuitem>, or via the command line:</para>
+ <screen>
+ <userinput>yum groupinfo "Games and Entertainment"</userinput>
+ </screen>
+ <para>For help using <command>yum</command> to install the assorted
+ game packages, refer to the guide available at:</para><para>
+ <ulink url="http://docs.fedoraproject.org/yum/"/>
+ </para>
+</section>
diff --git a/en-US/Hardware_overview.xml b/en-US/Hardware_overview.xml
index 49c5bf8..545b2b2 100644
--- a/en-US/Hardware_overview.xml
+++ b/en-US/Hardware_overview.xml
@@ -1,46 +1,64 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/HardwareOverview</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/HardwareOverview</title>
- <section id="sn-">
- <title>Hardware Overview </title>
- <para>Users often request that Fedora provide a <emphasis>hardware compatibility list</emphasis>, which we have carefully avoided doing. Why? It is a difficult and thankless task that is best handled by the community at large than by one little Linux distribution.</para><para>However, because of our stance against closed-source hardware drivers and the problems of binary firmware for hardware, there is some additional information the Fedora Project wants to provide Fedora users.</para>
- <section id="sn-">
- <title>Useful hardware information in these release notes </title>
- <itemizedlist>
- <listitem>
- <para> For 32-bit x86 - <ulink url="http://fedoraproject.org/w/index.php?title=Docs/Beats/ArchSpecific/x86"> Docs/Beats/ArchSpecific/x86</ulink>
- </para>
- </listitem><listitem>
- <para> For 64-bit x86 - <ulink url="http://fedoraproject.org/w/index.php?title=Docs/Beats/ArchSpecific/x86_64"> Docs/Beats/ArchSpecific/x86_64</ulink>
- </para>
- </listitem><listitem>
- <para> For PowerPC - <ulink url="http://fedoraproject.org/w/index.php?title=Docs/Beats/ArchSpecific/PPC"> Docs/Beats/ArchSpecific/PPC</ulink>
- </para>
- </listitem>
- </itemizedlist>
- </section><section id="sn-">
- <title>Hardware stance </title>
- <para>From <ulink url="http://fedoraproject.org/wiki/ForbiddenItems">[1]</ulink> :</para><itemizedlist>
- <listitem>
- <para> If it is proprietary, it cannot be included in Fedora.</para>
- </listitem><listitem>
- <para> If it is legally encumbered, it cannot be included in Fedora.</para>
- </listitem><listitem>
- <para> If it violates United States federal law, it cannot be included in Fedora.</para>
- </listitem>
- </itemizedlist>
- </section><section id="sn-">
- <title>What can you do? </title>
- <para>1. Get active. Tell your hardware vendors you only want free, open source drivers and firmware 1. Use your buying power and only purchase from hardware vendors that support their hardware with open drivers and firmware. Refer to <ulink url="http://www.fsf.org/campaigns/hardware.html">http://www.fsf.org/campaigns/hardware.html</ulink> for more information.</para>
- </section>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
+<section lang="en" id="sn-Hardware_overview">
+ <title>Hardware overview</title>
+ <para>Users often request that Fedora provide a <firstterm>hardware
+ compatibility list</firstterm> (<abbrev>HCL</abbrev>), which we have carefully avoided
+ doing. Why? It is a difficult and thankless task that is best
+ handled by the community at large than by one little Linux
+ distribution.</para>
+ <para>However, because of our stance against closed-source hardware
+ drivers and the problems of binary firmware for hardware, there is
+ some additional information the Fedora Project wants to provide
+ Fedora users.</para>
+ <section id="sn-Useful_hardware_information_in_these_release_notes">
+ <title>Useful hardware information in these release notes</title>
+ <itemizedlist>
+ <listitem>
+ <para>For 32-bit x86 - <xref
+ linkend="x86_specifics_for_Fedora"/>
+ </para>
+ </listitem><listitem>
+ <para>For 64-bit x86 - <xref
+ linkend="x86_64_specifics_for_Fedora"/>
+ </para>
+ </listitem><listitem>
+ <para>For PowerPC (<abbrev>PPC</abbrev>)- <xref
+ linkend="PPC_specifics_for_Fedora"/>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section><section id="sn-Hardware_stance">
+ <title>Hardware stance</title>
+ <para>From <ulink
+ url="http://fedoraproject.org/wiki/ForbiddenItems"/>:</para>
+ <itemizedlist>
+ <listitem>
+ <para>If it is proprietary, it cannot be included in
+ Fedora.</para>
+ </listitem><listitem>
+ <para>If it is legally encumbered, it cannot be included in
+ Fedora.</para>
+ </listitem><listitem>
+ <para>If it violates United States federal law, it cannot be
+ included in Fedora.</para>
+ </listitem>
+ </itemizedlist>
+ </section><section id="sn-What_can_you_do?">
+ <title>What can you do?</title>
+ <orderedlist>
+ <listitem>
+ <para>Get active. Tell your hardware vendors you only want
+ free, open source drivers and firmware</para>
+ </listitem>
+ <listitem>
+ <para>Use your buying power and only purchase from hardware
+ vendors that support their hardware with open drivers and
+ firmware. Refer to <ulink
+ url="http://www.fsf.org/campaigns/hardware.html"/>
+ for more information.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+</section>
diff --git a/en-US/How_are_Things_for_Developers.xml b/en-US/How_are_Things_for_Developers.xml
index e119274..0d100e4 100644
--- a/en-US/How_are_Things_for_Developers.xml
+++ b/en-US/How_are_Things_for_Developers.xml
@@ -2,24 +2,34 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<chapter id="blah-Test">
- <title>Test</title>
- <para>
- This is a test paragraph
- </para>
- <section id="blah-Test-Section_1_Test">
- <title>Section 1 Test</title>
- <para>
- Test of a section &TEST_ENTITY;
- </para>
- </section>
-
- <section id="blah-Test-Section_2_Test">
- <title>Section 2 Test</title>
- <para>
- Test of a section
- </para>
- </section>
+<chapter id="How_are_Things_for_Developers">
+ <title>How are Things for Developers</title>
+ <para/>
+
+<!-- Java.xml -->
+
+ <xi:include href="Java.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+<!-- Development.xml -->
+
+ <xi:include href="Development.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+<!-- Linux_kernel.xml -->
+
+ <xi:include href="Linux_kernel.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+<!-- Embedded.xml -->
+
+ <xi:include href="Embedded.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+<!-- KDE_3_development_platform_and_libraries.xml -->
+
+ <xi:include href="KDE_3_development_platform_and_libraries.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
</chapter>
diff --git a/en-US/International_language_support.xml b/en-US/International_language_support.xml
index c556185..9b57020 100644
--- a/en-US/International_language_support.xml
+++ b/en-US/International_language_support.xml
@@ -1,166 +1,277 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/I18n</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/I18n</title>
- <section id="sn-">
- <title>International Language Support </title>
- <para>This section includes information on language support under Fedora.</para>
- <itemizedlist>
- <listitem>
- <para> Localization (translation) of Fedora is coordinated by the Fedora Localization Project -- <ulink url="http://fedoraproject.org/wiki/L10N">http://fedoraproject.org/wiki/L10N</ulink>
- </para>
- </listitem><listitem>
- <para> Internationalization of Fedora is maintained by the Fedora I18n Project -- <ulink url="http://fedoraproject.org/wiki/I18N">http://fedoraproject.org/wiki/I18N</ulink>
- </para>
- </listitem>
- </itemizedlist><section id="sn-">
- <title>Language Coverage </title>
- <para>Fedora features a variety of software that is translated in many languages. For a list of languages refer to the translation statistics for the <emphasis>Anaconda</emphasis> module, which is one of the core software applications in Fedora.</para><itemizedlist>
- <listitem>
- <para>
- <ulink url="http://translate.fedoraproject.org/languages">http://translate.fedoraproject.org/languages</ulink>
- </para>
- </listitem><listitem>
- <para>
- <ulink url="http://translate.fedoraproject.org/module/anaconda">http://translate.fedoraproject.org/module/anaconda</ulink>
- </para>
- </listitem>
- </itemizedlist><section id="sn-">
- <title>Language Support Installation </title>
- <para> To install langpacks and additional language support from the <emphasis>Languages</emphasis> group, run this command:</para><para />
- <programlisting>su -c 'yum groupinstall <language>-support'
-</programlisting>
- <para />
- <para>In the command above, <programlisting format="linespecific"><language></programlisting> is one of <programlisting format="linespecific">assamese</programlisting>, <programlisting format="linespecific">bengali</programlisting>, <programlisting format="linespecific">chinese</programlisting>, <programlisting format="linespecific">gujarati</programlisting>, <programlisting format="linespecific">hindi</programlisting>, <programlisting format="linespecific">japanese</programlisting>, <programlisting format="linespecific">kannada</programlisting>, <programlisting format="linespecific">korean</programlisting>, <programlisting format="linespecific">malayalam</programlisting>, <programlisting format="linespecific">marathi</programlisting>, <programlisting format="linespecific">oriya</programlisting>, <programlisting format="linespecific">punjabi</programlisting>, <programlisting format="linespecific">sinhala</programlisting>, <programlisting format="linespecifi
c">tamil</programlisting>, <programlisting format="linespecific">telegu</programlisting>, <programlisting format="linespecific">thai</programlisting>, and so on.</para><para>SCIM users upgrading from earlier releases of Fedora are strongly urged to install <programlisting format="linespecific">scim-bridge-gtk</programlisting>, which works well with third-party C++ applications linked against older versions of <programlisting format="linespecific">libstdc++</programlisting>.</para>
- </section><section id="sn-">
- <title>Transifex </title>
- <para> Transifex is Fedora's online tool to facilitate contributing translations to projects hosted on remote and disparate version control systems. Many of the core packages use Transifex to receive translations from numerous contributors.</para>
- <para>
- <ulink url="https://fedorahosted.org/transifex/">https://fedorahosted.org/transifex/</ulink>
- </para><para>Through a combination of <ulink url="http://translate.fedoraproject.org/"> new web tools</ulink>, community growth, and better processes, translators can contribute directly to any upstream project through one translator-oriented web interface. Developers of projects with no existing translation community can easily reach out to Fedora's established community for translations. In turn, translators can reach out to numerous projects related to Fedora to easily contribute translations.</para><para>
- <ulink url="https://translate.fedoraproject.org/submit">https://translate.fedoraproject.org/submit</ulink>
- </para>
- </section>
- </section><section id="sn-">
- <title>Fonts </title>
- <para>Fonts for most languages are installed by default on the desktop to give good default language coverage.</para>
- <section id="sn-">
- <title>Default language for Han Unification </title>
- <para> When not using an Asian locale in GTK-based applications, Chinese characters (that is, Chinese Hanzi, Japanese Kanji, or Korean Hanja) may render with a mixture of Chinese, Japanese, and Korean fonts depending on the text. This happens when Pango does not have sufficient context to know which language is being used. The current default font configuration seems to prefer Chinese fonts. If you normally want to use Japanese or Korean say, you can tell Pango to use it by default by setting the <programlisting format="linespecific">PANGO_LANGUAGE</programlisting> environment variable. For example ...</para><para />
- <programlisting>export PANGO_LANGUAGE=ja</programlisting>
- <para />
- <para>... tells Pango rendering to assume Japanese text when it has no other indications.</para>
- </section><section id="sn-">
- <title>Japanese </title>
- <para>The <programlisting format="linespecific">fonts-japanese</programlisting> package has been renamed to <programlisting format="linespecific">japanese-bitmap-fonts</programlisting>.</para>
- </section><section id="sn-">
- <title>Khmer </title>
- <para> Khmer OS Fonts <programlisting format="linespecific">khmeros-fonts</programlisting> have been added to Fedora for Khmer coverage in this release.</para>
- </section><section id="sn-">
- <title>Korean </title>
- <para> The <programlisting format="linespecific">un-core-fonts</programlisting> packages replaces <programlisting format="linespecific">baekmuk-ttf-fonts</programlisting> as the new Hangul default fonts.</para>
- </section><section id="sn-">
- <title>Complete list of changes </title>
- <para>All fonts changes are listed on their dedicated page:</para>
- <para>
- <ulink url="http://fedoraproject.org/wiki/Fonts_inclusion_history#F10">http://fedoraproject.org/wiki/Fonts_inclusion_history#F10</ulink>
- </para><para>
- <para>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata contentwidth="35px" fileref="http://fedoraproject.org/w/uploads/a/a4/Idea.png" scalefit="1" width="35px" />
- </imageobject><caption>
- <para />
- </caption>
- </inlinemediaobject>
- </para><para>
- <emphasis>Fonts in Fedora Linux</emphasis>
- <literallayout>
-</literallayout>The <ulink url="http://fedoraproject.org/w/index.php?title=Fonts_SIG">Fonts SIG</ulink> takes loving care of <ulink url="http://fedoraproject.org/w/index.php?title=Fonts">Fedora Linux fonts</ulink>. Please <ulink url="http://fedoraproject.org/w/index.php?title=Joining_the_Fonts_SIG">join</ulink> this special interest group if you are interested in <ulink url="http://fedoraproject.org/w/index.php?title=Fonts_and_text-related_creative_tasks">creating</ulink>, <ulink url="http://fedoraproject.org/w/index.php?title=Fonts_and_text_quality_assurance">improving</ulink>, <ulink url="http://fedoraproject.org/w/index.php?title=Fonts_packaging">packaging</ulink>, or just <ulink url="http://fedoraproject.org/w/index.php?title=Font_wishlist">suggesting</ulink> a font. Any help will be appreciated.</para>
- </para>
- </para>
- </section>
- </section><section id="sn-">
- <title>Input Methods </title>
- <para> There is a new <programlisting format="linespecific">yum</programlisting> group called <programlisting format="linespecific">input-methods</programlisting> and <emphasis>Input Methods</emphasis> for many languages are now installed by default. This allows turning on the default input method system and immediately having the standard input methods for most languages available. It also brings normal installs in line with Fedora Live.</para><section id="sn-">
- <title>im-chooser and imsettings </title>
- <para> It is now possible to start and stop the use of Input Methods during runtime thanks to the <programlisting format="linespecific">imsettings</programlisting> framework. The <programlisting format="linespecific">GTK_IM_MODULE</programlisting> environment variable is no longer needed by default but can still be used to override the <programlisting format="linespecific">imsettings</programlisting>.</para><para>Input Methods only start by default on desktops running in an Asian locale. The current locale list is: <programlisting format="linespecific">as</programlisting>, <programlisting format="linespecific">bn</programlisting>, <programlisting format="linespecific">gu</programlisting>, <programlisting format="linespecific">hi</programlisting>, <programlisting format="linespecific">ja</programlisting>, <programlisting format="linespecific">kn</programlisting>, <programlisting format="linespecific">ko</programlisting>, <programlisting format="linespecific">ml<
/programlisting>, <programlisting format="linespecific">mr</programlisting>, <programlisting format="linespecific">ne</programlisting>, <programlisting format="linespecific">or</programlisting>, <programlisting format="linespecific">pa</programlisting>, <programlisting format="linespecific">si</programlisting>, <programlisting format="linespecific">ta</programlisting>, <programlisting format="linespecific">te</programlisting>, <programlisting format="linespecific">th</programlisting>, <programlisting format="linespecific">ur</programlisting>, <programlisting format="linespecific">vi</programlisting>, <programlisting format="linespecific">zh</programlisting>. Use <programlisting format="linespecific">im-chooser</programlisting> via <emphasis>System > Preferences > Personal > Input Method</emphasis> to enable or disable Input Method usage on your desktop.</para>
- </section><section id="sn-">
- <title>ibus </title>
- <para> Fedora 10 includes <programlisting format="linespecific">ibus</programlisting>, a new input method system that has been developed to overcome some of the limitations of <programlisting format="linespecific">scim</programlisting>. It may become the default input method system in Fedora 11.</para><para>
- <ulink url="http://code.google.com/p/ibus">http://code.google.com/p/ibus</ulink>
- </para><para>It already provides a number of input method engines and immodules:</para>
- <itemizedlist>
- <listitem>
- <para>
- <programlisting format="linespecific">ibus-anthy</programlisting> (Japanese)</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">ibus-chewing</programlisting> (Traditional Chinese)</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">ibus-gtk</programlisting> (GTK immodule)</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">ibus-hangu</programlisting>l (Korean)</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">ibus-m17</programlisting>n (Indic and many other languages)</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">ibus-pinyi</programlisting>n (Simplified Chinese)</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">ibus-q</programlisting>t (Qt immodule)</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">ibus-tabl</programlisting>e (Chinese, etc)</para>
- </listitem>
- </itemizedlist><para>We encourage people to install <programlisting format="linespecific">ibus</programlisting>, test it for their language, and report any problems.</para>
- </section><section id="sn-">
- <title>Indic Onscreen Keyboard </title>
- <para> Fedora 10 includes <programlisting format="linespecific">iok</programlisting>, an onscreen virtual keyboard for Indian languages, which allows input using Inscript keymap layouts and other 1:1 key mappings. For more information refer to the homepage:</para><para>
- <ulink url="http://fedorahosted.org/iok.">http://fedorahosted.org/iok.</ulink>
- </para>
- </section>
- </section>
- </section><section id="sn-">
- <title>Indic collation support </title>
- <para> Fedora 10 includes sorting support for Indic languages. This support fixes listing and order of menus in these languages, representing them in sorted order and making it easy to find desired elements.</para>
- <para>These languages are covered by this support:</para>
- <itemizedlist>
- <listitem>
- <para> Marathi</para>
- </listitem><listitem>
- <para> Hindi</para>
- </listitem><listitem>
- <para> Gujarati </para>
- </listitem><listitem>
- <para> Kashmiri</para>
- </listitem><listitem>
- <para> Sindhi</para>
- </listitem><listitem>
- <para> Maithili</para>
- </listitem><listitem>
- <para> Nepali</para>
- </listitem><listitem>
- <para> Konkani</para>
- </listitem><listitem>
- <para> Telugu</para>
- </listitem><listitem>
- <para> Kannada</para>
- </listitem><listitem>
- <para> Punjabi</para>
- </listitem>
- </itemizedlist>
- </section>
+
+<section lang="en" id="sn-International_language_support">
+ <title>International language support</title>
+ <para>This section includes information on language support under
+ Fedora.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Localization (translation) of Fedora is coordinated by the
+ Fedora Localization Project -- <ulink
+ url="http://fedoraproject.org/wiki/L10N"/>
+ </para>
+ </listitem><listitem>
+ <para>Internationalization of Fedora is maintained by the Fedora
+ I18n Project -- <ulink
+ url="http://fedoraproject.org/wiki/I18N"/>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <section id="sn-Language_coverage">
+ <title>Language coverage</title>
+ <para>Fedora features a variety of software that is translated in
+ many languages. For a list of languages refer to the translation
+ statistics for the <application>Anaconda</application> module,
+ which is one of the core software applications in Fedora.</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://translate.fedoraproject.org/languages"/>
+ </para>
+ </listitem><listitem>
+ <para>
+ <ulink
+ url="http://translate.fedoraproject.org/module/anaconda"/>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <section id="sn-Language_support_installation">
+ <title>Language support installation</title>
+ <para>To install langpacks and additional language support from
+ the <menuchoice>Languages</menuchoice> group, run this
+ command:</para>
+ <screen>
+ <userinput>su -c 'yum groupinstall
+ <language>-support'</userinput>
+ </screen>
+ <para>In the command above,
+ <userinput><language></userinput> is one of
+ <userinput>assamese</userinput>, <userinput>bengali</userinput>,
+ <userinput>chinese</userinput>, <userinput>gujarati</userinput>,
+ <userinput>hindi</userinput>, <userinput>japanese</userinput>,
+ <userinput>kannada</userinput>, <userinput>korean</userinput>,
+ <userinput>malayalam</userinput>,
+ <userinput>marathi</userinput>, <userinput>oriya</userinput>,
+ <userinput>punjabi</userinput>, <userinput>sinhala</userinput>,
+ <userinput>tamil</userinput>, <userinput>telegu</userinput>,
+ <userinput>thai</userinput>, and so on.</para>
+ <para>SCIM users upgrading from earlier releases of Fedora are
+ strongly urged to install <package>scim-bridge-gtk</package>,
+ which works well with third-party C++ applications linked
+ against older versions of <package>libstdc++</package>.</para>
</section>
- </article>
-</book>
\ No newline at end of file
+ <section id="sn-Transifex">
+ <title>Transifex</title>
+ <para>Transifex is Fedora's online tool to facilitate contributing
+ translations to projects hosted on remote and disparate version
+ control systems. Many of the core packages use Transifex to
+ receive translations from numerous contributors.</para>
+ <para>
+ <ulink url="https://fedorahosted.org/transifex/"/>
+ </para>
+ <para>Through a combination of new web tools (<ulink
+ url="http://translate.fedoraproject.org/"/>), community
+ growth, and better processes, translators can contribute
+ directly to any upstream project through one translator-oriented
+ web interface. Developers of projects with no existing
+ translation community can easily reach out to Fedora's
+ established community for translations. In turn, translators can
+ reach out to numerous projects related to Fedora to easily
+ contribute translations.</para>
+ <para>
+ <ulink url="https://translate.fedoraproject.org/submit"/>
+ </para>
+ </section>
+ </section>
+ <section id="sn-Fonts">
+ <title>Fonts</title>
+ <para>Fonts for most languages are installed by default on the
+ desktop to give good default language coverage.</para>
+ <section id="sn-Default_language_for_Han_Unification">
+ <title>Default language for Han Unification</title>
+ <para>When not using an Asian locale in GTK-based applications,
+ Chinese characters (that is, Chinese Hanzi, Japanese Kanji, or
+ Korean Hanja) may render with a mixture of Chinese, Japanese,
+ and Korean fonts depending on the text. This happens when Pango
+ does not have sufficient context to know which language is being
+ used. The current default font configuration seems to prefer
+ Chinese fonts. If you normally want to use Japanese or Korean
+ say, you can tell Pango to use it by default by setting the
+ <envar>PANGO_LANGUAGE</envar> environment variable. For example
+ ...</para><para />
+ <screen>
+ <envar>export PANGO_LANGUAGE=ja</envar>
+ </screen>
+ <para>... tells Pango rendering to assume Japanese text when it
+ has no other indications.</para>
+ </section>
+ <section id="sn-Japanese">
+ <title>Japanese</title>
+ <para>The <package>fonts-japanese</package> package has been
+ renamed to <package>japanese-bitmap-fonts</package>.</para>
+ </section>
+ <section id="sn-Khmer">
+ <title>Khmer</title>
+ <para>Khmer OS Fonts <package>khmeros-fonts</package> have been
+ added to Fedora for Khmer coverage in this release.</para>
+ </section>
+ <section id="sn-Korean">
+ <title>Korean</title>
+ <para>The <package>un-core-fonts</package> packages replaces
+ <package>baekmuk-ttf-fonts</package> as the new Hangul default
+ fonts.</para>
+ </section>
+ <section id="sn-Complete_list_of_changes">
+ <title>Complete list of changes</title>
+ <para>All fonts changes are listed on their dedicated page:</para>
+ <para>
+ <ulink
+ url="http://fedoraproject.org/wiki/Fonts_inclusion_history#F10"/>
+ </para>
+ <tip>
+ <title>Fonts in Fedora Linux</title>
+ <para>The Fonts SIG (<ulink
+ url="http://fedoraproject.org/wiki/Fonts_SIG"/>) takes
+ loving care of Fedora Linux fonts (<ulink
+ url="http://fedoraproject.org/wiki/Fonts"/>). Please join
+ this special interest group if you are interested in creating,
+ improving, packaging, or just suggesting a font. Any help is
+ appreciated.</para>
+ <para><ulink
+ url="http://fedoraproject.org/wiki/Joining_the_Fonts_SIG"/>
+ </para>
+ <para><ulink
+ url="http://fedoraproject.org/wiki/Fonts_and_text-related_creative_tasks"/>
+ </para>
+ <para><ulink
+ url="http://fedoraproject.org/wiki/Fonts_and_text_quality_assurance"/></para>
+ <para><ulink
+ url="http://fedoraproject.org/wiki/Fonts_packaging"></para>
+ <para><ulink
+ url="http://fedoraproject.org/wiki/Font_wishlist"></para>
+ </tip>
+ </section>
+ </section>
+ <section id="sn-Input_Methods">
+ <title>Input Methods</title>
+ <para>There is a new <command>yum</command> group called
+ <package>input-methods</package> and <firstterm>Input
+ Methods</firstterm> for many languages are now installed by
+ default. This allows turning on the default input method system
+ and immediately having the standard input methods for most
+ languages available. It also brings normal installs in line with
+ Fedora Live.</para>
+ <section id="sn-im-chooser_and_imsettings">
+ <title>im-chooser and imsettings</title>
+ <para>It is now possible to start and stop the use of Input
+ Methods during runtime thanks to the
+ <command>imsettings</command> framework. The
+ <envar>GTK_IM_MODULE</envar> environment variable is no longer
+ needed by default but can still be used to override the
+ <command>imsettings</command>.</para>
+ <para>Input Methods only start by default on desktops running in
+ an Asian locale. The current locale list is:
+ <option>as</option>, <option>bn</option>, <option>gu</option>,
+ <option>hi</option>, <option>ja</option>, <option>kn</option>,
+ <option>ko</option>, <option>ml</option>, <option>mr</option>,
+ <option>ne</option>, <option>or</option>, <option>pa</option>,
+ <option>si</option>, <option>ta</option>, <option>te</option>,
+ <option>th</option>, <option>ur</option>, <option>vi</option>,
+ <option>zh</option>. Use <command>im-chooser</command> via
+ <keycombo>
+ <keycap>System</keycap>
+ <keycap>Preferences</keycap>
+ <keycap>Personal</keycap>
+ <keycap>Input Method</keycap></keycombo> to enable or disable
+ Input Method usage on your desktop.</para>
+ </section>
+ <section id="sn-New_ibus_input_method_system">
+ <title>New <command>ibus</command> input method system</title>
+ <para>Fedora 10 includes <command>ibus</command>, a new input
+ method system that has been developed to overcome some of the
+ limitations of <command>scim</command>. It may become the
+ default input method system in Fedora 11.</para>
+ <para>
+ <ulink url="http://code.google.com/p/ibus"/>
+ </para>
+ <para>It already provides a number of input method engines and
+ immodules:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <option>ibus-anthy</option> (Japanese)</para>
+ </listitem><listitem>
+ <para>
+ <option>ibus-chewing</option> (Traditional Chinese)</para>
+ </listitem><listitem>
+ <para>
+ <option>ibus-gtk</option> (GTK immodule)</para>
+ </listitem><listitem>
+ <para>
+ <option>ibus-hangul</option> (Korean)</para>
+ </listitem><listitem>
+ <para>
+ <option>ibus-m17n</option> (Indic and many other
+ languages)</para>
+ </listitem><listitem>
+ <para>
+ <option>ibus-pinyin</option> (Simplified Chinese)</para>
+ </listitem><listitem>
+ <para>
+ <option>ibus-qt</option> (Qt immodule)</para>
+ </listitem><listitem>
+ <para>
+ <option>ibus-table</option> (Chinese, etc)</para>
+ </listitem>
+ </itemizedlist>
+ <para>We encourage people to install <command>ibus</command>, test
+ it for their language, and report any problems.</para>
+ </section>
+ </section>
+ <section id="sn-Indic_onscreen_keyboard">
+ <title>Indic onscreen keyboard</title>
+ <para> Fedora 10 includes <command>iok</command>, an onscreen
+ virtual keyboard for Indian languages, which allows input using
+ Inscript keymap layouts and other 1:1 key mappings. For more
+ information refer to the homepage:</para>
+ <para>
+ <ulink url="http://fedorahosted.org/iok"/>
+ </para>
+ </section>
+ <section id="sn-Indic_collation_support">
+ <title>Indic collation support</title>
+ <para>Fedora 10 includes sorting support for Indic languages. This
+ support fixes listing and order of menus in these languages,
+ representing them in sorted order and making it easy to find
+ desired elements.</para>
+ <para>These languages are covered by this support:</para>
+ <itemizedlist>
+ <listitem>
+ <para>Marathi</para>
+ </listitem><listitem>
+ <para>Hindi</para>
+ </listitem><listitem>
+ <para>Gujarati </para>
+ </listitem><listitem>
+ <para>Kashmiri</para>
+ </listitem><listitem>
+ <para>indhi</para>
+ </listitem><listitem>
+ <para>Maithili</para>
+ </listitem><listitem>
+ <para>Nepali</para>
+ </listitem><listitem>
+ <para>Konkani</para>
+ </listitem><listitem>
+ <para>Telugu</para>
+ </listitem><listitem>
+ <para>Kannada</para>
+ </listitem><listitem>
+ <para>Punjabi</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+</section>
+
diff --git a/en-US/Introduction_to_Fedora_Project_and_technical_release_notes.xml b/en-US/Introduction_to_Fedora_Project_and_technical_release_notes.xml
index 152f986..cbdb1ac 100644
--- a/en-US/Introduction_to_Fedora_Project_and_technical_release_notes.xml
+++ b/en-US/Introduction_to_Fedora_Project_and_technical_release_notes.xml
@@ -1,36 +1,28 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
+
+<section lang="en" id="sn-Introduction_to_Fedora_Project_and_technical_release_notes">
+ <title>Introduction to Fedora Project and technical release
+ notes</title>
+ <para>The Fedora Project is an openly-developed project designed by
+ Red Hat, open for general participation, led by a meritocracy, and
+ following a set of project objectives. The results from this project
+ include Fedora Core, which is a complete, general-purpose operating
+ system built exclusively from open source software.</para>
+ <note>
+ <title>Fedora is a community supported project</title>
+ <para>Fedora is not a commercially supported product of Red Hat,
+ Inc.</para>
+ </note>
+ <para>For more information, refer to <xref linkend="Fedora_Project"/>.</para>
+ <para>Additional important information about this release may be made
+ available at <ulink
+ url="http://docs.fedoraproject.org/release-notes/"/>. Users are
+ advised to check this link regularly for updates.</para>
+ <para>For reporting errors or other requests about these release
+ notes, file a bug report using this pre-filled bugzilla template:
+ <ulink
+ url="http://tinyurl.com/byvk2"/>
+ </para>
+</section>
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/Introduction</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/Introduction</title>
- <section id="sn-">
- <title>Introduction to Fedora Project and Technical Release Notes </title>
- <para>The Fedora Project is an openly-developed project designed by Red Hat, open for general participation, led by a meritocracy, and following a set of project objectives. The results from this project include Fedora Core, which is a complete, general-purpose operating system built exclusively from open source software.</para>
- <para>
- <para>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata contentwidth="35px" fileref="http://fedoraproject.org/w/uploads/c/cc/Note.png" scalefit="1" width="35px" />
- </imageobject><caption>
- <para />
- </caption>
- </inlinemediaobject>
- </para><para>
- <emphasis> Fedora Core is a community supported project.</emphasis>
- <literallayout>
-</literallayout>
- </para>
- </para>
- </para><para>Fedora Core is not a commercially supported product of Red Hat, Inc..</para>
- <para>For more information, refer to the <ulink url="http://fedoraproject.org/w/index.php?title=Docs/Beats/Overview"> Overview</ulink> .</para><para>Additional important information about this release may be made available at <ulink url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink> . Users are advised to check this link regularly for updates.</para><para>For reporting errors or other requests about these release notes, file a bug report using this pre-filled bugzilla template: <ulink url="http://tinyurl.com/byvk2">http://tinyurl.com/byvk2</ulink>
- </para>
- </section>
- </section>
- </article>
-</book>
\ No newline at end of file
diff --git a/en-US/Java.xml b/en-US/Java.xml
index 2d05c54..b0348bb 100644
--- a/en-US/Java.xml
+++ b/en-US/Java.xml
@@ -1,60 +1,141 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?xml-stylesheet href="http://www.informatik.fh-wiesbaden.de/~werntges/home_t/proj/dbkcss102/wysiwygdocbook1.02/driver.css" type="text/css"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/Java</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/Java</title>
- <section id="sn-">
- <title>Java</title>
- <section id="sn-">
- <title>Best of breed free software Java implementation </title>
- <para>Fedora includes multiple best of breed free software Java(TM) implementations, obtained through active adoption of innovative technology integrations produced by Fedora and others within upstream projects. The implementations integrated into Fedora are based on OpenJDK (<ulink url="http://openjdk.java.net/)">http://openjdk.java.net/)</ulink> and the IcedTea GNU/Linux distribution integration project (<ulink url="http://icedtea.classpath.org/),">http://icedtea.classpath.org/),</ulink> or based on alternatives such as the GNU Compiler for Java (GCJ - <ulink url="http://gcc.gnu.org/java)">http://gcc.gnu.org/java)</ulink> and the GNU Classpath core class libraries (<ulink url="http://www.gnu.org/software/classpath/).">http://www.gnu.org/software/classpath/).</ulink> All Fedora innovations are pushed upstream to get the widest possible integration of the technologies in general Java implementations.</para><para>The implementation of OpenJDK 6 included in Fedora 10
uses the HotSpot virtual machine runtime compiler on x86, x86_64, and SPARC. On PowerPC (PPC) it uses the zero interpreter, which is slower. On all architectures an alternative implementation based on GCJ and GNU Classpath is included that includes an ahead-of-time compiler to produce native binaries.</para>
- <para>Fedora binaries for selected architectures (currently only x86 and x86_64 based on OpenJDK) are tested against the Java Compatibility Kit (JCK) by Red Hat to guarantee 100% compatibility with the Java Specification (JDK 1.6 at this time).</para>
- </section><section id="sn-">
- <title>Handling Java Applets and Web Start Applications </title>
- <para>In Fedora 10 <programlisting format="linespecific">gcjwebplugin</programlisting> has been replaced by <programlisting format="linespecific">IcedTeaPlugin</programlisting> that runs untrusted applets safely in a Web browser and works on any architecture. You can see which Applet Plugin is installed by typing <programlisting format="linespecific">about:plugins</programlisting> in Firefox. The new plugin adds support for the JavaScript bridge (LiveConnect) that was missing from earlier versions. For more details on "bytecode-to-JavaScript bridge (LiveConnect)", refer to the bug report:</para><para>
- <ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=304021">https://bugzilla.redhat.com/show_bug.cgi?id=304021</ulink>
- </para><para>Feedback on the security policy is very appreciated. If you suspect the security policy may be too restrictive to enable restricted applets, run the <programlisting format="linespecific">firefox -g</programlisting> command in a terminal window to see what is being restricted, then grant the restricted permission in the <programlisting format="linespecific">/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/security/java.policy</programlisting> file. If you then file a bug report, your exception could end up in the packaged security policy and you won't have to hack the policy file in the future.</para><para>Experimental Web Start (<programlisting format="linespecific">javaws</programlisting>) support via NetX has been added to the IcedTea repository. When a Java Network Launching Protocol (<programlisting format="linespecific">.jnlp</programlisting>) file is embedded on a web page you can open it with the IcedTea Web Start (<programlisting format="linesp
ecific">/usr/bin/javaws</programlisting>).</para><para>
- <ulink url="http://jnlp.sourceforge.net/">http://jnlp.sourceforge.net/</ulink> -- NetX</para>
- </section><section id="sn-">
- <title>New integration with other Fedora technologies </title>
- <para>Through the IcedTea project OpenJDK has been integrated with several new technologies that are also part of Fedora 10.</para>
- <section id="sn-">
- <title>VisualVM integration through the NetBeans framework </title>
- <para>VisualVM (<programlisting format="linespecific">jvisualvm</programlisting>) provides a graphical overview of any local or remotely running Java application, letting you monitor all running threads, classes, and objects allocated by the application by taking thread dumps, heap dumps, and other lightweight profiling tools.</para>
- </section><section id="sn-">
- <title>PulseAudio integration for javax.sound </title>
- <para>PulseAudio integrations provides all the benefits of PulseAudio to any java application using the <programlisting format="linespecific">javax.sound</programlisting> package.</para>
- </section><section id="sn-">
- <title>Integration of Mozilla Rhino (JavaScript) </title>
- <para>Rhino is a pure-Java JavaScript implementation from Mozilla providing an easy mixing of Java and JavaScript for developers using the <programlisting format="linespecific">javax.script</programlisting> package.</para>
- </section><section id="sn-">
- <title>Other improvements </title>
- <para>Also in Fedora 10 Java cryptography (<programlisting format="linespecific">javax.crypto</programlisting>) is fully supported without any (regional) restrictions.</para>
- </section>
- </section><section id="sn-">
- <title>Fedora and JPackage </title>
- <para>Fedora 10 includes many packages derived from the JPackage Project.</para>
- <para>
- <ulink url="http://jpackage.org">http://jpackage.org</ulink>
- </para><para>Some of these packages are modified in Fedora to remove proprietary software dependencies, and to make use of GCJ's ahead-of-time compilation feature. Use the Fedora repositories to update these packages, or use the JPackage repository for packages not provided by Fedora. Refer to the JPackage website for more information about the project and the software it provides.</para>
- <para>Admonition("warning", "Mixing Packages from Fedora and JPackage", "Research package compatibility before you install software from both the Fedora and JPackage repositories on the same system. Incompatible packages may cause complex issues.")</para>
- </section><section id="sn-">
- <title>Note on upgrading from Fedora 8 - OpenJDK Replaces IcedTea </title>
- <para>Since Fedora 9 the packages called <programlisting format="linespecific">java-1.7.0-icedtea*</programlisting> in Fedora 8 have been renamed to <programlisting format="linespecific">java-1.6.0-openjdk*</programlisting>. The Fedora 8 IcedTea packages tracked the unstable OpenJDK 7 branch, whereas the <programlisting format="linespecific">java-1.6.0-openjdk*</programlisting> packages track the stable OpenJDK 6 branch. All the upstream IcedTea sources are included in the <programlisting format="linespecific">java-1.6.0-openjdk</programlisting> SRPM.</para><para>If you are upgrading from a system based on Fedora 8 that still has IcedTea installed, the package changeover does not happen automatically. The packages related to IcedTea based on OpenJDK 7 must first be erased, then the new OpenJDK 6 packages installed.</para>
- <para />
- <programlisting>
-su -c 'yum erase java-1.7.0-icedtea{,-plugin}'
-su -c 'yum install java-1.6.0-openjdk{,-plugin}'
-</programlisting>
- <para />
- <para>Upgrading from Fedora 9 does not require special action.</para>
- </section>
- </section>
+
+<section lang="en" id="sn-Java">
+ <title>Java</title>
+ <para />
+ <section id="sn-Best_of_breed_free_software_Java_implementation">
+ <title>Best of breed free software Java implementation</title>
+ <para>Fedora includes multiple best of breed free software Java(TM)
+ implementations, obtained through active adoption of innovative
+ technology integrations produced by Fedora and others within
+ upstream projects. The implementations integrated into Fedora are
+ based on OpenJDK (<ulink url="http://openjdk.java.net/"/>) and the
+ IcedTea GNU/Linux distribution integration project (<ulink
+ url="http://icedtea.classpath.org/"/>), or based on alternatives
+ such as the GNU Compiler for Java (GCJ - <ulink
+ url="http://gcc.gnu.org/java"/> and the GNU Classpath core class
+ libraries (<ulink url="http://www.gnu.org/software/classpath/">).
+ All Fedora innovations are pushed upstream to get the widest
+ possible integration of the technologies in general Java
+ implementations.</para>
+ <para>The implementation of OpenJDK 6 included in Fedora 10 uses the
+ HotSpot virtual machine runtime compiler on x86, x86_64, and
+ SPARC. On PowerPC (PPC) it uses the zero interpreter, which is
+ slower. On all architectures an alternative implementation based
+ on GCJ and GNU Classpath is included that includes an
+ ahead-of-time compiler to produce native binaries.</para>
+ <para>Fedora binaries for selected architectures (currently only x86
+ and x86_64 based on OpenJDK) are tested against the Java
+ Compatibility Kit (JCK) by Red Hat to guarantee 100% compatibility
+ with the Java Specification (JDK 1.6 at this time).</para>
+ </section>
+ <section id="sn-Handling_Java_applets_and_web_start_applications">
+ <title>Handling Java Applets and web start applications</title>
+ <para>In Fedora 10 <command>gcjwebplugin</command> has been
+ replaced by <command>IcedTeaPlugin</command> that runs
+ untrusted applets safely in a Web browser and works on any
+ architecture. You can see which Applet Plugin is installed by
+ typing <userinput>about:plugins</userinput> in Firefox.
+ The new plugin adds support for the JavaScript bridge
+ (LiveConnect) that was missing from earlier versions. For more
+ details on "bytecode-to-JavaScript bridge (LiveConnect)", refer to
+ the bug report:</para>
+ <para>
+ <ulink
+ url="https://bugzilla.redhat.com/show_bug.cgi?id=304021"/>
+ </para>
+ <para>Feedback on the security policy is very appreciated. If
+ you suspect the security policy may be too restrictive to enable
+ restricted applets, run the <command>firefox -g</command> command in a
+ terminal window to see what is being restricted, then grant the
+ restricted permission in the <filename>/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/security/java.policy</filename>
+ file. If you then file a bug report, your exception could end up
+ in the packaged security policy and you won't have to hack the
+ policy file in the future.</para>
+ <para>Experimental Web Start
+ (<command>javaws</command>)
+ support via NetX has been added to the IcedTea repository. When a
+ Java Network Launching Protocol (<filename>.jnlp</filename>) file is embedded
+ on a web page you can open it with the IcedTea Web Start
+ (<filename>/usr/bin/javaws</filename>).</para>
+ <para>
+ <ulink
+ url="http://jnlp.sourceforge.net/"/> -- NetX</para>
+ </section>
+ <section id="sn-New_integration_with_other_Fedora_technologies">
+ <title>New integration with other Fedora technologies</title>
+ <para>Through the IcedTea project, OpenJDK has been integrated with
+ several new technologies that are also part of Fedora 10.</para>
+ <section id="sn-VisualVM_integration_through_the_NetBeans_framework">
+ <title>VisualVM integration through the NetBeans framework</title>
+ <para>VisualVM (<programlisting
+ format="linespecific">jvisualvm</programlisting>) provides a
+ graphical overview of any local or remotely running Java
+ application, letting you monitor all running threads, classes,
+ and objects allocated by the application by taking thread dumps,
+ heap dumps, and other lightweight profiling tools.</para>
</section>
- </article>
-</book>
\ No newline at end of file
+ <section id="sn-PulseAudio_integration_for_javax.sound">
+ <title>PulseAudio integration for
+ <package>javax.sound</package></title>
+ <para>PulseAudio integrations provides all the benefits of
+ PulseAudio to any java application using the
+ <package>javax.sound</package> package.</para>
+ </section>
+ <section id="sn-Integration_of_Mozilla_Rhino_-_JavaScript">
+ <title>Integration of Mozilla Rhino - JavaScript</title>
+ <para>Rhino is a pure-Java JavaScript implementation from Mozilla
+ providing an easy mixing of Java and JavaScript for developers
+ using the <package>javax.script</package>
+ package.</para>
+ </section>
+ <section id="sn-Other_improvements">
+ <title>Other improvements</title>
+ <para>Also in Fedora 10 Java cryptography
+ (<package>javax.crypto</package>) is fully supported without any
+ (regional) restrictions.</para>
+ </section>
+ </section>
+ <section id="sn-Fedora and JPackage">
+ <title>Fedora and JPackage</title>
+ <para>Fedora 10 includes many packages derived from the JPackage
+ Project.</para>
+ <para>
+ <ulink url="http://jpackage.org"/>
+ </para>
+ <para>Some of these packages are modified in Fedora to remove
+ proprietary software dependencies, and to make use of GCJ's
+ ahead-of-time compilation feature. Use the Fedora repositories to
+ update these packages, or use the JPackage repository for packages
+ not provided by Fedora. Refer to the JPackage website for more
+ information about the project and the software it provides.</para>
+ <warning>
+ <title>Mixing Packages from Fedora and JPackage</title>
+ <para>Research package compatibility before you install software
+ from both the Fedora and JPackage repositories on the same
+ system. Incompatible packages may cause complex issues.</para>
+ </warning>
+ </section>
+ <section id="sn-Note_on_upgrading_from_Fedora_8_-_OpenJDK_Replaces_IcedTea">
+ <title>Note on upgrading from Fedora 8 - OpenJDK Replaces IcedTea</title>
+ <para>Since Fedora 9 the packages called <package>java-1.7.0-icedtea*</package> in
+ Fedora 8 have been renamed to <package>java-1.6.0-openjdk*</package>. The
+ Fedora 8 IcedTea packages tracked the unstable OpenJDK 7 branch,
+ whereas the <package>java-1.6.0-openjdk*</package>
+ packages track the stable OpenJDK 6 branch. All the upstream
+ IcedTea sources are included in the <package>java-1.6.0-openjdk</package>
+ SRPM.</para>
+ <para>If you are upgrading from a system based on Fedora 8 that
+ still has IcedTea installed, the package changeover does not
+ happen automatically. The packages related to IcedTea based on
+ OpenJDK 7 must first be erased, then the new OpenJDK 6 packages
+ installed.</para>
+ <screen>
+ <userinput>su -c 'yum erase java-1.7.0-icedtea{,-plugin}' su -c 'yum install java-1.6.0-openjdk{,-plugin}'</userinput>
+ </screen>
+ <para>Upgrading from Fedora 9 does not require special
+ action.</para>
+ </section>
+</section>
diff --git a/en-US/Legal_Stuff_and_Administrivia.xml b/en-US/Legal_Stuff_and_Administrivia.xml
index 7a26431..d7023a7 100644
--- a/en-US/Legal_Stuff_and_Administrivia.xml
+++ b/en-US/Legal_Stuff_and_Administrivia.xml
@@ -2,8 +2,8 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<chapter id="blah-Test">
- <title>Test</title>
+<chapter id="Legal_Stuff_and_Administrivia">
+ <title>Legal Stuff and Administrivia</title>
<para/>
<!-- Fedora_overview.xml -->
diff --git a/en-US/Welcome_to_Fedora.xml b/en-US/Welcome_to_Fedora.xml
index 17161ca..c4da363 100644
--- a/en-US/Welcome_to_Fedora.xml
+++ b/en-US/Welcome_to_Fedora.xml
@@ -47,6 +47,11 @@
</para>
</listitem>
</itemizedlist>
+
+<!-- Fedora_10_Overview.xml -->
+
+ <xi:include href="Fedora_10_Overview.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
</section>
commit 4cd1607f13c9936081610eec4044bf59e465ef90
Author: Karsten 'quaid' Wade <kwade at calliope.phig.org>
Date: Thu Oct 16 23:57:06 2008 -0700
Changing name to match the actual term 'Fedora Live'.
diff --git a/en-US/Fedora_Live_images.xml b/en-US/Fedora_Live_images.xml
new file mode 100644
index 0000000..480ee8b
--- /dev/null
+++ b/en-US/Fedora_Live_images.xml
@@ -0,0 +1,80 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
+<?
+
+ <book>
+ <article lang="en">
+ <articleinfo>
+ <title>Docs/Beats/Live</title>
+ </articleinfo><section id="sn-">
+ <title>Docs/Beats/Live</title>
+ <section id="sn-">
+ <title>Fedora Live Images </title>
+ <para>The Fedora 10 release includes several Fedora Live ISO images in addition to the traditional installation images. These ISO images are bootable, and you can burn them to media and use them to try out Fedora. They also include a feature that allows you to install the Fedora Live image content to your hard drive for persistence and higher performance. </para>
+ <section id="sn-">
+ <title>Available Images </title>
+ <para>For a complete list of current spins available, and instructions for using them, refer to:</para>
+ <para>
+ <ulink url="http://fedoraproject.org/wiki/CustomSpins">http://fedoraproject.org/wiki/CustomSpins</ulink>
+ </para>
+ </section><section id="sn-">
+ <title>Usage Information </title>
+ <para>To boot from the Fedora Live image, insert it into your computer and restart. To log in and use the desktop environment, enter the username <programlisting format="linespecific">fedora</programlisting>. There is no password on this account. The GNOME-based Fedora Live images automatically login after one minute, so users have time to select a preferred language. After logging in, if you wish to install the contents of the live image to your hard drive, click on the <emphasis>Install to Hard Drive</emphasis> icon on the desktop.</para>
+ </section><section id="sn-">
+ <title>Text Mode Installation </title>
+ <para>You can do a text mode installation of the Fedora Live images using the <programlisting format="linespecific">liveinst</programlisting> command in the console.</para>
+ </section><section id="sn-">
+ <title>USB Booting </title>
+ <para>Another way to use these Fedora Live images is to put them on a USB stick. To do this, you can use liveusb-creator graphical interface. You can use Add/Remove software, search and install liveusb-creator or install using yum:</para>
+ <para />
+ <programlisting>
+su -c 'yum install liveusb-creator'
+</programlisting>
+ <para />
+ <para>You can also use the command line interface, install the <programlisting format="linespecific">livecd-tools</programlisting> package from the repository. Then, run the <programlisting format="linespecific">livecd-iso-to-disk</programlisting> script:</para><para />
+ <programlisting>/usr/bin/livecd-iso-to-disk /path/to/live.iso /dev/sdb1
+</programlisting>
+ <para />
+ <para>Replace <emphasis>/dev/sdb1</emphasis> with the partition where you want to put the image.</para><para>This is <emphasis>not</emphasis> a destructive process; any data you currently have on your USB stick <emphasis>is preserved</emphasis>.</para>
+ </section><section id="sn-">
+ <title>Persistent Home Directory </title>
+ <para>Support for keeping a persistent <programlisting format="linespecific">/home</programlisting> with the rest of the system stateless has been added for Fedora 10. This includes support for encrypting <programlisting format="linespecific">/home</programlisting> to protect your system in the case where your USB stick is lost or stolen. To use this, download the live image and run the following command:</para><para />
+ <programlisting>livecd-iso-to-disk --home-size-mb 512 /path/to/live.iso /dev/sdb1
+</programlisting>
+ <para />
+ <para>Replace <programlisting format="linespecific">/dev/sdb1</programlisting> with the partition where you want to put the image.</para><para>Replace <programlisting format="linespecific">512</programlisting> with the desired size in megabytes of the persistent <programlisting format="linespecific">/home</programlisting>. The <programlisting format="linespecific">livecd-iso-to-disk</programlisting> shell script is stored in the <programlisting format="linespecific">LiveOS</programlisting> directory at the top level of the CD image. The USB media must have sufficient free space for the Fedora Live image, plus the <programlisting format="linespecific">/home</programlisting>, plus any other data to be stored on the media. By default, this encrypts your data and prompts for a passphrase to use. If you want to have an unencrypted <programlisting format="linespecific">/home</programlisting>, then you can specify <programlisting format="linespecific">--unencrypted-hom
e</programlisting>.</para><para>Note that later runs of <programlisting format="linespecific">livecd-iso-to-disk</programlisting> preserve the <programlisting format="linespecific">/home</programlisting> that is created on the USB stick, continuing to use it even if you change your live image. </para>
+ </section><section id="sn-">
+ <title>Live USB Persistence </title>
+ <para>Support for persistent changes with a Fedora Live image exists for Fedora 9 and later. The primary use case is booting from a Fedora Live image on a USB flash drive and storing changes to that same device. To do this, download the Fedora Live image and then run the following command:</para>
+ <para />
+ <programlisting>livecd-iso-to-disk --overlay-size-mb 512 /path/to/live.iso /dev/sdb1
+</programlisting>
+ <para />
+ <para>Replace <programlisting format="linespecific">/dev/sdb1</programlisting> with the partition where you want to put the image.</para><para>Replace <programlisting format="linespecific">512</programlisting> with the desired size in megabytes of the persistent data, or <programlisting format="linespecific">overlay</programlisting>. The <programlisting format="linespecific">livecd-iso-to-disk</programlisting> shell script is stored in the <programlisting format="linespecific">LiveOS</programlisting> directory at the top level of the CD image. The USB media must have sufficient free space for the Fedora Live image, plus the overlay, plus any other data to be stored on the media.</para>
+ </section><section id="sn-">
+ <title>Booting a Fedora Live Image Off of USB on Intel-based Apple Hardware </title>
+ <para>Fedora 10 includes support for putting the live image onto a USB image and then booting it on Intel processor-based Apple hardware. Unlike for most x86 machines, this unfortunately requires reformatting the USB stick that you are using. To set up a stick for this, you can run</para>
+ <para />
+ <programlisting>/usr/bin/livecd-iso-to-disk --mactel /path/to/live.iso /dev/sdb1
+</programlisting>
+ <para />
+ <para>Replace <programlisting format="linespecific">/dev/sdb1</programlisting> with the partition where you want to put the image.</para><para>Note that all of the other arguments for the <programlisting format="linespecific">livecd-iso-to-disk</programlisting> tool as described above can be used here as well.</para>
+ </section><section id="sn-">
+ <title>Differences From a Regular Fedora Install </title>
+ <para>The following items are different from a normal Fedora install with the Fedora Live images.</para>
+ <itemizedlist>
+ <listitem>
+ <para> Fedora Live images provide a subset of packages available in the regular DVD image. Both connect to the same repository that has all the packages.</para>
+ </listitem><listitem>
+ <para> The SSH daemon <programlisting format="linespecific">sshd</programlisting> is disabled by default. The daemon is disabled because the default username in the Fedora Live images does not have a password. However, installation to hard disk prompts for creating a new username and password.</para>
+ </listitem><listitem>
+ <para> Fedora Live image installations do not allow any package selection or upgrade capability since they copy the entire file system from media or USB disks to the hard disk. After the installation is complete, and your system has been rebooted, you can add and remove packages as desired with the <emphasis>Add/Remove Packages</emphasis> tool, <programlisting format="linespecific">yum</programlisting>, or the other software management tools.</para>
+ </listitem><listitem>
+ <para> Fedora Live images do not work on <programlisting format="linespecific">i586</programlisting> architecture.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+ </section>
+ </article>
+</book>
\ No newline at end of file
commit 94983ab814b1b5c1aeb4be632e1f664025d47859
Author: Karsten 'quaid' Wade <kwade at calliope.phig.org>
Date: Thu Oct 16 16:33:30 2008 -0700
Removing Fedora 9 content, replaced by the KDE 3 devel libraries chapter.
diff --git a/en-US/KDE_4_development_platform.xml b/en-US/KDE_4_development_platform.xml
deleted file mode 100644
index be50784..0000000
--- a/en-US/KDE_4_development_platform.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-
-<section lang="en" id="sn-KDE_4_development_platform">
- <title>KDE 4 development platform</title>
- <para>Fedora 8 includes KDE 4.0 (beta) development libraries. The following new packages are provided: </para>
- <itemizedlist>
- <listitem>
- <para>
- <programlisting format="linespecific">kdelibs4</programlisting>: KDE 4 libraries</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">kdepimlibs</programlisting>: KDE 4 PIM libraries</para>
- </listitem><listitem>
- <para>
- <programlisting format="linespecific">kdebase4</programlisting>: KDE 4 core runtime files</para>
- </listitem>
- </itemizedlist><para>Use these packages to develop, build and run KDE 4 applications within KDE 3 or any other desktop environment.</para>
- <para>The <programlisting format="linespecific">kdebase4</programlisting> package also includes a beta version of the <emphasis>Dolphin</emphasis> file manager as a technology preview. As this is a beta version, some issues may still be present. If you need a stable version of <emphasis>Dolphin</emphasis>, please install the <programlisting format="linespecific">d3lphin</programlisting> package, which is based on KDE 3 and can be safely installed alongside <programlisting format="linespecific">kdebase4</programlisting>.</para><para>These packages are designed to: </para>
- <itemizedlist>
- <listitem>
- <para> comply with the Filesystem Hierarchy Standard (FHS), and</para>
- </listitem><listitem>
- <para> be completely safe to install in parallel with KDE 3, including the <programlisting format="linespecific">-devel</programlisting> packages.</para>
- </listitem>
- </itemizedlist><para>In order to achieve this, Fedora KDE SIG members made 2 changes to the <programlisting format="linespecific">-devel</programlisting> packages: </para><itemizedlist>
- <listitem>
- <para> The library symlinks are installed to <programlisting format="linespecific">/usr/lib/kde4/devel</programlisting> or <programlisting format="linespecific">/usr/lib64/kde4/devel</programlisting> depending on system architecture.</para>
- </listitem><listitem>
- <para> The <programlisting format="linespecific">kconfig_compiler</programlisting> and <programlisting format="linespecific">makekdewidgets</programlisting> tools have been renamed <programlisting format="linespecific">kconfig_compiler4</programlisting> and <programlisting format="linespecific">makekdewidgets4</programlisting>, respectively.</para>
- </listitem>
- </itemizedlist><para>These changes should be completely transparent to the vast majority of KDE 4 applications that use <programlisting format="linespecific">cmake</programlisting> to build, since <programlisting format="linespecific">FindKDE4Internal.cmake</programlisting> has been patched to match these changes.</para><para>Note that <programlisting format="linespecific">kdebase4</programlisting> does <emphasis>not</emphasis> include the KDE 4 Desktop package <programlisting format="linespecific">kdebase-workspace</programlisting> and its components such as <emphasis>Plasma</emphasis> and <emphasis>KWin</emphasis> version 4. The <programlisting format="linespecific">kdebase-workspace</programlisting> package is still too incomplete and unstable for daily use and would conflict with KDE 3.</para>
- </section>
- </section>
- </section>
commit a643302ac64aa07711aa5dd8b83d5050869a385f
Author: Karsten 'quaid' Wade <kwade at calliope.phig.org>
Date: Thu Oct 16 15:42:12 2008 -0700
XML clean-up and content for bz#461656
* XML clean-up as per conversion from wiki
* Fix for https://bugzilla.redhat.com/show_bug.cgi?id=461656
diff --git a/en-US/Installation_notes.xml b/en-US/Installation_notes.xml
index ecf2a80..2efa68a 100644
--- a/en-US/Installation_notes.xml
+++ b/en-US/Installation_notes.xml
@@ -1,182 +1,355 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<?
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
- <book>
- <article lang="en">
- <articleinfo>
- <title>Docs/Beats/Installer</title>
- </articleinfo><section id="sn-">
- <title>Docs/Beats/Installer</title>
- <section id="sn-">
- <title>Installation Notes </title>
- <para>
- <para>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata contentwidth="35px" fileref="http://fedoraproject.org/w/uploads/a/a4/Idea.png" scalefit="1" width="35px" />
- </imageobject><caption>
- <para />
- </caption>
- </inlinemediaobject>
- </para><para>
- <emphasis> To learn how to install Fedora, refer to <ulink url="http://docs.fedoraproject.org/install-guide/.">http://docs.fedoraproject.org/install-guide/.</ulink>
- </emphasis><literallayout>
-</literallayout>If you encounter a problem or have a question during installation that is not covered in these release notes, refer to <ulink url="http://www.fedoraproject.org/wiki/FAQ">http://www.fedoraproject.org/wiki/FAQ</ulink> and <ulink url="http://www.fedoraproject.org/wiki/Bugs/Common.">http://www.fedoraproject.org/wiki/Bugs/Common.</ulink>
- </para>
- </para>
- </para><para>
- <emphasis>Anaconda</emphasis> is the name of the Fedora installer. This section outlines issues related to <emphasis>Anaconda</emphasis> and installing Fedora 10.</para><section id="sn-">
- <title>Installation media </title>
- <para>
- <para>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata contentwidth="35px" fileref="http://fedoraproject.org/w/uploads/c/cc/Note.png" scalefit="1" width="35px" />
- </imageobject><caption>
- <para />
- </caption>
- </inlinemediaobject>
- </para><para>
- <emphasis> If you intend to download the Fedora DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2 GiB in size. </emphasis>
- <literallayout>
-</literallayout>The programs <programlisting format="linespecific">wget</programlisting> 1.9.1-16 and above, <programlisting format="linespecific">curl</programlisting>, and <programlisting format="linespecific">ncftpget</programlisting> do not have this limitation, and can successfully download files larger than 2 GiB. BitTorrent is another method for downloading large files. For information about obtaining and using the torrent file, refer to <ulink url="http://torrent.fedoraproject.org/.">http://torrent.fedoraproject.org/.</ulink>
- </para>
- </para>
- </para><para>
- <emphasis>Anaconda</emphasis> asks if it should verify the installation medium when <emphasis>Install or upgrade an existing system</emphasis> is selected during boot from an installation-only media.</para><para>For Fedora Live media, press any key during the initial boot countdown, bringing up a boot option menu. Select <emphasis>Verify and boot</emphasis> to perform the media test. The pure installation medium can be used to verify a Fedora Live medium. <emphasis>Anaconda</emphasis> asks during the mediacheck if you want to check any other disc than the one <emphasis>Anaconda</emphasis>' is running from. To test another media, select <programlisting format="linespecific">eject</programlisting> to eject the inserted medium, then replace it with the medium you want to test instead.</para><para>Perform this test everytime after you create or receive a new installation or live medium.</para>
- <para>The Fedora Project strongly recommends that you perform this test before reporting any installation-related bugs. Many of the bugs reported are actually due to improperly-burned CD or DVDs.</para>
- <para>In rare cases, the testing procedure may report some usable discs as faulty. This result is often caused by disc writing software that does not include padding when creating discs from ISO files.</para>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata contentwidth="35px" fileref="http://fedoraproject.org/w/uploads/c/cc/Note.png" scalefit="1" width="35px" />
- </imageobject><caption>
- <para />
- </caption>
- </inlinemediaobject>
- </para><para>
- <emphasis> BitTorrent Automatically Verifies File Integrity.</emphasis>
- <literallayout>
-</literallayout>If you use BitTorrent, any files you download are automatically validated. If your file completes downloading you do not need to check it. Once you burn your CD or DVD, however, you should still use <programlisting format="linespecific">mediacheck</programlisting> to test the integrity of the media.</para>
- </para>
- </para><para>Another reason for a failure during installation is faulty memory. To perform memory testing before you install Fedora, press any key to enter the boot menu, then select <emphasis>Memory Test</emphasis>. This option runs the <emphasis>Memtest86</emphasis> standalone memory testing software in place of <emphasis>Anaconda</emphasis>. <emphasis>Memtest86</emphasis> memory testing continues until you press the <emphasis>[Esc]</emphasis> key.</para><para>Fedora 10 supports graphical FTP and HTTP installations. However, the installer image must either fit in RAM or appear on local storage, such as the installation DVD or Live Media. Therefore, only systems with more than 192MiB of RAM or that boot from the installation DVD or Live Media can use the graphical installer. Systems with 192MiB RAM or less fall back to using the text-based installer automatically. If you prefer to use the text-based installer, type <programlisting format="linespecific">linux text<
/programlisting> at the <programlisting format="linespecific">boot:</programlisting> prompt.</para>
- </section><section id="sn-">
- <title>Changes in Anaconda </title>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://www.fedoraproject.org/wiki/Anaconda/Features/NetConfigForNM"> NetConfig in NM</ulink> -- Anaconda is now using NetworkManager for configuring network interfaces during installation. The previous backend tool was <programlisting format="linespecific">libdhcp</programlisting> (which was a replacement for <programlisting format="linespecific">libpump</programlisting>). Anaconda uses NetworkManager by communicating with it via D-Bus during installation. The move to NetworkManager in Anaconda is still ongoing and some things are not yet 100% functional, but the bulk of existing functionality has been retained. NetworkManager is enabled by default on newly installed systems, so moving to NetworkManager in Anaconda allows the installer to use the same network management tool that the final system uses. The move to NetworkManager brings some changes, most notably the removal of the network interface configuration screen in Anaconda. You are no lon
ger asked to verify the network settings during installation. The screen now simply prompts for the hostname. The settings used during installation are written to the system.</para>
- </listitem>
- </itemizedlist><itemizedlist>
- <listitem>
- <para> When using the <programlisting format="linespecific">netinst.iso</programlisting> to boot the installer, Anaconda defaults to using the Fedora mirrorlist URL as the installation source. The method selection screen no longer appears by default. If you do not wish to use the mirrorlist URL, either add <programlisting format="linespecific">repo=<your installation source></programlisting> or add <programlisting format="linespecific">askmethod</programlisting> to the installer boot parameters. The <programlisting format="linespecific">askmethod</programlisting> option causes the selection screen to appear as it did in previous releases. Boot parameters can be added by pressing the <emphasis>[Tab]</emphasis> key in the initial boot screen and appending your new parameters to the existing list. For more information, see the <programlisting format="linespecific">repo=</programlisting> and <programlisting format="linespecific">stage2=</programlisting> descr
iptions at <ulink url="http://fedoraproject.org/wiki/Anaconda/Options">http://fedoraproject.org/wiki/Anaconda/Options</ulink>
- </para>
- </listitem>
- </itemizedlist>
- </section><section id="sn-">
- <title>Installation Related Issues </title>
- <itemizedlist>
- <listitem>
- <para> When PXE booting and using a .iso file for the installation media via NFS you are now required to add method=nfsiso:server:/path to the command line.</para>
- </listitem>
- </itemizedlist><section id="sn-">
- <title>IDE device names </title>
- <para>Use of <programlisting format="linespecific">/dev/hdX</programlisting> on i386 and x86_64 for IDE drives changed to <programlisting format="linespecific">/dev/sdX</programlisting> in Fedora 7. If you are upgrading from an earlier version than Fedora 7, you need to research about the importance of labeling devices for upgrades and any partition limitations.</para>
- </section><section id="sn-">
- <title>IDE RAID </title>
- <para>Not all IDE RAID controllers are supported. If your RAID controller is not yet supported by <programlisting format="linespecific">dmraid</programlisting>, you may combine drives into RAID arrays by configuring Linux software RAID. For supported controllers, configure the RAID functions in the computer BIOS.</para>
- </section><section id="sn-">
- <title>Multiple NICs and PXE installation </title>
- <para>Some servers with multiple network interfaces may not assign eth0 to the first network interface as BIOS knows it, which can cause the installer to try using a different network interface than was used by PXE. To change this behavior, use the following in <programlisting format="linespecific">pxelinux.cfg/*</programlisting> config files:</para><para />
- <programlisting>IPAPPEND 2
-APPEND ksdevice=bootif
-</programlisting>
- <para />
- <para>The configuration options above causes the installer to use the same network interface as BIOS and PXE use. You can also use the following option: </para>
- <programlisting>ksdevice=link
-</programlisting>
- <para />
- <para>This option causes the installer to use the first network device it finds that is linked to a network switch.</para>
- </section>
- </section><section id="sn-">
- <title>Upgrade related issues </title>
- <para>Refer to <ulink url="http://fedoraproject.org/wiki/DistributionUpgrades">http://fedoraproject.org/wiki/DistributionUpgrades</ulink> for detailed recommended procedures for upgrading Fedora.</para><section id="sn-">
- <title>SCSI driver partition limits </title>
- <para>Whereas older IDE drivers supported up to 63 partitions per device, SCSI devices are limited to 15 partitions per device. <emphasis>Anaconda</emphasis> uses the <programlisting format="linespecific">libata</programlisting> driver in the same fashion as the rest of Fedora, so it is unable to detect more than 15 partitions on an IDE disk during the installation or upgrade process.</para><para>If you are upgrading a system with more than 15 partitions, you may need to migrate the disk to Logical Volume Management (LVM). This restriction may cause conflicts with other installed systems if they do not support LVM. Most modern Linux distributions support LVM and drivers are available for other operating systems as well.</para>
- </section><section id="sn-">
- <title>Disk partitions must be labeled </title>
- <para>A change in the way that the linux kernel handles storage devices means that device names like <programlisting format="linespecific">/dev/hdX</programlisting> or <programlisting format="linespecific">/dev/sdX</programlisting> may differ from the values used in earlier releases. <emphasis>Anaconda</emphasis> solves this problem by relying on partition labels or UUIDs for finding devices. If these are not present, then <emphasis>Anaconda</emphasis> presents a warning indicating that partitions need to be labelled and that the upgrade can not proceed. Systems that use Logical Volume Management (LVM) and the device mapper usually do not require relabeling.</para><section id="sn-">
- <title>To check disk partition labels </title>
- <para>To view partition labels, boot the existing Fedora installation, and enter the following at a terminal prompt: </para>
- <programlisting>/sbin/blkid
-</programlisting>
- <para> Confirm that each volume line in the list has a <programlisting format="linespecific">LABEL=</programlisting> value, as shown below: </para><programlisting>/dev/hdd1: LABEL="/boot" UUID="ec6a9d6c-6f05-487e-a8bd-a2594b854406" SEC_TYPE="ext2" TYPE="ext3"
-</programlisting>
- <para />
- </section><section id="sn-">
- <title>To set disk partition labels </title>
- <para>For ext2 and ext3 partitions without a label, use the following command: </para>
- <programlisting>su -c 'e2label /dev/example f7-slash'
-</programlisting>
- <para> For a VFAT filesystem use <programlisting format="linespecific">dosfslabel</programlisting> from the <programlisting format="linespecific">dosfstools</programlisting> package, and for NTFS filesystem use <programlisting format="linespecific">ntfslabel</programlisting> from the <programlisting format="linespecific">ntfsprogs</programlisting> package. Before rebooting the machine, also update the file system mount entries, and the GRUB kernel root entry.</para>
- </section><section id="sn-">
- <title>Update the file system mount entries </title>
- <para>If any filesystem labels were added or modified, then the device entries in <programlisting format="linespecific">/etc/fstab</programlisting> must be adjusted to match: </para><programlisting>su -c 'cp /etc/fstab /etc/fstab.orig'
-su -c 'gedit /etc/fstab'
-</programlisting>
- <para> An example of a mount by label entry is: </para>
- <programlisting> LABEL=f7-slash / ext3 defaults 1 1
-</programlisting>
- <para />
- </section><section id="sn-">
- <title>Update the grub.conf kernel root entry </title>
- <para>If the label for the / (root) filesystem was modified, the kernel boot parameter in the grub configuration file must also be modified: </para>
- <programlisting>su -c 'gedit /boot/grub/grub.conf'
-</programlisting>
- <para> A matching example kernel grub line is: </para>
- <programlisting> kernel /vmlinuz-2.6.20-1.2948.fc6 ro root=LABEL=f7-slash rhgb quiet
-</programlisting>
- <para />
- </section><section id="sn-">
- <title>Test changes made to labels </title>
- <para>If partition labels were adjusted, or the <programlisting format="linespecific">/etc/fstab</programlisting> file modified, then boot the existing Fedora installation to confirm that all partitions still mount normally and login is successful. When complete, reboot with the installation media to start the installer and begin the upgrade.</para>
- </section>
- </section><section id="sn-">
- <title>Upgrades versus fresh installations </title>
- <para>In general, fresh installations are recommended over upgrades. This is particularly true for systems that include software from third-party repositories. Third-party packages remaining from a previous installation may not work as expected on an upgraded Fedora system. If you decide to perform an upgrade anyway, the following information may be helpful:</para>
- <para>Before you upgrade, back up the system completely. In particular, preserve <programlisting format="linespecific">/etc</programlisting>, <programlisting format="linespecific">/home</programlisting>, and possibly <programlisting format="linespecific">/opt</programlisting> and <programlisting format="linespecific">/usr/local</programlisting> if customized packages are installed there. You may want to use a multi-boot approach with a "clone" of the old installation on alternate partition(s) as a fallback. In that case, create alternate boot media, such as a GRUB boot floppy.</para><para>
- <para>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata contentwidth="35px" fileref="http://fedoraproject.org/w/uploads/a/a4/Idea.png" scalefit="1" width="35px" />
- </imageobject><caption>
- <para />
- </caption>
- </inlinemediaobject>
- </para><para>
- <emphasis> Backups of configurations in <programlisting format="linespecific">/etc</programlisting> are also useful in reconstructing system settings after a fresh installation.</emphasis><literallayout>
-</literallayout>
- </para>
- </para>
- </para><para>After you complete the upgrade, run the following command:</para>
- <para />
- <programlisting>rpm -qa --last > RPMS_by_Install_Time.txt
-</programlisting>
- <para />
- <para>Inspect the end of the output for packages that pre-date the upgrade. Remove or upgrade those packages from third-party repositories, or otherwise deal with them as necessary. Some previously installed packages may no longer be available in any configured repository. To list all these packages, use the following command: </para>
- <programlisting>su -c 'yum list extras'
-</programlisting>
- <para />
- </section>
- </section><section id="sn-">
- <title>Kickstart HTTP Issue </title>
- <para> When using a Kickstart configuration file via HTTP, kickstart file retrieval may fail with an error that indicates the file could not be retrieved. Click the <emphasis>OK</emphasis> button several times without making modifications to override this error successfully. As a workaround, use one of the other supported methods to retrieve Kickstart configurations.</para>
- </section>
+<section lang="en" id="sn-Installation_notes">
+ <title>Installation notes</title>
+ <tip>
+ <title>To learn how to install Fedora, refer to <ulink
+ url="http://docs.fedoraproject.org/install-guide/"/>
+ </title>
+ <para>
+ If you encounter a problem or have a question during installation
+ that is not covered in these release notes, refer to <ulink
+ url="http://www.fedoraproject.org/wiki/FAQ"/> and <ulink
+ url="http://www.fedoraproject.org/wiki/Bugs/Common"/>.
+ </para>
+ </tip>
+ <para>
+ <application>Anaconda</application> is the name of the Fedora
+ installer. This section outlines issues related to
+ <application>Anaconda</application> and installing Fedora 10.</para>
+ <section id="sn-Installation media">
+ <title>Installation media</title>
+ <note>
+ <title> If you intend to download the Fedora DVD ISO image, keep
+ in mind that not all file downloading tools can accommodate
+ files larger than 2 GiB in size. </title>
+ <para> The programs <command>wget</command> 1.9.1-16 and above,
+ <command>curl</command>, and <command>ncftpget</command> do not
+ have this limitation, and can successfully download files larger
+ than 2 GiB. BitTorrent is another method for downloading large
+ files. For information about obtaining and using the torrent
+ file, refer to <ulink url="http://torrent.fedoraproject.org/">.
+ </para>
+ </note>
+ <para>
+ <application>Anaconda</application> asks if it should verify the
+ installation medium when <menuchoice>Install or upgrade an
+ existing system</menuchoice> is selected during boot from an
+ installation-only media.</para>
+ <para>For Fedora Live media, press any key during the initial boot
+ countdown, bringing up a boot option menu. Select
+ <menuchoice>Verify and boot</menuchoice> to perform the media
+ test. The pure installation medium can be used to verify a Fedora
+ Live medium. <application>Anaconda</application> asks during the
+ mediacheck if you want to check any other disc than the one
+ <application>Anaconda</application> is running from. To test
+ another media, select <menuchoice>eject</menuchoice> to eject
+ the inserted medium, then replace it with the medium you want to
+ test instead.</para>
+ <para>Perform this test everytime after you create or receive a new
+ installation or live medium.</para>
+ <para>The Fedora Project strongly recommends that you perform this
+ test before reporting any installation-related bugs. Many of the
+ bugs reported are actually due to improperly-burned CD or
+ DVDs.</para>
+ <para>In rare cases, the testing procedure may report some usable
+ discs as faulty. This result is often caused by disc writing
+ software that does not include padding when creating discs from
+ ISO files.</para>
+ <note>
+ <title>BitTorrent Automatically Verifies File Integrity.</title>
+ <para>If you use BitTorrent, any files you download are
+ automatically validated. If your file completes downloading you
+ do not need to check it. Once you burn your CD or DVD, however,
+ you should still use <programlisting
+ format="linespecific">mediacheck</programlisting> to test the
+ integrity of the media.</para>
+ </note>
+ <para>Another reason for a failure during installation is faulty
+ memory. To perform memory testing before you install Fedora, press
+ any key to enter the boot menu, then select
+ <menuchoice>Memory Test</menuchoice>. This option runs the
+ <application>Memtest86</application> standalone memory testing
+ software in place of <application>Anaconda</application>.
+ <application>Memtest86</application> memory testing continues
+ until you press the <keycap>Esc</keycap> key.</para>
+ <para>Fedora 10 supports graphical FTP and HTTP installations.
+ However, the installer image must either fit in RAM or appear on
+ local storage, such as the installation DVD or Live Media.
+ Therefore, only systems with more than 192MiB of RAM or that boot
+ from the installation DVD or Live Media can use the graphical
+ installer. Systems with 192MiB RAM or less fall back to using the
+ text-based installer automatically. If you prefer to use the
+ text-based installer, type <userinput>linux text</userinput> at
+ the <prompt>boot:</prompt> prompt.</para>
+ </section>
+ <section id="sn-Changes_in_Anaconda">
+ <title>Changes in Anaconda</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink
+ url="http://www.fedoraproject.org/wiki/Anaconda/Features/NetConfigForNM"/>
+ -- Anaconda is now using
+ <application>NetworkManager</application> for configuring
+ network interfaces during installation. The previous backend
+ tool was <systemitem class="library">libdhcp</systemitem>
+ (which was a replacement for <systemitem
+ class="library">libpump</systemitem>).
+ <application>Anaconda</application> uses
+ <application>NetworkManager</application> by communicating
+ with it via D-Bus during installation. The move to
+ <application>NetworkManager</application> in
+ <application>Anaconda</application> is still ongoing and some
+ things are not yet 100% functional, but the bulk of existing
+ functionality has been retained.
+ <application>NetworkManager</application> is enabled by
+ default on newly installed systems, so moving to
+ <application>NetworkManager</application> in
+ <application>Anaconda</application> allows the installer to
+ use the same network management tool that the final system
+ uses. The move to <application>NetworkManager</application>
+ brings some changes, most notably the removal of the network
+ interface configuration screen in
+ <application>Anaconda</application>. You are no longer asked
+ to verify the network settings during installation. The screen
+ now simply prompts for the hostname. The settings used during
+ installation are written to the system.</para>
+ </listitem>
+ <listitem>
+ <para>When using the <programlisting
+ format="linespecific">netinst.iso</programlisting> to boot
+ the installer, <application>Anaconda</application> defaults to
+ using the Fedora mirrorlist URL as the installation source.
+ The method selection screen no longer appears by default. If
+ you do not wish to use the mirrorlist URL, either add
+ <computeroutput>repo=<your installation
+ source></computeroutput> or add
+ <option>askmethod</option> to the installer boot parameters.
+ The <option>askmethod</option> option causes the selection
+ screen to appear as it did in previous releases. Boot
+ parameters can be added by pressing the <keycap>Tab</keycap>
+ key in the initial boot screen and appending your new
+ parameters to the existing list. For more information, refer
+ to the <computeroutput>repo=</computeroutput> and
+ <computeroutput>stage2=</computeroutput> descriptions at
+ <ulink url="http://fedoraproject.org/wiki/Anaconda/Options"/>.
+ </para>
+ </listitem>
+ <listitem>
+ <para></para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="sn-Installation_related_issues">
+ <title>Installation related issues</title>
+ <section id="PXE_booting_from_a_.iso">
+ <title>PXE booting from a <filename>.iso</filename></title>
+ <para>When PXE booting and using a <filename>.iso</filename> file
+ for the installation media via NFS you are now required to add
+ <userinput>method=nfsiso:server:/path</userinput> to the command
+ line.</para>
+ </section>
+ <section id="sn-IDE_device_names">
+ <title>IDE device names</title>
+ <para>Use of <filename>/dev/hdX</filename> on i386 and x86_64 for
+ IDE drives changed to <filename>/dev/sdX</filename> in Fedora 7.
+ If you are upgrading from an earlier version than Fedora 7, you
+ need to research about the importance of labeling devices for
+ upgrades and any partition limitations.</para>
+ </section>
+ <section id="sn-IDE_RAID">
+ <title>IDE RAID</title>
+ <para>Not all IDE RAID controllers are supported. If your RAID
+ controller is not yet supported by <systemitem
+ class="daemon">dmraid</systemitem>, you may combine drives
+ into RAID arrays by configuring Linux software RAID. For
+ supported controllers, configure the RAID functions in the
+ computer BIOS.</para>
+ </section>
+ <section id="sn-Multiple_NICs_and_PXE_installation">
+ <title>Multiple NICs and PXE installation</title>
+ <para>Some servers with multiple network interfaces may not assign
+ eth0 to the first network interface as BIOS knows it, which can
+ cause the installer to try using a different network interface
+ than was used by PXE. To change this behavior, use the
+ following in <filename>pxelinux.cfg/*</filename> config
+ files:</para>
+ <screen>
+ <computeroutput>IPAPPEND 2 APPEND
+ ksdevice=bootif</computeroutput>
+ </screen>
+ <para>The configuration options above causes the installer to use
+ the same network interface as BIOS and PXE use. You can also use
+ the following option: </para>
+ <screen>
+ <computeroutput>ksdevice=link</computeroutput>
+ </screen>
+ <para>This option causes the installer to use the first network
+ device it finds that is linked to a network switch.</para>
+ </section>
+ </section>
+ <section id="sn-Upgrade_related_issues">
+ <title>Upgrade related issues</title>
+ <para>Refer to <ulink
+ url="http://fedoraproject.org/wiki/DistributionUpgrades"/> for
+ detailed recommended procedures for upgrading Fedora.</para>
+ <section id="sn-SCSI_driver_partition_limits">
+ <title>SCSI driver partition limits</title>
+ <para>Whereas older IDE drivers supported up to 63 partitions per
+ device, SCSI devices are limited to 15 partitions per device.
+ <application>Anaconda</application> uses the <systemitem
+ class="library">libata</systemitem> driver in the same fashion
+ as the rest of Fedora, so it is unable to detect more than 15
+ partitions on an IDE disk during the installation or upgrade
+ process.</para>
+ <para>If you are upgrading a system with more than 15 partitions,
+ you may need to migrate the disk to Logical Volume Management
+ (LVM). This restriction may cause conflicts with other installed
+ systems if they do not support LVM. Most modern Linux
+ distributions support LVM and drivers are available for other
+ operating systems as well.</para>
+ </section>
+ <section id="sn-Disk_partitions_must_be_labeled">
+ <title>Disk partitions must be labeled</title>
+ <para>A change in the way that the Linux kernel handles storage
+ devices means that device names such as
+ <filename>/dev/hdX</filename> or <filename>/dev/sdX</filename>
+ may differ from the values used in earlier releases.
+ <application>Anaconda</application> solves this problem by
+ relying on partition labels or UUIDs for finding devices. If
+ these are not present, then <application>Anaconda</application>
+ presents a warning indicating that partitions need to be
+ labelled and that the upgrade can not proceed. Systems that use
+ Logical Volume Management (LVM) and the device mapper usually do
+ not require relabeling.</para>
+ <section id="sn-To_check_disk_partition_labels">
+ <title>To check disk partition labels</title>
+ <para>To view partition labels, boot the existing Fedora
+ installation, and enter the following at a terminal prompt:
+ </para>
+ <screen>
+ <userinput>/sbin/blkid</userinput>
+ </screen>
+ <para>Confirm that each volume line in the list has a
+ <computeroutput>LABEL=</computeroutput> value, as shown below:
+ </para>
+ <screen>
+ <computeroutput>/dev/hdd1: LABEL="/boot"
+ UUID="ec6a9d6c-6f05-487e-a8bd-a2594b854406" SEC_TYPE="ext2"
+ TYPE="ext3" </computeroutput>
+ </screen>
</section>
+ <section id="sn-To_set_disk_partition_labels">
+ <title>To set disk partition labels</title>
+ <para>For ext2 and ext3 partitions without a label, use the
+ following command: </para>
+ <screen>
+ <userinput>su -c 'e2label /dev/example f7-slash'</userinput>
+ </screen>
+ <para>For a VFAT filesystem use <command>dosfslabel</command>
+ from the <package>dosfstools</package> package, and for NTFS
+ filesystem use <command>ntfslabel</command> from the
+ <package>ntfsprogs</package> package. Before rebooting the
+ machine, also update the file system mount entries, and the
+ GRUB kernel root entry.</para>
+ </section>
+ <section id="sn-Update_the_file_system_mount_entries">
+ <title>Update the file system mount entries</title>
+ <para>If any filesystem labels were added or modified, then the
+ device entries in <filename>/etc/fstab</filename> must be
+ adjusted to match: </para>
+ <screen>
+ <userinput>su -c 'cp /etc/fstab /etc/fstab.orig' su -c 'gedit
+ /etc/fstab'</userinput>
+ </screen>
+ <para> An example of a mount by label entry is: </para>
+ <screen>
+ <computeroutput>LABEL=f7-slash / ext3 defaults 1
+ 1</computeroutput>
+ </screen>
+ </section>
+ <section id="sn-Update_the_grub.conf_kernel_root_entry">
+ <title>Update the <filename>grub.conf</filename> kernel root
+ entry</title>
+ <para>If the label for the <filename>/</filename> (root)
+ filesystem was modified, the kernel boot parameter in the grub
+ configuration file must also be modified: </para>
+ <screen>
+ <userinput>su -c 'gedit /boot/grub/grub.conf'</userinput>
+ </screen>
+ <para> A matching example kernel grub line is: </para>
+ <screen>
+ <computeroutput>kernel /vmlinuz-2.6.20-1.2948.fc6 ro
+ root=LABEL=f7-slash rhgb quiet</computeroutput>
+ </screen>
+ </section>
+ <section id="sn-Test_changes_made_to_labels">
+ <title>Test changes made to labels</title>
+ <para>If partition labels were adjusted, or the
+ <filename>/etc/fstab</filename> file modified, then boot the
+ existing Fedora installation to confirm that all partitions
+ still mount normally and login is successful. When complete,
+ reboot with the installation media to start the installer and
+ begin the upgrade.</para>
+ </section>
+ </section>
+ <section id="sn-Upgrades_versus_fresh_installations">
+ <title>Upgrades versus fresh installations</title>
+ <para>In general, fresh installations are recommended over
+ upgrades. This is particularly true for systems that include
+ software from third-party repositories. Third-party packages
+ remaining from a previous installation may not work as expected
+ on an upgraded Fedora system. If you decide to perform an
+ upgrade anyway, the following information may be helpful:</para>
+ <para>Before you upgrade, back up the system completely. In
+ particular, preserve <filename>/etc</filename>,
+ <filename>/home</filename>, and possibly
+ <filename>/opt</filename> and <filename>/usr/local</filename> if
+ customized packages are installed there. You may want to use a
+ multi-boot approach with a "clone" of the old installation on
+ alternate partition(s) as a fallback. In that case, create
+ alternate boot media, such as a GRUB boot floppy.</para>
+ <tip>
+ <title>Backups of configurations in <filename>/etc</filename>
+ are also useful in reconstructing system settings after a
+ fresh installation.</title>
+ </tip>
+ <para>After you complete the upgrade, run the following
+ command:</para>
+ <screen>
+ xs <userinput>rpm -qa --last >
+ RPMS_by_Install_Time.txt</userinput>
+ </screen>
+ <para>Inspect the end of the output for packages that pre-date the
+ upgrade. Remove or upgrade those packages from third-party
+ repositories, or otherwise deal with them as necessary. Some
+ previously installed packages may no longer be available in any
+ configured repository. To list all these packages, use the
+ following command: </para>
+ <screen>
+ <userinput>su -c 'yum list extras'</userinput>
+ </screen>
</section>
- </article>
-</book>
+ </section>
+ <section id="sn-Kickstart_HTTP_issue">
+ <title>Kickstart HTTP issue</title>
+ <para> When using a Kickstart configuration file via HTTP, kickstart
+ file retrieval may fail with an error that indicates the file
+ could not be retrieved. Click the <guibutton>OK</guibutton> button
+ several times without making modifications to override this error
+ successfully. As a workaround, use one of the other supported
+ methods to retrieve Kickstart configurations.</para>
+ </section>
+ <section id="Firstboot_requires_creation_of_non-root_user">
+ <title>Firstboot requires creation of non-root user</title>
+ <para>The <application>Firstboot</application> application requires
+ the creation of a non-root user for the system. This is to
+ support <systemitem class="daemon">gdm</systemitem> no longer
+ allowing the root user to log in to the graphical desktop.</para>
+ <para>If a network authentication mechanism is chosen during
+ installation <application>Firstboot</application> does not require
+ creating a that does not use local user.</para>
+ </section>
+</section>
More information about the docs-commits
mailing list