From fedora-docs-commits at redhat.com  Tue Nov  1 05:30:26 2005
From: fedora-docs-commits at redhat.com (Tatsuo Sekine (tsekine))
Date: Tue,  1 Nov 2005 00:30:26 -0500
Subject: release-notes RELEASE-NOTES-ja_JP.xml, NONE, 1.1 daemons-ja_JP.xml,
	NONE, 1.1 desktop-ja_JP.xml, NONE,
	1.1 development-tools-ja_JP.xml, NONE,
	1.1 entertainment-ja_JP.xml, NONE, 1.1 feedback-ja_JP.xml,
	NONE, 1.1 file-servers-ja_JP.xml, NONE,
	1.1 hardware-reqs-ja_JP.xml, NONE, 1.1 i18n-ja_JP.xml, NONE,
	1.1 install-notes-ja_JP.xml, NONE, 1.1 intro-ja_JP.xml, NONE,
	1.1 java-package-ja_JP.xml, NONE, 1.1 kernel-ja_JP.xml, NONE,
	1.1 legacy-ja_JP.xml, NONE, 1.1 misc-server-ja_JP.xml, NONE,
	1.1 multimedia-ja_JP.xml, NONE, 1.1 networking-ja_JP.xml, NONE,
	1.1 overview-ja_JP.xml, NONE, 1.1 package-movement-ja_JP.xml,
	NONE, 1.1 package-notes-ja_JP.xml, NONE,
	1.1 printing-ja_JP.xml, NONE, 1.1 project-overview-ja_JP.xml,
	NONE, 1.1 samba-ja_JP.xml, NONE, 1.1 security-ja_JP.xml, NONE,
	1.1 server-tools-ja_JP.xml, NONE, 1.1 splash-ja_JP.xml, NONE,
	1.1 web-servers-ja_JP.xml, NONE, 1.1 xorg-ja_JP.xml, NONE, 1.1
Message-ID: <200511010530.jA15UQjb029523@cvs-int.fedora.redhat.com>

Author: tsekine

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29480

Added Files:
	RELEASE-NOTES-ja_JP.xml daemons-ja_JP.xml desktop-ja_JP.xml 
	development-tools-ja_JP.xml entertainment-ja_JP.xml 
	feedback-ja_JP.xml file-servers-ja_JP.xml 
	hardware-reqs-ja_JP.xml i18n-ja_JP.xml install-notes-ja_JP.xml 
	intro-ja_JP.xml java-package-ja_JP.xml kernel-ja_JP.xml 
	legacy-ja_JP.xml misc-server-ja_JP.xml multimedia-ja_JP.xml 
	networking-ja_JP.xml overview-ja_JP.xml 
	package-movement-ja_JP.xml package-notes-ja_JP.xml 
	printing-ja_JP.xml project-overview-ja_JP.xml samba-ja_JP.xml 
	security-ja_JP.xml server-tools-ja_JP.xml splash-ja_JP.xml 
	web-servers-ja_JP.xml xorg-ja_JP.xml 
Log Message:
add Japanese (ja_JP) files.


***** Error reading new file: [Errno 2] No such file or directory: 'RELEASE-NOTES-ja_JP.xml'

--- NEW FILE daemons-ja_JP.xml ---
<section id="sn-daemons">
  <title>????????????????????????</title>
  <caution>
    <title>????????????????????????????????????</title>
    <para>
      ????????????????????? &DISTRO; &DISTROVER; ???????????????????????????????????????????????????
    </para>
  </caution>
  <section id="sn-daemons-updatedb">
    <title><filename>cron</filename> ???
      <filename>slocate</filename></title>
    <para>
      <command>slocate</command> ??????????????????????????????????????????????????????????????????????????????????????????
      <command>updatedb</command> ???????????????????????????????????????????????????????????????????????????
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      <command>slocate</command> ??????????????????????????????????????????????????????????????????
      <filename>/etc/updatedb.conf</filename> ?????????????????????????????????????????????????????????
    </para>
     
    <screen>
      DAILY_UPDATE=yes
    </screen>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
coding: utf-8-unix
End:
-->
    


--- NEW FILE desktop-ja_JP.xml ---
<section id="sn-desktop">
  <title>Desktop</title>
  <itemizedlist>
    <title>Notes</title>
    <listitem>
      <para>GNOME 2.12 ??? KDE 3.4.2 ???????????????
      </para>
    </listitem>
    <listitem>
      <para>
	????????????????????????????????? GNOME 2.12.1 ?????????????????????????????? GNOME 2.14 ????????????????????????????????????????????????
      </para>
      <itemizedlist>
        <listitem>
          <para>gnome-power-manager:
	    ??????????????????????????????????????? UPS ????????????????????????????????????????????????(HAL)????????????????????????
	    ??????????????????????????????????????????????????????
	    (????????????????????????????????????????????????????????????????????????)???????????? UI ??????????????????
	  </para>
        </listitem>
        <listitem>
          <para>gnome-screensaver:
	    ?????????????????????????????? <guilabel>Lock Screen</guilabel>
	    ??????????????????????????? UI ????????????????????????
	  </para>
        </listitem>
        <listitem>
          <para>
	    fontconfig ????????? shared-mime-info ??????????????????????????????????????????
	    (????????????????????????????????????????????????????????????????????????????????????????????????)???
	    ??????????????????????????????????????????????????????????????????
	  </para>
        </listitem>
      </itemizedlist>
    </listitem>
  <para>
    ?????????????????????????????????????????????????????????????????????????????????  
  </para>
  <para>
    GNOME 2.12 ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    Fedora Extras ????????? nautilus-open-terminal ???????????????????????????????????????????????????
    GNOME 2.12 ???????????????????????????????????????????????????????????????????????????????????????????????????????????? extras ??????????????????????????????????????????????????????????????????????????????????????????
  </para>
  <para>
    ???????????????????????????????????????????????????????????????????????????????????????????????????
    ????????????????????????????????????????????????????????????????????????????????????
  </para>
  <para>
      MCS SELinux ??? rawhide ??????????????????
      ????????????
      (<emphasis>??????</emphasis> - ??????????????????????????????????????????)
  </para>
  <caution>
    <title>OpenOffice ??????????????????????????????????????????????????????</title>
    <para>
      ????????????????????????????????????????????????????????? <emphasis role='strong'>?????????</emphasis>????????????????????????????????????????????????????????????????????????????????? <ulink
	url='/OpenOffice'>OpenOffice</ulink> ??????????????????????????????????????????????????????????????????
    </para>
    <para>
      ???????????????????????????????????????????????????????????????<emphasis
      role='strong'>??????</emphasis>???????????????????????????????????????
    </para>
<screen>
<command>rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
</screen>
  </caution>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
coding: utf-8-unix
End:
-->


--- NEW FILE development-tools-ja_JP.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "This header makes editing XML easier" >
 <!ENTITY DISTRO      "DISTRO" >
 <!ENTITY DISTROVER   "DISTROVER" >

]>
-->
<!-- Content commented out, no update performed by beat writer yet.
<section id="sn-devel">
  <title>
    ???????????????
  </title>
  <section id="sn-devel-gcc">
    <title>GCC ?????????????????????????????????</title>
    <para>
      &DISTRO; &DISTROVER; ??? <abbrev>GCC</abbrev>
      4.0 ???????????????????????????
      ?????? <abbrev>GCC</abbrev> ???????????????????????????????????????????????????????????????
    </para>
    <itemizedlist>
      <title>??????</title>
      <listitem>
        <para>
	  ????????????????????? <parameter
	    class="option">-fno-var-tracking</parameter>
	  ??????????????????????????????????????????????????????????????????????????????????????????
	  <abbrev>GDB</abbrev> 6.1 ????????????????????????????????????????????????
        </para>
      </listitem>
      <listitem>
        <para>
          ??????????????? <parameter class="option">-fwritable-strings</parameter>
	  ??????????????????????????????????????????
        </para>
      </listitem>
      <listitem>
        <para>
	  ????????????????????????????????????Unicode ????????????????????????????????????
	  ???????????????????????????????????????<envar>LC_CTYPE</envar>
	  ??????????????? &quot;<filename>C</filename>&quot;
	  ???????????????????????????????????????????????????????????????????????????
        </para>
      </listitem>
      <listitem>
        <para>
	  ???????????????????????????????????? <filename>specs</filename>
	  ???????????????????????????????????????????????????
	  ????????????????????????????????????????????????????????????????????????????????????????????????????????? 
	  <parameter
	    class="option">-dumpspecs</parameter>
	  ???????????????????????????????????????????????????????????????????????????????????????????????????
        </para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title>???????????????</title>
      <listitem>
        <para>
	  <abbrev>SSA</abbrev> ?????????????????????????????????????????????
	  ???????????????????????????????????? (constant propagation)???????????????????????????
	  (partial redundancy elimination)??????????????????
	  (strength reduction)????????????/?????????????????????????????????????????????????????????
	  (dead storage elimination)???????????????????????????????????????????????????????????????
	  (tail recursion by accumulation)
	  ????????????????????????
        </para>
      </listitem>
      <listitem>
        <para>
	  ??????????????????????????????????????????????????????
	  ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
        </para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title>????????????</title>
      <listitem>
        <para>
	  <function>execl(char *path, const char *arg,
	    ...)</function> ?????????????????????????????????
	  <literal>NULL</literal> ?????????????????????????????????
	  <literal>NULL</literal>
	  ?????????????????????????????????????????????????????????????????????????????????<computeroutput>sentinel</computeroutput>
	  ?????????????????????????????????
        </para>
      </listitem>
      <listitem>
        <para>
          ?????? <wordasword>cast-as-lvalue</wordasword>,
	  <wordasword>conditional-expression-as-lvalue</wordasword>,
	  <wordasword>compund-expression-as-lvalue</wordasword>
	  ???????????????????????????
        </para>
      </listitem>
      <listitem>
        <para>
          <computeroutput>#pragma pack()</computeroutput>
	  ????????????????????????????????????????????????????????????????????????
        </para>
      </listitem>
      <listitem>
        <para>
	  <computeroutput>register</computeroutput>
	  ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
        </para>
      </listitem>
      <listitem>
        <para>
	  ????????????????????????????????????????????????????????????????????????????????????
	  ???????????????????????????????????????????????????????????????????????????????????????
        </para>
      </listitem>
      <listitem>
        <para>
	  ????????????????????????????????????????????????????????? (<parameter
	    class="option">-O0</parameter>) ???????????????????????????
	  25% ??????????????????????????????????????????
        </para>
      </listitem>
      <listitem>
        <para>
	  ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????????????????????????????
	  <parameter
	    class="option">-fno-threadsafe-statics</parameter>
	  ????????????????????????????????????????????????????????????????????????????????????????????????????????????
        </para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title>Java</title>
      <listitem>
	<para>
	  ????????????????????????????????????<filename>rmic</filename> ???
	  <filename>grmic</filename> ??????<filename>rmiregistry</filename>
	  ??? <filename>grmiregistry</filename> ??????<filename>jar</filename>
	  ??? <filename>fastjar</filename> ?????????????????????
        </para>
      </listitem>
      <listitem>
	<para>
	  <filename>gnu.jit</filename>
	  ?????????????????????<application>GCJ</application> ???????????????
	  ??? just-in-time (<abbrev>JIT</abbrev>) ?????????????????????????????????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  <abbrev>AWT</abbrev> ??? <abbrev>SWING</abbrev>
	  ??????????????????????????????????????????????????????????????????????????????
	</para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title>FORTRAN</title>
      <listitem>
	<para>
	  <abbrev>GNU</abbrev> <application>FORTRAN 77</application>
	  ???????????????????????????????????? <application>FORTRAN
	    90/95</application> ?????????????????????????????????
	</para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title>Eclipse ????????????</title>
      <listitem>
	<para>
	  Eclipse 3.1M6 ???????????????????????????????????????????????????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  C Development Tool (<abbrev>CDT</abbrev>) ???????????????????????????
	</para>
      </listitem>
    </itemizedlist>
  </section>
</section>
-->

<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE entertainment-ja_JP.xml ---
<section id="sn-entertainment">
  <title>???????????????????????????????????????</title>
  <para>
    &FC; ??? &FEX; ??????????????????????????????????????????????????????
    ????????????????????????&FC; ?????? GNOME ???
    (<filename>gnome-games</filename> ???????????????)
    ??????????????????????????????????????????
    <command>yum</command> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>
<screen>
<command>yum groupinfo "Games and Entertainment"</command>
</screen>
  <para>
    ?????????????????????????????????????????????????????????????????? <command>yum</command>
    ??????????????????????????????????????????????????????????????????????????????????????????????????????
    <para>
      <ulink
	url="http://fedora.redhat.com/docs/yum/">http://fedora.redhat.com/docs/yum/</ulink>
    </para>
  </para>
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE feedback-ja_JP.xml ---
  <section id="sn-test" os="test">
    <title>??????????????????????????????????????????????????????</title>

    <para>
    (???????????????????????????&DISTRO; ???????????????????????????????????????????????????????????????)
    </para>

    <para>
    ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    ???????????????????????????
    </para>

    <para>%%% https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=<replaceable>&lt;????????????&gt;</replaceable> %%% </para>

    <para>
    ???????????? URL ????????????????????? URL
    ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    ???????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>

    <para>
    ????????????????????????????????????????????????????????????????????????????????????????????? URL
    ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????HTML
    ????????????????????? &mdash; ?????????????????????????????? URL ????????????????????????
    </para>

    <para><ulink
    url="https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Core&amp;op_sys=Linux&amp;version=devel&amp;component=fedora-release&amp;component_text=&amp;rep_platform=All&amp;priority=normal&amp;bug_severity=normal&amp;bug_status=NEW&amp;assigned_to=&amp;cc=&amp;estimated_time=0.0&amp;bug_file_loc=http%3A%2F%2F&amp;short_desc=FC3%20release%20notes%20--%20&amp;comment=Please%20add%20a%20descriptive%20phrase%20to%20the%20summary%2C%20and%20more%20in-depth%0D%0Adescription%20here%20%28be%20sure%20to%20note%20any%20arch-specific%20issues%29%3A%0D%0A%0D%0A&amp;keywords=&amp;dependson=&amp;blocked=114398&amp;maketemplate=Remember%20values%20as%20bookmarkable%20template&amp;form_name=enter_bug">????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</ulink></para>

    <para>
    ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para><ulink
    url="http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398">http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398</ulink></para>

    <para>
    ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
    ??????????????????????????????????????????????????????????????????????????????
    </para>
  </section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE file-servers-ja_JP.xml ---
<section id="sn-file-servers">
  <title>????????????????????????</title>
  <caution>
    <title>????????????????????????????????????</title>
    <para>
      ????????????????????? &DISTRO; &DISTROVER;
      ???????????????????????????????????????????????????
    </para>
  </caution>
  <para>
    ???????????????????????????????????????????????????????????????????????????????????????
    HTTP (Web) ????????????????????? Samba (Windows) ????????????????????????????????????????????????
    <xref linkend="sn-web-servers"/> ???
    <xref linkend="sn-samba"/>
    ??????????????????????????????
  </para>
  <section id="sn-file-servers-netatalk-suite">
    <title>Netatalk (Macintosh ??????)</title>
    <para>
      AppleTalk ????????????????????????????????????????????? Macintosh
      ??????????????? Linux ????????????????????????????????????????????????????????????????????????
      Netatalk ??????????????????????????????
    </para>
    <section id="sn-file-servers-netatalk-package">
      <title><filename>netatalk</filename></title>
      <para>
	&DISTRO; &DISTROVER; ??? Netatalk ?????????????????? 2 ?????????
	<emphasis>Netatalk ?????????????????? 1 ????????????????????? 2
	??????????????????????????????????????????????????????????????????????????????</emphasis>???
	Netatalk ??????????????? 2 ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
      <para>
	?????????????????????????????? Netatalk ?????????????????????????????????????????????
      </para>
      <para>
	<ulink
	  url="http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html">http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html</ulink>
      </para>
      <para>
	??????????????????????????? <filename>netatalk</filename>
	???????????????????????????????????????
	<filename>/usr/share/doc/netatalk-<replaceable>version</replaceable>/doc/htmldocs/upgrade.html</filename>, 
	?????????
	<filename>/usr/share/doc/netatalk-<replaceable>version</replaceable>/doc/Netatalk-Manual.pdf</filename> 
	(??????????????? 25, ???????????? 33 ????????????)
	??????????????????????????????
      </para>
    </section>
  </section>
</section>

<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE hardware-reqs-ja_JP.xml ---
<section id="sn-hardware-reqs">
  <title>????????????????????????</title>
  <para>
    ????????????&DISTRO; &DISTROVER;
    ????????????????????????????????????????????????????????????????????????????????????
  </para>
  <note>
    <title>??????</title>
    <para>
      ??????????????????????????????????????????????????????????????????????????? /
      ????????????????????????????????????????????? /
      ???????????????????????????????????????????????????????????? /
      ?????????????????????????????????????????????????????????
    </para>
  </note>
<!-- Something like this needs to be said, but this really needs a -->
<!-- better treatment and probably a new section devoted to help resources.
  <para>
    This section does not address hardware compatability.  To find out
    about using a specific piece of hardware with &FC; &LOCALVER; 
  </para>
-->
  <section>
    <title>CPU ??????</title>

    <para>
      ?????????????????? &DISTRO; &DISTROVER;
      ????????????????????? CPU ????????????????????????
    </para>

    <note arch="x86">
      <title><!-- <remark os="test">(x86)</remark>--> ??????</title>

      <para><!-- <remark os="test">(x86)</remark> -->
	????????? CPU ????????????Intel ??????????????????????????????????????????????????????
	?????????????????????????????????AMD???Cyrix???VIA ???????????????????????????????????????????????????
	Intel ????????????????????????????????????????????????????????????????????????
	&DISTRO; ?????????????????????????????????
      </para>
    </note>

    <itemizedlist arch="x86">
      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> ?????????:
	  Pentium ????????? &mdash;
	  &FC; &LOCALVER; ??????Pentium 4????????????????????????CPU
	  ???????????????????????????????????????????????????????????? CPU???????????? Pentium,
	  Pentium Pro, Pentium II, Pentium III ??? AMD ??? VIA
	  ????????????????????????????????????????????????????????????
	  Pentium ?????????????????????????????????????????????Pentium
	  ???????????????????????????????????????????????????????????????????????????????????????????????????
	  Pentium 4 ??????????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  <!-- <remark os="test">%%% <ulink
	  url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254</ulink> 
	  %%%</remark> -->
	</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> -->
	  ???????????????????????????????????????: 200 MHz Pentium ???????????????
	</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> -->
	  ?????????????????????????????????????????????: 400 MHz Pentium II ???????????????
	</para>
      </listitem>
    </itemizedlist>

    <itemizedlist arch="x86_64">
      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> -->
	  AMD64 ??????????????????Athlon64 ??? Opteron ????????????
	</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> -->
	  <trademark class="registered">Intel</trademark>
	  Extended Memory 64 Technology (<trademark
	    class="registered">Intel</trademark> EM64T)
	  ????????????????????? Intel ???????????????
	  </para>
      </listitem>
    </itemizedlist>
  </section>
  <section>
    <title>??????????????????????????????????????????</title>

    <para>
      ?????????????????? &DISTRO; &DISTROVER;
      ????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <note>
      <title>??????</title>

      <para>
	?????????????????????????????????????????????????????????&DISTRO; &DISTROVER;
	????????????????????????????????????<emphasis>???</emphasis>???????????????????????????
	?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	???????????????????????????CD-ROM 1 ?????????<filename>/Fedora/base/stage2.img</filename>
	???????????????????????????????????????????????? <filename>/var/lib/rpm</filename>
	?????????????????????????????????????????????
      </para>

        <!-- Update these figures every release -->

      <para>
	??????????????????????????????????????????????????????????????? 90MB
	??????????????????????????????????????????????????????????????? 175MB
	?????????????????????????????????????????????????????????????????????
      </para>

      <para>
	?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	5% ?????????????????????????????????????????????????????????????????????
      </para>
    </note>

      <!-- Get actual numbers from installer, multiply by 1.1, and round -->
      <!-- up to the nearest 10MB or .1GB -->
    <para>
      ?????????????????? 32-bit x86 ????????????????????????????????????:
    </para>
    <itemizedlist arch="x86">
      <listitem>
	<para><!-- <remark os="test">(x86)</remark> -->
	  ??????????????????????????????????????????: 620MB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> -->
	  ?????????: 1.1GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> -->
	  ?????????????????????????????????: 2.3GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> -->
	  ???????????????????????????: 3.0GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> -->
	  ??????????????????????????????????????????: 6.9GB</para>
      </listitem>
    </itemizedlist>
    <para>
      ?????????????????? 64-bit x86 ????????????????????????????????????:
    </para>
    <itemizedlist arch="x86_64">
      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> -->
	  ??????????????????????????????????????????: 900MB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> -->
	  ?????????: 1.5GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> -->
	  ?????????????????????????????????: 2.7GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> -->
	  ???????????????????????????: 3.4GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> -->
	  ??????????????????????????????????????????: 7.5GB</para>
      </listitem>
    </itemizedlist>
  </section>

  <section>
    <title>???????????????</title>

    <para>
      ??????????????????&DISTRO; &DISTROVER;
      ???????????????????????????????????????????????????????????????
    </para>
    <para>
      ?????????????????? 32-bit x86 ????????????????????????????????????:
    </para>
    <itemizedlist arch="x86">
      <listitem>
	<para><!-- <remark os="test">(x86)</remark> -->
	  ??????????????????????????????????????????: 64MB
	</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> -->
	  ????????????????????????????????????????????????: 192MB
	</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> -->
	  ????????????????????????????????????????????????: 256MB
	</para>
      </listitem>
    </itemizedlist>
    <para>
      ?????????????????? 64-bit x86 ????????????????????????????????????:
    </para>
    <itemizedlist arch="x86_64">
      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> -->
	  ??????????????????????????????????????????: 128MB
	</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> -->
	  ????????????????????????????????????????????????: 256MB
	</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> -->
	  ????????????????????????????????????????????????: 512MB
	</para>
      </listitem>
    </itemizedlist>
  </section>
  <section id="sn-hardware-reqs-ppc">
    <title>PPC ????????????????????????</title>
    <para>
      ??????????????????&FC; &LOCALVER; ??? PowerPC (PPC)
      ????????????????????????????????????????????????????????????????????????????????????
    </para>
    <itemizedlist>
      <listitem>
	<para>
	  <!--<remark os="test">(ppc)</remark> -->
	  ?????????: PowerPC G3 / POWER4
	</para>
      </listitem>
      <listitem>
	<para>
	  <!--<remark os="test">(ppc)</remark> -->
	  &FC; &LOCALVER; ???
	  <quote>New World</quote> ???????????????
	  1999 ?????????????????????????????? Apple Power Macintosh
	  ?????????????????????????????????
	  ?????? 64-bit G5 ??????????????????IBM eServer pSeries
	  ??? POWER ??????????????????????????????????????????
	  ?????????32-bit ??? IBM RS/6000 ???????????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  <!--<remark os="test">(x86)</remark> -->
	  ???????????????????????????????????????: 233 MHz G3 ??????
	</para>
      </listitem>
      <listitem>
	<para>
	  <!-- <remark os="test">(ppc)</remark> --> 
	  ?????????????????????????????????????????????: 400 MHz G3 ??????
	</para>
      </listitem>
    </itemizedlist>
  </section>
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE i18n-ja_JP.xml ---
<section id="sn-i18n">
  <title>????????? (i18n)</title>
  <para>
    SCIM ????????????????????????????????????????????????????????????
    ????????????????????????
  </para>
  <section>
    <title>??????????????????</title>
    <para>
      ??????????????? &DISTRO;
      ?????????????????????????????????????????????????????????????????????????????????
    </para>
    <section>
      <title>IIIMF ??????????????????</title>
      <para>
	IIIMF ????????????????????????/????????????????????????????????????????????????????????????
	(Internet/Intranet Input Method Framework) ?????????
	&FC; &LOCALVER; ?????? <filename>iiimf</filename>
	????????????????????????????????? 12.2 ???????????????????????????
      </para>
      <variablelist>
	<varlistentry>
	  <term>???????????????????????????</term>
	  <listitem>
	    <para>
	      <filename>iiimf</filename>
	      ?????????????????????????????????????????????????????????????????????????????????????????????
	    </para>
	    <para>
	      IIIMF ????????????????????? <filename>/usr/sbin/htt</filename> ??????
	      <filename>/usr/bin/iiimd</filename>
	      ?????????????????????????????? XIM ???????????????????????????????????????
	      <filename>httx</filename> ??????
	      <filename>iiimx</filename> ?????????????????????????????????
	      <filename>init.d</filename>
	      ?????????????????????????????????????????????????????????
	      ????????? <filename>iiim</filename> ?????????
	      ??????????????????????????????????????????
	      <filename>/etc/iiim/</filename> ?????????????????????????????????
	    </para>
	    <para>
	      Language Engine (LE) ????????????????????????
	      LE ?????????????????????????????????
	      <filename>${libdir}/iiim/le/<filename>&lt;LE_NAME&gt;</filename>/</filename>
	      ????????????????????????????????????????????????
<filename>/var/lib/iiim/le/<replaceable>&lt;LE_NAME&gt;</replaceable>/</filename>
	      ???????????????????????????????????????????????????????????????????????????
	    </para>
	    <para>
	      ????????????????????????????????????????????????????????????????????????????????????????????????
	      Fedora IIIMF FAQ
	    </para>
	    <para>
	      <ulink
		url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>.
	    </para>
	    <para>
	      ??????????????????????????????
	    </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term>???????????????</term>
	  <listitem>
	    <para>
	      ????????????????????????????????????
	      <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo> 
	      ????????????????????????????????????????????????????????????
	      <command>iiimf-le-tools</command>
	      ???????????????????????????
	      ???????????????????????????????????? GTK2 ??????????????????????????????????????????????????????????????????
	      ???????????? XIM ?????????????????????????????????????????????????????????X ????????????????????????????????????????????????????????????
	      ?????????????????????????????????????????????????????? <ulink
		url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>
	      ????????? IIIMF FAQ ??????????????????????????????
	    </para>
	    <para>
	      ???????????????X ????????????????????????????????????????????????????????????????????????
	      ??????????????????
	      <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>
	      ???????????????????????????'&lt;Control&gt;@' ????????????
	      '&lt;Control&gt;at' ???????????????????????????????????????
	    </para>
	    <para>
	      &SEL; ??? enforcing ??????????????????&SEL;
	      ????????????????????????????????????????????????????????????????????????????????????????????????
	      ??????????????????????????????????????????????????????????????????????????????????????????
	    </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term>Qt ???????????????</term>
	  <listitem>
	    <para>
	      <filename>iiimf</filename> ???????????? QT immodule ???????????????????????????
	      ?????? immodule ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	      ???????????????QT ????????????????????????????????????????????????
	      IIMF ????????????????????????????????? XIM ?????????????????????
	    </para>
	    <para>
	      QT ??????????????????????????? immodule ???????????????????????????????????????
	      <filename>iiimf-qt</filename>
	      ?????????????????????????????????????????????????????????????????????????????????????????????
	      ??????????????????????????????
	      button-3????????????????????????????????????????????????
	      <guisubmenu>Select Input Method</guisubmenu>
	      ???????????????????????????
	      <guimenuitem>iiimqcf</guimenuitem> ??????????????????????????????
	    </para>
	  </listitem>
	</varlistentry>
      </variablelist>
    </section>
  </section>
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE install-notes-ja_JP.xml ---
<section id="sn-anaconda">
  <title>??????????????????????????????</title>
  <para>
    ??????????????????Anaconda???&DISTRO; ??????????????????????????????????????????????????????????????????&DISTRO;
    &DISTROVER; ??????????????????????????????????????????????????????????????????????????????
  </para>
  <note>
    <title>??????</title>
    <para>
      ?????????&DISTRO; &DISTROVER; ??? DVD ISO ?????????????????????????????????????????????????????????????????????????????????????????????????????? 2GB ????????????????????????????????????????????????????????????????????????????????????????????????????????????
      ????????????<command>wget</command> ???
      <computeroutput>File size	limit exceeded</computeroutput>
      (???????????????????????????????????????) ?????????????????????????????????
    </para>
    <para>
      ?????????????????????????????????????????? <command>curl</command>
      ??? <command>ncftpget</command> ??????????????????????????????2GB
      ?????????????????????????????????????????????????????????????????????
    </para>
    <para>
      Bittorrent ????????????????????????????????????????????????????????????????????????
      torrent ???????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      <ulink
	url="http://torrent.fedoraproject.org/">http://torrent.fedoraproject.org/</ulink>
    </para>
    <para>
      ??????????????????????????????
    </para>
  </note>
  <section id="sn-install-notes-ppc">
    <title>PPC ????????????????????????????????????</title>
    <section>
      <title>PPC ????????????????????????</title>
      <para>
	???????????????  &DISTRO; &DISTROVER; ??? PowerPC (PPC)
	???????????????????????????????????????????????????????????????????????????????????????
      </para>
      <itemizedlist>
	<listitem>
	  <para>?????????: PowerPC G3 / POWER4 </para>
	</listitem>
	<listitem>
	  <para> &FC; &LOCALVER; ??? "New World" ???????????????
	    1999 ?????????????????????????????? Apple Power Macintosh
	    ?????????????????????????????????
	  </para>
	</listitem>
	<listitem>
	  <para>&DISTRO; &DISTROVER; ??? IBM eServer pSeries, IBM
	    RS/6000, Genesi Pegasos II ???????????????????????????????????????
	  </para>
	</listitem>
	<listitem>
	  <para>???????????????????????????????????????: 233 MHz G3
	    ?????????64MB RAM???
	  </para>
	</listitem>
	<listitem>
	  <para>?????????????????????????????????????????????: 400 MHz G3 ?????????
	    128MB RAM???
	  </para>
	</listitem>
      </itemizedlist>
      <para>
	&FC; ??? DVD ????????????????????? CD
	???????????????????????????????????????????????????????????????????????????????????????????????????
	????????????????????????????????? CD ??????????????? DVD ????????????????????? CD
	??? <filename>images/</filename> ??????????????????????????????????????????
	???????????????????????????????????????????????????????????????????????????????????????
      </para>
      <variablelist>
	<title>??????????????????????????????????????????????????????</title>
	<varlistentry>
	  <term>Apple Macintosh </term>
	  <listitem>
	    <para>
	      ???????????????????????? 32-bit ????????? 64-bit
	      ???????????????????????????????????????????????????????????????????????????????????????
	      ??????????????????????????????????????????????????????????????????????????????????????????
	      <command>apmud</command> ????????????????????????????????????
	      &FEX; ??????????????????
	      &FC; ???????????? &FEX; ???????????????????????? yum ??????????????????????????????
	      ???????????????????????? <command>yum install apmud</command>
	      ???????????????????????? <command>apmud</command>
	      ????????????????????????????????????
	    </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term>64-bit IBM eServer pSeries (POWER4/POWER5)</term>
	  <listitem>
	    <para>
	      CD ???????????????????????? OpenFirmware ??????????????????????????????????????????
	      (<command>yaboot</command>)
	      ??????????????? 64-bit ??????????????????????????????????????????
	    </para>
	  </listitem>        
	</varlistentry>
	<varlistentry>
	  <term>32-bit CHRP (IBM RS/6000 and others)</term>
	  <listitem>
	    <para>
	      CD ???????????????????????? OpenFirmware ?????????????????????
	      <prompt>boot:</prompt> ????????????????????????????????????
	      <filename>linux32</filename> ???????????????32-bit
	      ???????????????????????????????????????????????????
	      ?????????????????? 64-bit
	      ??????????????????????????????????????????????????????????????????????????????
	    </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term>Genesi Pegasos II</term>
	  <listitem>
	    <para>
	      &DISTRO; &DISTROVER; ???????????????ISO9660
	      ?????????????????????????????????????????????????????? Pegasos
	      ?????????????????????????????????????????????????????????????????????
	      ?????????????????????????????????????????????????????????????????????????????????????????????
	      OpenFirmware ?????????????????????????????????????????????????????????
	    </para>
<screen>
<command>boot cd: /images/netboot/ppc32.img</command> 
</screen>          
	    <para>
	      ????????????????????????????????? &FC; ?????????????????????????????????
	      Pegasos ?????? OpenFirmware ????????????????????????????????????????????????
	      ???????????????????????????????????????
	      <envar>boot-device</envar> ??? <envar>boot-file</envar>
	      ????????????????????????????????????????????????
	    </para>
	  </listitem>        
	</varlistentry>
	<varlistentry>
	  <term>????????????????????????</term>
	  <listitem>
	    <para>
	      ??????????????????????????????????????? ramdisk
	      ??????????????????????????????????????????????????????????????????
	      images/netboot/ ??????????????????????????????????????????
	      ???????????? TFTP
	      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	    </para>
	    <para>
	      <command>yaboot</command> ??????????????? IBM eServer pSeries
	      ??? Apple Macintosh ???????????? tftp ?????????????????????????????????
	      &FED; ??????????????????????????????????????????????????????
	      yaboot ????????????????????????????????????
	    </para>
	</listitem>
	</varlistentry>
      </variablelist>
    </section>
  </section>
  <section>
    <title>Anaconda ??????????????????</title>

    <itemizedlist>
      <listitem>
	<para>
	  &DISTRO; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ????????????CD???DVD??????????????????????????? ISO ???????????????NFS
	  ??? ISO ????????????????????????????????????????????????????????????
	  &RH; ????????????????????????????????????????????????????????????????????????????????????????????????
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? CD ??????????????????????????????
	  ?????????????????????????????????<prompt>boot:</prompt> ??????????????????
	  <command>linux mediacheck</command> ??????????????????????????????
	</para>
	<para>
	  <command>mediacheck</command> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????ISO
	  ???????????????????????????????????????????????????????????????
	  (padding) ?????????????????????????????????????????????????????????
	  <command>mediacheck</command> ????????????????????????????????????
	</para>
<screen>
linux ide=nodma
</screen>
	<para>
	  ???????????????????????????????????????????????????
	</para>

	<para>
	  ??????????????????????????????????????????<command>sha1sum</command>
	  ?????????????????????????????????????????????????????????????????????
	  ?????????????????????????????????????????????ISO ????????????????????????????????????????????????????????????
	</para>
      </listitem>
      <listitem arch="x86">
<!--	<remark os="test">%%% <ulink
	    url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654</ulink> 
	  %%%</remark>
-->
	<para>
	  <!-- <remark os="test">(x86)</remark> -->
	  &DISTRO; ??????????????????????????????????????????????????????????????????????????????????????????????????????
	  ????????? <prompt>boot:</prompt> ??????????????????
	  <command>memtest86</command> ???????????????????????????????????????
	  ??????????????????Memtest86???????????????????????????????????????????????????????????????????????????????????????
	  Memtest86 ?????????????????????????????????<keycap>Esc</keycap>
	  ??????????????????????????????????????????????????????
	</para>
	<para>
	  <!-- <remark os="test">(x86)</remark> -->
	  ??????: ??????????????????????????????????????????CD-ROM 1 (????????? rescue CD-ROM)
	  ????????????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
<!--	<remark os="test">%%% <ulink
	    url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627</ulink> 
	  %%%</remark>
-->
	<para>
	  &DISTRO; &DISTROVER; ??????????????????????????? FTP???HTTP
	  ?????????????????????????????????????????????
	  ????????????????????????????????????????????? RAM ???????????????????????????????????????128MB
	  ????????? RAM ??????????????????????????????????????? CD-ROM 1 
	  ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  128MB ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
      </listitem>
    </itemizedlist>
  </section>
  <section>
    <title>????????????????????????????????????</title>
    <itemizedlist>
      <listitem>
	<para>
	  ?????????????????????????????????????????? LCD
	  ????????????????????????????????????????????????&DISTRO;
	  ??????????????????????????????????????????????????????????????????????????????????????????
	  ?????????????????????????????????????????????????????????????????????????????????
	  "<command>nofb</command>" ?????????????????????????????????????????????
	</para>

	<note>
	  <title>???</title>
	  <para>
	    ???????????????????????????????????????????????????????????????????????????????????????"<command>nofb</command>"
	    ?????????????????????????????????????????????????????????????????????
	    ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	</note>   
      </listitem>
      <listitem arch="x86">
	<para>
<!--	  <remark os="test">(x86)</remark> -->
	  ?????? Sony <trademark class="registered">VAIO</trademark>
	  ???????????????????????????????????????&DISTRO; ??? CD-ROM
	  ??????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
<screen>
<!-- <remark os="test">(x86)</remark> -->
<command>pci=off ide1=0x180,0x386</command>
</screen>
	<para>
	  <!-- <remark os="test">(x86)</remark> -->
	  ????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????????????????????????????????????????????????????&DISTRO;
	  ??????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  ??????????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????????????? X ???????????????????????????????????????????????????????????????????????????
	  ??????????????????????????? 119474 ??????????????????????????????
	</para>
	<para>
	  <ulink
	    url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474</ulink>
	</para>
      </listitem>
      <listitem arch="x86">
	<para>
	  <!-- <remark os="test">(x86)</remark> -->
	  ???????????????????????????????????????&FP; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????&RHL;
	  7.<replaceable>&lt;x&gt;</replaceable>, 8.0, 9 ?????????
	  &FC; 1, 2, 3
	  ????????????????????????????????????????????????????????????????????????????????????
	  ????????? Ximian GNOME ?????????
	</para>
	<para>
	  ?????????????????????????????? &RHL; (????????? &PROJ;) ??? RPM ??????Ximian
	  ??? RPM ??????????????????????????????????????????
	  ???????????????????????????????????????????????????
	  ????????????????????????????????????????????????????????????????????????????????????
	</para>
	<orderedlist numeration="loweralpha">
	  <listitem>
	    <para>
	      <!-- <remark os="test">(x86)</remark> -->
	      &DISTRO; ???????????????????????????????????????Ximian GNOME??????????????????
	    </para>
	  </listitem>
	  <listitem>
	    <para>
	      <!-- <remark os="test">(x86)</remark> -->
	      ??????????????????????????????????????????????????? Ximian GNOME ?????????????????????????????????
	    </para>
	  </listitem>
	  <listitem>
	    <para>
	      <!-- <remark os="test">(x86)</remark> -->
	      ????????????????????????????????????????????????????????????????????? Ximian ??? RPM
	      ??????????????????????????????????????? &DISTRO; ??? RPM ?????????????????????
	    </para>
	  </listitem>
	</orderedlist>	
	<para>
	  <!-- <remark os="test">(x86)</remark> -->
	  ???????????????????????????????????????????????????????????????????????????????????????<emphasis>??????????????????????????????</emphasis>???
	  ???????????????????????????????????????GNOME ???????????????????????????????????????????????????
	</para>
      </listitem>
    </itemizedlist>
  </section>
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE intro-ja_JP.xml ---
<section id="sn-intro">
  <title>????????????</title>
  <para>
    &PROJ; ??????&RH;
    ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    &DISTRO; ??????????????????
  </para>
  <note>
    <title>??????</title>
    <para>
      &FC; ????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      &FC; ??????&FORMAL-RHI;??????????????????????????????????????????????????????????????????
    </para>
  </note>
  <para>
    ???????????????????????????<xref linkend="sn-overview"/>??????????????????????????????
  </para>
  <para>
    ???????????????????????????????????????????????????????????????<ulink
      url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>
    ????????????????????????
    ???????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>
  <para>
    ?????????????????????????????????????????????????????????????????????????????????????????????
    <ulink url="&BUG-URL;">bugzilla ??????????????????</ulink>
    ?????????????????????????????????????????????
  </para>
<!-- This is just to tweaky to HTML and will make people think it's b0rked
  <para>
    <ulink
    url="&BUG-URL;">&BUG-URL;</ulink>
  </para>
-->
  <para>
    <ulink url="&TINY-BUG-URL;">&TINY-BUG-URL;</ulink> ?????????
    bugzilla ??????????????????????????????????????????
  </para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
coding: utf-8-unix
End:
-->


--- NEW FILE java-package-ja_JP.xml ---
<section id="sn-java-packages">
  <title>Java ????????????????????????</title>
  <caution>
    <title>????????????????????????????????????</title>
    <para>
      ????????????????????? &DISTRO; &DISTROVER; ???????????????????????????????????????????????????
    </para>
  </caution>
  <para>
    &FC; &LOCALVER; ??????????????????Sun ???????????????????????????
    Java RPM ???????????????????????????????????????????????????
    ?????? RPM ??? &FC; &LOCALVER; ??????????????????????????????????????????????????????????????????
    <computeroutput>Provides</computeroutput>
    ??????????????????
    ??????????????????Sun Java ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>
  <para>
    &FC; &LOCALVER; ??????????????? jpackage.org ??????????????? RPM ?????????????????????Sun
    Java tar ??????????????????????????? <filename>/opt</filename>
    ?????????????????????????????????????????????
    <!-- ???????????????????????????Sun Java 1.5 ??????????????????????????? -->
  </para>
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE kernel-ja_JP.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "These FAKE ENTITIES are just to make editing easier" >
 <!ENTITY FC            "FC"                                  >
 <!ENTITY LOCALVER      "LOCALVER"                            >
 <!ENTITY DISTRO        "DISTRO"                              >
 <!ENTITY DISTROVER     "DISTROVER"                           >

]>
-->
<section id="sn-kernel">
  <title>
    Linux ????????????
  </title>
  <section id="sn-kernel-lotsa">
    <title>???????????????</title>
    <para>
      ?????????????????????????????????????????? 2.6.11 ?????????????????????????????????????????????
      &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????
      ??????????????????&FC; ??????????????????
      <ulink
	url="http://www.kernel.org"><filename>kernel.org</filename></ulink> 
      ???????????????<firstterm></firstterm>????????????????????????????????????????????????
    </para>
    <para>
      &FC;
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
<screen width="56">
<command>rpm <parameter class="option">-qpl</parameter> <filename>kernel-<replaceable>???????????????</replaceable>.src.rpm</filename></command>
</screen>
  </section>
  <section id="sn-kernel-flavors">
    <title>?????????????????????</title>
    <para>
      &FC; ????????????????????????????????????????????????
    </para>
    <itemizedlist>
      <listitem>
        <para>
	  ????????????????????????
	  ????????????????????????<abbrev>SMP</abbrev> ????????????
	  ????????????????????????
	  <filename>kernel-devel-<replaceable>???????????????</replaceable>.<replaceable>?????????????????????</replaceable>.rpm</filename> 
	  ??????????????????????????????????????????
        </para>
      </listitem>
      <listitem>
        <para>
	  <wordasword>Xen</wordasword>
	  ???????????????????????????????????????????????????????????????
	  ????????????????????????
	  <filename>kernel-xen0-devel-<replaceable>???????????????</replaceable>.<replaceable>?????????????????????</replaceable>.rpm</filename> 
	  ??????????????????????????????????????????
        </para>
      </listitem>
    </itemizedlist>
    <para>
      ????????????????????????????????????????????????????????????????????????????????????????????????
      ???????????????
      <filename>/usr/src/kernels/<replaceable>???????????????</replaceable>[-xen0]-<replaceable>arch</replaceable>/</filename> 
      ??????????????????????????????????????????
      ???????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
<screen width="56">
<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-devel[-xen0]-<replaceable>???????????????</replaceable>.<replaceable>arch</replaceable>.rpm</filename></command> 
</screen>
    <tip>
      <title>Linux ???????????????????????????????????????????????????</title>
      <para>
	Linux ???????????????????????????????????????????????????????????????????????????????????????????????????????????????
	<filename>/usr/src/linux</filename>
	?????????????????????????????????????????????????????????????????????????????????????????????
	???????????????????????????????????????????????????????????????&FC;
	??????????????????????????????????????????????????????????????????????????????
	??????????????????????????????????????????????????????????????????????????????????????????
      </para>
<screen width="56">
<command>ln <parameter class="option">-s</parameter> <filename>/usr/src/kernels/kernel-<replaceable>???????????????</replaceable></filename> <filename>/usr/src/linux</filename></command>
</screen>
      <para>
	?????????????????????
      </para>
    </tip>
  </section>
  <!--
  <tip>
    <title>Using <command>yum</command> to Uninstall Kernel
    Packages</title>
    <para>
      &FC; &LOCALVER; contains support for clustering systems using CMAN and GFS.
      These kernels require assistance from some user-space packages.
      These packages are not removed when using <command>rpm -e</command> to uninstall older versions of the kernel packages.
    </para>
    <para>
      When using <command>rpm -e kernel-<replaceable>version</replaceable> </command> to uninstall the kernel, you must also remove the assisting user-space packages.  You may wish to consider a dependecy resolving tool such as <command>yum remove kernel-<replaceable>version</replaceable> </command>.
      This automatically removes any dependant packages.
    </para>
  </tip>
  -->
  <section id="sn-kernel-exploding">
    <title>
      ????????????????????????????????????
    </title>
    <para>
      &DISTRO; &DISTROVER; ??????????????????????????????????????????????????????
      <filename>kernel-source</filename> ????????????????????????????????????
      ?????????????????????<xref
	linkend="sn-kernel-flavors"/>???????????????????????????????????????????????????????????????????????????
      &FC; ????????????????????????<filename>kernel</filename> <filename>.src.rpm</filename>
      ??????????????????????????????????????????????????????
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <important>
    <title>??????????????????????????????????????????????????????????????????</title>
      <para>
	?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	????????????????????????<replaceable>version</replaceable>
	?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
<screen width="56">
<command>uname <parameter class="option">-r</parameter></command>
</screen>
    </important>
    <procedure id="sn-kernel-exploding-steps">
      <step>
        <para>
	  ?????????????????????????????????
	  <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename> 
	  ?????????????????????
        </para>
        <itemizedlist>
          <listitem>
            <para>
	      ????????? <wordasword>SRPMS</wordasword>
	      <abbrev>CD</abbrev> <filename>iso</filename> ???????????????
	      <filename>SRPMS</filename> ??????????????????
              </para>
          </listitem>
          <listitem>
            <para>
	      ?????????????????????????????????????????????????????? FTP ?????????
            </para>
          </listitem>
          <listitem>
            <para>
	      ????????????????????????????????????
            </para>
<screen width="56">
<command>up2date <parameter class="option">--get-source</parameter> <filename>kernel</filename></command>
</screen>
          </listitem>
        </itemizedlist>
      </step>
      <step>
        <para>
	  ??????????????????????????????
	  <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename> 
	  ?????????????????????????????????
        </para>
<screen width="56">
<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
</screen>
        <para>
	  ????????? <abbrev>RPM</abbrev> ????????????
	  <filename>/usr/src/redhat/SOURCES</filename> ???
	  <filename>/usr/src/redhat/SPECS</filename>
	  ??????????????????????????????
        </para>
      </step>
      <step>
        <para>
	  ???????????????????????????????????????????????????????????????
        </para>
<screen width="56">
<command>cd <filename>/usr/src/redhat/SPECS</filename></command>
<command>rpmbuild <parameter class="option">-bp --target $(arch)</parameter> <filename>kernel-2.6.spec</filename></command>
</screen>
        <para>
	  ?????????????????????????????????
	  <filename>/usr/src/redhat/BUILD/kernel-</filename><replaceable>version</replaceable> 
	  ????????????????????????????????????????????????
	  ?????????
	  <filename>linux-</filename><replaceable>version</replaceable> 
	  ????????????????????? <filename>/usr/src</filename>
	  ?????????????????????????????????????????????????????????
	  ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
        </para>
<screen width="56">
<command>cd <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
<command>mv <filename>linux-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
<command>cd <filename>/usr/src</filename></command>
<command>ln <parameter class="option">-s</parameter> <filename>./linux-<replaceable>version</replaceable></filename> <filename>linux</filename></command>
<command>cd <filename>/usr/src/linux</filename></command>
</screen>
      </step>
      <step>
        <para>
	  &DISTRO; &DISTROVER; ???????????????????????????????????????
	  <filename>configs/</filename> ??????????????????????????????????????????
	  ???????????????i686 SMP ???????????????????????????
	  <filename>configs/kernel-<replaceable>version</replaceable>-i686-smp.config</filename>
	  ??????????????????
	  ????????????????????????????????????????????????????????????????????????????????????????????????????????????
        </para>
<screen width="56">
<command>cp <filename>configs/<replaceable>???????????????????????????</replaceable></filename> <filename>.config</filename></command>
</screen>
        <para>
	  ????????????????????????????????????????????? <filename>.config</filename>
	  ???????????????
	  <filename>/lib/modules/</filename><replaceable>???????????????</replaceable><filename>/build/.config</filename> 
	  ??????????????????
        </para>
      </step>
      <step>
        <para>
	  ???????????????????????????????????????????????????????????????????????????????????????
	  ??????????????? <command>uname -r</command>
	  ??????????????????????????????????????????????????????
	  ?????????????????????????????????????????? <filename>Makefile</filename>
	  ?????????????????????????????????????????????
	  ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  <filename>Makefile</filename> ??????????????????????????????
	  ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????
	  <filename>Makefile</filename>
	  ???????????????????????????????????????
        </para>
        <para>
	  ???????????? <command>uname -r</command> ???????????? <systemitem
	    class="osname">2.6.11-1.234_FC4</systemitem>
	  ??????????????????????????????<systemitem
	    class="macro">EXTRAVERSION</systemitem> ?????????
        </para>
<screen width="60">
EXTRAVERSION = -prep
</screen>
        <para>
	  ??????
	</para>
<screen width="60">
EXTRAVERSION = -1.234_FC4
</screen>
        <para>
	  ?????????????????????
	  ??????????????????????????????????????????????????????????????????
        </para>
      </step>
      <step>
        <para>
          ????????????????????????????????????????????????
        </para>
<screen width="56">
<command>make oldconfig</command>
</screen>
      </step>
    </procedure>
    <para>
      ???????????????????????????????????????????????????????????????
    </para>
  </section>
  <section id="sn-kernel-3rdparty">
    <title>??????????????????????????????????????????</title>
    <para>
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<emphasis>?????????????????????</emphasis>???
    </para>
    <para>
      ????????????<filename>foo.ko</filename>
      ??????????????????????????????????????????<filename>foo.c</filename>
      ?????????????????????????????????????????????????????????????????????????????????????????????
      <filename>Makefile</filename>????????????????????????
    </para>
<programlisting width="56">
obj-m := foo.o

KDIR  := /lib/modules/$(shell uname -r)/build
PWD   := $(shell pwd)

default:
    $(MAKE) -C $(KDIR) M=$(PWD) modules
</programlisting>
      <para>
      ????????? <filename>foo.ko</filename> ??????????????????????????????????????????
      <command>make</command> ?????????????????????????????????
    </para>
  </section>
  <section id="sn-kernel-coop">
    <title>?????????????????????????????????????????????</title>
    <para>
      &DISTRO; ???????????????????????????????????????????????????????????????
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      <command>rpm -e
	kernel-<replaceable>version</replaceable></command>
      ??????????????????<emphasis>???????????????</emphasis>???
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      ?????????????????????????????????????????????????????????????????????????????????????????????
      <command>rpm -e</command> ?????????????????????????????????<command>yum</command>
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      <command>yum remove
	kernel-<replaceable>version</replaceable></command>
      ?????????????????????
    </para>
  </section>
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE legacy-ja_JP.xml ---
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE misc-server-ja_JP.xml ---
<section id="sn-misc-server-notes">
  <title>?????????</title>
  <para>
    ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>
  <section id="sn-misc-notes-openoffice">
    <title>OpenOffice ??????????????????????????????????????????????????????</title>
    <para>
      ????????????????????????????????????????????????????????? <emphasis role='strong'>?????????</emphasis>????????????????????????????????????????????????????????????????????????????????? <ulink
	url='/OpenOffice'>OpenOffice</ulink> ??????????????????????????????????????????????????????????????????
    </para>
    <para>
      ???????????????????????????????????????????????????????????????<emphasis
      role='strong'>??????</emphasis>???????????????????????????????????????
    </para>
<screen>
<command>rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
  </section>
</section>

<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE multimedia-ja_JP.xml ---
<section id="sn-multimedia">
  <title>Multimedia</title>
  <para>
    FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    ??????????????????????????? &FEX; ???????????????????????????
  </para>
  <variablelist>
    <varlistentry>
      <term>????????????????????????????????????</term>
      <listitem>
	<para>
	  &FC; ????????????????????????
	  <filename>rhythmbox</filename>???<filename>totem</filename>???<application>Helix Player</application>
	  (<command>hxplay</command> ????????????)
	  ??????????????????????????????????????????????????????????????????
	  ??????????????????????????? xmms ?????????????????????????????????????????????????????????
	  &FC; ????????? &FEX; ??????????????????????????????????????????
	  GNOME???KDE ???????????????????????????????????????????????????????????????????????????????????????????????????
	  Adobe/Macromedia ??? Flash ??????????????????Real ??????????????????VLC???MPlayer???Xine
	  ????????????????????????????????????????????????????????????????????????????????????????????????&FED;
	  ??????????????????????????????????????????????????????
	  ??????????????????&FED; ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ????????????????????????????????? <xref
	  linkend="sn-multimedia-excluded"/> ??????????????????????????????
	</para>

	<para>
	  ?????? &FC; ??? Advanced Linux Sound Architecture (ALSA)
	  ????????????????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????????????????????????????????????????????????????
	  ????????????????????? Linux ????????????????????????????????????????????????
	  ??????????????????????????????????????????????????? ALSA ???????????????????????????????????????????????????????????????????????????????????????????????????
	  ALSA ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
	<para>
	  <ulink url='http://www.alsa-project.org/'>http://www.alsa-project.org/</ulink>
	</para>
      </listitem>    
    </varlistentry>
    <varlistentry>
      <term>Ogg ????????? Xiph.Org Foundation ??????????????????</term>
      <listitem>
	<para>
	  &FED; ??? Ogg ?????????????????????????????????????????????Vorbis
	  ??????????????????Theora ????????????Speex ??????????????????FLAC
	  ???????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????????????????????????????????????????????????????????????????
	  Xiph.Org Foundation ????????????????????????????????????????????????????????????
	</para>
	<para>
	  <ulink url='http://www.xiph.org/'>http://www.xiph.org/</ulink>
	</para>
      </listitem>   
    </varlistentry>
    <varlistentry>
      <term>MP3 &amp; DVD ???????????????</term>
      <listitem>
	<para>
	  MP3 ????????? MPEG (DVD) ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FC;
	  ????????? &FEX; ?????? MP3 ??? DVD
	  ????????????????????????????????????????????????????????????????????????
	  ?????????????????? <xref
	    linkend="sn-multimedia-excluded"/> ??????????????????????????????
	</para>
      </listitem>
    </varlistentry>
  </variablelist>
  <section id="sn-multimedia-excluded">
    <title>????????????????????????????????????????????????????????????</title>
    <para>
      ????????????????????????????????????????????????????????????????????? &FC; ????????? &FEX;
      ????????????????????????????????????
      ????????????  MP3 ??? DVD ???????????????????????????????????????Flash Player???Real
      Player ?????????????????????
      ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      &FED; ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      ???????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      <ulink url='http://fedoraproject.org/wiki/ForbiddenItems'>http://fedoraproject.org/wiki/ForbiddenItems</ulink>
    </para>
  </section>
  <section id="sn-multimedia-cd-dvd-burning">
    <title>CD???DVD ????????????????????????????????????</title>
    <para>
      &FC; ??? &FEX; ?????? CD ??? DVD ????????????????????????????????????????????????????????????
      ??????????????????????????????????????????????????????
      <command>cdrecord</command>???<command>readcd</command>???<command>mkisofs</command>
      ?????????????????????????????? Linux ??????????????????????????????????????????
      GNOME ??????????????????&FC; ????????? <filename>xcdroast</filename>
      ?????????????????? &FEX; ????????? <filename>graveman</filename>
      ???????????????????????????????????????????????????/?????????????????????????????????????????????
      KDE ???????????????????????????????????????????????????????????????????????????????????????
      <filename>k3b</filename> ?????????????????????????????????
    </para>
  </section>
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE networking-ja_JP.xml ---
<section id="sn-networking">
  <title>??????????????????</title>
  <variablelist>
    <title>???????????? 2.6.11 - 2.6.14 ??????????????????</title>
    <varlistentry>
      <term>IPv4 ?????????????????????</term>
      <listitem>
	<para>
	  ??????????????????????????? 2.6.12 ???????????????????????? (address promption)
	  ??????????????????????????????????????????????????????
	  ??????????????? IPv4 ???????????????????????? IPv4
	  ????????????????????????????????????????????????????????????
	  ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ????????? <command>sysctl</command>
	  <option>net.ipv4.conf.all.promote_secondaries</option>
	  (???????????????????????????????????????????????????????????????)
	  ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>ICMP Errors ???????????????????????????????????????</term>
      <listitem>
	<para>
	  ICMP ????????????????????????????????????????????????????????????????????????????????? ICMP
	  ????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????? 2.6.12 ??????????????? <command>sysctl</command>
	  <option>net.ipv4.icmp_errors_use_inbound_ifaddr</option>
	  ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
	<para>
	  ?????????????????????????????? ICMP echo request ???
	  <computeroutput>eth0</computeroutput> ???????????????????????????????????????
	  ?????????????????????????????????????????? ICMP echo reply ???
	  <computeroutput>eth1</computeroutput> ?????????????????????????????????
	  ???????????????????????????????????????????????????
	  <computeroutput>eth1</computeroutput>
	  ??????????????????????????????????????????????????????
	  <command>sysctl</command> ???????????????????????????????????????????????????
	  <computeroutput>eth0</computeroutput> ?????????????????????
	</para>
	<para>
	  ??????????????????????????????????????????????????????????????????????????????????????????
	</para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>LC-Trie ??????????????????????????????????????????????????????</term>
      <listitem>
	<para>
	  <firstterm>trie</firstterm>
	  ????????????????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>?????????????????????????????????????????????????????????</term>
      <listitem>
	<para>
	  TCP ?????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ?????? <firstterm>new RENO</firstterm> ?????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
	<itemizedlist>
	  <listitem>
	    <para>High Speed TCP congestion control.
	    </para>
	  </listitem>
	  <listitem>
	    <para>TCP Hybla congestion avoidance.
	    </para>
	  </listitem>
	  <listitem>
	    <para>H-TCP congestion control.
	    </para>
	  </listitem>
	  <listitem>
	    <para>Scalable TCP congestion control.
	    </para>
	  </listitem>
	</itemizedlist>
	<para>
	  ??????????????????????????????????????????????????????????????????????????????????????????BIC ??????????????? ??????????????????????????????????????????????????????????????? BICTCP 1.1 ???????????????????????????
	</para>
	<note>
	  <title>Affecting the Congestion Control Algorithm</title>
	  <para>
	    ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	    <option>TCP_CONGESTION</option>
	    ????????????????????????????????????????????????
	  </para>
	</note>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>????????????????????????????????????????????????</term>
      <listitem>
      <para>
	  ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>DCCP ??????????????????????????????</term>
      <listitem>
	<para>
	  ??????????????????????????? 2.6.14-rc1 ??? DCCP
	  ?????????????????????????????????????????????????????????????????????
	  ????????????????????????????????????????????????????????????????????????
	  ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>??????</term>
      <listitem>
	<para>
	  HostAP ????????????????????????????????????????????? 2.6.14-rc1 ???????????????????????????
	  ???????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????  Intersil Prism2 ?????????????????????
	  (PC Card/PCI/PLX) ???????????????????????????
	  Intel(R) PRO/Wireless 2100 and 2200 ?????? LAN ??????????????????????????????????????????????????????
	</para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>?????????</term>
      <listitem>
	<itemizedlist>
	  <listitem>
	    <para>
	      TCP Segmentation Offloading (TSO)
	      ???????????????????????????????????????????????????????????????
	    </para>
	  </listitem>
	  <listitem>
	    <para>
	      iptables ???????????????????????????????????????????????????????????????????????????????????????????????????
	    </para>
	  </listitem>
	  <listitem>
	    <para>
	      ???????????????????????????????????????????????????????????????????????? IPv4 ?????????
	      IPv6 ???????????????????????????????????????????????????????????????????????????????????????
	    </para>
	  </listitem>
	  <listitem>
	    <para>
	      SNMPv2 MIB ?????????????????? ipInAddrErrors ???
	      ????????? IPv4 ?????????????????????????????????
	    </para>
	  </listitem>
	  <listitem>
	    <para>
	      ???????????? API (RFC3542)
	      ??????????????????????????????????????????????????????????????????????????????????????????
	    </para>
	  </listitem>
	</itemizedlist>
      </listitem> 
    </varlistentry>
  </variablelist>
  <section sn="kernel-userspace-tools">
    <title>???????????????????????????</title>
    <title>iproute</title>
    <para>
      IPv4 ????????????????????????????????????????????????????????? 2.6.12
      ??????????????????????????????????????????????????????????????????
      ?????????????????????????????????iproute2
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
<screen>
ip addr list dev eth0
4: eth0: &lt;BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    inet 10.0.0.3/24 scope global eth0
su -c 'ip addr del 10.0.0.3 dev eth0'
Warning: Executing wildcard deletion to stay compatible with old
      scripts. Explicitly specify the prefix length (10.0.0.3/32) to
      avoid this warning. This special behaviour is likely to disappear
      in further releases, fix your scripts!
</screen>
    <para>
      ??????????????????????????????????????????????????????????????????
    </para>
<screen>
su -c 'ip addr del 10.0.0.3/24 dev eth0'
</screen>
    <para>
      ?????????
    </para>
    <para>
      ??????????????????????????????????????????????????????????????????????????????????????????
      (??????????????????????????????) ??????????????????????????????????????????????????????????????????????????????
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????<computeroutput>NO-CARRIER</computeroutput>
      ?????????????????????????????????????????????
    </para>
    <para>
      <command>ip</command> ??????????????????????????????????????????????????????<command>tc</command>
      ?????????????????????????????? <option>-batch</option>
      ??????????????????????????????????????????????????????????????????????????????
    </para>
  </section>
</section>

<!-- cruft, but saved just in case :)
  <para>
   This section contains information relating to network connectivity.
  </para>
  <section id="sn-networking-networkmanager">
    <title><filename>NetworkManager</filename></title>
    <para>
      The <command>NetworkManager</command> service allows computers
      such as laptops to automatically manage changing network
      connections.  It includes support for wireless networking.
    </para>
    <para>
      You must manually enable the <command>NetworkManager</command>
      service.  To do so, type the following in a terminal window:
    </para>
<screen>
su -c '/sbin/chkconfig --level 345 NetworkManager on; /sbin/service NetworkManager start'
su -c '/sbin/chkconfig --level 345 NetworkManagerDispatcher on; /sbin/service NetworkManagerDispatcher start'
</screen>
    <para>
      Enter the root password when prompted.
    </para>
    <para>
      Use the <application>Network Monitor</application> desktop applet
      to monitor and configure <command>NetworkManager</command>.  To load the
      applet in GNOME, right-click on the panel and select:
    </para>
    <para>
     <guimenuitem>Add to Panel...</guimenuitem><guimenuitem>Network
     Monitor</guimenuitem>
    </para>
    <para>
      <command>NetworkManager</command> uses BIND to proxy DNS requests.
      Enabling the <command>NetworkManager</command> service also loads the
      <command>named</command> service as well.  By default BIND is
      configured as a cacheing service for the local system, and does
      not accept connections from other systems.  
    </para>
    <para>
	Note that some wireless network cards require drivers or firmware
	that cannot be included with &DISTRO;.  This software must be
	installed separately for <command>NetworkManager</command> to function.
    </para>
-->
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE overview-ja_JP.xml ---
<section id="sn-overview">
  <title>?????????????????????</title>
  <caution>
    <title>????????????????????????????????????</title>
    <para>
      ????????????????????? &DISTRO; &DISTROVER; ???????????????????????????????????????????????????
    </para>
  </caution>
<!--
  <para>
    ????????????????????? &DISTRO; &DISTROVER; ???????????????????????????????????????????????????
  </para>
  <itemizedlist>
    <listitem>
      <para>
	&DISTRO; &DISTROVER; ???????????????????????????????????????
      </para>
      <itemizedlist>
	<listitem>
	  <para>
	    PowerPC (PPC) ???????????????????????????????????????
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GCC 4.0
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GNOME 2.10
	  </para>
	</listitem>
	<listitem>
	  <para>
	    KDE 3.4 &mdash; ????????????????????????????????????????????????
	    ???????????????????????? 
	    <guimenu>KDS Control
	      Center</guimenu>-<guisubmenu>Regional &amp;
	      Accessibility</guisubmenu>-<guisubmenu>Accessibility</guisubmenu>
	    ????????????????????????
	    <note>
	      <title>????????? KDE ???????????????????????????????????????????????????</title>
	    </note>
	  </para>
	</listitem>
	<listitem>
	  <para>
	    ??????????????? Eclipse 3.1M6 (???????????? Java ???????????????)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    MySQL 4.1
	  </para>
	</listitem>
	<listitem>
	  <para>
	    PHP 5.0
	  </para>
	</listitem>
	<listitem>
	  <para>
	    Xen 2 (?????? OS ?????????????????????????????????????????????????????????)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GFS 6.1-0.pre22 (???????????????????????????????????????)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    Evince 0.2.1 (????????????????????????????????????)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GDM 2.6 - ?????????????????????????????????
	  </para>
	</listitem>
	<listitem>
	  <para>
	    &SEL; &mdash;
	    targeted ??????????????? 80 ??????????????????????????????????????????????????????
	    ??????????????????????????????????????????????????????
	    targeted ?????????????????????????????????????????????????????????
	    ?????????????????????????????? <ulink
	      url="http://fedora.redhat.com/docs/selinux-faq/">http://fedora.redhat.com/docs/selinux-faq/</ulink>
	    ??????????????????????????????
	    ????????? targeted ???????????????????????????????????????????????????????????????
	  </para>
	  <itemizedlist>
	    <listitem>
	      <para>
		<command>NetworkManager</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>amanda</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>apache</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>apmd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>arpwatch</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>auditd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>bluetooth</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>canna</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cardmgr</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>checkpolicy</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>chkpwd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>compat</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>comsat</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>consoletype</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cpucontrol</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cpuspeed</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>crond</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cups</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cvs</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cyrus</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dbskkd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dbusd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dhcpc</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dhcpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dictd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dmidecode</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dovecot</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>fingerd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>fsadm</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ftpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>getty</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>hald</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>hostname</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>hotplug</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>howl</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>hwclock</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>i18n_input</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ifconfig</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>inetd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>init</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>initrc</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>innd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>kerberos</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>klogd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ktalkd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>kudzu</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ldconfig</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>load_policy</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>login</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>lpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>mailman</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>modutil</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>mta</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>mysqld</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>named</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>netutils</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>nscd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ntpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>portmap</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>postgresql</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ppd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>privoxy</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>radius</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>radvd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>restorecon</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>rlogind</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>rpcd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>rpm</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>rshd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>rsync</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>samba</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>saslauthd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>sendmail</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>setfiles</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>slapd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>snmpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>squid</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ssh</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>stunnel</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>syslogd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>telnetd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>tftpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>udev</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>updfstab</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>uucpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>webalizer</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>winbind</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>xdm</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ypbind</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ypserv</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>zebra</command>
	      </para>
	    </listitem>
	  </itemizedlist>
	</listitem>
      </itemizedlist>
    </listitem>
  </itemizedlist>
-->
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
coding: utf-8-unix
End:
-->


--- NEW FILE package-movement-ja_JP.xml ---
<section id="sn-package-movement">
  <title>????????????????????????</title>
  <!-- 
  FIXME
  Needs updating of entire contents for FC4.
  -->
  <para>
    ????????????????????????????????????????????????????????????????????????????????????????????????????????????
    ???????????????????????? <computeroutput>\</computeroutput>
    ??????????????????????????????????????????????????????????????????????????????
  </para>
<screen>
<command>treediff.py dist-fc4 dist-rawhide > /tmp/diff \
sed -e 's,^,* ,g' -e 's,$,\n,g' /tmp/diff > diffwiki</command>
</screen>
  <section>
    <title>????????????????????????</title>
    <para>2005/09/21 ??????</para>
    <para>[106429] MAKEDEV-3.19-1 -> [115423] MAKEDEV-3.19-4 </para>
    <para>[111566] <ulink
	url='/ImageMagick'>ImageMagick</ulink>-6.2.2.0-2 -> [112246]
      <ulink url='/ImageMagick'>ImageMagick</ulink>-6.2.2.0-4 </para>
    <para>[105261] newt-0.51.6-7 -> [117695] newt-0.51.6-8 </para>
    <para>[106878] am-utils-6.0.9-12 -> [117066] am-utils-6.1.1-2
    </para>
    <para>[108819] amanda-2.4.5-2 -> [115871] amanda-2.4.5-3 </para>
    <para>[112105] anaconda-10.2.1.5-2 -> [118390]
      anaconda-10.3.0.24-1 </para>
    <para>[105300] aspell-0.50.5-6 -> [114172] aspell-0.60.3-2 </para>
    <para>[108035] aspell-ca-0.50-2 -> [114184] aspell-ca-0.50-4
    </para>
    <para>[108036] aspell-cs-0.51-2 -> [114270] aspell-cs-0.51-3
    </para>
    <para>[108038] aspell-da-0.50-11 -> [114276] aspell-da-0.50-12
    </para>
    <para>[106443] libsoup-2.2.3-2 -> [116988] libsoup-2.2.6.1-1
    </para>
    <para>[108042] aspell-es-0.50-11 -> [117058] aspell-es-0.50-13
    </para>
    <para>[108044] aspell-fr-0.50-8 -> [114285] aspell-fr-0.50-9
    </para>
    <para>[108051] aspell-it-0.53-2 -> [114362] aspell-it-0.53-3
    </para>
    <para>[108055] aspell-nl-0.50-6 -> [114363] aspell-nl-0.50-7
    </para>
    <para>[108058] aspell-no-0.50.1-8 -> [114366] aspell-no-0.50.1-9
    </para>
    <para>[108060] aspell-pl-0.51-3 -> [118018] aspell-pl-0.51-5
    </para>
    <para>[108061] aspell-sv-0.50-7 -> [114371] aspell-sv-0.50-8
    </para>
    <para>[107959] at-3.1.8-77_FC4 -> [112026] at-3.1.8-78 </para>
    <para>[108132] gtkhtml3-3.6.2-1 -> [117587] gtkhtml3-3.8.0-1
    </para>
    <para>[108304] ntp-4.2.0.a.20040617-8 -> [117060]
      ntp-4.2.0.a.20050816-1 </para>
    <para>[108909] autofs-4.1.4-5 -> [112718] autofs-4.1.4-9 </para>
    <para>[102923] automake-1.9.5-1 -> [114414] automake-1.9.6-1
    </para>
    <para>[108562] autorun-3.16-1 -> [118091] autorun-3.17-1 </para>
    <para>[105321] awesfx-0.5.0d-2 -> [113536] awesfx-0.5.0d-3 </para>
    <para>[105808] nut-2.0.1-1 -> [114509] nut-2.0.2-1 </para>
    <para>[110344] bash-3.0-31 -> [118423] bash-3.0-34 </para>
    <para>[110908] bind-9.3.1-4 -> [116915] bind-9.3.1-11 </para>
    <para>[111486] binutils-2.15.94.0.2.2-2 -> [116754]
      binutils-2.16.91.0.2-4 </para>
    <para>[105319] bootparamd-0.17-22.devel -> [116780]
      bootparamd-0.17-23.devel </para>
    <para>[106988] bug-buddy-2.10.0-1 -> [117633] bug-buddy-2.12.0-1
    </para>
    <para>[111028] bzip2-1.0.2-16 -> [117182] bzip2-1.0.3-1 </para>
    <para>[106470] pax-3.0-11 -> [116422] pax-3.4-1 </para>
    <para>[109185] <ulink url='/SysVinit'>SysVinit</ulink>-2.85-39 ->
      [113360] <ulink url='/SysVinit'>SysVinit</ulink>-2.85-40 </para>
    <para>[111393] control-center-2.10.1-6 -> [118105]
      control-center-2.12.0-2 </para>
    <para>[111120] openldap-2.2.23-5 -> [111936] openldap-2.2.26-1
    </para>
    <para>[110745] cpio-2.6-7 -> [113389] cpio-2.6-8 </para>
    <para>[106419] cracklib-2.8.2-1 -> [111862] cracklib-2.8.3-1
    </para>
    <para>[104496] bluez-hcidump-1.18-1 -> [115995]
      bluez-hcidump-1.24-1 </para>
    <para>[104877] ctags-5.5.4-3 -> [115419] ctags-5.5.4-4 </para>
    <para>[108614] cvs-1.11.19-8 -> [116935] cvs-1.11.19-10 </para>
    <para>[108252] cyrus-sasl-2.1.20-5 -> [117833] cyrus-sasl-2.1.21-5
    </para>
    <para>[109650] pam-0.79-8 -> [118330] pam-0.80-8 </para>
    <para>[109663] dhcp-3.0.2-12 -> [117972] dhcp-3.0.3-6 </para>
    <para>[110743] apr-0.9.6-3 -> [118164] apr-0.9.6-6 </para>
    <para>[110347] e2fsprogs-1.37-4 -> [117739] e2fsprogs-1.38-1
    </para>
    <para>[104668] diffstat-1.38-2 -> [116208] diffstat-1.38-4 </para>
    <para>[107298] doxygen-1.4.2-1 -> [118248] doxygen-1.4.4-2 </para>
    <para>[110505] dump-0.4b40-2 -> [113542] dump-0.4b40-4 </para>
    <para>[110508] eject-2.0.13-15 -> [117061] eject-2.1.2-1 </para>
    <para>[110262] parted-1.6.22-2 -> [117238] parted-1.6.24-1 </para>
    <para>[110911] emacs-21.4-5 -> [114092] emacs-21.4-7 </para>
    <para>[111808] esound-0.2.35-5 -> [114327] esound-0.2.36-1 </para>
    <para>[105304] passwd-0.69-2 -> [112701] passwd-0.70-1 </para>
    <para>[106286] fetchmail-6.2.5-7 -> [114678] fetchmail-6.2.5.2-1
    </para>
    <para>[109759] patch-2.5.4-24 -> [117794] patch-2.5.4-29 </para>
    <para>[111272] filesystem-2.3.4-1 -> [116817] filesystem-2.3.5-1
    </para>
    <para>[106330] findutils-4.2.20-1 -> [117490] findutils-4.2.25-2
    </para>
    <para>[105012] finger-0.17-28 -> [113967] finger-0.17-29 </para>
    <para>[105097] freetype-2.1.9-2 -> [116586] freetype-2.1.9-4
    </para>
    <para>[111401] ftp-0.17-26 -> [117241] ftp-0.17-29 </para>
    <para>[104499] gawk-3.1.4-5 -> [118359] gawk-3.1.5-2 </para>
    <para>[111099] gcc-4.0.0-8 -> [118294] gcc-4.0.1-14 </para>
    <para>[108458] gd-2.0.33-2 -> [117628] gd-2.0.33-3 </para>
    <para>[109684] gdb-6.3.0.0-1.21 -> [117661] gdb-6.3.0.0-1.65
    </para>
    <para>[106626] gettext-0.14.3-1 -> [116274] gettext-0.14.5-1
    </para>
    <para>[111402] gdm-2.6.0.8-16 -> [117776] gdm-2.8.0.4-1 </para>
    <para>[108333] gedit-2.10.2-3 -> [117719] gedit-2.12.0-1 </para>
    <para>[110935] perl-5.8.6-15 -> [117489] perl-5.8.7-0.3.fc5
    </para>
    <para>[107237] gok-1.0.3-1 -> [116496] gok-1.0.5-4 </para>
    <para>[110356] php-5.0.4-10 -> [118097] php-5.0.5-3 </para>
    <para>[110581] gimp-2.2.7-4 -> [116538] gimp-2.2.8-3 </para>
    <para>[111654] gnome-applets-2.10.1-9 -> [117721]
      gnome-applets-2.12.0-1 </para>
    <para>[111691] glibc-2.3.5-10 -> [117966] glibc-2.3.90-12 </para>
    <para>[111104] gnome-games-2.10.0-5 -> [117724]
      gnome-games-2.12.0-1 </para>
    <para>[111214] gnome-media-2.10.2-4 -> [117726]
      gnome-media-2.12.0-1 </para>
    <para>[106508] kdeadmin-3.4.0-1 -> [118336] kdeadmin-3.4.2-2
    </para>
    <para>[110919] gnome-utils-2.10.0-3 -> [117738]
      gnome-utils-2.12.0-1 </para>
    <para>[110246] gnupg-1.4.1-3 -> [116120] gnupg-1.4.2-3 </para>
    <para>[104528] gnuplot-4.0.0-7 -> [117403] gnuplot-4.0.0-8 </para>
    <para>[104506] gperf-3.0.1-6 -> [115552] gperf-3.0.1-7 </para>
    <para>[104548] grep-2.5.1-48 -> [113236] grep-2.5.1-50 </para>
    <para>[108057] xinitrc-4.0.18-1 -> [111974] xinitrc-4.0.19-1
    </para>
    <para>[104544] guile-1.6.7-2 -> [117402] guile-1.6.7-4 </para>
    <para>[104475] hdparm-5.9-1 -> [112183] hdparm-6.1-1 </para>
    <para>[111501] initscripts-8.11.1-1 -> [117977] initscripts-8.14-1
    </para>
    <para>[107880] inn-2.4.2-3 -> [115559] inn-2.4.2-4 </para>
    <para>[106114] iproute-2.6.11-1 -> [118247] iproute-2.6.14-3
    </para>
    <para>[106499] iptables-1.3.0-2 -> [114287] iptables-1.3.2-1
    </para>
    <para>[107881] iputils-20020927-22 -> [117698] iputils-20020927-26
    </para>
    <para>[111656] isdn4k-utils-3.2-28 -> [115009] isdn4k-utils-3.2-32
    </para>
    <para>[105032] joe-3.1-8 -> [112056] joe-3.3-1 </para>
    <para>[108237] kdebase-3.4.0-5 -> [118422] kdebase-3.4.2-5 </para>
    <para>[106532] kdegames-3.4.0-1 -> [116019] kdegames-3.4.2-1
    </para>
    <para>[107198] kdegraphics-3.4.0-2 -> [117508] kdegraphics-3.4.2-3
    </para>
    <para>[104526] openobex-1.0.1-3 -> [111937] openobex-1.0.1-4
    </para>
    <para>[107226] kdemultimedia-3.4.0-2 -> [115553]
      kdemultimedia-3.4.2-1 </para>
    <para>[106551] kdeutils-3.4.0-1 -> [117699] kdeutils-3.4.2-2
    </para>
    <para>[105322] minicom-2.00.0-21 -> [114175] minicom-2.1-1 </para>
    <para>[112015] kernel-2.6.11-1.1369_FC4 -> [118394]
      kernel-2.6.13-1.1565_FC5 </para>
    <para>[108707] libbtctl-0.4.1-7 -> [114382] libbtctl-0.4.1-8
    </para>
    <para>[107067] krb5-1.4-3 -> [118053] krb5-1.4.2-4 </para>
    <para>[106252] krbafs-1.2.2-7 -> [115422] krbafs-1.2.2-8 </para>
    <para>[111032] kudzu-1.1.116.2-2 -> [118290] kudzu-1.2.7-1 </para>
    <para>[105596] lam-7.1.1-3 -> [115564] lam-7.1.1-7.FC5 </para>
    <para>[105047] less-382-7 -> [117533] less-382-8 </para>
    <para>[104599] libieee1284-0.2.9-2 -> [114409] libieee1284-0.2.9-3
    </para>
    <para>[106523] libtermcap-2.0.8-41 -> [115467] libtermcap-2.0.8-42
    </para>
    <para>[110440] libtiff-3.7.1-6 -> [113273] libtiff-3.7.2-1 </para>
    <para>[109070] libtool-1.5.16.multilib2-1 -> [118098]
      libtool-1.5.20-3 </para>
    <para>[104597] lm_sensors-2.8.8-5 -> [117365] lm_sensors-2.9.1-4
    </para>
    <para>[105199] lockdev-1.0.1-7 -> [118409] lockdev-1.0.1-9 </para>
    <para>[107338] logrotate-3.7.1-10 -> [117629] logrotate-3.7.2-3
    </para>
    <para>[110353] lsof-4.74-7 -> [118297] lsof-4.76-1 </para>
    <para>[108835] dovecot-0.99.14-4.fc4 -> [114740]
      dovecot-0.99.14-6.fc5 </para>
    <para>[106781] make-3.80-7 -> [116850] make-3.80-8 </para>
    <para>[104365] distcache-1.4.5-7 -> [115345] distcache-1.4.5-11
    </para>
    <para>[107530] man-pages-1.67-7 -> [118017] man-pages-2.07-5
    </para>
    <para>[93204] man-pages-cs-0.16-4 -> [115882] man-pages-cs-0.16-5
    </para>
    <para>[93194] man-pages-de-0.4-9 -> [115873] man-pages-de-0.4-10
    </para>
    <para>[108613] man-pages-ja-20050415-1 -> [116660]
      man-pages-ja-20050815-1 </para>
    <para>[110081] mx4j-2.1.0-1jpp_7fc -> [114677] mx4j-3.0.1-1jpp_5fc
    </para>
    <para>[109945] mc-4.6.1a-0.9 -> [118021] mc-4.6.1a-0.15 </para>
    <para>[101562] desktop-file-utils-0.10-1 -> [117302]
      desktop-file-utils-0.10-3 </para>
    <para>[111217] redhat-artwork-0.122-10 -> [116975]
      redhat-artwork-0.128-1 </para>
    <para>[104435] mikmod-3.1.6-34 -> [112072] mikmod-3.1.6-35 </para>
    <para>[110923] mkinitrd-4.2.15-1 -> [116471] mkinitrd-4.2.21-1
    </para>
    <para>[110244] gimp-print-4.2.7-7 -> [116481] gimp-print-4.2.7-12
    </para>
    <para>[111409] rhpl-0.167-1 -> [118384] rhpl-0.174-1 </para>
    <para>[108728] glade2-2.10.0-1 -> [116544] glade2-2.10.0-2 </para>
    <para>[107181] pyxf86config-0.3.19-4 -> [114209]
      pyxf86config-0.3.19-6 </para>
    <para>[105582] arptables_jf-0.0.8-4 -> [116740]
      arptables_jf-0.0.8-6 </para>
    <para>[108583] fontconfig-2.2.3-13 -> [114861] fontconfig-2.3.2-1
    </para>
    <para>[108241] oprofile-0.8.2-4 -> [114916] oprofile-0.9.1-2
    </para>
    <para>[104605] mtr-0.69-3 -> [117503] mtr-0.69-4 </para>
    <para>[105384] mutt-1.4.2.1-2 -> [117134] mutt-1.4.2.1-3 </para>
    <para>[106486] kdeedu-3.4.0-1 -> [118428] kdeedu-3.4.2-3 </para>
    <para>[111281] httpd-2.0.54-10 -> [115215] httpd-2.0.54-12 </para>
    <para>[109664] libwpd-0.8.1-1 -> [117298] libwpd-0.8.3-1 </para>
    <para>[109161] ncurses-5.4-17 -> [115668] ncurses-5.4-18 </para>
    <para>[109016] net-tools-1.60-52 -> [115663] net-tools-1.60-56
    </para>
    <para>[106997] rdesktop-1.4.0-2 -> [113322] rdesktop-1.4.1-1.fc5
    </para>
    <para>[106852] redhat-rpm-config-8.0.34-1 -> [116588]
      redhat-rpm-config-8.0.39-1 </para>
    <para>[104517] compat-slang-1.4.5-10 -> [115421]
      compat-slang-1.4.5-11 </para>
    <para>[111646] nfs-utils-1.0.7-8 -> [117732] nfs-utils-1.0.7-16
    </para>
    <para>[104611] rarpd-ss981107-20 -> [114929] rarpd-ss981107-22
    </para>
    <para>[111216] nss_ldap-234-4 -> [117936] nss_ldap-241-1 </para>
    <para>[101793] squirrelmail-1.4.4-2 -> [117917]
      squirrelmail-1.4.6-0.cvs20050812.2.fc5 </para>
    <para>- perl-Filter-1.30-7 </para>
    <para>- perl-Filter-Simple-0.79-5 </para>
    <para>[111400] libxslt-1.1.14-2 -> [117480] libxslt-1.1.15-1
    </para>
    <para>[111035] pam_krb5-2.1.7-3 -> [115747] pam_krb5-2.1.8-2
    </para>
    <para>[106493] file-roller-2.10.0-1 -> [117656]
      file-roller-2.12.0-1 </para>
    <para>[106353] pyOpenSSL-0.6-1.p24.4 -> [117052]
      pyOpenSSL-0.6-1.p24.6 </para>
    <para>[104627] rdist-6.1.5-40 -> [111944] rdist-6.1.5-41 </para>
    <para>[110926] spamassassin-3.0.3-4.fc4 -> [118074]
      spamassassin-3.1.0-1.fc5 </para>
    <para>[105950] pilot-link-0.12.0-0.pre2.0 -> [117233]
      pilot-link-0.12.0-0.pre4.5 </para>
    <para>[106474] star-1.5a54-2 -> [117115] star-1.5a65-1 </para>
    <para>[111515] net-snmp-5.2.1-12 -> [118322] net-snmp-5.2.1.2-3
    </para>
    <para>[96116] ppp-2.4.2-7 -> [115416] ppp-2.4.3-3 </para>
    <para>[110366] vlock-1.3-19 -> [115661] vlock-1.3-20 </para>
    <para>[110359] procps-3.2.5-6 -> [117548] procps-3.2.5-7 </para>
    <para>[105210] psmisc-21.5-4 -> [117707] psmisc-21.6-1 </para>
    <para>[105614] pvm-3.4.5-3_FC4 -> [111812] pvm-3.4.5-5 </para>
    <para>[105105] bogl-0.1.18-7 -> [118318] bogl-0.1.18-10 </para>
    <para>[108185] gnopernicus-0.10.6-1 -> [117638]
      gnopernicus-0.11.6-1 </para>
    <para>[110883] qt-3.3.4-14 -> [118419] qt-3.3.5-2 </para>
    <para>[104494] ksh-20050202-1 -> [111912] ksh-20050202-3 </para>
    <para>[108083] quota-3.12-6 -> [116742] quota-3.12-7 </para>
    <para>[101735] gnome-speech-0.3.6-1 -> [115904]
      gnome-speech-0.3.7-1 </para>
    <para>[111387] openoffice.org-1.9.104-2 -> [118196]
      openoffice.org-1.9.130-1.2.fc5 </para>
    <para>[105350] rp-pppoe-3.5-27 -> [116414] rp-pppoe-3.5-30 </para>
    <para>[111410] rpm-4.4.1-21 -> [117156] rpm-4.4.2-4 </para>
    <para>[110925] rsync-2.6.4-3 -> [115264] rsync-2.6.6-2 </para>
    <para>[104630] rusers-0.17-43 -> [117620] rusers-0.17-45 </para>
    <para>[109533] samba-3.0.14a-2 -> [117971] samba-3.0.20-2 </para>
    <para>- sash-3.7-6 </para>
    <para>[110268] sendmail-8.13.4-2 -> [118253] sendmail-8.13.5-1
    </para>
    <para>[111123] setup-2.5.44-1 -> [117568] setup-2.5.47-1.1 </para>
    <para>[111408] shadow-utils-4.0.7-9 -> [117343]
      shadow-utils-4.0.12-2 </para>
    <para>[106465] slang-1.4.9-17 -> [117492] slang-1.4.9-19 </para>
    <para>[108441] slocate-2.7-22 -> [118067] slocate-2.7-27 </para>
    <para>[105316] slrn-0.9.8.1-4 -> [114996] slrn-0.9.8.1-5 </para>
    <para>[110665] squid-2.5.STABLE9-7 -> [117506]
      squid-2.5.STABLE10-4 </para>
    <para>[106754] strace-4.5.11-1 -> [115667] strace-4.5.13-1 </para>
    <para>[108145] sudo-1.6.8p8-1 -> [118285] sudo-1.6.8p9-4 </para>
    <para>[93654] switchdesk-4.0.6-3 -> [114432] switchdesk-4.0.7-1
    </para>
    <para>[111041] sysklogd-1.4.1-30 -> [117045] sysklogd-1.4.1-33
    </para>
    <para>[112528] syslinux-3.08-2 -> [117044] syslinux-3.10-2 </para>
    <para>[110362] sysreport-1.4.1-2 -> [112702] sysreport-1.4.1-4
    </para>
    <para>[105297] sysstat-5.0.5-9.fc -> [116738] sysstat-5.0.5-11.fc
    </para>
    <para>[108370] tar-1.15.1-5 -> [117554] tar-1.15.1-10 </para>
    <para>[109655] tcpdump-3.8.2-12 -> [116178] tcpdump-3.9.3-3
    </para>
    <para>[106994] tcsh-6.14-1 -> [115897] tcsh-6.14-5 </para>
    <para>[106284] termcap-5.4-4 -> [118201] termcap-5.4-7 </para>
    <para>[110274] tetex-3.0-4 -> [116781] tetex-3.0-6 </para>
    <para>[106019] texinfo-4.8-4 -> [112242] texinfo-4.8-6 </para>
    <para>[109641] jwhois-3.2.2-14 -> [115889] jwhois-3.2.3-2 </para>
    <para>[110348] elfutils-0.108-1 -> [117517] elfutils-0.115-1
    </para>
    <para>[105286] expect-5.43.0-1 -> [111871] expect-5.43.0-2 </para>
    <para>[105014] traceroute-1.4a12-26 -> [116290]
      traceroute-1.4a12-27 </para>
    <para>[108240] subversion-1.1.4-3 -> [117737] subversion-1.2.3-3
    </para>
    <para>- schedutils-1.4.0-4 </para>
    <para>[106314] umb-scheme-3.2-38 -> [117616] umb-scheme-3.2-39
    </para>
    <para>[104847] units-1.80-12 -> [114388] units-1.85-1 </para>
    <para>[107560] quagga-0.98.3-2 -> [117222] quagga-0.98.5-2 </para>
    <para>[105298] unzip-5.51-10 -> [115669] unzip-5.51-12 </para>
    <para>[109681] util-linux-2.12p-9.3 -> [117509]
      util-linux-2.13-0.3.pre2 </para>
    <para>[108550] uucp-1.07-9 -> [114161] uucp-1.07-11 </para>
    <para>[109140] vim-6.3.071-3 -> [117700] vim-6.3.086-5 </para>
    <para>[108347] vixie-cron-4.1-33 -> [113831] vixie-cron-4.1-36.FC5
    </para>
    <para>[106439] gtksourceview-1.2.0-1 -> [117747]
      gtksourceview-1.4.1-1 </para>
    <para>[109142] vnc-4.1.1-10 -> [117547] vnc-4.1.1-17 </para>
    <para>- w3c-libwww-5.4.0-13 </para>
    <para>[104493] wget-1.9.1-22 -> [117731] wget-1.10.1-7 </para>
    <para>[100923] wireless-tools-28-0.pre4.3 -> [117952]
      wireless-tools-28-0.pre9.5 </para>
    <para>[104447] neon-0.24.7-6 -> [118267] neon-0.24.7-7 </para>
    <para>[108529] desktop-printing-0.18-10 -> [116635]
      desktop-printing-0.19-2 </para>
    <para>[109757] libselinux-1.23.10-2 -> [118218] libselinux-1.26-6
    </para>
    <para>[110975] xfig-3.2.4-11 -> [114406] xfig-3.2.4-13 </para>
    <para>[106604] ttmkfdir-3.0.9-16 -> [115679] ttmkfdir-3.0.9-17
    </para>
    <para>[106293] ckermit-8.0.211-1 -> [117400] ckermit-8.0.211-3
    </para>
    <para>[111493] coreutils-5.2.1-48 -> [117826] coreutils-5.2.1-55
    </para>
    <para>[109668] gstreamer-0.8.10-1 -> [117857] gstreamer-0.8.11-1
    </para>
    <para>[110247] gstreamer-plugins-0.8.8-6 -> [117858]
      gstreamer-plugins-0.8.11-1 </para>
    <para>[108260] gnome-icon-theme-2.10.1-4 -> [117725]
      gnome-icon-theme-2.12.0-1 </para>
    <para>[111290] xpdf-3.00-19 -> [116734] xpdf-3.01-1 </para>
    <para>[104699] xsane-0.95-3 -> [112799] xsane-0.95-4 </para>
    <para>[110438] xscreensaver-4.21-4 -> [118219]
      xscreensaver-4.22-16 </para>
    <para>[106575] nautilus-cd-burner-2.10.0-2 -> [117669]
      nautilus-cd-burner-2.12.0-1 </para>
    <para>- hpoj-0.91-13 </para>
    <para>[108081] ypserv-2.13-6 -> [114545] ypserv-2.13-7 </para>
    <para>[108065] zlib-1.2.2.2-3 -> [117021] zlib-1.2.3-1 </para>
    <para>[110759] gthumb-2.6.5-1 -> [117742] gthumb-2.6.7-1 </para>
    <para>[110698] alsa-utils-1.0.9rc2-2 -> [116939]
      alsa-utils-1.0.9rf-5 </para>
    <para>[111418] libgnomeprint22-2.10.3-1 -> [117675]
      libgnomeprint22-2.12.0-1 </para>
    <para>[106542] libgnomeprintui22-2.10.1-1 -> [117676]
      libgnomeprintui22-2.12.0-1 </para>
    <para>[106076] rhythmbox-0.8.8-2 -> [117443]
      rhythmbox-0.9.0.cvs20050902-1 </para>
    <para>[104518] libgsf-1.11.1-2 -> [118324] libgsf-1.12.3-1 </para>
    <para>[104645] libmng-1.0.9-1 -> [112902] libmng-1.0.9-2 </para>
    <para>[104492] bluez-libs-2.15-1 -> [117512] bluez-libs-2.20-1
    </para>
    <para>[109626] bluez-utils-2.15-7 -> [117513] bluez-utils-2.20-1
    </para>
    <para>[109284] gnome-themes-2.10.1-2 -> [117637]
      gnome-themes-2.12.0-1 </para>
    <para>[106333] lv-4.51-5 -> [113778] lv-4.51-6 </para>
    <para>[106337] nkf-2.04-5 -> [113596] nkf-2.05-1 </para>
    <para>- nvi-m17n-1.79-20040401.23 </para>
    <para>[108025] ruby-1.8.2-7 -> [118404] ruby-1.8.3-1 </para>
    <para>[109083] stunnel-4.08-2 -> [113854] stunnel-4.11-1 </para>
    <para>[108440] 4Suite-1.0-8.b1 -> [112368] 4Suite-1.0-9.b1 </para>
    <para>[106235] nss_db-2.2-31 -> [117271] nss_db-2.2-33 </para>
    <para>[111212] eclipse-3.1.0_fc-0.M6.22 -> [115167]
      eclipse-3.1.0_fc-12 </para>
    <para>[111394] dbus-0.33-3 -> [117773] dbus-0.50-1 </para>
    <para>[106803] a2ps-4.13b-46 -> [111842] a2ps-4.13b-47 </para>
    <para>[109643] libuser-0.53.7-1 -> [117997] libuser-0.54-1 </para>
    <para>[109886] gtk-doc-1.3-2 -> [113533] gtk-doc-1.4-1 </para>
    <para>[109144] perl-DBD-MySQL-2.9007-1 -> [117217]
      perl-DBD-MySQL-3.0002-1 </para>
    <para>[111122] perl-DBD-Pg-1.41-2 -> [113244] perl-DBD-Pg-1.43-1
    </para>
    <para>[105244] kdbg-1.2.10-2 -> [114272] kdbg-2.0.0-1 </para>
    <para>[106810] kdepim-3.4.0-4 -> [117234] kdepim-3.4.2-3 </para>
    <para>[106772] xdelta-1.1.3-16 -> [117821] xdelta-1.1.3-17 </para>
    <para>[107253] pkgconfig-0.15.0-6 -> [116158] pkgconfig-0.18.1-4
    </para>
    <para>[108628] kdesdk-3.4.0-3 -> [116008] kdesdk-3.4.2-1 </para>
    <para>[106503] kde-i18n-3.4.0-1 -> [116284] kde-i18n-3.4.2-1
    </para>
    <para>[111302] hotplug-2004_09_23-7 -> [118092]
      hotplug-2004_09_23-10 </para>
    <para>[112023] fedora-release-4-2 -> [113067]
      fedora-release-4-rawhide </para>
    <para>[108436] xterm-200-6 -> [118082] xterm-200-9 </para>
    <para>[106145] ppc64-utils-0.7-9 -> [118408] ppc64-utils-0.7-11
    </para>
    <para>[104559] htdig-3.2.0b6-5 -> [117484] htdig-3.2.0b6-6 </para>
    <para>- libgal2-2.4.2-4 </para>
    <para>[110442] gaim-1.3.0-1.fc4 -> [118167] gaim-1.5.0-5.fc5
    </para>
    <para>[108062] aspell-en-0.51-12 -> [114279] aspell-en-6.0-1
    </para>
    <para>[108357] freeradius-1.0.2-2 -> [114495] freeradius-1.0.4-2
    </para>
    <para>[110988] devhelp-0.10-1 -> [116721] devhelp-0.10-5 </para>
    <para>[106525] kdebindings-3.4.0-1 -> [116107] kdebindings-3.4.2-1
    </para>
    <para>[110439] nautilus-2.10.0-4 -> [117668] nautilus-2.12.0-1
    </para>
    <para>[111391] boost-1.32.0-6 -> [116965] boost-1.33.0-3 </para>
    <para>[104523] nano-1.3.5-0.20050302 -> [117495] nano-1.3.8-1
    </para>
    <para>[110577] epiphany-1.6.1-3 -> [117510] epiphany-1.8.0-1
    </para>
    <para>[111496] yum-2.3.2-7 -> [118230] yum-2.4.0-3 </para>
    <para>[104625] GConf-1.0.9-16 -> [115534] GConf-1.0.9-17 </para>
    <para>[105438] g-wrap-1.3.4-8 -> [113627] g-wrap-1.3.4-9 </para>
    <para>[105029] pcre-5.0-4 -> [117019] pcre-6.3-1 </para>
    <para>[103293] pychecker-0.8.14-3 -> [117907] pychecker-0.8.16-1
    </para>
    <para>[107295] gnome-bluetooth-0.5.1-12 -> [116637]
      gnome-bluetooth-0.5.1-14 </para>
    <para>[110227] setarch-1.7-3 -> [113328] setarch-1.8-1 </para>
    <para>[107662] kdeaddons-3.4.0-2 -> [116097] kdeaddons-3.4.2-1
    </para>
    <para>[105264] MyODBC-2.50.39-24 -> [116340] MyODBC-2.50.39-25
    </para>
    <para>[108719] nmap-3.81-3 -> [118008] nmap-3.93-1 </para>
    <para>[107878] glib2-2.6.4-1 -> [116932] glib2-2.8.1-1 </para>
    <para>[106280] m2crypto-0.13-2 -> [117174] m2crypto-0.15-1 </para>
    <para>[105135] pango-1.8.1-2 -> [116700] pango-1.10.0-1 </para>
    <para>[106004] atk-1.9.1-1 -> [117631] atk-1.10.3-1 </para>
    <para>[110350] gtk2-2.6.7-4 -> [117200] gtk2-2.8.3-1 </para>
    <para>[110963] logwatch-6.0.1-2 -> [118256] logwatch-6.1.2-4
    </para>
    <para>[107440] libxml2-2.6.19-1 -> [117989] libxml2-2.6.22-1
    </para>
    <para>[107238] gnome-mag-0.12.0-2 -> [116495] gnome-mag-0.12.1-2
    </para>
    <para>[109656] tzdata-2005i-2 -> [117537] tzdata-2005m-2 </para>
    <para>[105136] ddd-3.3.10-2 -> [112263] ddd-3.3.11-1 </para>
    <para>[111516] ethereal-0.10.11-2 -> [118418] ethereal-0.10.12-7
    </para>
    <para>[105946] mrtg-2.11.1-3 -> [117906] mrtg-2.12.2-2 </para>
    <para>[109779] curl-7.13.1-3 -> [112559] curl-7.14.0-1 </para>
    <para>[110585] mozilla-1.7.8-2 -> [118143] mozilla-1.7.11-5
    </para>
    <para>[104474] cdrdao-1.1.9-9 -> [114286] cdrdao-1.2.0-1 </para>
    <para>[111152] policycoreutils-1.23.10-2 -> [118399]
      policycoreutils-1.27.1-1 </para>
    <para>[108677] selinux-doc-1.19.5-1 -> [118233] selinux-doc-1.22-1
    </para>
    <para>[108338] checkpolicy-1.23.1-1 -> [118421]
      checkpolicy-1.27.2-1 </para>
    <para>[107547] sound-juicer-2.10.1-1 -> [116671]
      sound-juicer-2.11.91-1 </para>
    <para>[104852] mod_auth_mysql-2.6.1-4 -> [112597]
      mod_auth_mysql-2.9.0-1 </para>
    <para>[106515] kdeartwork-3.4.0-1 -> [116101] kdeartwork-3.4.2-1
    </para>
    <para>[111390] setools-2.1.0-5 -> [118333] setools-2.1.2-1 </para>
    <para>[111060] grub-0.95-13 -> [114871] grub-0.95-15 </para>
    <para>[110652] openssh-4.0p1-3 -> [117588] openssh-4.2p1-1 </para>
    <para>[108233] gnucash-1.8.11-3 -> [117839] gnucash-1.8.11-4
    </para>
    <para>[108697] MySQL-python-1.2.0-1 -> [115666]
      MySQL-python-1.2.0-2 </para>
    <para>[106774] PyQt-3.14.1-1 ->
      [117928] PyQt-3.15-1 </para>
    <para>[106773] sip-4.2.1-1 -> [117925] sip-4.3.1-1 </para>
    <para>[109146] jpilot-0.99.8-0.pre8.4 -> [116645]
      jpilot-0.99.8-0.pre10.2 </para>
    <para>[108932] lftp-3.1.3-1 -> [117026] lftp-3.3.0-1 </para>
    <para>[107870] cdrtools-2.01.1-9 -> [117294] cdrtools-2.01.1-10
    </para>
    <para>- apel-10.6-6 </para>
    <para>[107986] mysql-4.1.11-2 -> [116941] mysql-4.1.12-3 </para>
    <para>[108427] tmpwatch-2.9.3-1 -> [112807] tmpwatch-2.9.4-1
    </para>
    <para>[107682] kdenetwork-3.4.0-3 -> [116293] kdenetwork-3.4.2-1
    </para>
    <para>[111395] fedora-logos-1.1.31-1 -> [117762]
      fedora-logos-1.1.31-2 </para>
    <para>[100527] junit-3.8.1-3jpp_4fc -> [112932]
      junit-3.8.1-3jpp_5fc </para>
    <para>[105492] xmlsec1-1.2.7-4 -> [118326] xmlsec1-1.2.9-1 </para>
    <para>[104606] openCryptoki-2.1.5-9 -> [117535]
      openCryptoki-2.1.5-10 </para>
    <para>[110363] system-config-bind-4.0.0-16_FC4 -> [116458]
      system-config-bind-4.0.0-30_FC5 </para>
    <para>[110056] system-config-date-1.7.18-1 -> [115786]
      system-config-date-1.7.99.0-1 </para>
    <para>[109174] system-config-keyboard-1.2.6-2 -> [118188]
      system-config-keyboard-1.2.6-3 </para>
    <para>[109127] system-config-kickstart-2.5.22-2 -> [118045]
      system-config-kickstart-2.5.24-1 </para>
    <para>- system-config-mouse-1.2.11-1 </para>
    <para>[108705] system-config-netboot-0.1.14-1 -> [116895]
      system-config-netboot-0.1.30-1_FC5 </para>
    <para>[110270] system-config-nfs-1.3.10-1 -> [113615]
      system-config-nfs-1.3.11-1 </para>
    <para>[110775] system-config-printer-0.6.131-1 -> [117714]
      system-config-printer-0.6.142-1 </para>
    <para>[110889] system-config-securitylevel-1.5.8-1 -> [116959]
      system-config-securitylevel-1.6.4-1 </para>
    <para>[110271] system-config-services-0.8.25-1 -> [116537]
      system-config-services-0.8.26-1 </para>
    <para>[111388] system-config-soundcard-1.2.11-5 -> [116656]
      system-config-soundcard-1.2.12-5 </para>
    <para>[111429] system-config-display-1.0.29-1 -> [117812]
      system-config-display-1.0.31-1 </para>
    <para>[111664] alsa-lib-1.0.9rc4-2 -> [114503] alsa-lib-1.0.9rf-3
    </para>
    <para>[105652] tcl-8.4.9-3 -> [113371] tcl-8.4.11-1 </para>
    <para>[105658] tk-8.4.9-3 -> [113372] tk-8.4.11-1 </para>
    <para>[109302] lvm2-2.01.08-2.1 -> [118142] lvm2-2.01.14-2 </para>
    <para>[110929] device-mapper-1.01.02-1.0 -> [115634]
      device-mapper-1.01.04-1.0 </para>
    <para>[108262] libgnomecups-0.2.0-2 -> [117671]
      libgnomecups-0.2.1-1 </para>
    <para>[109132] tvtime-0.9.15-7 -> [117915] tvtime-1.0.1-1 </para>
    <para>- hpijs-1.7.1-3 </para>
    <para>[111138] shared-mime-info-0.16-3 -> [112690]
      shared-mime-info-0.16-4 </para>
    <para>[110914] evolution-data-server-1.2.2-3 -> [118144]
      evolution-data-server-1.4.0-2 </para>
    <para>[106495] gnome-keyring-0.4.2-1 -> [117659]
      gnome-keyring-0.4.4-1 </para>
    <para>[111218] udev-058-1 -> [118405] udev-069-4 </para>
    <para>- pcmcia-cs-3.2.8-4.12 </para>
    <para>- iiimf-le-xcin-0.1.10-1 </para>
    <para>[109118] gnome-netstatus-2.10.0-4 -> [116639]
      gnome-netstatus-2.11.90-2 </para>
    <para>[110265] perl-XML-NamespaceSupport-1.08-7 ->
      [117865] perl-XML-NamespaceSupport-1.09-1 </para>
    <para>[107102] memtest86+-1.55.1-1 -> [113262] memtest86+-1.60-1
    </para>
    <para>[100526] antlr-2.7.4-2jpp_1fc -> [112867]
      antlr-2.7.4-2jpp_2fc </para>
    <para>[111283] jakarta-commons-beanutils-1.7.0-1jpp_4fc ->
      [114381] jakarta-commons-beanutils-1.7.0-2jpp_2fc </para>
    <para>[111285] jakarta-commons-collections-3.1-1jpp_4fc ->
      [114380] jakarta-commons-collections-3.1-2jpp_2fc </para>
    <para>[101451] jakarta-commons-dbcp-1.2.1-3jpp_1fc -> [112880]
      jakarta-commons-dbcp-1.2.1-3jpp_2fc </para>
    <para>[111286] jakarta-commons-digester-1.6-2jpp_4fc -> [114394]
      jakarta-commons-digester-1.6-2jpp_6fc </para>
    <para>[111288] jakarta-commons-logging-1.0.4-2jpp_4fc -> [114180]
      jakarta-commons-logging-1.0.4-2jpp_6fc </para>
    <para>[111289] jakarta-commons-modeler-1.1-3jpp_4fc -> [114487]
      jakarta-commons-modeler-1.1-4jpp_2fc </para>
    <para>[101447] jakarta-commons-pool-1.2-2jpp_1fc -> [112885]
      jakarta-commons-pool-1.2-2jpp_2fc </para>
    <para>[101435] jakarta-commons-validator-1.1.3-1jpp_1fc ->
      [112887] jakarta-commons-validator-1.1.3-1jpp_2fc </para>
    <para>[100530] jdepend-2.6-2jpp_3fc -> [112928]
      jdepend-2.6-2jpp_4fc </para>
    <para>[111423] log4j-1.2.8-7jpp_4fc -> [112933]
      log4j-1.2.8-7jpp_5fc </para>
    <para>[96312] oro-2.0.8-1jpp_2fc -> [113162] oro-2.0.8-1jpp_3fc
    </para>
    <para>[109898] regexp-1.3-1jpp_5fc -> [114182] regexp-1.3-2jpp_3fc
    </para>
    <para>[100606] xalan-j2-2.6.0-2jpp_1fc -> [114410]
      xalan-j2-2.6.0-3jpp_3fc </para>
    <para>[109899] xerces-j2-2.6.2-4jpp_5fc -> [114312]
      xerces-j2-2.6.2-5jpp_2fc </para>
    <para>[109900] xml-commons-1.0-0.b2.6jpp_12fc -> [114196]
      xml-commons-1.0-0.b2.7jpp_3fc </para>
    <para>[96303] xml-commons-resolver-1.1-1jpp_4fc -> [113163]
      xml-commons-resolver-1.1-1jpp_5fc </para>
    <para>[101437] jakarta-commons-lang-2.0-2jpp_1fc -> [112883]
      jakarta-commons-lang-2.0-2jpp_2fc </para>
    <para>[96300] java_cup-0.10-0.k.1jpp_2fc -> [114395]
      java_cup-0.10-0.k.1jpp_5fc </para>
    <para>[100540] avalon-logkit-1.2-2jpp_4fc -> [113428]
      avalon-logkit-1.2-3jpp_1fc </para>
    <para>[101462] cryptix-3.2.0-4jpp_1fc -> [112869]
      cryptix-3.2.0-4jpp_2fc </para>
    <para>[101463] cryptix-asn1-20011119-4jpp_1fc -> [112873]
      cryptix-asn1-20011119-4jpp_2fc </para>
    <para>[101464] gnu.getopt-1.0.9-4jpp_1fc -> [112875]
      gnu.getopt-1.0.9-4jpp_2fc </para>
    <para>[110589] xorg-x11-6.8.2-31 -> [115364] xorg-x11-6.8.2-45
    </para>
    <para>[108218] aspell-is-0.51.1-1 -> [114361] aspell-is-0.51.1-2
    </para>
    <para>[106231] pyparted-1.6.9-3 -> [117327] pyparted-1.6.9-4
    </para>
    <para>[110354] mod_auth_kerb-5.0-6 -> [118413] mod_auth_kerb-5.0-7
    </para>
    <para>[106186] iprutils-2.0.13.7-2 -> [115548] iprutils-2.0.15.3-1
    </para>
    <para>[110365] tomcat5-5.0.30-5jpp_6fc -> [118323]
      tomcat5-5.0.30-8jpp_3fc </para>
    <para>[110776] xchat-2.4.3-3 -> [118268] xchat-2.4.5-1 </para>
    <para>[111287] jakarta-commons-el-1.0-2jpp_3fc -> [114396]
      jakarta-commons-el-1.0-4jpp_2fc </para>
    <para>- GFS-6.1-0.pre22.6 </para>
    <para>[107882] k3b-0.11.23-3 -> [114095] k3b-0.12.2-1 </para>
    <para>[111251] hal-0.5.2-2 -> [117285] hal-0.5.4-3 </para>
    <para>[107343] gnome-volume-manager-1.3.1-1 -> [117761]
      gnome-volume-manager-1.5.1-1 </para>
    <para>[106242] pam_passwdqc-0.7.6-1 -> [118214]
      pam_passwdqc-1.0.2-1 </para>
    <para>[106603] libidn-0.5.15-1 -> [118283] libidn-0.5.19-1 </para>
    <para>[110913] evolution-connector-2.2.2-5 -> [118165]
      evolution-connector-2.4.0-2 </para>
    <para>[111158] selinux-policy-targeted-1.23.16-6 -> [118397]
      selinux-policy-targeted-1.27.1-4 </para>
    <para>[111157] selinux-policy-strict-1.23.16-6 -> [118396]
      selinux-policy-strict-1.27.1-4 </para>
    <para>- ecj-3.1-0.M4.9 </para>
    <para>[104920] diskdumputils-1.0.1-6 -> [116910]
      diskdumputils-1.1.9-2 </para>
    <para>[108918] module-init-tools-3.1-3 -> [117811]
      module-init-tools-3.2-0.pre7.3 </para>
    <para>[104418] numactl-0.6.4-1.18 -> [113672] numactl-0.6.4-1.23
    </para>
    <para>[104522] libwmf-0.2.8.3-8 -> [115159] libwmf-0.2.8.4-1
    </para>
    <para>[107934] authd-1.4.3-4.devel -> [113028] authd-1.4.3-5.devel
    </para>
    <para>[112018] gamin-0.1.0-1.1 -> [118342] gamin-0.1.6-2 </para>
    <para>[111127] vino-2.10.0-4 -> [117670] vino-2.12.0-1 </para>
    <para>[109620] HelixPlayer-1.0.4-4 -> [116508]
      HelixPlayer-1.0.5-2 </para>
    <para>[110936] totem-1.0.2-1 -> [116504] totem-1.1.4-1 </para>
    <para>- gnbd-kernel-2.6.11.2-20050420.133124.FC4.35 </para>
    <para>[108039] aspell-de-0.50-10 -> [114277] aspell-de-0.50-11
    </para>
    <para>[109112] eclipse-changelog-2.0.1_fc-21 -> [114192]
      eclipse-changelog-2.0.1_fc-22 </para>
    <para>[111405] eclipse-cdt-3.0.0_fc-0.M6.7 -> [116981]
      eclipse-cdt-3.0.0_fc-1 </para>
    <para>- iiimf-le-chinput-0.3-19 </para>
    <para>[106138] synaptics-0.14.0-2 -> [115769] synaptics-0.14.3-3
    </para>
    <para>[110766] libsepol-1.5.9-2 -> [118331] libsepol-1.9.4-1
    </para>
    <para>[108031] aspell-af-0.50-2 -> [114179] aspell-af-0.50-4
    </para>
    <para>[103800] aspell-bg-0.50-9 -> [114176] aspell-bg-0.50-11
    </para>
    <para>[108032] aspell-br-0.50-2 -> [114181] aspell-br-0.50-4
    </para>
    <para>[108037] aspell-cy-0.50-2 -> [114274] aspell-cy-0.50-4
    </para>
    <para>[108040] aspell-el-0.50-2 -> [114278] aspell-el-0.50-4
    </para>
    <para>[108043] aspell-fo-0.51-2 -> [114281] aspell-fo-0.51-4
    </para>
    <para>[108045] aspell-ga-0.50-2 -> [114288] aspell-ga-0.50-4
    </para>
    <para>[108047] aspell-gd-0.50-2 -> [114357] aspell-gd-0.50-4
    </para>
    <para>[108048] aspell-gl-0.50-2 -> [114358] aspell-gl-0.50-4
    </para>
    <para>[108049] aspell-hr-0.51-2 -> [114359] aspell-hr-0.51-4
    </para>
    <para>[108050] aspell-id-0.50.1-2 -> [114360] aspell-id-0.50.1-4
    </para>
    <para>[105301] busybox-1.00-4 -> [111857] busybox-1.00-5 </para>
    <para>[104570] sysfsutils-1.2.0-4 -> [113812] sysfsutils-1.3.0-1
    </para>
    <para>- rgmanager-1.9.31-3 </para>
    <para>[109173] openswan-2.3.1-2 -> [118022] openswan-2.4.0-1
    </para>
    <para>[110687] NetworkManager-0.4-15.cvs20050404
      -> [118005] NetworkManager-0.4.1-2.cvs20050912
    </para>
    <para>[112106] java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh ->
      [118416] java-1.4.2-gcj-compat-1.4.2.0-40jpp_51rh </para>
    <para>[106674] gnome-keyring-manager-0.0.4-3 -> [117662]
      gnome-keyring-manager-2.12.0-1 </para>
    <para>[105646] evolution-webcal-2.2.0-1 -> [118166]
      evolution-webcal-2.4.0.1-2 </para>
    <para>[106722] krb5-auth-dialog-0.2-5 -> [116572]
      krb5-auth-dialog-0.2-6 </para>
    <para>[107396] dhcpv6-0.10-13 -> [116466] dhcpv6-0.10-14 </para>
    <para>[106006] dasher-3.2.15-1 -> [117634] dasher-3.2.18-1 </para>
    <para>[111497] firefox-1.0.4-4 -> [118182] firefox-1.5-0.5.0.beta1
    </para>
    <para>[110588] thunderbird-1.0.2-6 -> [116773] thunderbird-1.0.6-5
    </para>
    <para>- valgrind-callgrind-0.9.11-1 </para>
    <para>[106256] pam_ccreds-1-6 -> [112255] pam_ccreds-1-7 </para>
    <para>[100966] createrepo-0.4.2-2 -> [114098] createrepo-0.4.3-1
    </para>
    <para>[111205] audit-0.8.2-1 -> [116925] audit-1.0.3-1 </para>
    <para>[109751] kdewebdev-3.4.0-3 -> [116306] kdewebdev-3.4.2-1
    </para>
    <para>[98989] slib-3a1-2 -> [117769] slib-3a1-5 </para>
    <para>[105026] webalizer-2.01_10-28 -> [118412]
      webalizer-2.01_10-29 </para>
    <para>[108536] ipv6calc-0.48-5 -> [118194] ipv6calc-0.50-1 </para>
    <para>[100524] classpathx-mail-1.0-3jpp_1fc -> [111780]
      classpathx-mail-1.0-4jpp_2fc </para>
    <para>[111648] gnu-crypto-2.0.1-1jpp_5fc -> [114171]
      gnu-crypto-2.0.1-1jpp_7fc </para>
    <para>[107249] OpenIPMI-1.4.11-5 -> [117704] OpenIPMI-1.4.14-9
    </para>
    <para>[100864] zsh-4.2.1-2 -> [113141] zsh-4.2.5-1 </para>
    <para>[104688] sane-backends-1.0.15-9 -> [116782]
      sane-backends-1.0.16-1 </para>
    <para>- lvm2-cluster-2.01.09-3.0 </para>
    <para>- struts11-1.1-1jpp_7fc </para>
    <para>[107376] gkrellm-2.2.4-4 -> [117540] gkrellm-2.2.7-3 </para>
    <para>[108839] cpufreq-utils-0.2-1.1.14 -> [115418]
      cpufreq-utils-0.3-1.1.16 </para>
    <para>[108362] dmidecode-2.6-1.14 -> [117909] dmidecode-2.7-1.15
    </para>
    <para>[109300] hardlink-1.0-1.13 -> [117099] hardlink-1.0-1.14
    </para>
    <para>[111037] readahead-1.1-1.14 -> [115793] readahead-1.1-1.17
    </para>
    <para>[104427] smartmontools-5.33-1.5 -> [115762]
      smartmontools-5.33-1.7 </para>
    <para>[108364] x86info-1.13-1.10 -> [117440] x86info-1.15-1.13
    </para>
    <para>- python-twisted-1.3.0-4 </para>
    <para>[111505] evince-0.3.1-1 -> [118030] evince-0.4.0-2 </para>
    <para>[109178] gnome-doc-utils-0.2.0-2 -> [117722]
      gnome-doc-utils-0.4.0-1 </para>
    <para>[108845] gnome-menus-2.10.1-3 -> [117531]
      gnome-menus-2.12.0-1 </para>
    <para>[107103] gnome-python2-extras-2.10.0-2.1 -> [116816]
      gnome-python2-extras-2.11.4-9 </para>
    <para>[109933] gjdoc-0.7.4-5 -> [114163] gjdoc-0.7.5-4 </para>
    <para>[109753] kdelibs-3.4.0-6 -> [115465] kdelibs-3.4.2-1 </para>
    <para>[106258] kdeaccessibility-3.4.0-1 -> [116016]
      kdeaccessibility-3.4.2-1 </para>
    <para>[108603] fonts-korean-1.0.11-4 -> [116512]
      fonts-korean-1.0.11-6 </para>
    <para>[108601] fonts-japanese-0.20050222-3 -> [116488]
      fonts-japanese-0.20050222-7 </para>
    <para>[108604] fonts-chinese-2.15-2 -> [117399]
      fonts-chinese-3.00.pre2-1 </para>
    <para>[111507] poppler-0.3.2-1 -> [117476] poppler-0.4.2-1 </para>
    <para>[111030] eclipse-bugzilla-0.1.0_fc-16 -> [114650]
      eclipse-bugzilla-0.1.1_fc-5 </para>
    <para>[109095] eclipse-pydev-0.9.3_fc-7 -> [115587]
      eclipse-pydev-0.9.3_fc-11 </para>
    <para>[108005] sqlite-3.1.2-3 -> [117898] sqlite-3.2.5-1 </para>
    <para>[105636] python-urlgrabber-2.9.6-1 -> [118139]
      python-urlgrabber-2.9.6-3 </para>
    <para>[107161] cryptsetup-luks-1.0-1 -> [116857]
      cryptsetup-luks-1.0.1-2 </para>
    <para>[108817] jsch-0.1.18-1jpp_1fc -> [114185]
      jsch-0.1.18-1jpp_2fc </para>
    <para>[109747] latex2html-2002.2.1-3 -> [112874]
      latex2html-2002.2.1-4 </para>
    <para>[110960] openssl-0.9.7f-7 -> [116949] openssl-0.9.7f-9
    </para>
    <para>- iiimf-12.2-4 </para>
    <para>[108246] kdevelop-3.2.0-2 -> [116301] kdevelop-3.2.2-1
    </para>
    <para>- Canna-3.7p3-13 </para>
    <para>- VFlib2-2.25.6-28 </para>
    <para>[108287] perl-Archive-Zip-1.14-1 -> [117218]
      perl-Archive-Zip-1.16-1 </para>
    <para>[108275] pm-utils-0.01-1 -> [116385] pm-utils-0.04-1 </para>
    <para>[109632] foomatic-3.0.2-19 -> [118014] foomatic-3.0.2-28
    </para>
    <para>[108982] perl-DateManip-5.42a-4 -> [117863]
      perl-DateManip-5.44-1 </para>
    <para>- perl-libxml-enno-1.02-31 </para>
    <para>[104653] s390utils-1.3.2-4 -> [112864] s390utils-1.3.2-5
    </para>
    <para>[107373] m4-1.4.3-1 -> [118239] m4-1.4.3-2 </para>
    <para>[110355] ORBit2-2.12.1-3 -> [117666] ORBit2-2.12.4-1 </para>
    <para>[110242] GConf2-2.10.0-4 -> [117717] GConf2-2.12.0-1 </para>
    <para>[106017] libgnomecanvas-2.10.0-1 -> [117642]
      libgnomecanvas-2.12.0-1 </para>
    <para>[102603] libbonobo-2.8.1-1 -> [117820] libbonobo-2.10.1-2
    </para>
    <para>[109591] gnome-vfs2-2.10.0-5 -> [117664] gnome-vfs2-2.12.0-1
    </para>
    <para>[109285] libgnome-2.10.0-3 -> [117751] libgnome-2.12.0-1
    </para>
    <para>[109171] libbonoboui-2.8.1-4 -> [117749]
      libbonoboui-2.10.1-1 </para>
    <para>[104650] librsvg2-2.9.5-2 -> [117304] librsvg2-2.11.1-1
    </para>
    <para>[107485] eel2-2.10.0-2 -> [117651] eel2-2.12.0-1 </para>
    <para>[106316] tn5250-0.16.5-5 -> [113112] tn5250-0.16.5-6 </para>
    <para>[106143] yaboot-1.3.12-9 -> [118141] yaboot-1.3.13-0.16
    </para>
    <para>[107969] libgnomeui-2.10.0-1 -> [117980] libgnomeui-2.12.0-2
    </para>
    <para>[104629] libglade2-2.5.1-2 -> [116545] libglade2-2.5.1-3
    </para>
    <para>[105166] libIDL-0.8.5-2 -> [117667] libIDL-0.8.6-1 </para>
    <para>[110521] usermode-1.80-1 -> [116503] usermode-1.81-1 </para>
    <para>[102961] docbook-style-xsl-1.68.1-1 -> [116354]
      docbook-style-xsl-1.69.1-1 </para>
    <para>[104584] intltool-0.33-2 -> [115810] intltool-0.34.1-1
    </para>
    <para>[110237] evolution-2.2.2-5 -> [118148] evolution-2.4.0-2
    </para>
    <para>[104652] xmltex-20020625-5 -> [118338] xmltex-20020625-6
    </para>
    <para>[105333] pygtk2-2.6.0-2 -> [117772] pygtk2-2.8.0-1 </para>
    <para>[105908] gnome-python2-2.10.0-1 -> [116511]
      gnome-python2-2.11.3-2 </para>
    <para>[104649] libpng10-1.0.18-2 -> [115463] libpng10-1.0.18-3
    </para>
    <para>[96234] aspell-pt-0.50-9 -> [114369] aspell-pt-0.50-10
    </para>
    <para>[106303] stardict-2.4.4-3 -> [118242] stardict-2.4.5-1
    </para>
    <para>[108452] glibc-kernheaders-2.4-9.1.94 -> [111898]
      glibc-kernheaders-2.4-9.1.95 </para>
    <para>[105250] wordtrans-1.1pre13-10 -> [115775]
      wordtrans-1.1pre13-11 </para>
    <para>[104417] microcode_ctl-1.11-1.21 -> [118068]
      microcode_ctl-1.12-1.23 </para>
    <para>[109638] gnome-pilot-2.0.13-2 -> [116547]
      gnome-pilot-2.0.13-7.fc5 </para>
    <para>[106005] at-spi-1.6.3-1 -> [117632] at-spi-1.6.6-1 </para>
    <para>[110915] gail-1.8.3-2 -> [117635] gail-1.8.5-1 </para>
    <para>[106768] vsftpd-2.0.3-1 -> [117823] vsftpd-2.0.3-10 </para>
    <para>[108150] authconfig-4.6.12-1 -> [117485] authconfig-5.0.1-1
    </para>
    <para>[104665] linuxdoc-tools-0.9.21-5 -> [113333]
      linuxdoc-tools-0.9.21-6 </para>
    <para>[111809] gphoto2-2.1.5-10 -> [115052] gphoto2-2.1.6-2
    </para>
    <para>[104555] xmlto-0.0.18-6 -> [116003] xmlto-0.0.18-9 </para>
    <para>- perl-Time-HiRes-1.65-1 </para>
    <para>[108948] db4-4.3.27-3 -> [118387] db4-4.3.28-2 </para>
    <para>[107533] openmotif-2.2.3-10 -> [117413] openmotif-2.2.3-11
    </para>
    <para>[101890] docbook-dtds-1.0-26 -> [111825] docbook-dtds-1.0-27
    </para>
    <para>[111495] firstboot-1.3.42-1 -> [118187] firstboot-1.3.47-2
    </para>
    <para>[107310] cups-1.1.23-15 -> [117439] cups-1.1.23-17 </para>
    <para>[108639] postfix-2.2.2-2 -> [117702] postfix-2.2.5-1 </para>
    <para>[110444] booty-0.53-1 -> [118032] booty-0.57-1 </para>
    <para>[106326] cdicconf-0.2-11 -> [113538] cdicconf-0.2-12 </para>
    <para>[110352] libwnck-2.10.0-3 -> [117752] libwnck-2.12.0-1
    </para>
    <para>[110575] crypto-utils-2.2-5 -> [111863] crypto-utils-2.2-6
    </para>
    <para>[107303] perl-Compress-Zlib-1.34-2 -> [117468]
      perl-Compress-Zlib-1.37-1.fc5 </para>
    <para>[109590] libgtop2-2.10.1-1 -> [117665] libgtop2-2.12.0-1
    </para>
    <para>[110990] yelp-2.10.0-1 -> [117757] yelp-2.12.0-1 </para>
    <para>[110693] hwdata-0.158-1 -> [117804] hwdata-0.169-1 </para>
    <para>[106407] rhnlib-1.8-6.p24.1 -> [116200] rhnlib-1.8-6.p24.11
    </para>
    <para>[106361] arts-1.4.0-1 -> [115461] arts-1.4.2-1 </para>
    <para>[107873] dia-0.94-11 -> [116485] dia-0.94-13 </para>
    <para>[106665] gnome-system-monitor-2.10.0-2 -> [117663]
      gnome-system-monitor-2.12.0-1 </para>
    <para>[106473] pwlib-1.8.4-1 -> [117530] pwlib-1.8.7-1 </para>
    <para>[106475] openh323-1.15.3-1 -> [117538] openh323-1.15.6-1
    </para>
    <para>[106477] gnomemeeting-1.2.1-1 -> [118169]
      gnomemeeting-1.2.2-2 </para>
    <para>[93048] fonts-KOI8-R-1.0-7 -> [113604] fonts-KOI8-R-1.0-8
    </para>
    <para>[104596] patchutils-0.2.30-4 -> [114399] patchutils-0.2.31-2
    </para>
    <para>[107936] man-1.5p-4 -> [111925] man-1.5p-6 </para>
    <para>[110750] elinks-0.10.3-3 -> [112404] elinks-0.10.3-3.1
    </para>
    <para>[107263] netatalk-2.0.2-3 -> [114554] netatalk-2.0.3-2
    </para>
    <para>[107736] netdump-0.7.7-6 -> [115481] netdump-0.7.10-4
    </para>
    <para>[111279] ant-1.6.2-3jpp_8fc -> [115662] ant-1.6.2-3jpp_14fc
    </para>
    <para>[109158] openmotif21-2.1.30-14 -> [116779]
      openmotif21-2.1.30-17.1 </para>
    <para>[109640] gnutls-1.0.25-1 -> [115978] gnutls-1.2.6-1 </para>
    <para>[104487] privoxy-3.0.3-7 -> [117709] privoxy-3.0.3-9 </para>
    <para>[107117] eog-2.10.0-1 -> [117654] eog-2.12.0-1 </para>
    <para>[109172] gconf-editor-2.10.0-5 -> [117718]
      gconf-editor-2.12.0-1 </para>
    <para>[111105] gtk2-engines-2.6.3-2 -> [117640]
      gtk2-engines-2.6.5-1 </para>
    <para>[111267] gnome-desktop-2.10.0-5 -> [117723]
      gnome-desktop-2.12.0-1 </para>
    <para>[110510] gnome-panel-2.10.1-10 -> [118149]
      gnome-panel-2.12.0-2 </para>
    <para>[108570] gnome-session-2.10.0-2 -> [117729]
      gnome-session-2.12.0-1 </para>
    <para>[109748] gnome-terminal-2.10.0-2 -> [117730]
      gnome-terminal-2.12.0-1 </para>
    <para>[107500] metacity-2.10.0-1 -> [117759] metacity-2.12.0-1
    </para>
    <para>[107193] valgrind-2.4.0-2 -> [117903] valgrind-3.0.1-1
    </para>
    <para>[111389] vte-0.11.13-2.fc4 -> [117756] vte-0.11.15-1.fc5
    </para>
    <para>[105809] ghostscript-7.07-40 -> [116480]
      ghostscript-8.15-0.rc4.3 </para>
    <para>[108033] file-4.13-4 -> [118257] file-4.15-3 </para>
    <para>[108940] mgetty-1.1.33-1 -> [115032] mgetty-1.1.33-3_FC5
    </para>
    <para>[111301] xen-2-20050522 -> [118168] xen-3.0-0.20050912.fc5.1
    </para>
    <para>[106289] libraw1394-1.1.0-3 -> [114765]
      libraw1394-1.2.0-1.fc5 </para>
    <para>[108526] mod_perl-2.0.0-0.rc5.3 -> [112776]
      mod_perl-2.0.1-1.fc5 </para>
    <para>[103976] radvd-0.7.3-1_FC4 -> [114404] radvd-0.8-2.FC5
    </para>
    <para>[111033] ncpfs-2.2.4-8 -> [115462] ncpfs-2.2.4-9 </para>
    <para>[106079] prelink-0.3.4-3 -> [117615] prelink-0.3.6-1 </para>
    <para>[110767] netpbm-10.27-3 -> [116518] netpbm-10.29-1 </para>
    <section id="sn-packages-added">
      <title>??????????????????????????????</title>
      <para>
	&FC; ?????????????????????????????????????????????????????????????????????????????????
      </para>
      <para>scim-anthy-0.6.1-1.fc5 </para>
      <para>struts-1.2.4-2jpp_3fc </para>
      <para>jonas-4.3.3-1jpp_10fc </para>
      <para>nspr-4.6-4 </para>
      <para>scim-1.4.2-3 </para>
      <para>anthy-6829-3 </para>
      <para>system-config-cluster-0.9.69-1.0 </para>
      <para>axis-1.2.1-1jpp_1fc </para>
      <para>bsf-2.3.0-6jpp_2fc </para>
      <para>bsh-1.3.0-5jpp_1fc </para>
      <para>concurrent-1.3.2-2jpp_1fc </para>
      <para>dtdparser-1.21-2jpp_1fc </para>
      <para>jakarta-commons-discovery-0.3-1jpp_1fc </para>
      <para>jdom-1.0-1jpp_2fc </para>
      <para>wsdl4j-1.5.1-1jpp_1fc </para>
      <para>javacc-3.2-1jpp_3fc </para>
      <para>jakarta-commons-httpclient-3.0-0.rc2.0jpp_1fc </para>
      <para>castor-0.9.5-1jpp_1fc </para>
      <para>adaptx-0.9.6-1jpp_1fc </para>
      <para>amtu-1.0.2-1 </para>
      <para>xdoclet-1.2.2-2jpp_1fc </para>
      <para>xjavadoc-1.1-1jpp_1fc </para>
      <para>jgroups-2.2.6-1jpp_1fc </para>
      <para>hsqldb-1.80.1-1jpp_1fc </para>
      <para>jonathan-core-4.1-1jpp_4fc </para>
      <para>jonathan-jeremie-4.2-1jpp_4fc </para>
      <para>jrefactory-2.8.9-3jpp_1fc </para>
      <para>mockobjects-0.09-12jpp_2fc </para>
      <para>monolog-1.8.6-1jpp_5fc </para>
      <para>oldkilim-1.1.3-2jpp_3fc </para>
      <para>p6spy-1.3-2jpp_3fc </para>
      <para>fractal-2.2-2jpp_1fc </para>
      <para>velocity-1.4-3jpp_1fc </para>
      <para>werken.xpath-0.9.4-0.beta.9jpp_1fc </para>
      <para>gnu.regexp-1.1.4-7jpp_1fc </para>
      <para>nanoxml-2.2.3-3jpp_3fc </para>
      <para>asm-1.5.3-1jpp_1fc </para>
      <para>cairo-1.0.0-1 </para>
      <para>objectweb-anttask-1.2-1jpp_1fc </para>
      <para>objectweb-deploysched-0.2-1jpp_1fc </para>
      <para>carol-1.8.9.3-1jpp_5fc </para>
      <para>jacorb-2.2-3jpp_3fc </para>
      <para>jakarta-commons-cli-1.0-6jpp_1fc </para>
      <para>tanukiwrapper-3.1.1-4jpp_3fc </para>
      <para>tog-pegasus-2.4.1-4.FC5 </para>
      <para>joram-4.1.5-1jpp_5fc </para>
      <para>jotm-2.0.5-1jpp_3fc </para>
      <para>lucene-1.4.3-1jpp_1fc </para>
      <para>geronimo-specs-1.0-0.M2.2jpp_4fc </para>
      <para>jakarta-commons-codec-1.3-2jpp_1fc </para>
      <para>howl-logger-0.1.8-1jpp_3fc </para>
      <para>dhcdbd-1.8-1 </para>
      <para>aspell-ru-0.99f7-2 </para>
      <para>hplip-0.9.5-3 </para>
      <para>gpart-0.1h-1 </para>
      <para>iso-codes-0.47-1 </para>
      <para>gif89encoder-0.90-0.b.1jpp_1fc </para>
      <para>jonathan-rmi-3.1-5 </para>
      <para>pup-0.0.2-1 </para>
      <para>jorm-2.4.3-1jpp_2fc </para>
      <para>jorm-rdb-adapter-2.6-1jpp_1fc </para>
      <para>medor-1.4.4-1jpp_1fc </para>
      <para>medor-expression-1.4.2-1jpp_1fc </para>
      <para>perseus-cache-1.3.4-1jpp_1fc </para>
      <para>perseus-concurrency-1.4-1jpp_1fc </para>
      <para>perseus-dependency-1.4-1jpp_1fc </para>
      <para>perseus-distribution-1.3.2-1jpp_1fc </para>
      <para>perseus-fos-1.3.1-1jpp_1fc </para>
      <para>perseus-persistence-1.3.4-1jpp_1fc </para>
      <para>perseus-pool-1.3.3-1jpp_1fc </para>
      <para>systemtap-0.4.1-2 </para>
      <para>pcmciautils-007-1 </para>
      <para>scim-tables-0.5.3-4 </para>
      <para>libsemanage-1.3.2-1 </para>
      <para>scim-hangul-0.2.0-5.fc5 </para>
      <para>scim-pinyin-0.5.91-1 </para>
      <para>scim-chewing-0.2.1-1 </para>
      <para>scim-qtimm-0.9.4-1 </para>
      <para>libchewing-0.2.7-1 </para>
      <para>kasumi-0.9-3.fc5 </para>
      <para>kexec-tools-1.101-2 </para>
      <para>libsetrans-0.1.7-1 </para>
      <para>icu-3.4-4 </para>
      <para>libiec61883-1.0.0-8.fc5 </para>
    </section>
    <section>
      <title>??????????????????????????????</title>
      <para>
	??????????????????????????????????????????????????????
      </para>
      <para>ccs-0.25-0.17 </para>
      <para>cman-1.0-0.pre33.15 </para>
      <para>cman-kernel-2.6.11.5-20050601.152643.FC4.2 </para>
      <para>dlm-1.0-0.pre21.10 </para>
      <para>dlm-kernel-2.6.11.5-20050601.152643.FC4.2 </para>
      <para>fence-1.27-16 </para>
      <para>GFS-kernel-2.6.11.8-20050601.152643.FC4.2 </para>
      <para>gnbd-1.0-0.pre14.6 </para>
      <para>gulm-1.0-0.pre30.1 </para>
      <para>iddev-1.9-21 </para>
      <para>magma-1.0-0.pre21.7 </para>
      <para>magma-plugins-1.0-0.pre18.3 </para>
    </section>
  </section>
  <section>
    <title>??????</title>
    <para>
      ??????????????????????????? <application>system-config-mouse</application>
      ????????????????????????????????????????????????
      synaptic ??? 3 ??????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      ???????????????????????????????????????????????????????????????????????????????????????????
      ???????????????????????????????????????????????????????????????????????????????????????
    </para>
<!-- FIXME
    <para>
      Gbenson agreed to justify any inclusion of Java packages in
      FC5. Send a mail. Should include this info before test1 release 
    </para>
-->
  </section>

</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->



--- NEW FILE package-notes-ja_JP.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "This header makes editing XML easier" >
 <!ENTITY DISTRO "DISTRO">
 <!ENTITY DISTROVER "DISTROVER">
 <!ENTITY FEX "FEX">
 <!ENTITY FP "FP">
 <!ENTITY FC "FC" >
 <!ENTITY LOCALVER "LOCALVER">
 <!ENTITY RHL "RHL">
 <!ENTITY SERVER-TOOLS SYSTEM "/dev/null">
 <!ENTITY KERNEL SYSTEM "/dev/null">
 <!ENTITY SECURITY SYSTEM "/dev/null">
 <!ENTITY SEL SYSTEM "/dev/null">
 <!ENTITY PRINTING SYSTEM "/dev/null">
 <!ENTITY DATABASE-SERVERS SYSTEM "/dev/null">
 <!ENTITY MULTIMEDIA SYSTEM "/dev/null">
 <!ENTITY WEB-SERVERS SYSTEM "/dev/null">
 <!ENTITY SAMBA SYSTEM "/dev/null">
 <!ENTITY XORG SYSTEM "/dev/null">
 <!ENTITY DEVELOPMENT-TOOLS SYSTEM "./development-tools.xml">

]>
-->
<section id="sn-package-notes">
  <title>???????????????????????????</title>
  <!--
  FIXME
  Needs updating of entire contents for FC5.
  -->
  <para>
    ??????????????? &DISTRO; &DISTROVER;
    ??????????????????????????????????????????????????????????????????????????????
    ?????????????????????????????????Anaconda
    ???????????????????????????????????????????????????
  </para>
  <caution>
    <title>????????????????????????????????????</title>
    <para>
      ????????????????????? &DISTRO; &DISTROVER;
      ???????????????????????????????????????????????????
    </para>
  </caution>
  <section id="sn-basic-components">
    <title>?????????????????????</title>
    <para>
      ??????????????????????????????????????????????????????????????????????????????
    </para>
    <section>
      <title>&FEX; ???????????????</title>
      <para>
	&FEX; ???????????????????????????????????????????????? &FP; ?????????????????????
	&FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	&FC; &LOCALVER; ??????????????????????????? &FEX; ????????????????????????????????????????????????
      </para>
      <para>
	????????????????????????&FEX; ???????????????????????????????????????????????????
      </para>
      <para>
	<ulink
	  url="http://fedoraproject.org/wiki/Extras">http://fedoraproject.org/wiki/Extras</ulink>
      </para>
      <para>
	&FEX; ???????????????????????????????????????????????????????????????????????????<command>yum</command>
	?????????????????????????????????
      </para>
<screen>
<command>yum install <replaceable>&lt;packagename&gt;</replaceable></command>
</screen>
      <para>
	????????? <replaceable>&lt;packagename&gt;</replaceable>
	???????????????????????????????????????????????????????????????
	????????? <filename>abiword</filename>
	??????????????????????????????????????????????????????????????????
	<command>yum install abiword</command>
	?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
    </section>
    <section id="sn-audit-daemon">
      <title>?????????????????? <command>auditd</command> ??????????????????????????????</title>
      <para>
	?????? (audit) ????????????????????? auditd ????????????????????????????????????????????????
	<command>auditd</command>
	???????????????????????????????????????????????????????????????
	<filename>/var/log/audit/audit.log</filename>
	?????????????????????
	?????????????????????????????? <filename>/etc/auditd.conf</filename>
	?????????????????????
      </para>
      <para>
	&SEL; ???????????? AVC ????????????????????????????????????????????????????????????????????????
	??????????????????????????????
	<filename>/var/log/audit/audit.log</filename>
	????????????????????????
      </para>
      <para>
	auditd ??????????????????????????????????????????????????????????????????????????????
	syslog ??????????????????
	??????????????????????????????????????? <filename>/var/log/messages</filename>
	???????????????????????? <command>dmesg</command>
	????????????????????????????????????????????????
      </para>
      <para>
	??????????????????????????? PAM ?????????????????????????????????
	???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
      <para>
	????????????????????????????????????????????????????????????<parameter>audit=1</parameter>
	?????????????????????????????????????????????????????????????????????????????????
	????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
<screen>
<command>auditctl -e 1</command>
</screen>
    </section>
    <section id="sn-nptl">
      <title>LinuxThreads ??? NPTL</title>
      <para>
	???????????????????????? LinuxThreads
	???????????????????????????????????????????????????????????????????????????&FC;
	&LOCALVER; ?????????????????????/??????????????????????????????????????????
	NPTL ????????????????????????????????????????????????
      </para>
      <para>
	&RHL; 9	???????????????????????????????????????????????????????????????????????????????????????????????????????????? LinuxThreads ???????????????????????????????????????????????????
	NPTL ????????????????????????????????????(<parameter>-fexception</parameter>
	???????????????C ???????????????????????????)
	????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	?????????????????????
	<option>-I/usr/include/nptl</option> ???
	<option>-L/usr/lib{,64}/nptl</option>
	??????????????????????????????????????????
	??????????????? <parameter>lib{,64}</parameter> ??????DSO ???
	lib64 ?????????????????????????????????????????????????????????
	<filename>lib64/</filename>
	??????????????????????????? <filename>lib/</filename> ??????????????????????????????
      </para>
      <para>
	&FC; &LOCALVER; ??? LinuxThreads
	????????????????????????????????????????????????????????????????????????????????????
	???????????????????????? <filename>linuxthreads-devel</filename>
	???????????????????????????????????????????????????????????????????????????????????????
      </para>
<screen>
<option>-I/usr/include/linuxthreads -L/usr/lib{,64}/linuxthreads</option>
</screen>
      <para>
	?????????????????????????????????
      </para>
      <para>
	???????????????????????????????????????????????? glibc ??? libpgthread DSH
	????????????????????????????????????????????????????????????
	??????????????????????????????????????????????????????????????????
      </para>
<screen>
<envar>LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads</envar>
</screen>
      <para>
	??????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	????????? <envar>DT_RPATH</envar>????????????
	<envar>LD_LIBRARY_PATH</envar> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
      <para>
	??????????????????????????????LinuxThreads
	?????????????????????????????????????????????????????????????????????????????????
	??????????????????????????????????????????????????????
      </para>
      <important>
	<title>??????</title>
	<para>
	  FC5 ??? LinuxThreads
	  ???????????????????????????????????????????????????????????????????????????????????????
	  NPTL ??????????????????????????????????????????????????????
	</para>
      </important>
      <para>
	??????????????????NPTL ???????????????????????????????????????????????????????????????????????????
      </para>
    </section>
    <section>
      <title><filename>slocate</filename> ????????????????????????????????????</title>
      <para>
	<command>locate</command>
	???????????????????????????????????????????????????????????????????????????????????????????????????????????????
	<command>locate</command>
	???????????????????????????<filename>/etc/updatedb.conf</filename> ???????????????
	<computeroutput>DAILY_UPDATE</computeroutput> ??? <option>yes</option>
	?????????????????????????????????????????????????????????????????????????????????
      </para>
    </section>
    <section>
      <title><filename>openssh</filename> ????????????????????????????????????</title>
      <para>
	&FC; &LOCALVER; ??? OpenSSH ????????????????????? OpenSSH 3.9
	????????????????????? <filename>~/.ssh/config</filename>
	???????????????????????????????????????????????????????????????????????????
	???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<command>ssh</command>
	?????????????????????????????????
      </para>
      <para>
	<filename>~/</filename> ???????????????
	<filename>~/.ssh/config</filename>
	???????????????????????????????????????????????? 600
	????????????????????????????????????????????????????????????
      </para>
<screen>
ls -l ~/.ssh/config
-rw-------  1 username username 400 May  5 18:44 /home/username/.ssh/config
</screen>
      <para>
	?????????????????? <filename>~/</filename>
	???????????????????????????????????????????????????????????????????????????????????????????????????????????????
	<filename>/home/username/</filename> ?????????
      </para>
      <para>
	?????????????????????????????????OpenSSH ????????????????????????????????? X11
	???????????????????????????????????????????????????????????????
	X11 ?????????????????????????????? <option>-X</option> ?????????
	<option>-Y</option>
	????????????????????????????????????<filename>~/.ssh/config</filename>
	??????????????? <option>ForwardX11</option>
	????????????????????????????????????????????????????????????
      </para>
      <para>
	<option>-X</option> ???????????????????????????????????????
	<command>ssh</command> ?????????????????????????????????????????????????????????
	OpennSSH 3.8 ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? X11 ???????????????????????????
	?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????X11 ????????????????????????????????????
	?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	????????????????????????????????????????????????????????????????????????????????????????????? X11
	??????????????????????????????<option>-X</option>	??????????????????????????????
	<option>-Y</option> ??????????????????????????????
	ssh ?????????????????????
	???????????????<filename>~/.ssh/config</filename>
	???????????????????????? <option>ForwardX11Trusted</option>
	?????????????????????
      </para>
    </section>
    <section id="sn-perl">
      <title>Perl ?????????????????????????????????????????????</title>
      <para>
	<filename>perl-5.8.0</filename>,
	<filename>perl-5.8.1</filename>,
	<filename>perl-5.8.2</filename>
	????????????????????????????????????????????????????????????????????????????????????
	???????????????????????????????????? perl ?????????????????? perl
	???????????????????????????????????????&FC; &LOCALVER;
	??????????????? <filename>perl-5.8.6</filename>
	???????????????????????????????????????????????????
      </para>
    </section>
    &SERVER-TOOLS;
    &JAVA-PACKAGE;
  </section>

  <section id="sn-packages-core">
    <title>??????</title>
    <para>
      ???????????????????????????????????? &DISTRO;
      ????????????????????????????????????????????????????????????
    </para>
    <section>
      <title>yum</title>
      <para>
        yum ?????? sqllite ??????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
      <para>
        &FEX; ???????????????????????????????????????????????????????????????
      </para>
    </section>
    &KERNEL;
    &SECURITY;
  </section>
  &DEVELOPMENT-TOOLS;
  &I18N;
  &PRINTING;
<!--  no content for this release
  &DATABASE-SERVERS; -->
  &MULTIMEDIA;
  &WEB-SERVERS;
  &SAMBA;
  &XORG;
  &ENTERTAINMENT;
</section>

<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE printing-ja_JP.xml ---
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE project-overview-ja_JP.xml ---
  <section id="sn-whatitis">
    <title>&PROJ; ??????</title>
    <para>
    &PROJ; ???????????????Linux
    ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    ???????????????????????????????????????????????????
    ???????????????????????????????????????????????? &DISTRO;
    ????????????????????????????????????????????????????????????????????????????????????????????????????????????
    &RH; ???????????????????????????????????? &DISTRO;
    ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
    ?????????????????????&PROJ; ??? Web ???????????????????????????????????????
    </para>
    <para>
      <ulink
	url="http://fedora.redhat.com/">http://fedora.redhat.com/</ulink>
    </para>
    <para>
    Web ?????????????????????????????????????????????????????????????????????????????????
    </para>
    <itemizedlist>
      <listitem>
        <para>
	  fedora-list at redhat.com &mdash; &DISTRO; ?????????????????????????????????
	</para>
      </listitem>
      <listitem>
        <para>
	fedora-test-list at redhat.com &mdash;
	&DISTRO; ??????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
        <para>
	fedora-devel-list at redhat.com &mdash;
	??????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
        <para>
	fedora-docs-list at redhat.com &mdash;
	Documentation Project ???????????????
	</para>
      </listitem>
    </itemizedlist>
    <para>
    ?????????????????????????????????????????????????????????????????? "subscribe"
    ???????????????????????????
    <computeroutput><replaceable>&lt;listname&gt;</replaceable>-request</computeroutput>
    ????????????
      <computeroutput><replaceable>&lt;listname&gt;</replaceable></computeroutput>
    ???????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
    ??????
    </para>
    <para>
      <ulink url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
    </para>
    <para>
    ??????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      ???????????????
      rhl-list???rhl-beta-list???rhl-devel-list???rhl-docs-list
      ???????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      &PROJ; ?????????IRC (Internet Relay Chat) ????????????????????????????????? 
      IRC ?????????????????????????????????????????????????????????????????????????????????????????????
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
    IRC ?????????????????? &PROJ; ?????????????????????????????????freenode IRC
    ??????????????????????????????????????????????????????
    ????????????<filename>irc.freenode.net</filename> ??? IRC
    ?????????????????????????????????????????????????????????????????????????????????????????????????????????
    ?????????????????? freenode ?????????????????? 
    (<ulink
      url="http://www.freenode.net/">http://www.freenode.net/</ulink>)
    ??????????????????????????????
    &PROJ; ???????????? <filename>#fedora</filename> ????????????????????????
    &PROJ; ???????????? <filename>#fedora-devel</filename> ?????????????????????????????????
    ??????????????????????????????????????????????????????????????????????????????????????????????????????
    ?????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
    <filename>#fedora</filename> ?????????????????????????????????????????????????????????????????????????????? (<firstterm>nick</firstterm>) ?????????????????????????????????????????????
    ???????????????????????? <command>/join</command> ????????????????????????????????????
    </para>
    <note>
      <title>???</title>
      <para>
      &RH; ??? &PROJ; IRC ?????????????????????????????????????????????????????????????????????????????????
      </para>
    </note>
  </section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE samba-ja_JP.xml ---
<section id="sn-samba">
  <title>Samba???Windows ?????????????????????????????????</title>
  
  <para>
    ??????????????? Samba ??????????????????????????????????????????
    ??????????????????Linux ???????????????????????? Windows
    ?????????????????????????????????????????????????????????????????????????????????
  </para>

  <para>
    Windows ?????????????????? SMB ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &DISTRO; &DISTROVER; ???????????????????????????????????????
    ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
   </para>

  <para>
    ??????????????????Samba ????????????????????????????????? SMB
    ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    ??????????????? 2 ?????????????????????????????????
  </para>

  <itemizedlist>
    <listitem>
      <para>
	???????????????????????? WINS ???????????????????????????WINS ??????????????????????????????
	<filename>smb.conf</filename> ??? "<option>wins server</option>"
	????????????????????????????????????
      </para>
    </listitem>
    <listitem>
      <para>
	???????????????????????????????????????????????????
      </para>
    </listitem>
  </itemizedlist>

  <warning>
    <title>???????????????????????????????????????????????????????????????????????????????????????</title>  
    <para>
      ??????????????????????????????????????????????????????????????????????????????????????????
    </para>
  </warning>

  <para>
    ???????????????????????????????????????????????????????????????????????????
  </para>
  
  <para>
    <ulink url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478</ulink>
  </para>
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE security-ja_JP.xml ---
<section id="sn-security">
  <title>??????????????????</title>
  <para>
    ???????????? &FC; ???????????????????????????????????????????????????????????????
  </para>
  <para>
    <computeroutput>Pam_stack</computeroutput> ????????????????????????
    ????????? fedora-test-list (<ulink
    url="http://www.redhat.com/mailman/listinfo/fedora-test-list">http://www.redhat.com/mailman/listinfo/fedora-test-list</ulink>)
    ??????????????????????????????
  </para>
  <section id="sn-security-highlights">
    <title>??????????????????????????????</title>
    <para>
      ???????????? &FC; ???????????????????????????????????????????????????????????????
    </para>
    <para>
      ?????????????????????<filename>/etc/pki/</filename>
      ???????????????????????????????????????????????????
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      OpenSSL: <filename>/usr/share/ssl</filename> ??????????????????
      <filename>/etc/pki/tls</filename> ??? <filename>/etc/pki/CA</filename>
      ???????????????????????????
    </para>
    <para>
      Dovecot: ???????????? <filename>dovecot-openssl.cnf</filename>
      ??????????????? <filename>/etc/pki/dovecot/</filename>
      ??????????????????????????????????????????
    </para>
  </section>
  <section id="sn-security-selinux-changes">
    <title>SELinux ????????????</title>
    <para>
      MCS SELinux???????????????????????????
      ???????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      <ulink
	url="http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/msg00001.html">http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/msg00001.html</ulink>
    </para>
  </section>
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE server-tools-ja_JP.xml ---
<section id="sn-server-sys-config">
  <title>?????????????????????????????????????????????</title>
  <caution>
    <title>????????????????????????????????????</title>
    <para>
      ????????????????????? &DISTRO; &DISTROVER; ???????????????????????????????????????????????????
    </para>
  </caution>
  <para>
    ??????????????? &FC; ???????????? ???????????????????????????????????? GUI
    ??????????????????????????????????????????????????????
  </para>
  <section id="sn-system-config-lvm">
    <title><application>system-config-lvm</application></title>
    <para>
      ????????? LVM ????????? <application>system-config-lvm</application>
      ????????????????????????????????????????????????????????????
    </para>
  </section>
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE splash-ja_JP.xml ---
<section id="sn-splash">
  <title>&FC; &LOCALVER; ???????????????</title>
  <caution>
    <title>????????????????????????????????????</title>
    <para>
      ????????????????????? &DISTRO; &DISTROVER; ???????????????????????????????????????????????????
    </para>
  </caution>
  <para>
    &FC; ??? Linux ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    &FP; ??? &RH; ???????????????????????????????????? &FED;
    ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>
  <tip>
    <title>Latest Release Notes on the Web</title>
    <para>
      These release notes may be updated.  Visit <ulink
	url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>
      to view the latest release notes for &DISTRO; &DISTROVER;.
    </para>
  </tip>
<!-- save for when the FIG is actually updated
  <note>
    <title>???????????????????????????????????????????????????</title>
    <para>
      ???????????????????????????????????????????????? <citetitle>&FC; &LOCALVER;
      &IG;</citetitle> ??????????????????
      ???????????????????????????????????????????????????????????????????????????
      URL ???????????????????????????
    </para>
    <para>
      <ulink url="http://fedora.redhat.com/docs/fedora-install-guide-ja
/">http://fedora.redhat.com/docs/fedora-install-guide-ja/</ulink>
    </para>
  </note>  
-->
  <para>
    &FED; ?????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>
  <itemizedlist>
<!-- FIXME Return when the section is updated
    <listitem>
      <para>
	<xref linkend="sn-new-in-fc"/>
      </para>
    </listitem>
-->
    <listitem>
      <para>
	<xref linkend="sn-intro"/> &mdash; ?????????????????????????????????
      </para>
    </listitem>
    <listitem>
      <para>
	???????????????????????? (<ulink
	  url="http://fedora.redhat.com/participate/communicate/">http://fedora.redhat.com/participate/communicate/</ulink>) 
      </para>
    </listitem>
    <listitem>
      <para>
	&FP; ???????????? (<ulink
	  url="http://fedora.redhat.com/participate/">http://fedora.redhat.com/participate/</ulink>) 
      </para>
    </listitem>
    <listitem>
      <para>
	&FP; ???????????? (<ulink
	  url="http://fedora.redhat.com/about/">http://fedora.redhat.com/about/</ulink>)
      </para>
    </listitem>
  </itemizedlist>
<!-- commented out until the content can be updated
  <section id="sn-new-in-fc">
    <title>&FC; &LOCALVER; ??????????????????</title>
    <para>
      &FC; &LOCALVER; ??????????????????????????? &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      ?????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <itemizedlist>
      <listitem>
	<para>
          ?????????????????????????????? &mdash; &FED;
	  ????????????????????????????????????????????????????????????????????????GNOME 2.10
	  ??? KDE 3.4 ????????????????????????????????????????????????????????????
	  GNOME ????????????????????????????????????????????????????????? Clearlooks
	  ??????????????????????????????????????????????????????
	  ????????????????????? Red Hat Bluecurve
	  ?????????????????????????????????????????????<xref
	  linkend="ex-desktop-screenshot-clearlooks"/>
	  ????????????????????????
	</para>
	<example id="ex-desktop-screenshot-clearlooks">
	  <title>??????????????? Clearlooks ??? Evince ??????????????????????????????</title>
	  <mediaobject id="txt-fedora-desktop-screenshot">
	    <imageobject>
	      <imagedata fileref="./figs/Fedora_Desktop.eps" format="EPS"/>
	    </imageobject>
	    <imageobject>
	      <imagedata fileref="./figs/Fedora_Desktop.png" format="PNG"/>
	    </imageobject>
	    <textobject>
	      <para>
		Fedora ??????????????????????????????????????????????????????????????????
		Firefox ??????????????????????????????????????????????????????????????????????????????
		Evince ???????????????????????????
		Evince ??? Lawrence Lessig ??? Free Culture ????????????????????????
	      </para>
	    </textobject>
	  </mediaobject>
	</example>      
      </listitem>
      <listitem>
	<para>
	  ??????????????????
	</para>
	<itemizedlist>
	  <listitem>
	    <para>
	      Evince (<ulink
		url="http://www.gnome.org/projects/evince/">http://www.gnome.org/projects/evince/</ulink>) 
	      ??? pdf???postscript
	      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	      ???????????????????????????????????????????????????????????????Evince ??????????????????????????????????????????????????????????????????
	    </para>
	  </listitem>
	  <listitem>
	    <para>
	      OpenOffice.org 2.0 (<ulink
		url="http://www.openoffice.org/product2/index.html">http://www.openoffice.org/product2/index.html</ulink>)
	      ????????????????????????????????????
	      ??????????????????????????????
	      Microsoft Office ????????????????????????????????????????????????????????????????????????????????????????????????
	      Impress???OpenDocument
	      ???????????????????????????????????????-?????????????????????????????????
	      ???????????????????????????????????????????????????????????????????????????????????????????????????????????????
	      Base ????????????????????????
	      ??????????????????????????????????????????
	      <ulink url="http://marketing.openoffice.org/2.0/featureguide.html">http://marketing.openoffice.org/2.0/featureguide.html</ulink>
	      ????????????????????????
	      </para>
	  </listitem>
	  <listitem>
	    <para>
	      Eclipse 3.1 ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	      (<acronym>IDE</acronym>) ?????????
	    </para>
	  </listitem>
	</itemizedlist>
      </listitem>
      <listitem>
	<para>
	  PowerPC (PPC) ????????????????????????????????????????????? &mdash;
	  <xref linkend="sn-hardware-reqs-ppc"/>
	  ?????????
	  <xref linkend="sn-install-notes-ppc"/>
	  ?????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  ??????????????????????????? &mdash; &SEL; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ?????????????????? targetd ??????????????????????????? 80
	  ?????????????????????????????????????????????????????????????????????
	  ????????????????????????????????? <xref linkend="sn-overview"/>
	  ??????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  ?????????????????????????????????????????? &mdash; Global File System
	  (<acronym>GFS</acronym>)
	  ??????????????????????????????????????????????????????????????????????????????Linux
	  ??????????????????????????????????????????????????????????????????????????????????????????????????????
	  &FC; &LOCALVER; ??????????????????????????????????????????????????????????????? GFS ???????????????????????????????????????????????????
	  <ulink url="http://www.redhat.com/software/rha/gfs/">http://www.redhat.com/software/rha/gfs/</ulink> 
	  ?????????
	  <ulink url="http://www.redhat.com/docs/manuals/enterprise/">http://www.redhat.com/docs/manuals/enterprise/</ulink>
	  ?????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  ??????????????????????????? &mdash; Xen ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  Xen ????????????????????????????????????????????? &FC; ?????????????????????????????????
	  <ulink url="http://fedora.redhat.com/projects/virtualization/">http://fedora.redhat.com/projects/virtualization/</ulink>
	  ??? Xen ?????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  ????????????????????????????????? &mdash; &FC; &LOCALVER; ???
	  GNU Compiler Collection ???????????? 4.0 ??????????????????
	  ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? JAVA ???????????????????????????????????????
	  ????????????????????????????????? OpenOffice.org 2.0., Eclipse,  Apache Jakarta ???????????????????????????
	</para>
      </listitem>
    </itemizedlist>
  </section>
-->
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE web-servers-ja_JP.xml ---
<section id="sn-web-servers">
  <title>Web ????????????</title>
  <para>
    ??????????????? Web ??????????????????????????????????????????????????????
  </para>
  <section>
    <title><command>httpd</command></title>
    <para>
      ???????????????????????????????????? <command>httpd</command>
      ??????????????????????????????????????????
    </para>
    <itemizedlist>
      <listitem>
	<para>
	  <computeroutput>mod_cern_meta</computeroutput> ???
	  <computeroutput>mod_asis</computeroutput>
	  ??????????????????????????????????????????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  <computeroutput>mod_ext_filter</computeroutput>
	  ????????????????????????????????????????????????????????????????????????????????????
	</para>
      </listitem>
    </itemizedlist>
  </section>
</section>
<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE xorg-ja_JP.xml ---
<section id="sn-xwindows">
  <title>X Window System????????????????????????</title>
  <caution>
    <title>????????????????????????????????????</title>
    <para>
      ????????????????????? &DISTRO; &DISTROVER; ???????????????????????????????????????????????????
    </para>
  </caution>
  <para>
    ??????????????????&DISTRO; ??????????????????????????? X Window System
    ???????????????????????????????????????
  </para>
  <section id="sn-xwindows-xorg">
    <title><filename>xorg-x11</filename></title>
    <para>
      X.org ??? X11 ????????????????????????????????????????????????????????? &RH;
      ??? &FED; ???????????????????????????????????????????????????????????? XFree86.org ??? X11
      ?????????????????????????????????????????????????????????????????????????????????
      ??????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      X ???????????????????????????
    </para>
    <itemizedlist>
      <listitem>
	<para>XFree86 X11: <filename>XFree86</filename></para>
      </listitem>
      <listitem>
	<para>X.org X11: <filename>Xorg</filename></para>
      </listitem>
    </itemizedlist>
    <para>
      X ??????????????????????????????
    </para>
    <itemizedlist>
      <listitem>
	<para>XFree86 X11:
	  <filename>/etc/X11/XF86Config</filename></para>
      </listitem>
      <listitem>
	<para>X.org X11: <filename>/etc/X11/xorg.conf</filename></para>
      </listitem>
    </itemizedlist>
    <para>
      X ??????????????????????????????
    </para>
    <itemizedlist>
      <listitem>
	<para>XFree86 X11:
	  <filename>/var/log/XFree86.<replaceable>$DISPLAY</replaceable>.log</filename></para>
      </listitem>
      <listitem>
	<para>X.org X11:
	  <filename>/var/log/Xorg.<replaceable>$DISPLAY</replaceable>.log</filename></para>
      </listitem>
    </itemizedlist>
    <para>
      ?????????????????? X ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      &DISTRO; ???????????????????????????????????????????????? &RHL;????????????X
      Window System ??????????????????????????????????????????????????????????????????
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <itemizedlist>
      <listitem>
	<para>
	  ?????????????????????15??????????????????????????????????????????????????????<firstterm>core
	    X font ??????????????????</firstterm> ?????????????????????
	  ???????????????????????????????????????????????????????????????????????????????????????????????????X
	  ??????????????????????????????????????????????????????????????????????????????????????????
	  <computeroutput>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</computeroutput>
	</para>
      </listitem>
      <listitem>
	<para>
	  ?????????????????????????????????????????????<firstterm>fontconfig</firstterm>
	  ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  fontconfig ???????????? <filename>Xft</filename>
	  ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  fontconfig ??????????????????????????????????????????????????????????????????????????????
	  <computeroutput>Luxi Sans-10</computeroutput>
	</para>
      </listitem>
    </itemizedlist>
    <para>
      ?????????fontconfog/<filename>Xft</filename> ???????????????
      core X ??????????????????????????????????????????????????????????????????????????????
      ?????????Qt 3 ????????? GTK 2 ??????????????????????????????????????????????????????????????????????????????
      KDE ??? GNOME ?????????????????????????????????????????????
      fontconfig ??? Xft ????????????????????????????????????????????????????????????????????????????????????????????????
      core X ????????????????????????????????????
    </para>
    <para>
      ??????????????????&FC; ???????????????????????????????????????????????????????????????????????????XFS
      ??????????????????????????????????????? fontconfig/Xft ????????????????????????????????????????????????
    </para>
    <note>
      <title>???</title>
      <para>
	????????????????????????????????????????????????????????????????????????
	OpenOffice.org 
	????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
    </note>
    <para>
      &DISTRO; &DISTROVER;
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      core X ???????????????????????????????????????????????????????????????????????????
    </para>

    <procedure>
      <step>
	<para>
	  <filename>/usr/share/fonts/local/</filename>
	  ?????????????????????????????????????????????????????????
	</para>
<screen>
<command>mkdir /usr/share/fonts/local/</command>
</screen>
      </step>
      <step>
	<para>
	  ????????????????????????????????????
	  <filename>/usr/share/fonts/local/</filename>
	  ?????????????????????
	</para>
      </step>
      <step>
	<para>
	  ???????????????????????????????????????????????????????????????????????????????????????:
	  ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  ??????????????????????????????????????????????????????????????????????????????
	</para>
<screen>
<command>ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</command>
<command>mkfontdir /usr/share/fonts/local/</command>
</screen>
      </step>
      <step>
	<para>
	  ?????? <filename>/usr/share/fonts/local/</filename>
	  ??????????????????????????????????????????????????????X ????????????????????????
	  (<command>xfs</command>) ????????????????????????????????????
<screen>
<command>chkfontpath --add /usr/share/fonts/local/</command>
</screen>
	</para>
      </step>
    </procedure>
    <para>
      fontconfig ???????????????????????????????????????????????????????????????????????????????????????????????????
      ???????????????????????????????????? <filename>/usr/share/fonts/</filename>
      ???????????????????????????????????????????????????
      ?????????????????????????????? <filename>~/.fonts/</filename>
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      ??????????????????<command>fc-cache</command>
      ?????????????????????????????????????????????????????????????????????????????????
    </para>
<screen>
<command>fc-cache <replaceable>&lt;directory&gt;</replaceable></command>
</screen>
    <para>
      ????????????
      <command><replaceable>&lt;directory&gt;</replaceable></command>
      ??????<filename>/usr/share/fonts/</filename>
      ????????? <filename>~/.fonts/</filename>
      ??????????????????????????????????????????????????????
    </para>
    <para>
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????
      <application>Nautilus</application> ??? <command>fonts:///</command>
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <note>
      <title>???</title>
      <para>
	???????????????????????????????????? "<filename>.gz</filename>"
	??????????????????????????????????????? <command>gzip</command>
	?????????????????????????????????fontconfig
	??????????????????????????????????????????????????????<command>gunzip</command>
	??????????????????????????????????????????????????????????????????
      </para>
    </note>      
    <para>
      fontconfig/Xft ??????????????????????????????????????????????????????????????????????????????GTK+
      1.2 ???????????????????????????<guilabel>???????????????????????????</guilabel>???????????????????????????????????????????????????????????????????????????????????????
      ???????????????????????????????????????????????????????????????????????????
      <filename>~/.gtkrc.mine</filename>
      ?????????????????????????????????????????????????????????
    </para>
<screen>    
<computeroutput>style "user-font" {
fontset = "<replaceable>&lt;font-specification&gt;</replaceable>"
}
widget_class "*" style "user-font"</computeroutput>
</screen>
    <para>
      ????????????
      <command><replaceable>&lt;font-specification&gt;</replaceable></command> 
      ??????
      "<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>"
      ????????????????????? X
      ???????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
  </section>
</section>

<!--
Local variables:
mode: xml
coding: utf-8-unix
sgml-parent-document:("RELEASE-NOTES-ja_JP.xml" "article" "section")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Thu Nov  3 15:22:22 2005
From: fedora-docs-commits at redhat.com (Tatsuo Sekine (tsekine))
Date: Thu,  3 Nov 2005 10:22:22 -0500
Subject: release-notes Makefile,1.5,1.6
Message-ID: <200511031522.jA3FMMmP018631@cvs-int.fedora.redhat.com>

Author: tsekine

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18614

Modified Files:
	Makefile 
Log Message:
The generic rule is added for XMLEXTRAFILE-${LANG}.



Index: Makefile
===================================================================
RCS file: /cvs/docs/release-notes/Makefile,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- Makefile	30 Oct 2005 02:36:48 -0000	1.5
+++ Makefile	3 Nov 2005 15:22:14 -0000	1.6
@@ -12,7 +12,13 @@
 #
 LANGUAGES      	= en
 DOCBASE        	= RELEASE-NOTES
-XMLEXTRAFILES-en=daemons-en.xml database-servers-en.xml desktop-en.xml development-tools-en.xml feedback-en.xml file-servers-en.xml file-systems-en.xml hardware-reqs-en.xml install-notes-en.xml intro-en.xml java-package-en.xml kernel-en.xml misc-server-en.xml multimedia-en.xml networking-en.xml overview-en.xml package-movement-en.xml package-notes-en.xml printing-en.xml project-overview-en.xml samba-en.xml security-en.xml server-tools-en.xml splash-en.xml web-servers-en.xml xorg-en.xml
+
+define XMLEXTRAFILES_template
+XMLEXTRAFILES-$(1)=daemons-$(1).xml desktop-$(1).xml development-tools-$(1).xml feedback-$(1).xml file-servers-$(1).xml hardware-reqs-$(1).xml install-notes-$(1).xml intro-$(1).xml java-package-$(1).xml kernel-$(1).xml misc-server-$(1).xml multimedia-$(1).xml networking-$(1).xml overview-$(1).xml package-movement-$(1).xml package-notes-$(1).xml printing-$(1).xml project-overview-$(1).xml samba-$(1).xml security-$(1).xml server-tools-$(1).xml splash-$(1).xml web-servers-$(1).xml xorg-$(1).xml
+endef
+
+$(foreach LANG,${LANGUAGES},$(eval $(call XMLEXTRAFILES_template,${LANG})))
+
 #
 ######################################################
 include ../docs-common/Makefile.common



From fedora-docs-commits at redhat.com  Thu Nov  3 15:31:49 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu,  3 Nov 2005 10:31:49 -0500
Subject: docs-common/css fedora.css,1.7,1.8
Message-ID: <200511031531.jA3FVnLV018810@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/css
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18772

Modified Files:
	fedora.css 
Log Message:
Center paragraph (aka figure) titles, since the figure is also centered.



Index: fedora.css
===================================================================
RCS file: /cvs/docs/docs-common/css/fedora.css,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora.css	30 Jul 2005 01:44:15 -0000	1.7
+++ fedora.css	3 Nov 2005 15:31:40 -0000	1.8
@@ -132,3 +132,7 @@
 	/* prevent inheritance */
 	margin-bottom: 0em;
 }
+
+p.title	{
+	text-align: center;
+}



From fedora-docs-commits at redhat.com  Thu Nov  3 16:29:50 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu,  3 Nov 2005 11:29:50 -0500
Subject: docs-common README,1.10,1.11
Message-ID: <200511031629.jA3GTovR021743@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21718

Modified Files:
	README 
Log Message:
Added note about the possibility that these "css/" stylesheets will not
be the same stylesheets used for production document rendering.`



Index: README
===================================================================
RCS file: /cvs/docs/docs-common/README,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- README	27 Jun 2005 19:49:20 -0000	1.10
+++ README	3 Nov 2005 16:29:43 -0000	1.11
@@ -20,6 +20,11 @@
 
 		Cascading Style Sheets (CSS) that control the "look
 		and feel" used to render documents in HTML format.
+
+		NOTE: These may not be the same stylesheets used for
+		final production rendering.  Just use them as a guide
+		to ensure your XML is correct, but do not expect the
+		finished documents to look the same.
 	
 	stylesheet-images/
 	



From fedora-docs-commits at redhat.com  Fri Nov  4 13:38:48 2005
From: fedora-docs-commits at redhat.com (Yuan Yijun (bbbush))
Date: Fri,  4 Nov 2005 08:38:48 -0500
Subject: install-guide fedora-install-guide-abouttoinstall-zh_CN.xml, NONE,
 1.1 fedora-install-guide-acknowledgements-zh_CN.xml, NONE,
 1.1 fedora-install-guide-beginninginstallation-zh_CN.xml, NONE,
 1.1 fedora-install-guide-bootloader-zh_CN.xml, NONE,
 1.1 fedora-install-guide-diskpartitioning-zh_CN.xml, NONE,
 1.1 fedora-install-guide-firewallconfig-zh_CN.xml, NONE,
 1.1 fedora-install-guide-firstboot-zh_CN.xml, NONE,
 1.1 fedora-install-guide-installingpackages-zh_CN.xml, NONE,
 1.1 fedora-install-guide-installtypes-zh_CN.xml, NONE,
 1.1 fedora-install-guide-intro-zh_CN.xml, NONE,
 1.1 fedora-install-guide-locale-zh_CN.xml, NONE,
 1.1 fedora-install-guide-networkconfig-zh_CN.xml, NONE,
 1.1 fedora-install-guide-nextsteps-zh_CN.xml, NONE,
 1.1 fedora-install-guide-other-instmethods-zh_CN.xml, NONE,
 1.1 fedora-install-guide-packageselection-zh_CN.xml, NONE,
 1.1 fedora-install-guide-rootpassword-zh_CN.xml, NONE,
 1.1 fedora-install-guide-timezone-zh_CN.xml, NONE,
 1.1 fedora-install-guide-upgrading-zh_CN.xml, NONE, 1.1 fed!
 ora-install-guide-zh_CN.xml,NONE,1.1
Message-ID: <200511041338.jA4Dcmk8028227@cvs-int.fedora.redhat.com>

Author: bbbush

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28193

Added Files:
	fedora-install-guide-abouttoinstall-zh_CN.xml 
	fedora-install-guide-acknowledgements-zh_CN.xml 
	fedora-install-guide-beginninginstallation-zh_CN.xml 
	fedora-install-guide-bootloader-zh_CN.xml 
	fedora-install-guide-diskpartitioning-zh_CN.xml 
	fedora-install-guide-firewallconfig-zh_CN.xml 
	fedora-install-guide-firstboot-zh_CN.xml 
	fedora-install-guide-installingpackages-zh_CN.xml 
	fedora-install-guide-installtypes-zh_CN.xml 
	fedora-install-guide-intro-zh_CN.xml 
	fedora-install-guide-locale-zh_CN.xml 
	fedora-install-guide-networkconfig-zh_CN.xml 
	fedora-install-guide-nextsteps-zh_CN.xml 
	fedora-install-guide-other-instmethods-zh_CN.xml 
	fedora-install-guide-packageselection-zh_CN.xml 
	fedora-install-guide-rootpassword-zh_CN.xml 
	fedora-install-guide-timezone-zh_CN.xml 
	fedora-install-guide-upgrading-zh_CN.xml 
	fedora-install-guide-zh_CN.xml 
Log Message:



--- NEW FILE fedora-install-guide-abouttoinstall-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-abouttoinstall">
  <title>??????????????????</title>
  <para>????????? <guilabel>Next</guilabel> ????????????????????????????????????????????????????????????????????????????????????????????????&FC; ??????????????????????????????????????????????????????????????????????????????????????? <guilabel>Back</guilabel>????????????????????????????????????????????????????????????</para>
  <important>
    <title>??????????????????</title>
    <para>?????????????????????????????????????????????????????????&FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  </important>
  <figure id="fig-about-to-install">
    <title>???????????????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/about-to-install.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/about-to-install.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>??????????????????????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>
  <para>?????? <guilabel>Next</guilabel> ??????????????????</para>
  <para>???????????????????????????????????????????????????&FC; ?????????????????????????????????????????????????????????????????????????????????????????? <guibutton>Reboot</guibutton> ?????????????????????????????????????????? <guibutton>Continue</guibutton>???</para>
</chapter>


--- NEW FILE fedora-install-guide-acknowledgements-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-acknowledgements">
  <title>??????</title>
  <para>Rahul Sundaram ??? Anaconda ????????????????????????????????????????????????</para>
</chapter>


--- NEW FILE fedora-install-guide-beginninginstallation-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-beginninginstallation">
  <title>????????????</title>
  <para>??????????????? &FC;?????????????????????????????????????????????????????? CD ??? DVD ?????????USB ?????????????????????????????????????????????????????????</para>
  <note>
    <title>??????????????????</title>
    <para>??????????????????????????? &FC;???</para>
  </note>
  <para>
    <indexterm>
      <primary>BIOS (????????????????????????)</primary>
    </indexterm> ??????????????????<firstterm>BIOS</firstterm> (Basic Input/Output System) ???????????????????????????????????????BIOS ?????????????????????????????????????????????????????? &FC; ?????????????????????????????????????????? CD ??? DVD ???????????????????????????????????????USB ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <indexterm><primary>PXE (Pre-boot eXecution Environment)</primary></indexterm><firstterm>PXE</firstterm> ?????????PXE (????????? "pixie") ???????????????????????????????????????????????????????????????????????????????????????</para>
  <para>??????????????????????????????????????????????????????????????????????????? BIOS?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  <note>
    <title>????????????</title>
    <para>?????? <guilabel>Installing Packages</guilabel> ???????????????????????????????????????????????????????????? <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo> ?????????????????????????????????????????????&FED; ?????????????????????????????????????????????????????????????????????</para>
  </note>
  <section id="sn-booting-from-disc">
    <title>???????????????</title>
    <para>????????????????????????????????????</para>
    <procedure>
      <step>
        <para>????????????????????????</para>
      </step>
      <step>
        <para>???????????????????????? CD ??? DVD ????????????</para>
      </step>
      <step>
        <para>????????????????????????????????????????????? <prompt>boot:</prompt> ????????????</para>
      </step>
    </procedure>
    <figure id="fig-boot">
      <title>????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/boot.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/boot.png" format="PNG"/>
        </imageobject>
        <textobject id="tx-boot">
          <phrase>&FC; ????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>??????????????? <keycap>Enter</keycap>?????????????????????????????????????????????????????????????????????????????? CD ??? DVD ???????????????????????????????????????????????????????????????????????? <prompt>boot:</prompt> ?????????????????? <userinput>linux</userinput> ???????????????????????????????????????</para>
    <itemizedlist>
      <listitem>
        <para>????????????????????????????????????????????????????????? <userinput>askmethod</userinput>???</para>
      </listitem>
      <listitem>
        <para>???????????????????????????????????? <userinput>text</userinput></para>
      </listitem>
      <listitem>
        <para>????????????????????????????????????????????????????????????????????????????????? <userinput>acpi=off</userinput>???</para>
      </listitem>
    </itemizedlist>
    <para>????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FDPDOCS-URL; ?????????</para>
    <para>????????? <prompt>boot:</prompt> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <figure id="fig-media-test">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/media-test.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/media-test.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????? <guibutton>OK</guibutton> ?????????????????????????????? <guibutton>Skip</guibutton> ???????????????????????????????????????</para>
    <caution>
      <title>????????????</title>
      <para>????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    </caution>
    <para>????????????????????????????????????????????????????????????????????????????????????</para>
    <figure id="fig-mediacheck-result">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/mediacheck-result.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/mediacheck-result.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????? <guibutton>OK</guibutton>??????????????????????????????</para>
    <figure id="fig-mediacheck-next">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/mediacheck-next.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/mediacheck-next.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????? <guibutton>Test</guibutton> ???????????????????????????????????? <guibutton>Continue</guibutton> ????????????????????????</para>
    <!--

    <note>
      <title>The <guilabel>Media Check</guilabel> may fail usable
	discs</title>
      <para>
	Discs that are valid and usable may still fail to pass the
	<guilabel>Media Check</guilabel>.
      </para>
    </note>

    Let's hash this out before we print this in the guide.  The media
    check performs a MD5 checksum over the entire data area of a CD,
    save for a small reserved area at the top, which is not used for any
    installation data.  It is possible for a disc to fail this sum and
    still install, because the error may occur in, for example, a RPM
    package that the user has not selected.  However, the user may
    encounter this error later when he tries to install that package.
    Or he may pass the disc(s) on to another person, who may make
    different choices and thus induce the media error.

    It's best to have discs that pass this check; although the user
    *may* not have a problem, we don't want to encourage people to try
    installing from bad discs on that chance. - PWF.

-->
    <para>?????????????????????????????? <guibutton>Continue</guibutton> ??????????????????????????????????????????????????????????????????????????????????????????</para>
    <para>???????????????????????????????????????????????????????????????????????? <prompt>boot:</prompt> ?????????????????? <userinput>linux askmethod</userinput>???&FC; ?????????????????????????????????????????? CD????????????????????? ISO ???????????????????????? &FC; ???????????????????????????????????? <filename>images/boot.iso</filename>???</para>
    <para>???????????? ISO ???????????????????????????????????? CD ??????????????? CD ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? CD ????????????????????????????????????????????? Linux???????????????????????????????????? CD ?????????????????????????????????????????? CD ??????</para>
    <screen>
      <userinput>cdrecord --device=<replaceable>cdwriter-device</replaceable> -tao -eject <replaceable>image-file.iso</replaceable></userinput>
    </screen>
    <note>
      <title>BIOS ????????????</title>
      <para>BIOS ?????????????????????????????????????????????????????????????????? &FC; ??????????????????????????????????????????????????? BIOS ???????????????</para>
    </note>
  </section>
  <section id="sn-using-otherbootmedia">
    <title>???????????????????????????</title>
    <para>????????? USB ?????????????????????????????????????????????????????? CF ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <section id="sn-preparing-otherbootmedia">
      <title>??????????????????</title>
      <warning>
        <title>????????????</title>
        <para>
          <emphasis>??????????????????????????????????????????</emphasis> ???????????????????????????????????????????????????????????? USB ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
      </warning>
      <para>????????? &FC; ?????????????????? <filename>images/diskboot.img</filename> ???????????? USB ????????????????????????????????????????????????????????????????????? &FC; ??? FTP ??? Web ??????????????????</para>
      <para>??? Windows ??? Linux ?????????????????????????????????????????????????????????????????????Linux ?????? <command>dd</command> ???????????????????????????????????????????????????????????????????????????????????? &FC; ??????????????? <command>dd</command> ?????????</para>
      <procedure>
        <step>
          <para>?????????????????????</para>
        </step>
        <step>
          <para>????????????????????????</para>
        </step>
        <step>
          <para>???????????????????????????????????????????????????????????????????????????????????????????????????</para>
        </step>
        <step>
          <para>???????????????????????????</para>
        </step>
        <step>
          <para>?????????????????????????????????????????????<screen><userinput>dd if=diskboot.img of=/dev/sdax</userinput></screen></para>
        </step>
      </procedure>
    </section>
    <section id="sn-booting-from-otherbootmedia">
      <title>???????????????</title>
      <para>??????????????????????????????????????????</para>
      <procedure>
        <step>
          <para>????????????????????????</para>
        </step>
        <step>
          <para>????????????????????????</para>
        </step>
        <step>
          <para>????????????????????????????????? <prompt>boot:</prompt> ??????????????????????????????????????? <keycap>Enter</keycap> ??????</para>
        </step>
      </procedure>
      <note>
        <title>BIOS ????????????</title>
        <para>BIOS ?????????????????????????????????????????????????????????????????? &FC; ??????????????????????????????????????????????????? BIOS ???????????????</para>
      </note>
    </section>
  </section>
  <section id="sn-booting-from-pxe">
    <title>?????? PXE ???????????????</title>
    <para>????????? <indexterm><primary>PXE (Pre-boot eXecution Environment)<primary> PXE </primary></primary></indexterm></para>
    <para>????????????????????????????????????????????????????????? BIOS ???????????????????????? <option>Network Boot</option> ??? <option>Boot Services</option>??????????????????????????? PXE ??????????????????????????? &FED; ???????????????????????????????????????</para>
    <para>????????? PXE ???????????????????????????</para>
    <procedure>
      <step>
        <para>??????????????????????????????????????????????????????????????????????????????????????????????????????</para>
      </step>
      <step>
        <para>????????????????????????</para>
      </step>
      <step>
        <para>???????????????????????????????????????????????????????????????????????????????????????</para>
      </step>
    </procedure>
    <figure id="fig-pxe-instmethod">
      <title>???????????? Red Hat ??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/pxe-instmethod.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/pxe-instmethod.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>Red Hat ???????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>??????????????????????????????????????????</para>
    <note>
      <title>PXE ????????????</title>
      <para>???????????????????????????????????????????????????????????? BIOS ?????????????????????????????????????????????????????? BIOS ?????????????????????????????????????????????????????????????????? PXE ?????????????????????????????????????????????????????????</para>
    </note>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-bootloader-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-bootloader">
  <title>???????????????</title>
  <para>
    <firstterm>boot loader</firstterm> ?????????????????????????????????????????????????????????????????????&FC; ???????????? <application>GRUB</application> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  <para>???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? Linux ?????????????????????????????? &FC;????????? <application>GRUB</application> ???????????????????????????????????? Linux ??????????????????????????????????????????????????????????????? <application>GRUB</application>???</para>
  <warning>
    <title>?????? GRUB</title>
    <para>??????????????? GRUB??????????????????????????????????????????</para>
  </warning>
  <para>?????????????????????????????????????????????????????????</para>
  <figure id="fig-bootloader-config">
    <title>???????????????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="figs/bootloader-config.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="figs/bootloader-config.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>??????????????????????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>
  <section id="sn-bootloader-config-change">
    <title>???????????????????????????????????????</title>
    <para>????????????????????????????????? GRUB ??????????????????????????????????????? <firstterm>master boot record</firstterm>, <indexterm><primary>master boot record</primary></indexterm> ???????????????????????? <abbrev>MBR</abbrev> ??????????????????????????????????????????????????????????????????????????? <guibutton>Change boot loader</guibutton> ???????????? <xref linkend="fig-bootloader-change"/> ?????????????????????????????????????????????????????????????????????????????????</para>
    <figure id="fig-bootloader-change">
      <title>?????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-change.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-change.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>??????????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <important>
      <title>?????????????????????</title>
      <para>???????????????????????? <application>GRUB</application> ???????????????????????????????????????????????????????????????????????????????????????</para>
    </important>
  </section>
  <section id="sn-bootloader-others">
    <title>????????????????????????</title>
    <para>?????????????????????????????????????????????&FC; ??????????????????????????? <application>GRUB</application> ??????????????????????????????????????????????????????????????????????????? <application>GRUB</application> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <variablelist>
      <varlistentry>
        <term>
          <guibutton>??????</guibutton>
        </term>
        <listitem>
          <para>?????? <guibutton>Add</guibutton> ?????? GRUB ?????????????????????????????????&FC; ????????? <xref linkend="fig-bootloader-others-popup"/> ????????????</para>
          <para>???????????????????????????????????????????????????????????????????????????????????????????????????<application>GRUB</application> ??????????????????????????????????????????</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guibutton>??????</guibutton>
        </term>
        <listitem>
          <para>????????? GRUB ?????????????????????????????????????????????????????? <guibutton>Edit</guibutton> ?????????</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guibutton>??????</guibutton>
        </term>
        <listitem>
          <para>?????? GRUB ????????????????????????????????????????????????????????????????????? <guibutton>Delete</guibutton> ?????????</para>
        </listitem>
      </varlistentry>
    </variablelist>
    <figure id="fig-bootloader-others-popup">
      <title>?????????????????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-others.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-others.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>??? GRUB ???????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
  </section>
  <section id="sn-bootloader-password">
    <title>??????????????????????????????</title>
    <para>
      <application>GRUB</application> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <application>GRUB</application> ????????????????????????????????????????????????????????????????????????????????????</para>
    <tip>
      <title>????????? GRUB ??????</title>
      <para>???????????????????????????????????????????????????????????????????????????????????????????????????????????? <application>GRUB</application> ?????????</para>
      <para>?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <application>GRUB</application>?????????????????????????????????</para>
    </tip>
    <para>?????????????????????????????? <guibutton>Use a boot loader password</guibutton> ?????????????????? <guibutton>Change password</guibutton> ???????????????????????? <guibutton>Change password</guibutton> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <figure id="fig-bootloader-password">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-password.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-password.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>???????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <tip>
      <title>?????????????????????</title>
      <para>??????????????????????????????????????????????????????????????????</para>
    </tip>
    <warning>
      <title>????????? <application>GRUB</application> ??????</title>
      <para>
        <application>GRUB</application> ???????????????????????????????????????<emphasis>??????</emphasis> ????????????????????????????????????????????????????????????????????????????????????????????????????????? <filename>/boot/grub/grub.conf</filename> ???????????????????????????????????????????????????????????? &FC; ??????????????????????????? "rescue" ?????????????????????????????? GRUB ?????????</para>
    </warning>
    <para>???????????????????????? <application>GRUB</application> ??????????????? <command>grub-md5-crypt</command> ??????????????????????????????????????????????????????????????????????????? <command>man grub-md5-crypt</command> ?????????????????????</para>
  </section>
  <section id="sn-bootloader-advanced">
    <title>???????????????????????????</title>
    <para>??????????????????????????????????????????????????????????????????????????? <application>GRUB</application> ???????????????????????? <indexterm><primary>master boot record</primary></indexterm> ??????????????? (<abbrev>MBR</abbrev>) ?????????????????????????????????????????????</para>
    <para>??????????????? <abbrev>MBR</abbrev> ??????????????????????????????????????????????????? <application>GRUB</application> ??????????????? Linux ?????????????????????????????????????????????</para>
    <para>???????????? <abbrev>BIOS</abbrev> ?????? &FC; ??????????????????????????????????????????????????????????????????????????????????????? <abbrev>BIOS</abbrev> ?????????&FC; ??????????????????????????????????????????????????????????????????????????????????????? <guibutton>Force LBA32</guibutton> ?????????</para>
    <para>Linux ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <note>
      <title>????????????</title>
      <para>????????????????????????????????????????????????????????????????????????????????????<userinput>man bootparam</userinput>??????????????????????????????????????????????????????????????????????????????</para>
    </note>
    <para>?????????????????????????????????????????? <guibutton>Configure advanced boot loader options</guibutton> ?????????????????? <guibutton>Next</guibutton>???????????? <xref linkend="fig-bootloader-advanced"/> ??????????????????</para>
    <note>
      <title>???????????????</title>
      <para>
        <emphasis>??????</emphasis> ??????????????????????????????????????????????????????&FC; ??????????????????????????????????????????</para>
    </note>
    <figure id="fig-bootloader-advanced">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-advanced.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-advanced.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>??????????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-diskpartitioning-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-disk-partitioning">
  <title>????????????</title>
  <para>???????????? Linux ????????????????????????????????????????????????????????????????????????????????? Linux ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  <figure id="fig-partitioning-setup">
    <title>????????????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="figs/partitioning-setup.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="figs/partitioning-setup.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>????????????????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>
  <section id="sn-choosing-partition-method">
    <title>????????????????????????</title>
    <section id="sn-automatic-partitioning">
      <title>??????????????????</title>
      <para>????????????????????? <guilabel>Automatic partitioning</guilabel> ?????????????????????????????????<application>Disk Druid</application> ????????????????????????????????????</para>
      <figure id="fig-partitioning-automatic">
        <title>????????????????????????</title>
        <mediaobject>
          <imageobject>
            <imagedata align="center" fileref="figs/partitioning-automatic.eps" format="EPS"/>
          </imageobject>
          <imageobject>
            <imagedata align="center" fileref="figs/partitioning-automatic.png" format="PNG"/>
          </imageobject>
          <textobject>
            <phrase>??????????????????</phrase>
          </textobject>
        </mediaobject>
      </figure>
      <variablelist>
        <varlistentry>
          <term>
            <guilabel>????????????????????? Linux ??????</guilabel>
          </term>
          <listitem>
            <para>???????????????????????? <firstterm>ext2</firstterm>, <firstterm>ext3</firstterm> ??? <firstterm>Linux swap</firstterm> ???????????????</para>
          </listitem>
        </varlistentry>
        <varlistentry>
          <term>
            <guilabel>??????????????????????????????</guilabel>
          </term>
          <listitem>
            <para>?????????????????? <emphasis>??????<emphasis> ????????????</emphasis></emphasis></para>
          </listitem>
        </varlistentry>
        <varlistentry>
          <term>
            <guilabel>???????????????????????????????????????????????????</guilabel>
          </term>
          <listitem>
            <para>????????????????????? <emphasis>???????????????</emphasis> ????????? &FC;</para>
          </listitem>
        </varlistentry>
      </variablelist>
      <para>????????????????????????</para>
      <para>??????????????????????????????????????? Linux ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? Linux ?????????????????????????????????????????????????????????????????????????????????????????????</para>
      <note>
        <title>????????????</title>
        <para>?????????????????????????????????????????????????????????????????????????????? Linux Partition-HOWTO???????????? <ulink url="http://www.tldp.org/HOWTO/Partition/partition-2.html">http://www.tldp.org/HOWTO/Partition/partition-2.html</ulink>???</para>
      </note>
      <para>??????????????????????????????????????? <guilabel>Review</guilabel> ????????????</para>
      <para>?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guibutton>Next</guibutton> ??????????????????????????????????????? <xref linkend="ch-bootloader"/>???</para>
    </section>
    <section id="sn-manual-partitioning">
      <title>??????????????????</title>
      <para>?????????????????????????????????????????? <guilabel>Manually partition with Disk Druid</guilabel>???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <xref linkend="sn-disk-druid"/>?????????????????? <xref linkend="sn-partitioning-general"/>???</para>
    </section>
  </section>
  <section id="sn-partitioning-general">
    <title>?????????????????????</title>
    <para>&FC; ?????????????????????????????????</para>
    <itemizedlist>
      <listitem>
        <para>?????????????????????????????? <filename>/boot</filename></para>
      </listitem>
      <listitem>
        <para>?????????????????????????????? <filename>/</filename></para>
      </listitem>
      <listitem>
        <para>?????? swap ????????????</para>
      </listitem>
    </itemizedlist>
    <para>?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <xref linkend="sn-choosing-partition-method"/> ????????????????????????</para>
    <para>??????????????????????????? <indexterm><primary>mount point</primary></indexterm><firstterm>mount point</firstterm> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <filename>/</filename> (<indexterm><primary>partition</primary><secondary>root</secondary></indexterm><firstterm>root</firstterm> ???) ????????????</para>
    <important>
      <title>???????????? <filename>/root</filename></title>
      <para>
        <filename>/</filename> (<indexterm><primary>partition</primary><secondary>root</secondary></indexterm> ???) ?????????????????????????????????<indexterm><primary>partition</primary><secondary><filename>/root</filename></secondary></indexterm><filename>/root</filename> (???????????? "slash-root") ??????????????????????????????????????????</para>
    </important>
    <para>???????????????????????????</para>
    <itemizedlist>
      <listitem>
        <para>?????? <filename>/boot</filename> ??????????????????????????? <filename>/boot</filename> ??????????????????????????? <filename>/boot/grub/grub.conf</filename> ????????? <filename>/boot</filename> ????????????</para>
      </listitem>
      <listitem>
        <para>?????? <filename>/boot</filename> ?????????????????????????????? <filename>/etc/passwd</filename>???????????? <filename>/</filename> ????????????</para>
      </listitem>
    </itemizedlist>
    <para>??????????????????????????????????????????????????????????????????????????????????????? <filename>/usr</filename> ??? <filename>/usr/local</filename> ???????????????????????????<filename>/usr/local/</filename> ??????????????????????????? <filename>/usr/local/bin/foo</filename> ???????????? <filename>/usr/local</filename> ???????????????<filename>/usr</filename> ????????????????????????????????? <filename>/usr/bin/foo</filename> ??????????????? <filename>/usr</filename> ????????????</para>
    <para>????????????????????????????????????????????????????????? <filename>/</filename> ????????????????????????????????????????????? <application>Disk Druid</application> ??? <link linkend="disk-druid-edit">Edit option</link> ????????????????????????????????????</para>
    <section id="sn-partitioning-types">
      <title>????????????</title>
      <para>???????????????????????? <indexterm><primary>partition</primary><secondary>type</secondary><seealso>file system</seealso></indexterm><firstterm>partition type</firstterm> ?????????????????????????????????????????? <indexterm><primary>file system</primary></indexterm><firstterm>file system</firstterm> ?????????????????????????????????????????? Linux ??????????????????????????????????????????????????????????????? <indexterm><primary><systemitem class="filesystem">ext3</systemitem></primary><see>file system</see></indexterm><indexterm><primary>file systemext3ext3 </primary></indexterm></para>
    </section>
    <section id="sn-partitioning-lvm">
      <title>?????? LVM</title>
      <indexterm>
        <primary>LVM</primary>
        <secondary>??????</secondary>
      </indexterm>
      <para>LVM ???Logical Volume Management) ???????????????????????????????????????????????????????????????LVM ????????????????????? <indexterm><primary>LVM</primary><secondary>physical volume</secondary></indexterm><firstterm>physical volumes</firstterm> ?????????????????????????????????????????????????????? <indexterm><primary>LVM</primary><secondary>volume group</secondary></indexterm><firstterm>volume group</firstterm> ?????????????????????????????????????????????????????????????????????????????? <indexterm><primary>LVM</primary><primary>logical volume</primary></indexterm><firstterm>logical volumes</firstterm> ????????????????????????????????????????????????????????????????????????????????????????????????????????? <systemitem class="filesystem">ext3</systemitem>???????????????????????????</para>
      <para>????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? RAID ????????????</para>
      <note>
        <title>??????????????? LVM</title>
        <para>??????????????????????????????????????? LVM ??????</para>
      </note>
    </section>
  </section>
  <!-- some notes follow:

    Sanity checks on partitions require:
    /usr  ge 250 MB
    /tmp  ge  50
    /var  ge 384
    /home ge 100
    /boot ge  75
    /     ge 250

    for ia64:
    /boot/efi ge 50 MB

    Cannot have these as separate partitions:
    /bin /dev /sbin /etc /lib /root lost+found /proc

    Cannot make partitions for these symlinks:
    /var/mail /usr/bin/X11 /usr/lib/X11 /usr/tmp

-->
  <section id="sn-disk-druid">
    <title>Disk Druid</title>
    <para>
      <indexterm>
        <primary>Disk Druid</primary>
      </indexterm>
      <application>
        <firstterm>Disk Druid</firstterm>
      </application> ?????????????????????????????????????????????????????????????????????????????? &FC; ???????????????????????????Disk Druid ?????? <indexterm><primary>RAID</primary></indexterm><firstterm>RAID</firstterm> ??? <indexterm><primary>LVM</primary></indexterm><firstterm>LVM</firstterm>????????????????????????????????????????????????</para>
    <figure id="fig-disk-setup">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/disk-setup.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/disk-setup.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>??????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>
      <application>Disk Druid</application> ???????????????????????????????????????</para>
    <variablelist>
      <varlistentry id="vle-disk-druid-new">
        <term>
          <guilabel>??????</guilabel>
        </term>
        <listitem>
          <para>?????????????????????????????????????????????????????? <indexterm><primary>partition</primary><secondary>adding</secondary></indexterm> ?????? LVM ??????????????? <guilabel>Add partition</guilabel> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? MB ????????????</para>
          <important>
            <title>????????????</title>
            <para>
              <indexterm>
                <primary>partition</primary>
                <secondary>illegal</secondary>
              </indexterm> ?????? <filename>/bin/</filename>, <filename>/dev/</filename>, <filename>/etc/</filename>, <filename>/lib/</filename>, <filename>/proc/</filename>, <filename>/root/</filename>, ?????? <filename>/sbin/</filename> ?????????????????????????????????????????? <application>Disk Druid</application> ?????????????????????????????? <indexterm><primary>partition</primary><secondary>root</secondary></indexterm><filename>/</filename> (???) ?????????</para>
            <para>
              <filename>/boot</filename> ?????????????????? LVM ??????????????????????????????????????????????????? <filename>/boot</filename> ?????????</para>
          </important>
          <para>?????????????????????????????????????????????</para>
          <variablelist>
            <varlistentry>
              <term>
                <guilabel>Fixed size</guilabel>
              </term>
              <listitem>
                <para>???????????????????????????????????????????????????</para>
              </listitem>
            </varlistentry>
            <varlistentry>
              <term>
                <guilabel>??????????????????</guilabel>
              </term>
              <listitem>
                <para>???????????????????????????????????????????????????</para>
              </listitem>
            </varlistentry>
            <varlistentry>
              <term>
                <guilabel>Fill to maximum allowable size</guilabel>
              </term>
              <listitem>
                <para>????????????????????????????????????????????????</para>
              </listitem>
            </varlistentry>
          </variablelist>
          <note>
            <title>????????????</title>
            <para>????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
          </note>
          <para>??????????????????????????????????????????????????? <guibutton>OK</guibutton> ?????????</para>
        </listitem>
      </varlistentry>
      <varlistentry id="disk-druid-edit">
        <term>
          <guilabel>??????</guilabel>
        </term>
        <listitem>
          <para>?????????????????????????????????????????????<indexterm><primary>partition</primary><secondary>editing</secondary></indexterm> LVM ??????????????????????????????????????????????????????????????? LVM ??????????????????????????????????????????????????????????????????</para>
          <warning>
            <title>?????? LVM ??????</title>
            <para>?????????????????????????????????????????? LVM ??????????????????????????????????????????????????????</para>
          </warning>
          <para>??????????????????????????????????????????????????????????????????????????????????????????????????????</para>
          <itemizedlist>
            <listitem>
              <para>??????????????????????????????</para>
            </listitem>
            <listitem>
              <para>?????? Linux ?????????????????????????????????????????? &FC; ??????</para>
            </listitem>
            <listitem>
              <para>?????? Linux ???????????????????????????</para>
            </listitem>
          </itemizedlist>
          <note>
            <title>Windows ??????</title>
            <para>??? &FC; ???????????????????????? <indexterm><primary><systemitem class="filesystem">NTFS</systemitem></primary><see>file system</see></indexterm><indexterm><primary>file system</primary><secondary><systemitem class="filesystem">NTFS</systemitem></secondary></indexterm><systemitem class="filesystem">NTFS</systemitem> ??????????????????????????????????????????????????? <indexterm><primary><systemitem class="filesystem">vfat</systemitem></primary><see>file system</see></indexterm><indexterm><primary>file system</primary><secondary><systemitem class="filesystem">vfat</systemitem></secondary></indexterm><systemitem class="filesystem"><firstterm>vfat</firstterm></systemitem> (<systemitem class="filesystem">FAT16</systemitem> ??? <systemitem class="filesystem">FAT32</systemitem>) ?????????????????????????????????</para>
          </note>
          <para>??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
          <para>??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <indexterm><primary>partition</primary><secondary><filename>/home</filename></secondary></indexterm><filename>/home</filename> ???????????????????????????????????????????????????????????????????????????????????? <filename>/boot</filename>???</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>??????</guilabel>
        </term>
        <listitem>
          <para>???????????????????????????????????????????????? <indexterm><primary>partition</primary><secondary>deleting</secondary></indexterm> ?????? LVM ??????????????????????????? LVM ???????????????????????????????????????????????????</para>
          <para>?????????????????????????????? <guilabel>Reset</guilabel> ?????????????????????????????????????????????</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>??????</guilabel>
        </term>
        <listitem>
          <para>???????????????????????? <application>Disk Druid</application> ?????????????????????????????????????????????</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>RAID</guilabel>
        </term>
        <listitem>
          <para>???????????????????????? &FED; ????????????????????? RAID <indexterm><primary>RAID</primary></indexterm>???</para>
          <variablelist>
            <varlistentry>
              <term>
                <guilabel>?????????????????? RAID ??????</guilabel>
              </term>
              <listitem>
                <para>?????????????????????????????? RAID ?????????????????????????????????????????????????????? RAID ??????????????????????????????????????????????????????</para>
              </listitem>
            </varlistentry>
            <varlistentry>
              <term>
                <guilabel>???????????? RAID ??????</guilabel>
              </term>
              <listitem>
                <para>??????????????????????????????????????????????????? RAID ?????????????????? RAID ??????????????????????????????????????????????????? RAID ????????????????????????????????????</para>
              </listitem>
            </varlistentry>
            <varlistentry>
              <term>
                <guilabel>????????????????????????????????? RAID ?????????</guilabel>
              </term>
              <listitem>
                <para>?????????????????????????????????????????? RAID <firstterm>mirror</firstterm> ???????????????????????????????????????????????????????????????????????????????????????</para>
              </listitem>
            </varlistentry>
          </variablelist>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>LVM</guilabel>
        </term>
        <listitem>
          <para>?????????????????????????????? &FED; ??????????????? LVM <indexterm><primary>LVM</primary></indexterm>??????????????? <application>Next</application> ????????????????????????????????????????????? RAID ????????????????????? LVM ????????????</para>
          <para>??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>Add</guilabel>, <guilabel>Edit</guilabel> ??? <guilabel>Delete</guilabel> ?????????</para>
          <para>?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? 5GB LVM ???????????????????????????????????????????????? 8GB ??????????????????????????????????????????????????????????????????????????????????????????????????????????????? 5GB ????????????????????? 8GB ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? 4GB ???????????????????????????????????????????????????</para>
        </listitem>
      </varlistentry>
    </variablelist>
    <para>????????????????????????????????????????????? <guilabel>Next</guilabel> ????????????????????????</para>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-firewallconfig-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-security-config">
  <title>????????????</title>
  <para>&FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  <figure id="fig-firewall">
    <title>??????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/firewall.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/firewall.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>?????????????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>
  <para>???????????????????????????????????????????????????????????????????????? <guibutton>Next</guibutton> ????????????</para>
  <section id="sn-firewall-settings">
    <title>?????????</title>
    <para>&FC; ?????? <indexterm><primary>firewall</primary></indexterm><firstterm>firewall</firstterm>???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <para>??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FED; ?????????????????????????????????</para>
    <para>???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <para>????????????????????????????????????????????????????????? <guilabel>No firewall</guilabel>???</para>
    <tip>
      <title>?????????????????????</title>
      <para>??????????????????????????????????????????????????????????????? <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu>Security Level and Firewall</menuchoice></para>
    </tip>
  </section>
  <section id="sn-selinux">
    <title>&SEL;</title>
    <para>
      <indexterm>
        <primary>&SEL;</primary>
      </indexterm>
      <firstterm>&SEL;</firstterm> (??????????????? Linux ??????)??? &FC; ???????????????&SEL; ???????????????????????????????????????????????????????????????????????????????????????????????????????????? &SEL; ????????????????????????????????????????????????????????????????????????&SEL; ??????????????????????????????????????????????????????????????????</para>
    <para>??????????????? &SEL; ?????????????????? &FED; ?????????????????????????????? &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &SEL; ??????????????????????????????????????? &SEL; ????????????????????????</para>
    <variablelist>
      <varlistentry>
        <term>
          <guilabel>Active</guilabel>
        </term>
        <listitem>
          <para>?????????????????????????????? &FED; ??????????????? &SEL; ??????????????????????????? &FED; ????????????????????????</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>Warn</guilabel>
        </term>
        <listitem>
          <para>?????? &SEL; ?????????????????????????????????????????????????????????????????????????????????????????? &SEL; ????????????????????????????????????????????????????????????????????????????????????????????? &SEL; ?????????????????????????????????????????????????????????????????????????????????????????? &SEL; ??????????????? <guilabel>Active</guilabel></para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>Disabled</guilabel>
        </term>
        <listitem>
          <para>?????????????????????????????????&FED; ???????????????????????????????????????????????????????????? &SEL;??????????????????????????? <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guimenuitem>Security Level and Firewall</guimenuitem></menuchoice>???</para>
        </listitem>
      </varlistentry>
    </variablelist>
    <tip>
      <title>?????? &SEL; ??????</title>
      <para>&SEL; ?????????????????????????????????????????????????????????????????????????????????????????? &SEL; ???????????????????????????????????? <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guimenuitem>Security Level and Firewall</guimenuitem></menuchoice>???</para>
    </tip>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-firstboot-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-firstboot">
  <title>????????????</title>
  <para>
    <application>Setup Agent</application> ?????????????????????????????? &FC; ???????????????????????? <application>Setup Agent</application> ??????????????????????????????</para>
  <figure id="fig-fboot-welcome">
    <title>????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/fboot-welcome.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/fboot-welcome.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>???????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>
  <para>?????? <guibutton>Next</guibutton> ????????? <application>Setup Agent</application>???</para>
  <note>
    <title>??????????????????</title>
    <para>
      <application>Setup Agent</application> ?????????????????????????????????????????????????????????????????????????????????????????????</para>
  </note>
  <section id="sn-firstboot-licence">
    <title>????????????</title>
    <para>????????????????????? &FC; ????????????????????????&FC; ?????????????????????????????????????????????????????????????????? <indexterm><primary>OSI (Open Source Initiative)</primary></indexterm> Open Source Initiative (OSI) ???????????????????????? OSI ???????????????????????? <ulink url="http://www.opensource.org/">http://www.opensource.org/</ulink>???</para>
    <figure id="fig-fboot-licence">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-licence.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-licence.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????????????????? <guilabel>Yes, I agree to the License Agreement</guilabel>??????????????? <guilabel>Next</guilabel>???</para>
  </section>
  <section id="sn-firstboot-datetime">
    <title>???????????????</title>
    <para>?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <indexterm><primary>NTP (Network Time Protocol)</primary></indexterm><firstterm>NTP</firstterm> (??????????????????) ????????????????????????????????????NTP ???????????????????????????????????????????????????????????????????????????????????????????????????????????? NTP ?????????</para>
    <para>??????????????????????????????????????????????????????</para>
    <figure id="fig-fboot-time">
      <title>?????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-time.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-time.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????? <guilabel>Network Time Protocol</guilabel> ??????????????????????????? NTP ?????????</para>
    <tip>
      <title>????????????</title>
      <para>????????????????????????????????????????????????????????? <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guimenuitem>Date &amp; Time</guimenuitem></menuchoice>???</para>
    </tip>
    <para>????????????????????????????????????????????????????????? <guilabel>Enable Network Time Protocol</guilabel> ????????????????????????????????? <guilabel>Date and Time</guilabel> ?????????????????????????????????????????????</para>
    <figure id="fig-fboot-time-ntp">
      <title>?????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-time-ntp.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-time-ntp.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>??????????????????&FC; ??????????????????????????????????????????????????? <firstterm>pool</firstterm>???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <para>?????????????????????????????????????????? <guilabel>Server</guilabel> ????????????????????????????????????????????? DNS ????????????????????? <guilabel>Add</guilabel>???????????????????????????????????????????????????????????????????????????????????? <guilabel>Delete</guilabel>???????????????????????????????????????????????????????????? &RH; ????????????</para>
    <para>????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>Show advanced options</guilabel> ???????????? <guilabel>Use Local Time Source</guilabel> ????????????????????????????????????????????????NTP ????????????????????????????????????????????????</para>
    <para>?????????????????? <guilabel>Enable NTP Broadcast</guilabel> ???????????????&FC; ???????????????????????????????????????????????????</para>
  </section>
  <section id="sn-firstboot-display">
    <title>????????????</title>
    <para>
      <application>Setup Agent</application> ??????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>Resolution</guilabel> ???????????? <guilabel>Color Depth</guilabel> ?????????????????????</para>
    <figure id="fig-fboot-display">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-display.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-display.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>??????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>????????????????????????????????????????????? <guilabel>Configure</guilabel> ??????????????????????????????????????????????????????????????????????????????????????? <keycap>+</keycap> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>OK</guilabel>?????????????????????????????????????????????????????? <guilabel>Generic CRT Display</guilabel> ???????????? <guilabel>Generic LCD Display</guilabel> ????????????????????????????????????</para>
    <figure id="fig-fboot-display-monitor">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-display-monitor.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-display-monitor.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>???????????????????????????????????? <guilabel>Resolution</guilabel> ?????? <guilabel>Color Depth</guilabel>????????????????????????????????????????????????<application>Setup Agent</application> ???????????????????????????????????????????????????</para>
    <tip>
      <title>??????????????????</title>
      <para>??????????????????????????????????????????????????????????????????????????? <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guimenuitem>Display</guimenuitem></menuchoice>???</para>
    </tip>
  </section>
  <section id="sn-firstboot-systemuser">
    <title>????????????</title>
    <para>?????????????????????????????????????????????????????????????????????????????????????????????????????? &FC; ????????????????????? <systemitem class="username">root</systemitem> ?????????</para>
    <figure id="fig-fboot-user">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-user.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-user.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????????????????????????????????????????????????????????????????????????????? <guilabel>Confirm Password</guilabel> ????????????????????????????????????????????????????????????????????? <xref linkend="ch-rootpassword"/> ???????????????????????????????????????????????????</para>
    <tip>
      <title>???????????????????????????</title>
      <para>??????????????????????????????????????????????????????????????????????????????????????? <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guimenuitem>Users &amp; Groups</guimenuitem></menuchoice>???</para>
    </tip>
    <para>????????? &FC; ??????????????????????????????????????????????????????????????? <guibutton>Use Network Login...</guibutton>???</para>
    <para>?????????????????????????????????????????? <guibutton>Next</guibutton> ?????????</para>
  </section>
  <section id="sn-firstboot-soundcard">
    <title>??????</title>
    <para>
      <application>Setup Agent</application> ??????????????????????????????????????????</para>
    <figure id="fig-fboot-sound">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-sound.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-sound.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????? <guibutton>Play Test Sound</guibutton> ?????????????????????????????????????????????&FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <para>???????????????????????????????????????????????? &FC; ??????????????????????????????????????????????????????????????????????????????????????????</para>
    <tip>
      <title>????????????</title>
      <para>??????????????????????????????????????????&FC; ??????????????????????????????????????????????????????????????????????????????????????? <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guimenuitem>Soundcard Detection</guimenuitem></menuchoice>???</para>
    </tip>
  </section>
  <section id="sn-firstboot-additional-cds">
    <title>?????? CD</title>
    <para>???????????????????????????????????????????????????????????????????????????????????????????????????????????? &FC; ??????????????????????????????</para>
    <tip>
      <title>????????????</title>
      <para>????????? &FC; ???????????????????????????????????????????????? <application>Package Manager</application> ??????????????????????????????????????? <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guimenuitem>Add/Remove Applications</guimenuitem></menuchoice>???</para>
    </tip>
    <figure id="fig-fboot-cds">
      <title>?????? CD ??????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-cds.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-cds.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????? CD ?????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????? <guilabel>Next</guilabel> ??????????????????????????????</para>
    <figure id="fig-fboot-finish">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-finish.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fboot-finish.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????? <guilabel>Next</guilabel> ????????????????????????????????? &FC; ???????????????????????????</para>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-installingpackages-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-installing-packages">
  <title>???????????????</title>
  <para>&FC; ????????????????????????????????????????????????????????????????????? DVD ??????????????????????????????????????????????????? CD ????????????&FC; ???????????????????????????????????????????????????????????????????????? <guibutton>OK</guibutton> ??????????????????</para>
  <figure id="fig-installing-inprogress">
    <title>???????????????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/installing-inprogress.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/installing-inprogress.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>??????????????????????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>
  <para>???????????????????????? <guibutton>Reboot</guibutton> ?????????????????????&FC; ??????????????????????????????????????????</para>
</chapter>


--- NEW FILE fedora-install-guide-installtypes-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-installtypes">
  <title>????????????</title>
  <para>
    <indexterm>
      <primary>installation type</primary>
    </indexterm>
    <firstterm>installation type</firstterm> ?????????????????????????????????????????????????????????????????? &FED; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  <section id="ch-choosing-installtype">
    <title>????????????????????????</title>
    <figure id="fig-install-types">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/install-types.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/install-types.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <variablelist>
      <varlistentry>
        <term>
          <guilabel>????????????</guilabel>
        </term>
        <listitem>
          <para>???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>?????????</guilabel>
        </term>
        <listitem>
          <para>??????????????????????????? <guilabel>Personal Desktop</guilabel> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>?????????</guilabel>
        </term>
        <listitem>
          <para>??????????????????????????????????????????????????? Apache Web ??????????????? Samba ????????????????????????????????????????????????????????????????????????????????????</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>?????????</guilabel>
        </term>
        <listitem>
          <para>???????????????????????????????????????????????????????????????????????? <guilabel>Personal Desktop</guilabel> ?????????????????????????????????????????? <guilabel>Custom</guilabel> ???????????????????????????????????????????????????????????????????????????????????????</para>
        </listitem>
      </varlistentry>
    </variablelist>
    <para>????????????????????????????????? <guibutton>Next</guibutton> ?????????</para>
  </section>
  <section id="installtype-notes">
    <title>????????????</title>
    <para>?????? &FC; ???????????????????????????????????????????????????</para>
    <itemizedlist>
      <listitem>
        <para>?????? <indexterm><primary>SMTP (Simple Mail Transfer Protocol)</primary></indexterm><firstterm>SMTP</firstterm> (????????????????????????) ???????????????</para>
      </listitem>
      <listitem>
        <para>
          <indexterm>
            <primary>NFS (Network File System)</primary>
            <secondary>service installed</secondary>
          </indexterm> ??????????????????????????? NFS (??????????????????)</para>
      </listitem>
      <listitem>
        <para>
          <indexterm>
            <primary>CUPS (Common UNIX Printing System)</primary>
          </indexterm> ????????????????????? <firstterm>CUPS</firstterm> (?????? UNIX ????????????)</para>
      </listitem>
      <listitem>
        <para>
          <indexterm>
            <primary>SSH (Secure SHell)</primary>
          </indexterm> ????????????????????? <firstterm>SSH</firstterm> (?????? SHell)</para>
      </listitem>
    </itemizedlist>
    <para>?????? &FED; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FED; ??????????????????????????? NFS ???????????????????????? NFS <emphasis>??????</emphasis> ?????????????????????????????????????????????????????? &FED; ??????????????????????????????NFS ??????????????????SSH ????????????????????????</para>
    <tip>
      <title>????????????</title>
      <para>??????????????????????????????????????? <guilabel>Custom</guilabel> ?????????????????? <guilabel>Package Group Selection</guilabel> ????????????????????? <guilabel>Minimal</guilabel> ????????? <guilabel>Minimal</guilabel> ??????????????????????????????????????????????????????NFS ??? SSH ????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    </tip>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-intro-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><preface id="ch-intro">
  <title>??????</title>
  <!--  removed until we begin working on the FC5 version
  &DRAFTNOTICE;  -->
  <para>&FC; ?????????????????????????????????????????????????????????????????????????????????</para>
  <caution>
    <title>&FC; ????????????</title>
    <para>&FC; ???????????????????????????????????????????????????????????????&FC; ?????????????????????????????????????????????????????????</para>
  </caution>
  <para>????????????????????? &FC; ????????????????????????????????????????????????????????????????????????????????????????????? Linux ??????????????????????????????????????????????????????????????????????????????????????????&FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  <para>?????????????????????????????????????????????????????????</para>
  <section id="sn-background">
    <title>??????</title>
    <para>&FP; ?????????????????? &FC;????????? &FORMAL-RHI; ??? <indexterm><primary>free software</primary><see>FOSS</see></indexterm><indexterm><primary>open source</primary><see>FOSS</see></indexterm><indexterm><primary>FOSS (free and open source software)</primary></indexterm><firstterm>?????????????????????</firstterm> (FOSS) ????????????????????????&FP; ???????????? &FEX;??????????????????????????? &FC; ??????????????????????????????</para>
    <para>??????????????? &FP; ??????????????????????????? <ulink url="http://fedora.redhat.com/">&FP-URL;</ulink>????????? <ulink url="http://www.opensource.org/">http://www.opensource.org/</ulink> ??? <ulink url="http://www.gnu.org/philosophy/free-sw.html">http://www.gnu.org/philosophy/free-sw.html</ulink> ??????????????????????????????????????????????????????</para>
  </section>
  <section id="sn-before-begin">
    <title>????????????</title>
    <para>?????????????????? &FC;????????????????????????????????????????????? DVD ?????????????????????????????? <firstterm>architecture</firstterm> ????????????????????????????????????????????????&FC; ?????? <firstterm>i386</firstterm>, <firstterm>ppc</firstterm>, ??? <firstterm>x86_64</firstterm> ???????????????????????????????????????</para>
    <variablelist>
      <varlistentry>
        <term>i386</term>
        <listitem>
          <para>Intel x86-??????????????????????????? Pentium ??? Pentium-MMX, Pentium Pro, Pentium-II, Pentium-III, Celeron, Pentium 4, ??? Xeon; VIA C3/C3-m ?????? Eden/Eden-N; ?????? AMD Athlon, AthlonXP, Duron, AthlonMP, ??? Sempron</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>ppc</term>
        <listitem>
          <para>PowerPC ?????????????????? Apple Power Macintosh, G3, G4, and G5, ??? IBM pSeries ??????????????????</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>x86_64</term>
        <listitem>
          <para>64-bit AMD ?????????????????? Athlon64, Turion64, Opteron; ?????? Intel 64-bit ????????? EM64T</para>
        </listitem>
      </varlistentry>
    </variablelist>
    <para>?????????????????????????????????</para>
    <itemizedlist>
      <listitem>
        <para>?????????????????????????????????</para>
      </listitem>
      <listitem>
        <para>?????? &IG; ???????????????</para>
      </listitem>
    </itemizedlist>
    <para>???????????????????????????????????????????????? &FC; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <para>??????????????????????????????????????????????????? HTML ?????????????????????????????????????????? &IG; ???????????????????????? <ulink url="http://fedora.redhat.com/docs/">&FDPDOCS-URL;</ulink> ?????????</para>
    <section id="sn-installing-network-configurations">
      <title>??????</title>
      <para>??????????????????&FC; ?????????????????? <indexterm><primary>DHCP (Dynamic Host Configuration Protocol)</primary></indexterm><firstterm>DHCP</firstterm> (????????????????????????) ???????????????????????????????????????????????????????????? DHCP ????????????????????????????????????????????????DHCP ?????????????????????????????????????????????????????????????????????????????????????????????</para>
      <para>?????????????????????????????????????????????????????????????????????????????????????????? <xref linkend="sn-installing-networkinstallation"/> ??? <xref linkend="sn-installing-managed-network"/> ????????????????????????</para>
      <note>
        <title>Modem ??????</title>
        <para>&FC; ??????????????????????????????????????????????????????????????????????????? modem????????????????????????????????????????????????</para>
      </note>
    </section>
    <section id="sn-installing-asaserver">
      <title>??? &FC; ????????????????????????</title>
      <para>&FC; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>Server</guilabel> ????????????????????? <xref linkend="ch-installtypes"/> ????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    </section>
    <section id="sn-installing-networkinstallation">
      <title>??????????????????????????????</title>
      <para>????????????????????????????????? &FC;?????????????????????????????????</para>
      <itemizedlist>
        <listitem>
          <para>??????????????????</para>
        </listitem>
        <listitem>
          <para>??????????????????????????? (FTP, HTTP ?????? NFS)</para>
        </listitem>
        <listitem>
          <para>????????????????????????</para>
        </listitem>
      </itemizedlist>
      <para>???????????????????????????????????????????????????????????? <firstterm>PXE</firstterm> (Pre-boot eXecution Environment) ??????????????????????????? DVD ?????????????????????????????? CD????????????????????? USB ??????????????????????????????????????????</para>
      <para>PXE (???????????? <firstterm>netboot</firstterm> ????????????) ???????????????????????? PC ????????????????????????????????????????????????&FC; ??????????????????????????????????????????????????? PXE ????????????</para>
      <para>????????? <xref linkend="ch-beginninginstallation"/> ???????????????????????????</para>
    </section>
    <section id="sn-installing-managed-network">
      <title>????????????????????????????????? &FC;</title>
      <para>??????????????????????????? <firstterm>directory service</firstterm> ????????????????????????????????????????????????&FC; ?????????????????? Kerberos, NIS, Hesiod, ?????? <trademark class="registered">Microsoft</trademark><trademark class="registered">Windows</trademark> ???????????????????????????????????????&FC; ??????????????? LDAP ?????????</para>
      <!--
	
	<para>
	  The process of configuring your &FC; system to use network
	  authentication services is explained in a separate tutorial.
	</para>

	[When this tutorial exists, remove these comments.]

	-->
      <caution>
        <title>?????????????????????</title>
        <para>???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
      </caution>
    </section>
  </section>
</preface>


--- NEW FILE fedora-install-guide-locale-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-installer-locale">
  <title>????????????????????????</title>
  <para>??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  <important>
    <para>???????????????????????? 128MB???HTTP ??? FTP ?????????????????????????????????????????????</para>
  </important>
  <section id="sn-installer-language">
    <title>????????????</title>
    <para>?????????????????? &FED; ????????????????????????</para>
    <figure id="fig-lang-selection">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/lang-selection.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/lang-selection.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>????????????????????????????????????????????? <guibutton>Next</guibutton>???</para>
    <note>
      <title>??????????????????????????????</title>
      <para>??????????????????????????????????????????????????????????????????????????????????????????????????????????????? <xref linkend="sn-lang-packages"/>???</para>
    </note>
  </section>
  <section id="sn-installer-keyboard">
    <title>????????????</title>
    <para>??????????????????????????? &FED; ????????????????????????</para>
    <figure id="fig-keyb-conf">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/keyb-conf.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/keyb-conf.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>??????????????????????????????????????????????????? <guibutton>Next</guibutton>???</para>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-networkconfig-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-networkconfig">
  <title>????????????</title>
  <para>??????????????????????????? &FED; ???????????????????????????</para>
  <para>?????????????????? &FED; ?????????????????????????????????????????????????????? <indexterm><primary>DHCP (Dynamic Host Configuration Protocol)</primary></indexterm><firstterm>DHCP</firstterm> (????????????????????????) ????????????????????????????????????????????????????????????????????????&FC; ????????????????????????????????????????????????????????? DHCP???</para>
  <para>?????? DHCP ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  <figure id="fig-net-config-dhcp">
    <title>??????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/net-config-dhcp.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/net-config-dhcp.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>?????????????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>
  <section id="sn-network-devices">
    <title>????????????</title>
    <para>&FED; ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <firstterm>IP address</firstterm><indexterm><primary>IP address</primary></indexterm> ?????????????????????????????? <indexterm><primary>DHCP (Dynamic Host Configuration Protocol)</primary></indexterm> DHCP ?????????????????????????????????</para>
    <para>??????????????? IP ??????????????? <guilabel>Network Device</guilabel> ????????????????????????????????? <guibutton>Edit</guibutton>???&FED; ???????????????????????????????????????<emphasis>??????</emphasis> <guilabel>Configure using DHCP</guilabel> ?????????????????????????????????????????? <guilabel>IP Address</guilabel> ???????????? <guilabel>Netmask</guilabel>??????????????? <guibutton>OK</guibutton>???</para>
    <para>????????????????????????????????????????????????????????? DHCP???????????????????????????????????????????????????????????? DHCP ?????????????????????????????????????????????????????????</para>
    <para>???????????????????????????????????????????????????????????? <guilabel>Active on Boot</guilabel> ?????????????????????????????????????????????????????????????????????????????????????????????</para>
    <note>
      <title>Modem ??????</title>
      <para>
        <guilabel>Network Configuration</guilabel> ?????????????????? <indexterm><primary>modem</primary></indexterm> modem ????????????????????????????????????????????????????????????????????? <application>Internet Configuration Wizard</application> ?????? <application>Network Configuration</application> ??????????????????????????????????????????????????? (ISP)???????????????????????????</para>
    </note>
  </section>
  <section id="sn-computer-hostname">
    <title>??????????????????</title>
    <para>?????????????????????DHCP ??????????????????????????????????????? <indexterm><primary>hostname</primary></indexterm><firstterm>hostname</firstterm> ??????????????????????????????????????? <guilabel>Manual</guilabel> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <replaceable>machine1.example.com</replaceable>????????????????????? (??? "?????????") ??? <replaceable>machine1</replaceable>?????? <indexterm><primary>domain name</primary></indexterm> ????????? <replaceable>example.com</replaceable>???</para>
    <tip>
      <title>??????????????????</title>
      <para>????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    </tip>
  </section>
  <section id="sn-network-misc-settings">
    <title>????????????</title>
    <para>????????????????????????????????????????????????????????????????????????????????????????????????????????? IP ?????????</para>
    <para>
      <firstterm>gateway</firstterm>
      <indexterm>
        <primary>gateway</primary>
      </indexterm> ??????????????????????????????????????????????????????????????? <indexterm><primary>router</primary><see>gateway</see></indexterm><firstterm>routers</firstterm> ??????????????????????????????????????????????????????????????????????????? <guilabel>Gateway</guilabel> ?????????????????????????????????</para>
    <para>????????????????????? <indexterm><primary>DNS (Domain Name Service)</primary></indexterm><firstterm>DNS</firstterm> (??????????????????) ???????????????????????????????????????????????????DNS ????????????????????? IP ?????????????????????????????????&FC; ?????????????????? DNS ????????????????????? DNS ????????????????????????????????????????????? DNS ???????????????????????????????????????????????? DNS ??????????????? <guilabel>Primary</guilabel>, <guilabel>Secondary</guilabel>, ??? <guilabel>Tertiary DNS Server</guilabel> ????????????????????????????????????</para>
    <para>??????????????????????????????????????????????????? <guibutton>Next</guibutton> ?????????</para>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-nextsteps-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-next-steps">
  <title>??????????????????</title>
  <para>&FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  <section id="sn-web-help">
    <title>Web ????????????</title>
    <para>&FC; ?????????????????? &FP; ??????????????????</para>
    <!-- institutional shyness of the word official, odd legal standing -->
    <para>
      <ulink url="http://fedora.redhat.com/docs/">http://fedora.redhat.com/docs/</ulink>
    </para>
    <para>Linux ???????????? (LDP) ???????????????????????????</para>
    <para>
      <ulink url="http://www.tldp.org/">http://www.tldp.org/</ulink>
    </para>
    <para>?????? &FC; ?????????????????????????????? &RHEL; ???????????????????????????</para>
    <para>
      <ulink url="http://www.redhat.com/docs/manuals/enterprise/">http://www.redhat.com/docs/manuals/enterprise/</ulink>
    </para>
    <para>?????????????????????????????????????????????????????? &FED; ?????????????????????????????????????????? Google ?????????????????????????????????</para>
    <para>
      <ulink url="http://www.google.com/linux/">http://www.google.com/linux/</ulink>
    </para>
  </section>
  <section id="sn-community-help">
    <title>????????????</title>
    <para>&FED; ???????????????????????????????????????????????????????????????????????? Linux ????????? (LUG) ??????????????????</para>
    <para>???????????????????????????</para>
    <para>
      <ulink url="http://forums.fedoraforum.org/">http://forums.fedoraforum.org/</ulink>
    </para>
  </section>
  <section id="sn-community">
    <title>?????? &FED; ??????</title>
    <para>&FP; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FC; ?????????????????? &RH; ????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <para>????????????????????????????????????</para>
    <para>
      <ulink url="http://fedora.redhat.com/participate/">http://fedora.redhat.com/participate/</ulink>
    </para>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-other-instmethods-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-other-install-methods">
  <title>??????????????????</title>
  <para>????????????????????????????????????????????????????????????????????????</para>
  <orderedlist>
    <listitem>
      <para>???????????? PXE ??? USB ??????????????????????????????</para>
    </listitem>
    <listitem>
      <para>?????? <prompt>boot:</prompt> ???????????????????????? <option>askmethod</option> ?????????</para>
    </listitem>
  </orderedlist>
  <figure id="fig-install-method">
    <title>????????????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/install-method.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/install-method.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>???????????????????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>
  <para>????????????????????????????????????????????????????????? <guibutton>OK</guibutton>???</para>
  <note>
    <title>CD/DVD ??????</title>
    <para>???????????????????????????????????? &FED; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  </note>
  <section id="sn-install-method-server">
    <title>????????????????????????</title>
    <para>????????????????????? FTP, HTTP, ??? <indexterm><primary>NFS (Network File System)</primary><secondary>install from</secondary></indexterm> NFS ??????????????? &FC;???</para>
    <section id="sn-installer-tcpip">
      <title>TCP/IP ??????</title>
      <para>???????????????????????????????????? DHCP ??????????????????????????????????????????????????? DHCP ????????????????????? <guibutton>Use dynamic IP configuration</guibutton> ?????????????????????????????????????????? <guibutton>OK</guibutton> ?????????</para>
      <figure id="fig-inst-ipsetup">
        <title>TCP/IP ???????????????</title>
        <mediaobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/inst-ipsetup.eps" format="EPS"/>
          </imageobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/inst-ipsetup.png" format="PNG"/>
          </imageobject>
          <textobject>
            <phrase>TCP/IP ??????????????????</phrase>
          </textobject>
        </mediaobject>
      </figure>
      <para>??????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    </section>
    <section id="sn-installer-service-settings">
      <title>??????????????????</title>
      <para>FTP, HTTP ??? NFS ??????????????????????????????????????????????????????????????????????????? IP ??????????????????????????????????????????</para>
      <figure id="fig-ftp-setup">
        <title>FTP ???????????????</title>
        <mediaobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/ftp-setup.eps" format="EPS"/>
          </imageobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/ftp-setup.png" format="PNG"/>
          </imageobject>
          <textobject>
            <phrase>FTP ??????????????????</phrase>
          </textobject>
        </mediaobject>
      </figure>
      <para>FTP ??????????????????????????????????????? <guilabel>non-anonymous FTP</guilabel>??????????????? FTP ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guibutton>OK</guibutton> ?????????</para>
      <figure id="fig-ftp-setup-further">
        <title>????????? FTP ???????????????</title>
        <mediaobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/ftp-setup-further.eps" format="EPS"/>
          </imageobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/ftp-setup-further.png" format="PNG"/>
          </imageobject>
          <textobject>
            <phrase>????????? FTP ??????????????????</phrase>
          </textobject>
        </mediaobject>
      </figure>
    </section>
  </section>
  <section id="sn-installing-from-harddrive">
    <title>???????????????</title>
    <para>????????????????????? &FED; ???????????????????????????????????????????????????????????????????????? USB ?????????????????????????????? ISO ???????????????????????? <indexterm><primary>ext2</primary><see>file systems</see></indexterm><indexterm><primary>file systems</primary><secondary>ext2</secondary></indexterm><firstterm>ext2</firstterm>, <indexterm><primary>ext3</primary><see>file systems</see></indexterm><indexterm><primary>file systems</primary><secondary>ext3</secondary></indexterm><firstterm>ext3</firstterm> ?????? <indexterm><primary>vfat</primary><see>file systems</see></indexterm><indexterm><primary>file systems</primary><secondary>vfat</secondary></indexterm><firstterm>vfat</firstterm> ?????????????????????????????? &FED; ??????<systemitem class="filesystem">vfat</systemitem> ?????????????????????????????????????????? FAT-16 ??? FAT-32??????????????????????????????????????????????????????????????????????????? <systemitem class="filesystem">vfat</systemi!
 tem> (FAT-32) ????????????????????? Microsoft Windows ?????????????????????????????????????????? <systemitem class="filesystem">vfat</systemitem> ???????????????</para>
    <note>
      <title>FAT-16, FAT-32, ??? <systemitem class="filesystem">vfat</systemitem></title>
      <para>?????????????????????????????????????????????????????????????????? &FED; ??????????????????????????? Windows ??????????????????????????????????????? <application>Disk Management</application> ??????????????? Linux ??????????????????????????????????????? <command>fdisk</command> ???????????????</para>
    </note>
    <para>???????????? ISO ??????????????? LVM (???????????????) ??????????????????????????? <xref linkend="sn-partitioning-general"/> ?????????????????????????????????????????????</para>
    <para>????????????????????????????????????????????????????????????</para>
    <figure id="fig-hdd-instmethod">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/hdd-instmethod.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/hdd-instmethod.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????????????????????????????????????????? ISO ??????????????????????????? IDE ????????????????????? <filename>/dev/hd</filename> ?????????SCSI ?????? USB ???????????????????????? <filename>/dev/sd</filename> ??????????????????????????????????????????????????????????????? <filename>/dev/hda</filename>????????????????????????????????????????????????????????? <filename>/dev/sda1</filename>???</para>
    <para>????????????????????? <guilabel>Directory holding images</guilabel> ?????????????????????????????????????????? ISO ????????????????????????????????????</para>
    <para>?????? <guibutton>OK</guibutton> ?????????</para>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-packageselection-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-packageselection">
  <title>???????????????</title>
  <para>&FED; ??????????????????????????????????????????????????? <xref linkend="ch-installtypes"/> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>Custom</guilabel> ???????????????&FED; ??????????????? <guilabel>Package Group Selection</guilabel>???</para>
  <tip>
    <title>????????????</title>
    <para>??????????????????????????????????????????????????????????????????????????????????????????????????? <application>Package Management</application> ?????????????????????????????????????????????????????????????????????????????? <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guimenuitem>Add/Remove Applications</guimenuitem></menuchoice>???</para>
  </tip>
  <section id="sn-defaultpackages">
    <title>?????????????????????</title>
    <para>?????????????????????????????????????????????</para>
    <figure id="fig-package-default">
      <title>???????????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/package-default.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/package-default.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>??????????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????????????????????????????????????????? <guilabel>Install the default software packages</guilabel>????????? <guilabel>Next</guilabel> ????????????????????? <xref linkend="ch-abouttoinstall"/>???</para>
    <para>???????????????????????????????????? <guilabel>Customize software packages to be installed</guilabel>????????? <guilabel>Next</guilabel> ???????????????????????? <xref linkend="sn-packagegroups"/>???</para>
  </section>
  <section id="sn-packagegroups">
    <title>?????????????????????</title>
    <para>&FC; ????????????????????? <indexterm><primary>package groups</primary></indexterm><firstterm>package groups</firstterm>?????????????????????????????????</para>
    <figure id="fig-package-selection">
      <title>???????????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/package-selection.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/package-selection.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>??????????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<emphasis>?????????</emphasis> ?????????????????????????????????????????????????????????????????????????????????</para>
    <para>???????????????????????????????????????????????????????????????????????? <guilabel>Details</guilabel> ?????????&FC; ???????????????????????? <guilabel>Base Packages</guilabel> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>Optional Packages</guilabel> ?????????</para>
    <para>&FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <figure id="fig-package-selection-details">
      <title>??????????????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/package-selection-details.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/package-selection-details.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
  </section>
  <section id="sn-lang-packages">
    <title>??????????????????</title>
    <para>?????? &FC; ?????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>Language Support</guilabel> ????????????????????????????????????????????????????????????</para>
    <warning>
      <title>????????????</title>
      <para>?????? <emphasis>??????</emphasis> ??????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    </warning>
  </section>
  <section id="sn-extreme-packagegroups">
    <title>
      <guilabel>Everything</guilabel> ??????????????? <guilabel>Minimal</guilabel> ????????????</title>
    <para>
      <guilabel>Miscellaneous</guilabel> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <para>?????????????????? <guilabel>Everything</guilabel>???&FC; ?????? <emphasis>??????</emphasis> ?????????????????? &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <caution>
      <title>??????????????????</title>
      <para>
        <guilabel>Everything</guilabel> ??????????????????????????? 6.9GB ??????????????????????????????????????????????????????????????? 175MB ????????????????????????????????????????????????????????????????????????????????????</para>
    </caution>
    <para>
      <guilabel>Minimal</guilabel> ????????????????????????????????????????????????????????????????????????????????????????????????</para>
    <para>???????????????????????????????????????????????? <guilabel>Next</guilabel> ?????????&FC; ?????????????????????????????????????????????????????????????????????</para>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-rootpassword-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-rootpassword">
  <title>?????? root ?????????</title>
  <para>&FED; ???????????????????????????????????? <indexterm><primary>root account</primary></indexterm><firstterm><systemitem class="username">root</systemitem></firstterm> ?????????????????????????????? Linux ????????????<systemitem class="username">root</systemitem> ???????????? &SEL; ???????????????????????????????????????????????????????????????????????????/??????????????????????????????????????????????????????????????????????????????????????????????????? <systemitem class="username">root</systemitem> ?????????</para>
  <important>
    <title>?????? <systemitem class="username">root</systemitem> ??????</title>
    <para>????????????????????? <systemitem class="username">root</systemitem> ?????????????????? &FC; ??????????????????????????????????????? <systemitem class="username">root</systemitem> ????????????????????????????????????</para>
  </important>
  <para>&FED; ?????????????????? <systemitem class="username">root</systemitem> ??????????????? 6 ?????????????????? <systemitem class="username">root</systemitem> ????????????????????????????????????????????????????????????????????????????????????</para>
  <itemizedlist>
    <listitem>
      <para>??????????????????????????????????????????????????????????????????????????????</para>
    </listitem>
    <listitem>
      <para>??????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    </listitem>
    <listitem>
      <para>??????????????????????????????????????????????????????</para>
    </listitem>
  </itemizedlist>
  <para>??????????????????????????????</para>
  <itemizedlist>
    <listitem>
      <para>
        <systemitem>f9*@1Ls99A</systemitem>
      </para>
    </listitem>
    <listitem>
      <para>
        <systemitem>HL8$391%%rb</systemitem>
      </para>
    </listitem>
    <listitem>
      <para>
        <systemitem>Iwtb,10^th</systemitem>
      </para>
    </listitem>
  </itemizedlist>
  <para>??? <guilabel>Root Password</guilabel> ?????????????????? <systemitem class="username">root</systemitem> ??????????????????????????????&FED; ?????????????????????????????? <guilabel>Confirm</guilabel> ????????????????????????????????????????????????</para>
  <figure id="fig-set-rootpw">
    <title>?????? root ????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/root-passwd.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/root-passwd.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>?????? root ???????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>
  <para>??????????????? root ????????????????????? <guibutton>Next</guibutton> ?????????</para>
</chapter>


--- NEW FILE fedora-install-guide-timezone-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-timezone">
  <title>????????????</title>
  <para>?????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <indexterm><primary>NTP (Network Time Protocol)</primary></indexterm> NTP (??????????????????) ?????????????????????????????????</para>
  <section id="sn-selecting-timezone">
    <title>??????????????????</title>
    <para>&FED; ????????????????????????????????????????????????</para>
    <figure id="fig-timezone">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/timezone.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/timezone.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FED; ??????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>X</guilabel> ????????????????????????</para>
    <para>??????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  </section>
  <section id="sn-utc">
    <title>Universal Co-ordinated Time (UTC)</title>
    <para>
      <indexterm>
        <primary>UTC (Universal Co-ordinated time)</primary>
      </indexterm> Universal Co-ordinated Time ???????????? <indexterm><primary>GMT (Greenwich Mean Time)</primary><see>UTC</see></indexterm> ????????????????????? (GMT)???</para>
    <para>?????? &FC; ????????????????????????????????????????????? <guilabel>System clock uses UTC</guilabel>????????????????????????????????????????????????????????????&FC; ???????????????????????????????????????????????? UTC ?????????????????????????????? UNIX ??????????????????????????????????????????</para>
    <caution>
      <title>Windows ???????????????</title>
      <para>????????????????????????????????? Microsoft Windows??????????????? <guilabel>System clock uses UTC</guilabel> ?????????Microsoft ????????????????????? BIOS ????????????????????????????????? UTC????????? &FC; ??????????????????????????????????????????</para>
    </caution>
    <para>?????? <guibutton>Next</guibutton> ??????????????????</para>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-upgrading-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: --><chapter id="ch-upgrading-system">
  <title>?????????????????????</title>
  <para>?????????????????????????????? &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
  <section id="sn-upgrade-examine">
    <title>????????????</title>
    <para>???????????????????????????????????? &FC; ?????? &RHL; ????????????????????????????????????</para>
    <figure id="fig-upgrade-examine">
      <title>??????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/upgrade-examine.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/upgrade-examine.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>?????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????????????????????????????????????????????????????????????????????????????????????????? <guibutton>Next</guibutton>???</para>
    <note>
      <title>?????????????????????</title>
      <para>??????????????????????????????????????? &FC; ??? &RHL; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    </note>
  </section>
  <section id="sn-upgrading-bootloader">
    <title>???????????????????????????</title>
    <para>
      <indexterm>
        <primary>boot loader</primary>
        <secondary>upgrading</secondary>
      </indexterm> ?????? &FC; ??????????????????????????????????????? <indexterm><primary>boot loader</primary><seealso>GRUB</seealso></indexterm><firstterm>boot loader</firstterm> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????  <xref linkend="ch-bootloader"/> ????????????????????????</para>
    <figure id="fig-upgrade-bootloader">
      <title>???????????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/upgrade-bootloader.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/upgrade-bootloader.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>??????????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>?????????????????????????????????????????? Linux ??????????????????????????????????????????????????????????????? &FC; ??????????????????????????? Linux ???????????????????????? <guilabel>Update boot loader configuration</guilabel>???????????????????????? &FC; ??? &RHL; ??????????????????????????????????????????</para>
    <para>
      <firstterm>GRUB</firstterm> ??? &FED; ??????????????????????????????????????????????????????????????????????????????????????? <trademark>BootMagic</trademark>???<trademark>System Commander</trademark> ?????? Microsoft Windows ?????????????????????????????? &FED; ????????????????????????????????????????????? <guilabel>Skip boot loader updating</guilabel>?????????????????????????????????????????????????????????????????????????????????</para>
    <para>????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>Create new boot loader configuration</guilabel> ?????????????????????????????????????????? GRUB???</para>
    <para>??????????????????????????? <guibutton>Next</guibutton> ????????????</para>
  </section>
</chapter>


--- NEW FILE fedora-install-guide-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;

<!ENTITY VERSION "1.0">
<!ENTITY BOOKID "fedora-install-guide-en-&VERSION; (2005-06-10-T16:20-0700)">
<!ENTITY BUG-NUM "129911">
<!ENTITY FCLOCALVER "4">
<!ENTITY DOCLOCALVER "1.0">
<!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-zh_CN.xml" >
<!ENTITY BEGINNINGINSTALLATION SYSTEM "fedora-install-guide-beginninginstallation-zh_CN.xml" >
<!ENTITY OTHERINSTALLMETHODS SYSTEM "fedora-install-guide-other-instmethods-zh_CN.xml" >
<!ENTITY LOCALE SYSTEM "fedora-install-guide-locale-zh_CN.xml" >
<!ENTITY UPGRADING SYSTEM "fedora-install-guide-upgrading-zh_CN.xml" >
<!ENTITY INSTALLTYPES SYSTEM "fedora-install-guide-installtypes-zh_CN.xml" >
<!ENTITY DISKPARTITIONING SYSTEM "fedora-install-guide-diskpartitioning-zh_CN.xml" >
<!ENTITY BOOTLOADER SYSTEM "fedora-install-guide-bootloader-zh_CN.xml" >
<!ENTITY NETWORKCONFIG SYSTEM "fedora-install-guide-networkconfig-zh_CN.xml" >
<!ENTITY FIREWALLCONFIG SYSTEM "fedora-install-guide-firewallconfig-zh_CN.xml" >
<!ENTITY TIMEZONE SYSTEM "fedora-install-guide-timezone-zh_CN.xml" >
<!ENTITY ROOTPASSWORD SYSTEM "fedora-install-guide-rootpassword-zh_CN.xml" >
<!ENTITY PACKAGESELECTION SYSTEM "fedora-install-guide-packageselection-zh_CN.xml" >
<!ENTITY ABOUTTOINSTALL SYSTEM "fedora-install-guide-abouttoinstall-zh_CN.xml" >
<!ENTITY INSTALLINGPACKAGES SYSTEM "fedora-install-guide-installingpackages-zh_CN.xml" >
<!ENTITY FIRSTBOOT SYSTEM "fedora-install-guide-firstboot-zh_CN.xml" >
<!ENTITY NEXTSTEPS SYSTEM "fedora-install-guide-nextsteps-zh_CN.xml" >
<!ENTITY ACKNOWLEDGEMENTS SYSTEM "fedora-install-guide-acknowledgements-zh_CN.xml" >
]>
<book id="book" lang="zh_CN">
  <bookinfo>
    <title>&FC; &FCLOCALVER; &IG;</title>
    <copyright>
      <year>2005</year>
      <holder>&FORMAL-RHI;</holder>
      <holder>Stuart Ellis</holder>
      <holder>Paul W. Frields</holder>
    </copyright>
    <authorgroup>
      <author>
        <surname>Ellis</surname>
        <firstname>Stuart</firstname>
      </author>
      <author>
        <surname>Frields</surname>
        <firstname>Paul</firstname>
        <othername role="mi">W.</othername>
      </author>
    </authorgroup> &LEGALNOTICE; <revhistory><revision><revnumber>0.6.2</revnumber><date>2005-04-30</date><authorinitials>StuartEllis</authorinitials><authorinitials>PaulWFrields</authorinitials><revdescription><para>?????? CVS???????????????</para></revdescription></revision><revision><revnumber>0.6.3</revnumber><date>2005-05-10</date><authorinitials>PaulWFrields</authorinitials><authorinitials>StuartEllis</authorinitials><revdescription><para>????????????????????????????????? "nextsteps"</para></revdescription></revision><revision><revnumber>0.7</revnumber><date>2005-05-15</date><authorinitials>StuartEllis</authorinitials><authorinitials>PaulWFrields</authorinitials><revdescription><para>???????????????????????????</para></revdescription></revision><revision><revnumber>1.0rc1</revnumber><date>2005-06-08</date><authorinitials>KarstenWade</authorinitials><revdescription><para>?????????????????????????????????</para></revdescription></revision><revision><revnumber>1.0</revnum!
 ber><date>2005-06-10</date><authorinitials>KarstenWade</authorinitials><revdescription><para>????????????</para></revdescription></revision></revhistory></bookinfo> &INTRODUCTION; &BEGINNINGINSTALLATION; &OTHERINSTALLMETHODS; &LOCALE; &UPGRADING; &INSTALLTYPES; &DISKPARTITIONING; &BOOTLOADER; &NETWORKCONFIG; &FIREWALLCONFIG; &TIMEZONE; &ROOTPASSWORD; &PACKAGESELECTION; &ABOUTTOINSTALL; &INSTALLINGPACKAGES; &FIRSTBOOT; &NEXTSTEPS; &ACKNOWLEDGEMENTS; <index id="generated-index"/></book>



From fedora-docs-commits at redhat.com  Fri Nov  4 19:54:15 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Fri,  4 Nov 2005 14:54:15 -0500
Subject: release-notes daemons-it.xml,NONE,1.1
Message-ID: <200511041954.jA4JsGYd008521@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8505

Added Files:
	daemons-it.xml 
Log Message:



--- NEW FILE daemons-it.xml ---
<section id="sn-daemons">
  <title>Servizi di sistema</title>
  <caution>
    <title>Informazioni antiquate</title>
    <para>
      Il contenuto in questa sezione ha necessit?? di essere aggiornato per &DISTRO;
      &DISTROVER;
    </para>
  </caution>
  <section id="sn-daemons-updatedb">
    <title><filename>cron</filename> e
      <filename>slocate</filename></title>
    <para>
      L'utilit?? <command>updatedb</command> non viene pi?? eseguita
      automaticamente da <command>cron</command> per creare ed aggiornare il datatbase
      dei files usati da <command>slocate</command>. Aggiornare questo
      database ?? un processo intensivo che gli utenti di workstations e
      laptops potrebbero trovare controproducente.
    </para>
    <para>
      Per abilitare gli aggiornamenti quotidiani del database <command>slocate</command>,
      editate il file <filename>/etc/updatedb.conf</filename> come segue:
    </para>
     
    <screen>
      DAILY_UPDATE=yes
    </screen>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->
    



From fedora-docs-commits at redhat.com  Fri Nov  4 19:54:34 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Fri,  4 Nov 2005 14:54:34 -0500
Subject: release-notes database-servers-it.xml,NONE,1.1
Message-ID: <200511041954.jA4JsYim008545@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8527

Added Files:
	database-servers-it.xml 
Log Message:



--- NEW FILE database-servers-it.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Fri Nov  4 19:54:53 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Fri,  4 Nov 2005 14:54:53 -0500
Subject: release-notes desktop-it.xml,NONE,1.1
Message-ID: <200511041954.jA4JsrpG008576@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8553

Added Files:
	desktop-it.xml 
Log Message:



--- NEW FILE desktop-it.xml ---
<section id="sn-desktop">
  <title>Desktop</title>
  <itemizedlist>
    <title>Note</title>
    <listitem>
      <para>GNOME 2.12 e KDE 3.4.2 Caratteristiche principali
      </para>
    </listitem>
    <listitem>
      <para>La test release attuale ha GNOME 2.12.1, insieme ad
	alcune anticipazioni di tecnologia del prossimo GNOME 2.14:
      </para>
      <itemizedlist>
        <listitem>
          <para>gnome-power-manager: porta l'Hardware Abstraction
	    Layer al mondo delle batterie dei laptop e delle unit?? UPS - queste
	    cose dovrebbero "semplicemente funzionare", con una semplice UI
	    (naturalmente, in una test release, potrebbero non farlo)
	  </para>
        </listitem>
        <listitem>
          <para>gnome-screensaver: da una fresca UI agli screensavers e
	    alla finestra di dialogo <guilabel>Lock Screen</guilabel>
	  </para>
        </listitem>
        <listitem>
          <para>Ottimizzazioni della memoria nei pacchetti fontconfig e
	    shared-mime-info (questi ora usano shared
	    memory-mapped caches per questi dati).  Entrambe queste caches
	    sono ancora qualcosa di sperimentale.
	  </para>
        </listitem>
      </itemizedlist>
    </listitem>
  <para>
    Sono apprezzati in modo speciale i feedback di test su questi pacchetti
    sperimentali.
  </para>
  <para>
    GNOME 2.12 ha rimosso l'opzione terminale dal menu di base del desktop.
    nautilus-open-terminal nel repositorio Fedora Extras ne fornisce un
    sostituto avanzato. E' anche gi?? menzionato nella release notes di 
    GNOME 2.12 ma abbiamo voluto evidenziarlo poich?? il pacchetto ?? fornito
    con il repositorio extras.
  </para>
  <para>
    Screensavers per impostazione predefinita non sono pi?? installati. Spiegheremo perch??
    e forniremo i comandi per installarli.
  </para>
  <para>MCS SELinux ?? in rawhide. Caratteristiche principali
    (<emphasis>tentativo</emphasis> - non assicuriamo la qualificazione del
    cambiamento)
  </para>
  <caution>
    <title>OpenOffice ed upgrading dalle test releases</title>
    <para>
      Se hai scelto di andare contro le raccomandazioni di <emphasis
	role='strong'>non</emphasis> aggiornare da una test
      release precedente, potrai avere un problema con <ulink
	url='/OpenOffice'>OpenOffice</ulink> eseguendo l'upgrade.
    </para>
    <para>
      Per risolverla, dovrai dare il seguente comando <emphasis
	role='strong'>prima</emphasis> di fare l'upgrade:
    </para>
<screen>
<command>rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
</screen>
  </caution>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Fri Nov  4 19:55:22 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Fri,  4 Nov 2005 14:55:22 -0500
Subject: release-notes development-tools-it.xml, NONE,
	1.1 entertainment-it.xml, NONE, 1.1 feedback-it.xml, NONE,
	1.1 file-servers-it.xml, NONE, 1.1
Message-ID: <200511041955.jA4JtM5o008601@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8582

Added Files:
	development-tools-it.xml entertainment-it.xml feedback-it.xml 
	file-servers-it.xml 
Log Message:



--- NEW FILE development-tools-it.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//IT"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "This header makes editing XML easier" >
 <!ENTITY DISTRO      "DISTRO" >
 <!ENTITY DISTROVER   "DISTROVER" >

]>
-->
<!-- Content commented out, no update performed by beat writer yet.
<section id="sn-devel">
  <title>
    Strumenti di sviluppo
  </title>
  <section id="sn-devel-gcc">
    <title>Collezione di compilatori GCC</title>
    <para>
      &DISTRO; &DISTROVER; ?? stato compilato usando <abbrev>GCC</abbrev>
      4.0, che ?? incluso nella distribuzione.
    </para>
    <itemizedlist>
      <title>Avvertimenti</title>
      <listitem>
        <para>
          <abbrev>GDB</abbrev> 6.1 o superiore ?? necessario per eseguire il debug di binari
	  a meno di compilare usando l'opzione di compilazione 
	  <parameter class="option">-fno-var-tracking</parameter>.
        </para>
      </listitem>
      <listitem>
        <para>
          L'opzione <parameter class="option">-fwritable-strings</parameter>
	  non ?? pi?? accettata.
        </para>
      </listitem>
      <listitem>
        <para>
          I messaggi diagnostici in lingua inglese adesso usano apici Unicode;
	  se non puoi leggerli, imposta la tua variabile ambiente <envar>LC_CTYPE</envar>
	  su &quot;<filename>C</filename>&quot; o
	  cambia l'emulatore terminale.
        </para>
      </listitem>
      <listitem>
        <para>
          Il file <filename>specs</filename> non ?? pi?? installato su
	  molti systems. Gli utenti comunit non lo noteranno, ma gli sviluppatori
	  che debbono alterare il file possono usare l'opzione <parameter
	    class="option">-dumpspecs</parameter> per generare il file
	  per l'editing.
        </para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title>Generazione di codice</title>
      <listitem>
        <para>
          L'ottimizzatore di codice <abbrev>SSA</abbrev> ?? ora incluso e
	  porta con se una migliore costante propagazione, parziale eliminazione
	  della ridondanza, load e store code motion, riduzione della forza,
	  eliminazione del dead storage, miglior individuazione del codice
	  irraggiungibile, e ricorsivit?? delle code per accumulazione.
        </para>
      </listitem>
      <listitem>
        <para>
          L'autovettorizazione ?? supportata. Questa tecnica ottiene pi?? alte prestazioni
	  per cicli repetitivi di codice, in alcune circostanze.
        </para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title>Estensione delle lingue</title>
      <listitem>
        <para>
          Un attributo <computeroutput>sentinel</computeroutput> ?? stato aggiunto
	  affinch?? il compilatore possa inviare un messaggio di avvertimento se una
	  funczione tipo <function>execl(char *path, const char *arg,
	    ...)</function>, che richiede un terminatore di lista <literal>NULL</literal>
	  manchi il <literal>NULL</literal>.
        </para>
      </listitem>
      <listitem>
        <para>
          Le estensioni <wordasword>cast-as-lvalue</wordasword>,
	  <wordasword>conditional-expression-as-lvalue</wordasword>, e
	  <wordasword>compund-expression-as-lvalue</wordasword>
	  sono state rimosse.
        </para>
      </listitem>
      <listitem>
        <para>
          La semantica <computeroutput>#pragma pack()</computeroutput>
	  ?? stata portata pi?? vicina a quelle usate dagli altri compilatori.
        </para>
      </listitem>
      <listitem>
        <para>
          Ricavare l'indirizzo di una variabile dichiarata con il
	  modificatore <computeroutput>register</computeroutput> ora
	  genera un errore invece di un avvertimento.
        </para>
      </listitem>
      <listitem>
        <para>
          Arrays di tipi di elementi incompleti ora generano un errore. Ci??
	  implica nessun trasferimento di referenza alle definizioni di struttura.
        </para>
      </listitem>
      <listitem>
        <para>
          Il compilatore base, senza nessuna ottimizzazione (<parameter
	    class="option">-O0</parameter>), ?? stato misurato come pi??
	  veloce del 25% su codice reale.
        </para>
      </listitem>
      <listitem>
        <para>
          Le librerie possono ora contenere a scopo funzionale variabili statiche
	  nei programmi multi-threaded. Il <parameter
	    class="option">-fno-threadsafe-statics</parameter> pu?? essere usato
	  dagli sviluppatori interni per disattivare questa caratteristica, ma
	  gli utenti ordinari non dovranno mai farlo.
        </para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title>Java</title>
      <listitem>
	<para>
          Per evitare conflitti sui nomi: <filename>rmic</filename> ?? ora
	  <filename>grmic</filename>; <filename>rmiregistry</filename>
	  ?? ora <filename>grmiregistry</filename>; e
	  <filename>jar</filename> ?? ora <filename>fastjar</filename>.
        </para>
      </listitem>
      <listitem>
	<para>
	  Il compilatore <application>GCJ</application> pu?? adesso essere utilizzato come
	  uno strumento just-in-time (<abbrev>JIT</abbrev>) usando le facilities
	  <filename>gnu.jit</filename>.
	</para>
      </listitem>
      <listitem>
	<para>
	  E' stato aggiunto un maggior supporto dei pacchetti <abbrev>AWT</abbrev>
	  e <abbrev>SWING</abbrev>.
	</para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title>FORTRAN</title>
      <listitem>
	<para>
	  Il front end <abbrev>GNU</abbrev> <application>FORTRAN 77</application>
	  ?? stato sostituito da un nuovo ricognitore <application>FORTRAN
	    90/95</application>.
	</para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title>Ambiente di Sviluppo Eclipse</title>
      <listitem>
	<para>
	  Eclipse 3.1M6 ?? stato compilato come un applicazione nativa.
	</para>
      </listitem>
      <listitem>
	<para>
	  Lo C Development Tool (<abbrev>CDT</abbrev>) ?? stato
	  incluso.
	</para>
      </listitem>
    </itemizedlist>
  </section>
</section>
-->

<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE entertainment-it.xml ---
<section id="sn-entertainment">
  <title>Giochi ed intrattenimento</title>
  <para>
    &FC; e &FEX; forniscono una selezione di giochi che coprono una variet?? di
    generi.  Per impostazione predefinita, &FC; include un piccolo pacchetto di giochi per GNOME
    (chiamato <filename>gnome-games</filename>).  Per una lista di altri
    giochi disponibili per l'installazione mediante
    <command>yum</command>, aprite un terminale ed inserite il seguente
    commando: 
  </para>
<screen>
<command>yum groupinfo "Games and Entertainment"</command>
</screen>
  <para>
    Per aiuto su come usare <command>yum</command> per installare pacchetti di giochi
    assortiti, fate riferimento alla guida disponibile su: </para>
    <para>
    <ulink
      url="http://fedora.redhat.com/docs/yum/">http://fedora.redhat.com/docs/yum/</ulink>
    </para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE feedback-it.xml ---
  <section id="sn-test" os="test">
	  <title>Procedura per i suggerimenti alle Release Notes</title>

    <para>(Questa sezione scomparir?? quando la release finale di &DISTRO; sar?? creata.)</para>

    <para>Se pensi che queste release notes possano essere migliorate in qualche modo,
      puoi inviare il tuo suggerimento diretamente all'autore.  Se vedi un URL nelle
      release notes che sia tipo:</para>

    <para>%%% https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=<replaceable>&lt;bug-number&gt;</replaceable> %%% </para>

    <para>Puoi cliccare sull'URL ed inviare il tuo suggerimento nella sezione inerente
      le release notes.  Il tuo suggerimento sar?? aggiunto come commento a
      un rapporto d'errore esistente.</para>

    <para>Se le sezioni delle release notes per cui hai suggerimenti
      non hanno uno di questi URLs (o stai inviando una richiesta per un contenuto completamente 
      nuovo), puoi cliccare sul seguente link (questo funziona solo per la versione
      HTML, naturalmente &mdash; l'URL ?? troppo lungo per essere incluso come
      testo):</para>

    <para><ulink
    url="https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Core&amp;op_sys=Linux&amp;version=devel&amp;component=fedora-release&amp;component_text=&amp;rep_platform=All&amp;priority=normal&amp;bug_severity=normal&amp;bug_status=NEW&amp;assigned_to=&amp;cc=&amp;estimated_time=0.0&amp;bug_file_loc=http%3A%2F%2F&amp;short_desc=FC3%20release%20notes%20--%20&amp;comment=Please%20add%20a%20descriptive%20phrase%20to%20the%20summary%2C%20and%20more%20in-depth%0D%0Adescription%20here%20%28be%20sure%20to%20note%20any%20arch-specific%20issues%29%3A%0D%0A%0D%0A&amp;keywords=&amp;dependson=&amp;blocked=114398&amp;maketemplate=Remember%20values%20as%20bookmarkable%20template&amp;form_name=enter_bug">Clicca
    qui per inviare un nuovo suggerimento per le release notes</ulink></para>

    <para>Se vuoi rivedere i cambiamenti che sono gi?? stati inviati
      per questo documento, usate il seguente link:</para>

    <para><ulink
    url="http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398">http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398</ulink></para>

    <para>Man mano che gli errori vengono spediti per le varie parti delle release notes,
      susseguentemente le versioni test di queste release notes conterranno links simili
      a quello descritto sopra.</para>

    <para>Grazie (in anticipo) per il tuo suggerimento!</para>

  </section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE file-servers-it.xml ---
<section id="sn-file-servers">
  <title>File Servers</title>
  <caution>
    <title>Informazioni antiquate</title>
    <para>
      Il contenuto in questa sezione ha necessit?? di essere aggiornato per &DISTRO;
      &DISTROVER;
    </para>
  </caution>
  <para>
    Questa sezione si riferisce ai servers di file e di condivisione.
    Siete pregati di fare riferimento alle sezioni &WEB-SERVERS; e &SAMBA; per
    informazioni sul trasferimento file HTTP (Web) e sulla condivisione file Samba (Windows).
  </para>
  <section id="sn-file-servers-netatalk-suite">
    <title>Netatalk (Compatibilit?? Macintosh)</title>
    <para>
      Questa sezione contiene informazioni relative a Netatalk, una suite
      di software che permette a Linux di interagire con i sistemi Macintosh
      usando i protocolli di rete AppleTalk.
    </para>
    <section id="sn-file-servers-netatalk-package">
      <title><filename>netatalk</filename></title>
      <para>
	&DISTRO; &DISTROVER; include la versione 2 di Netatalk.
	<emphasis>Aggiornare da Netatalk versione 1 a versione 2 pu??
	  causare la perdita di dati</emphasis>.    La versione 2 di Netatalk usa
	un differente metodo per registrare i file resource forks dalla
	precedente versione, e pu?? richiedere una differente codifica del nome del
	file.  Siete pregati di leggere la documentazione e pianificare la vostra migrazione
	prima di eseguire l'aggiornamento.
      </para>
      <para>
	Le informazioni sull'aggiornamento sono disponibili direttamente dal sito
	Netatalk:
      </para>
      <para>
	<ulink
	  url="http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html">http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html</ulink>
      </para>
      <para>
	Anche la documentazione ?? inclusa nel pacchetto
	<filename>netatalk</filename>.  Fate riferimento a
	<filename>/usr/share/doc/netatalk-<replaceable>version</replaceable>/doc/htmldocs/upgrade.html</filename>, 
	oppure
	<filename>/usr/share/doc/netatalk-<replaceable>version</replaceable>/doc/Netatalk-Manual.pdf</filename> 
	(pagina numerata 25, pagina del documento 33).
      </para>
    </section>
  </section>
</section>

<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Fri Nov  4 19:56:16 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Fri,  4 Nov 2005 14:56:16 -0500
Subject: release-notes file-systems-it.xml, NONE, 1.1 hardware-reqs-it.xml,
	NONE, 1.1 i18n-it.xml, NONE, 1.1 install-notes-it.xml, NONE,
	1.1 intro-it.xml, NONE, 1.1
Message-ID: <200511041956.jA4JuGLi008629@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8609

Added Files:
	file-systems-it.xml hardware-reqs-it.xml i18n-it.xml 
	install-notes-it.xml intro-it.xml 
Log Message:



--- NEW FILE file-systems-it.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE hardware-reqs-it.xml ---
<section id="sn-hardware-reqs">
  <title>Requisiti Hardware</title>
  <para>
    Le seguenti informazioni rappresentano il minimo requisito
    hardware necessario ad installare con successo &DISTRO; &DISTROVER;.
  </para>
  <note>
    <title>Nota</title>
    <para>
      Pu?? essere necessaria la compatibilit??/disponibilit?? di altri
      componenti hardware (tipo schede video e di network) per specifiche
      modalit?? di installazione e/o uso post-installazione.
    </para>
  </note>
<!-- Something like this needs to be said, but this really needs a -->
<!-- better treatment and probably a new section devoted to help resources.
  <para>
    Questa sezione non riguarda la compatibilit?? hardware.  Per sapere
    del funzionamento di uno specifico componente hardware con &FC; &LOCALVER; 
  </para>
-->
  <section>
    <title>Requisiti CPU</title>

    <para>Questa sezione elenca le specifiche di CPU richieste da &DISTRO;
      &DISTROVER;.</para>

    <note arch="x86">
      <title><!-- <remark os="test">(x86)</remark>--> Nota</title>

      <para><!-- <remark os="test">(x86)</remark> --> Le seguenti specifiche di CPU
	sono dichiarate in termini di processori Intel.  Altri
	processori (notoriamente, offerti da AMD, Cyrix, e VIA) che
	sono compatibili ed equivalenti ai seguenti processori Intel
	possono essere usati con &DISTRO;.</para>
    </note>

    <itemizedlist arch="x86">
      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> Minimo:
	  Pentium-class &mdash; &FC; &LOCALVER; ?? ottimizzata per CPUs Pentium4,
	  ma supporta anche CPUs precedenti (come il Pentium,
	  Pentium Pro, Pentium II, Pentium III, inclusi gli AMD e le varianti
	  VIA).  E' stato usato questo approccio poich??
	  le ottimizzazioni Pentium-class attualmente danno prestazioni ridotte
	  per processori di classe non-Pentium, e lo scheduling del Pentium4
	  ?? sufficientemente differente (rispetto alla massa dei processori
	  di oggi) per garantire questo cambio. <!-- <remark
	  os="test">%%% <ulink
	  url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254</ulink> 
	  %%%</remark> -->
	</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> Raccomandato per la
	  modalit?? testo: 200 MHz Pentium-class o superiore</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> Recomandato per la
	  modalit?? grafica: 400 MHz Pentium II o superiore</para>
      </listitem>
    </itemizedlist>

    <itemizedlist arch="x86_64">
      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> --> Processori
	  AMD64 (sia Athlon64 che Opteron)</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> --> Processori Intel
	  con <trademark
	    class="registered">Intel</trademark> Extended Memory 64
	  Technology (<trademark class="registered">Intel</trademark>
	  EM64T)</para>
      </listitem>
    </itemizedlist>
  </section>
  <section>
    <title>Requisiti di spazio su Hard Disk</title>

    <para>Questa sezione elenca lo spazio necessario all'installazione di &DISTRO;
      &DISTROVER;.</para>

    <note>
      <title>Nota</title>

      <para>I requisiti di spazio su disco elencati qui sotto rappresentano lo spazio su
	disco occupato da &DISTRO; &DISTROVER;
	<emphasis>dopo</emphasis> che l'installazione ?? stata completata.
	Comunque, dello spazio su disco aggiuntivo ?? richiesto durante
	l'installazione per supportare l'ambiente di'installazione.  Questo
	spazio aggiuntivo corrisponde alla dimensione dello
	<filename>/Fedora/base/stage2.img</filename> (sul CD-ROM 1) pi??
	la grandezza dei files in <filename>/var/lib/rpm</filename> sul sistema
	installato.</para>

        <!-- Update these figures every release -->
      <para>In termini pratici, vuol dire che un po pi?? di
	90MB possono essere necessari per una installazione minima,
	mentre pi?? di 175MB possono essere necessari per un installazione
	del tipo "Installa tutto".</para>

      <para>Inoltre, tenete in mente che dello spazio aggiuntivo pu?? essere necessario
	per ogni dato utente, e che almeno il 5% di spazio libero deve essere mantenuto
	per il funzionamento appropriato del sistema.</para>
    </note>

      <!-- Get actual numbers from installer, multiply by 1.1, and round -->
      <!-- up to the nearest 10MB or .1GB -->
    <para>
      This list is for 32-bit x86 systems:
    </para>
    <itemizedlist arch="x86">
      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> Installazione 
	  personalizzata (Minima): 620MB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> Server:
	  1.1GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> Desktop
	  personale: 2.3GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> Workstation:
	  3.0GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> Installazione 
	personalizzata (Installa tutto): 6.9GB</para>
      </listitem>
    </itemizedlist>
    <para>
      Questo elenco ?? per i sistemi a 64-bit x86_64:
    </para>
    <itemizedlist arch="x86_64">
      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> --> Installazione 
	personalizzata (Minimal): 900MB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> --> Server:
	  1.5GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> --> Desktop
	  personale: 2.7GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> --> Workstation:
	  3.4GB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> --> Installazione
	  personalizzata: (Installa tutto) 7.5GB</para>
      </listitem>
    </itemizedlist>
  </section>

  <section>
    <title>Requisiti di memoria</title>

    <para>Questa sezione elenca la memoria necessaria all'installazione di &DISTRO;
      &DISTROVER;.</para>
    <para>
      Questo elenco ?? per i sistemi a 32-bit x86:
    </para>
    <itemizedlist arch="x86">
      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> Minima per
	  la modalit?? testo: 64MB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> Minima per
	  la modalit?? grafica: 192MB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86)</remark> --> Recomandata per
	  la modalit?? grafica: 256MB</para>
      </listitem>
    </itemizedlist>
    <para>
      Questo elenco ?? per i sistemi a 64-bit x86_64:
    </para>
    <itemizedlist arch="x86_64">
      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> --> Minima per
	  la modalit?? testo: 128MB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> --> Minima per
	  la modalit?? grafica: 256MB</para>
      </listitem>

      <listitem>
	<para><!-- <remark os="test">(x86_64)</remark> --> Recomandata per
	  la modalit?? grafica: 512MB</para>
      </listitem>
    </itemizedlist>
  </section>
  <section id="sn-hardware-reqs-ppc">
    <title>Requisiti Hardware PPC</title>
    <para>
      Questa sezione elenca il minimo hardware per PowerPC (PPC) necessario
      all'installazione di &FC; &LOCALVER;.
    </para>
    <itemizedlist>
      <listitem>
	<para>
	  <!--<remark os="test">(ppc)</remark> --> Minimo: PowerPC G3 /
	  POWER4
	</para>
      </listitem>
      <listitem>
	<para>
	  <!--<remark os="test">(ppc)</remark> --> &FC; &LOCALVER;
	  supporta solo la generazione <quote>New World</quote> di Apple
	  Power Macintosh, venduta dal 1999 in avanti. Supporta anche
	  il processore 64-bit G5 ed i processori POWER negli IBM eServer
	  pSeries. Attualmente le macchine a 32-bit IBM RS/6000 non sono
	  supportate.
	</para>
      </listitem>
      <listitem>
	<para>
	  <!--<remark os="test">(x86)</remark> --> Recommandato per
	  la modalit?? testo: 233 MHz G3 o superiore
	</para>
      </listitem>
      <listitem>
	<para>
	  <!-- <remark os="test">(ppc)</remark> --> Recommendeto per
	  la modalit?? grafica: 400 MHz G3 o superiore
	</para>
      </listitem>
    </itemizedlist>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE i18n-it.xml ---
<section id="sn-i18n">
  <title>Internationalizazione (i18n)</title>
  <para>
    SCIM ha sostituito tutti gli altri metodi di input. Principali caratteristiche.
  </para>
  <section>
    <title>Supporto Linguaggi</title>
    <para>
      Questa sezione include le informazioni relative al supporto dei
      vari linguaggi in &DISTRO;.
    </para>
    <section>
      <title>Il sistema di input IIIMF</title>
      <para>
	IIIMF ?? l'Internet/Intranet Input Method Framework.  In &FC;
	&LOCALVER; il pacchetto <filename>iiimf</filename> ?? aggiornato alla
	versione 12.2.
      </para>
      <variablelist>
	<varlistentry>
	  <term>Cambiamenti di percorso dei file</term>
	  <listitem>
	    <para>
	      I nomi e le locazioni di alcuni files nel pacchetto
	      <filename>iiimf</filename> sono stati cambiati.
	    </para>
	    <para>
	      Il server IIIMF ?? stato rinominato da
	      <filename>/usr/sbin/htt</filename> a
	      <filename>/usr/bin/iiimd</filename>, e lo XIM bridge
	      client ?? stato rinominato da <filename>httx</filename> a
	      <filename>iiimx</filename>. Il nome dello script
	      <filename>init.d</filename> non ?? cambiato:
	      ?? ancora chiamato <filename>iiim</filename>. Tutti i
	      files di configurazione globali del sistema sono ora collocati sotto
	      <filename>/etc/iiim/</filename>.
	    </para>
	    <para>
	      Gli sviluppatori della Language Engine (LE) noteranno che i moduli LE
	      ed i loro dati adesso risiedono sotto
	      <filename>${libdir}/iiim/le/<filename>&lt;LE_NAME&gt;</filename>/</filename>, 
	      mentre i dati di runtime sono immagazzinati sotto
	      <filename>/var/lib/iiim/le/<replaceable>&lt;LE_NAME&gt;</replaceable>/</filename>.
	    </para>
	    <para>
	      Per ulteriori informazioni sull'esatto percorso e cambiamento della locazione
	      dei file, fate riferimento alle Fedora IIIMF FAQ:
	    </para>
	    <para>
	      <ulink
		url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>.
	    </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term>Hotkeys</term>
	  <listitem>
	    <para>
	      Le scorciatoie, come
	      <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo> 
	      usate per attivare Input Methods, sono ora configurabili con lo strumento a
	      linea di comando <command>iiimf-le-tools</command>.
	      Questa caratteristica ?? attualmente supportata solo dalle applicazioni
	      GTK2.  Per le altre applicazioni che usano XIM le chiavi
	      di scorciatoia possono essere cambiate usando una risorsa X.  Fate riferimento alle
	      IIIMF FAQ su <ulink
		url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink> 
	      per ulteriori dettagli su come cambiare le chiavi di scorciatoia.
	    </para>
	    <para>
	      Nota che il nome della chiave si riferisce al nome del simbolo della chiave X. Per
	      esempio, se vuoi attivare un
	      <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>, 
	      devi specificare '&lt;Control&gt;at' come nome della chiave e non
	      '&lt;Control&gt;@'.
	    </para>
	    <para>
	      La configurazione per-user delle scorciatoie attualmente non funziona
	      con &SEL; in modalit?? enforcing a causa di una mancanza della
	      &SEL; policy.  In questo caso, le scorciatoie possono essere cambiate
	      solo nella configurazione globale del sistema.
	    </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term>Supporto Qt</term>
	  <listitem>
	    <para>
	      Un immodule Qt per <filename>iiimf</filename> ?? ora
	      incluso.  Questo immodule funziona, ma manca di una finestra di status
	      ed ?? considerato sperimentale.  Perci??, le impostazioni predefinite
	      per le applicazioni Qt sono di continuare ad usare XIM per l'input IIMF.
	    </para>
	    <para>
	      Se vuoi provare l'immodule in un applicazione Qt, prima
	      installa il pacchetto <filename>iiimf-qt</filename>, avvia
	      l'applicazione, quindi clicca il bottone-3 del mouse in un area
	      di input e seleziona <guimenuitem>iiimqcf</guimenuitem> dal
	      submenu <guisubmenu>Select Input Method</guisubmenu>'.
	    </para>
	  </listitem>
	</varlistentry>
      </variablelist>
    </section>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE install-notes-it.xml ---
<section id="sn-anaconda">
  <title>Note Relative all'installazione</title>
  <para>
    Questa sezione descrive le problematiche relative ad Anaconda
    (il programma di installazione di &DISTRO;) ed all'installazione di &DISTRO;
    &DISTROVER; in generale.
  </para>
  <note>
    <title>Nota</title>
    <para>
      Se intendi scaricare l'immagine ISO DVD di &DISTRO; &DISTROVER;,
      tieni in mente che non tutti gli strumenti di download file possono
      scaricare files pi?? grandi di 2GB.  Per esempio,
      <command>wget</command> si chiuderebbe con un errore <computeroutput>File size
	limit exceeded</computeroutput>.
    </para>
    <para>
      Gli strumenti <command>curl</command> e <command>ncftpget</command>
      non hanno questa limitazione, e possono
      scaricare con successo files pi?? grandi di 2GB.
    </para>
    <para>
      Bittorrent ?? un altro metodo per scaricare grandi files.  Per
      informazioni su come ottenere ed usare il file torrent fate riferimento a
      questo sito web:
    </para>
    <para>
      <ulink
	url="http://torrent.fedoraproject.org/">http://torrent.fedoraproject.org/</ulink>
    </para>
  </note>
  <section id="sn-install-notes-ppc">
    <title>Note di installazione PPC</title>
    <section>
      <title>Requisiti hardware PPC</title>
      <para>
	Questa sezione elenca l'hardware minimo PowerPC (PPC) necessario
	all'installazione di &DISTRO; &DISTROVER;.
      </para>
      <itemizedlist>
	<listitem>
	  <para>Minimo: PowerPC G3 / POWER4 </para>
	</listitem>
	<listitem>
	  <para>&DISTRO; &DISTROVER; supporta solo la generazione ???New World???
	    degli Apple Power Macintosh, venduta all'incirca dal 1999 in avanti.
	  </para>
	</listitem>
	<listitem>
	  <para>&DISTRO; &DISTROVER; supporta anche gli IBM eServer pSeries, IBM
	    RS/6000, e le macchine Genesi Pegasos II.</para>
	</listitem>
	<listitem>
	  <para>Raccomandato per la modalit?? testo: 233 MHz G3 or better, 64MB
	    RAM.</para>
	</listitem>
	<listitem>
	  <para>Raccomandato per la modalit?? grafica: 400 MHz G3 or better, 128MB
	    RAM.</para>
	</listitem>
      </itemizedlist>
      <para>
	Il DVD o il primo CD del gruppo di dischi d'installazione di &FC; ?? impostato
	per essere avviabile sull'hardware supportato. In aggiunta, immagini avviabili di CD
	possono essere trovate nella directory <filename>images/</filename> del
	DVD o del primo CD. Queste si comporteranno differentemente a seconda
	dell'hardware:
      </para>
      <variablelist>
	<title>Comportamento delle immagini di boot per Hardware</title>
	<varlistentry>
	  <term>Apple Macintosh </term>
	  <listitem>
	    <para>The bootloader avvier?? automaticamente
	      l'appropriato installer a 32-bit o 64-bit.  Il supporto del power
	      management, incluso lo sleep e l'amministrazione della retroilluminazione,
	      ?? presente nel pacchetto <filename>apmud</filename>,
	      che ?? in &FEX;. &FEX; per &FC; ?? configurato per impostazione predefinita
	      per yum. Seguendo l'installazione,
	      <filename>apmud</filename> pu?? essere installato seguendo il
	      comando <command>yum install apmud</command> in un
	      terminale.
	    </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term>64-bit IBM eServer pSeries (POWER4/POWER5)</term>
	  <listitem>
	    <para>Dopo aver utilizzato OpenFirmware per avviare il CD, il
	      bootloader (<command>yaboot</command>) dovr??
	      automaticamente avviare l'installer a 64-bit.
	    </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term>32-bit CHRP (IBM RS/6000 ed altri)</term>
	  <listitem>
	    <para>Dopo aver utilizzato OpenFirmware per avviare il CD, selezionate la
	      boot image <filename>linux32</filename> al prompt di
	      <prompt>boot:</prompt> per avviare l'installer a 32-bit.
	      Altrimenti, sar?? avviato l'installer a 64-bit, che non
	      funzioner??.</para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term>Genesi Pegasos II</term>
	  <listitem>
	    <para>A cominciare da &DISTRO; &DISTROVER;, un firmware con pieno supporto
	      per i filesystems ISO9660 non ?? ancora stato rilasciato per
	      Pegasos.  Comunque, pu?? essere usata l'immagine di boot da network. Al
	      prompt di OpenFirmware, inserite il comando:
	    </para>
<screen>
<command>boot cd: /images/netboot/ppc32.img</command> 
</screen> 
	    <para>
	      Avrai anche bisogno di configurare manualmente OpenFirmware sul
	      Pegasos per rendere il sistema &FC; installato
	      avviabile. Per far questo, dovrai impostare le variabili ambiente
	      <envar>boot-device</envar> e <envar>boot-file</envar>
	      in modo appropriato.
	    </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term>Avvio via network</term>
	  <listitem>
	    <para>Ci sono immagini combinate contenenti il kernel d'installazione
	      ed il ramdisk nella directory images/netboot/ dell'albero
	      d'installazione. Queste sono intese per l'avvio da network con
	      TFTP, ma possono essere usate in molti modi.
	    </para>
	    <para>
	      Il comando <command>yaboot</command> supporta l'avvio tftp
	      per IBM eServer pSeries ed Apple Macintosh. &FED;
	      raccomanda di usare yaboot sulle immagini netboot.
	    </para>
	</listitem>
	</varlistentry>
      </variablelist>
    </section>
  </section>
  <section>
    <title>Note su anaconda</title>

    <itemizedlist>
      <listitem>
	<para>
	  Il programma d'installazione di &DISTRO; ha la capacit?? di testare
	  l'intyegrit?? dei media d'installazione. Funziona con i metodi di
	  installazione CD, DVD, hard drive ISO, e NFS ISO. &RH;
	  raccomanda che tu esegua il test di tutti i media prima di
	  cominciare il processo d'installazione, e prima di riportare qualsiasi
	  rapporto d'errore inerente l'installazione (molti degli errori riportati sono
	  attualmente causati da CDs masterizzati inappropriatamente). Per usare questo test, scrivete
	  <command>linux mediacheck</command> al prompt
	  <prompt>boot:</prompt>.
	</para>
	<para>
	  La funzione <command>mediacheck</command> ?? altamente
	  sensitiva, e pu?? restituire alcuni dischi utilizzabili come errati.
	  Questo risultato ?? spesso causato dal software di scrittura del disco che non
	  include il padding quando vengono creati dischi dai files ISO.  Per ottenere
	  i migliori risultati con <command>mediacheck</command>, eseguite il boot con
	  l'opzione:
	</para>
<screen>
linux ide=nodma
</screen>
	<para>
	  Usa l'utilit?? <command>sha1sum</command> per verificare i dischi
	  prima di portare a termine un installazione.  Questo test identifica
	  accuratamente dischi che non sono validi o identici ai files
	  immagine ISO.
	</para>
      </listitem>
      <listitem arch="x86">
<!--	<remark os="test">%%% <ulink
	    url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654</ulink> 
	  %%%</remark>
-->
	<para>
	  <!-- <remark os="test">(x86)</remark> --> Testing della memoria possono essere
	  effettuati prima di eseguire l'installazione di &DISTRO; immettendo
	  <command>memtest86</command> al prompt <prompt>boot:</prompt>.
	  Cio causa l'avvio standalone del software di testing della
	  memoria Memtest86. Il test di Memtest86 continua fino a che
	  il tasto <keycap>Esc</keycap> non viene premuto.
	</para>
	<para>
	  <!-- <remark os="test">(x86)</remark> --> NOTA: Devi eseguire il boot dal
	  CD-ROM 1 (o da un rescue CD-ROM) per poter usare questa
	  caratteristica.
	</para>
      </listitem>
      <listitem>
<!--	<remark os="test">%%% <ulink
	    url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627</ulink> 
	  %%%</remark>
-->
	<para>
	  &DISTRO; &DISTROVER; supporta installazioni grafiche FTP ed HTTP.
	  Comunque, a causa della necessit?? di contenere
	  l'immagine d'installazione in RAM, solo i sistemi con pi?? di 128MB
	  di RAM (o sistemi avviati dal CD-ROM 1, che contiene l'immagine
	  d'installazione) possono usare l'installer grafico.  I sistemi
	  con 128MB o meno potranno continuare ad usare l'installer testuale.
	</para>
      </listitem>
    </itemizedlist>
  </section>
  <section>
    <title>Problemi relativi all'intallazione</title>
    <itemizedlist>
      <listitem>
	<para>
	  Certe configurazioni hardware (in particolare quelle con
	  gli schermi LCD) potrebbero dare problemi durante l'avvio del
	  programma di'installazione di &DISTRO;.  In queste circostanze, ricominciate
	  l'installazione, ed aggiungete l'opzione "<command>nofb</command>" nella
	  linea di comando di boot.
	</para>

	<note>
	  <title>Nota</title>
	  <para>
	    Le installazioni grafiche Cinese, Giapponese e Koreana
	    avviate usando l'opzione "<command>nofb</command>"
	    cominceranno in Inglese, quindi cambieranno nel linguaggio
	    appropriato una volta che la fase grafica del processo di
	    installazione ha inizio.
	  </para>
	</note>   
      </listitem>
      <listitem arch="x86">
	<para>
<!--	  <remark os="test">(x86)</remark> --> Alcuni portatili Sony <trademark
	    class="registered">VAIO</trademark> potrebbero avere dei
	  problemi installando &DISTRO; da CD-ROM.  Se ci?? accade,
	  riavviate il processo d'installazione ed aggiungete la
	  seguente opzione nella linea di comando di boot:
	</para>
<screen>
<!-- <remark os="test">(x86)</remark> -->
<command>pci=off ide1=0x180,0x386</command>
</screen>
	<para>
	  <!-- <remark os="test">(x86)</remark> --> Questa opzione permette
	  all'installazione di procedere normalmente; qualsiasi periferica non riconosciuta
	  a causa dell'uso di questa opzione verr?? configurata la prima volta che
	  &DISTRO; ?? avviata.
	</para>
      </listitem>
      <listitem>
	<para>
	  E' risaputo che i mouse seriali sono non operativi durante
	  l'installazione. Comunque, ci sono indicazioni che mouse seriali
	  funzionano correttamente in X dopo che l'installazione ?? stata completata.
	  Fate riferimento al bug 119474 per maggiori informazioni:
	</para>
	<para>
	  <ulink
	    url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474</ulink>
	</para>
      </listitem>
      <listitem arch="x86">
	<para>
	  <!-- <remark os="test">(x86)</remark> --> Ci sono state
	  problematiche osservate durante l'aggiornamento di sistemi &RHL;
	  7.<replaceable>&lt;x&gt;</replaceable>, 8.0, 9, e &FC; 1, 2,
	  e 3 dove pacchetti di terze parti sono stati installati che
	  sono in conflitto con i pacchetti forniti da &FP;.  Un esempio ??
	  Ximian GNOME.
	</para>
	<para>
	  Le problematiche con Ximian GNOME sono causate dalla sovrapposizione di versioni
	  fra gli RPMs ufficiali di &RHL; (o quelli di &PROJ;)
	  e gli RPMs di Ximian.  Questa configurazione non ?? supportata. Hai
	  diverse scelte nel risolvere questo particolare problema:
	</para>
	<orderedlist numeration="loweralpha">
	  <listitem>
	    <para>
	      <!-- <remark os="test">(x86)</remark> -->Puoi rimuovere
	      Ximian GNOME dal tuo sistema prima di aggiornarti a
	      &DISTRO;.
	    </para>
	  </listitem>
	  <listitem>
	    <para>
	      <!-- <remark os="test">(x86)</remark> -->Puoi aggiornare
	      il tuo sistema, quindi reinstallare immediatamente Ximian GNOME.
	    </para>
	  </listitem>
	  <listitem>
	    <para>
	      <!-- <remark os="test">(x86)</remark> -->Puoi aggiornare
	      il tuo sistema, e quindi rimuovere tutti i rimanenti
	      RPMs di Ximian, sostituendoli con i corrispondenti RPMs
	      &DISTRO;.
	    </para>
	  </listitem>
	</orderedlist>	
	<para>
	  <!-- <remark os="test">(x86)</remark> -->
	  <emphasis>Devi</emphasis> risolvere la sovrapposizione di versione usando
	  uno delle scelte suindicate.  Un fallimento nella procedura porter?? ad una
	  configurazione di GNOME instabile.
	</para>
      </listitem>
    </itemizedlist>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE intro-it.xml ---
<section id="sn-intro">
  <title>Introduzione e Release Notes Tecniche</title>
  <para>
    Il &PROJ; ?? un progetto sviluppato apertamente disegnato da &RH;, aperto per
    una partecipazione generale, condotto in modo meritocratico, e che segue una serie di
    obbiettivi di progetto.  Il risultato di questo progetto include &DISTRO;,
    che ?? un completo, sistema operativo general-purpose compilato
    esclusivamente da software open source.
  </para>
  <note>
    <title>Nota</title>
    <para>
      &FC; ?? un progetto supportato dalla communit??.
    </para>
    <para>
      &FC; non ?? un prodotto supportato commercialmente da &FORMAL-RHI;.
    </para>
  </note>
  <para>
    Per maggiori informazioni, fate riferimento a <xref linkend="sn-overview"/>.
  </para>
  <para>
    Ulteriori importanti informazioni su questa release potrebbero essere rese
    disponibili su <ulink
      url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>. 
    Gli utenti sono avvisati di controllare questo url regolarmente per gli aggiornamenti.
  </para>
  <para>
    Per riportare errori o altre richieste su queste release notes,
    inviate un bug report usando questo <ulink url="&BUG-URL;">
      bugzilla template precompilato</ulink>.
  </para>
<!-- This is just to tweaky to HTML and will make people think it's b0rked
  <para>
    <ulink
    url="&BUG-URL;">&BUG-URL;</ulink>
  </para>
-->
  <para>
    Questo <ulink url="&TINY-BUG-URL;">&TINY-BUG-URL;</ulink> ti porter??
    al medesimo bugzilla template precompilato.
  </para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Fri Nov  4 19:57:04 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Fri,  4 Nov 2005 14:57:04 -0500
Subject: release-notes java-package-it.xml, NONE, 1.1 kernel-it.xml, NONE,
	1.1 legacy-it.xml, NONE, 1.1 misc-server-it.xml, NONE,
	1.1 multimedia-it.xml, NONE, 1.1
Message-ID: <200511041957.jA4Jv4aW008657@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8637

Added Files:
	java-package-it.xml kernel-it.xml legacy-it.xml 
	misc-server-it.xml multimedia-it.xml 
Log Message:



--- NEW FILE java-package-it.xml ---
<section id="sn-java-packages">
  <title>Raccomandazioni sul pacchetto Java</title>
  <caution>
    <title>Information Out-of-Date</title>
    <para>
      Il contenuto in questa sezione ha necessit?? di essere aggiornato per &DISTRO;
      &DISTROVER;
    </para>
  </caution>
  <para>
    Gli utenti di &FC; &LOCALVER; sono avvisati di non utilizzare i pacchetti RPM Java forniti
    da Sun.  Essi contengono <computeroutput>Forniscono</computeroutput> quel
    conflitto con i nomi usati nei pacchetti forniti come parte di &FC;
    &LOCALVER;.  Per questo motivo, Sun Java potrebbe scomparire da un
    sistema installato durante le operazioni di aggiornamento dei pacchetti.
  </para>
  <para>
    Gli utenti di &FC; &LOCALVER; potranno usare invece usare i pacchetti RPM di jpackage.org o
    installare manualmente il tarball Java di Sun in
    <filename>/opt</filename>.  <!-- Sun Java 1.5+ is recommended for
    stability purposes. -->
  </para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE kernel-it.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "These FAKE ENTITIES are just to make editing easier" >
 <!ENTITY FC            "FC"                                  >
 <!ENTITY LOCALVER      "LOCALVER"                            >
 <!ENTITY DISTRO        "DISTRO"                              >
 <!ENTITY DISTROVER     "DISTROVER"                           >

]>
-->
<section id="sn-kernel">
  <title>
    Linux Kernel
  </title>
  <section id="sn-kernel-lotsa">
    <title>Versione</title>
    <para>
      La distribuzione ?? basata sulla serie 2.6 del kernel di Linux. &FC; pu?? includere
      patches aggiuntive per miglioramenti, bug fixes, o caratteristiche
      aggiuntive. Per questa ragione, il kernel di &FC; potrebbe non essere
      linea-per-linea equivalente al kernel vanilla<firstterm></firstterm> proveniente dal sito web di
      <ulink
  url="http://www.kernel.org"><filename>kernel.org</filename></ulink>.
    </para>
    <para>
      Potrai ottenere una lista di ciascuna di queste patches usando il comando sul pacchetto di &FC;:
    </para>
<screen width="56">
<command>rpm <parameter class="option">-qpl</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
</screen>
  </section>
  <section id="sn-kernel-flavors">
    <title>Tipi di Kernel</title>
    <para>
      &FC; include i seguenti kernel builds:
    </para>
    <itemizedlist>
      <listitem>
        <para>Kernel nativo, nelle variet?? uniprocessore e
	  <abbrev>SMP</abbrev>. Sorgenti configurati sono
	  disponibili nel pacchetto
	  <filename>kernel-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>.
        </para>
      </listitem>
      <listitem>
        <para>
          Kernel virtuale per l'uso con il pacchetto emulatore <application>Xen</application>.
	  Sorgenti configurati sono disponibili nel pacchetto
	  <filename>kernel-xen0-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>.
        </para>
      </listitem>
    </itemizedlist>
    <para>
      I sorgenti per entrambe i tipi di kernel possono essere installati allo stesso momento.
      I files sono installati nell'albero
      <filename>/usr/src/kernels/<replaceable>version</replaceable>[-xen0]-<replaceable>arch</replaceable>/</filename>.
      Usa il comando:
    </para>
<screen width="56">
<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename></command>
</screen>
    <para>
      appropriatamente.
    </para>
    <tip>
      <title>Riguardo ai libri di testo generici sul Kernel di Linux</title>
      <para>
        Molti dei tutorial, esempi, e libri di testo sullo sviluppo del 
	kernel Linux assumono che i sorgenti del kernel siano installati sotto
	la directory <filename>/usr/src/linux</filename>. Se fai un link
	simbolico, come mostrato sotto, sarai in grado si usare quel
	materiale dapprendimento con i pacchetti di &FC;. Installa gli
	appropriati sorgenti del kernel, come mostrato sopra, e poi:
      </para>
<screen width="56">
<command>ln <parameter class="option">-s</parameter> <filename>/usr/src/kernels/kernel-<replaceable>all-the-rest</replaceable></filename> <filename>/usr/src/linux</filename></command>
</screen>
    </tip>
  </section>
  <!--
  <tip>
    <title>Usare <command>yum</command> per rimuovere i pacchetti del Kernel
    </title>
    <para>
      &FC; &LOCALVER; contiene il supporto per sistemi cluster che usano CMAN e GFS.
      Questi kernels richiedono assistenza da alcuni pacchetti in user-space.
      Questi pacchetti non sono rimossi quando usi <command>rpm
      -e</command> per rimuovere le vecchie versioni dei pacchetti del kernel.
    </para>
    <para>
      Quando usi <command>rpm -e kernel-<replaceable>version</replaceable> </command> per rimuovere il kernel, devi anche rimuovere i pacchetti di assistenza user-space.  Potresti considerare uno strumento di risoluzione delle dipendenze come <command>yum remove kernel-<replaceable>version</replaceable> </command>.
      Questo automaticamente rimuover?? qualsiasi pacchetto dipendente.
    </para>
  </tip>
  -->
  <section id="sn-kernel-exploding">
    <title>
      Preparazione allo sviluppo del Kernel
    </title>
    <para>
      &DISTRO; &DISTROVER; non include il pacchetto
      <filename>kernel-source</filename> fornito nelle vecchie
      versioni. Invece, sono disponibili sorgenti configurati come descritto
      in <xref
  linkend="sn-kernel-flavors"/>. Gli utenti che hanno bisogno dei sorgenti 
      originali del kernel di &FC; possono trovarli nel pacchetto
      <filename>kernel</filename> <filename>.src.rpm</filename>.
      Per creare un albero di sorgenti esploso da questo file, seguite i
      seguenti passi:
    </para>
    <important>
    <title>Queste istruzioni fanno riferimento al Kernel attuale!</title>
      <para>
	Per semplificare le seguenti direttive, assumiamo che tu voglia
	configurare i sorgenti del kernel che combaciano con la versione del kernel
	che hai in esecuzione. Nei prossimi passi, dovrai capire che
	la frase
	<replaceable>version</replaceable> si riferisce alla versione del kernel
	mostrata da questo comando:
      </para>
<screen width="56">
<command>uname <parameter class="option">-r</parameter></command>
</screen>
    </important>
    <procedure id="sn-kernel-exploding-steps">
      <step>
        <para>
          Puoi ottenere il file
	  <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename> 
	  da una delle seguenti risorse:
        </para>
        <itemizedlist>
          <listitem>
            <para>La directory <filename>SRPMS/</filename> sull'appropriato
	      <abbrev>CD</abbrev> immagine <filename>ISO</filename>
	      <wordasword>SRPMS</wordasword>.
              </para>
          </listitem>
          <listitem>
            <para>Il sito FTP da dove hai scaricato il pacchetto del kernel.
            </para>
          </listitem>
          <listitem>
            <para>Eseguendo il seguente comando:
            </para>
<!-- FIXME up2date is sorta deprecated for FC, how to do this with yum? -->
<screen width="56">
<command>up2date <parameter class="option">--get-source</parameter> <filename>kernel</filename></command>
</screen>
          </listitem>
        </itemizedlist>
      </step>
      <step>
        <para>
          Installa il pacchetto
	  <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename> 
	  usando il seguente comando:
        </para>
<screen width="56">
<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
</screen>
        <para>
          Questo scriver?? i contenuti dell'<abbrev>RPM</abbrev> in
	  <filename>/usr/src/redhat/SOURCES</filename> e
	  <filename>/usr/src/redhat/SPECS</filename>.
        </para>
      </step>
      <step>
        <para>
          Prepara i sorgenti del kernel usando i comandi:
        </para>
<screen width="56">
<command>cd <filename>/usr/src/redhat/SPECS</filename></command>
<command>rpmbuild <parameter class="option">-bp --target $(arch)</parameter> <filename>kernel-2.6.spec</filename></command>
</screen>
        <para>
          L'albero dei sorgenti del kernel ?? locato nella directory
	  <filename>/usr/src/redhat/BUILD/kernel-</filename><replaceable>version</replaceable>.
	  E' pratica comune muovere le risultanti directory
	  <filename>linux-<replaceable>version</replaceable></filename>
	  nell'albero <filename>/usr/src</filename>; anche se non ??
	  strettamente necessario, cos?? facendo lo farai coincidere con quanto riportato nella
	  documentazione generica.
        </para>
<screen width="56">
<command>cd <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
<command>mv <filename>linux-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
<command>cd <filename>/usr/src</filename></command>
<command>ln <parameter class="option">-s</parameter> <filename>./linux-<replaceable>version</replaceable></filename> <filename>linux</filename></command>
<command>cd <filename>/usr/src/linux</filename></command>
</screen>
      </step>
      <step>
        <para>
          Le configurazioni per i kernel specifici distribuiti con
	  &DISTRO; &DISTROVER; sono nella directory <filename>configs/</filename>.
	  Per esempio, il file di configurazione i686 SMP
	  ?? nominato
	  <filename>configs/kernel-<replaceable>version</replaceable>-i686-smp.config</filename>. 
	  Lancia il seguente comando per porre il file di configurazione deiderato
	  nel posto giusto per la compilazione:
        </para>
<screen width="56">
<command>cp <filename>configs/<replaceable>desired-config-file</replaceable></filename> <filename>.config</filename></command>
</screen>
        <para>
          Puoi trovare inoltre il file <filename>.config</filename> che combacia
	  la tua configurazione attuale del kernel nel file
	  <filename>/lib/modules/</filename><replaceable>version</replaceable><filename>/build/.config</filename>.
        </para>
      </step>
      <step>
        <para>
          Ogni kernel ha un nome basato sul numero della sua versione. Questo ??
	  il valore che mostra il comando <command>uname -r</command>.
	  Il nome del kernel ?? definito dalle prime quattro linee del
	  kernel <filename>Makefile</filename>. Per proteggere gli innocenti,
	  il <filename>Makefile</filename> ?? stato cambiato per generare
	  un kernel con un nome differente da quello in esecuzione.
	  Prima che un modulo possa essere accettato dal kernel in esecuzione,
	  quel modulo deve essere compilato per un kernel con il nome
	  corretto.  Per fare questo, devi editare il kernel
	  <filename>Makefile</filename>
        </para>
        <para>
          Per esempio, se con <command>uname -r</command> restituir?? la
	  stringa <systemitem
	    class="osname">2.6.11-1.234_FC4</systemitem>, canmbia la definizione
	  <systemitem class="macro">EXTRAVERSION</systemitem>
	  da questo:
        </para>
<screen width="60">
EXTRAVERSION = -prep
</screen>
        <para>
	  a questo:
	</para>
<screen width="60">
EXTRAVERSION = -1.234_FC4
</screen>
        <para>
          Cos??, sostituite ogni cosa dall'inizio alla fine.
        </para>
      </step>
      <step>
        <para>
          Impartite il seguente comando:
        </para>
<screen width="56">
<command>make oldconfig</command>
</screen>
      </step>
    </procedure>
    <para>
      Quindi potrai procedere come al solito.
    </para>
  </section>
  <section id="sn-kernel-3rdparty">
    <title>Compilare solo i moduli del Kernel</title>
    <para>
      Un albero dei sorgenti esploso <emphasis>non</emphasis> ?? necessario per
      compilare un modulo del kernel, tipo il tuo driver di periferica, per il
      kernel in uso.
    </para>
    <para>
      Per esempio, per compilare il modulo <filename>foo.ko</filename>,
      create il seguente <filename>Makefile</filename> nella
      directory contenente il file <filename>foo.c</filename>:
    </para>
<programlisting width="56">
obj-m := foo.o

KDIR  := /lib/modules/$(shell uname -r)/build
PWD   := $(shell pwd)

default:
    $(MAKE) -C $(KDIR) M=$(PWD) modules
</programlisting>
      <para>
      Impartite il comando <command>make</command> per creare
      il modulo <filename>foo.ko</filename>.
    </para>
  </section>
  <section id="sn-kernel-coop">
    <title>Dipendenze User Space sul Kernel</title>
    <para>
      &DISTRO; aggiunge supporto per i sistemi cluster. Ci?? richiede un
      kernel speciale che funzioni in congiunzione con alcune utilit?? 
      user-space, tipo i demoni di amministrazione. Di conseguenza, per rimuovere
      un simile kernel, forse dopo un aggiornamento,
      <emphasis>non puoi</emphasis> semplicemente usare il comando <command>rpm -e
	kernel-<replaceable>version</replaceable></command> come
      nelle precedenti distribuzioni poich?? questi pacchetti in user space
      dipendono dal pacchetto del kernel. Potresti elencare sia il pacchetto kernel
      ed i suoi pacchetti user space dependenti al comando <command>rpm
	-e</command>, o potresti usare il comando <command>yum
	remove kernel-<replaceable>version</replaceable></command>
      invece, poich?? <command>yum</command> rimuover?? automaticamente
      i pacchetti dependenti se necessario.
    </para>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE legacy-it.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE misc-server-it.xml ---
<section id="sn-misc-server-notes">
  <title>Note Miscellanee</title>
  <para>
    Questa sezione contiene informazioni relative ai pacchetti che non
    rientrano in nessuna delle precedenti categorie.
  </para>
  <section id="sn-misc-notes-openoffice">
      <title>OpenOffice e l'aggiornamento dalle test releases</title>
    <para>
      Se hai scelto di contravvenire alle raccomandazioni di
      <emphasis>non</emphasis> aggiornare da una test release precedente, potrai
      incontrare un problema con OpenOffice eseguedo l'upgrade.
    </para>
    <para>
      Per risolverlo, dovrai eseguire il seguente comando
      <emphasis>prima</emphasis> di eseguire l'aggiornamento:
    </para>
    <para>
      <command>rm -rf
	/usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
    </para>
  </section>
</section>

<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE multimedia-it.xml ---
<section id="sn-multimedia">
  <title>Multimedia</title>
  <para>
    &FC; include applicazioni per funzioni multimediali assortite,
    incluso ascolto, registrazione, ed editing.  Pacchetti aggiuntivi sono
    disponibili attraverso il repositorio &FEX;.
  </para>
  <variablelist>
    <varlistentry>
      <term>Multimedia Players</term>
      <listitem>
	<para>Per impostazione predefinita, &FC; viene installata con
	  <filename>rhythmbox</filename>, <filename>totem</filename>,
	  ed <application>Helix Player</application>
	  (<command>hxplay</command>) per il playback dei media.  Inoltre,
	  molti altri programmi sono disponibili nei repositori di &FC; e &FEX;,
	  incluso il popolare pacchetto xmms.  Sia GNOME
	  che KDE posseggono specifici gruppi di programmi che possono essere usati
	  con una variet?? di formati.  Anche altri popolari programmi, come
	  Adobe/Macromedia's Flash Player, Real Player, VLC, MPlayer,
	  e Xine, possono essere installati, ma sono esclusi dai repositori
	  &FED; a causa della loro incompatibilit?? con la licenza di &FED;
	  o sono solitamente distribuiti con il supporto di un ristretto numero
	  di formati.  Per saperne di pi?? su questo, fate riferimento a <xref
	  linkend="sn-multimedia-excluded"/>.
	</para>
	<para>
	  &FC; ?? anche ecquipaggiata per ottenere un pieno vantaggio dal sistema sonoro
	  Advanced Linux Sound Architecture (ALSA).  Questo vuol dire che
	  molti programmi possono suonare simultaneamente, che era una cosa
	  difficile sui sistemi linux.  Quando tutti i software multimediali sono
	  configurati per usare ALSA per il suppoto sonoro, questa vecchia limitazione
	  scompare.  Per maggiori informazioni su ALSA, visita il sito
	  web del progetto:
	</para>
	<para>
	  <ulink url='http://www.alsa-project.org/'>http://www.alsa-project.org/</ulink>
	</para>
      </listitem>    
    </varlistentry>
    <varlistentry>
      <term>I formati Ogg e Xiph.Org Foundation</term>
      <listitem>
	<para>Fedora include il supporto completo per il formato contenitore di
	media Ogg, il Vorbis audio, Theora video, Speex audio,
	ed il formato audio senza perdita di dati FLAC.  Maggiori informazioni su questi
	formati e su come usarli possono essere trovate sul sito web di Xiph.Org
	Foundation:
	</para>
	<para>
	  <ulink url='http://www.xiph.org/'>http://www.xiph.org/</ulink>
	</para>
      </listitem>   
    </varlistentry>
    <varlistentry>
      <term>MP3 &amp; DVD Support</term>
      <listitem>
	<para>&FC; e &FEX; non possono includere il supporto per il playback o la
	  registrazione degli MP3 o DVD, perch?? i formati MP3 e MPEG (DVD) sono
	  protetti da copyright, ed i proprietari dei brevetti non forniscono le
	  necessarie licenze.  Per maggiori informazioni, fate riferimento a <xref
	    linkend="sn-multimedia-excluded"/>.
	</para>
      </listitem>
    </varlistentry>
  </variablelist>
  <section id="sn-multimedia-excluded">
	  <title>Software multimediale escluso</title>
    <para>
      Diversi programmi sono esclusi da &FC; e &FEX; a cusa di problemi di
      licenza.  Queso include programmi che forniscono supporto MP3 e DVD,
      Flash Player e Real Player.  Gli utenti che desiderano usare questi
      programmi o formati ristretti devono acquisire pacchetti aggiuntivi
      dai loro rispettivi repositori.  Molte delle applicazioni
      multimediali nei repositorie Fedora supportano i plugins, cos??
      il supporto per nuovi formati pu?? essere facilmente aggiunto o rimosso.
      Per maggiori informazioni su questo soggetto, siete pregati di vedere:
    </para>
    <para>
      <ulink url='http://fedoraproject.org/wiki/ForbiddenItems'>http://fedoraproject.org/wiki/ForbiddenItems</ulink>
    </para>
  </section>
  <section id="sn-multimedia-cd-dvd-burning">
    <title>CD e DVD Authoring e Burning</title>
    <para>
      Strumenti per masterizzare facilmente CDs e DVDs sono inclusi in &FC; e &FEX;.
      Gli strumenti possono essere usati dalla console
      includono <command>cdrecord</command>, <command>readcd</command>,
      <command>mkisofs</command>, ed altre tipiche applicazioni Linux.
      Per gli utenti GNOME, il pacchetto <filename>xcdroast</filename> da
      &FC; ed il pacchetto <filename>graveman</filename> da &FEX;
      permettono una semplice preparazione di dischi audio e dati.  Per gli utenti KDE,
      il pacchetto <filename>k3b</filename> fornisce uno strumento robustissimo
      per questi compiti.
    </para>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Fri Nov  4 19:59:45 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Fri,  4 Nov 2005 14:59:45 -0500
Subject: release-notes printing-it.xml, NONE, 1.1 RELEASE-NOTES-it.xml, NONE,
	1.1 samba-it.xml, NONE, 1.1 security-it.xml, NONE,
	1.1 server-tools-it.xml, NONE, 1.1 web-servers-it.xml, NONE, 1.1
Message-ID: <200511041959.jA4Jxjux008684@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8663

Added Files:
	printing-it.xml RELEASE-NOTES-it.xml samba-it.xml 
	security-it.xml server-tools-it.xml web-servers-it.xml 
Log Message:



--- NEW FILE printing-it.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


***** Error reading new file: [Errno 2] No such file or directory: 'RELEASE-NOTES-it.xml'

--- NEW FILE samba-it.xml ---
<section id="sn-samba">
  <title>Samba (Compatibilit?? con il File System di Windows)</title>
  
  <para>
    Questa sezione contiene informazioni relative a Samba, la suite
    di software che consente a Linux di interagire con i sistemi Microsoft
    Windows.
  </para>

  <para>
    Esplorare le condivisioni di Windows (conosciuta anche come esplorazione SMB) fallisce
    sui sistemi &DISTRO; &DISTROVER; che hanno il firewall standard
    configurato. Questo pu?? pi?? facilmente essere notato con il fallimento del
    desktop nel mostrare le condivisioni.
   </para>

  <para>
   Il firewall disgrega la modalit?? broadcast dell'esplorazione SMB, per impostazione
   predefinita.  Ci sono due modi per ovviare al problema:
  </para>

  <itemizedlist>
    <listitem>
      <para>
	Configurare un WINS server sulla rete, ed impostare l'opzione
	"wins server" in smb.conf con l'indirizzo del WINS server.
      </para>
    </listitem>
    <listitem>
      <para>
	Disabilitare il firewall.
      </para>
    </listitem>
  </itemizedlist>

  <warning>
    <title>Disabilitare il firewall potrebbe rendere il tuo sistema vulnerabile</title>  
    <para>
      Sii sicuro di aver pienamente compreso il rischio prima di prendere questa
      decisione.
    </para>
  </warning>

  <para>
    Per ulteriori informazioni, fai riferimento al seguente bug report:
  </para>
  
  <para>
    <ulink url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478</ulink>
  </para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE security-it.xml ---
<section id="sn-security">
  <title>Sicurezza</title>
  <para>
    Questa sezione evidenzia varie questioni di sicurezza da &FC;.
  </para>
  <para>
    <computeroutput>Pam_stack</computeroutput> ?? deprecato. Maggiori
    dettagli sono disponibili dalla fedora-test-list (<ulink
    url="http://www.redhat.com/mailman/listinfo/fedora-test-list">http://www.redhat.com/mailman/listinfo/fedora-test-list</ulink>
  </para>
  <section id="sn-security-highlights">
    <title>Novit?? sulla sicurezza</title>
    <para>
      Questa sezione evidenzia varie questioni di sicurezza da &FC;.
    </para>
    <para>
      I certificati digitali sono ora centralizzati in directories
      sotto <filename>/etc/pki/</filename>. Gli utenti che eseguono un aggiornamento devono
      rilocare i propri certificati digitali.
    </para>
    <para>
      OpenSSL: i contenuti di <filename>/usr/share/ssl/</filename> sono stati
      sossi su <filename>/etc/pki/tls/</filename> e
      <filename>/etc/pki/CA/</filename>.
    </para>
    <para>
      Dovecot: Un file dovecot-openssl.cnf ?? automaticamente installato in
      <filename>/etc/pki/dovecot/</filename>.
    </para>
  </section>
  <section id="sn-security-selinux-changes">
    <title>Cambiamenti su SELinux</title>
    <para>
      MCS SELinux ?? dentro. Maggiori novit??.  Per maggiori
      informazioni, leggete questo articolo informativo:
    </para>
    <para>
      <ulink
	url="http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/msg00001.html">http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/msg00001.html</ulink>
    </para>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE server-tools-it.xml ---
<section id="sn-server-sys-config">
  <title>Strumenti di configurazione del server e del sistema</title>
  <caution>
    <title>Information Out-of-Date</title>
    <para>
      Il contenuto in questa sezione ha necessit?? di essere aggiornato per &DISTRO;
      &DISTROVER;
    </para>
  </caution>
  <para>
    Questa sezione evidenzia i cambiamenti e le aggiunte alle svariate GUI degli
    strumenti dei servers e del sistema in &FC;.
  </para>
  <section id="sn-system-config-lvm">
    <title><application>system-config-lvm</application></title>
    <para>
      Il nuovo strumento LVM <application>system-config-lvm</application>
      ti assiste nell'amministrazione dei volumi logici.
    </para>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE web-servers-it.xml ---
<section id="sn-web-servers">
  <title>Web Servers</title>
  <para>
    Questa sezione contiene informazioni sulle applicazioni relative al web.
  </para>
  <section>
    <title><command>httpd</command></title>
    <para>
      Il seguenti cambiamenti sono stati fatti sulla configurazione predefinita di <command></command>httpd:
    </para>
    <itemizedlist>
      <listitem>
	<para>I moduli <computeroutput>mod_cern_meta</computeroutput> e
	  <computeroutput>mod_asis</computeroutput> non sono pi?? caricati
	  per impostazione predefinita.
	</para>
      </listitem>
      <listitem>
	<para>Il modulo <computeroutput>mod_ext_filter</computeroutput> ?? ora caricato
	  per impostazione predefinita.
	</para>
      </listitem>
    </itemizedlist>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Fri Nov  4 20:03:03 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Fri,  4 Nov 2005 15:03:03 -0500
Subject: release-notes networking-it.xml, NONE, 1.1 overview-it.xml, NONE,
	1.1 package-movement-it.xml, NONE, 1.1 package-notes-it.xml,
	NONE, 1.1 project-overview-it.xml, NONE, 1.1 README-it.xml,
	NONE, 1.1 RELEASE-NOTES-master-it.xml, NONE, 1.1 splash-it.xml,
	NONE, 1.1 xorg-it.xml, NONE, 1.1
Message-ID: <200511042003.jA4K33Hk010197@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10168

Added Files:
	networking-it.xml overview-it.xml package-movement-it.xml 
	package-notes-it.xml project-overview-it.xml README-it.xml 
	RELEASE-NOTES-master-it.xml splash-it.xml xorg-it.xml 
Log Message:



--- NEW FILE networking-it.xml ---
<section id="sn-networking">
  <title>Networking</title>
  <variablelist>
    <title>Principali cambiamenti nel Kernel 2.6.11 - 2.6.14</title>
    <varlistentry>
      <term>Promozione indirizzo IPv4</term>
      <listitem>
      <para>A partire dalla versione 2.6.12 del kernel una nuova caratteristica ?? stata
	aggiunta chiamata promozione indirizzo. Essa permette la promozione di un indirizzo IPv4
	secondario come indirizzo primario. Di solito quando l'indirizzo
	primario ?? cancellato tutti gli indirizzi secondari sono cancellati
	anch'essi. Abilitando il nuovo <command>sysctl</command>
	<option>net.ipv4.conf.all.promote_secondaries</option> (o una delle
	varianti specifiche d'interfaccia) questo comportamento pu?? essere cambiato per
	promuovere uno degli indirizzi secondari come nuovo indirizzo
	primario.
      </para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>Indirizzo sorgente configurabile per gli errori ICMP</term>
      <listitem>
	<para>
	  Il comportamento attuale quando selezioniamo l'indirizzo sorgente per
	  i messaggi d'errore ICMP ?? quello di usare l'indirizzo dell'interfaccia
	  verso cui l'errore ICMP sta andando per essere spedito. La versione del Kernel
	  2.6.12 introduce un nuovo <command>sysctl</command>
	  <option>net.ipv4.icmp_errors_use_inbound_ifaddr</option> che permette
	  di cambiare questo comportamento per usare l'indirizzo
	  dell'interfaccia che ha ricevuto il pacchetto originale che ha causato
	  l'errore.
	</para>
	<para>
	  Per esempio, il kernel riceve una richiesta echo ICMP su
	  <computeroutput>eth0</computeroutput>.  Poich?? la nuova opzione
	  <command>sysctl</command> ?? abilitata, ci?? causa che la
	  risposta all'echo ICMP sia spedita via
	  <computeroutput>eth1</computeroutput>. L'indirizzo di
	  <computeroutput>eth0</computeroutput> ?? usato quando il comportamento
	  predefinito user?? l'indirizzo di
	  <computeroutput>eth</computeroutput>.
	</para>
	<para>
	  Questo potrebbe facilitare il debug della rete nell'installazione
	  di routing asincrono.
	</para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>LC-Trie Based Routing Lookup Algorithm</term>
      <listitem>
	<para>
	  E' stato aggiunto un nuovo algoritmo di routing
	  lookup chiamato <firstterm>trie</firstterm>. E' inteso per
	  grandi tavole di routing e mostra un chiaro miglioramento delle prestazioni
	  rispetto all'origninale implementazione hash al costo di un aumento
	  del consumo di memoria e della complessit??.
	</para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>Pluggable Congestion Control Algorithm Infrastructure</term>
      <listitem>
	<para>L'algoritmo di controllo della congestione TCP ?? ora pluggable e
	  quindi modulare. L'algoritmo legacy <firstterm>new RENO</firstterm>
	  rimane il predefinito e funziona come algoritmo di ritorno. Nel periodo
	  di questo lavoro i seguenti nuovi algoritmi di controllo della congestione
	  sono stati aggiunti:
	</para>
	<itemizedlist>
	  <listitem>
	    <para>Controllo di congestione TCP ad alta velocit??.
	    </para>
	  </listitem>
	  <listitem>
	    <para>Impedimento di congestione TCP Hybla.
	    </para>
	  </listitem>
	  <listitem>
	    <para>Controllo di congestione H-TCP.
	    </para>
	  </listitem>
	  <listitem>
	    <para>Controllo di congestione TCP scalabile.
	    </para>
	  </listitem>
	</itemizedlist>
	<para>Tutti i moduli di controllo della congestione sono stati
	  convertiti a questa nuova infrastruttura ed il controllo di
	  congestione BIC ?? stato migliorato dal BICTCP 1.1
	  per manipolare links a bassa latenza.
	</para>
	<note>
	  <title>Cose che interessano L'algoritmo di controllo di congestione</title>
	  <para>
	    Una interessante aggiunta per gli sviluppatori ?? che
	    l'algoritmo di controllo della congestione ?? spcifico al socket e pu??
	    essere cambiato mediante l'opzione socket
	    <option>TCP_CONGESTION</option>. 
	  </para>
	</note>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>Impedimento di accodamento per perdita di linea</term>
      <listitem>
      <para>Quando un driver di rete si accorge di una perdita di linea, per esempio
	  quando un cavo viene staccato, il driver ferma la coda davanti
	  al driver. Questo ha causato che i pacchetti siano stati
	  accodati al layer di coda disciplinata per un certo periodo
	  di tempo causando effetti inaspettati. Per prvenire questo
	  effetto, lo stack di rete di base adesso cessa di accettare qualsiasi
	  paccchetto per la coda da ogni device che sia operativamente
	  disattivato, cio??, ha l'accodamento disabilitato.
	</para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>DCCP Protocol Support</term>
      <listitem>
	<para>Kernel version 2.6.14-rc1 was the first version to receive
	  support for the DCCP protocol. The implementation is still
	  experimental but known to work. Work to make userspace
	  applications aware of this new protocol has started.
	</para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>Wireless</term>
      <listitem>
	<para>A new driver named HostAP has been added to 2.6.14-rc1
	  allowing the emulation of a wireless access point in software.
	  Currently this driver only works for Intersil Prism2-based
	  cards (PC Card/PCI/PLX). Support for wireless cards Intel(R)
	  PRO/Wireless 2100 and 2200 has been added.
	</para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term>Miscellaneous</term>
      <listitem>
	<itemizedlist>
	  <listitem>
	    <para>A lot of TCP Segmentation Offloading (TSO) related
	      fixes have been included.
	    </para>
	  </listitem>
	  <listitem>
	    <para>A new textsearch infrastructure has been added
	      useable with the corresponding iptables and extended
	      match.
	    </para>
	  </listitem>
	  <listitem>
	    <para>Both the IPv4 and IPv6 multicast joining interface
	      visible by userspace have been reworked and brought up to
	      the latest standards.
	    </para>
	  </listitem>
	  <listitem>
	    <para>The SNMPv2 MIB counter ipInAddrErrors is finally
	      supported for IPv4.
	    </para>
	  </listitem>
	  <listitem>
	    <para>Various new socket options proposed in Advanced API
	      (RFC3542) have been added.
	    </para>
	  </listitem>
	</itemizedlist>
      </listitem> 
    </varlistentry>
  </variablelist>
  <section sn="kernel-userspace-tools">
    <title>Userspace Tools</title>
    <title>iproute</title>
    <para>
      The IPv4 address deletion algorithm did not take the prefix
      length into account up to kernel version 2.6.12. Since this has
      changed the iproute2 tool now issues a warning if no prefix length
      is provided to warn about possible unintended deletions:
    </para>
<screen>
ip addr list dev eth0
4: eth0: &lt;BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    inet 10.0.0.3/24 scope global eth0
su -c 'ip addr del 10.0.0.3 dev eth0'
Warning: Executing wildcard deletion to stay compatible with old
      scripts. Explicitly specify the prefix length (10.0.0.3/32) to
      avoid this warning. This special behaviour is likely to disappear
      in further releases, fix your scripts!
</screen>
    <para>
      The correct method of deleting the address and thus avoiding the
      warning is:
    </para>
<screen>
su -c 'ip addr del 10.0.0.3/24 dev eth0'
</screen>
    <para>
      It has not been possible to tell if an interface is down
      administratively or because no carrier can be found (cable
      unplugged). The flag <computeroutput>NO-CARRIER</computeroutput>
      has been introduced that shows up as a link flag if the link is
      administratively up but no carrier can be found.
    </para>
    <para>
      The <command>ip</command> command now supports a batch mode via
      the argument <option>-batch</option> just like the
      <command>tc</command> command to speed up batches of tasks.
    </para>
  </section>
</section>

<!-- cruft, but saved just in case :)
  <para>
   This section contains information relating to network connectivity.
  </para>
  <section id="sn-networking-networkmanager">
    <title><filename>NetworkManager</filename></title>
    <para>
      The <command>NetworkManager</command> service allows computers
      such as laptops to automatically manage changing network
      connections.  It includes support for wireless networking.
    </para>
    <para>
      You must manually enable the <command>NetworkManager</command>
      service.  To do so, type the following in a terminal window:
    </para>
<screen>
su -c '/sbin/chkconfig --level 345 NetworkManager on; /sbin/service NetworkManager start'
su -c '/sbin/chkconfig --level 345 NetworkManagerDispatcher on; /sbin/service NetworkManagerDispatcher start'
</screen>
    <para>
      Enter the root password when prompted.
    </para>
    <para>
      Use the <application>Network Monitor</application> desktop applet
      to monitor and configure <command>NetworkManager</command>.  To load the
      applet in GNOME, right-click on the panel and select:
    </para>
    <para>
     <guimenuitem>Add to Panel...</guimenuitem><guimenuitem>Network
     Monitor</guimenuitem>
    </para>
    <para>
      <command>NetworkManager</command> uses BIND to proxy DNS requests.
      Enabling the <command>NetworkManager</command> service also loads the
      <command>named</command> service as well.  By default BIND is
      configured as a cacheing service for the local system, and does
      not accept connections from other systems.  
    </para>
    <para>
	Note that some wireless network cards require drivers or firmware
	that cannot be included with &DISTRO;.  This software must be
	installed separately for <command>NetworkManager</command> to function.
    </para>
-->
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE overview-it.xml ---
<section id="sn-overview">
  <title>Overview of This Release</title>
  <caution>
    <title>Information Out-of-Date</title>
    <para>
      The content in this section needs to be updated for &DISTRO;
      &DISTROVER;
    </para>
  </caution>
<!--
  <para>
    The following list includes brief summaries of some of the more
    significant aspects of &DISTRO; &DISTROVER;:
  </para>
  <itemizedlist>
    <listitem>
      <para>
	&DISTRO; &DISTROVER; contains the following changes:
      </para>
      <itemizedlist>
	<listitem>
	  <para>
	    Support for the PowerPC (PPC) architecture.
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GCC 4.0
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GNOME 2.10
	  </para>
	</listitem>
	<listitem>
	  <para>
	    KDE 3.4 &mdash; includes new accessibility features.  You
	    can manage these new features in <guimenu>KDS Control
	      Center</guimenu><guisubmenu>Regional &amp;
	      Accessibility</guisubmenu><guisubmenu>Accessibility</guisubmenu>.
	  </para>
	</listitem>
	<listitem>
	  <para>
	    Native Eclipse 3.1M6 (part of a free Java stack)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    MySQL 4.1
	  </para>
	</listitem>
	<listitem>
	  <para>
	    PHP 5.0
	  </para>
	</listitem>
	<listitem>
	  <para>
	    Xen 2 (virtualization to run multiple versions of an OS)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GFS 6.1-0.pre22 (cluster file system)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    Evince 0.2.1 (universal document viewer)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GDM 2.6 - Includes early login capability
	  </para>
	</listitem>
	<listitem>
	  <para>
	    &SEL; &mdash; This release includes coverage for 80 new
	    daemons by the targeted policy.  There are changes to the
	    handling of Booleans.  The targeted policy is enabled by
	    default.  For more information, refer to:  <ulink
	      url="http://fedora.redhat.com/docs/selinux-faq/">http://fedora.redhat.com/docs/selinux-faq/</ulink>. 
	    This is the complete list of daemons covered by the targeted
	    policy:
	  </para>
	  <itemizedlist>
	    <listitem>
	      <para>
		<command>NetworkManager</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>amanda</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>apache</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>apmd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>arpwatch</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>auditd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>bluetooth</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>canna</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cardmgr</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>checkpolicy</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>chkpwd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>compat</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>comsat</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>consoletype</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cpucontrol</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cpuspeed</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>crond</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cups</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cvs</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>cyrus</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dbskkd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dbusd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dhcpc</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dhcpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dictd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dmidecode</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>dovecot</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>fingerd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>fsadm</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ftpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>getty</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>hald</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>hostname</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>hotplug</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>howl</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>hwclock</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>i18n_input</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ifconfig</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>inetd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>init</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>initrc</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>innd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>kerberos</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>klogd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ktalkd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>kudzu</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ldconfig</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>load_policy</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>login</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>lpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>mailman</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>modutil</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>mta</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>mysqld</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>named</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>netutils</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>nscd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ntpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>portmap</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>postgresql</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ppd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>privoxy</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>radius</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>radvd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>restorecon</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>rlogind</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>rpcd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>rpm</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>rshd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>rsync</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>samba</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>saslauthd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>sendmail</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>setfiles</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>slapd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>snmpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>squid</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ssh</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>stunnel</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>syslogd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>telnetd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>tftpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>udev</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>updfstab</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>uucpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>webalizer</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>winbind</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>xdm</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ypbind</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>ypserv</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command>zebra</command>
	      </para>
	    </listitem>
	  </itemizedlist>
	</listitem>
      </itemizedlist>
    </listitem>
  </itemizedlist>
-->
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE package-movement-it.xml ---
<section id="sn-package-movement">
  <title>Packages Movement</title>
  <!-- 
  FIXME
  Needs updating of entire contents for FC4.
  -->
  <para>
    This command was used to generate the list of package changes.  The
    backslash <computeroutput>\</computeroutput> is used to artificially
    break the line for printing purposes.:
  </para>
<screen>
<command>treediff.py dist-fc4 dist-rawhide > /tmp/diff \
sed -e 's,^,* ,g' -e 's,$,\n,g' /tmp/diff > diffwiki</command>
</screen>
  <section>
    <title>Package Changes</title>
    <para>As of 21st September 2005 </para>
    <para>[106429] MAKEDEV-3.19-1 -> [115423] MAKEDEV-3.19-4 </para>
    <para>[111566] <ulink
	url='/ImageMagick'>ImageMagick</ulink>-6.2.2.0-2 -> [112246]
      <ulink url='/ImageMagick'>ImageMagick</ulink>-6.2.2.0-4 </para>
    <para>[105261] newt-0.51.6-7 -> [117695] newt-0.51.6-8 </para>
    <para>[106878] am-utils-6.0.9-12 -> [117066] am-utils-6.1.1-2
    </para>
    <para>[108819] amanda-2.4.5-2 -> [115871] amanda-2.4.5-3 </para>
    <para>[112105] anaconda-10.2.1.5-2 -> [118390]
      anaconda-10.3.0.24-1 </para>
    <para>[105300] aspell-0.50.5-6 -> [114172] aspell-0.60.3-2 </para>
    <para>[108035] aspell-ca-0.50-2 -> [114184] aspell-ca-0.50-4
    </para>
    <para>[108036] aspell-cs-0.51-2 -> [114270] aspell-cs-0.51-3
    </para>
    <para>[108038] aspell-da-0.50-11 -> [114276] aspell-da-0.50-12
    </para>
    <para>[106443] libsoup-2.2.3-2 -> [116988] libsoup-2.2.6.1-1
    </para>
    <para>[108042] aspell-es-0.50-11 -> [117058] aspell-es-0.50-13
    </para>
    <para>[108044] aspell-fr-0.50-8 -> [114285] aspell-fr-0.50-9
    </para>
    <para>[108051] aspell-it-0.53-2 -> [114362] aspell-it-0.53-3
    </para>
    <para>[108055] aspell-nl-0.50-6 -> [114363] aspell-nl-0.50-7
    </para>
    <para>[108058] aspell-no-0.50.1-8 -> [114366] aspell-no-0.50.1-9
    </para>
    <para>[108060] aspell-pl-0.51-3 -> [118018] aspell-pl-0.51-5
    </para>
    <para>[108061] aspell-sv-0.50-7 -> [114371] aspell-sv-0.50-8
    </para>
    <para>[107959] at-3.1.8-77_FC4 -> [112026] at-3.1.8-78 </para>
    <para>[108132] gtkhtml3-3.6.2-1 -> [117587] gtkhtml3-3.8.0-1
    </para>
    <para>[108304] ntp-4.2.0.a.20040617-8 -> [117060]
      ntp-4.2.0.a.20050816-1 </para>
    <para>[108909] autofs-4.1.4-5 -> [112718] autofs-4.1.4-9 </para>
    <para>[102923] automake-1.9.5-1 -> [114414] automake-1.9.6-1
    </para>
    <para>[108562] autorun-3.16-1 -> [118091] autorun-3.17-1 </para>
    <para>[105321] awesfx-0.5.0d-2 -> [113536] awesfx-0.5.0d-3 </para>
    <para>[105808] nut-2.0.1-1 -> [114509] nut-2.0.2-1 </para>
    <para>[110344] bash-3.0-31 -> [118423] bash-3.0-34 </para>
    <para>[110908] bind-9.3.1-4 -> [116915] bind-9.3.1-11 </para>
    <para>[111486] binutils-2.15.94.0.2.2-2 -> [116754]
      binutils-2.16.91.0.2-4 </para>
    <para>[105319] bootparamd-0.17-22.devel -> [116780]
      bootparamd-0.17-23.devel </para>
    <para>[106988] bug-buddy-2.10.0-1 -> [117633] bug-buddy-2.12.0-1
    </para>
    <para>[111028] bzip2-1.0.2-16 -> [117182] bzip2-1.0.3-1 </para>
    <para>[106470] pax-3.0-11 -> [116422] pax-3.4-1 </para>
    <para>[109185] <ulink url='/SysVinit'>SysVinit</ulink>-2.85-39 ->
      [113360] <ulink url='/SysVinit'>SysVinit</ulink>-2.85-40 </para>
    <para>[111393] control-center-2.10.1-6 -> [118105]
      control-center-2.12.0-2 </para>
    <para>[111120] openldap-2.2.23-5 -> [111936] openldap-2.2.26-1
    </para>
    <para>[110745] cpio-2.6-7 -> [113389] cpio-2.6-8 </para>
    <para>[106419] cracklib-2.8.2-1 -> [111862] cracklib-2.8.3-1
    </para>
    <para>[104496] bluez-hcidump-1.18-1 -> [115995]
      bluez-hcidump-1.24-1 </para>
    <para>[104877] ctags-5.5.4-3 -> [115419] ctags-5.5.4-4 </para>
    <para>[108614] cvs-1.11.19-8 -> [116935] cvs-1.11.19-10 </para>
    <para>[108252] cyrus-sasl-2.1.20-5 -> [117833] cyrus-sasl-2.1.21-5
    </para>
    <para>[109650] pam-0.79-8 -> [118330] pam-0.80-8 </para>
    <para>[109663] dhcp-3.0.2-12 -> [117972] dhcp-3.0.3-6 </para>
    <para>[110743] apr-0.9.6-3 -> [118164] apr-0.9.6-6 </para>
    <para>[110347] e2fsprogs-1.37-4 -> [117739] e2fsprogs-1.38-1
    </para>
    <para>[104668] diffstat-1.38-2 -> [116208] diffstat-1.38-4 </para>
    <para>[107298] doxygen-1.4.2-1 -> [118248] doxygen-1.4.4-2 </para>
    <para>[110505] dump-0.4b40-2 -> [113542] dump-0.4b40-4 </para>
    <para>[110508] eject-2.0.13-15 -> [117061] eject-2.1.2-1 </para>
    <para>[110262] parted-1.6.22-2 -> [117238] parted-1.6.24-1 </para>
    <para>[110911] emacs-21.4-5 -> [114092] emacs-21.4-7 </para>
    <para>[111808] esound-0.2.35-5 -> [114327] esound-0.2.36-1 </para>
    <para>[105304] passwd-0.69-2 -> [112701] passwd-0.70-1 </para>
    <para>[106286] fetchmail-6.2.5-7 -> [114678] fetchmail-6.2.5.2-1
    </para>
    <para>[109759] patch-2.5.4-24 -> [117794] patch-2.5.4-29 </para>
    <para>[111272] filesystem-2.3.4-1 -> [116817] filesystem-2.3.5-1
    </para>
    <para>[106330] findutils-4.2.20-1 -> [117490] findutils-4.2.25-2
    </para>
    <para>[105012] finger-0.17-28 -> [113967] finger-0.17-29 </para>
    <para>[105097] freetype-2.1.9-2 -> [116586] freetype-2.1.9-4
    </para>
    <para>[111401] ftp-0.17-26 -> [117241] ftp-0.17-29 </para>
    <para>[104499] gawk-3.1.4-5 -> [118359] gawk-3.1.5-2 </para>
    <para>[111099] gcc-4.0.0-8 -> [118294] gcc-4.0.1-14 </para>
    <para>[108458] gd-2.0.33-2 -> [117628] gd-2.0.33-3 </para>
    <para>[109684] gdb-6.3.0.0-1.21 -> [117661] gdb-6.3.0.0-1.65
    </para>
    <para>[106626] gettext-0.14.3-1 -> [116274] gettext-0.14.5-1
    </para>
    <para>[111402] gdm-2.6.0.8-16 -> [117776] gdm-2.8.0.4-1 </para>
    <para>[108333] gedit-2.10.2-3 -> [117719] gedit-2.12.0-1 </para>
    <para>[110935] perl-5.8.6-15 -> [117489] perl-5.8.7-0.3.fc5
    </para>
    <para>[107237] gok-1.0.3-1 -> [116496] gok-1.0.5-4 </para>
    <para>[110356] php-5.0.4-10 -> [118097] php-5.0.5-3 </para>
    <para>[110581] gimp-2.2.7-4 -> [116538] gimp-2.2.8-3 </para>
    <para>[111654] gnome-applets-2.10.1-9 -> [117721]
      gnome-applets-2.12.0-1 </para>
    <para>[111691] glibc-2.3.5-10 -> [117966] glibc-2.3.90-12 </para>
    <para>[111104] gnome-games-2.10.0-5 -> [117724]
      gnome-games-2.12.0-1 </para>
    <para>[111214] gnome-media-2.10.2-4 -> [117726]
      gnome-media-2.12.0-1 </para>
    <para>[106508] kdeadmin-3.4.0-1 -> [118336] kdeadmin-3.4.2-2
    </para>
    <para>[110919] gnome-utils-2.10.0-3 -> [117738]
      gnome-utils-2.12.0-1 </para>
    <para>[110246] gnupg-1.4.1-3 -> [116120] gnupg-1.4.2-3 </para>
    <para>[104528] gnuplot-4.0.0-7 -> [117403] gnuplot-4.0.0-8 </para>
    <para>[104506] gperf-3.0.1-6 -> [115552] gperf-3.0.1-7 </para>
    <para>[104548] grep-2.5.1-48 -> [113236] grep-2.5.1-50 </para>
    <para>[108057] xinitrc-4.0.18-1 -> [111974] xinitrc-4.0.19-1
    </para>
    <para>[104544] guile-1.6.7-2 -> [117402] guile-1.6.7-4 </para>
    <para>[104475] hdparm-5.9-1 -> [112183] hdparm-6.1-1 </para>
    <para>[111501] initscripts-8.11.1-1 -> [117977] initscripts-8.14-1
    </para>
    <para>[107880] inn-2.4.2-3 -> [115559] inn-2.4.2-4 </para>
    <para>[106114] iproute-2.6.11-1 -> [118247] iproute-2.6.14-3
    </para>
    <para>[106499] iptables-1.3.0-2 -> [114287] iptables-1.3.2-1
    </para>
    <para>[107881] iputils-20020927-22 -> [117698] iputils-20020927-26
    </para>
    <para>[111656] isdn4k-utils-3.2-28 -> [115009] isdn4k-utils-3.2-32
    </para>
    <para>[105032] joe-3.1-8 -> [112056] joe-3.3-1 </para>
    <para>[108237] kdebase-3.4.0-5 -> [118422] kdebase-3.4.2-5 </para>
    <para>[106532] kdegames-3.4.0-1 -> [116019] kdegames-3.4.2-1
    </para>
    <para>[107198] kdegraphics-3.4.0-2 -> [117508] kdegraphics-3.4.2-3
    </para>
    <para>[104526] openobex-1.0.1-3 -> [111937] openobex-1.0.1-4
    </para>
    <para>[107226] kdemultimedia-3.4.0-2 -> [115553]
      kdemultimedia-3.4.2-1 </para>
    <para>[106551] kdeutils-3.4.0-1 -> [117699] kdeutils-3.4.2-2
    </para>
    <para>[105322] minicom-2.00.0-21 -> [114175] minicom-2.1-1 </para>
    <para>[112015] kernel-2.6.11-1.1369_FC4 -> [118394]
      kernel-2.6.13-1.1565_FC5 </para>
    <para>[108707] libbtctl-0.4.1-7 -> [114382] libbtctl-0.4.1-8
    </para>
    <para>[107067] krb5-1.4-3 -> [118053] krb5-1.4.2-4 </para>
    <para>[106252] krbafs-1.2.2-7 -> [115422] krbafs-1.2.2-8 </para>
    <para>[111032] kudzu-1.1.116.2-2 -> [118290] kudzu-1.2.7-1 </para>
    <para>[105596] lam-7.1.1-3 -> [115564] lam-7.1.1-7.FC5 </para>
    <para>[105047] less-382-7 -> [117533] less-382-8 </para>
    <para>[104599] libieee1284-0.2.9-2 -> [114409] libieee1284-0.2.9-3
    </para>
    <para>[106523] libtermcap-2.0.8-41 -> [115467] libtermcap-2.0.8-42
    </para>
    <para>[110440] libtiff-3.7.1-6 -> [113273] libtiff-3.7.2-1 </para>
    <para>[109070] libtool-1.5.16.multilib2-1 -> [118098]
      libtool-1.5.20-3 </para>
    <para>[104597] lm_sensors-2.8.8-5 -> [117365] lm_sensors-2.9.1-4
    </para>
    <para>[105199] lockdev-1.0.1-7 -> [118409] lockdev-1.0.1-9 </para>
    <para>[107338] logrotate-3.7.1-10 -> [117629] logrotate-3.7.2-3
    </para>
    <para>[110353] lsof-4.74-7 -> [118297] lsof-4.76-1 </para>
    <para>[108835] dovecot-0.99.14-4.fc4 -> [114740]
      dovecot-0.99.14-6.fc5 </para>
    <para>[106781] make-3.80-7 -> [116850] make-3.80-8 </para>
    <para>[104365] distcache-1.4.5-7 -> [115345] distcache-1.4.5-11
    </para>
    <para>[107530] man-pages-1.67-7 -> [118017] man-pages-2.07-5
    </para>
    <para>[93204] man-pages-cs-0.16-4 -> [115882] man-pages-cs-0.16-5
    </para>
    <para>[93194] man-pages-de-0.4-9 -> [115873] man-pages-de-0.4-10
    </para>
    <para>[108613] man-pages-ja-20050415-1 -> [116660]
      man-pages-ja-20050815-1 </para>
    <para>[110081] mx4j-2.1.0-1jpp_7fc -> [114677] mx4j-3.0.1-1jpp_5fc
    </para>
    <para>[109945] mc-4.6.1a-0.9 -> [118021] mc-4.6.1a-0.15 </para>
    <para>[101562] desktop-file-utils-0.10-1 -> [117302]
      desktop-file-utils-0.10-3 </para>
    <para>[111217] redhat-artwork-0.122-10 -> [116975]
      redhat-artwork-0.128-1 </para>
    <para>[104435] mikmod-3.1.6-34 -> [112072] mikmod-3.1.6-35 </para>
    <para>[110923] mkinitrd-4.2.15-1 -> [116471] mkinitrd-4.2.21-1
    </para>
    <para>[110244] gimp-print-4.2.7-7 -> [116481] gimp-print-4.2.7-12
    </para>
    <para>[111409] rhpl-0.167-1 -> [118384] rhpl-0.174-1 </para>
    <para>[108728] glade2-2.10.0-1 -> [116544] glade2-2.10.0-2 </para>
    <para>[107181] pyxf86config-0.3.19-4 -> [114209]
      pyxf86config-0.3.19-6 </para>
    <para>[105582] arptables_jf-0.0.8-4 -> [116740]
      arptables_jf-0.0.8-6 </para>
    <para>[108583] fontconfig-2.2.3-13 -> [114861] fontconfig-2.3.2-1
    </para>
    <para>[108241] oprofile-0.8.2-4 -> [114916] oprofile-0.9.1-2
    </para>
    <para>[104605] mtr-0.69-3 -> [117503] mtr-0.69-4 </para>
    <para>[105384] mutt-1.4.2.1-2 -> [117134] mutt-1.4.2.1-3 </para>
    <para>[106486] kdeedu-3.4.0-1 -> [118428] kdeedu-3.4.2-3 </para>
    <para>[111281] httpd-2.0.54-10 -> [115215] httpd-2.0.54-12 </para>
    <para>[109664] libwpd-0.8.1-1 -> [117298] libwpd-0.8.3-1 </para>
    <para>[109161] ncurses-5.4-17 -> [115668] ncurses-5.4-18 </para>
    <para>[109016] net-tools-1.60-52 -> [115663] net-tools-1.60-56
    </para>
    <para>[106997] rdesktop-1.4.0-2 -> [113322] rdesktop-1.4.1-1.fc5
    </para>
    <para>[106852] redhat-rpm-config-8.0.34-1 -> [116588]
      redhat-rpm-config-8.0.39-1 </para>
    <para>[104517] compat-slang-1.4.5-10 -> [115421]
      compat-slang-1.4.5-11 </para>
    <para>[111646] nfs-utils-1.0.7-8 -> [117732] nfs-utils-1.0.7-16
    </para>
    <para>[104611] rarpd-ss981107-20 -> [114929] rarpd-ss981107-22
    </para>
    <para>[111216] nss_ldap-234-4 -> [117936] nss_ldap-241-1 </para>
    <para>[101793] squirrelmail-1.4.4-2 -> [117917]
      squirrelmail-1.4.6-0.cvs20050812.2.fc5 </para>
    <para>- perl-Filter-1.30-7 </para>
    <para>- perl-Filter-Simple-0.79-5 </para>
    <para>[111400] libxslt-1.1.14-2 -> [117480] libxslt-1.1.15-1
    </para>
    <para>[111035] pam_krb5-2.1.7-3 -> [115747] pam_krb5-2.1.8-2
    </para>
    <para>[106493] file-roller-2.10.0-1 -> [117656]
      file-roller-2.12.0-1 </para>
    <para>[106353] pyOpenSSL-0.6-1.p24.4 -> [117052]
      pyOpenSSL-0.6-1.p24.6 </para>
    <para>[104627] rdist-6.1.5-40 -> [111944] rdist-6.1.5-41 </para>
    <para>[110926] spamassassin-3.0.3-4.fc4 -> [118074]
      spamassassin-3.1.0-1.fc5 </para>
    <para>[105950] pilot-link-0.12.0-0.pre2.0 -> [117233]
      pilot-link-0.12.0-0.pre4.5 </para>
    <para>[106474] star-1.5a54-2 -> [117115] star-1.5a65-1 </para>
    <para>[111515] net-snmp-5.2.1-12 -> [118322] net-snmp-5.2.1.2-3
    </para>
    <para>[96116] ppp-2.4.2-7 -> [115416] ppp-2.4.3-3 </para>
    <para>[110366] vlock-1.3-19 -> [115661] vlock-1.3-20 </para>
    <para>[110359] procps-3.2.5-6 -> [117548] procps-3.2.5-7 </para>
    <para>[105210] psmisc-21.5-4 -> [117707] psmisc-21.6-1 </para>
    <para>[105614] pvm-3.4.5-3_FC4 -> [111812] pvm-3.4.5-5 </para>
    <para>[105105] bogl-0.1.18-7 -> [118318] bogl-0.1.18-10 </para>
    <para>[108185] gnopernicus-0.10.6-1 -> [117638]
      gnopernicus-0.11.6-1 </para>
    <para>[110883] qt-3.3.4-14 -> [118419] qt-3.3.5-2 </para>
    <para>[104494] ksh-20050202-1 -> [111912] ksh-20050202-3 </para>
    <para>[108083] quota-3.12-6 -> [116742] quota-3.12-7 </para>
    <para>[101735] gnome-speech-0.3.6-1 -> [115904]
      gnome-speech-0.3.7-1 </para>
    <para>[111387] openoffice.org-1.9.104-2 -> [118196]
      openoffice.org-1.9.130-1.2.fc5 </para>
    <para>[105350] rp-pppoe-3.5-27 -> [116414] rp-pppoe-3.5-30 </para>
    <para>[111410] rpm-4.4.1-21 -> [117156] rpm-4.4.2-4 </para>
    <para>[110925] rsync-2.6.4-3 -> [115264] rsync-2.6.6-2 </para>
    <para>[104630] rusers-0.17-43 -> [117620] rusers-0.17-45 </para>
    <para>[109533] samba-3.0.14a-2 -> [117971] samba-3.0.20-2 </para>
    <para>- sash-3.7-6 </para>
    <para>[110268] sendmail-8.13.4-2 -> [118253] sendmail-8.13.5-1
    </para>
    <para>[111123] setup-2.5.44-1 -> [117568] setup-2.5.47-1.1 </para>
    <para>[111408] shadow-utils-4.0.7-9 -> [117343]
      shadow-utils-4.0.12-2 </para>
    <para>[106465] slang-1.4.9-17 -> [117492] slang-1.4.9-19 </para>
    <para>[108441] slocate-2.7-22 -> [118067] slocate-2.7-27 </para>
    <para>[105316] slrn-0.9.8.1-4 -> [114996] slrn-0.9.8.1-5 </para>
    <para>[110665] squid-2.5.STABLE9-7 -> [117506]
      squid-2.5.STABLE10-4 </para>
    <para>[106754] strace-4.5.11-1 -> [115667] strace-4.5.13-1 </para>
    <para>[108145] sudo-1.6.8p8-1 -> [118285] sudo-1.6.8p9-4 </para>
    <para>[93654] switchdesk-4.0.6-3 -> [114432] switchdesk-4.0.7-1
    </para>
    <para>[111041] sysklogd-1.4.1-30 -> [117045] sysklogd-1.4.1-33
    </para>
    <para>[112528] syslinux-3.08-2 -> [117044] syslinux-3.10-2 </para>
    <para>[110362] sysreport-1.4.1-2 -> [112702] sysreport-1.4.1-4
    </para>
    <para>[105297] sysstat-5.0.5-9.fc -> [116738] sysstat-5.0.5-11.fc
    </para>
    <para>[108370] tar-1.15.1-5 -> [117554] tar-1.15.1-10 </para>
    <para>[109655] tcpdump-3.8.2-12 -> [116178] tcpdump-3.9.3-3
    </para>
    <para>[106994] tcsh-6.14-1 -> [115897] tcsh-6.14-5 </para>
    <para>[106284] termcap-5.4-4 -> [118201] termcap-5.4-7 </para>
    <para>[110274] tetex-3.0-4 -> [116781] tetex-3.0-6 </para>
    <para>[106019] texinfo-4.8-4 -> [112242] texinfo-4.8-6 </para>
    <para>[109641] jwhois-3.2.2-14 -> [115889] jwhois-3.2.3-2 </para>
    <para>[110348] elfutils-0.108-1 -> [117517] elfutils-0.115-1
    </para>
    <para>[105286] expect-5.43.0-1 -> [111871] expect-5.43.0-2 </para>
    <para>[105014] traceroute-1.4a12-26 -> [116290]
      traceroute-1.4a12-27 </para>
    <para>[108240] subversion-1.1.4-3 -> [117737] subversion-1.2.3-3
    </para>
    <para>- schedutils-1.4.0-4 </para>
    <para>[106314] umb-scheme-3.2-38 -> [117616] umb-scheme-3.2-39
    </para>
    <para>[104847] units-1.80-12 -> [114388] units-1.85-1 </para>
    <para>[107560] quagga-0.98.3-2 -> [117222] quagga-0.98.5-2 </para>
    <para>[105298] unzip-5.51-10 -> [115669] unzip-5.51-12 </para>
    <para>[109681] util-linux-2.12p-9.3 -> [117509]
      util-linux-2.13-0.3.pre2 </para>
    <para>[108550] uucp-1.07-9 -> [114161] uucp-1.07-11 </para>
    <para>[109140] vim-6.3.071-3 -> [117700] vim-6.3.086-5 </para>
    <para>[108347] vixie-cron-4.1-33 -> [113831] vixie-cron-4.1-36.FC5
    </para>
    <para>[106439] gtksourceview-1.2.0-1 -> [117747]
      gtksourceview-1.4.1-1 </para>
    <para>[109142] vnc-4.1.1-10 -> [117547] vnc-4.1.1-17 </para>
    <para>- w3c-libwww-5.4.0-13 </para>
    <para>[104493] wget-1.9.1-22 -> [117731] wget-1.10.1-7 </para>
    <para>[100923] wireless-tools-28-0.pre4.3 -> [117952]
      wireless-tools-28-0.pre9.5 </para>
    <para>[104447] neon-0.24.7-6 -> [118267] neon-0.24.7-7 </para>
    <para>[108529] desktop-printing-0.18-10 -> [116635]
      desktop-printing-0.19-2 </para>
    <para>[109757] libselinux-1.23.10-2 -> [118218] libselinux-1.26-6
    </para>
    <para>[110975] xfig-3.2.4-11 -> [114406] xfig-3.2.4-13 </para>
    <para>[106604] ttmkfdir-3.0.9-16 -> [115679] ttmkfdir-3.0.9-17
    </para>
    <para>[106293] ckermit-8.0.211-1 -> [117400] ckermit-8.0.211-3
    </para>
    <para>[111493] coreutils-5.2.1-48 -> [117826] coreutils-5.2.1-55
    </para>
    <para>[109668] gstreamer-0.8.10-1 -> [117857] gstreamer-0.8.11-1
    </para>
    <para>[110247] gstreamer-plugins-0.8.8-6 -> [117858]
      gstreamer-plugins-0.8.11-1 </para>
    <para>[108260] gnome-icon-theme-2.10.1-4 -> [117725]
      gnome-icon-theme-2.12.0-1 </para>
    <para>[111290] xpdf-3.00-19 -> [116734] xpdf-3.01-1 </para>
    <para>[104699] xsane-0.95-3 -> [112799] xsane-0.95-4 </para>
    <para>[110438] xscreensaver-4.21-4 -> [118219]
      xscreensaver-4.22-16 </para>
    <para>[106575] nautilus-cd-burner-2.10.0-2 -> [117669]
      nautilus-cd-burner-2.12.0-1 </para>
    <para>- hpoj-0.91-13 </para>
    <para>[108081] ypserv-2.13-6 -> [114545] ypserv-2.13-7 </para>
    <para>[108065] zlib-1.2.2.2-3 -> [117021] zlib-1.2.3-1 </para>
    <para>[110759] gthumb-2.6.5-1 -> [117742] gthumb-2.6.7-1 </para>
    <para>[110698] alsa-utils-1.0.9rc2-2 -> [116939]
      alsa-utils-1.0.9rf-5 </para>
    <para>[111418] libgnomeprint22-2.10.3-1 -> [117675]
      libgnomeprint22-2.12.0-1 </para>
    <para>[106542] libgnomeprintui22-2.10.1-1 -> [117676]
      libgnomeprintui22-2.12.0-1 </para>
    <para>[106076] rhythmbox-0.8.8-2 -> [117443]
      rhythmbox-0.9.0.cvs20050902-1 </para>
    <para>[104518] libgsf-1.11.1-2 -> [118324] libgsf-1.12.3-1 </para>
    <para>[104645] libmng-1.0.9-1 -> [112902] libmng-1.0.9-2 </para>
    <para>[104492] bluez-libs-2.15-1 -> [117512] bluez-libs-2.20-1
    </para>
    <para>[109626] bluez-utils-2.15-7 -> [117513] bluez-utils-2.20-1
    </para>
    <para>[109284] gnome-themes-2.10.1-2 -> [117637]
      gnome-themes-2.12.0-1 </para>
    <para>[106333] lv-4.51-5 -> [113778] lv-4.51-6 </para>
    <para>[106337] nkf-2.04-5 -> [113596] nkf-2.05-1 </para>
    <para>- nvi-m17n-1.79-20040401.23 </para>
    <para>[108025] ruby-1.8.2-7 -> [118404] ruby-1.8.3-1 </para>
    <para>[109083] stunnel-4.08-2 -> [113854] stunnel-4.11-1 </para>
    <para>[108440] 4Suite-1.0-8.b1 -> [112368] 4Suite-1.0-9.b1 </para>
    <para>[106235] nss_db-2.2-31 -> [117271] nss_db-2.2-33 </para>
    <para>[111212] eclipse-3.1.0_fc-0.M6.22 -> [115167]
      eclipse-3.1.0_fc-12 </para>
    <para>[111394] dbus-0.33-3 -> [117773] dbus-0.50-1 </para>
    <para>[106803] a2ps-4.13b-46 -> [111842] a2ps-4.13b-47 </para>
    <para>[109643] libuser-0.53.7-1 -> [117997] libuser-0.54-1 </para>
    <para>[109886] gtk-doc-1.3-2 -> [113533] gtk-doc-1.4-1 </para>
    <para>[109144] perl-DBD-MySQL-2.9007-1 -> [117217]
      perl-DBD-MySQL-3.0002-1 </para>
    <para>[111122] perl-DBD-Pg-1.41-2 -> [113244] perl-DBD-Pg-1.43-1
    </para>
    <para>[105244] kdbg-1.2.10-2 -> [114272] kdbg-2.0.0-1 </para>
    <para>[106810] kdepim-3.4.0-4 -> [117234] kdepim-3.4.2-3 </para>
    <para>[106772] xdelta-1.1.3-16 -> [117821] xdelta-1.1.3-17 </para>
    <para>[107253] pkgconfig-0.15.0-6 -> [116158] pkgconfig-0.18.1-4
    </para>
    <para>[108628] kdesdk-3.4.0-3 -> [116008] kdesdk-3.4.2-1 </para>
    <para>[106503] kde-i18n-3.4.0-1 -> [116284] kde-i18n-3.4.2-1
    </para>
    <para>[111302] hotplug-2004_09_23-7 -> [118092]
      hotplug-2004_09_23-10 </para>
    <para>[112023] fedora-release-4-2 -> [113067]
      fedora-release-4-rawhide </para>
    <para>[108436] xterm-200-6 -> [118082] xterm-200-9 </para>
    <para>[106145] ppc64-utils-0.7-9 -> [118408] ppc64-utils-0.7-11
    </para>
    <para>[104559] htdig-3.2.0b6-5 -> [117484] htdig-3.2.0b6-6 </para>
    <para>- libgal2-2.4.2-4 </para>
    <para>[110442] gaim-1.3.0-1.fc4 -> [118167] gaim-1.5.0-5.fc5
    </para>
    <para>[108062] aspell-en-0.51-12 -> [114279] aspell-en-6.0-1
    </para>
    <para>[108357] freeradius-1.0.2-2 -> [114495] freeradius-1.0.4-2
    </para>
    <para>[110988] devhelp-0.10-1 -> [116721] devhelp-0.10-5 </para>
    <para>[106525] kdebindings-3.4.0-1 -> [116107] kdebindings-3.4.2-1
    </para>
    <para>[110439] nautilus-2.10.0-4 -> [117668] nautilus-2.12.0-1
    </para>
    <para>[111391] boost-1.32.0-6 -> [116965] boost-1.33.0-3 </para>
    <para>[104523] nano-1.3.5-0.20050302 -> [117495] nano-1.3.8-1
    </para>
    <para>[110577] epiphany-1.6.1-3 -> [117510] epiphany-1.8.0-1
    </para>
    <para>[111496] yum-2.3.2-7 -> [118230] yum-2.4.0-3 </para>
    <para>[104625] GConf-1.0.9-16 -> [115534] GConf-1.0.9-17 </para>
    <para>[105438] g-wrap-1.3.4-8 -> [113627] g-wrap-1.3.4-9 </para>
    <para>[105029] pcre-5.0-4 -> [117019] pcre-6.3-1 </para>
    <para>[103293] pychecker-0.8.14-3 -> [117907] pychecker-0.8.16-1
    </para>
    <para>[107295] gnome-bluetooth-0.5.1-12 -> [116637]
      gnome-bluetooth-0.5.1-14 </para>
    <para>[110227] setarch-1.7-3 -> [113328] setarch-1.8-1 </para>
    <para>[107662] kdeaddons-3.4.0-2 -> [116097] kdeaddons-3.4.2-1
    </para>
    <para>[105264] MyODBC-2.50.39-24 -> [116340] MyODBC-2.50.39-25
    </para>
    <para>[108719] nmap-3.81-3 -> [118008] nmap-3.93-1 </para>
    <para>[107878] glib2-2.6.4-1 -> [116932] glib2-2.8.1-1 </para>
    <para>[106280] m2crypto-0.13-2 -> [117174] m2crypto-0.15-1 </para>
    <para>[105135] pango-1.8.1-2 -> [116700] pango-1.10.0-1 </para>
    <para>[106004] atk-1.9.1-1 -> [117631] atk-1.10.3-1 </para>
    <para>[110350] gtk2-2.6.7-4 -> [117200] gtk2-2.8.3-1 </para>
    <para>[110963] logwatch-6.0.1-2 -> [118256] logwatch-6.1.2-4
    </para>
    <para>[107440] libxml2-2.6.19-1 -> [117989] libxml2-2.6.22-1
    </para>
    <para>[107238] gnome-mag-0.12.0-2 -> [116495] gnome-mag-0.12.1-2
    </para>
    <para>[109656] tzdata-2005i-2 -> [117537] tzdata-2005m-2 </para>
    <para>[105136] ddd-3.3.10-2 -> [112263] ddd-3.3.11-1 </para>
    <para>[111516] ethereal-0.10.11-2 -> [118418] ethereal-0.10.12-7
    </para>
    <para>[105946] mrtg-2.11.1-3 -> [117906] mrtg-2.12.2-2 </para>
    <para>[109779] curl-7.13.1-3 -> [112559] curl-7.14.0-1 </para>
    <para>[110585] mozilla-1.7.8-2 -> [118143] mozilla-1.7.11-5
    </para>
    <para>[104474] cdrdao-1.1.9-9 -> [114286] cdrdao-1.2.0-1 </para>
    <para>[111152] policycoreutils-1.23.10-2 -> [118399]
      policycoreutils-1.27.1-1 </para>
    <para>[108677] selinux-doc-1.19.5-1 -> [118233] selinux-doc-1.22-1
    </para>
    <para>[108338] checkpolicy-1.23.1-1 -> [118421]
      checkpolicy-1.27.2-1 </para>
    <para>[107547] sound-juicer-2.10.1-1 -> [116671]
      sound-juicer-2.11.91-1 </para>
    <para>[104852] mod_auth_mysql-2.6.1-4 -> [112597]
      mod_auth_mysql-2.9.0-1 </para>
    <para>[106515] kdeartwork-3.4.0-1 -> [116101] kdeartwork-3.4.2-1
    </para>
    <para>[111390] setools-2.1.0-5 -> [118333] setools-2.1.2-1 </para>
    <para>[111060] grub-0.95-13 -> [114871] grub-0.95-15 </para>
    <para>[110652] openssh-4.0p1-3 -> [117588] openssh-4.2p1-1 </para>
    <para>[108233] gnucash-1.8.11-3 -> [117839] gnucash-1.8.11-4
    </para>
    <para>[108697] MySQL-python-1.2.0-1 -> [115666]
      MySQL-python-1.2.0-2 </para>
    <para>[106774] PyQt-3.14.1-1 ->
      [117928] PyQt-3.15-1 </para>
    <para>[106773] sip-4.2.1-1 -> [117925] sip-4.3.1-1 </para>
    <para>[109146] jpilot-0.99.8-0.pre8.4 -> [116645]
      jpilot-0.99.8-0.pre10.2 </para>
    <para>[108932] lftp-3.1.3-1 -> [117026] lftp-3.3.0-1 </para>
    <para>[107870] cdrtools-2.01.1-9 -> [117294] cdrtools-2.01.1-10
    </para>
    <para>- apel-10.6-6 </para>
    <para>[107986] mysql-4.1.11-2 -> [116941] mysql-4.1.12-3 </para>
    <para>[108427] tmpwatch-2.9.3-1 -> [112807] tmpwatch-2.9.4-1
    </para>
    <para>[107682] kdenetwork-3.4.0-3 -> [116293] kdenetwork-3.4.2-1
    </para>
    <para>[111395] fedora-logos-1.1.31-1 -> [117762]
      fedora-logos-1.1.31-2 </para>
    <para>[100527] junit-3.8.1-3jpp_4fc -> [112932]
      junit-3.8.1-3jpp_5fc </para>
    <para>[105492] xmlsec1-1.2.7-4 -> [118326] xmlsec1-1.2.9-1 </para>
    <para>[104606] openCryptoki-2.1.5-9 -> [117535]
      openCryptoki-2.1.5-10 </para>
    <para>[110363] system-config-bind-4.0.0-16_FC4 -> [116458]
      system-config-bind-4.0.0-30_FC5 </para>
    <para>[110056] system-config-date-1.7.18-1 -> [115786]
      system-config-date-1.7.99.0-1 </para>
    <para>[109174] system-config-keyboard-1.2.6-2 -> [118188]
      system-config-keyboard-1.2.6-3 </para>
    <para>[109127] system-config-kickstart-2.5.22-2 -> [118045]
      system-config-kickstart-2.5.24-1 </para>
    <para>- system-config-mouse-1.2.11-1 </para>
    <para>[108705] system-config-netboot-0.1.14-1 -> [116895]
      system-config-netboot-0.1.30-1_FC5 </para>
    <para>[110270] system-config-nfs-1.3.10-1 -> [113615]
      system-config-nfs-1.3.11-1 </para>
    <para>[110775] system-config-printer-0.6.131-1 -> [117714]
      system-config-printer-0.6.142-1 </para>
    <para>[110889] system-config-securitylevel-1.5.8-1 -> [116959]
      system-config-securitylevel-1.6.4-1 </para>
    <para>[110271] system-config-services-0.8.25-1 -> [116537]
      system-config-services-0.8.26-1 </para>
    <para>[111388] system-config-soundcard-1.2.11-5 -> [116656]
      system-config-soundcard-1.2.12-5 </para>
    <para>[111429] system-config-display-1.0.29-1 -> [117812]
      system-config-display-1.0.31-1 </para>
    <para>[111664] alsa-lib-1.0.9rc4-2 -> [114503] alsa-lib-1.0.9rf-3
    </para>
    <para>[105652] tcl-8.4.9-3 -> [113371] tcl-8.4.11-1 </para>
    <para>[105658] tk-8.4.9-3 -> [113372] tk-8.4.11-1 </para>
    <para>[109302] lvm2-2.01.08-2.1 -> [118142] lvm2-2.01.14-2 </para>
    <para>[110929] device-mapper-1.01.02-1.0 -> [115634]
      device-mapper-1.01.04-1.0 </para>
    <para>[108262] libgnomecups-0.2.0-2 -> [117671]
      libgnomecups-0.2.1-1 </para>
    <para>[109132] tvtime-0.9.15-7 -> [117915] tvtime-1.0.1-1 </para>
    <para>- hpijs-1.7.1-3 </para>
    <para>[111138] shared-mime-info-0.16-3 -> [112690]
      shared-mime-info-0.16-4 </para>
    <para>[110914] evolution-data-server-1.2.2-3 -> [118144]
      evolution-data-server-1.4.0-2 </para>
    <para>[106495] gnome-keyring-0.4.2-1 -> [117659]
      gnome-keyring-0.4.4-1 </para>
    <para>[111218] udev-058-1 -> [118405] udev-069-4 </para>
    <para>- pcmcia-cs-3.2.8-4.12 </para>
    <para>- iiimf-le-xcin-0.1.10-1 </para>
    <para>[109118] gnome-netstatus-2.10.0-4 -> [116639]
      gnome-netstatus-2.11.90-2 </para>
    <para>[110265] perl-XML-NamespaceSupport-1.08-7 ->
      [117865] perl-XML-NamespaceSupport-1.09-1 </para>
    <para>[107102] memtest86+-1.55.1-1 -> [113262] memtest86+-1.60-1
    </para>
    <para>[100526] antlr-2.7.4-2jpp_1fc -> [112867]
      antlr-2.7.4-2jpp_2fc </para>
    <para>[111283] jakarta-commons-beanutils-1.7.0-1jpp_4fc ->
      [114381] jakarta-commons-beanutils-1.7.0-2jpp_2fc </para>
    <para>[111285] jakarta-commons-collections-3.1-1jpp_4fc ->
      [114380] jakarta-commons-collections-3.1-2jpp_2fc </para>
    <para>[101451] jakarta-commons-dbcp-1.2.1-3jpp_1fc -> [112880]
      jakarta-commons-dbcp-1.2.1-3jpp_2fc </para>
    <para>[111286] jakarta-commons-digester-1.6-2jpp_4fc -> [114394]
      jakarta-commons-digester-1.6-2jpp_6fc </para>
    <para>[111288] jakarta-commons-logging-1.0.4-2jpp_4fc -> [114180]
      jakarta-commons-logging-1.0.4-2jpp_6fc </para>
    <para>[111289] jakarta-commons-modeler-1.1-3jpp_4fc -> [114487]
      jakarta-commons-modeler-1.1-4jpp_2fc </para>
    <para>[101447] jakarta-commons-pool-1.2-2jpp_1fc -> [112885]
      jakarta-commons-pool-1.2-2jpp_2fc </para>
    <para>[101435] jakarta-commons-validator-1.1.3-1jpp_1fc ->
      [112887] jakarta-commons-validator-1.1.3-1jpp_2fc </para>
    <para>[100530] jdepend-2.6-2jpp_3fc -> [112928]
      jdepend-2.6-2jpp_4fc </para>
    <para>[111423] log4j-1.2.8-7jpp_4fc -> [112933]
      log4j-1.2.8-7jpp_5fc </para>
    <para>[96312] oro-2.0.8-1jpp_2fc -> [113162] oro-2.0.8-1jpp_3fc
    </para>
    <para>[109898] regexp-1.3-1jpp_5fc -> [114182] regexp-1.3-2jpp_3fc
    </para>
    <para>[100606] xalan-j2-2.6.0-2jpp_1fc -> [114410]
      xalan-j2-2.6.0-3jpp_3fc </para>
    <para>[109899] xerces-j2-2.6.2-4jpp_5fc -> [114312]
      xerces-j2-2.6.2-5jpp_2fc </para>
    <para>[109900] xml-commons-1.0-0.b2.6jpp_12fc -> [114196]
      xml-commons-1.0-0.b2.7jpp_3fc </para>
    <para>[96303] xml-commons-resolver-1.1-1jpp_4fc -> [113163]
      xml-commons-resolver-1.1-1jpp_5fc </para>
    <para>[101437] jakarta-commons-lang-2.0-2jpp_1fc -> [112883]
      jakarta-commons-lang-2.0-2jpp_2fc </para>
    <para>[96300] java_cup-0.10-0.k.1jpp_2fc -> [114395]
      java_cup-0.10-0.k.1jpp_5fc </para>
    <para>[100540] avalon-logkit-1.2-2jpp_4fc -> [113428]
      avalon-logkit-1.2-3jpp_1fc </para>
    <para>[101462] cryptix-3.2.0-4jpp_1fc -> [112869]
      cryptix-3.2.0-4jpp_2fc </para>
    <para>[101463] cryptix-asn1-20011119-4jpp_1fc -> [112873]
      cryptix-asn1-20011119-4jpp_2fc </para>
    <para>[101464] gnu.getopt-1.0.9-4jpp_1fc -> [112875]
      gnu.getopt-1.0.9-4jpp_2fc </para>
    <para>[110589] xorg-x11-6.8.2-31 -> [115364] xorg-x11-6.8.2-45
    </para>
    <para>[108218] aspell-is-0.51.1-1 -> [114361] aspell-is-0.51.1-2
    </para>
    <para>[106231] pyparted-1.6.9-3 -> [117327] pyparted-1.6.9-4
    </para>
    <para>[110354] mod_auth_kerb-5.0-6 -> [118413] mod_auth_kerb-5.0-7
    </para>
    <para>[106186] iprutils-2.0.13.7-2 -> [115548] iprutils-2.0.15.3-1
    </para>
    <para>[110365] tomcat5-5.0.30-5jpp_6fc -> [118323]
      tomcat5-5.0.30-8jpp_3fc </para>
    <para>[110776] xchat-2.4.3-3 -> [118268] xchat-2.4.5-1 </para>
    <para>[111287] jakarta-commons-el-1.0-2jpp_3fc -> [114396]
      jakarta-commons-el-1.0-4jpp_2fc </para>
    <para>- GFS-6.1-0.pre22.6 </para>
    <para>[107882] k3b-0.11.23-3 -> [114095] k3b-0.12.2-1 </para>
    <para>[111251] hal-0.5.2-2 -> [117285] hal-0.5.4-3 </para>
    <para>[107343] gnome-volume-manager-1.3.1-1 -> [117761]
      gnome-volume-manager-1.5.1-1 </para>
    <para>[106242] pam_passwdqc-0.7.6-1 -> [118214]
      pam_passwdqc-1.0.2-1 </para>
    <para>[106603] libidn-0.5.15-1 -> [118283] libidn-0.5.19-1 </para>
    <para>[110913] evolution-connector-2.2.2-5 -> [118165]
      evolution-connector-2.4.0-2 </para>
    <para>[111158] selinux-policy-targeted-1.23.16-6 -> [118397]
      selinux-policy-targeted-1.27.1-4 </para>
    <para>[111157] selinux-policy-strict-1.23.16-6 -> [118396]
      selinux-policy-strict-1.27.1-4 </para>
    <para>- ecj-3.1-0.M4.9 </para>
    <para>[104920] diskdumputils-1.0.1-6 -> [116910]
      diskdumputils-1.1.9-2 </para>
    <para>[108918] module-init-tools-3.1-3 -> [117811]
      module-init-tools-3.2-0.pre7.3 </para>
    <para>[104418] numactl-0.6.4-1.18 -> [113672] numactl-0.6.4-1.23
    </para>
    <para>[104522] libwmf-0.2.8.3-8 -> [115159] libwmf-0.2.8.4-1
    </para>
    <para>[107934] authd-1.4.3-4.devel -> [113028] authd-1.4.3-5.devel
    </para>
    <para>[112018] gamin-0.1.0-1.1 -> [118342] gamin-0.1.6-2 </para>
    <para>[111127] vino-2.10.0-4 -> [117670] vino-2.12.0-1 </para>
    <para>[109620] HelixPlayer-1.0.4-4 -> [116508]
      HelixPlayer-1.0.5-2 </para>
    <para>[110936] totem-1.0.2-1 -> [116504] totem-1.1.4-1 </para>
    <para>- gnbd-kernel-2.6.11.2-20050420.133124.FC4.35 </para>
    <para>[108039] aspell-de-0.50-10 -> [114277] aspell-de-0.50-11
    </para>
    <para>[109112] eclipse-changelog-2.0.1_fc-21 -> [114192]
      eclipse-changelog-2.0.1_fc-22 </para>
    <para>[111405] eclipse-cdt-3.0.0_fc-0.M6.7 -> [116981]
      eclipse-cdt-3.0.0_fc-1 </para>
    <para>- iiimf-le-chinput-0.3-19 </para>
    <para>[106138] synaptics-0.14.0-2 -> [115769] synaptics-0.14.3-3
    </para>
    <para>[110766] libsepol-1.5.9-2 -> [118331] libsepol-1.9.4-1
    </para>
    <para>[108031] aspell-af-0.50-2 -> [114179] aspell-af-0.50-4
    </para>
    <para>[103800] aspell-bg-0.50-9 -> [114176] aspell-bg-0.50-11
    </para>
    <para>[108032] aspell-br-0.50-2 -> [114181] aspell-br-0.50-4
    </para>
    <para>[108037] aspell-cy-0.50-2 -> [114274] aspell-cy-0.50-4
    </para>
    <para>[108040] aspell-el-0.50-2 -> [114278] aspell-el-0.50-4
    </para>
    <para>[108043] aspell-fo-0.51-2 -> [114281] aspell-fo-0.51-4
    </para>
    <para>[108045] aspell-ga-0.50-2 -> [114288] aspell-ga-0.50-4
    </para>
    <para>[108047] aspell-gd-0.50-2 -> [114357] aspell-gd-0.50-4
    </para>
    <para>[108048] aspell-gl-0.50-2 -> [114358] aspell-gl-0.50-4
    </para>
    <para>[108049] aspell-hr-0.51-2 -> [114359] aspell-hr-0.51-4
    </para>
    <para>[108050] aspell-id-0.50.1-2 -> [114360] aspell-id-0.50.1-4
    </para>
    <para>[105301] busybox-1.00-4 -> [111857] busybox-1.00-5 </para>
    <para>[104570] sysfsutils-1.2.0-4 -> [113812] sysfsutils-1.3.0-1
    </para>
    <para>- rgmanager-1.9.31-3 </para>
    <para>[109173] openswan-2.3.1-2 -> [118022] openswan-2.4.0-1
    </para>
    <para>[110687] NetworkManager-0.4-15.cvs20050404
      -> [118005] NetworkManager-0.4.1-2.cvs20050912
    </para>
    <para>[112106] java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh ->
      [118416] java-1.4.2-gcj-compat-1.4.2.0-40jpp_51rh </para>
    <para>[106674] gnome-keyring-manager-0.0.4-3 -> [117662]
      gnome-keyring-manager-2.12.0-1 </para>
    <para>[105646] evolution-webcal-2.2.0-1 -> [118166]
      evolution-webcal-2.4.0.1-2 </para>
    <para>[106722] krb5-auth-dialog-0.2-5 -> [116572]
      krb5-auth-dialog-0.2-6 </para>
    <para>[107396] dhcpv6-0.10-13 -> [116466] dhcpv6-0.10-14 </para>
    <para>[106006] dasher-3.2.15-1 -> [117634] dasher-3.2.18-1 </para>
    <para>[111497] firefox-1.0.4-4 -> [118182] firefox-1.5-0.5.0.beta1
    </para>
    <para>[110588] thunderbird-1.0.2-6 -> [116773] thunderbird-1.0.6-5
    </para>
    <para>- valgrind-callgrind-0.9.11-1 </para>
    <para>[106256] pam_ccreds-1-6 -> [112255] pam_ccreds-1-7 </para>
    <para>[100966] createrepo-0.4.2-2 -> [114098] createrepo-0.4.3-1
    </para>
    <para>[111205] audit-0.8.2-1 -> [116925] audit-1.0.3-1 </para>
    <para>[109751] kdewebdev-3.4.0-3 -> [116306] kdewebdev-3.4.2-1
    </para>
    <para>[98989] slib-3a1-2 -> [117769] slib-3a1-5 </para>
    <para>[105026] webalizer-2.01_10-28 -> [118412]
      webalizer-2.01_10-29 </para>
    <para>[108536] ipv6calc-0.48-5 -> [118194] ipv6calc-0.50-1 </para>
    <para>[100524] classpathx-mail-1.0-3jpp_1fc -> [111780]
      classpathx-mail-1.0-4jpp_2fc </para>
    <para>[111648] gnu-crypto-2.0.1-1jpp_5fc -> [114171]
      gnu-crypto-2.0.1-1jpp_7fc </para>
    <para>[107249] OpenIPMI-1.4.11-5 -> [117704] OpenIPMI-1.4.14-9
    </para>
    <para>[100864] zsh-4.2.1-2 -> [113141] zsh-4.2.5-1 </para>
    <para>[104688] sane-backends-1.0.15-9 -> [116782]
      sane-backends-1.0.16-1 </para>
    <para>- lvm2-cluster-2.01.09-3.0 </para>
    <para>- struts11-1.1-1jpp_7fc </para>
    <para>[107376] gkrellm-2.2.4-4 -> [117540] gkrellm-2.2.7-3 </para>
    <para>[108839] cpufreq-utils-0.2-1.1.14 -> [115418]
      cpufreq-utils-0.3-1.1.16 </para>
    <para>[108362] dmidecode-2.6-1.14 -> [117909] dmidecode-2.7-1.15
    </para>
    <para>[109300] hardlink-1.0-1.13 -> [117099] hardlink-1.0-1.14
    </para>
    <para>[111037] readahead-1.1-1.14 -> [115793] readahead-1.1-1.17
    </para>
    <para>[104427] smartmontools-5.33-1.5 -> [115762]
      smartmontools-5.33-1.7 </para>
    <para>[108364] x86info-1.13-1.10 -> [117440] x86info-1.15-1.13
    </para>
    <para>- python-twisted-1.3.0-4 </para>
    <para>[111505] evince-0.3.1-1 -> [118030] evince-0.4.0-2 </para>
    <para>[109178] gnome-doc-utils-0.2.0-2 -> [117722]
      gnome-doc-utils-0.4.0-1 </para>
    <para>[108845] gnome-menus-2.10.1-3 -> [117531]
      gnome-menus-2.12.0-1 </para>
    <para>[107103] gnome-python2-extras-2.10.0-2.1 -> [116816]
      gnome-python2-extras-2.11.4-9 </para>
    <para>[109933] gjdoc-0.7.4-5 -> [114163] gjdoc-0.7.5-4 </para>
    <para>[109753] kdelibs-3.4.0-6 -> [115465] kdelibs-3.4.2-1 </para>
    <para>[106258] kdeaccessibility-3.4.0-1 -> [116016]
      kdeaccessibility-3.4.2-1 </para>
    <para>[108603] fonts-korean-1.0.11-4 -> [116512]
      fonts-korean-1.0.11-6 </para>
    <para>[108601] fonts-japanese-0.20050222-3 -> [116488]
      fonts-japanese-0.20050222-7 </para>
    <para>[108604] fonts-chinese-2.15-2 -> [117399]
      fonts-chinese-3.00.pre2-1 </para>
    <para>[111507] poppler-0.3.2-1 -> [117476] poppler-0.4.2-1 </para>
    <para>[111030] eclipse-bugzilla-0.1.0_fc-16 -> [114650]
      eclipse-bugzilla-0.1.1_fc-5 </para>
    <para>[109095] eclipse-pydev-0.9.3_fc-7 -> [115587]
      eclipse-pydev-0.9.3_fc-11 </para>
    <para>[108005] sqlite-3.1.2-3 -> [117898] sqlite-3.2.5-1 </para>
    <para>[105636] python-urlgrabber-2.9.6-1 -> [118139]
      python-urlgrabber-2.9.6-3 </para>
    <para>[107161] cryptsetup-luks-1.0-1 -> [116857]
      cryptsetup-luks-1.0.1-2 </para>
    <para>[108817] jsch-0.1.18-1jpp_1fc -> [114185]
      jsch-0.1.18-1jpp_2fc </para>
    <para>[109747] latex2html-2002.2.1-3 -> [112874]
      latex2html-2002.2.1-4 </para>
    <para>[110960] openssl-0.9.7f-7 -> [116949] openssl-0.9.7f-9
    </para>
    <para>- iiimf-12.2-4 </para>
    <para>[108246] kdevelop-3.2.0-2 -> [116301] kdevelop-3.2.2-1
    </para>
    <para>- Canna-3.7p3-13 </para>
    <para>- VFlib2-2.25.6-28 </para>
    <para>[108287] perl-Archive-Zip-1.14-1 -> [117218]
      perl-Archive-Zip-1.16-1 </para>
    <para>[108275] pm-utils-0.01-1 -> [116385] pm-utils-0.04-1 </para>
    <para>[109632] foomatic-3.0.2-19 -> [118014] foomatic-3.0.2-28
    </para>
    <para>[108982] perl-DateManip-5.42a-4 -> [117863]
      perl-DateManip-5.44-1 </para>
    <para>- perl-libxml-enno-1.02-31 </para>
    <para>[104653] s390utils-1.3.2-4 -> [112864] s390utils-1.3.2-5
    </para>
    <para>[107373] m4-1.4.3-1 -> [118239] m4-1.4.3-2 </para>
    <para>[110355] ORBit2-2.12.1-3 -> [117666] ORBit2-2.12.4-1 </para>
    <para>[110242] GConf2-2.10.0-4 -> [117717] GConf2-2.12.0-1 </para>
    <para>[106017] libgnomecanvas-2.10.0-1 -> [117642]
      libgnomecanvas-2.12.0-1 </para>
    <para>[102603] libbonobo-2.8.1-1 -> [117820] libbonobo-2.10.1-2
    </para>
    <para>[109591] gnome-vfs2-2.10.0-5 -> [117664] gnome-vfs2-2.12.0-1
    </para>
    <para>[109285] libgnome-2.10.0-3 -> [117751] libgnome-2.12.0-1
    </para>
    <para>[109171] libbonoboui-2.8.1-4 -> [117749]
      libbonoboui-2.10.1-1 </para>
    <para>[104650] librsvg2-2.9.5-2 -> [117304] librsvg2-2.11.1-1
    </para>
    <para>[107485] eel2-2.10.0-2 -> [117651] eel2-2.12.0-1 </para>
    <para>[106316] tn5250-0.16.5-5 -> [113112] tn5250-0.16.5-6 </para>
    <para>[106143] yaboot-1.3.12-9 -> [118141] yaboot-1.3.13-0.16
    </para>
    <para>[107969] libgnomeui-2.10.0-1 -> [117980] libgnomeui-2.12.0-2
    </para>
    <para>[104629] libglade2-2.5.1-2 -> [116545] libglade2-2.5.1-3
    </para>
    <para>[105166] libIDL-0.8.5-2 -> [117667] libIDL-0.8.6-1 </para>
    <para>[110521] usermode-1.80-1 -> [116503] usermode-1.81-1 </para>
    <para>[102961] docbook-style-xsl-1.68.1-1 -> [116354]
      docbook-style-xsl-1.69.1-1 </para>
    <para>[104584] intltool-0.33-2 -> [115810] intltool-0.34.1-1
    </para>
    <para>[110237] evolution-2.2.2-5 -> [118148] evolution-2.4.0-2
    </para>
    <para>[104652] xmltex-20020625-5 -> [118338] xmltex-20020625-6
    </para>
    <para>[105333] pygtk2-2.6.0-2 -> [117772] pygtk2-2.8.0-1 </para>
    <para>[105908] gnome-python2-2.10.0-1 -> [116511]
      gnome-python2-2.11.3-2 </para>
    <para>[104649] libpng10-1.0.18-2 -> [115463] libpng10-1.0.18-3
    </para>
    <para>[96234] aspell-pt-0.50-9 -> [114369] aspell-pt-0.50-10
    </para>
    <para>[106303] stardict-2.4.4-3 -> [118242] stardict-2.4.5-1
    </para>
    <para>[108452] glibc-kernheaders-2.4-9.1.94 -> [111898]
      glibc-kernheaders-2.4-9.1.95 </para>
    <para>[105250] wordtrans-1.1pre13-10 -> [115775]
      wordtrans-1.1pre13-11 </para>
    <para>[104417] microcode_ctl-1.11-1.21 -> [118068]
      microcode_ctl-1.12-1.23 </para>
    <para>[109638] gnome-pilot-2.0.13-2 -> [116547]
      gnome-pilot-2.0.13-7.fc5 </para>
    <para>[106005] at-spi-1.6.3-1 -> [117632] at-spi-1.6.6-1 </para>
    <para>[110915] gail-1.8.3-2 -> [117635] gail-1.8.5-1 </para>
    <para>[106768] vsftpd-2.0.3-1 -> [117823] vsftpd-2.0.3-10 </para>
    <para>[108150] authconfig-4.6.12-1 -> [117485] authconfig-5.0.1-1
    </para>
    <para>[104665] linuxdoc-tools-0.9.21-5 -> [113333]
      linuxdoc-tools-0.9.21-6 </para>
    <para>[111809] gphoto2-2.1.5-10 -> [115052] gphoto2-2.1.6-2
    </para>
    <para>[104555] xmlto-0.0.18-6 -> [116003] xmlto-0.0.18-9 </para>
    <para>- perl-Time-HiRes-1.65-1 </para>
    <para>[108948] db4-4.3.27-3 -> [118387] db4-4.3.28-2 </para>
    <para>[107533] openmotif-2.2.3-10 -> [117413] openmotif-2.2.3-11
    </para>
    <para>[101890] docbook-dtds-1.0-26 -> [111825] docbook-dtds-1.0-27
    </para>
    <para>[111495] firstboot-1.3.42-1 -> [118187] firstboot-1.3.47-2
    </para>
    <para>[107310] cups-1.1.23-15 -> [117439] cups-1.1.23-17 </para>
    <para>[108639] postfix-2.2.2-2 -> [117702] postfix-2.2.5-1 </para>
    <para>[110444] booty-0.53-1 -> [118032] booty-0.57-1 </para>
    <para>[106326] cdicconf-0.2-11 -> [113538] cdicconf-0.2-12 </para>
    <para>[110352] libwnck-2.10.0-3 -> [117752] libwnck-2.12.0-1
    </para>
    <para>[110575] crypto-utils-2.2-5 -> [111863] crypto-utils-2.2-6
    </para>
    <para>[107303] perl-Compress-Zlib-1.34-2 -> [117468]
      perl-Compress-Zlib-1.37-1.fc5 </para>
    <para>[109590] libgtop2-2.10.1-1 -> [117665] libgtop2-2.12.0-1
    </para>
    <para>[110990] yelp-2.10.0-1 -> [117757] yelp-2.12.0-1 </para>
    <para>[110693] hwdata-0.158-1 -> [117804] hwdata-0.169-1 </para>
    <para>[106407] rhnlib-1.8-6.p24.1 -> [116200] rhnlib-1.8-6.p24.11
    </para>
    <para>[106361] arts-1.4.0-1 -> [115461] arts-1.4.2-1 </para>
    <para>[107873] dia-0.94-11 -> [116485] dia-0.94-13 </para>
    <para>[106665] gnome-system-monitor-2.10.0-2 -> [117663]
      gnome-system-monitor-2.12.0-1 </para>
    <para>[106473] pwlib-1.8.4-1 -> [117530] pwlib-1.8.7-1 </para>
    <para>[106475] openh323-1.15.3-1 -> [117538] openh323-1.15.6-1
    </para>
    <para>[106477] gnomemeeting-1.2.1-1 -> [118169]
      gnomemeeting-1.2.2-2 </para>
    <para>[93048] fonts-KOI8-R-1.0-7 -> [113604] fonts-KOI8-R-1.0-8
    </para>
    <para>[104596] patchutils-0.2.30-4 -> [114399] patchutils-0.2.31-2
    </para>
    <para>[107936] man-1.5p-4 -> [111925] man-1.5p-6 </para>
    <para>[110750] elinks-0.10.3-3 -> [112404] elinks-0.10.3-3.1
    </para>
    <para>[107263] netatalk-2.0.2-3 -> [114554] netatalk-2.0.3-2
    </para>
    <para>[107736] netdump-0.7.7-6 -> [115481] netdump-0.7.10-4
    </para>
    <para>[111279] ant-1.6.2-3jpp_8fc -> [115662] ant-1.6.2-3jpp_14fc
    </para>
    <para>[109158] openmotif21-2.1.30-14 -> [116779]
      openmotif21-2.1.30-17.1 </para>
    <para>[109640] gnutls-1.0.25-1 -> [115978] gnutls-1.2.6-1 </para>
    <para>[104487] privoxy-3.0.3-7 -> [117709] privoxy-3.0.3-9 </para>
    <para>[107117] eog-2.10.0-1 -> [117654] eog-2.12.0-1 </para>
    <para>[109172] gconf-editor-2.10.0-5 -> [117718]
      gconf-editor-2.12.0-1 </para>
    <para>[111105] gtk2-engines-2.6.3-2 -> [117640]
      gtk2-engines-2.6.5-1 </para>
    <para>[111267] gnome-desktop-2.10.0-5 -> [117723]
      gnome-desktop-2.12.0-1 </para>
    <para>[110510] gnome-panel-2.10.1-10 -> [118149]
      gnome-panel-2.12.0-2 </para>
    <para>[108570] gnome-session-2.10.0-2 -> [117729]
      gnome-session-2.12.0-1 </para>
    <para>[109748] gnome-terminal-2.10.0-2 -> [117730]
      gnome-terminal-2.12.0-1 </para>
    <para>[107500] metacity-2.10.0-1 -> [117759] metacity-2.12.0-1
    </para>
    <para>[107193] valgrind-2.4.0-2 -> [117903] valgrind-3.0.1-1
    </para>
    <para>[111389] vte-0.11.13-2.fc4 -> [117756] vte-0.11.15-1.fc5
    </para>
    <para>[105809] ghostscript-7.07-40 -> [116480]
      ghostscript-8.15-0.rc4.3 </para>
    <para>[108033] file-4.13-4 -> [118257] file-4.15-3 </para>
    <para>[108940] mgetty-1.1.33-1 -> [115032] mgetty-1.1.33-3_FC5
    </para>
    <para>[111301] xen-2-20050522 -> [118168] xen-3.0-0.20050912.fc5.1
    </para>
    <para>[106289] libraw1394-1.1.0-3 -> [114765]
      libraw1394-1.2.0-1.fc5 </para>
    <para>[108526] mod_perl-2.0.0-0.rc5.3 -> [112776]
      mod_perl-2.0.1-1.fc5 </para>
    <para>[103976] radvd-0.7.3-1_FC4 -> [114404] radvd-0.8-2.FC5
    </para>
    <para>[111033] ncpfs-2.2.4-8 -> [115462] ncpfs-2.2.4-9 </para>
    <para>[106079] prelink-0.3.4-3 -> [117615] prelink-0.3.6-1 </para>
    <para>[110767] netpbm-10.27-3 -> [116518] netpbm-10.29-1 </para>
    <section id="sn-packages-added">
      <title>Packages Added</title>
      <para>
	These packages have been added to &FC; for this release notes.
      </para>
      <para>scim-anthy-0.6.1-1.fc5 </para>
      <para>struts-1.2.4-2jpp_3fc </para>
      <para>jonas-4.3.3-1jpp_10fc </para>
      <para>nspr-4.6-4 </para>
      <para>scim-1.4.2-3 </para>
      <para>anthy-6829-3 </para>
      <para>system-config-cluster-0.9.69-1.0 </para>
      <para>axis-1.2.1-1jpp_1fc </para>
      <para>bsf-2.3.0-6jpp_2fc </para>
      <para>bsh-1.3.0-5jpp_1fc </para>
      <para>concurrent-1.3.2-2jpp_1fc </para>
      <para>dtdparser-1.21-2jpp_1fc </para>
      <para>jakarta-commons-discovery-0.3-1jpp_1fc </para>
      <para>jdom-1.0-1jpp_2fc </para>
      <para>wsdl4j-1.5.1-1jpp_1fc </para>
      <para>javacc-3.2-1jpp_3fc </para>
      <para>jakarta-commons-httpclient-3.0-0.rc2.0jpp_1fc </para>
      <para>castor-0.9.5-1jpp_1fc </para>
      <para>adaptx-0.9.6-1jpp_1fc </para>
      <para>amtu-1.0.2-1 </para>
      <para>xdoclet-1.2.2-2jpp_1fc </para>
      <para>xjavadoc-1.1-1jpp_1fc </para>
      <para>jgroups-2.2.6-1jpp_1fc </para>
      <para>hsqldb-1.80.1-1jpp_1fc </para>
      <para>jonathan-core-4.1-1jpp_4fc </para>
      <para>jonathan-jeremie-4.2-1jpp_4fc </para>
      <para>jrefactory-2.8.9-3jpp_1fc </para>
      <para>mockobjects-0.09-12jpp_2fc </para>
      <para>monolog-1.8.6-1jpp_5fc </para>
      <para>oldkilim-1.1.3-2jpp_3fc </para>
      <para>p6spy-1.3-2jpp_3fc </para>
      <para>fractal-2.2-2jpp_1fc </para>
      <para>velocity-1.4-3jpp_1fc </para>
      <para>werken.xpath-0.9.4-0.beta.9jpp_1fc </para>
      <para>gnu.regexp-1.1.4-7jpp_1fc </para>
      <para>nanoxml-2.2.3-3jpp_3fc </para>
      <para>asm-1.5.3-1jpp_1fc </para>
      <para>cairo-1.0.0-1 </para>
      <para>objectweb-anttask-1.2-1jpp_1fc </para>
      <para>objectweb-deploysched-0.2-1jpp_1fc </para>
      <para>carol-1.8.9.3-1jpp_5fc </para>
      <para>jacorb-2.2-3jpp_3fc </para>
      <para>jakarta-commons-cli-1.0-6jpp_1fc </para>
      <para>tanukiwrapper-3.1.1-4jpp_3fc </para>
      <para>tog-pegasus-2.4.1-4.FC5 </para>
      <para>joram-4.1.5-1jpp_5fc </para>
      <para>jotm-2.0.5-1jpp_3fc </para>
      <para>lucene-1.4.3-1jpp_1fc </para>
      <para>geronimo-specs-1.0-0.M2.2jpp_4fc </para>
      <para>jakarta-commons-codec-1.3-2jpp_1fc </para>
      <para>howl-logger-0.1.8-1jpp_3fc </para>
      <para>dhcdbd-1.8-1 </para>
      <para>aspell-ru-0.99f7-2 </para>
      <para>hplip-0.9.5-3 </para>
      <para>gpart-0.1h-1 </para>
      <para>iso-codes-0.47-1 </para>
      <para>gif89encoder-0.90-0.b.1jpp_1fc </para>
      <para>jonathan-rmi-3.1-5 </para>
      <para>pup-0.0.2-1 </para>
      <para>jorm-2.4.3-1jpp_2fc </para>
      <para>jorm-rdb-adapter-2.6-1jpp_1fc </para>
      <para>medor-1.4.4-1jpp_1fc </para>
      <para>medor-expression-1.4.2-1jpp_1fc </para>
      <para>perseus-cache-1.3.4-1jpp_1fc </para>
      <para>perseus-concurrency-1.4-1jpp_1fc </para>
      <para>perseus-dependency-1.4-1jpp_1fc </para>
      <para>perseus-distribution-1.3.2-1jpp_1fc </para>
      <para>perseus-fos-1.3.1-1jpp_1fc </para>
      <para>perseus-persistence-1.3.4-1jpp_1fc </para>
      <para>perseus-pool-1.3.3-1jpp_1fc </para>
      <para>systemtap-0.4.1-2 </para>
      <para>pcmciautils-007-1 </para>
      <para>scim-tables-0.5.3-4 </para>
      <para>libsemanage-1.3.2-1 </para>
      <para>scim-hangul-0.2.0-5.fc5 </para>
      <para>scim-pinyin-0.5.91-1 </para>
      <para>scim-chewing-0.2.1-1 </para>
      <para>scim-qtimm-0.9.4-1 </para>
      <para>libchewing-0.2.7-1 </para>
      <para>kasumi-0.9-3.fc5 </para>
      <para>kexec-tools-1.101-2 </para>
      <para>libsetrans-0.1.7-1 </para>
      <para>icu-3.4-4 </para>
      <para>libiec61883-1.0.0-8.fc5 </para>
    </section>
    <section>
      <title>Packages Removed</title>
      <para>
	These packages have been removed:
      </para>
      <para>ccs-0.25-0.17 </para>
      <para>cman-1.0-0.pre33.15 </para>
      <para>cman-kernel-2.6.11.5-20050601.152643.FC4.2 </para>
      <para>dlm-1.0-0.pre21.10 </para>
      <para>dlm-kernel-2.6.11.5-20050601.152643.FC4.2 </para>
      <para>fence-1.27-16 </para>
      <para>GFS-kernel-2.6.11.8-20050601.152643.FC4.2 </para>
      <para>gnbd-1.0-0.pre14.6 </para>
      <para>gulm-1.0-0.pre30.1 </para>
      <para>iddev-1.9-21 </para>
      <para>magma-1.0-0.pre21.7 </para>
      <para>magma-plugins-1.0-0.pre18.3 </para>
    </section>
  </section>
  <section>
    <title>Notes</title>
    <para>
      <application>system-config-mouse</application> configuration
      utility has been dropped in this release because synaptic and 3
      button mouse configuration is being done automatically and serial
      mice are not supported.
    </para>
    <para>
      Screensavers not installed by default anymore?  Explain
      why and provide commands to install them.
    </para>
<!-- FIXME
    <para>
      Gbenson agreed to justify any inclusion of Java packages in
      FC5. Send a mail. Should include this info before test1 release 
    </para>
-->
  </section>

</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE package-notes-it.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "This header makes editing XML easier" >
 <!ENTITY DISTRO "DISTRO">
 <!ENTITY DISTROVER "DISTROVER">
 <!ENTITY FEX "FEX">
 <!ENTITY FP "FP">
 <!ENTITY FC "FC" >
 <!ENTITY LOCALVER "LOCALVER">
 <!ENTITY RHL "RHL">
 <!ENTITY SERVER-TOOLS SYSTEM "/dev/null">
 <!ENTITY KERNEL SYSTEM "/dev/null">
 <!ENTITY SECURITY SYSTEM "/dev/null">
 <!ENTITY SEL SYSTEM "/dev/null">
 <!ENTITY PRINTING SYSTEM "/dev/null">
 <!ENTITY DATABASE-SERVERS SYSTEM "/dev/null">
 <!ENTITY MULTIMEDIA SYSTEM "/dev/null">
 <!ENTITY WEB-SERVERS SYSTEM "/dev/null">
 <!ENTITY SAMBA SYSTEM "/dev/null">
 <!ENTITY XORG SYSTEM "/dev/null">
 <!ENTITY DEVELOPMENT-TOOLS SYSTEM "./development-tools.xml">

]>
-->
<section id="sn-package-notes">
  <title>Package-Specific Notes</title>
  <!--
  FIXME
  Needs updating of entire contents for FC5.
  -->
  <para>
    The following sections contain information regarding packages that
    have undergone significant changes for &DISTRO; &DISTROVER;.  For
    easier access, they are generally organized using the same groups
    used in Anaconda.
  </para>
  <caution>
    <title>Information Out-of-Date</title>
    <para>
      The content in this section needs to be updated for &DISTRO;
      &DISTROVER;
    </para>
  </caution>
  <section id="sn-basic-components">
    <title>Basic Components</title>
    <para>
      This section contains information related to basic system
      components.
    </para>
    <section>
      <title>&FEX; Repository</title>
      <para>
	&FEX; is part of the larger &FP; and is a volunteer-based
	community effort to create a repository of packages that
	compliment &FC;. The &FEX; repository is enabled by default from
	&FC; &LOCALVER; onwards.
      </para>
      <para>
	You can lean more about &FEX; from:
      </para>
      <para>
	<ulink
	  url="http://fedoraproject.org/wiki/Extras">http://fedoraproject.org/wiki/Extras</ulink>
      </para>
      <para>
	If you would like to install any software available from
	Fedora extras you can use <command>yum</command>.
      </para>
<screen>
<command>yum install <replaceable>&lt;packagename&gt;</replaceable></command>
</screen>
      <para>
	Where <replaceable>&lt;packagename&gt;</replaceable> is the name
	of the package you want to install.  For example, if you wanted
	to install the <filename>abiword</filename> package, the command
	<command>yum install abiword</command> automatically installs
	the package and all dependencies.
      </para>
    </section>
    <section id="sn-audit-daemon">
      <title>Audit Daemon <command>auditd</command> and Log
	Files</title>
      <para>
	The audit daemon, auditd, is now enabled by default.  When
	auditd is running, the kernel directs audit messages to
	<filename>/var/log/audit/audit.log</filename>.  The location of this file is
	specified in <filename>/etc/auditd.conf</filename>.
      </para>
      <para>
	AVC messages for &SEL; are sent using the audit infrastructure.
	These messages are now in
	<filename>/var/log/audit/audit.log</filename>.
      </para>
      <para>
	When auditd is not running, the kernel passes audit messages to
	syslog.  These logs are typically kept in <filename>/var/log/messages</filename> and
	are viewable using <command>dmesg</command>.
      </para>
      <para>
	Audit extensions are now compiled into PAM.  All programs that
	do grant entry to the system or change user account attributes
	will generate an audit message.
      </para>
      <para>
	To enable auditing within the kernel, you must pass the
	parameter <parameter>audit=1</parameter> to the kernel during
	boot.  Otherwise, you can use this command to enable auditing
	during run time:
      </para>
<screen>
<command>auditctl -e 1</command>
</screen>
    </section>
    <section id="sn-nptl">
      <title>LinuxThreads versus NPTL</title>
      <para>
	As the next step in removing support for the obsolete
	LinuxThreads library, code compiled and linked on &FC;
	&LOCALVER; now automatically uses the NPTL headers and
	libraries.
      </para>
      <para>
	In previous releases since &RHL; 9, the default threading was
	LinuxThreads since the interface is mostly forward compatible.
	The advantages of the NPTL interface is that the cancellation
	handling is faster (when <parameter>-fexception</parameter> is
	used, even in C code) and that the additional interfaces are now
	available without special compiler and linker parameters.  In
	other words, you do not need to use
	<option>-I/usr/include/nptl</option> and
	<option>-L/usr/lib{,64}/nptl</option> any longer.  Note that
	<parameter>lib{,64}</parameter> is to be interpreted as lib64 on
	platforms which place DSOs in <filename>lib64/</filename>
	directories, and <filename>lib/</filename> otherwise.
      </para>
      <para>
	In &FC; &LOCALVER; it is still possible to create code using the
	LinuxThreads definitions.  For this the
	<filename>linuxthreads-devel</filename> package must be
	installed and
      </para>
<screen>
<option>-I/usr/include/linuxthreads -L/usr/lib{,64}/linuxthreads</option>
</screen>
      <para>
	must be passed to the compiler.
      </para>
      <para>
	Previously, you could select the version of glibc and the
	libpgthread DSH using run time environment variables.  You now
	need to also specify this variable in the environment:
      </para>
<screen>
<envar>LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads</envar>
</screen>
      <para>
	This additional variable is required because the run/time
	libraries have been moved out of the way.  There may be programs
	that will not work if the program uses an unfortunate
	<envar>DT_RPATH</envar> (which overwrites the
	<envar>LD_LIBRARY_PATH</envar> setting).
      </para>
      <para>
	All this makes it more cumbersome to run programs which depend
	on LinuxThreads.  But this is intentional.
      </para>
      <important>
	<title>Important</title>
	<para>
	  FC5 will not have LinuxThreads support and all programs have
	  to be converted to use NPTL by then.
	</para>
      </important>
      <para>
	In general, conversion to using NPTL has not been an issue.
      </para>
    </section>
    <section>
      <title>Enabling the <filename>slocate</filename> Database</title>
      <para>
	The database needed by the <command>locate</command> utility is
	no longer created by default. Enable the database creation by
	setting <computeroutput>DAILY_UPDATE</computeroutput> to
	<option>yes</option> in <filename>/etc/updatedb.conf</filename>
	if you want to use <command>locate</command>.
      </para>
    </section>
    <section>
      <title>Stricter Controls in <filename>openssh</filename></title>
      <para>
	The version of OpenSSH in &FC; &LOCALVER; is based on OpenSSH
	3.9 and includes strict permission and ownership checks for the
	user configuration file <filename>~/.ssh/config</filename>. If
	this file does not have appropriate ownership and permissions,
	<command>ssh</command> will exit.
      </para>
      <para>
	Check that <filename>~/.ssh/config</filename> is owned by the
	owner of <filename>~/</filename>, and that its permissions are
	set to mode 600.
      </para>
<screen>
ls -l ~/.ssh/config
-rw-------  1 username username 400 May  5 18:44 /home/username/.ssh/config
</screen>
      <para>
	The directory <filename>~/</filename> is command-line shorthand
	for the logged in user's home directory, usually
	<filename>/home/username/</filename>.
      </para>
      <para>
	In addition, OpenSSH is no longer configured to request X11
	forwarding by default when connecting to servers.  To enable X11
	forwarding, the <option>-X</option> or <option>-Y</option>
	option must be specified, or the <option>ForwardX11</option>
	option must be enabled in the <filename>~/.ssh/config</filename>
	file.
      </para>
      <para>
	The behavior of <command>ssh</command> clients that are invoked
	with the <option>-X</option> option has changed.  In OpenSSH 3.8
	and later, X11 forwarding is performed in a way that
	applications run as untrusted clients by default. Previously,
	X11 forwarding was performed so that applications always ran as
	trusted clients. Some applications may not function properly
	when run as untrusted clients. To forward X11 so that
	applications are run as trusted clients, invoke ssh with the
	<option>-Y</option> option instead of the <option>-X</option>
	option, or set <option>ForwardX11Trusted</option> in the
	<option>~/.ssh/config</option> file.
      </para>
    </section>
    <section id="sn-perl">
      <title>Perl Binary Compat Symlinks</title>
      <para>
	Binary compat symlinks for <filename>perl-5.8.0</filename>,
	<filename>perl-5.8.1</filename>, and
	<filename>perl-5.8.2</filename> have been removed.  If you have
	perl modules built with those older versions of perl, you need
	to rebuild using the <filename>perl-5.8.6</filename> contained
	in &FC; &LOCALVER;.
      </para>
    </section>
    &SERVER-TOOLS;
    &JAVA-PACKAGE;
  </section>
  <section id="sn-packages-core">
    <title>Core</title>
    <para>
      This section contains the most elemental components of &DISTRO;,
      including the kernel.
    </para>
    <section>
      <title>yum</title>
      <para>
	The sqllite database is now used by yum, and makes performance
	noticeably faster.
      </para>
      <para>
	The Fedora Extras repository is now enabled by default.
      </para>
    </section>
    &KERNEL;
    &SECURITY;
  </section>
  &DEVELOPMENT-TOOLS;
  &I18N;
  &PRINTING;
<!--  no content for this release
  &DATABASE-SERVERS; -->
  &MULTIMEDIA;
  &ENTERTAINMENT;
  &WEB-SERVERS;
  &SAMBA;
  &XORG;
  &ENTERTAINMENT;
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE project-overview-it.xml ---
  <section id="sn-whatitis">
    <title>An Overview of the &PROJ;</title>
    <para>
      The goal of the &PROJ; is to work with the Linux community to
      build a complete, general-purpose operating system exclusively
      from open source software.  Development is done in a public forum.
      The project produces time-based releases of &DISTRO; approximately
      2-3 times a year, with a public release schedule.  The &RH;
      engineering team continues to participate in building &DISTRO;
      and invites and encourages more outside participation than was
      possible in the past.  By using this more open process, we hope to
      provide an operating system more in line with the ideals of free
      software and more appealing to the open source community.
    </para>
    <para>
      For more information, refer to the &PROJ; website:
    </para>
    <para>
      <ulink
	url="http://fedora.redhat.com/">http://fedora.redhat.com/</ulink>
    </para>
    <para>
      In addition to the website, the following mailing lists are
      available:
    </para>
    <itemizedlist>
      <listitem>
        <para>
	  fedora-list at redhat.com &mdash; For users of &DISTRO; releases
	</para>
      </listitem>
      <listitem>
        <para>
	  fedora-test-list at redhat.com &mdash; For testers of &DISTRO;
	  test releases
	</para>
      </listitem>
      <listitem>
        <para>
	  fedora-devel-list at redhat.com &mdash; For developers,
	  developers, developers
	</para>
      </listitem>
      <listitem>
        <para>
	  fedora-docs-list at redhat.com &mdash; 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
      <computeroutput><replaceable>&lt;listname&gt;</replaceable>-request</computeroutput>
      (where
      <computeroutput><replaceable>&lt;listname&gt;</replaceable></computeroutput>
      is one of the above list names.)
    </para>
    <para>
      Alternately, you can subscribe through the Web interface:
    </para>
    <para>
      <ulink url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
    </para>
    <para>
      If you have subscribed in the past to rhl-list, rhl-beta-list,
      rhl-devel-list, or rhl-docs-list, your subscriptions have been
      retained.
    </para>
    <para>
      The &PROJ; also includes an IRC (Internet Relay Chat) channel.  IRC is
      a real-time, text-based form of communication.  With it, you can have
      conversations with multiple people in an open channel or chat with someone
      privately one-on-one.
    </para>
    <para>
      To talk with other &PROJ; participants via IRC, access freenode IRC
      network.  Initially, you can use <filename>irc.freenode.net</filename> as
      the IRC server, although you may decide to select a server that is
      geographically closer to you.  Refer to the freenode website (<ulink
      url="http://www.freenode.net/">http://www.freenode.net/</ulink>) for more
      information.  &PROJ; participants frequent the
      <filename>#fedora</filename> channel, while &PROJ; developers can often be
      found on the <filename>#fedora-devel</filename> channel.  Some of the
      larger projects may have their own channels as well; this information can
      be found on the project pages.
    </para>
    <para>
      In order to talk on the <filename>#fedora</filename> channel, you
      will need to register your nickname (<firstterm>nick</firstterm>).
      Instructions are given when you <command>/join</command> the
      channel.
    </para>
    <note>
      <title>Note</title>
      <para>
	&RH; has no control over the &PROJ; IRC channels or their
	content.
      </para>
    </note>
  </section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE README-it.xml ---
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

<!ENTITY % ALPHA "IGNORE">
<!ENTITY % X86 "INCLUDE">
<!ENTITY % IA64 "IGNORE">
<!ENTITY % S390 "IGNORE">
<!ENTITY % HA "IGNORE">
<!ENTITY % X86-64 "IGNORE">

<!ENTITY RH "Red Hat"> <!-- The generic term "Red Hat" -->
<!ENTITY RHL "&RH; Linux"> <!-- The generic term "Red Hat Linux" -->
<!ENTITY FORMAL-RHI "&RH;, Inc."> <!-- Formal version -->
<!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
<!ENTITY PROJ "&NAME; Project"> <!-- The project's name -->
<!ENTITY DISTRO "&NAME; Core"> <!-- The software's name -->
<!ENTITY DISTROVER "4"> <!-- The software's version -->

]>

<article id="index" lang="en" arch="x86;x86_64" os="test;final">
  <articleinfo>
    <title>&DISTRO; &DISTROVER; README</title>
    <copyright>
      <year>2005</year>
      <holder>&FORMAL-RHI;</holder>
    </copyright>
    <legalnotice id="legalnotice">
      <para>The contents of this CD-ROM are Copyright &copy; 2005 &PROJ; and
        others.  Refer to the End User License Agreement and individual
        copyright notices in each source package for distribution terms.</para>

      <para>&NAME;, &RH;, &RH; Network, the &RH; "Shadow Man" logo, RPM, Maximum
        RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover,
        RHmember, RHmember More, Rough Cuts, Rawhide and all &RH;-based
        trademarks and logos are trademarks or registered trademarks of
        &FORMAL-RHI; in the United States and other countries.</para>

      <para>Linux is a registered trademark of Linus Torvalds.</para>

      <para>Motif and UNIX are registered trademarks of The Open Group.</para>

      <para>Intel and Pentium are registered trademarks of Intel
        Corporation. Itanium and Celeron are trademarks of Intel
        Corporation.</para>

      <para>AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of Advanced
        Micro Devices, Inc.</para>

      <para>Windows is a registered trademark of Microsoft Corporation.</para>

      <para>SSH and Secure Shell are trademarks of SSH Communications Security,
        Inc.</para>

      <para>FireWire is a trademark of Apple Computer Corporation.</para>

      <para>All other trademarks and copyrights referred to are the property of
        their respective owners.</para>

      <para>The GPG fingerprint of the <computeroutput>"Fedora Project
        &lt;fedora at redhat.com&gt;"</computeroutput> key is:</para>

      <para>CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2</para>
    </legalnotice>
  </articleinfo>

  <section id="dir-org">
    <title>DIRECTORY ORGANIZATION</title>

    <para>&DISTRO; is delivered on multiple CD-ROMs consisting of installation
      CD-ROMs and source code CD-ROMs.</para>

    <para>The first installation CD-ROM can be directly booted into the
      installation on most modern systems, and contains the following directory
      structure (where <filename>/mnt/cdrom</filename> is the mount point of the
      CD-ROM):</para>

    <screen arch="x86">
      <!-- <remark os="test">(x86)</remark> -->
<computeroutput>
/mnt/cdrom
  |----> Fedora
  |        |----> RPMS         -- binary packages
  |        `----> base         -- information on this release of Fedora
  |                               Core used by the installation process
  |----> images                -- boot and driver disk images
  |----> isolinux              -- files necessary to boot from CD-ROM
  |----> README                -- this file
  |----> RELEASE-NOTES         -- the latest information about this release
  |                               of Fedora Core
  `----> RPM-GPG-KEY           -- GPG signature for packages from Red Hat
</computeroutput>
    </screen>
<!-- repetitive for the moment
    <screen arch="x86_64">
      <remark os="test">(x86_64)</remark>
<computeroutput>
/mnt/cdrom
  |- - - -> Fedora
  |        |- - - -> RPMS         - - binary packages
  |        `- - - -> base         - - information on this release of Fedora
  |                               Core used by the installation process
  |- - - -> images                - - boot disk ISO image
  |- - - -> isolinux              - - files necessary to boot from CD-ROM
  |- - - -> README                - - this file
  |- - - -> RELEASE-NOTES         - - the latest information about this release
  |                               of Fedora Core
  `- - - -> RPM-GPG-KEY           - - GPG signature for packages from Red Hat
</computeroutput>
  </screen>
    -->
    <para>The remaining Installation CD-ROMs are similar to Installation CD-ROM
      1, except that only the <filename>Fedora</filename> subdirectory is
      present.</para>

    <para>The directory layout of each source code CD-ROM is as follows:</para>

    <screen>
<computeroutput>
/mnt/cdrom
  |----> SRPMS                 -- source packages
  `----> RPM-GPG-KEY           -- GPG signature for packages from Red Hat
</computeroutput>
    </screen>

    <para>If you are setting up an installation tree for NFS, FTP, or HTTP
      installations, you need to copy the <filename>RELEASE-NOTES</filename>
      files and all files from the <filename>Fedora</filename> directory on
      discs 1-3.  On Linux and Unix systems, the following process will properly
      configure the /target/directory on your server (repeat for each disc):</para>

    <orderedlist>
      <listitem>
        <para>Insert disc</para>
      </listitem>

      <listitem>
        <para><command>mount /mnt/cdrom</command></para>
      </listitem>

      <listitem>
        <para><command>cp -a /mnt/cdrom/Fedora
            /target/directory</command></para>
      </listitem>

      <listitem>
        <para><command>cp /mnt/cdrom/RELEASE-NOTES* /target/directory</command>
          (Do this only for disc 1)</para>
      </listitem>

      <listitem>
        <para><command>umount /mnt/cdrom</command></para>
      </listitem>
    </orderedlist>
  </section>

  <section id="installing">
    <title>INSTALLING</title>

    <para>Many computers can now automatically boot from CD-ROMs. If you have
      such a machine (and it is properly configured) you can boot the &DISTRO;
      CD-ROM directly.  After booting, the &DISTRO; installation program will
      start, and you will be able to install your system from the CD-ROM.</para>

    <para arch="x86;x86_64"><!-- <remark os="test">(x86;x86_64)</remark> --> The
      <filename>images/</filename> directory contains the file
      <filename>boot.iso</filename>.  This file is an ISO image that can be used
      to boot the &DISTRO; installation program.  It is a handy way to start
      network-based installations without having to use multiple diskettes.  To
      use <filename>boot.iso</filename>, your computer must be able to boot from
      its CD-ROM drive, and its BIOS settings must be configured to do so.  You
      must then burn <filename>boot.iso</filename> onto a recordable/rewriteable
      CD-ROM.</para>

    <para arch="x86;x86_64"><!-- <remark os="test">(x86;x86_64)</remark> --> Another image
      file contained in the <filename>images/</filename> directory is
      <filename>diskboot.img</filename>.  This file is designed for use with USB
      pen drives (or other bootable media with a capacity larger than a diskette
      drive).  Use the <command>dd</command> command to write the image.</para>

    <note arch="x86;x86_64">

      <title>Note</title>
      <!-- <remark os="test">(x86;x86_64)</remark> -->

      <para>The ability to use this image file with a USB pen drive depends on
        the ability of your system's BIOS to boot from a USB device.</para>
        </note>
  </section>

  <section id="get-help">
    <title>GETTING HELP</title>

    <para>For those that have web access, see <ulink
        url="http://fedora.redhat.com">http://fedora.redhat.com</ulink>.  In
        particular, access to &PROJ; mailing lists can be found at:</para>

    <para><ulink
    url="https://listman.redhat.com/mailman/listinfo/">https://listman.redhat.com/mailman/listinfo/</ulink></para>
  </section>

  <section id="export-ctl">
    <title>EXPORT CONTROL</title>

    <para>The communication or transfer of any information received with this
      product may be subject to specific government export approval.  User shall
      adhere to all applicable laws, regulations and rules relating to the
      export or re-export of technical data or products to any proscribed
      country listed in such applicable laws, regulations and rules unless
      properly authorized.  The obligations under this paragraph shall survive
      in perpetuity.</para>
  </section>
<!--
  <section id="s1-test" os="test">
    <title>README Feedback Procedure</title>

    <para>(This section will disappear when the final &DISTRO; release is
      created.)</para>

    <para>If you feel that this README could be improved in some way, submit a
      bug report in &RH;'s bug reporting system:</para>

    <para><ulink
    url="https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi">https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi</ulink></para>

    <para>When posting your bug, include the following information in the
      specified fields:</para>

    <itemizedlist>
      <listitem>
        <para><guilabel>Product:</guilabel> &DISTRO;</para>
      </listitem>

      <listitem>
        <para><guilabel>Version:</guilabel> Not really important (I'm using
          "devel")</para>
      </listitem>

      <listitem>
        <para><guilabel>Component:</guilabel> fedora-release</para>
      </listitem>

      <listitem>
        <para><guilabel>Summary:</guilabel> A short description of what could be
          improved.  If it includes the word "README", so much the
          better.</para>
      </listitem>

      <listitem>
        <para><guilabel>Description:</guilabel> A more in-depth description of
          what could be improved.</para>
      </listitem>

      <listitem>
        <para><guilabel>Blocks:</guilabel> 114406 (The README blocker bug
          number)</para>
      </listitem>
    </itemizedlist>

    <para>A quick way of seeing what sorts of bugs have been posted against the
      README is to look at the bugs listed in the <guilabel>Bug 114406 depends
      on:</guilabel> field of the &DISTRO; release notes blocker bug:</para>

    <para><ulink
        url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114406">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114406</ulink></para>

    <para>If you are interested in following the discussion of any of these
      bugs, feel free to add yourself to the bug's CC list.  That way, you'll
      get email whenever there are any changes to the bug.</para>

    <para>As bugs are posted for the various parts of the README file,
      subsequent test versions of these release notes will contain links similar
      to this one:</para>

    <remark os="test">%%% <ulink
        url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114408">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114408</ulink>
        %%%</remark>

    <para>These links point to Bugzilla entries for the information preceding
  the link.  This makes it easier for people to contribute &mdash; just
      point your browser at the link, add your comments to the bug, and commit
      your changes.</para>
  </section>
-->
<!--
  <ackno>(
    <emphasis arch="x86">x86</emphasis>
    <emphasis arch="x86_64">x86_64</emphasis>
    )</ackno>
-->
</article>


--- NEW FILE RELEASE-NOTES-master-it.xml ---
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
 [

<!ENTITY RH "Red Hat">
<!ENTITY FORMAL-RHI "&RH;, Inc.">
<!ENTITY RHN "&RH; Network">
<!ENTITY RHL "Red Hat Linux"> 
<!ENTITY RHEL "&RH; Enterprise Linux">
<!ENTITY PROD "&RHEL;">
<!ENTITY PRODVER "@VERSION@">

<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">
<!ENTITY SYSTEM "./.xml">

]>

<!-- if you add an arch to build, you must add it to this master list also -->
<article id="index" lang="en" arch="i386;ia64;s390;s390x;x86_64;ppc">
  <articleinfo>
    <title>&PROD; @VARIANTUPPER@ &PRODVER; Release Notes</title>
    <copyright>
      <year>2003</year>
      <holder>&FORMAL-RHI;</holder>
    </copyright>
  </articleinfo>

  <sect1 id="s1-overview">
    <title>Overview</title>
  
    <para>The following topics are covered in these release notes:</para>

    <itemizedlist>
      <listitem>
        <para>Booting Anaconda</para>
      </listitem>

      <listitem arch="s390;s390x">
        <para>Parameter file notes</para>
      </listitem>

      <listitem>
        <para>Installation-related notes</para>
      </listitem>

      <listitem>
        <para>Notes on input methods</para>
      </listitem>

      <listitem>
        <para>General notes</para>
      </listitem>

      <listitem>
        <para>Kernel notes</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="booting-anaconda">
    <title>Booting Anaconda</title>

    <para>This section describes the process necessary to boot
      <application>Anaconda</application>, the &PROD; installation
      program.</para>

    <para arch="ppc">For the <trademark class="registered">IBM</trademark>
      <trademark>eServer</trademark> <trademark>pSeries</trademark>:</para>

    <para arch="i386;ia64;x86_64;ppc">The first CD-ROM is bootable, and can
      be used to start the installation process.  If a CD-ROM-based installation
      is not desired (for example, if you want to install &PROD; &PRODVER; over a
      network connection), a CD-ROM image file containing only those files
      required to start the installation process is also available as
      <filename>boot.iso</filename> in the <filename>images/</filename>
      directory on the first CD-ROM.</para>
                                                                                
    <para arch="ppc">A network boot image (named
      <filename>netboot.img</filename>) is available, and is located in the
      <filename>images/</filename> directory on Installation CD 1.  Consult the
      documentation that came with your system for instructions on setting up
      network boot.  Kernel command line arguments (such as anaconda options)
      must be passed from the Open Firmware prompt.  For example, if there is a
      devalias named <command>network</command> for the device that is
      configured for network booting, the following command line would load a
      driver disk from an HTTP server:</para>
                                                                                
    <para arch="ppc"><command>boot network
        dd=http://server.example.com/path/to/driverdisk.img</command></para>
                                                                                
    <para arch="ppc">Additional documentation for configuring netboot on pSeries can be
      found here:</para>

    <para arch="ppc"><ulink
      url="http://people.redhat.com/msw/mirror/penguinppc.org/~hollis/linux/rs6k-netboot.shtml">http://people.redhat.com/msw/mirror/penguinppc.org/~hollis/linux/rs6k-netboot.shtml</ulink></para>

    <para arch="ppc">For the IBM eServer <trademark>iSeries</trademark>:</para>

    <para arch="ppc">You must direct <trademark
      class="registered">OS/400</trademark> to boot the stream file
      <filename>ppc/iSeries/boot.img</filename>, which is located on the first
      CD-ROM.  You can either point directly at the CD-ROM or copy the file to a
      location in IFS.  When the installation is complete, it will boot from
      side C, but this will only work until you vary off your LPAR.  After
      varying off your LPAR, you must change your IPL source to side B to
      continue booting &PROD;.</para>

    <para arch="s390;s390x">You must download the
      <filename>kernel.img</filename> and <filename>initrd.img</filename> files
      from the <filename>images/</filename> directory into CMS.  You can then
      use these with a parameter file (described in the following section) to
      start your installation.  Once the Linux kernel has booted, use ssh to
      access your VM and start the installation process.  When the installation
      finishes, you must use a command similar to <command>#cp ipl
      0200</command> to bootstrap (or IPL) the Linux installation on the DASD at
      0200.</para>
  </sect1>

  <sect1 id="s1-parm-file-notes" arch="s390;s390x">
    <title>Parameter File Notes</title>

    <para>The IBM <trademark class="registered">S/390</trademark> and IBM
        eServer <trademark class="registered">zSeries</trademark> architectures
        use a special parameter file to set up networking before the
        installation program (<application>anaconda</application>) can be
        started.  This section describes the contents of the parameter
        file.</para>

    <para>The parameter file should contain no more than 80 characters per
      line.</para>
 
    <para>The VM reader has a limit of 11 lines for the parameter file (for a
      total of 880 characters).</para>
 
    <para>The DASD and the tape IPL have a limit of 896 characters.</para>

    <para>The following parameters are required, and should always be
      present:</para>

    <itemizedlist>
      <listitem>
        <para><command>DASD=<replaceable>&lt;dasd-list&gt;</replaceable></command></para>

        <para>Where
          <command><replaceable>&lt;dasd-list&gt;</replaceable></command>
          represents the list of DASD devices to be used by &PROD;.  The list
          can consist of one or more DASD numbers separated by commas, and can
          also contain ranges, which are specified by two DASD numbers separated
          by a hyphen.  Both constructs can be combined in a single list, as in
          the following example:</para>

        <para><command>DASD=10A8,10A9,10AA,10A3-10A6</command></para>

        <para>NOTE: Although autoprobing for DASDs is done if this parameter is
          omitted, &RH; highly recommend including the DASD= parameter as the
          device numbers (and therefore the device names) can vary when new DASD
          is added to the &PROD; guest. This can result in an unusable
          system.</para>
      </listitem>

      <listitem>
        <para><command>root=<replaceable>&lt;file-system&gt;</replaceable></command></para>

        <para>Where
          <command><replaceable>&lt;file-system&gt;</replaceable></command>
          represents the device on which the root file system can be found.  For
          for installation purposes, it should be set to
          <command>/dev/ram0</command>, which is the ramdisk containing the
          &PROD; installation program.</para>
      </listitem>
    </itemizedlist>

    <para>The following parameters are required to set up networking:</para>

    <itemizedlist>
      <listitem>
        <para><command>CHANDEV=<replaceable>&lt;device&gt;</replaceable>,<replaceable>&lt;input&gt;</replaceable>,<replaceable>&lt;output&gt;</replaceable></command></para>

        <para>where:</para>

        <para>&middot;
          <command><replaceable>&lt;device&gt;</replaceable></command> is the
          type of device (for example, <command>ctc0</command>,
          <command>escon0</command>, or <command>lcs0</command>)</para>

        <para>&middot;
          <command><replaceable>&lt;input&gt;</replaceable></command> is the
          input port for this device</para>

        <para>&middot;
          <command><replaceable>&lt;output&gt;</replaceable></command> is the
          output port for this device</para>

        <para>For example:</para>

        <para><command>CHANDEV=ctc0,0x600,0x601</command></para>
        <para><command>CHANDEV=escon0,0x605,0x608</command></para>

        <para>To force a specific CTC protocol, additional parameters can be
          added. For example:</para>

        <para><command>CHANDEV=ctc0,0x600,0x601,0,<replaceable>&lt;n&gt;</replaceable></command></para>
        <para>where <replaceable>&lt;n&gt;</replaceable> is one of the
          following:</para>

        <para>&middot; <command>0</command> for compatibility mode (used with
          non-Linux peers other than S/390 and zSeries operating systems)</para>

        <para>&middot; <command>1</command> for extended mode</para>

        <para>&middot; <command>2</command> for CTC-based tty (only supported on
          Linux-to-Linux connections)</para>

        <para>&middot; <command>3</command> for compatibility mode with S/390
          and zSeries operating systems</para>
      </listitem>

      <listitem>
        <para><command>IUCV=<replaceable>&lt;userid&gt;</replaceable></command></para>

        <para>Where <command><replaceable>&lt;userid&gt;</replaceable></command>
          represents the ID of the guest machines you want to connect to.  Note
          that the ID must be written in capital letters.  For example, an IUCV
          connection to the VM TCP/IP service machine would be written
          as:</para>

        <para><command>IUCV=TCPIP</command></para>
      </listitem>
    </itemizedlist>
 
    <para>The following parameters are optional:</para>

    <itemizedlist>
      <listitem>
        <para><command>HOSTNAME=<replaceable>&lt;string&gt;</replaceable></command></para>

        <para>where <command><replaceable>&lt;string&gt;</replaceable></command>
          is the hostname of the newly-installed Linux guest.</para>
      </listitem>

      <listitem>
        <para><command>NETTYPE=<replaceable>&lt;type&gt;</replaceable></command></para>

        <para>where <command><replaceable>&lt;type&gt;</replaceable></command>
          must be one of the following: <command>ctc</command>,
          <command>escon</command>, <command>tr</command>,
          <command>hsi</command>, <command>iucv</command>, or
          <command>eth</command>.</para>
      </listitem>

      <listitem>
        <para><command>IPADDR=<replaceable>&lt;IP&gt;</replaceable></command></para>

        <para>where <command><replaceable>&lt;IP&gt;</replaceable></command> is
          the IP address of the new Linux guest.</para>
      </listitem>

      <listitem>
        <para><command>NETWORK=<replaceable>&lt;network&gt;</replaceable></command></para>

        <para>where
          <command><replaceable>&lt;network&gt;</replaceable></command> is the
          address of your network.</para>
      </listitem>

      <listitem>
        <para><command>NETMASK=<replaceable>&lt;netmask&gt;</replaceable></command></para>

        <para>where
          <command><replaceable>&lt;netmask&gt;</replaceable></command> is the
          netmask.</para>
      </listitem>

      <listitem>
        <para><command>BROADCAST=<replaceable>&lt;broadcast&gt;</replaceable></command></para>

        <para>where
          <command><replaceable>&lt;broadcast&gt;</replaceable></command> is the
          broadcast address.</para>
      </listitem>

      <listitem>
        <para><command>GATEWAY=<replaceable>&lt;gw&gt;</replaceable></command></para>

        <para>where <command><replaceable>&lt;gw&gt;</replaceable></command> is
          either the gateway-IP for your eth device or the IP address of the
          ctc/escon/iucv point-to-point partner.</para>
      </listitem>

      <listitem>
        <para><command>MTU=<replaceable>&lt;mtu&gt;</replaceable></command></para>

        <para>where <command><replaceable>&lt;mtu&gt;</replaceable></command> is
          the Maximum Transmission Unit (MTU) for this connection.</para>
      </listitem>

      <listitem>
        <para><command>DNS=<replaceable>&lt;server1&gt;</replaceable>:<replaceable>&lt;server2&gt;</replaceable>:&hellip;:<replaceable>&lt;serverN&gt;</replaceable></command></para>

        <para>where
          <command><replaceable>&lt;server1&gt;</replaceable>:<replaceable>&lt;server2&gt;</replaceable>:&hellip;:<replaceable>&lt;serverN&gt;</replaceable></command>
          is a list of DNS servers, separated by colons.  For example:</para>

        <para><command>DNS=10.0.0.1:10.0.0.2</command></para>
      </listitem>

      <listitem>
        <para><command>SEARCHDNS=<replaceable>&lt;domain1&gt;</replaceable>:<replaceable>&lt;domain2&gt;</replaceable>:&hellip;:<replaceable>&lt;domainN&gt;</replaceable></command></para>

        <para>where
          <command><replaceable>&lt;domain1&gt;</replaceable>:<replaceable>&lt;domain2&gt;</replaceable>:&hellip;:<replaceable>&lt;domainN&gt;</replaceable></command>
          is a list of the search domains, separated by colons.  For
          example:</para>

        <para><command>SEARCHDNS=example.com:example.org</command></para>
      </listitem>
    </itemizedlist>

    <para>The following parameter for installations using a qeth device is
      optional:</para>

    <itemizedlist>
      <listitem>
        <para><command>QETHPARM=</command></para>

        <para>Use this option to specify additional parameters for your QETH
          device (for CHANDEV) such as:</para>

        <para><command>add_parms,0x10,{lo_devno,hi_devno},portname:<replaceable>&lt;port_name&gt;</replaceable></command></para>
      </listitem>
    </itemizedlist>

    <para>The following parameter for kickstart installation is optional:</para>

    <itemizedlist>
      <listitem>
        <para><command>RUNKS=<replaceable>&lt;value&gt;</replaceable></command></para>

        <para>Where <command><replaceable>&lt;value&gt;</replaceable></command>
          is <command>1</command> if you want to run the installation program in
          non-interactive mode in the 3270 terminal, or <command>0</command>
          otherwise.</para>

        <para>NOTE: Make sure that your kickstart file contains all required
          parameters before you use this option.</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="inst-notes">
    <title>Installation-Related Notes</title>

    <para>This section describes issues related to the &PROD; installation
      program <application>Anaconda</application>.</para>

    <itemizedlist>
      <listitem>
        <para>The sequence for processing CD-ROMs has changed for &PROD;
          &PRODVER;.  The first CD-ROM is required when booting the installation
          program, and again after subsequent CD-ROMs have been
          processed.</para>
      </listitem>

      <listitem>
        <para>The &PROD; installation program has the ability to test the
            integrity of the installation media. It works with the CD, hard
            drive ISO, and NFS ISO installation methods. &RH; recommends that
            you test all installation media before starting the installation
            process, and before reporting any installation-related bugs (many of
            the bugs reported are actually due to improperly-burned CDs). To use
            this test, type <command>linux mediacheck</command> at the
            <prompt>boot:</prompt> prompt.</para>
      </listitem>

      <listitem arch="s390;s390x">
        <para>The Object-code-only (OCO) driver necessary to support the IBM
          3590 Tape Drive on the IBM S/390(R) and IBM eServer zSeries(R)
          architectures is available for download from IBM here:</para>
 
        <para>http://www10.software.ibm.com/developerworks/opensource/linux390/special_oco_rh_2.4.shtml</para>

        <para>NOTE: You must verify that the driver you download is the correct
          one for the version of the kernel running on your system.</para>
      </listitem>

      <listitem arch="s390;s390x">
        <para>A new storage option is available on the s390 and zSeries
          architectures: a SCSI subsystem.  To that end, generic SCSI support is
          enabled and a driver (known as <command>zfcp</command>) is
          supplied.</para>
                                                                                
        <para>The generic SCSI subsystem on &PROD; &PRODVER; does not use the
          REPORT LUNs command at this time; therefore use small LUN numbers for
          virtual volumes.  In addition, the following line must be supplied in
          <filename>/etc/modules.conf</filename>:</para>

        <para><command>options scsi_mod
            max_scsi_luns=<replaceable>&lt;NNN&gt;</replaceable></command></para>

        <para>(Where <command><replaceable>&lt;NNN&gt;</replaceable></command>
          should be a number larger than the largest LUN number used.)  NOTE:
          Larger values slow the bootstrapping process somewhat.</para>
      </listitem>

      <listitem arch="i386">
        <para>&PROD; &PRODVER; includes a new kernel known as the
          <firstterm>hugemem</firstterm> kernel.  This kernel supports a 4GB per
          process user space (versus 3GB for the other kernels), and a 4GB
          direct kernel space. Using this kernel allows &PROD; to run on systems
          with up to 64GB of main memory.  The hugemem kernel is required in
          order to use all the memory in system configurations containing more
          than 16GB of memory.  The hugemem kernel can also benefit
          configurations running with less memory (if running an application
          that could benefit from the larger per process user space, for
          example.)</para>

        <para>To remind you of this issue, the &PROD; &PRODVER; kernel displays a
          message at boot time if your system configuration contains more than
          16GB of memory.  After the system has booted, the following command
          can be used to see if your system displayed the message:</para>

        <para><command>dmesg | less</command></para>

        <para>NOTE: To provide a 4GB address space for both kernel and user
          space, the kernel must maintain two separate virtual memory address
          mappings.  This introduces overhead when transferring from user to
          kernel space; for example, in the case of system calls and interrupts.
          The impact of this overhead on overall performance is highly
          application dependent.</para>

        <para>Also note that, because some drivers were not originally written
          to work well in large-memory environments, &RH; only supports a
          validated subset of drivers when the hugemem kernel is used.  Drivers
          that have been validated by &RH; for use with the hugemem kernel are
          contained in the <filename>kernel-hugemem</filename> package.  Drivers
          that have not been validated, but are still provided, are available in
          the <filename>kernel-hugemem-unsupported</filename> RPM.  To see the
          list of drivers in these RPMs, use the following command:</para>

        <para><command>rpm -qlp
            <replaceable>&lt;kernel-rpm&gt;</replaceable></command></para>

        <para>(Where <command><replaceable>&lt;
              kernel-rpm&gt;</replaceable></command> is the complete filename of
              the appropriate hugemem RPM.  Note that these RPMs can be found on
              CD-ROM #2, in the <filename>RedHat/RPMS/</filename>
              directory.)</para>

        <para>Should you decide that the hugemem kernel's additional overhead
          and the subset of available drivers present no problem for your
          hardware configuration and system environment, and you wish to use the
          hugemem kernel, you must first install it.  To install the hugemem
          kernel, enter the following command while logged in as root:</para>

        <para><command>rpm -ivh
            <replaceable>&lt;kernel-rpm&gt;</replaceable></command></para>

        <para>(Where
          <command><replaceable>&lt;kernel-rpm&gt;</replaceable></command> is
          the name of the hugemem kernel RPM file &mdash;
          <filename>kernel-hugemem-2.4.21-3.EL.i686.rpm</filename>,
          for example.)</para>

        <para>After the installation is complete, reboot your system, making
          sure to select the newly-installed hugemem kernel.  After testing your
          system for proper operation while running the hugemem kernel, you
          should modify the <filename>/boot/grub/grub.conf</filename> file so
          that the hugemem kernel is booted by default.</para>
      </listitem>

      <listitem arch="i386">
        <para>&PROD; &PRODVER; can be installed on the IBM eServer <trademark
          class="registered">xSeries</trademark> 440 and 445.  However, the
          installation process supports configurations containing no more than
          one chassis, and no attached RXE-100 Remote Expansion Enclosures.  If
          your system configuration does not conform to these requirements, you
          can remove any additional chassis and/or RXE-100s, and then perform
          the installation.  Once the installation is complete, the chassis
          and/or RXE-100s can then be re-installed, and will operate normally
          under &PROD;.</para>
      </listitem>

      <listitem arch="ppc">
        <para>Support for some Input/Output Processors/Adapters (IOP/IOA)
          present in some iSeries and pSeries systems require the use of the
          IBMSIS driver.  This driver can be found on the &PROD; &PRODVER;
          Extras CD, and can be loaded as driver media when the &PROD;
          installation process is started.</para>

        <para>Loading the IBMSIS driver via CD-ROM using a non-IDE CD-ROM drive
          (including the iSeries virtual CD-ROM drive) is possible by adding the
          following command to the boot command line:</para>

        <para><command>dd=cdrom</command></para>

        <para>You will then be prompted if you have any driver media for
          additional drivers after all drivers included on the CD-ROM are
          loaded.  Note that this is in addition to the other methods of using
          driver media as described in the <citetitle>&PROD; &PRODVER;
          Installation Guide for the IBM eServer iSeries and IBM eServer pSeries
          Architectures</citetitle>.</para>

        <para>After installation, IBMSIS users should install the
          <filename>ibmsis</filename> and <filename>ibmsis-utils</filename>
          packages from the &PROD; Extras CD.</para>
                                                                                
        <para>After an upgrade to a new version of the kernel, the IBMSIS driver
          must be rebuilt and installed.  The <command>ibmsistool</command>
          program (provided in the <filename>ibmsis</filename> package on the
          &PROD; &PRODVER; Extras CD) largely automates this process.  The
          <filename>kernel-source</filename> package that corresponds to the new
          kernel must be installed, as it provides the headers needed to build
          IBMSIS.  For example, after installing the 2.4.21-3.EL kernel and
          corresponding <filename>kernel-source</filename> packages, the
          following command would update the IBMSIS driver:
        </para>
                                                                                
        <para><command>/usr/sbin/ibmsistool -v 2.4.21-3.EL build
            install</command></para>
      </listitem>

      <listitem>
        <para>&PROD; &PRODVER; now includes support for <firstterm>Logical
            Volume Management</firstterm> (LVM).  LVM is a means of allocating disk
          space into one or more logical volumes, which can then be used to
            implement easily-resizable file systems.</para>
      </listitem>

      <listitem arch="i386">
        <para>While most present-day computers are able to start the
          installation process by booting directly from the first &PROD;
          distribution CD, some hardware configurations require the use of a
          boot diskette.  If your hardware requires a boot diskette, you should
          be aware of the following change.</para>

        <para>&PROD; &PRODVER; uses a different boot diskette layout than
          previous releases of &PROD;.  There is now a single boot diskette
          image file (<filename>bootdisk.img</filename>) that is used to boot
          all systems requiring a boot diskette.</para>

        <para>If you are performing anything other than an installation from an
          IDE or USB device, you will be asked to insert a driver diskette
          created from one of the following image files:</para>

        <para>&middot; <filename>drvnet.img</filename> &mdash; For network
          installations</para>

        <para>&middot; <filename>drvblock.img</filename> &mdash; For SCSI
          installations</para>

        <para>&middot; <filename>pcmciadd.img</filename> &mdash; For PCMCIA
          installations</para>

        <para>As with previous releases of &PROD;, these image files can be found
          in the <filename>images/</filename> directory on the first installation
          CD.</para>
      </listitem>

      <listitem arch="s390;s390x">
        <para>Due to the page-oriented nature of the 3270-style console, output
          to <filename>/dev/console</filename> can fill the screen.  If the
          screen is filled, the &PROD; environment stops operating until the
          screen is cleared.  The screen can be cleared using one of two
          different methods:</para>

        <para>&middot; By issuing the keystrokes necessary to clear the screen
          (For example,
          <keycombo><keycap>Alt</keycap><keycap>C</keycap></keycombo> for the
          <application>x3270</application> terminal emulator, and
          <keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo> for the
          <command>c3270</command> terminal emulator.)</para>

        <para>&middot; By waiting for the screen to be automatically cleared.
          The default wait time is 60 seconds; however, this can be changed by
          using the following command:</para>

        <para><command>#cp term more
            <replaceable>&lt;alarm-time&gt;</replaceable>
            <replaceable>&lt;clear-time&gt;</replaceable></command></para>

        <para>Where
            <command><replaceable>&lt;alarm-time&gt;</replaceable></command>
            represents the number of seconds between the time the screen fills
            and the time the terminal alarm should be sounded, and
            <command><replaceable>&lt;clear-time&gt;</replaceable></command> is
            the number of seconds between the time the terminal alarm is sounded
            and the screen is automatically cleared.  Both the
            <command><replaceable>&lt;alarm-time&gt;</replaceable></command> and
            <command><replaceable>&lt;clear-time&gt;</replaceable></command>
            parameters must be numbers between 0 and 255.</para>

        <para>NOTE: This aspect of the 3270-style console is most likely to be
          an issue whenever a large amount of output is sent to
          <filename>/dev/console</filename>.  Therefore, the console's screen is
          most likely to fill at the following times:</para>

        <para>&middot; During the &PROD; installation process</para>

        <para>&middot; When &PROD; is booted</para>

        <para>&middot; <command>syslog</command> messages are sent to the
          console</para>
      </listitem>

      <listitem arch="i386;ia64;x86_64;ppc">
        <para>Text mode installations using a serial terminal work best when the
          terminal supports UTF-8.  Under UNIX and Linux, Kermit supports UTF-8.
          For Windows, Kermit '95 works well.  Non-UTF-8 capable terminals will
          work as long as only English is used during installation.  An enhanced
          serial display can be used by passing "<command>utf8</command>" as a
          boot-time option to the installation program.  For example:</para>

        <para><command>linux console=ttyS0 utf8</command></para>
      </listitem>

      <listitem>
        <para>The firewall configuration screen in the &PROD; installation
          program has been simplified.  The previous
          "<guilabel>High</guilabel>", "<guilabel>Medium</guilabel>", and
          "<guilabel>No firewall</guilabel>" settings have been replaced by a
          more straightforward on/off-style control.  In addition, the default
          firewall configuration is now stateful, making it more secure.  The
          new design also makes it possible for users of NIS authentication,
          NFS, and DNS to deploy a firewall with no additional customization
          required (although customization by specifying port and protocol is
          still possible).</para>

        <para>NOTE: This change also applies to the <application>Security Level
          Configuration Tool</application>
          (<command>redhat-config-securitylevel</command>).</para>
      </listitem>

      <listitem>
        <para>Installation via VNC is now supported.  To initiate a VNC-based
          installation, pass <command>vnc</command> as a boot-time option.  If
          necessary, a password can be set by adding
          "<command>vncpassword=<replaceable>&lt;password&gt;</replaceable></command>"
          to the boot-time options.  The VNC display will be
          "<command><replaceable>&lt;host&gt;</replaceable>:1</command>", where
          <command><replaceable>&lt;host&gt;</replaceable></command> is the
          hostname or IP address of the system installing &PROD;.</para>

        <para>It is also possible for the &PROD; installation program to
          initiate a connection to a listening VNC client.  This is done by
          using the <command>vncconnect</command> boot-time option:</para>

        <para><command>linux vnc
            vncconnect=<replaceable>&lt;client&gt;</replaceable>[:<replaceable>&lt;port&gt;</replaceable>]</command></para>

        <para>(Where
          <command><replaceable>&lt;client&gt;</replaceable></command> is the
          hostname or IP address of the system running the listening VNC client,
          and <command><replaceable>&lt;port&gt;</replaceable></command> is an
          optional port specification that may be specified if the VNC client is
          not listening on port 5500, which the default port for this type of
          connection).  The following examples show the how the boot-time option
          is specified for standard and non-standard ports:</para>

        <para><command>linux vnc
            vncconnect=pigdog.example.com</command></para>

        <para><command>linux vnc
            vncconnect=pigdog.example.com:27910</command></para>

        <para>The system that is to run the listening VNC client must then
          launch the appropriate software to run the VNC client in its listening
          mode.  For the VNC client supplied with &PROD; &PRODVER;, the
          following command is sufficient:</para>

        <para><command>vncviewer -listen</command></para>

        <para>In addition, a new kickstart directive has been added to support
          VNC-based installations:</para>

        <para><command>vnc [--password
            <replaceable>&lt;password&gt;</replaceable>] [--connect
            <replaceable>&lt;host&gt;</replaceable>[:<replaceable>&lt;port&gt;</replaceable>]]</command></para>

        <para>(Where <command>--password
            <replaceable>&lt;password&gt;</replaceable></command> is an optional
            parameter for specifying a VNC password, and <command>[--connect
            <replaceable>&lt;host&gt;</replaceable>[:<replaceable>&lt;port&gt;</replaceable>]]</command>
            is an optional parameter for specifying the host (and optionally,
            port) of a system running a listening VNC client.</para>

        <para>NOTE: If you specify any of the VNC-related boot-time options,
          they will override the corresponding options present in the kickstart
          file.</para>

        <para arch="ppc">&PROD; &PRODVER; for the iSeries and pSeries
          architectures includes support for installation using the VNC remote
          display system, and support for accessing virtual consoles via telnet
          for installation on iSeries.  VNC and telnet clients for a variety of
          platforms are available for download from:</para>
                                                                                
        <para arch="ppc">http://www.ibm.com/servers/eserver/iseries/linux/products.html</para>
      </listitem>

      <listitem arch="i386">
        <para>The XFree86 open source vmware video driver is provided as a
          convenience to our customers and is not supported in any way by
          &FORMAL-RHI; However, any problem reports with the XFree86 open source
          vmware video driver received by &RH; will be forwarded to the
          appropriate VMware staff, so that they can investigate.  Bug fixes
          that become available for this driver may be reviewed by &RH; for
          potential inclusion in future errata and products as time
          permits.</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="input-methods">
    <title>Input Methods</title>

    <para>This section contains general information related to the use of input
      methods.</para>

    <para>An input method allows users to enter non-Western characters into
      common applications such as word-processing, email and instant messaging.
      &PROD; comes with input method support for the following languages:</para>

    <itemizedlist>
      <listitem>
        <para>Chinese (Simplified and Traditional)</para>
      </listitem>

      <listitem>
        <para>Japanese</para>
      </listitem>

      <listitem>
        <para>Korean</para>
      </listitem>
    </itemizedlist>

    <para>The following entries describe the use of input methods for each of
      these languages.</para>

    <itemizedlist>
      <listitem>
        <para>Simplified Chinese</para>
                                                                                
        <para>To enter Simplified Chinese characters, you use the miniChinput
          input method.  To activate the input method, press
          <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>.</para>
                                                                                
        <para>The miniChinput input method supports the following
          modules:</para>

        <para>&middot; intelligent pinyin input</para>

        <para>&middot; gbk pinyin input</para>

        <para>&middot; shuang pin input</para>

        <para>&middot; internal code (gb18030 code) input</para>
                                                                                
        <para>The <filename>miniChinput</filename> package is installed by
          default if Simplified Chinese language support is selected during
          installation.</para>
      </listitem>
                                                                                
      <listitem>
        <para>Traditional Chinese</para>
                                                                                
        <para>To enter Traditional Chinese characters, you use the xcin input
          method.  To activate the input method, press
          <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>.
          Pressing
          <keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap></keycombo> or
          <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Num</keycap></keycombo>
          allows you to change between input modules.</para>
                                                                                
        <para>The xcin input method supports the following modules:</para>

        <para>&middot; CJ</para>

        <para>&middot; Simplex</para>

        <para>&middot; Phone</para>

        <para>&middot; CantonPing</para>

        <para>&middot; Bimsphone</para>

        <para>&middot; Bimspinyin</para>

        <para>&middot; Array30</para>

        <para>&middot; Cantonping (no intonation)</para>
                                                                                
        <para>The <filename>xcin</filename> package is installed by default if
          Traditional Chinese language support is selected during
          installation.</para>
      </listitem>

      <listitem>
        <para>Japanese</para>
                                                                                
        <para>To enter Japanese characters, you use the Canna, FreeWnn or skk
          input methods.  To activate the input method, press
          <keycombo><keycap>Shift</keycap><keycap>Space</keycap></keycombo>.</para>
                                                                                
        <para>The following modules are supported:</para>

        <para>&middot; romaji</para>

        <para>&middot; kana (only Canna &mdash; depends on the configuration
          file)</para>
                                                                                
        <para>The <filename>Canna</filename>, <filename>FreeWnn</filename>, and
          <filename>skkinput</filename> packages are installed by default if
          Japanese language support is selected during installation.</para>
      </listitem>

      <listitem>
        <para>Korean</para>
                                                                                
        <para>To enter Korean characters, you use the ami input method.  To
          activate the input method, press
          <keycombo><keycap>Shift</keycap><keycap>Space</keycap></keycombo>.</para>
                                                                                
        <para>The <filename>ami</filename> package is installed by default if
          Korean language support is selected during installation.</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="general-notes">
    <title>General Notes</title>

    <para>This section contains general notes relating to post-installation
      issues.</para>

    <itemizedlist>
      <listitem arch="ia64">
        <para>&PROD; &PRODVER; for the Itanium 2 Architecture contains the
          <filename>fpswa.efi</filename> binary, which is an EFI (Extensible
          Firmware Interface) driver invoked by the operating system's kernel
          whenever the processor issues FPSWA (Floating-Point Software
          Assistance) requests for floating-point operations that are not fully
          implemented in hardware. The handler provides the result of the
          operation in these cases. Presently, Itanium processors issue FPSWA
          requests mainly when very small numbers (denormalized, or tiny
          numbers) are consumed or produced by floating-point instructions. To
          avoid the performance penalty caused by calls to the handler when tiny
          numbers are produced, the flush-to-zero mode can be turned on, but at
          the cost of a slightly less accurate computation.</para>
                                                                                
        <para>FPSWA is licensed, patented and copyrighted protected material by
          Intel or its supplier under the laws of the United states and other
          countries and international treaty provisions. FPSWA is subject to the
          applicable end user license agreement which can be accessed at
          http://www.redhat.com/licenses/.</para>
      </listitem>

      <listitem>
        <para>The Apache HTTP server has been updated to version 2.0. The
          updated package replaces version 1.3 and has been renamed to
          <filename>httpd</filename>.</para>

        <para>&middot; The <command>auth_ldap</command>,
          <command>mod_put</command>, <command>mod_roaming</command>,
          <command>mod_auth_any</command>, <command>mod_bandwidth</command>,
          <command>mod_throttle</command>, and <command>mod_dav</command>
          modules have been removed.</para>

        <para>&middot; WebDAV functionality is now included with the
          <filename>httpd</filename> package.</para>

        <para>NOTE: Some changes to existing configuration files are needed.
          Third-party Apache modules may also require updating.  Refer to the
          migration guide at
          <filename>/usr/share/doc/httpd-*/migration.html</filename> for more
          details.</para>
      </listitem>

      <listitem arch="i386">
        <para>&PROD; &PRODVER; supports booting over the network using the PXE
          (Pre-Boot Execution Environment) protocol.  As in previous releases it
          is possible to configure &PROD; &PRODVER; as an installation server,
          which makes kernels and image files available for the purpose of
          starting network installations.</para>

        <para>Also available in &PROD; &PRODVER; is support for diskless
          environments.  A diskless server (similar to an installation server)
          makes kernels and image files available to diskless client systems.
          After booting, the diskless client systems mount a root file system
          via NFS, eliminating the need for locally-attached storage.</para>

        <para>The <application>Network Booting Tool</application>
          (<command>redhat-config-netboot</command>) is a graphical
          configuration tool allows you to configure both environments.</para>
      </listitem>

      <listitem>
        <para>The LPRng print spooler has been replaced by CUPS, and the
          <application>Printer Configuration Tool</application>
          (<command>redhat-config-printer</command>) is the recommended tool for
          configuring it.  It may be launched from the <guimenu>System
          Settings</guimenu> menu, using the <guimenuitem>Printing</guimenuitem>
          menu entry.</para>
      </listitem>

      <listitem>
        <para>The <application>Security Level Configuration Tool</application>
            (<command>redhat-config-securitylevel</command>) has been
            simplified.  The previous "<guilabel>High</guilabel>",
            "<guilabel>Medium</guilabel>", and "<guilabel>No
            firewall</guilabel>" settings have been replaced by a more
            straightforward on/off-style control.  In addition, the default
            firewall configuration is now stateful, making it more secure.  The
            new design also makes it possible for users of NIS authentication,
            NFS, and DNS to deploy a firewall with no additional customization
            required (although customization by specifying port and protocol is
            still possible).</para>

        <para>NOTE: This change also applies to the &PROD; installation
          program.</para>
      </listitem>

      <listitem>
        <para><application>GNOME Print Manager</application>, a simple graphical
          print queue management tool, is now included.  It may be launched from
          the <guimenu>System Tools</guimenu> menu, using the <guimenuitem>Print
          Manager</guimenuitem> menu entry.  In addition, when a print job is in
          the queue, an icon will appear in the panel's system notification
          area.</para>
      </listitem>

      <listitem arch="i386;ia64;x86_64;s390x;ppc">
        <para>&PROD; &PRODVER; includes the setarch utility.  Setarch makes it
          possible to change the output produced by the <command>uname</command>
          command.  This is useful for a number of reasons, such as running
          32-bit applications (those written to expect a particular value from
          <command>uname -m</command>) in 64-bit environments.</para>

        <para>The format for the setarch command is:</para>

        <para><command>setarch <replaceable>&lt;arch&gt;</replaceable>
            <replaceable>&lt;command&gt;</replaceable></command></para>

        <para>(Where <command><replaceable>&lt;arch&gt;</replaceable></command>
          represents the desired architecture string (such as
          <command>i386</command>), and
          <command><replaceable>&lt;command&gt;</replaceable></command>
          represents the command to be run while the architecture has been
          modified.)  Note that
          <command><replaceable>&lt;command&gt;</replaceable></command> can be
          omitted, in which case <command>/bin/sh</command> is run.</para>

        <para>In addition, some applications (such as older versions of Java)
          are written to assume a 3GB virtual address space; when run on systems
          with larger virtual address spaces (such as 64-bit AMD64-based
          systems, or 32-bit systems running the hugemem kernel) such
          applications can malfunction.  The setarch utility makes it possible
          to emulate a 3GB virtual address space, allowing such applications to
          run properly:</para>

        <para><command>setarch -3 java</command></para>
      </listitem>

      <listitem arch="ia64">
        <para>Accelerated 3D rendering with DRI has been disabled in &PROD;
          &PRODVER; for the IA64 architecture.  On this architecture,the agpgart
          kernel driver does not function properly; since the DRI subsystem
          depends on this driver, no 3D acceleration is possible.  Note,
          however, that this does not affect unaccelerated 3D rendering or
          third-party drivers that provide their own agpgart
          implementation.</para>
      </listitem>

      <listitem>
        <para>&PROD; &PRODVER; includes the Native POSIX Thread Library (NPTL),
          a new implementation of POSIX threads for Linux. This library provides
          performance improvements and increased scalability.</para>

        <para>This thread library is designed to be binary compatible with the
          old LinuxThreads implementation; however, applications that rely on
          the places where the LinuxThreads implementation deviates from the
          POSIX standard will need to be fixed.  Notable differences include:</para>

        <para>&middot; Signal handling has changed from per-thread signal
          handling to POSIX process signal handling.</para>

        <para>&middot; <command>getpid()</command> returns the same value in all
          threads.</para>

        <para>&middot; Thread handlers registered with
          <command>pthread_atfork</command> are not run if
          <command>vfork()</command> is used.</para>

        <para>&middot; No manager thread.</para>

        <para arch="i386">Applications that are known to have problems using
          NPTL include:</para>

        <para arch="i386">- Sun JRE prior to version 1.4.1</para>
        <para arch="i386">- IBM JRE</para>

        <para>If an application does not work properly with NPTL, it can be run
          using the old LinuxThreads implementation by setting the following
          environment variable:</para>

        <para><envar>LD_ASSUME_KERNEL=<replaceable>&lt;kernel-version&gt;</replaceable></envar></para>

        <para>The following versions are available:</para>

        <para>&middot; 2.4.19 &mdash; Linuxthreads with floating stacks</para>

        <para arch="i386">&middot; 2.2.5 &mdash; Linuxthreads without floating
          stacks</para>

        <para>Note that software using <command>errno</command>,
          <command>h_errno</command>, and <command>_res</command> must
          <command>#include</command> the appropriate header file
          (<filename>errno.h</filename>, <filename>netdb.h</filename>, and
          <filename>resolv.h</filename> respectively) before they are used.
          However, <envar>LD_ASSUME_KERNEL=2.4.19</envar> can be used as a
          workaround until the software can be fixed.</para>
      </listitem>

      <listitem>
        <para>Multi-threaded C++ programs using thread cancellation might need
          to be forced to use the LinuxThreads library using the
          <envar>LD_ASSUME_KERNEL=2.4.19</envar> environment variable setting.
          Otherwise, the program will terminate abnormally if the cancellation
          is acted on (since the generated exception is not caught).</para>
                                                                                
        <para>Newly-written C++ code that uses functions from the C runtime
          environment might have to be adjusted to take the cancellation into
          account.  This can be done by one of the following methods:</para>
                                                                                
        <para>&middot; Not marking the C++ function with
          <command>throw()</command> (so that callers are aware that an
          exception might be thrown) and by compiling the code with exceptions.
          This is the default compilation option; users should not specify
          <command>-fno-exceptions</command> when compiling.</para>
                                                                                
        <para>&middot; Disabling cancellation completely before entering the
          functions that call the cancel-able C runtime functions.  This can be
          done with the following call:</para>
                                                                                
        <para><command>pthread_setcancelstate (PTHREAD_CANCEL_DISABLE,
            &amp;oldstate)</command></para>
                                                                                
        <para>After the C functions are called cancellation can be enabled again
          with the following call:</para>
                                                                                
        <para><command>pthread_setcancelstate (oldstate, NULL)</command></para>
                                                                                
        <para>NOTE: At this point the cancellations are acted upon and therefore
          the function calling pthread_setcancelstate() must be compiled with
          exceptions enabled and must be marked as throwing exceptions.</para>
      </listitem>

      <listitem>
        <para>A new system message has been added to &PROD; &PRODVER;:</para>

        <para><computeroutput>application bug:
            <replaceable>&lt;app-name&gt;</replaceable>(<replaceable>&lt;app-pid&gt;</replaceable>)
            has SIGCHLD set to SIG_IGN but calls wait().  (see the NOTES section
            of 'man 2 wait'). Workaround activated.</computeroutput></para>

        <para>This message (which is displayed on the system console and/or in
          the system log files) indicates that the application is not completely
          standards compliant with respect to its handling of child processes.
          If you notice this message, you should alert the application's
          developers.</para>
      </listitem>

      <listitem>
        <para>&PROD; &PRODVER; includes the capability of producing Position
          Independent Executables (PIE) for C, C++, and Java.  This feature is
          enabled with the <command>-fpie</command> and <command>-fPIE</command>
          GCC options to compile, which are similar in usage to the
          <command>-fpic</command> and <command>-fPIC</command> options,
          respectively, and at link time with the <command>-pie</command>
          option.</para>
      </listitem>

      <listitem>
        <para>The <command>fileutils</command>, <command>textutils</command>,
          <command>sh-utils</command>, and <command>stat</command> packages have
          been replaced by the newer <command>coreutils</command> package.</para>
      </listitem>

      <listitem>
        <para>The RPMs containing the <application>Network Administration
            Tool</application> (<command>redhat-config-network</command>) have
            changed names and functions.  The
            <filename>redhat-config-network</filename> RPM contains the tool's
            graphical user interface, while
            <filename>redhat-config-network-tui</filename> contains the tool
            itself (along with its text-based user interface).</para>
      </listitem>

      <listitem>
        <para>Support for XHTML1 &mdash; the reformulation of HTML in XML
          &mdash; has been improved.  This has been done by adding the
          <command>xhtml1-dtd</command> package, installing the DTDs in the
          system catalog, and adding native support in the
          <command>libxml2</command> and <command>xsltproc</command>
          tools.</para>
      </listitem>

      <listitem>
        <para>The XML toolkit have been extended to support Relax-NG validation,
          and streaming of large files.</para>
      </listitem>

      <listitem>
        <para>The OProfile system-wide profiler has been added to &PROD;
          &PRODVER;.  OProfile is a programmer's tool for analyzing system
          performance, using special hardware built into many modern computers.
          Documentation for OProfile exists in the <command>oprofile</command>
          package; after installing &PROD; &PRODVER;, issue the command
          <command>rpm -qd oprofile</command> to obtain a listing of the
          available documentation.  Visit the OProfile website at
          http://oprofile.sourceforge.net for more details.</para>

        <para>NOTE: The kernel support for OProfile in &PROD; &PRODVER; is based
          on the backported code from the 2.5 development kernel.  Therefore, if
          you refer to the OProfile documentation, keep in mind that features
          listed as being 2.5-specific actually apply to the &PROD; kernel, even
          though the kernel version is 2.4.  Likewise, this means that features
          listed as being specific to the 2.4 kernel do <emphasis>not</emphasis>
          apply to the &PROD; kernel.</para>
      </listitem>

      <listitem>
        <para>At the present time, the X Window System makes use of two font
          subsystems, each with different characteristics:</para>

        <para>&middot; The original (15+ year old) subsystem is referred to as
          the "core X font subsystem".  Fonts rendered by this subsystem are not
          anti-aliased, are handled by the X server, and have names like:</para>

        <para>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</para>

        <para>The newer font subsystem is known as "fontconfig", and allows
          applications direct access to the font files.  Fontconfig is often
          used along with the "Xft" library, which allows applications to render
          fontconfig fonts to the screen with antialiasing.  Fontconfig uses
          more human-friendly names like:</para>

        <para>Luxi Sans-10</para>

        <para>Over time, fontconfig/Xft will replace the core X font subsystem.
          At the present time, applications using the Qt 3 or GTK 2 toolkits
          (which would include KDE and GNOME applications) use the fontconfig
          and Xft font subsystem; most everything else uses the core X
          fonts.</para>

        <para>In the future, &RH; may support only fontconfig/Xft in place of
          the XFS font server as the default local font access method.</para>

        <para>NOTE: One exception to the font subsystem usage outlined above is
          OpenOffice.org, which uses its own font rendering technology.</para>

        <para>If you wish to add new fonts to your &PROD; &PRODVER; system, you
          must be aware that the steps necessary depend on which font subsystem
          is to use the new fonts.  For the core X font subsystem, you
          must:</para>

        <para>1. Create the <filename>/usr/share/fonts/local/</filename>
          directory (if it does not already exist):</para>

        <para><command>mkdir /usr/share/fonts/local/</command></para>

        <para>2. Copy the new font file into
          <filename>/usr/share/fonts/local/</filename></para>

        <para>3. Update the font information by issuing the following commands
          (note that, due to formatting restrictions, the following commands may
          appear on more than one line; in use, each commands should be entered
          on a single line):</para>

        <para><command>ttmkfdir -d /usr/share/fonts/local/ -o
            /usr/share/fonts/local/fonts.scale</command></para>

        <para><command>mkfontdir /usr/share/fonts/local/</command></para>

        <para>4. If you had to create
          <filename>/usr/share/fonts/local/</filename>, you must then add it to
          the X font server (xfs) path:</para>

        <para><command>chkfontpath --add
            /usr/share/fonts/local/</command></para>

        <para>Adding new fonts to the fontconfig font subsystem is more
          straightforward; the new font file only needs to be copied into the
          <filename>/usr/share/fonts/</filename> directory (individual users can
          modify their personal font configuration by copying the font file into
          the <filename>~/.fonts/</filename> directory).</para>

        <para>After the new font has been copied, use
          <command>fc-cache</command> to update the font information cache:</para>

        <para><command>fc-cache
            <replaceable>&lt;directory&gt;</replaceable></command></para>

        <para>(Where
          <command><replaceable>&lt;directory&gt;</replaceable></command> would
          be either the <filename>/usr/share/fonts/</filename> or
          <filename>~/.fonts/</filename> directories.)</para>

        <para>Individual users may also install fonts graphically, by browsing
          <command>fonts:///</command> in <application>Nautilus</application>,
          and dragging the new font files there.</para>

        <para>NOTE: If the font filename ends with "<filename>.gz</filename>",
          it has been compressed with <command>gzip</command>, and must be
          decompressed (with the <command>gunzip</command> command) before the
          fontconfig font subsystem can use the font.</para>
      </listitem>

      <listitem>
        <para>Due to the transition to the new font system based on
          fontconfig/Xft, GTK+ 1.2 applications are not affected by any changes
          made via the <guilabel>Font Preferences</guilabel> dialog.  For these
          applications, a font can be configured by adding the following lines
          to the file <filename>~/.gtkrc.mine</filename>:</para>


        <para><command>style "user-font" {</command></para>
        <para><command>fontset =
            "<replaceable>&lt;font-specification&gt;</replaceable>"</command></para>
        <para><command>}</command></para>
        <para><computeroutput> </computeroutput></para>
        <para><computeroutput>widget_class "*" style "user-font"</computeroutput></para>

        <para>(Where
          <command><replaceable>&lt;font-specification&gt;</replaceable></command>
          represents a font specification in the style used by traditional X
          applications, such as
          "<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>".)</para>
      </listitem>

      <listitem>
        <para>By default, the Sendmail mail transport agent (MTA) does not
          accept network connections from any host other than the local
          computer.  If you want to configure Sendmail as a server for other
          clients, you must edit <filename>/etc/mail/sendmail.mc</filename> and
          change the <parameter>DAEMON_OPTIONS</parameter> line to also listen
          on network devices (or comment out this option entirely using the
          <command>dnl</command> comment delimiter).  You must then regenerate
          <filename>/etc/mail/sendmail.cf</filename> by running the following
          command (as root):</para>

        <para><command>make -C /etc/mail</command></para>

        <para>Note that you must have the <filename>sendmail-cf</filename>
          package installed for this to work.</para>
      </listitem>

      <listitem>
        <para>The default FTP server in &PROD; &PRODVER; is now
          <command>vsftpd</command>, and runs as a SysV service.</para>
      </listitem>

      <listitem>
        <para>Change to <command>fdisk</command>'s interpretation of partition
          size multipliers</para>

        <para>The <command>fdisk</command> command now has a different
          interpretation of the size multipliers that may be used when creating
          new disk partitions.  The size suffixes <command>K</command>,
          <command>M</command>, and <command>G</command> now refer to multiples
          of thousands, millions, and billions of bytes, respectively.  This is
          more consistent with the disk size specifications provided by disk
          drive manufacturers.</para>

        <para>Therefore, if a user wants to create a 512MB partition, the size
          value specified with an "M" suffix would be 512*1024*1024
          (536,870,912), rounded up to a multiple of a million (537,000,000),
          and then divided by a million (537), resulting in a size specification
          of <command>+537M</command>.</para>
      </listitem>

      <listitem>
        <para>While compatibility for executables and dynamic shared objects
          (DSOs, also known as shared libraries) created on earlier &RHL; and
          &PROD; is supported, the same does not apply to object
          (<filename>.o</filename>) files.  Object files created on earlier
          versions can be used on &PROD; &PRODVER; to create new executables or
          DSOs only if they were built without including any system header
          files.</para>

        <para>Otherwise, the only way to use these files is to link the object
          files to the compatibility version of glibc (part of the
          <filename>compat-glibc</filename> package).  Any newly-generated
          object file must use the headers from the compatibility package.  For
          example, to compile object files, add the following to the beginning
          of the compiler command line:</para>

        <para><command>-I/usr/lib/i386-redhat-linux7/include</command></para>

        <para>To link the resulting executable or DSO add the following to the
          command line:</para>

        <para><command>-L/usr/lib/i386-redhat-linux7/lib</command></para>

        <para>Any mixture of old object files and those compiled against the
          current system headers can have negative results.  Linking old object
          files with the regular system libraries may result in completely
          unusable executables or executables with subtle bugs (such as memory
          corruption).</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 id="kernel-notes">
    <title>Kernel Notes</title>

    <para>This section contains notes relating to the &PROD; &PRODVER;
      kernel.</para>

    <itemizedlist>
      <listitem>
        <para>The &PROD; &PRODVER; kernel makes use of a new kernel packaging
          technique.  Due to the almost limitless variety of available hardware,
          it is not possible for &RH; to fully support all hardware components.
          Therefore, while kernel modules for fully-supported hardware remain in
          the standard <filename>kernel</filename> packages, a series of new
          <firstterm>unsupported</firstterm> kernel packages are included with
          &PROD; &PRODVER;.</para>

        <para>For each kernel package shipped there is a corresponding
          unsupported kernel package.  For example, the unsupported kernel
          package for
          <filename>kernel-smp-2.4.21-3.EL.i686.rpm</filename>
          is
          <filename>kernel-smp-unsupported-2.4.21-3.EL.i686.rpm</filename>.</para>

        <para>NOTE: The unsupported kernel packages are not installed by the
          &PROD; installation program; therefore, in order to use unsupported
          kernel modules, you must manually install the unsupported kernel
          package corresponding to the kernel your system uses.</para>

        <para>After installing the appropriate unsupported kernel package, you
          must use the following command to update the module dependency tree
          and your initrd:</para>

        <para><command>/sbin/new-kernel-pkg --mkinitrd --depmod --install
            <replaceable>&lt;kernel-version&gt;</replaceable></command></para>

        <para>(Where
          <command><replaceable>&lt;kernel-version&gt;</replaceable></command>
          represents the version of the installed kernel.)</para>

        <para>Drivers contained within the unsupported kernel packages are
          provided on a best-effort basis. This means that updates and upstream
          fixes may or may not be incorporated over time, and are not covered by
          the same support expectations as the fully supported drivers. Custom
          support arrangements covering drivers in the unsupported package may
          be worked out with Red Hat in some situations.</para>
      </listitem>

      <listitem>
        <para>The &PROD; &PRODVER; kernel includes more accurate process timing
          functionality.  This new process timing mode uses timestamps to
          provide more accurate timing of idle and process times.  When enabled,
          this information is available via the usual monitoring tools (such as
          <command>top</command>, <command>vmstat</command>, and
          <command>procinfo</command>), and the <command>getrusage</command>
          system call.</para>

        <para>To enable timestamp-based process timing, you must boot your
          system using the following boot-time option:</para>

        <para><command>process_timing=<replaceable>&lt;value&gt;</replaceable></command></para>

        <para>Where <command><replaceable>&lt;value&gt;</replaceable></command>
          can be one or more of the following, with multiple values separated by
          commas:</para>

        <para>&middot; <command>irq</command> &mdash; Use timestamps to account
          for IRQ interrupts</para>

        <para>&middot; <command>softirq</command> &mdash; Use timestamps to
          account for softirq time in the kernel</para>

        <para>&middot; <command>process</command> &mdash; Allow processes to
          enable timestamp-based process timing on themselves (It is then
          disabled for all processes by default)</para>

        <para>&middot; <command>all_process</command> &mdash; Force
          timestamp-based process timing on all processes (including the idle
          tasks)</para>

        <para>&middot; <command>everything</command> &mdash; Same as specifying
          <command>irq,softirq,all_process</command></para>

        <para>If the system is booted with the <command>process</command>
          option, no processes initially have timestamp-based process timing
          enabled by default.  However, processes can use the
          <command>prctl()</command> system call to both determine and modify
          their process timing mode.  The system call to determine the process
          timing mode is:</para>

        <para><command>mode = prctl(PR_GET_TIMING, 0, 0, 0, 0);</command></para>

        <para>The system call to set the process timing mode is:</para>

        <para><command>status = prctl(PR_SET_TIMING,
            <replaceable>&lt;mode&gt;</replaceable>, 0, 0, 0)</command></para>

        <para>(Where <command><replaceable>&lt;mode&gt;</replaceable></command>
          is <command>PR_TIMING_STATISTICAL</command> for enabling the
          traditional process timing mode, or
          <command>PR_TIMING_TIMESTAMP</command> for enabling timestamp-based
          process timing mode .)  Note that enabling one process timing mode
          automatically disables the other.</para>

        <para>NOTE: The <command>prctl()</command> system call can only be used
          on systems booted with the <command>process</command> value.
          Otherwise, the system call will return <command>-EINVAL</command>.
          This includes attempts to disable timestamp-based process timing on
          systems booted with the <command>all_process</command> option.</para>

        <para>A child process's timing mode is inherited from its parent;
          however, the child can use the <command>prctl()</command> system call
          to modify its own process timing mode (subject to the conditions
          outlined in the previous note).</para>
      </listitem>

      <listitem>
        <para>The BusLogic driver (for certain Mylex SCSI host bus adapters) is
          provided in the standard kernel packages, but it is only supported
          when the kernel is a guest operating system within
          <trademark>VMWare</trademark> virtual machine software. This is
          because VMWare presents an emulated SCSI adapter to the BusLogic
          driver, and this environment has been thoroughly tested and supported
          by VMWare, Inc. The BusLogic driver is not supported on physical SCSI
          host adapters because this driver has not been maintained in the
          official Linux kernel for several years, and has not received
          extensive testing in the &RHEL; kernel.</para>
      </listitem>

      <listitem>
        <para>The qla1280 driver (for the Qlogic ISP1x80/1x160 SCSI adapters)
          has not been maintained in the official Linux kernel for many years.
          As a result, although this driver works correctly with the Intel x86
          architecture, it does not work correctly with other architectures.
          Therefore, &RH; only supports the qla1280 driver on Intel x86
          platforms.</para>
      </listitem>

      <listitem arch="ia64;s390;s390x;x86_64;ppc">
        <para>The netdump facility is currently disabled.  The
          <filename>netdump</filename> package is included so that, if the
          netdump facility is enabled in a future kernel update, netdump
          functionality will be available after the netdump-capable kernel is
          installed.</para>
      </listitem>

      <listitem arch="i386">
        <para>Systems based on the Intel I865/I875 chipsets and utilizing these
          chipsets' ICH5 integrated AC97 audio functionality may experience a
          failure to produce any sound when running &PROD; &PRODVER;.</para>

        <para>The ICH5 integrated AC97 audio subsystem can be identified by
          reviewing the output from the following command:</para>

        <para><command>/sbin/lspci -n</command></para>

        <para>The PCI vendor:device code for the ICH5 AC97 audio is
          8086:24d5.</para>
      </listitem>

      <listitem arch="i386">
        <para>Systems based on the Intel I865/I875 chipsets and utilizing these
          chipsets' ICH5 Serial ATA (SATA) functionality should configure the
          BIOS settings for their SATA devices to "enhanced" or "native" mode.
          "Legacy" or "combined" mode SATA is supported, but discouraged.</para>

        <para>NOTE: Not all BIOS implementations offer the ability to change
          these settings.</para>
      </listitem>

      <listitem>
        <para>New kernel support has been added to provide IPv6 capabilities.
          This support is consistent with the upstream 2.6-based implementation
          as of 2.6.0-test3.</para>
                                                                           
        <para>Note that &RH; will not be implementing additional IPv6 features
          (such as any of the draft standards for Mobile IP) for this release of
          &PROD;; our goal is to focus exclusively on bugs in existing
          features.</para>
      </listitem>

      <listitem>
        <para>EA (Extended Attributes) and ACL (Access Control Lists)
          functionality is now available for ext3 file systems.  In
          addition, ACL functionality is available for NFS.</para>

        <para>&PROD; &PRODVER; contains a kernel providing EA and ACL support
          for the ext3 file system.  Protocol extensions were also added to NFS
          to support ACL-related operations for NFS-exported file
          systems.</para>

        <para>To enable ACLs on a locally-mounted file system, the file system
          must be mounted with the <command>-o acl</command> mount option.  By
          default, the NFS server makes use of ACLs if the underlying file
          system supports them.  To disable this feature, you must specify the
          <command>no_acl</command> export option.</para>

        <para>EAs are used intrinsically for ACL support.  To use EAs
          separately, the file system must be mounted with the <command>-o
          user_xattr</command> mount option.</para>

        <para>The support for this comes in several packages:</para>

        <para>&middot; kernel &mdash; Provides support for storing EAs and ACLs
          on disk for ext3 file systems, as well the system calls to manipulate
          EAs and ACLs.  Finally, the kernel package provides the mechanisms to
          enforce ACLs on file access.</para>

        <para>&middot; e2fsprogs &mdash; Includes knowledge of the new on-disk
          extended attribute formats so that <command>fsck</command> can check
          file systems using the new feature.</para>

        <para>&middot; attr, libattr &mdash; Provides access to extended
          attributes attached to files.</para>

        <para>&middot; acl, libacl &mdash; Provides tools to set, modify, and
          query the ACLs set on files.</para>

        <para>&middot; libattr-devel, libacl-devel &mdash; Libraries and include
          files to build programs using the acl and attr libraries.</para>

        <para>&middot; star &mdash; An archiving tool which can create and
          unpack both <command>tar</command> and <command>pax</command> format
          archives, and which can backup and restore EAs and ACLs.</para>

        <para>NOTE: The options available for <command>star</command> are not
          completely equivalent with those available for <command>tar</command>;
          therefore, make sure you review the <command>star</command> man
          page.</para>

        <para>&middot; samba &mdash; Samba can export ACL functionality in this
          release.  Refer to the samba documentation for information on how to
          enable this in your configuration.</para>

        <para>In addition, the <command>coreutils</command> package has been
          updated so that the <command>cp</command> and <command>mv</command>
          commands copy the ACLs and EAs associated with a file.</para>

        <para>For more information on setting and reading ACLs, refer to the
          <command>setfacl</command> and <command>getfacl</command> man pages.
          General information about ACLs can be found in the
          <command>acl</command> man page.</para>

        <para>NOTE: The normal <command>tar</command> and
          <command>dump</command> commands will <emphasis>not</emphasis> backup
          ACLs and EAs.</para>

        <para>Compatibility with older systems:</para>

        <para>Any ext3 file system that has not had any ACLs or EAs set on it
          will work unchanged on older kernels, and can be checked using older
          e2fsprogs utilities.</para>

        <para>Once an EA or an ACL has been set on any file on a given file
          system, that file system will acquire the <command>ext_attr</command>
          attribute.  This attribute can be observed by using the following
          command:</para>

        <para><command>tune2fs -l
            <replaceable>&lt;filesystemdevice&gt;</replaceable></command></para>

        <para>A file system that has acquired the <command>ext_attr</command>
          attribute can be mounted with older kernels, but obviously those
          kernels are incapable of enforcing any ACLs that have been set.</para>

        <para>NOTE: Older versions of the file system checking program
          <command>e2fsck</command> refuse to check any file system with the
          <command>ext_attr</command> attribute.  This corresponds to versions
          of the <command>e2fsprogs</command> package prior to 1.22.</para>
      </listitem>

      <listitem>
        <para>The &PROD; &PRODVER; kernel now includes support for NFS over TCP.
          To use NFS over TCP, you must include the "<command>-o tcp</command>"
          option to <command>mount</command> when mounting the NFS-exported file
          system on the client system.</para>

        <para>NOTE: The default transport protocol for NFS remains UDP. Use the
          <command>mount</command> command with the "<command>-o tcp</command>"
          option to mount an NFS-exported file system using TCP; otherwise, UDP
          will be used by default.</para>
      </listitem>

      <listitem>
        <para>In this kernel, the following command has been added to scan for
          new devices on all attached SCSI host adapters:</para>

        <para><command>echo "scsi scan-new-devices" &gt;
            /proc/scsi/scsi</command></para>

        <para>This is currently a non-standard addition. In future kernels a
          different parameter may be used to provide the same capability, or the
          semantics of the same parameter
          (<computeroutput>scan-new-devices</computeroutput>) may change, as
          &RH; tracks the official Linux kernel in this area.</para>
      </listitem>

      <listitem arch="ppc">
        <para>Logical Partitions on iSeries platforms that have been configured
          to use more than one processor (either directly or from a shared pool)
          may wish to share interrupt processing across all processors.  Doing
          so may improve performance for some workloads. By default, &PROD; will
          only service interrupts on one processor in the LPAR.  To change this
          behavior, the following boot-time option must be entered:</para>

        <para><command>spread_lpevents=<replaceable>&lt;N&gt;</replaceable></command></para>

        <para>Where <command><replaceable>&lt;N&gt;</replaceable></command>
          represents the number of processors in the LPAR that should process
          interrupts.  This number should be less than or equal to
          either:</para>

        <para>&middot; The number of virtual processors (if a shared processor
          pool is being used)</para>

        <para>&middot; The number of direct processors assigned to the LPAR</para>
      </listitem>

      <listitem>
        <para>Change in permission semantics for user-mode memory locking</para>
                                                                                
        <para>&PROD; &PRODVER; now allows non-root processes to use user-mode
          memory locking system calls within the bounds of their
          <command>RLIMIT_MEMLOCK</command> resource limit.  The default limit
          is one physical page per process.  Limits can be reassigned by the
          system administrator on a per user-id, per group-id, or system-wide
          basis via the <filename>/etc/security/limits.conf</filename> file.
          Root processes are no longer constrained by this resource
          limit.</para>
                                                                                
        <para>The system calls affected by this change in semantics are
          <command>mlock(2)</command>, <command>munlock(2)</command>,
          <command>mlockall(2)</command>, <command>munlockall(2)</command>, and
          <command>shmctl(2)</command>.</para>
      </listitem>
    </itemizedlist>
  </sect1>
  <ackno>(
    <emphasis arch="i386">x86</emphasis>
    <emphasis arch="ia64">ia64</emphasis>
    <emphasis arch="s390">s390</emphasis>
    <emphasis arch="s390x">s390x</emphasis>
    <emphasis arch="x86_64">amd64</emphasis>
    <emphasis arch="ppc">ppc</emphasis>
    )</ackno>
</article>


--- NEW FILE splash-it.xml ---
<section id="sn-splash">
  <title>Welcome to &FC; &LOCALVER;</title>
  <caution>
    <title>Information Out-of-Date</title>
    <para>
      The content in this section needs to be updated for &DISTRO;
      &DISTROVER;
    </para>
  </caution>
  <para>
    &FC; is a completely free, user friendly, and secure general purpose
    platform based on Linux.  The &FP; is an open source project that
    pioneers leading edge technology and concepts sponsored by &RH; and
    supported by the &FED; community.
  </para>
  <tip>
    <title>Latest Release Notes on the Web</title>
    <para>
      These release notes may be updated.  Visit <ulink
	url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>
      to view the latest release notes for &DISTRO; &DISTROVER;.
    </para>
  </tip>

<!-- save for when the FIG is actually updated
  <note>
    <title>Installation Guide Updated</title>
    <para>
      New for this release is the <citetitle>&FC; &LOCALVER;
	&IG;</citetitle>.  This guide is useful for users of all levels
      and can be found at this URL:
    </para>
    <para>
      <ulink url="http://fedora.redhat.com/docs/fedora-install-guide-en/">http://fedora.redhat.com/docs/fedora-install-guide-en/</ulink>
    </para>
  </note>  
-->
  <para>
    Refer to these webpages to find out more information about &FED;:
  </para>
  <itemizedlist>
<!-- FIXME Return when the section is updated
    <listitem>
      <para>
	<xref linkend="sn-new-in-fc"/>
      </para>
    </listitem>
-->
    <listitem>
      <para>
	<xref linkend="sn-intro"/> &mdash; Technical release notes
      </para>
    </listitem>
    <listitem>
      <para>
	Help and Support (<ulink
	  url="http://fedora.redhat.com/participate/communicate/">http://fedora.redhat.com/participate/communicate/</ulink>) 
      </para>
    </listitem>
    <listitem>
      <para>
	Participate in the &FP; (<ulink
	  url="http://fedora.redhat.com/participate/">http://fedora.redhat.com/participate/</ulink>) 
      </para>
    </listitem>
    <listitem>
      <para>
	About the &FP; (<ulink
	  url="http://fedora.redhat.com/about/">http://fedora.redhat.com/about/</ulink>)
      </para>
    </listitem>
  </itemizedlist>
<!-- commented out until the content can be updated
  <section id="sn-new-in-fc">
    <title>New in &FC; &LOCALVER;</title>
    <para>
      &FC; &LOCALVER; is the latest version of the free and popular &FC;
      platform with a number of unique features and significant
      improvements over previous versions.  This section provides an
      overview of the major highlights in this release.
    </para>
    <itemizedlist>
      <listitem>
	<para>
	  Desktop Enhancements &mdash; The &FED; desktop brings to you
	  the latest software such as GNOME 2.10 and KDE 3.4 with a new
	  look and feel.  GNOME has the new simple and elegant Clearlooks
	  default theme that is inspired by the classic Red Hat
	  Bluecurve theme, as shown in <xref
	  linkend="ex-desktop-screenshot-clearlooks"/>.
	</para>
	<example id="ex-desktop-screenshot-clearlooks">
	  <title>New desktop featuring Clearlooks and Evince</title>
	  <mediaobject id="txt-fedora-desktop-screenshot">
	    <imageobject>
	      <imagedata fileref="./figs/Fedora_Desktop.eps" format="EPS"/>
	    </imageobject>
	    <imageobject>
	      <imagedata fileref="./figs/Fedora_Desktop.png" format="PNG"/>
	    </imageobject>
	    <textobject>
	      <para>
		Screenshot of Fedora desktop showing Firefox in the
		background and the new universal document viewer Evince
		in the foreground.  Evince is displaying Lawrence
		Lessig's Free Culture.
	      </para>
	    </textobject>
	  </mediaobject>
	</example>      
      </listitem>
      <listitem>
	<para>
	  Improved Productivity
	</para>
	<itemizedlist>
	  <listitem>
	    <para>
	      Evince (<ulink
		url="http://www.gnome.org/projects/evince/">http://www.gnome.org/projects/evince/</ulink>) 
	      is a document viewer for multiple document formats such as
	      pdf, postscript, and many others.  Evince replaces a whole
	      category of document viewers with a single simple
	      application.
	    </para>
	  </listitem>
	  <listitem>
	    <para>
	      OpenOffice.org 2.0 (<ulink
		url="http://www.openoffice.org/product2/index.html">http://www.openoffice.org/product2/index.html</ulink>) 
	      is an office productivity suite.  This latest version
	      includes several enhancements such as improved Microsoft
	      Office compatibility, completely revamped Impress
	      presentation software, and native support for the
	      OpenDocument format. This version also introduces Base, a
	      fully integrated database management software. You can
	      find the extensive list of new features at <ulink
		url="http://marketing.openoffice.org/2.0/featureguide.html">http://marketing.openoffice.org/2.0/featureguide.html</ulink>.</para>
	  </listitem>
	  <listitem>
	    <para>
	      Eclipse 3.1 is an open and extensible software development
	      platform that is an Integrated Development Environment
	      (<acronym>IDE</acronym>) useful for programming in any
	      language. 
	    </para>
	  </listitem>
	</itemizedlist>
      </listitem>
      <listitem>
	<para>
	  Support for PowerPC (PPC) Architecture &mdash; Refer to <xref
	    linkend="sn-hardware-reqs-ppc"/> and <xref
	    linkend="sn-install-notes-ppc"/>.
	</para>
      </listitem>
      <listitem>
	<para>
	  Improved Security &mdash; &SEL; is a security architecture
	  that protects applications and users through finely grained
	  mandatory security controls.  The default targeted policy has
	  been improved to cover 80 additional daemons. You can read
	  more in the technical release notes
	  <xref linkend="sn-overview"/>.
	</para>
      </listitem>
      <listitem>
	<para>
	  Integrated Clustering Technology &mdash; Global File System
	  (<acronym>GFS</acronym>) is an open source clustering file
	  system that allows a cluster of Linux servers to share a
	  common storage pool. &FC; &LOCALVER; has integrated GFS within
	  the system to manage your storage in an efficient way.  You
	  can read more at <ulink
	    url="http://www.redhat.com/software/rha/gfs/">http://www.redhat.com/software/rha/gfs/</ulink> 
	  and <ulink
	    url="http://www.redhat.com/docs/manuals/enterprise/">http://www.redhat.com/docs/manuals/enterprise/</ulink>.
	</para>
      </listitem>
      <listitem>
	<para>
	  Built-in Virtualization &mdash; Xen is a virtual machine that
	  can securely run multiple operating systems in their own
	  sandboxed domains.  Xen has been integrated into &FC; to work
	  in a seamless fashion.  You can read more about Xen at <ulink
	    url="http://fedora.redhat.com/projects/virtualization/">http://fedora.redhat.com/projects/virtualization/</ulink>.
	</para>
      </listitem>
      <listitem>
	<para>
	  Solid Platform &mdash; &FC; &LOCALVER; includes and integrates
	  the latest 4.0 version of GNU Compiler Collection, which has a
	  rewritten optimization infrastructure and improved support for
	  a native open source Java software stack.  This stack includes
	  parts of OpenOffice.org 2.0., Eclipse, and Apache Jakarta,
	  among others.
	</para>
      </listitem>
    </itemizedlist>
  </section>
  <section id="sn-why-no-mp3">
    <title>MP3 Codecs and Other Patented or Closed Source Software</title>
    <para>
      This section is a brief explanation of why certain software is not
      included in &FC; or &FEX;.  This information was drawn directly
      from the canonical wiki page:
    </para>
    <para>
      <ulink
	url="http://fedoraproject.org/wiki/ForbiddenItems">http://fedoraproject.org/wiki/ForbiddenItems</ulink>
    </para>
    <para>
      A frequent question of the &FP; is why certain items are not
      included in &FC; or &FEX;. This briefly explains some of the
      reasons.
    </para>
    <para>
      Other items, such as file systems support, requires community
      participation.  For more information, refer to <ulink
	url="http://fedoraproject.org/wiki/Wishlist">http://fedoraproject.org/wiki/Wishlist</ulink>
    </para>
    <variablelist>
      <varlistentry>
	<term>NTFS</term>
	<listitem>
	  <para>
	    NTFS Support is not included in the &FC; kernel because of
	    patent concerns. Using a file system natively supported by
	    Linux such as ext3 is a better option. If you must share
	    files between Windows and Linux on a single system, use
	    FAT/FAT32 (vfat) instead. For sharing across a network,
	    Samba is a good option.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>MP3 encode/decode functionality</term>
	<listitem>
	  <para>
	    MP3 support is not included in any &FC; application because
	    MP3 is heavily patented in several regions including the
	    United States. The patent holder is unwilling to give an
	    unrestricted patent grant, as required by the GPL. Other
	    platforms might have paid the royalty and/or included
	    proprietary software. Other Linux distributions not based in
	    a region affected by the patent might ship MP3
	    decoders/encoders. However, &FC; cannot and does not ship
	    MP3 decoders/encoders in order to serve the goal of shipping
	    only free and open source software. Using other open source
	    formats such as Ogg Vorbis (a lossy codec that has better
	    quality than MP3) or FLAC (a lossless codec) is highly
	    recommended.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>NVIDIA 3D drivers</term>
	<listitem>
	  <para>
	    The NVIDIA 3D drivers are closed source. &FC; does not
	    include proprietary binaries. Consider using an Intel or any
	    other manufacturer that supports open source cards with full
	    specifications and/or source code.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>ATI 3D drivers</term>
	<listitem>
	  <para>
	    The ATI 3D drivers are closed source. &FC; does not include
	    proprietary binaries. Consider using an Intel or any other
	    manufacturer that supports open source cards with full
	    specifications and/or source code.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>RealPlayer</term>
	<listitem>
	  <para>
	    RealPlayer is a closed source application. &FC; does not
	    include proprietary binaries. Consider using open source
	    codecs that do not have patent restrictions.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>DVD video playback</term>
	<listitem>
	  <para>
	    DVD video playback (of CSS encrypted DVDs) may violate the
	    US DMCA (refer to <ulink
	      url="http://en.wikipedia.org/wiki/DMCA">http://en.wikipedia.org/wiki/DMCA</ulink>) 
	    because it may be considered circumventing an encryption
	    mechanism. Additionally, MPEG2 is a patented codec, so even
	    DVDs without encryption cannot be played. Consider using
	    open source unencrypted mediums such as Ogg Theora formats.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>Mono</term>
	<listitem>
	  <para>
	    Mono packages are not currently included due to potential
	    legal issues. (Pending more input.) Applications can be
	    written in other languages that are open source, such as
	    Python, Perl, or Ruby. Java is cross-platform and GCJ is a
	    relatively mature open source implementation of it. These
	    are not direct one-to-one equivalents with .NET but might
	    serve your purpose.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>Cryptology (mcrypt)</term>
	<listitem>
	  <para>
	    Some cryptology related packages such as mcrypt are not
	    included within &FC; due to US export restrictions. Consider
	    using non-restricted cryptographical methods instead.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>szip</term>
	<listitem>
	  <para>
	    The szip license is too restrictive for inclusion in &FEX;.
	    Use other open source alternatives.
	  </para>
	</listitem>
      </varlistentry>
    </variablelist>
    <para>
      In conclusion:
    </para>
    <itemizedlist>
      <listitem>
	<para> If it is proprietary, it cannot be included in &FED;.
	</para>
      </listitem>
      <listitem>
	<para>
	  If it is legally encumbered, it cannot be included in &FED;.
	</para>
      </listitem>
      <listitem>
	<para>
	  If it violates US Federal law, it cannot be included in &FED;.
	</para>
      </listitem>
    </itemizedlist>
    <para>
      Of course, the logical followup is: "But I want to get foo and do
      bar, how can I do one of the items listed above?"
    </para>
    <para>
      The unofficial <ulink
	url="http://fedorafaq.org">http://fedorafaq.org</ulink> provides
      useful answers on commonly asked questions. However, these are
      completely unsupported by the &FP;. The &FP; encourages using free
      and open source software.
    </para>
    <para>
      The binary only drivers can be acquired from the vendors. You can
      find many interesting things with Google.
    </para>
  </section>
-->
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE xorg-it.xml ---
<section id="sn-xwindows">
  <title>X Window System (Graphics)</title>
  <caution>
    <title>Information Out-of-Date</title>
    <para>
      The content in this section needs to be updated for &DISTRO;
      &DISTROVER;
    </para>
  </caution>
  <para>
    This section contains information related to the X Window System
    implementation provided with &DISTRO;.
  </para>
  <section id="sn-xwindows-xorg">
    <title><filename>xorg-x11</filename></title>
    <para>
      Users new to the X.org X11 implementation should take note of a
      few differences between it and the XFree86.org X11 implementation
      which shipped in previous &RH; and &FED; operating systems. In
      particular, the names of some files have changed:
    </para>
    <para>
      X Server Binary:
    </para>
    <itemizedlist>
      <listitem>
	<para>XFree86 X11: <filename>XFree86</filename></para>
      </listitem>
      <listitem>
	<para>X.org X11: <filename>Xorg</filename></para>
      </listitem>
    </itemizedlist>
    <para>
      X Server Configuration File:
    </para>
    <itemizedlist>
      <listitem>
	<para>XFree86 X11:
	  <filename>/etc/X11/XF86Config</filename></para>
      </listitem>
      <listitem>
	<para>X.org X11: <filename>/etc/X11/xorg.conf</filename></para>
      </listitem>
    </itemizedlist>
    <para>
      X Server Log File:
    </para>
    <itemizedlist>
      <listitem>
	<para>XFree86 X11:
	  <filename>/var/log/XFree86.<replaceable>$DISPLAY</replaceable>.log</filename></para>
      </listitem>
      <listitem>
	<para>X.org X11:
	  <filename>/var/log/Xorg.<replaceable>$DISPLAY</replaceable>.log</filename></para>
      </listitem>
    </itemizedlist>
    <para>
      When configuring or troubleshooting your X server
      configuration, be sure that you are using the correct
      files.
    </para>
    <para>
      There has been some confusion regarding font-related issues
      under the X Window System in recent versions of &DISTRO; (and
      versions of &RHL; before it.)  At the present time, there are two
      font subsystems, each with different characteristics:
    </para>
    <itemizedlist>
      <listitem>
	<para>The original (15+ year old) subsystem is referred to as
	  the <firstterm>core X font subsystem</firstterm>.  Fonts
	  rendered by this subsystem are not anti-aliased, are handled
	  by the X server, and have names such as:
	  <computeroutput>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</computeroutput>
	</para>
      </listitem>
      <listitem>
	<para>
	  The newer font subsystem is known as
	  <firstterm>fontconfig</firstterm>, and allows applications
	  direct access to the font files.  Fontconfig is often used
	  along with the <filename>Xft</filename> library, which allows
	  applications to render fontconfig fonts to the screen with
	  antialiasing. Fontconfig uses more human-friendly names such
	  as: <computeroutput>Luxi Sans-10</computeroutput>
	</para>
      </listitem>
    </itemizedlist>
    <para>
      Over time, fontconfig and <filename>Xft</filename> will replace
      the core X font subsystem.  At the present time, applications
      using the Qt 3 or GTK 2 toolkits (which would include KDE and
      GNOME applications) use the fontconfig and Xft font subsystem;
      almost everything else uses the core X fonts.
    </para>
    <para>
      In the future, &FC; may support only fontconfig/Xft in
      place of the XFS font server as the default local font access
      method.
    </para>
    <note>
      <title>Note</title>
      <para>
	An exception to the font subsystem usage outlined above is
	OpenOffice.org, which uses its own font rendering technology.
      </para>
    </note>
    <para>
      The steps to add new fonts to &DISTRO; &DISTROVER; depend on the
      fonts subsystem this is going to use the new fonts.  For the core X
      font subsystem:
    </para>

    <procedure>
      <step>
	<para>
	  Create the <filename>/usr/share/fonts/local/</filename>
	  directory (if it doesn't already exist):
	</para>
<screen>
<command>mkdir /usr/share/fonts/local/</command>
</screen>
      </step>
      <step>
	<para>
	  Copy the new font file into
	  <filename>/usr/share/fonts/local/</filename>
	</para>
      </step>
      <step>
	<para>
	  Update the font information by issuing the following commands
	  (note that, due to formatting restrictions, the following
	  commands may appear on more than one line; in use, each
	  command should be entered on a single line):
	</para>
<screen>
<command>ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</command>
<command>mkfontdir /usr/share/fonts/local/</command>
</screen>
      </step>
      <step>
	<para>
	  If you had to create
	  <filename>/usr/share/fonts/local/</filename>, you must then
	  add it to the X font server (<command>xfs</command>) path:
	</para>
<screen>
<command>chkfontpath --add /usr/share/fonts/local/</command>
</screen>
      </step>
    </procedure>
    <para>
      Adding new fonts to the fontconfig font subsystem is more
      straightforward; the new font file only needs to be copied into
      the <filename>/usr/share/fonts/</filename> directory (individual
      users can modify their personal font configuration by copying the
      font file into the <filename>~/.fonts/</filename> directory).
    </para>
    <para>
      After the new font has been copied, use
      <command>fc-cache</command> to update the font information cache:
    </para>
<screen>
<command>fc-cache <replaceable>&lt;directory&gt;</replaceable></command>
</screen>
    <para>
      (Where
      <command><replaceable>&lt;directory&gt;</replaceable></command>
      would be either the <filename>/usr/share/fonts/</filename> or
      <filename>~/.fonts/</filename> directories.)
    </para>
    <para>
      Individual users may also install fonts graphically, by browsing
      <command>fonts:///</command> in
      <application>Nautilus</application>, and dragging the new font
      files there.
    </para>
    <note>
      <title>Note</title>
      <para>
	If the font filename ends with "<filename>.gz</filename>", it
	has been compressed with <command>gzip</command>, and must be
	decompressed (with the <command>gunzip</command> command) before
	the fontconfig font subsystem can use the font.
      </para>
    </note>      
    <para>
      Due to the transition to the new font system based on
      fontconfig/Xft, GTK+ 1.2 applications are not affected by any
      changes made via the <guilabel>Font Preferences</guilabel> dialog.
      For these applications, a font can be configured by adding the
      following lines to the file <filename>~/.gtkrc.mine</filename>:
    </para>
<screen>    
<computeroutput>style "user-font" {
fontset = "<replaceable>&lt;font-specification&gt;</replaceable>"
}
widget_class "*" style "user-font"</computeroutput>
</screen>
    <para>
      (Where
      <command><replaceable>&lt;font-specification&gt;</replaceable></command> 
      represents a font specification in the style used by traditional X
      applications, such as
      "<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>".)
    </para>
  </section>
</section>

<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-it.xml" "article" "section")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Fri Nov  4 21:13:42 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Fri,  4 Nov 2005 16:13:42 -0500
Subject: release-notes networking-it.xml,1.1,1.2
Message-ID: <200511042113.jA4LDgRk012084@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12067

Modified Files:
	networking-it.xml 
Log Message:
Completed


Index: networking-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/networking-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- networking-it.xml	4 Nov 2005 20:02:41 -0000	1.1
+++ networking-it.xml	4 Nov 2005 21:13:34 -0000	1.2
@@ -116,23 +116,23 @@
       </listitem>
     </varlistentry>
     <varlistentry>
-      <term>DCCP Protocol Support</term>
+      <term>Supporto protocollo DCCP</term>
       <listitem>
-	<para>Kernel version 2.6.14-rc1 was the first version to receive
-	  support for the DCCP protocol. The implementation is still
-	  experimental but known to work. Work to make userspace
-	  applications aware of this new protocol has started.
+	<para>Il Kernel versione 2.6.14-rc1 fu la prima versione a ricevere
+	  supporto per il protocollo DCCP. L'implementazione ?? ancora
+	  sperimentale ma ?? risaputo che funziona. Lavora per far si che le applicazioni
+	  in userspace siano a conoscenza che questo nuovo protocollo ?? iniziato.
 	</para>
       </listitem>
     </varlistentry>
     <varlistentry>
       <term>Wireless</term>
       <listitem>
-	<para>A new driver named HostAP has been added to 2.6.14-rc1
-	  allowing the emulation of a wireless access point in software.
-	  Currently this driver only works for Intersil Prism2-based
-	  cards (PC Card/PCI/PLX). Support for wireless cards Intel(R)
-	  PRO/Wireless 2100 and 2200 has been added.
+	<para>Un nuovo driver denominato HostAP ?? stato aggiunto a 2.6.14-rc1
+	  permettendo l'emulazione di un access point wireless in software.
+	  Attualmente questo driver funziona solo per le carte Intersil Prism2-based
+	  (PC Card/PCI/PLX). Il supporto per le carte wireless Intel(R)
+	  PRO/Wireless 2100 e 2200 ?? stato aggiunto.
 	</para>
       </listitem>
     </varlistentry>
@@ -141,30 +141,30 @@
       <listitem>
 	<itemizedlist>
 	  <listitem>
-	    <para>A lot of TCP Segmentation Offloading (TSO) related
-	      fixes have been included.
+	    <para>Moltissimi fix riguardanti la TCP Segmentation Offloading (TSO)
+	      sono stati inclusi.
 	    </para>
 	  </listitem>
 	  <listitem>
-	    <para>A new textsearch infrastructure has been added
-	      useable with the corresponding iptables and extended
+	    <para>Una nuova infrastruttura di ricerca testo ?? stata aggiunta
+	      utilizzabile con il corrispondente iptables ed extended
 	      match.
 	    </para>
 	  </listitem>
 	  <listitem>
-	    <para>Both the IPv4 and IPv6 multicast joining interface
-	      visible by userspace have been reworked and brought up to
-	      the latest standards.
+	    <para>Entrambe le IPv4 ed IPv6 multicast joining interface
+	      visibili in userspace sono state ristrutturate e portate fino
+	      agli ultimi standards.
 	    </para>
 	  </listitem>
 	  <listitem>
-	    <para>The SNMPv2 MIB counter ipInAddrErrors is finally
-	      supported for IPv4.
+	    <para>Il contatore SNMPv2 MIB ipInAddrErrors ?? finalmente
+	      supportato per IPv4.
 	    </para>
 	  </listitem>
 	  <listitem>
-	    <para>Various new socket options proposed in Advanced API
-	      (RFC3542) have been added.
+	    <para>Nuove varie opzioni socket proposte in Advanced API
+	      (RFC3542) sono state aggiunte.
 	    </para>
 	  </listitem>
 	</itemizedlist>
@@ -175,10 +175,10 @@
     <title>Userspace Tools</title>
     <title>iproute</title>
     <para>
-      The IPv4 address deletion algorithm did not take the prefix
-      length into account up to kernel version 2.6.12. Since this has
-      changed the iproute2 tool now issues a warning if no prefix length
-      is provided to warn about possible unintended deletions:
+      L'algoritmo di cancellazione indirizzo IPv4 address non prendeva la lunghezza
+      del prefisso in conto fino al kernel versione 2.6.12. Da quando ci?? ??
+      cambiato lo strumento iproute2 ora invia un messaggio d'avvertimento se un prefisso di
+      privo di lunghezza ?? fornito per avvertire di possibili cancellazioni non intenzionali:
     </para>
 <screen>
 ip addr list dev eth0
@@ -191,69 +191,68 @@
       in further releases, fix your scripts!
 </screen>
     <para>
-      The correct method of deleting the address and thus avoiding the
-      warning is:
+      Il metodo corretto di cancellare l'indirizzo evitando l'avvertimento ??:
     </para>
 <screen>
 su -c 'ip addr del 10.0.0.3/24 dev eth0'
 </screen>
     <para>
-      It has not been possible to tell if an interface is down
-      administratively or because no carrier can be found (cable
-      unplugged). The flag <computeroutput>NO-CARRIER</computeroutput>
-      has been introduced that shows up as a link flag if the link is
-      administratively up but no carrier can be found.
+      Non ?? stato possibile dire se un interfaccia ?? spenta
+      a scopo amministrativo o perch?? non c'?? linea (cavo
+      staccato). Il flag <computeroutput>NO-CARRIER</computeroutput>
+      ?? stato introdotto per mostrare un link flag se il link ??
+      administrativamente su ma non viene trovata linea.
     </para>
     <para>
-      The <command>ip</command> command now supports a batch mode via
-      the argument <option>-batch</option> just like the
-      <command>tc</command> command to speed up batches of tasks.
+      Il comando <command>ip</command> adesso supporta una modalit?? batch
+      con l'argomento <option>-batch</option> in modo simile al
+      comando <command>tc</command> per velocizzare delle serie di operazioni.
     </para>
   </section>
 </section>
 
 <!-- cruft, but saved just in case :)
   <para>
-   This section contains information relating to network connectivity.
+   Questa sezione contiene informazioni relative alla connettivit?? di rete.
   </para>
   <section id="sn-networking-networkmanager">
     <title><filename>NetworkManager</filename></title>
     <para>
-      The <command>NetworkManager</command> service allows computers
-      such as laptops to automatically manage changing network
-      connections.  It includes support for wireless networking.
+      Il servizio <command>NetworkManager</command> permette a computers
+      come i laptops di amministrare automaticamente cambi di connessione
+      di rete.  Include il supporto per le connessioni di rete wireless.
     </para>
     <para>
-      You must manually enable the <command>NetworkManager</command>
-      service.  To do so, type the following in a terminal window:
+      Devi abilitare manualmente il servizio <command>NetworkManager</command>.
+      Per farlo scrivi quanto segue in una finestra terminale:
     </para>
 <screen>
 su -c '/sbin/chkconfig --level 345 NetworkManager on; /sbin/service NetworkManager start'
 su -c '/sbin/chkconfig --level 345 NetworkManagerDispatcher on; /sbin/service NetworkManagerDispatcher start'
 </screen>
     <para>
-      Enter the root password when prompted.
+      Inserite la password di root quando richiesto.
     </para>
     <para>
-      Use the <application>Network Monitor</application> desktop applet
-      to monitor and configure <command>NetworkManager</command>.  To load the
-      applet in GNOME, right-click on the panel and select:
+      Usate l'applet del desktop <application>Network Monitor</application>
+      per monitorare e configurare <command>NetworkManager</command>.  Per caricare
+      l'applet in GNOME, click con il bottone destro del mouse sul pannelo e selezionate:
     </para>
     <para>
      <guimenuitem>Add to Panel...</guimenuitem><guimenuitem>Network
      Monitor</guimenuitem>
     </para>
     <para>
-      <command>NetworkManager</command> uses BIND to proxy DNS requests.
-      Enabling the <command>NetworkManager</command> service also loads the
-      <command>named</command> service as well.  By default BIND is
-      configured as a cacheing service for the local system, and does
-      not accept connections from other systems.  
+      Il <command>NetworkManager</command> usa BIND per mettere in cache le richieste DNS.
+      Abilitando il servizio <command>NetworkManager</command> verr?? caricato anche
+      il servizio <command>named</command>.  Per impostazione predefinita BIND ??
+      configurato come un servizio di cacheing per il sistema locale, e non accetta
+      connessioni da altri sistemi.
     </para>
     <para>
-	Note that some wireless network cards require drivers or firmware
-	that cannot be included with &DISTRO;.  This software must be
-	installed separately for <command>NetworkManager</command> to function.
+	Nota che alcune shcede di rete wireless richiedono drivers o firmware
+	che non pu?? essere incluso con &DISTRO;.  Questo software deve essere
+	installato separatamente per far funzionare <command>NetworkManager</command>.
     </para>
 -->
 <!--



From fedora-docs-commits at redhat.com  Sat Nov  5 12:08:31 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat,  5 Nov 2005 07:08:31 -0500
Subject: release-notes overview-it.xml,1.1,1.2
Message-ID: <200511051208.jA5C8VIm007054@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7037

Modified Files:
	overview-it.xml 
Log Message:



Index: overview-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/overview-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- overview-it.xml	4 Nov 2005 20:02:41 -0000	1.1
+++ overview-it.xml	5 Nov 2005 12:07:20 -0000	1.2
@@ -1,26 +1,26 @@
 <section id="sn-overview">
-  <title>Overview of This Release</title>
+  <title>Descrizione di questa release</title>
   <caution>
-    <title>Information Out-of-Date</title>
+    <title>Informazioni non aggiornate</title>
     <para>
-      The content in this section needs to be updated for &DISTRO;
+      Il contenuto in questa seczione deve essere aggiornato per &DISTRO;
       &DISTROVER;
     </para>
   </caution>
 <!--
   <para>
-    The following list includes brief summaries of some of the more
-    significant aspects of &DISTRO; &DISTROVER;:
+    Il seguente elenco include un breve sommario di alcune dei pi??
+    significativi aspetti di &DISTRO; &DISTROVER;:
   </para>
   <itemizedlist>
     <listitem>
       <para>
-	&DISTRO; &DISTROVER; contains the following changes:
+	&DISTRO; &DISTROVER; contiene i seguenti cambiamenti:
       </para>
       <itemizedlist>
 	<listitem>
 	  <para>
-	    Support for the PowerPC (PPC) architecture.
+	    Supporto per l'architettura PowerPC (PPC).
 	  </para>
 	</listitem>
 	<listitem>
@@ -35,15 +35,15 @@
 	</listitem>
 	<listitem>
 	  <para>
-	    KDE 3.4 &mdash; includes new accessibility features.  You
-	    can manage these new features in <guimenu>KDS Control
+	    KDE 3.4 &mdash; include nuove caratteristiche di accessibilit??.  Puoi
+	    amministrare queste nuove caratteristiche in <guimenu>KDS Control
 	      Center</guimenu><guisubmenu>Regional &amp;
 	      Accessibility</guisubmenu><guisubmenu>Accessibility</guisubmenu>.
 	  </para>
 	</listitem>
 	<listitem>
 	  <para>
-	    Native Eclipse 3.1M6 (part of a free Java stack)
+	    Eclipse 3.1M6 (part of a free Java stack) nativo
 	  </para>
 	</listitem>
 	<listitem>
@@ -58,7 +58,7 @@
 	</listitem>
 	<listitem>
 	  <para>
-	    Xen 2 (virtualization to run multiple versions of an OS)
+	    Xen 2 (virtualizzazione per eseguire multiple versioni di un OS)
 	  </para>
 	</listitem>
 	<listitem>
@@ -68,23 +68,23 @@
 	</listitem>
 	<listitem>
 	  <para>
-	    Evince 0.2.1 (universal document viewer)
+	    Evince 0.2.1 (visualizzatore di documenti universale)
 	  </para>
 	</listitem>
 	<listitem>
 	  <para>
-	    GDM 2.6 - Includes early login capability
+	    GDM 2.6 - Include le ultime capacit?? di login
 	  </para>
 	</listitem>
 	<listitem>
 	  <para>
-	    &SEL; &mdash; This release includes coverage for 80 new
-	    daemons by the targeted policy.  There are changes to the
-	    handling of Booleans.  The targeted policy is enabled by
-	    default.  For more information, refer to:  <ulink
+	    &SEL; &mdash; Questa release include la copertura per 80 nuovi
+	    demoni dalla policy targeted.  Ci sono cambiamenti sulla
+	    manipolazione delle booleane.  La policy targeted ?? abilitata
+	    per impostazione predefinita.  Per maggiori informazioni, riferitevi a:  <ulink
 	      url="http://fedora.redhat.com/docs/selinux-faq/">http://fedora.redhat.com/docs/selinux-faq/</ulink>. 
-	    This is the complete list of daemons covered by the targeted
-	    policy:
+	    Questa ?? la lista completa dei demoni coperti dalla policy
+	    targeted:
 	  </para>
 	  <itemizedlist>
 	    <listitem>



From fedora-docs-commits at redhat.com  Sat Nov  5 12:22:46 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat,  5 Nov 2005 07:22:46 -0500
Subject: release-notes package-movement-it.xml,1.1,1.2
Message-ID: <200511051222.jA5CMklp007154@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7137

Modified Files:
	package-movement-it.xml 
Log Message:



Index: package-movement-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-movement-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- package-movement-it.xml	4 Nov 2005 20:02:41 -0000	1.1
+++ package-movement-it.xml	5 Nov 2005 12:22:39 -0000	1.2
@@ -2,20 +2,20 @@
   <title>Packages Movement</title>
   <!-- 
   FIXME
-  Needs updating of entire contents for FC4.
+  Necessita dell'aggiornamento dell'intero contenuto di FC4.
   -->
   <para>
-    This command was used to generate the list of package changes.  The
-    backslash <computeroutput>\</computeroutput> is used to artificially
-    break the line for printing purposes.:
+    Questo comando ?? stato usato per generare la lista dei pacchetti modificati.  Lo
+    backslash <computeroutput>\</computeroutput> ?? usato per interrompere
+    artificialmente le linee per scopi di stampa.:
   </para>
 <screen>
 <command>treediff.py dist-fc4 dist-rawhide > /tmp/diff \
 sed -e 's,^,* ,g' -e 's,$,\n,g' /tmp/diff > diffwiki</command>
 </screen>
   <section>
-    <title>Package Changes</title>
-    <para>As of 21st September 2005 </para>
+    <title>Modifiche del pacchetto</title>
+    <para>Al 21st September 2005 </para>
     <para>[106429] MAKEDEV-3.19-1 -> [115423] MAKEDEV-3.19-4 </para>
     <para>[111566] <ulink
 	url='/ImageMagick'>ImageMagick</ulink>-6.2.2.0-2 -> [112246]
@@ -1042,21 +1042,21 @@
     </section>
   </section>
   <section>
-    <title>Notes</title>
+    <title>Note</title>
     <para>
-      <application>system-config-mouse</application> configuration
-      utility has been dropped in this release because synaptic and 3
-      button mouse configuration is being done automatically and serial
-      mice are not supported.
+      L'utilit?? di configurazione <application>system-config-mouse</application>
+      ?? stata scartata in questa release poich?? synaptic e la configurazione
+      dei mouse a 3 bottoni viene fatta automaticamente ed i mouse
+      seriali non sono supportati.
     </para>
     <para>
-      Screensavers not installed by default anymore?  Explain
-      why and provide commands to install them.
+      Gli screensavers, per impostazione predefinita non sono pi?? installati?  Spieghiamo
+      il perch?? e forniamo i comandi per installarli.
     </para>
 <!-- FIXME
     <para>
-      Gbenson agreed to justify any inclusion of Java packages in
-      FC5. Send a mail. Should include this info before test1 release 
+      Gbenson ?? daccordo nel giustificare qualsuasi inclusione di pacchetti Java in
+      FC5. Spedisci un e-mail. Questa info potrebbe essere inclusa prima del rilascio della release test1
     </para>
 -->
   </section>



From fedora-docs-commits at redhat.com  Sat Nov  5 14:13:12 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat,  5 Nov 2005 09:13:12 -0500
Subject: release-notes package-notes-it.xml,1.1,1.2
Message-ID: <200511051413.jA5EDCOR010351@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10334

Modified Files:
	package-notes-it.xml 
Log Message:



Index: package-notes-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- package-notes-it.xml	4 Nov 2005 20:02:41 -0000	1.1
+++ package-notes-it.xml	5 Nov 2005 14:13:04 -0000	1.2
@@ -26,221 +26,220 @@
 ]>
 -->
 <section id="sn-package-notes">
-  <title>Package-Specific Notes</title>
+  <title>Note Specifiche dei pacchetti</title>
   <!--
   FIXME
-  Needs updating of entire contents for FC5.
+  Necessita di aggiornamenti per l'intero contenuto per FC5.
   -->
   <para>
-    The following sections contain information regarding packages that
-    have undergone significant changes for &DISTRO; &DISTROVER;.  For
-    easier access, they are generally organized using the same groups
-    used in Anaconda.
+    Le seguenti sezioni contengono informazioni riguardanti i pacchetti che
+    hanno avuto significativi cambiamenti per &DISTRO; &DISTROVER;.  Per
+    un accesso facilitato, sono in linea generale organizzati usando gli stessi gruppi
+    usati in Anaconda.
   </para>
   <caution>
-    <title>Information Out-of-Date</title>
+    <title>Informazioni non aggiornate</title>
     <para>
-      The content in this section needs to be updated for &DISTRO;
+      Il contenuto di questa sezione necessita di essere aggiornato per &DISTRO;
       &DISTROVER;
     </para>
   </caution>
   <section id="sn-basic-components">
-    <title>Basic Components</title>
+    <title>Componenti di base</title>
     <para>
-      This section contains information related to basic system
-      components.
+      Questa sezione contiene informazioni relative al sistema base
+      dei componenti.
     </para>
     <section>
-      <title>&FEX; Repository</title>
+      <title>Repositorio &FEX;</title>
       <para>
-	&FEX; is part of the larger &FP; and is a volunteer-based
-	community effort to create a repository of packages that
-	compliment &FC;. The &FEX; repository is enabled by default from
-	&FC; &LOCALVER; onwards.
+	&FEX; ?? parte del pi?? largo &FP; e la creazione di repositori di pacchetti
+	a complemento di  &FC; ?? uno sforzo della comunit?? basata su volontariato.
+	Il repositorio &FEX; ?? abilitato come impostazione predefinita dalla
+	&FC; &LOCALVER; in avanti.
       </para>
       <para>
-	You can lean more about &FEX; from:
+	Puoi saperne di pi?? su &FEX; da:
       </para>
       <para>
 	<ulink
 	  url="http://fedoraproject.org/wiki/Extras">http://fedoraproject.org/wiki/Extras</ulink>
       </para>
       <para>
-	If you would like to install any software available from
-	Fedora extras you can use <command>yum</command>.
+	Se vuoi installare un qualsiasi software disponibile da
+	Fedora extras puoi usare <command>yum</command>.
       </para>
 <screen>
 <command>yum install <replaceable>&lt;packagename&gt;</replaceable></command>
 </screen>
       <para>
-	Where <replaceable>&lt;packagename&gt;</replaceable> is the name
-	of the package you want to install.  For example, if you wanted
-	to install the <filename>abiword</filename> package, the command
-	<command>yum install abiword</command> automatically installs
-	the package and all dependencies.
+	Dove <replaceable>&lt;packagename&gt;</replaceable> ?? il nome
+	del pacchetto che vuoi installare.  Per esempio, se vuoi
+	installare il pacchetto <filename>abiword</filename>, il comando
+	<command>yum install abiword</command> installer?? automaticamente
+	il pacchetto e tutte le dipendenze.
       </para>
     </section>
     <section id="sn-audit-daemon">
-      <title>Audit Daemon <command>auditd</command> and Log
-	Files</title>
+      <title>Audit Daemon <command>auditd</command> ed i files di log</title>
       <para>
-	The audit daemon, auditd, is now enabled by default.  When
-	auditd is running, the kernel directs audit messages to
-	<filename>/var/log/audit/audit.log</filename>.  The location of this file is
-	specified in <filename>/etc/auditd.conf</filename>.
+	Il demone audit, auditd, ?? abilitato per impostazione predefinita. Quando
+	auditd ?? in esecuzione, il kernel direziona i messagi a
+	<filename>/var/log/audit/audit.log</filename>.  La locazione di questo file ??
+	specificata in <filename>/etc/auditd.conf</filename>.
       </para>
       <para>
-	AVC messages for &SEL; are sent using the audit infrastructure.
-	These messages are now in
+	I messaggi AVC per &SEL; sono spediti usando l'infrastruttura audit.
+	Questi messaggi sno adesso in
 	<filename>/var/log/audit/audit.log</filename>.
       </para>
       <para>
-	When auditd is not running, the kernel passes audit messages to
-	syslog.  These logs are typically kept in <filename>/var/log/messages</filename> and
-	are viewable using <command>dmesg</command>.
+	Quando auditd non ?? in esecuzione, il kernel passa i messaggi di audit a
+	syslog.  Questi logs sono tipicamente lasciati tenuti in <filename>/var/log/messages</filename> e
+	sono visibili usando <command>dmesg</command>.
       </para>
       <para>
-	Audit extensions are now compiled into PAM.  All programs that
-	do grant entry to the system or change user account attributes
-	will generate an audit message.
+	Le estensioni audit sono ora compilate in PAM.  Tutti i programmi che
+	garantiscono accesso al sistema o che cambiano gli attributi di account utente
+	genereranno un messaggio audit.
       </para>
       <para>
-	To enable auditing within the kernel, you must pass the
-	parameter <parameter>audit=1</parameter> to the kernel during
-	boot.  Otherwise, you can use this command to enable auditing
-	during run time:
+	Per abilitare l'auditing nel kernel, devi passare il
+	parametro <parameter>audit=1</parameter> al kernel durante
+	il boot.  Altrimenti, potrai usare questo comando per abilitare l'auditing
+	durante l'esecuzione:
       </para>
 <screen>
 <command>auditctl -e 1</command>
 </screen>
     </section>
     <section id="sn-nptl">
-      <title>LinuxThreads versus NPTL</title>
+      <title>LinuxThreads contro NPTL</title>
       <para>
-	As the next step in removing support for the obsolete
-	LinuxThreads library, code compiled and linked on &FC;
-	&LOCALVER; now automatically uses the NPTL headers and
-	libraries.
-      </para>
-      <para>
-	In previous releases since &RHL; 9, the default threading was
-	LinuxThreads since the interface is mostly forward compatible.
-	The advantages of the NPTL interface is that the cancellation
-	handling is faster (when <parameter>-fexception</parameter> is
-	used, even in C code) and that the additional interfaces are now
-	available without special compiler and linker parameters.  In
-	other words, you do not need to use
-	<option>-I/usr/include/nptl</option> and
-	<option>-L/usr/lib{,64}/nptl</option> any longer.  Note that
-	<parameter>lib{,64}</parameter> is to be interpreted as lib64 on
-	platforms which place DSOs in <filename>lib64/</filename>
-	directories, and <filename>lib/</filename> otherwise.
-      </para>
-      <para>
-	In &FC; &LOCALVER; it is still possible to create code using the
-	LinuxThreads definitions.  For this the
-	<filename>linuxthreads-devel</filename> package must be
-	installed and
+	Come prossimo passo nel rimuovere il supporto per l'obsoleta
+	LinuxThreads library, il codice compilato e linkato su &FC;
+	&LOCALVER; adesso usa automaticamente gli headers NPTL e le
+	librerie.
+      </para>
+      <para>
+	Nelle precedenti releases fino alla &RHL; 9, l'impostazione predefinita per il
+	threading era LinuxThreads poich?? l'interfaccia era molto pi?? compatibile.
+	I vantaggi dell'interfaccia NPTL sono che la manipolazione della 
+	cancellazione ?? pi?? veloce (quando ?? usato <parameter>-fexception</parameter>,
+	anche nel codice C) e che le interfacce aggiuntive sono ora
+	disponibili senza parametri speciali per compilatori e linker.  In
+	altre parole, non hai bisogno di usare
+	<option>-I/usr/include/nptl</option> e
+	<option>-L/usr/lib{,64}/nptl</option> mai pi??.  Nota che
+	<parameter>lib{,64}</parameter> deve essere interpretata come lib64 sulle
+	piattaforme che impostano DSOs nelle directories <filename>lib64/</filename>,
+	e <filename>lib/</filename> altrimenti.
+      </para>
+      <para>
+	In &FC; &LOCALVER; ?? ancora possibile creare codice usando le
+	definizioni LinuxThreads.  Per questo il pacchetto
+	<filename>linuxthreads-devel</filename> deve essere
+	installato e
       </para>
 <screen>
 <option>-I/usr/include/linuxthreads -L/usr/lib{,64}/linuxthreads</option>
 </screen>
       <para>
-	must be passed to the compiler.
+	deve essere passato al compilatore.
       </para>
       <para>
-	Previously, you could select the version of glibc and the
-	libpgthread DSH using run time environment variables.  You now
-	need to also specify this variable in the environment:
+	In precedenza, potevi selezionare la versione di glibc e il
+	libpgthread DSH usando le variabili ambiente runtime.  Adesso
+	necessiti di specificare anche questa variabile ambiente:
       </para>
 <screen>
 <envar>LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads</envar>
 </screen>
       <para>
-	This additional variable is required because the run/time
-	libraries have been moved out of the way.  There may be programs
-	that will not work if the program uses an unfortunate
-	<envar>DT_RPATH</envar> (which overwrites the
-	<envar>LD_LIBRARY_PATH</envar> setting).
+	Questa variabile aggiuntiva ?? richiesta perch?? le librerie run/time
+	sono state spostate.  Ci potrebbero essere programmi
+	che non funzionano se usassero uno sfortunato
+	<envar>DT_RPATH</envar> (che altrimenti sovrascriver?? l'impostazione
+	<envar>LD_LIBRARY_PATH</envar>).
       </para>
       <para>
-	All this makes it more cumbersome to run programs which depend
-	on LinuxThreads.  But this is intentional.
+	Tutto ci?? rende molto pi?? ingombrante eseguire programmi che dipendono
+	da LinuxThreads.  Ma ?? intenzionale.
       </para>
       <important>
-	<title>Important</title>
+	<title>Importante</title>
 	<para>
-	  FC5 will not have LinuxThreads support and all programs have
-	  to be converted to use NPTL by then.
+	  FC5 non supporter?? LinuxThreads e tutti i programmi dovranno essere
+	  convertiti all'uso di NPTL.
 	</para>
       </important>
       <para>
-	In general, conversion to using NPTL has not been an issue.
+	In generale, la conversione all'uso di NPTL non ?? un problema.
       </para>
     </section>
     <section>
-      <title>Enabling the <filename>slocate</filename> Database</title>
+      <title>Abilitare il database <filename>slocate</filename></title>
       <para>
-	The database needed by the <command>locate</command> utility is
-	no longer created by default. Enable the database creation by
-	setting <computeroutput>DAILY_UPDATE</computeroutput> to
+	Il database necessario all'utilit?? <command>locate</command> non ??
+	pi?? creato per impostazione predefinita. Abilita la creazione del database
+	impostando <computeroutput>DAILY_UPDATE</computeroutput> su
 	<option>yes</option> in <filename>/etc/updatedb.conf</filename>
-	if you want to use <command>locate</command>.
+	se vuoi usare <command>locate</command>.
       </para>
     </section>
     <section>
-      <title>Stricter Controls in <filename>openssh</filename></title>
+      <title>Controlli ristretti in <filename>openssh</filename></title>
       <para>
-	The version of OpenSSH in &FC; &LOCALVER; is based on OpenSSH
-	3.9 and includes strict permission and ownership checks for the
-	user configuration file <filename>~/.ssh/config</filename>. If
-	this file does not have appropriate ownership and permissions,
-	<command>ssh</command> will exit.
+	La versione di OpenSSH in &FC; &LOCALVER; ?? basata su OpenSSH
+	3.9 ed include stretti controlli sui permessi e la propriet?? per il file
+	di configurazione utente <filename>~/.ssh/config</filename>. Se
+	questo file non ha l'appropriata appartenenza e permessi,
+	<command>ssh</command> cesser?? l'esecuzione.
       </para>
       <para>
-	Check that <filename>~/.ssh/config</filename> is owned by the
-	owner of <filename>~/</filename>, and that its permissions are
-	set to mode 600.
+	COntrollate che <filename>~/.ssh/config</filename> si aposseduto dal
+	proprietario di <filename>~/</filename>, e che i suoi permessi siano
+	impostati a 600.
       </para>
 <screen>
 ls -l ~/.ssh/config
 -rw-------  1 username username 400 May  5 18:44 /home/username/.ssh/config
 </screen>
       <para>
-	The directory <filename>~/</filename> is command-line shorthand
-	for the logged in user's home directory, usually
+	La directory <filename>~/</filename> ?? la scociatoia a linea di comando
+	per la home directory dell'utente loggato, solitamente
 	<filename>/home/username/</filename>.
       </para>
       <para>
-	In addition, OpenSSH is no longer configured to request X11
-	forwarding by default when connecting to servers.  To enable X11
-	forwarding, the <option>-X</option> or <option>-Y</option>
-	option must be specified, or the <option>ForwardX11</option>
-	option must be enabled in the <filename>~/.ssh/config</filename>
-	file.
-      </para>
-      <para>
-	The behavior of <command>ssh</command> clients that are invoked
-	with the <option>-X</option> option has changed.  In OpenSSH 3.8
-	and later, X11 forwarding is performed in a way that
-	applications run as untrusted clients by default. Previously,
-	X11 forwarding was performed so that applications always ran as
-	trusted clients. Some applications may not function properly
-	when run as untrusted clients. To forward X11 so that
-	applications are run as trusted clients, invoke ssh with the
-	<option>-Y</option> option instead of the <option>-X</option>
-	option, or set <option>ForwardX11Trusted</option> in the
-	<option>~/.ssh/config</option> file.
+	In aggiunta, OpenSSH non ?? pi?? configurato per richiedere l'X11
+	forwarding per impostazione predefinita quando si connette ai servers.  Per abilitare l'X11
+	forwarding, l'opzione <option>-X</option> o <option>-Y</option>
+	deve essere specificata, o l'opzione <option>ForwardX11</option>
+	deve essere abilitata nel file <filename>~/.ssh/config</filename>.
+      </para>
+      <para>
+	Il comportamento dei clients <command>ssh</command> che sono stati invocati
+	con l'opzione <option>-X</option> ?? cambiata.  In OpenSSH 3.8
+	e superiori, l'X11 forwarding ?? eseguito in modo che
+	le applicazioni siano eseguite come clients untrusted per impostazione predefinita.
+	Precedentemente, l'X11 forwarding era effettuato in modo tale che le applicazioni
+	corressero sempre come clients verificati. Alcune applicazioni potrebbero non funzionare
+	in modo corretto quando eseguite come client non verificati.
+	Per eseguire l'X11 forwarding affinch?? le applicazioni siano eseguite come
+	clients trusted, invocate ssh con l'opzione
+	<option>-Y</option> invece che l'opzione <option>-X</option>,
+	o impostate <option>ForwardX11Trusted</option> nel file
+	<option>~/.ssh/config</option>.
       </para>
     </section>
     <section id="sn-perl">
-      <title>Perl Binary Compat Symlinks</title>
+      <title>I symlinks Perl Binary Compat</title>
       <para>
-	Binary compat symlinks for <filename>perl-5.8.0</filename>,
-	<filename>perl-5.8.1</filename>, and
-	<filename>perl-5.8.2</filename> have been removed.  If you have
-	perl modules built with those older versions of perl, you need
-	to rebuild using the <filename>perl-5.8.6</filename> contained
+	I symlinks binary compat per <filename>perl-5.8.0</filename>,
+	<filename>perl-5.8.1</filename>, e
+	<filename>perl-5.8.2</filename> sono stati rimossi.  Se hai moduli perl
+	creati con queste vecchie versioni di perl, dovrai
+	ricompilarli usando il <filename>perl-5.8.6</filename> contenuto
 	in &FC; &LOCALVER;.
       </para>
     </section>
@@ -250,17 +249,17 @@
   <section id="sn-packages-core">
     <title>Core</title>
     <para>
-      This section contains the most elemental components of &DISTRO;,
-      including the kernel.
+      Questa sezione contiene le componenti pi?? elemntari di &DISTRO;,
+      incluso il kernel.
     </para>
     <section>
       <title>yum</title>
       <para>
-	The sqllite database is now used by yum, and makes performance
-	noticeably faster.
+	Il database sqllite ?? utilizzato da yum ora, e rende le prestazioni
+	notevolmente pi?? veloci.
       </para>
       <para>
-	The Fedora Extras repository is now enabled by default.
+	Il repositorio Fedora Extras ?? ora abilitato per impostazione predefinita.
       </para>
     </section>
     &KERNEL;



From fedora-docs-commits at redhat.com  Sat Nov  5 15:02:27 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat,  5 Nov 2005 10:02:27 -0500
Subject: release-notes RELEASE-NOTES-it.xml,1.1,1.2
Message-ID: <200511051502.jA5F2Rkn011922@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11905/release-notes

Modified Files:
	RELEASE-NOTES-it.xml 
Log Message:
Revisione


Index: RELEASE-NOTES-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- RELEASE-NOTES-it.xml	4 Nov 2005 19:59:37 -0000	1.1
+++ RELEASE-NOTES-it.xml	5 Nov 2005 15:02:18 -0000	1.2
@@ -34,9 +34,9 @@
 
 
 <!-- *************** COMMON FDP entities *************** -->
-<!ENTITY % FEDORA-ENTITIES-IT SYSTEM "../docs-common/common/fedora-entities-it.ent">
- %FEDORA-ENTITIES-IT;
- <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-it.xml">
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
+ %FEDORA-ENTITIES-EN;
+ <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
 
  <!-- *************** Local entities *************** -->
 
@@ -55,7 +55,7 @@
 
 <article id="index" lang="it" arch="x86;x86_64;ppc" os="test;final">
   <articleinfo>
-    <title>&DISTRO; &DISTROVER; Note di rilascio</title>
+    <title>Note di rilascio per &DISTRO; &DISTROVER;</title>
     <copyright>
       <year>2005</year>
       <holder>&FORMAL-RHI;</holder>



From fedora-docs-commits at redhat.com  Sat Nov  5 15:19:17 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat,  5 Nov 2005 10:19:17 -0500
Subject: release-notes hardware-reqs-it.xml,1.1,1.2
Message-ID: <200511051519.jA5FJHD9011998@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11981/release-notes

Modified Files:
	hardware-reqs-it.xml 
Log Message:



Index: hardware-reqs-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/hardware-reqs-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hardware-reqs-it.xml	4 Nov 2005 19:56:08 -0000	1.1
+++ hardware-reqs-it.xml	5 Nov 2005 15:19:09 -0000	1.2
@@ -2,7 +2,7 @@
   <title>Requisiti Hardware</title>
   <para>
     Le seguenti informazioni rappresentano il minimo requisito
-    hardware necessario ad installare con successo &DISTRO; &DISTROVER;.
+    hardware necessario per installare con successo &DISTRO; &DISTROVER;.
   </para>
   <note>
     <title>Nota</title>
@@ -29,7 +29,7 @@
       <title><!-- <remark os="test">(x86)</remark>--> Nota</title>
 
       <para><!-- <remark os="test">(x86)</remark> --> Le seguenti specifiche di CPU
-	sono dichiarate in termini di processori Intel.  Altri
+	sono dichiarate in paragone ai processori Intel.  Altri
 	processori (notoriamente, offerti da AMD, Cyrix, e VIA) che
 	sono compatibili ed equivalenti ai seguenti processori Intel
 	possono essere usati con &DISTRO;.</para>
@@ -79,7 +79,7 @@
     </itemizedlist>
   </section>
   <section>
-    <title>Requisiti di spazio su Hard Disk</title>
+    <title>Requisiti di spazio su sisco rigido</title>
 
     <para>Questa sezione elenca lo spazio necessario all'installazione di &DISTRO;
       &DISTROVER;.</para>
@@ -92,7 +92,7 @@
 	<emphasis>dopo</emphasis> che l'installazione ?? stata completata.
 	Comunque, dello spazio su disco aggiuntivo ?? richiesto durante
 	l'installazione per supportare l'ambiente di'installazione.  Questo
-	spazio aggiuntivo corrisponde alla dimensione dello
+	spazio aggiuntivo corrisponde alla dimensione del file
 	<filename>/Fedora/base/stage2.img</filename> (sul CD-ROM 1) pi??
 	la grandezza dei files in <filename>/var/lib/rpm</filename> sul sistema
 	installato.</para>
@@ -103,7 +103,7 @@
 	mentre pi?? di 175MB possono essere necessari per un installazione
 	del tipo "Installa tutto".</para>
 
-      <para>Inoltre, tenete in mente che dello spazio aggiuntivo pu?? essere necessario
+      <para>Inoltre, tenete a mente che dello spazio aggiuntivo pu?? essere necessario
 	per ogni dato utente, e che almeno il 5% di spazio libero deve essere mantenuto
 	per il funzionamento appropriato del sistema.</para>
     </note>
@@ -111,7 +111,7 @@
       <!-- Get actual numbers from installer, multiply by 1.1, and round -->
       <!-- up to the nearest 10MB or .1GB -->
     <para>
-      This list is for 32-bit x86 systems:
+      Questa elenco ?? per i sistemi a 32-bit x86:
     </para>
     <itemizedlist arch="x86">
       <listitem>
@@ -190,7 +190,7 @@
       </listitem>
 
       <listitem>
-	<para><!-- <remark os="test">(x86)</remark> --> Recomandata per
+	<para><!-- <remark os="test">(x86)</remark> --> Raccomandata per
 	  la modalit?? grafica: 256MB</para>
       </listitem>
     </itemizedlist>
@@ -239,13 +239,13 @@
       </listitem>
       <listitem>
 	<para>
-	  <!--<remark os="test">(x86)</remark> --> Recommandato per
+	  <!--<remark os="test">(x86)</remark> --> Raccommandato per
 	  la modalit?? testo: 233 MHz G3 o superiore
 	</para>
       </listitem>
       <listitem>
 	<para>
-	  <!-- <remark os="test">(ppc)</remark> --> Recommendeto per
+	  <!-- <remark os="test">(ppc)</remark> --> Raccommendato per
 	  la modalit?? grafica: 400 MHz G3 o superiore
 	</para>
       </listitem>



From fedora-docs-commits at redhat.com  Sat Nov  5 15:43:34 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat,  5 Nov 2005 10:43:34 -0500
Subject: release-notes install-notes-it.xml,1.1,1.2
Message-ID: <200511051543.jA5FhYaI012038@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12021/release-notes

Modified Files:
	install-notes-it.xml 
Log Message:



Index: install-notes-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- install-notes-it.xml	4 Nov 2005 19:56:08 -0000	1.1
+++ install-notes-it.xml	5 Nov 2005 15:43:27 -0000	1.2
@@ -9,7 +9,7 @@
     <title>Nota</title>
     <para>
       Se intendi scaricare l'immagine ISO DVD di &DISTRO; &DISTROVER;,
-      tieni in mente che non tutti gli strumenti di download file possono
+      tieni a mente che non tutti gli strumenti di download file possono
       scaricare files pi?? grandi di 2GB.  Per esempio,
       <command>wget</command> si chiuderebbe con un errore <computeroutput>File size
 	limit exceeded</computeroutput>.
@@ -71,13 +71,13 @@
 	<varlistentry>
 	  <term>Apple Macintosh </term>
 	  <listitem>
-	    <para>The bootloader avvier?? automaticamente
+	    <para>Il bootloader avvier?? automaticamente
 	      l'appropriato installer a 32-bit o 64-bit.  Il supporto del power
 	      management, incluso lo sleep e l'amministrazione della retroilluminazione,
 	      ?? presente nel pacchetto <filename>apmud</filename>,
-	      che ?? in &FEX;. &FEX; per &FC; ?? configurato per impostazione predefinita
+	      in &FEX;. &FEX; per &FC; ?? per impostazione predefinita, gi?? configurato
 	      per yum. Seguendo l'installazione,
-	      <filename>apmud</filename> pu?? essere installato seguendo il
+	      <filename>apmud</filename> pu?? essere installato eseguendo il
 	      comando <command>yum install apmud</command> in un
 	      terminale.
 	    </para>
@@ -87,8 +87,8 @@
 	  <term>64-bit IBM eServer pSeries (POWER4/POWER5)</term>
 	  <listitem>
 	    <para>Dopo aver utilizzato OpenFirmware per avviare il CD, il
-	      bootloader (<command>yaboot</command>) dovr??
-	      automaticamente avviare l'installer a 64-bit.
+	      bootloader (<command>yaboot</command>) avvier??
+	      automaticamente l'installer a 64-bit.
 	    </para>
 	  </listitem>
 	</varlistentry>
@@ -105,9 +105,9 @@
 	<varlistentry>
 	  <term>Genesi Pegasos II</term>
 	  <listitem>
-	    <para>A cominciare da &DISTRO; &DISTROVER;, un firmware con pieno supporto
+	    <para>Anche per &DISTRO; &DISTROVER;, un firmware con pieno supporto
 	      per i filesystems ISO9660 non ?? ancora stato rilasciato per
-	      Pegasos.  Comunque, pu?? essere usata l'immagine di boot da network. Al
+	      Pegasos.  Comunque, pu?? essere usata l'immagine di network boot. Al
 	      prompt di OpenFirmware, inserite il comando:
 	    </para>
 <screen>
@@ -126,14 +126,14 @@
 	  <term>Avvio via network</term>
 	  <listitem>
 	    <para>Ci sono immagini combinate contenenti il kernel d'installazione
-	      ed il ramdisk nella directory images/netboot/ dell'albero
+	      ed il ramdisk nella directory <filename>images/netboot/</filename> dell'albero
 	      d'installazione. Queste sono intese per l'avvio da network con
 	      TFTP, ma possono essere usate in molti modi.
 	    </para>
 	    <para>
 	      Il comando <command>yaboot</command> supporta l'avvio tftp
 	      per IBM eServer pSeries ed Apple Macintosh. &FED;
-	      raccomanda di usare yaboot sulle immagini netboot.
+	      raccomanda di usare <command>yaboot</command> sulle immagini netboot.
 	    </para>
 	</listitem>
 	</varlistentry>
@@ -147,18 +147,18 @@
       <listitem>
 	<para>
 	  Il programma d'installazione di &DISTRO; ha la capacit?? di testare
-	  l'intyegrit?? dei media d'installazione. Funziona con i metodi di
+	  l'integrit?? dei media d'installazione. Funziona con i metodi di
 	  installazione CD, DVD, hard drive ISO, e NFS ISO. &RH;
-	  raccomanda che tu esegua il test di tutti i media prima di
-	  cominciare il processo d'installazione, e prima di riportare qualsiasi
-	  rapporto d'errore inerente l'installazione (molti degli errori riportati sono
+	  ti raccomanda di eseguire il test di tutti i media prima di
+	  cominciare il processo d'installazione, e prima di inviare qualsiasi
+	  rapporto d'errore inerente l'installazione (molti degli errori inviati sono
 	  attualmente causati da CDs masterizzati inappropriatamente). Per usare questo test, scrivete
-	  <command>linux mediacheck</command> al prompt
-	  <prompt>boot:</prompt>.
+	  <command>linux mediacheck</command> al
+	  <prompt>boot:</prompt> prompt.
 	</para>
 	<para>
 	  La funzione <command>mediacheck</command> ?? altamente
-	  sensitiva, e pu?? restituire alcuni dischi utilizzabili come errati.
+	  sensitiva, e pu?? ritenere errati alcuni dischi utilizzabili.
 	  Questo risultato ?? spesso causato dal software di scrittura del disco che non
 	  include il padding quando vengono creati dischi dai files ISO.  Per ottenere
 	  i migliori risultati con <command>mediacheck</command>, eseguite il boot con
@@ -170,7 +170,7 @@
 	<para>
 	  Usa l'utilit?? <command>sha1sum</command> per verificare i dischi
 	  prima di portare a termine un installazione.  Questo test identifica
-	  accuratamente dischi che non sono validi o identici ai files
+	  accuratamente dischi non sono validi o non identici ai files
 	  immagine ISO.
 	</para>
       </listitem>
@@ -180,11 +180,11 @@
 	  %%%</remark>
 -->
 	<para>
-	  <!-- <remark os="test">(x86)</remark> --> Testing della memoria possono essere
+	  <!-- <remark os="test">(x86)</remark> --> Dei Test della memoria possono essere
 	  effettuati prima di eseguire l'installazione di &DISTRO; immettendo
-	  <command>memtest86</command> al prompt <prompt>boot:</prompt>.
-	  Cio causa l'avvio standalone del software di testing della
-	  memoria Memtest86. Il test di Memtest86 continua fino a che
+	  <command>memtest86</command> al <prompt>boot:</prompt> prompt.
+	  Questo causa l'avvio standalone del software di testing della
+	  memoria Memtest86. Le verifiche di Memtest86 continuano fino a che
 	  il tasto <keycap>Esc</keycap> non viene premuto.
 	</para>
 	<para>
@@ -216,7 +216,7 @@
 	<para>
 	  Certe configurazioni hardware (in particolare quelle con
 	  gli schermi LCD) potrebbero dare problemi durante l'avvio del
-	  programma di'installazione di &DISTRO;.  In queste circostanze, ricominciate
+	  programma d'installazione di &DISTRO;.  In queste circostanze, ricominciate
 	  l'installazione, ed aggiungete l'opzione "<command>nofb</command>" nella
 	  linea di comando di boot.
 	</para>
@@ -268,7 +268,7 @@
 	  <!-- <remark os="test">(x86)</remark> --> Ci sono state
 	  problematiche osservate durante l'aggiornamento di sistemi &RHL;
 	  7.<replaceable>&lt;x&gt;</replaceable>, 8.0, 9, e &FC; 1, 2,
-	  e 3 dove pacchetti di terze parti sono stati installati che
+	  e 3 dove pacchetti di terze parti che sono stati installati
 	  sono in conflitto con i pacchetti forniti da &FP;.  Un esempio ??
 	  Ximian GNOME.
 	</para>
@@ -304,7 +304,7 @@
 	<para>
 	  <!-- <remark os="test">(x86)</remark> -->
 	  <emphasis>Devi</emphasis> risolvere la sovrapposizione di versione usando
-	  uno delle scelte suindicate.  Un fallimento nella procedura porter?? ad una
+	  una delle scelte suindicate.  Un fallimento nella procedura porter?? ad una
 	  configurazione di GNOME instabile.
 	</para>
       </listitem>



From fedora-docs-commits at redhat.com  Sat Nov  5 17:47:14 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat,  5 Nov 2005 12:47:14 -0500
Subject: release-notes java-package-it.xml, 1.1, 1.2 package-notes-it.xml,
	1.2, 1.3 server-tools-it.xml, 1.1, 1.2
Message-ID: <200511051747.jA5HlEhj015238@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15217/release-notes

Modified Files:
	java-package-it.xml package-notes-it.xml server-tools-it.xml 
Log Message:



Index: java-package-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/java-package-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- java-package-it.xml	4 Nov 2005 19:56:57 -0000	1.1
+++ java-package-it.xml	5 Nov 2005 17:47:06 -0000	1.2
@@ -1,7 +1,7 @@
 <section id="sn-java-packages">
   <title>Raccomandazioni sul pacchetto Java</title>
   <caution>
-    <title>Information Out-of-Date</title>
+    <title>Informazioni non aggiornate</title>
     <para>
       Il contenuto in questa sezione ha necessit?? di essere aggiornato per &DISTRO;
       &DISTROVER;
@@ -9,8 +9,8 @@
   </caution>
   <para>
     Gli utenti di &FC; &LOCALVER; sono avvisati di non utilizzare i pacchetti RPM Java forniti
-    da Sun.  Essi contengono <computeroutput>Forniscono</computeroutput> quel
-    conflitto con i nomi usati nei pacchetti forniti come parte di &FC;
+    da Sun.  Essi contengono <computeroutput>producono</computeroutput> un
+    conflitto con i nomi usati nei pacchetti distribuiti come parte di &FC;
     &LOCALVER;.  Per questo motivo, Sun Java potrebbe scomparire da un
     sistema installato durante le operazioni di aggiornamento dei pacchetti.
   </para>


Index: package-notes-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- package-notes-it.xml	5 Nov 2005 14:13:04 -0000	1.2
+++ package-notes-it.xml	5 Nov 2005 17:47:06 -0000	1.3
@@ -26,7 +26,7 @@
 ]>
 -->
 <section id="sn-package-notes">
-  <title>Note Specifiche dei pacchetti</title>
+  <title>Note specifiche sui pacchetti</title>
   <!--
   FIXME
   Necessita di aggiornamenti per l'intero contenuto per FC5.
@@ -66,7 +66,7 @@
 	  url="http://fedoraproject.org/wiki/Extras">http://fedoraproject.org/wiki/Extras</ulink>
       </para>
       <para>
-	Se vuoi installare un qualsiasi software disponibile da
+	Se vuoi installare un qualsiasi software disponibile in
 	Fedora extras puoi usare <command>yum</command>.
       </para>
 <screen>
@@ -81,7 +81,7 @@
       </para>
     </section>
     <section id="sn-audit-daemon">
-      <title>Audit Daemon <command>auditd</command> ed i files di log</title>
+      <title>Il demone di audit <command>auditd</command> ed i files di log</title>
       <para>
 	Il demone audit, auditd, ?? abilitato per impostazione predefinita. Quando
 	auditd ?? in esecuzione, il kernel direziona i messagi a
@@ -90,12 +90,12 @@
       </para>
       <para>
 	I messaggi AVC per &SEL; sono spediti usando l'infrastruttura audit.
-	Questi messaggi sno adesso in
+	Questi messaggi sono adesso in
 	<filename>/var/log/audit/audit.log</filename>.
       </para>
       <para>
 	Quando auditd non ?? in esecuzione, il kernel passa i messaggi di audit a
-	syslog.  Questi logs sono tipicamente lasciati tenuti in <filename>/var/log/messages</filename> e
+	syslog.  Questi logs sono tipicamente tenuti in <filename>/var/log/messages</filename> e
 	sono visibili usando <command>dmesg</command>.
       </para>
       <para>
@@ -128,12 +128,12 @@
 	cancellazione ?? pi?? veloce (quando ?? usato <parameter>-fexception</parameter>,
 	anche nel codice C) e che le interfacce aggiuntive sono ora
 	disponibili senza parametri speciali per compilatori e linker.  In
-	altre parole, non hai bisogno di usare
+	altre parole, non avrai pi?? bisogno di usare
 	<option>-I/usr/include/nptl</option> e
-	<option>-L/usr/lib{,64}/nptl</option> mai pi??.  Nota che
+	<option>-L/usr/lib{,64}/nptl</option>.  Nota che
 	<parameter>lib{,64}</parameter> deve essere interpretata come lib64 sulle
 	piattaforme che impostano DSOs nelle directories <filename>lib64/</filename>,
-	e <filename>lib/</filename> altrimenti.
+	ed altrimenti <filename>lib/</filename>.
       </para>
       <para>
 	In &FC; &LOCALVER; ?? ancora possibile creare codice usando le
@@ -159,7 +159,7 @@
 	Questa variabile aggiuntiva ?? richiesta perch?? le librerie run/time
 	sono state spostate.  Ci potrebbero essere programmi
 	che non funzionano se usassero uno sfortunato
-	<envar>DT_RPATH</envar> (che altrimenti sovrascriver?? l'impostazione
+	<envar>DT_RPATH</envar> (che sovrascriver?? l'impostazione
 	<envar>LD_LIBRARY_PATH</envar>).
       </para>
       <para>
@@ -174,13 +174,13 @@
 	</para>
       </important>
       <para>
-	In generale, la conversione all'uso di NPTL non ?? un problema.
+	In generale, la conversione all'uso di NPTL non ?? stata un problema.
       </para>
     </section>
     <section>
       <title>Abilitare il database <filename>slocate</filename></title>
       <para>
-	Il database necessario all'utilit?? <command>locate</command> non ??
+	Il database necessario all'utilit?? <command>locate</command> non viene
 	pi?? creato per impostazione predefinita. Abilita la creazione del database
 	impostando <computeroutput>DAILY_UPDATE</computeroutput> su
 	<option>yes</option> in <filename>/etc/updatedb.conf</filename>
@@ -188,7 +188,7 @@
       </para>
     </section>
     <section>
-      <title>Controlli ristretti in <filename>openssh</filename></title>
+      <title>Controlli pi?? stretti in <filename>openssh</filename></title>
       <para>
 	La versione di OpenSSH in &FC; &LOCALVER; ?? basata su OpenSSH
 	3.9 ed include stretti controlli sui permessi e la propriet?? per il file
@@ -197,7 +197,7 @@
 	<command>ssh</command> cesser?? l'esecuzione.
       </para>
       <para>
-	COntrollate che <filename>~/.ssh/config</filename> si aposseduto dal
+	Controllate che <filename>~/.ssh/config</filename> sia posseduto dal
 	proprietario di <filename>~/</filename>, e che i suoi permessi siano
 	impostati a 600.
       </para>
@@ -206,27 +206,28 @@
 -rw-------  1 username username 400 May  5 18:44 /home/username/.ssh/config
 </screen>
       <para>
-	La directory <filename>~/</filename> ?? la scociatoia a linea di comando
+	La directory <filename>~/</filename> ?? l'abbreviazione nella linea di comando
 	per la home directory dell'utente loggato, solitamente
 	<filename>/home/username/</filename>.
       </para>
       <para>
-	In aggiunta, OpenSSH non ?? pi?? configurato per richiedere l'X11
-	forwarding per impostazione predefinita quando si connette ai servers.  Per abilitare l'X11
-	forwarding, l'opzione <option>-X</option> o <option>-Y</option>
-	deve essere specificata, o l'opzione <option>ForwardX11</option>
-	deve essere abilitata nel file <filename>~/.ssh/config</filename>.
+	In pi??, OpenSSH non ?? pi?? configurato per impostazione predefinita,
+	per richiedere l'X11 forwarding quando ci si connette ai servers.
+	Per abilitare l'X11 forwarding, l'opzione <option>-X</option> o
+	<option>-Y</option> deve essere specificata, o l'opzione
+	<option>ForwardX11</option> deve essere abilitata nel file <filename>~/.ssh/config</filename>.
       </para>
       <para>
 	Il comportamento dei clients <command>ssh</command> che sono stati invocati
 	con l'opzione <option>-X</option> ?? cambiata.  In OpenSSH 3.8
-	e superiori, l'X11 forwarding ?? eseguito in modo che
-	le applicazioni siano eseguite come clients untrusted per impostazione predefinita.
+	e superiori, l'X11 forwarding ?? eseguito in modo che, per impostazione predefinita,
+	le applicazioni siano eseguite come clients privi di credenziali (untrusted).
 	Precedentemente, l'X11 forwarding era effettuato in modo tale che le applicazioni
-	corressero sempre come clients verificati. Alcune applicazioni potrebbero non funzionare
-	in modo corretto quando eseguite come client non verificati.
+	fossero eseguite sempre come clients verificati.
+	Alcune applicazioni potrebbero non funzionare correttamente se eseguite
+	come client non verificati.
 	Per eseguire l'X11 forwarding affinch?? le applicazioni siano eseguite come
-	clients trusted, invocate ssh con l'opzione
+	clients verificati, invocate ssh con l'opzione
 	<option>-Y</option> invece che l'opzione <option>-X</option>,
 	o impostate <option>ForwardX11Trusted</option> nel file
 	<option>~/.ssh/config</option>.
@@ -249,13 +250,13 @@
   <section id="sn-packages-core">
     <title>Core</title>
     <para>
-      Questa sezione contiene le componenti pi?? elemntari di &DISTRO;,
+      Questa sezione contiene le componenti pi?? elementari di &DISTRO;,
       incluso il kernel.
     </para>
     <section>
       <title>yum</title>
       <para>
-	Il database sqllite ?? utilizzato da yum ora, e rende le prestazioni
+	Il database sqllite ?? ora utilizzato da yum, e rende le prestazioni
 	notevolmente pi?? veloci.
       </para>
       <para>


Index: server-tools-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/server-tools-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- server-tools-it.xml	4 Nov 2005 19:59:37 -0000	1.1
+++ server-tools-it.xml	5 Nov 2005 17:47:06 -0000	1.2
@@ -1,7 +1,7 @@
 <section id="sn-server-sys-config">
   <title>Strumenti di configurazione del server e del sistema</title>
   <caution>
-    <title>Information Out-of-Date</title>
+    <title>Informazioni non aggiornate</title>
     <para>
       Il contenuto in questa sezione ha necessit?? di essere aggiornato per &DISTRO;
       &DISTROVER;



From fedora-docs-commits at redhat.com  Sat Nov  5 18:08:44 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat,  5 Nov 2005 13:08:44 -0500
Subject: release-notes kernel-it.xml,1.1,1.2
Message-ID: <200511051808.jA5I8idO016759@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16742/release-notes

Modified Files:
	kernel-it.xml 
Log Message:



Index: kernel-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/kernel-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- kernel-it.xml	4 Nov 2005 19:56:57 -0000	1.1
+++ kernel-it.xml	5 Nov 2005 18:08:28 -0000	1.2
@@ -26,7 +26,7 @@
   url="http://www.kernel.org"><filename>kernel.org</filename></ulink>.
     </para>
     <para>
-      Potrai ottenere una lista di ciascuna di queste patches usando il comando sul pacchetto di &FC;:
+      Potrai ottenere una lista di ciascuna di queste patches usando il seguente comando sul pacchetto di &FC;:
     </para>
 <screen width="56">
 <command>rpm <parameter class="option">-qpl</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
@@ -35,12 +35,12 @@
   <section id="sn-kernel-flavors">
     <title>Tipi di Kernel</title>
     <para>
-      &FC; include i seguenti kernel builds:
+      &FC; include i seguenti kernel compilati:
     </para>
     <itemizedlist>
       <listitem>
         <para>Kernel nativo, nelle variet?? uniprocessore e
-	  <abbrev>SMP</abbrev>. Sorgenti configurati sono
+	  <abbrev>SMP</abbrev>. I sorgenti configurati sono
 	  disponibili nel pacchetto
 	  <filename>kernel-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>.
         </para>
@@ -48,7 +48,7 @@
       <listitem>
         <para>
           Kernel virtuale per l'uso con il pacchetto emulatore <application>Xen</application>.
-	  Sorgenti configurati sono disponibili nel pacchetto
+	  I sorgenti configurati sono disponibili nel pacchetto
 	  <filename>kernel-xen0-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>.
         </para>
       </listitem>
@@ -57,7 +57,7 @@
       I sorgenti per entrambe i tipi di kernel possono essere installati allo stesso momento.
       I files sono installati nell'albero
       <filename>/usr/src/kernels/<replaceable>version</replaceable>[-xen0]-<replaceable>arch</replaceable>/</filename>.
-      Usa il comando:
+      Usando il comando:
     </para>
 <screen width="56">
 <command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename></command>
@@ -73,7 +73,7 @@
 	la directory <filename>/usr/src/linux</filename>. Se fai un link
 	simbolico, come mostrato sotto, sarai in grado si usare quel
 	materiale dapprendimento con i pacchetti di &FC;. Installa gli
-	appropriati sorgenti del kernel, come mostrato sopra, e poi:
+	appropriati sorgenti del kernel, come mostrato sopra, quindi:
       </para>
 <screen width="56">
 <command>ln <parameter class="option">-s</parameter> <filename>/usr/src/kernels/kernel-<replaceable>all-the-rest</replaceable></filename> <filename>/usr/src/linux</filename></command>
@@ -117,7 +117,7 @@
 	Per semplificare le seguenti direttive, assumiamo che tu voglia
 	configurare i sorgenti del kernel che combaciano con la versione del kernel
 	che hai in esecuzione. Nei prossimi passi, dovrai capire che
-	la frase
+	la parola
 	<replaceable>version</replaceable> si riferisce alla versione del kernel
 	mostrata da questo comando:
       </para>
@@ -135,7 +135,7 @@
         <itemizedlist>
           <listitem>
             <para>La directory <filename>SRPMS/</filename> sull'appropriato
-	      <abbrev>CD</abbrev> immagine <filename>ISO</filename>
+	      <abbrev>CD</abbrev> o immagine <filename>ISO</filename>
 	      <wordasword>SRPMS</wordasword>.
               </para>
           </listitem>
@@ -200,7 +200,7 @@
 	  Per esempio, il file di configurazione i686 SMP
 	  ?? nominato
 	  <filename>configs/kernel-<replaceable>version</replaceable>-i686-smp.config</filename>. 
-	  Lancia il seguente comando per porre il file di configurazione deiderato
+	  Lancia il seguente comando per porre il file di configurazione desiderato
 	  nel posto giusto per la compilazione:
         </para>
 <screen width="56">
@@ -217,18 +217,18 @@
           Ogni kernel ha un nome basato sul numero della sua versione. Questo ??
 	  il valore che mostra il comando <command>uname -r</command>.
 	  Il nome del kernel ?? definito dalle prime quattro linee del
-	  kernel <filename>Makefile</filename>. Per proteggere gli innocenti,
+	  kernel <filename>Makefile</filename>. Per proteggere gli inconsapevoli,
 	  il <filename>Makefile</filename> ?? stato cambiato per generare
 	  un kernel con un nome differente da quello in esecuzione.
 	  Prima che un modulo possa essere accettato dal kernel in esecuzione,
 	  quel modulo deve essere compilato per un kernel con il nome
 	  corretto.  Per fare questo, devi editare il kernel
-	  <filename>Makefile</filename>
+	  <filename>Makefile</filename>.
         </para>
         <para>
           Per esempio, se con <command>uname -r</command> restituir?? la
 	  stringa <systemitem
-	    class="osname">2.6.11-1.234_FC4</systemitem>, canmbia la definizione
+	    class="osname">2.6.11-1.234_FC4</systemitem>, cambia la definizione
 	  <systemitem class="macro">EXTRAVERSION</systemitem>
 	  da questo:
         </para>
@@ -242,7 +242,7 @@
 EXTRAVERSION = -1.234_FC4
 </screen>
         <para>
-          Cos??, sostituite ogni cosa dall'inizio alla fine.
+          E cos?? via, sostituite ogni cosa dall'inizio alla fine.
         </para>
       </step>
       <step>
@@ -261,7 +261,7 @@
   <section id="sn-kernel-3rdparty">
     <title>Compilare solo i moduli del Kernel</title>
     <para>
-      Un albero dei sorgenti esploso <emphasis>non</emphasis> ?? necessario per
+      <emphasis>Non</emphasis> ?? necessario un albero dei sorgenti esploso per
       compilare un modulo del kernel, tipo il tuo driver di periferica, per il
       kernel in uso.
     </para>
@@ -290,15 +290,15 @@
       &DISTRO; aggiunge supporto per i sistemi cluster. Ci?? richiede un
       kernel speciale che funzioni in congiunzione con alcune utilit?? 
       user-space, tipo i demoni di amministrazione. Di conseguenza, per rimuovere
-      un simile kernel, forse dopo un aggiornamento,
+      un simile kernel, ad esempio dopo un aggiornamento,
       <emphasis>non puoi</emphasis> semplicemente usare il comando <command>rpm -e
 	kernel-<replaceable>version</replaceable></command> come
       nelle precedenti distribuzioni poich?? questi pacchetti in user space
       dipendono dal pacchetto del kernel. Potresti elencare sia il pacchetto kernel
       ed i suoi pacchetti user space dependenti al comando <command>rpm
-	-e</command>, o potresti usare il comando <command>yum
-	remove kernel-<replaceable>version</replaceable></command>
-      invece, poich?? <command>yum</command> rimuover?? automaticamente
+	-e</command>, oppure invece potresti usare il comando <command>yum
+	remove kernel-<replaceable>version</replaceable></command>,
+      e <command>yum</command> rimuover?? automaticamente
       i pacchetti dependenti se necessario.
     </para>
   </section>



From fedora-docs-commits at redhat.com  Sat Nov  5 19:38:10 2005
From: fedora-docs-commits at redhat.com (Yoshinari Takaoka (mumumu))
Date: Sat,  5 Nov 2005 14:38:10 -0500
Subject: install-guide fedora-install-guide-abouttoinstall-ja_JP.xml, NONE,
 1.1 fedora-install-guide-acknowledgements-ja_JP.xml, NONE,
 1.1 fedora-install-guide-beginninginstallation-ja_JP.xml, NONE,
 1.1 fedora-install-guide-bootloader-ja_JP.xml, NONE,
 1.1 fedora-install-guide-diskpartitioning-ja_JP.xml, NONE,
 1.1 fedora-install-guide-firewallconfig-ja_JP.xml, NONE,
 1.1 fedora-install-guide-firstboot-ja_JP.xml, NONE,
 1.1 fedora-install-guide-installingpackages-ja_JP.xml, NONE,
 1.1 fedora-install-guide-installtypes-ja_JP.xml, NONE,
 1.1 fedora-install-guide-intro-ja_JP.xml, NONE,
 1.1 fedora-install-guide-ja_JP.xml, NONE,
 1.1 fedora-install-guide-locale-ja_JP.xml, NONE,
 1.1 fedora-install-guide-networkconfig-ja_JP.xml, NONE,
 1.1 fedora-install-guide-nextsteps-ja_JP.xml, NONE,
 1.1 fedora-install-guide-other-instmethods-ja_JP.xml, NONE,
 1.1 fedora-install-guide-packageselection-ja_JP.xml, NONE,
 1.1 fedora-install-guide-rootpassword-ja_JP.xml, NONE,
 1.1 fedora-install-guide-timezone-ja_JP.xml, NONE, 1.1 fedora-instal!
 l-guide-upgrading-ja_JP.xml,NONE,1.1
Message-ID: <200511051938.jA5JcB5u018543@cvs-int.fedora.redhat.com>

Author: mumumu

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18509

Added Files:
	fedora-install-guide-abouttoinstall-ja_JP.xml 
	fedora-install-guide-acknowledgements-ja_JP.xml 
	fedora-install-guide-beginninginstallation-ja_JP.xml 
	fedora-install-guide-bootloader-ja_JP.xml 
	fedora-install-guide-diskpartitioning-ja_JP.xml 
	fedora-install-guide-firewallconfig-ja_JP.xml 
	fedora-install-guide-firstboot-ja_JP.xml 
	fedora-install-guide-installingpackages-ja_JP.xml 
	fedora-install-guide-installtypes-ja_JP.xml 
	fedora-install-guide-intro-ja_JP.xml 
	fedora-install-guide-ja_JP.xml 
	fedora-install-guide-locale-ja_JP.xml 
	fedora-install-guide-networkconfig-ja_JP.xml 
	fedora-install-guide-nextsteps-ja_JP.xml 
	fedora-install-guide-other-instmethods-ja_JP.xml 
	fedora-install-guide-packageselection-ja_JP.xml 
	fedora-install-guide-rootpassword-ja_JP.xml 
	fedora-install-guide-timezone-ja_JP.xml 
	fedora-install-guide-upgrading-ja_JP.xml 
Log Message:
initial japanese translation for fc5 test1. well done to me.


--- NEW FILE fedora-install-guide-abouttoinstall-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-abouttoinstall">
  <title>?????????????????????????????????</title>
    
  <para>
    <guilabel>???</guilabel> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FC; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>??????</guilabel> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <important>
    <title>?????????????????????????????????</title>
    <para>
      ??????????????????????????????????????????????????????????????????????????????&FC; ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
  </important>

  <figure id="fig-about-to-install">
    <title>???????????????????????????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/about-to-install.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/about-to-install.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	  ???????????????????????????????????????
        </phrase>
      </textobject>
    </mediaobject>
  </figure>

  <para>
    <guilabel>???</guilabel> ????????????????????????????????????????????????????????????
  </para>

  <para>
    ?????????????????????????????????????????????????????????????????????????????????&FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guibutton>?????????</guibutton> ????????????????????????????????????????????????????????????????????????????????????????????????<guibutton>??????</guibutton> ???????????????????????????????????????????????????
  </para>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-acknowledgements-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-acknowledgements">
  <title>??????</title>

  <para>
    ???????????????????????????????????????????????????Rahul Sundaram?????????anaconda???????????????????????????????????????
  </para>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-beginninginstallation-ja_JP.xml ---
<!-- $Id: -->
<chapter id="ch-beginninginstallation">
  <title>?????????????????????????????????</title>

  <para>
    &FC; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????CD?????????DVD??????????????????USB?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <note>
    <title>??????????????????????????????????????????????????????</title>
    <para>
      &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
  </note>

  <para>
    <indexterm>????????????????????????<primary>BIOS (Basic Input/Output System)</primary></indexterm> <firstterm>BIOS</firstterm> (Basic Input/Output System) ?????????????????????????????????????????????????????????????????????????????????????????????BIOS??????????????????????????????????????????????????????????????????????????????????????????&FC; ?????????????????????????????????????????????????????????????????????????????????????????????CD????????????DVD?????????????????????????????????????????????????????????????????????????????????????????????USB???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<indexterm><primary>PXE (Pre-boot eXecution Environment)</primary> </indexterm> <firstterm>PXE</firstterm> ??????????????????????????????????????????????????????????????????????!
 ?????????????????????????????PXE ("pixie"??????????????????)?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <para>
    ?????????????????????????????????????????????????????????????????????????????????????????????BIOS???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <note>
    <title>?????????????????????????????????</title>
    <para>
      <guilabel>?????????????????????????????????</guilabel> ????????????????????????????????????????????????????????????????????????<keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo> ??????????????????????????????????????????????????? ??????????????????????????????????????????????????? &FED; ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
  </note>


  <section id="sn-booting-from-disc">
    <title>?????????????????????????????????</title>

    <para>
      ???????????????????????????????????????????????????????????????
    </para>

    <procedure>
      <step>
	<para>???????????????????????????????????????????????????</para>
      </step>
      <step>
	<para>CD?????????DVD?????????????????????????????????????????????????????????</para>
      </step>
      <step>
	<para>?????? <prompt>boot:</prompt> ????????????????????????????????????????????????????????????????????????</para>
      </step>
    </procedure>

    <figure id="fig-boot">
      <title>???????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/boot.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/boot.png" format="PNG"/>
	</imageobject>
	<textobject id="tx-boot">
	  <phrase>
	    &FC; ???????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      <keycap>Enter</keycap> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????CD????????????DVD??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<prompt>boot:</prompt> ??????????????????????????? <userinput>linux</userinput> ???????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <itemizedlist>
      <listitem>
	<para>
          ???????????????????????????????????????????????????????????????????????????????????????????????????<userinput>askmethod</userinput> ????????????
	</para>
      </listitem>
      <listitem>
	<para>
          ??????????????????????????????????????????????????????<userinput>text</userinput> ????????????
	</para>
      </listitem>
      <listitem>
	<para>
          ?????????????????????????????????????????????????????????????????????????????????????????????<userinput>acpi=off</userinput> ????????????
	</para>
      </listitem>
    </itemizedlist>

    <para>
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FDPDOCS-URL; ????????????????????????
    </para>

    <para>
      <prompt>boot:</prompt> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-media-test">
      <title>???????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/media-test.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/media-test.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ???????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ???????????????????????????????????????<guibutton>OK</guibutton> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????<guibutton>Skip</guibutton> ?????????????????????
    </para>

    <caution>
      <title>??????????????????????????????</title>
      <para>
        ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
    </caution>

    <para>
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-mediacheck-result">
      <title>?????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/mediacheck-result.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/mediacheck-result.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
            ?????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      <guibutton>OK</guibutton> ??????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-mediacheck-next">
      <title>????????????????????????????????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/mediacheck-next.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/mediacheck-next.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ????????????????????????????????????????????????????????????????????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ?????????????????????????????????????????? <guibutton>Test</guibutton> ????????????????????????????????????????????????????????????????????????????????????????????????<guibutton>Continue</guibutton> ??????????????????????????????
    </para>

<!--

    <note>
      <title>The <guilabel>Media Check</guilabel> may fail usable
	discs</title>
      <para>
	Discs that are valid and usable may still fail to pass the
	<guilabel>Media Check</guilabel>.
      </para>
    </note>

    Let's hash this out before we print this in the guide.  The media
    check performs a MD5 checksum over the entire data area of a CD,
    save for a small reserved area at the top, which is not used for any
    installation data.  It is possible for a disc to fail this sum and
    still install, because the error may occur in, for example, a RPM
    package that the user has not selected.  However, the user may
    encounter this error later when he tries to install that package.
    Or he may pass the disc(s) on to another person, who may make
    different choices and thus induce the media error.

    It's best to have discs that pass this check; although the user
    *may* not have a problem, we don't want to encourage people to try
    installing from bad discs on that chance. - PWF.

-->

    <para>
      ????????????????????????????????????<guibutton>Continue</guibutton> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<userinput>linux askmethod</userinput> ??????????????? <prompt>boot:</prompt> ????????????????????????????????????&FC; ??????????????????????????????boot???????????????CD???????????????????????????????????? &FC; ????????????????????????????????????????????????, <filename>images/boot.iso</filename> ???ISO????????????????????????????????????????????????
    </para>

    <para>
      ISO???????????????????????????CD????????????????????????CD???????????????????????????CD??????????????????CD??????????????????????????????????????????????????????????????????????????????CD?????????????????????????????????????????????????????????????????????????????????????????????????????????CD???????????????????????????????????????????????????????????????????????????????????????????????????????????????Linux??????????????????????????????????????????????????????CD???CD??????????????????????????????????????????????????????????????????????????????
    </para>

<screen>
<userinput>cdrecord --device=<replaceable>cdwriter-device</replaceable> -tao -eject <replaceable>image-file.iso</replaceable></userinput>
</screen>

    <note>
      <title>BIOS??????????????????</title>
      <para>
        BIOS???????????????????????????????????????????????????????????????????????????????????????????????????PC??? &FC; ????????????????????????????????????????????????????????????????????????????????????BIOS?????????????????????????????????????????????
      </para>
    </note>

  </section>


  <section id="sn-using-otherbootmedia">
    <title>?????????????????????????????????????????????</title>

    <para>
      ????????????????????????????????????????????????????????????????????????USB?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>


    <section id="sn-preparing-otherbootmedia">
      <title>????????????????????????????????????</title>

      <warning>
	<title>???????????????</title>
	<para>
	  <emphasis>??????????????????????????????????????????????????????????????????????????????</emphasis> ??????????????????????????????????????????????????????????????????????????????????????????USB??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
      </warning>

      <para>
	&FC; ?????????????????????????????????????????????????????? <filename>images/diskboot.img</filename> ??????USB???????????????????????????????????????????????????????????????????????????????????????&FC; ?????????????????????FTP, Web????????? ???????????????????????????
      </para>

      <para>
        ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????Windows??????Linux???????????????????????????Linux??????????????????????????? <command>dd</command> ???????????????????????????????????????<command>dd</command> ??????????????????????????????????????????????????? &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>

      <procedure>
	<step>
	  <para>
	    ??????????????????????????????????????????
	  </para>
	</step>
	<step>
	  <para>
	    ???????????????????????????????????????????????????
	  </para>
	</step>
	<step>
	  <para>
            ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	</step>
	<step>
	  <para>
	    ??????????????????????????????????????????
	  </para>
	</step>
	<step>
	  <para>
             ???????????????????????????????????????????????????????????????????????????

<screen>
<userinput>dd if=diskboot.img of=/dev/sda1</userinput>
</screen>

	  </para>
	</step>
      </procedure>

    </section>


    <section id="sn-booting-from-otherbootmedia">
      <title>?????????????????????????????????</title>

      <para>
        ???????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>

      <procedure>
	<step>
          <para>
            ???????????????????????????????????????????????????
	  </para>
	</step>
	<step>
          <para>
	    ?????????????????????????????????????????????
	  </para>
	</step>
	<step>
          <para>
            ?????????????????????????????? <prompt>boot:</prompt> ?????????????????????????????????????????????????????????????????????????????????????????????????????? <keycap>Enter</keycap> ????????????????????????
	  </para>
	</step>
      </procedure>

      <note>
	<title>BIOS??????????????????</title>
	<para>
          BIOS???????????????????????????????????????????????????????????????????????????????????????????????????PC??? &FC; ???????????????>?????????????????????????????????????????????????????????????????????BIOS??????????????????????????????????????????????????????????????????
	</para>
      </note>

    </section>

  </section>


  <section id="sn-booting-from-pxe">
    <title>PXE??????????????????????????????????????????????????????</title>

    <para>
      <indexterm>
        <primary>PXE (Pre-boot eXecution Environment)</primary>
      </indexterm> PXE ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? PXE ??????????????????????????????????????????????????????????????????????????????????????????
      <!-- Refer
      to <ulink url="SOME-URL">SOME-URL</ulink> for information on how
      to configure a PXE server.  [When this tutorial exists, uncomment
      this. - PWF.] -->
    </para>

    <para>
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????BIOS?????????????????????<option>Network Boot</option> ???????????? <option>Boot Services</option> ???????????????????????????????????????????????????????????????????????????PXE?????????????????????????????????????????????????????????????????????????????????????????? &FED; ???????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      PXE??????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <procedure>
      <step>
	<para>
          ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
      </step>
      <step>
	<para>
	  ?????????????????????????????????????????????
	</para>
      </step>
      <step>
	<para>
           ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
      </step>
    </procedure>

    <figure id="fig-pxe-instmethod">
      <title>Red Hat Network????????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/pxe-instmethod.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/pxe-instmethod.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    Red Hat Network???????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ?????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <note>
      <title>PXE ????????????????????????????????????</title>
      <para>
        ????????????PC??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????BIOS???????????????????????????????????????BIOS????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????PXE??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
    </note>

  </section>


</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-bootloader-ja_JP.xml ---
<!-- $Id: -->
<chapter id="ch-bootloader">
  <title>?????????????????????</title>

  <para>
    <firstterm>?????????????????????</firstterm> ?????????????????????????????????????????????????????????????????????????????????????????????????????????&FC; ????????????????????? <application>GRUB</application> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <para>
    ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????Linux???????????????????????????????????????????????????&FC; ??????????????????????????????????????????Linux???????????????????????????????????????????????????????????????????????????????????????<application>GRUB</application> ?????????????????????????????????????????????????????????<application>GRUB</application> ???????????????????????????????????????????????????????????????????????????????????????
  </para>

  <warning>
    <title>GRUB ???????????????????????????</title>
    <para>
      GRUB ???????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
  </warning>

  <para>
    ????????????????????????????????????????????????????????????????????????????????????
  </para>
  <figure id="fig-bootloader-config">
    <title>
      ?????????????????????????????????
    </title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="figs/bootloader-config.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="figs/bootloader-config.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>?????????????????????????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>

  <section id="sn-bootloader-config-change">
    <title>???????????????????????????????????????????????????</title>
    <para>
      ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <firstterm>????????????????????????</firstterm>??? <indexterm>
        <primary>?????????????????????????????????</primary>
      </indexterm> ???????????? <abbrev>MBR</abbrev> ??? GRUB ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guibutton>??????????????????????????????</guibutton> ??????????????????????????????<xref linkend="fig-bootloader-change"/> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <figure id="fig-bootloader-change">
      <title>??????????????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-change.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-change.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>??????????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <important>
     <title>???????????????????????????????????????</title>
      <para>
        ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <application>GRUB</application> ??????????????????????????????????????????????????????????????????????????????????????????<!-- FIXME: Add reference to startup disk elsewhere in the
	IG. - PWF. -->
      </para>
    </important>
  </section>

  <section id="sn-bootloader-others">
    <title>
      ???????????????????????????????????????????????????????????????
    </title>
    <para>
      ??????????????????????????????????????????????????????????????????????????????????????????&FC; ????????????????????????????????????<application>GRUB</application> ?????????????????????????????????????????????????????????<application>GRUB</application> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????GRUB ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <variablelist>
      <varlistentry>
        <term>
          <guibutton>??????</guibutton>
        </term>
        <listitem>
          <para>
            <guibutton>??????</guibutton> ??????????????????????????????????????????????????????????????? GRUB ?????????????????????&FC; ??? <xref linkend="fig-bootloader-others-popup"/> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????GRUB????????????????????????????????????????????????????????????????????????????????????
	  </para>
          <para>
            ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<application>GRUB</application> ????????????????????????????????????????????????????????????????????????????????????
	  </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guibutton>??????</guibutton>
        </term>
	<listitem>
	  <para>
            GRUB ?????????????????????????????????????????????????????????????????????????????????????????? <guibutton>??????</guibutton> ?????????????????????
	  </para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guibutton>Delete</guibutton>
        </term>
        <listitem>
          <para>
            GRUB ????????????????????????????????????????????????????????????????????????????????????????????? <guibutton>??????</guibutton> ?????????????????????
	  </para>
        </listitem>
      </varlistentry>
    </variablelist>
    <figure id="fig-bootloader-others-popup">
      <title>???????????????????????????????????????????????????????????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-others.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-others.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>???????????????????????????????????????????????????????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
  </section>

  <section id="sn-bootloader-password">
    <title>
      ?????????????????????????????????????????????
    </title>
    <para>
      <application>GRUB</application> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<application>GRUB</application> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <tip>
      <title>GRUB ????????????????????????????????????????????????</title>
      <para>
        ???????????????????????????????????????????????????????????????????????????????????????????????????????????????
????????????????????????????????????????????????????????????????????????<application>GRUB</application> ??????????????????????????????????????????
      </para>
      <para>
        ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <application>GRUB</application> ????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
    </tip>
    <para>
      ????????????????????????????????????????????????<guibutton>?????????????????????????????????????????????</guibutton> ????????????????????????????????????????????????<guibutton>????????????????????????</guibutton> ???????????????????????????????????????????????????????????????????????????????????????????????? <guibutton>????????????????????????</guibutton> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <figure id="fig-bootloader-password">
      <title>???????????????????????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-password.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-password.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>??????????????????????????????????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <tip>
      <title>??????????????????????????????????????????</title>
      <para>
        ?????????????????????????????????????????????????????????????????????????????????????????????
      </para>
    </tip>
    <warning>
      <title><application>GRUB</application> ?????????????????????????????????</title>
      <para>
        <application>GRUB</application> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <emphasis>?????????</emphasis>???????????????????????????????????????????????????????????????????????????????????????????????? <filename>/boot/grub/grub.conf</filename> ???????????????password???????????????????????????????????????????????????????????????????????????????????????GRUB ????????????????????????????????????????????? &FC; ???????????????????????????????????????????????? "???????????????" ?????????????????????????????????????????? 
      </para>
    </warning>
    <para>
      <application>GRUB</application> ?????????????????????????????????????????????????????????<command>grub-md5-crypt</command> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <command>man grub-md5-crypt</command> ??????????????????????????????
    </para>
  </section>

  <section id="sn-bootloader-advanced">
    <title>
      ????????????????????????????????????????????????
    </title>
    <para>
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <application>GRUB</application> ????????????????????????<indexterm>
        <primary>?????????????????????????????????</primary>
      </indexterm> ????????????????????????????????? (<abbrev>MBR</abbrev>) ????????????????????????????????????????????????????????????????????????
    </para>
    <para>
      ????????????????????????????????? <abbrev>MBR</abbrev> ????????????????????????<application>GRUB</application> ???Linux?????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ?????????????????????????????????????????????????????? ??????????????????
    </para>
    <para>
      <abbrev>BIOS</abbrev> ??? &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????<abbrev>BIOS</abbrev> ??????????????????????????? &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guibutton>LBA32 ???????????????</guibutton> ???????????????????????????????????????????????????
    </para>
    <para>
      Linux kernel ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????????????????????????????????????????????????
    </para>
    <note>
     <title>???????????????????????????</title>
      <para>
        kernel ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????: <userinput>man bootparam</userinput>??????????????????????????????????????????????????????kernel?????????????????????????????????????????????????????????????????????????????????
      </para>
    </note>
    <para>
      ??????????????????????????????????????????<guibutton>??????????????????????????????????????????????????????</guibutton> ????????????????????????????????????????????????<guibutton>???</guibutton> ?????????????????? <xref linkend="fig-bootloader-advanced"/> ???????????????????????????????????????????????????
    </para>
    <note>
     <title>???????????????????????????</title>
      <para>
        &FC; ???????????????????????? ?????????????????????????????????????????????????????? ?????????????????????????????????????????????????????? <emphasis>??????</emphasis>??????????????? ???????????????????????????????????????????????? ???????????????????????????????????????
      </para>
    </note>
    <figure id="fig-bootloader-advanced">
      <title>????????????????????????????????????????????????</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-advanced.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloader-advanced.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>????????????????????????????????????????????????</phrase>
        </textobject>
      </mediaobject>
    </figure>

  </section>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-diskpartitioning-ja_JP.xml ---
<!-- $Id: -->
<chapter id="ch-disk-partitioning">
  <title>?????????????????????????????????????????????</title>
 
  <para>
    Linux ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? Linux ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

    <figure id="fig-partitioning-setup">
    <title>
       ????????????????????????????????????????????????
    </title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="figs/partitioning-setup.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="figs/partitioning-setup.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase> ????????????????????????????????????????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>


  <section id="sn-choosing-partition-method">
    <title>????????????????????????????????????????????????</title>

    <section id="sn-automatic-partitioning">
      <title>?????????????????????????????????????????????</title>

      <para>
        ???????????????????????? ????????????????????? ????????????????????????????????????????????????????????????????????????????????? <guilabel>?????????????????????????????????</guilabel> ?????????????????????<application>Disk Druid</application> ?????????????????????????????????????????????????????????
      </para>

      
    <figure id="fig-partitioning-automatic">
    <title>
      ??????????????????????????????????????????
    </title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="figs/partitioning-automatic.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="figs/partitioning-automatic.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>??????????????????????????????????????????</phrase>
      </textobject>
    </mediaobject>
  </figure>

      <variablelist>
	<varlistentry>
	  <term><guilabel>??????????????????????????? Linux ??????????????????????????????</guilabel>
	      </term>
	  <listitem>
	    <para>
              ????????????????????? ??????????????????<firstterm>ext2</firstterm>???
	      <firstterm>ext3</firstterm>???????????? <firstterm>Linux
		swap</firstterm> ???????????????????????????????????????
	    </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term><guilabel>?????????????????????????????????????????????????????????</guilabel></term>
	  <listitem>
	    <para>
              ???????????????????????????????????? <emphasis>??????</emphasis> ?????????????????????????????????????????????
	    </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term><guilabel>??????????????????????????????????????????????????????????????????????????????</guilabel></term>
	  <listitem>
	    <para>
              &FC; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	    </para>
	  </listitem>
	</varlistentry>
      </variablelist>

      <para>
        ??????????????????????????????????????????????????????
      </para>

      <para>
        ?????? Linux ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????1???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? Linux ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>

      <note>
	<title>???????????????</title>
	<para>
          ????????????????????????????????????????????????????????????????????????????????????Linux partion-HOWTO <ulink url="http://www.tldp.org/HOWTO/Partition/partition-2.html">http://www.tldp.org/HOWTO/Partition/partition-2.html</ulink> ??????????????????????????????
	</para>
      </note>

      <para>
        ??????????????????????????????????????????????????????????????????????????????<guilabel>??????????????????????????????????????????????????????????????????????????????</guilabel> ?????????????????????????????????????????????????????????
      </para>
      <para>
        ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ?????????????????????????????????????????????????????????????????????????????? <guibutton>???</guibutton> ???????????????????????????????????????<xref linkend="ch-bootloader"/> ???????????????????????????
      </para>

    </section>

    <section id="sn-manual-partitioning">
      <title>?????????????????????????????????????????????</title>

      <para>
        ???????????????????????????????????????????????????????????????<guilabel>Disk Druid???????????????????????????????????????????????????</guilabel> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????Linux??????????????????????????????????????????????????????????????????????????????????????????<xref linkend="sn-disk-druid"/> ???????????????????????????????????????????????? <xref linkend="sn-partitioning-general"/> ???????????????????????????
      </para>

    </section>

  </section>
    
  <section id="sn-partitioning-general">
    <title>??????????????????????????????????????????????????????</title>

    <para>
      &FC; ??????????????????????????????????????????3??????????????????????????????????????????????????????
    </para>

    <itemizedlist>
      <listitem>
	<para>
          <filename>/boot</filename> ????????????????????????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
          <filename>/</filename> ????????????????????????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  ????????????????????????????????????
	</para>
      </listitem>
    </itemizedlist>

    <para>
      ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<xref linkend="sn-choosing-partition-method"/> ????????????????????? ???????????????????????????????????? ??????????????????????????????
    </para>

    <para>
      ???????????????????????????????????????<indexterm>
	<primary>????????????????????????</primary>
      </indexterm> <firstterm>????????????????????????</firstterm> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<filename>/</filename> ( <indexterm>
	<primary>partition</primary>
	<secondary>?????????</secondary>
      </indexterm> <firstterm>?????????</firstterm> ) ?????????????????????????????????????????????  
     </para>

    <important>
     <title>????????????????????????????????? ??? <filename>/root</filename></title>
      <para>
       <filename>/</filename> (?????????
	      <indexterm><primary>????????????????????????</primary><secondary>root</secondary></indexterm>
	      ?????????) ??????????????????????????????????????????????????????????????????????????????????????????<indexterm><primary>????????????????????????</primary><secondary><filename>/root</filename></secondary></indexterm><filename>/root</filename> ( "????????????????????????" ???????????????????????????????????? ) ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	    </para>
     </important>

    <para>
    ?????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    <itemizedlist>
      <listitem>
	<para>
          <filename>/boot/</filename> ????????????????????????????????????????????????<filename>/boot</filename> ????????????????????????????????????????????????????????????<filename>/boot/grub/grub.conf</filename> ???????????????????????????<filename>/boot</filename> ????????????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
          <filename>/etc/passwd</filename> ???????????????<filename>/boot</filename> ??????????????????????????????????????????????????????????????? <filename>/</filename> ?????????????????????????????????????????????
	</para>
      </listitem>
    </itemizedlist>
    <para>
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<filename>/usr</filename> ??????<filename>/usr/local</filename> ????????????????????????????????????????????????????????????????????????<filename>/usr/local/bin/foo</filename> ???????????? <filename>/usr/local</filename> ???????????????????????????????????? <filename>/usr/local</filename> ???????????????????????????????????????????????????????????????<filename>/usr/bin/foo</filename> ???????????????<filename>/usr/</filename> ?????????????????????????????????????????? <filename>/usr</filename> ?????????????????????????????????????????????????????????????????????
    </para>
    <para>
      ????????? <filename>/</filename> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<application>Disk Druid</application> ??? <link linkend="disk-druid-edit">?????????????????????</link> ???????????????????????????????????????
    </para>


     <section id="sn-partitioning-types">
      <title>??????????????????????????????</title>

      <para>
      ???????????????????????????????????????????????????????????? <indexterm><primary>????????????????????????</primary> </indexterm> <firstterm>????????????????????????</firstterm> ??????????????????????????????????????? <indexterm><primary>????????????????????????</primary><secondary>?????????????????????????????????</secondary><seealso>????????????????????????</seealso></indexterm><firstterm>?????????????????????????????????</firstterm> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<indexterm><primary><systemitem class="filesystem">ext3</systemitem></primary>
        <see>????????????????????????</see>
      </indexterm><indexterm>
        <primary>????????????????????????</primary>
        <secondary
          sortas="filesystem"><systemitem>ext3</systemitem></secondary>
      </indexterm> <systemitem
        class="filesystem"><firstterm>ext3</firstterm></systemitem> ??????????????????????????????????????????????????????
      </para>

      </section> 

    
     <section id="sn-partitioning-lvm">
      <title>LVM???????????????</title>

      <indexterm>
	<primary>LVM</primary>
	<secondary>LVM???????????????</secondary>
      </indexterm>

      <para>
	LVM (Logical Volume Management) ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????LVM???????????????????????????<indexterm>
          <primary>LVM</primary>
          <secondary>?????????????????????</secondary></indexterm>
        <firstterm>?????????????????????</firstterm> ??????????????????????????????????????????1???????????????????????????????????????????????????????????? <indexterm>
          <primary>LVM</primary>
          <secondary>???????????????????????????</secondary>
      </indexterm> <firstterm>???????????????????????????</firstterm> ??????????????????????????????????????????????????????????????? 1????????????????????? <indexterm>
          <primary>LVM</primary>
          <primary>?????????????????????</primary></indexterm>
        <firstterm>?????????????????????</firstterm> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <systemitem class="filesystem">ext3</systemitem> ???????????????????????????????????????????????????????????????????????????????????????????????????
      </para>

      <para>
        ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????1 ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????RAID?????????????????????????????????????????????????????????????????????????????????
      </para>

      <note>
	<title>????????????????????????????????? ??? LVM</title>
         <para>
          ?????????????????????????????????????????????????????????????????????????????????????????? LVM ?????????????????????????????????????????????
         </para>
      </note>

   </section>


  </section>

<!-- some notes follow:

    Sanity checks on partitions require:
    /usr  ge 250 MB
    /tmp  ge  50
    /var  ge 384
    /home ge 100
    /boot ge  75
    /     ge 250

    for ia64:
    /boot/efi ge 50 MB

    Cannot have these as separate partitions:
    /bin /dev /sbin /etc /lib /root lost+found /proc

    Cannot make partitions for these symlinks:
    /var/mail /usr/bin/X11 /usr/lib/X11 /usr/tmp

-->

  <section id="sn-disk-druid">
    <title>Disk Druid</title>

    <para>
      <indexterm> 
	<primary>Disk Druid</primary>
      </indexterm> <application><firstterm>Disk
	  Druid</firstterm></application> ???????????????????????????????????????????????????????????????????????????????????????????????????????????? &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????Disk Druid????????????????????????, ???????????????????????????????????????????????????????????????????????? <indexterm>
	<primary>RAID</primary>
      </indexterm> <firstterm>RAID</firstterm> ??? 
      <indexterm>
	<primary>LVM</primary>
      </indexterm> <firstterm>LVM</firstterm> ?????????????????????????????????
    </para>

    <figure id="fig-disk-setup">
      <title>
	???????????????????????????????????????
      </title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="figs/disk-setup.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="figs/disk-setup.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>???????????????????????????????????????</phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      <application>Disk Druid</application> ????????????????????????????????????????????????????????????????????????????????????
    </para>
    <variablelist>
      <varlistentry id="vle-disk-druid-new">
	<term><guilabel>??????</guilabel></term>
	<listitem>
	  <para>
            ??????????????????LVM????????????????????????????????? <indexterm>
              <primary>????????????????????????</primary>
              <secondary>??????</secondary>
            </indexterm> ?????????????????????????????????????????????????????????????????????<guilabel>??????????????????????????????</guilabel> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	  <important>
	    <title>?????????????????????????????????</title>
	    <para>
	      <indexterm>
		<primary>????????????????????????</primary>
		<secondary>??????</secondary>
	      </indexterm> <filename>/bin/</filename>???
	      <filename>/dev/</filename>??? <filename>/etc/</filename>???
	      <filename>/lib/</filename>??? <filename>/proc/</filename>???
	      <filename>/root/</filename>??? ??????
	      <filename>/sbin/</filename> ????????????????????????<application>Disk Druid</application> ??????
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	      <indexterm>
		<primary>????????????????????????</primary>
		<secondary>root</secondary>
	      </indexterm> <filename>/</filename> ( root ) ????????????????????????????????????????????????
	    </para>
	    <para>
	      <filename>/boot</filename> ??????????????????????????????LVM?????????????????????????????????????????????????????????????????????<filename>/boot</filename> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	    </para>
	  </important>
	  <para>
            ????????????????????????????????????????????????????????????????????????3?????????????????????????????????????????????
	  </para>
	  <variablelist>
	    <varlistentry>
	      <term><guilabel>????????????</guilabel></term>
	      <listitem>
		<para>
                  ??????????????????????????????????????????????????????????????????????????????
		</para>
	      </listitem>
	    </varlistentry>
	    <varlistentry>
	      <term><guilabel>????????????????????????</guilabel></term>
	      <listitem>
		<para>
                  ?????????????????????????????????????????????????????????????????????????????????
		</para>
	      </listitem>
	    </varlistentry>
	    <varlistentry>
	      <term><guilabel>???????????????????????????</guilabel></term>
	      <listitem>
		<para>
                  ???????????????????????????????????????????????????????????????????????????????????????????????????
		</para>
	      </listitem>
	    </varlistentry>
	  </variablelist>
	  <note>
	    <title>????????????????????????????????????</title>
	    <para>
              ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	    </para>
	  </note>
	  <para>
	    ???????????????????????????????????????????????????????????????<guibutton>OK</guibutton> ?????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry id="disk-druid-edit">
	<term><guilabel>??????</guilabel></term>
	<listitem>
	  <para>
            ?????????????????? <indexterm>
              <primary>????????????????????????</primary>
              <secondary>??????</secondary>
            </indexterm> ??? LVM ??????????????????????????????, ???????????????????????????????????????????????????????????? LVM ??????????????????????????????????????????????????????????????????????????????????????????LVM ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	  <warning>
	    <title>LVM ???????????????????????????????????????</title>
	    <para>
              LVM ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	    </para>
	  </warning>
	  <para>
            ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	  <itemizedlist>
	    <listitem>
	      <para>
                ???????????????????????????????????????????????????????????????????????????
	      </para>
	    </listitem>
	    <listitem>
	      <para>
                &FC; ???????????????????????????????????????????????????????????????????????? Linux ????????????????????????????????????????????????
	      </para>
	    </listitem>
	    <listitem>
	      <para>
                Windows ????????????????????????????????????????????????????????????Linux ?????????????????????????????????????????????????????????????????????????????????
	      </para>
	    </listitem>
	  </itemizedlist>
	  <note>
	    <title>Windows ???????????????????????????</title>
	    <para>
              &FC; ?????????????????????????????????
	      <indexterm>
		<primary><systemitem
		    class="filesystem">NTFS</systemitem></primary>
		<see>????????????????????????</see>
	      </indexterm>
	      <indexterm>
		<primary>????????????????????????</primary>
		<secondary><systemitem
		    class="filesystem">NTFS</systemitem></secondary>
	      </indexterm> <systemitem
		class="filesystem">NTFS</systemitem> ?????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????????????????????????
	      <indexterm>
		<primary><systemitem
		    class="filesystem">vfat</systemitem></primary>
		<see>????????????????????????</see>
	      </indexterm>
	      <indexterm>
		<primary>????????????????????????</primary>
		<secondary><systemitem
		    class="filesystem">vfat</systemitem></secondary>
	      </indexterm> <systemitem
		class="filesystem"><firstterm>vfat</firstterm></systemitem> 
	      ( <systemitem class="filesystem">FAT16</systemitem> ????????? 
	      <systemitem class="filesystem">FAT32</systemitem> )
	      ???????????????????????????????????????????????????????????????????????????????????????????????????
	    </para>
	  </note>
	  <para>
            ?????????????????????????????????????????? <emphasis>????????????</emphasis> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	  <para>
            ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <indexterm>
              <primary>????????????????????????</primary>
              <secondary><filename>/home</filename></secondary>
            </indexterm> <filename>/home</filename> ????????????????????????????????????????????????<filename>/boot</filename> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><guilabel>??????</guilabel></term>
	<listitem>
	  <para>
            ?????????????????????????????????<indexterm>
              <primary>????????????????????????</primary>
              <secondary>??????</secondary>
            </indexterm>???????????? LVM ??????????????????????????????????????????????????????????????????????????????????????????LVM ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	  <para>
            ???????????????????????????????????????????????????????????????????????????????????? <guilabel>????????????</guilabel> ?????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><guilabel>????????????</guilabel></term>
	<listitem>
	  <para>
	    <application>Disk Druid</application> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><guilabel>RAID</guilabel></term>
	<listitem>
	  <para>
	    &FED; ?????????????????? ??????????????????RAID <indexterm>
              <primary>RAID</primary>
            </indexterm>??????????????????????????????????????????????????????????????????????????????
	  </para>
	  <variablelist>
	    <varlistentry>
	      <term><guilabel>?????????????????? RAID ?????????????????????????????????</guilabel></term>
	      <listitem>
		<para>
                  ??????????????????RAID??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????RAID????????????????????????????????????????????????????????????????????????????????????????????????
		</para>
	      </listitem>
	    </varlistentry>
	    <varlistentry>
	      <term><guilabel>RAID ?????????????????????</guilabel></term>
	      <listitem>
		<para>
                  ?????????????????????????????????????????????RAID?????????????????????????????????RAID??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????RAID????????????????????????????????????????????????????????????????????????????????????
		</para>
	      </listitem>
	    </varlistentry>
	    <varlistentry>
	      <term><guilabel>RAID?????????????????????????????????????????????</guilabel></term>
	      <listitem>
		<para>
                  ????????????????????????RAID1??? <firstterm>??????????????????</firstterm> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
		</para>
	      </listitem>
	    </varlistentry>
	  </variablelist>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><guilabel>LVM</guilabel></term>
	<listitem>
	  <para>
            &FED; ??????????????? LVM <indexterm>
              <primary>LVM</primary>
            </indexterm>????????????????????????????????????????????????????????????????????????????????? <application>??????</application> ???????????????????????????????????????????????????????????????????????????????????????????????????????????? RAID ??????????????? LVM ?????????????????????????????????????????????????????????
	  </para>
	  <para>
            ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>??????</guilabel>???<guilabel>??????</guilabel> ????????? <guilabel>??????</guilabel> ????????????????????????????????????????????????
	  </para>
	  <para>
            ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????5GB??? LVM ????????????????????????????????????????????????????????????????????????????????????8GB???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????8GB????????????????????????????????????????????????????????????????????????5GB?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????4GB?????????????????????5GB???!
 ???????????????????????????????????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
    </variablelist>
    <para>
      ?????????????????????????????????????????????????????????????????????????????????<guilabel>???</guilabel> ???????????????????????????????????????
    </para>

  </section>

</chapter>
  
    

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-firewallconfig-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-security-config">
  <title>????????????????????????</title>

  <para>
    &FC; ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <figure id="fig-firewall">
    <title>??????????????????????????????</title>
    <mediaobject>
      <imageobject>
	<imagedata align="center" fileref="./figs/firewall.eps" format="EPS"/>
      </imageobject>
      <imageobject>
	<imagedata align="center" fileref="./figs/firewall.png" format="PNG"/>
      </imageobject>
      <textobject>
	<phrase>
	  ??????????????????????????????
	</phrase>
      </textobject>
    </mediaobject>
  </figure>

  <para>
    ???????????????????????????????????????????????????????????????????????? <guibutton>???</guibutton> ????????????????????????????????????????????????
  </para>

  <section id="sn-firewall-settings">
    <title>????????????????????????</title>

    <para>
      &FC; ????????????????????? <indexterm><primary>????????????????????????</primary></indexterm><firstterm>????????????????????????</firstterm> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FED; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>?????????????????????????????? </guilabel> ??????????????????????????????
    </para>

    <tip>
      <title>???????????????????????????????????????</title>
      <para>
        ??????????????????????????????????????????????????????????????????????????? 
	<menuchoice>
	  <guimenu>Desktop</guimenu>
	  <guisubmenu>System Settings</guisubmenu><guimenuitem>Security
	    Level and Firewall</guimenuitem></menuchoice> ?????????????????????
      </para>   
    </tip>

  </section>


  <section id="sn-selinux">
    <title>&SEL;</title>

    <para>
      <indexterm>
	<primary>&SEL;</primary>
      </indexterm> <firstterm>&SEL;</firstterm> (Security Enhanced Linux) ???????????????????????????&FC; ??????????????????&SEL; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&SEL; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &SEL; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ??????????????? &SEL; ??????????????????????????????&FED; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&SEL; ????????????????????????????????????????????????????????????????????????????????????????????????????????????&SEL; ???????????????????????????????????????????????????????????????????????????
    </para>

    <variablelist>
      <varlistentry>
	<term><guilabel>???????????????</guilabel></term>
	<listitem>
	  <para>
            ?????????????????????????????? &FED; ???????????????????????????????????????????????????????????????????????????????????? &FED; ????????????????????????????????????????????????????????????????????? 
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><guilabel>??????</guilabel></term>
	<listitem>
	  <para>
            &SEL; ???????????????????????????????????????????????????????????????????????????????????????????????? &SEL; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &SEL; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &SEL; ??????????????? <guilabel>???????????????</guilabel> ???????????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><guilabel>??????</guilabel></term>
	<listitem>
	  <para>
            &SEL; ???????????????????????????????????????&FED; ???????????????????????????????????????????????????????????????????????? &SEL; ??????????????????????????????????????????????????????
	    <menuchoice>
	      <guimenu>Desktop</guimenu>
	      <guisubmenu>System Settings</guisubmenu>
	      <guimenuitem>Security Level and Firewall</guimenuitem>
	    </menuchoice> ?????????????????????
	  </para>
	</listitem>
      </varlistentry>
    </variablelist>

    <tip>
      <title> &SEL; ?????????????????????????????? </title>
      <para>
        &SEL; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &SEL; ????????????????????????????????????????????????????????????
	<menuchoice>
	  <guimenu>Desktop</guimenu>
	  <guisubmenu>System Settings</guisubmenu>
	  <guimenuitem>Security Level and Firewall</guimenuitem>
	</menuchoice> ?????????????????????
      </para>
    </tip>

  </section>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-firstboot-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-firstboot">
  <title>??????????????????</title>

  <para>
    ????????? &FC; ????????????????????????????????????????????????<application>????????????????????????????????????</application> ?????????????????????????????????????????????????????????????????????????????????????????????????????? <application>????????????????????????????????????</application> ??????????????????
  </para>

  <figure id="fig-fboot-welcome">
    <title>??????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/fboot-welcome.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/fboot-welcome.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	  ??????????????????
        </phrase>
      </textobject>
    </mediaobject>
  </figure>

  <para>
    <guibutton>??????</guibutton> ??????????????? <application>????????????????????????????????????</application> ?????????????????????
  </para>

  <note>
    <title>GUI???????????????</title>
    <para>
      <application>????????????????????????????????????</application> ???GUI????????????????????????GUI?????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
  </note>


  <section id="sn-firstboot-licence">
    <title>??????????????????????????????</title>

    <para>
      ??????????????????&FC; ?????????????????????????????????????????????????????????&FC; ?????????????????????????????????????????????????????????????????????<indexterm><primary>OSI (Open Source Initiative)</primary></indexterm>Open Source Initiative (OSI) ????????????????????????????????????????????????????????????????????????????????????????????????OSI?????????????????????????????????<ulink url="http://www.opensource.org/">http://www.opensource.org/</ulink> ??????????????????????????????
    </para>

    <figure id="fig-fboot-licence">
      <title>?????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-licence.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-licence.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ?????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ??????????????????<guilabel>Yes, I agree to the License Agreement</guilabel> ???????????????<guibutton>??????</guibutton>?????????????????????
    </para>

  </section>


  <section id="sn-firstboot-datetime">
    <title>????????????????????????</title>

    <para>
      ?????????????????????????????????????????????????????????????????????NTP?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<indexterm><primary>NTP (Network Time Protocol)</primary></indexterm> <firstterm>NTP</firstterm> ???????????????????????????NTP ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????NTP??????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-fboot-time">
      <title>??????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-time.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-time.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ??????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      NTP?????????????????????????????????????????????????????????????????????<guilabel>??????????????????????????????????????????</guilabel> ???????????????????????????
    </para>

    <tip>
      <title>???????????????</title>
      <para>
        ??????????????????????????????????????????????????????????????????????????????
	<menuchoice>
	  <guimenu>Desktop</guimenu>
	  <guisubmenu>System Settings</guisubmenu>
	  <guimenuitem>Date &amp; Time</guimenuitem>
	</menuchoice> ?????????????????????
      </para>
    </tip>


    <para>
      ???????????????NTP????????????????????????????????????????????????<guilabel>Enable Network Time Protocol</guilabel> ???????????????????????????????????????????????????????????? <guilabel>Date and Time</guilabel> ??????????????????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-fboot-time-ntp">
      <title>??????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-time-ntp.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-time-ntp.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ??????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ?????????????????? &FC; ???????????????????????????????????????????????????????????????????????? <firstterm>?????????</firstterm> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ?????????????????????????????????????????????<guilabel>?????????</guilabel> ???????????????????????????????????????????????????????????????????????????DNS?????????????????? <guilabel>Add</guilabel> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>Delete</guilabel> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &RH; ?????????????????????????????????????????????
    </para>

    <para>
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>Show advanced options</guilabel> ??????????????? <guilabel>Use Local Time Source</guilabel> ????????????????????????????????????????????????????????????????????????????????????????????????NTP????????????????????????????????????????????????????????????
    </para>

    <para>
      <guilabel>Enable NTP Broadcast</guilabel> advanced ???????????????????????????????????????&FC; ??????????????????????????????????????????????????????????????????????????????????????????
    </para>

  </section>


  <section id="sn-firstboot-display">
    <title>???????????????????????????</title>

    <para>
      <application>????????????????????????????????????</application> ???????????????????????????????????????????????????????????????????????????????????????<application>????????????????????????????????????</application> ????????????<guilabel>?????????</guilabel> ???<guilabel>????????????</guilabel> ???????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-fboot-display">
      <title>?????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-display.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-display.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ?????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ????????????????????????????????????????????????<guilabel>Configure</guilabel> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <keycap>+</keycap> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guibutton>OK</guibutton> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>Generic CRT Display</guilabel> ????????????????????? <guilabel>Generic LCD Display</guilabel> ???????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-fboot-display-monitor">
      <title>?????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-display-monitor.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-display-monitor.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ?????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ???????????????????????????????????????????????????<guilabel>?????????</guilabel> ????????? <guilabel>????????????</guilabel> ?????????????????????????????????????????????????????????????????????????????????<application>????????????????????????????????????</application> ???????????????????????????????????????????????????????????????????????????
    </para>

    <tip>
      <title>??????????????????????????????</title>
      <para>
        ????????????????????????????????????????????????????????????????????????????????????????????????????????????<menuchoice>
	  <guimenu>Desktop</guimenu>
	  <guisubmenu>System Settings</guisubmenu>
	  <guimenuitem>Display</guimenuitem>
	</menuchoice> ?????????????????????
      </para>
    </tip>

  </section>


  <section id="sn-firstboot-systemuser">
    <title>??????????????????????????????</title>

    <para>
      ???????????????????????????????????????????????????????????????&FC; ????????????????????????????????????????????????<systemitem class="username">root</systemitem> ???????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-fboot-user">
      <title>????????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-user.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-user.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ????????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>Confirm Password</guilabel> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<xref linkend="ch-rootpassword" /> ?????????????????????????????????????????????????????????
    </para>

    <tip>
      <title>????????????????????????????????????????????????</title>
      <para>
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<menuchoice>
	  <guimenu>Desktop</guimenu>
	  <guisubmenu>System Settings</guisubmenu>
	  <guimenuitem>Users &amp; Groups</guimenuitem>
	</menuchoice> ?????????????????????
      </para>
    </tip>

    <para>
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FC; ????????????????????????<guibutton>Use Network Login....</guibutton> ?????????????????????
      <!-- Network authentication is explained
      in a separate tutorial. [Remove this comment when the
      aforementioned tutorial exists. - PWF.] -->
    </para>

    <para>
      ?????????????????????????????????????????????<guibutton>??????</guibutton> ???????????????????????????????????????
    </para>

  </section>


  <section id="sn-firstboot-soundcard">
    <title>??????????????????????????????</title>

    <para>
      <application>????????????????????????????????????</application> ?????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-fboot-sound">
      <title>????????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-sound.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-sound.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ????????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      <guibutton>??????????????????????????????</guibutton> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FC; ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FC; ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <tip>
      <title>????????????????????????????????????</title>
      <para>
        &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<menuchoice>
	  <guimenu>Desktop</guimenu>
	  <guisubmenu>System Settings</guisubmenu>
	  <guimenuitem>Soundcard Detection</guimenuitem>
	</menuchoice> ?????????????????????
      </para>
    </tip>

  </section>


  <section id="sn-firstboot-additional-cds">
    <title>?????????CD</title>

    <para>
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <tip>
      <title>?????????????????????????????????</title>
      <para>
        &FC; ????????????????????????????????????????????????????????????????????????????????????????????????<application>?????????????????????????????????</application> ????????????????????????????????????????????????????????????????????????<menuchoice>
	  <guimenu>Desktop</guimenu>
	  <guisubmenu>System Settings</guisubmenu>
	  <guimenuitem>Add/Remove Applications</guimenuitem>
	</menuchoice> ?????????????????????
      </para>
    </tip>

    <figure id="fig-fboot-cds">
      <title>?????????CD ??????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-cds.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-cds.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ?????????CD ??????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      <guilabel>??????</guilabel> ???????????????????????????????????????????????????
    </para>

    <figure id="fig-fboot-finish">
      <title>??????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-finish.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/fboot-finish.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ??????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      <guilabel>??????</guilabel> ????????????????????????????????????????????????????????????????????? &FC; ????????????????????????????????????????????????????????????
    </para>

  </section>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-installingpackages-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-installing-packages">
  <title>????????????????????????????????????</title>

  <para>
    &FC; ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????DVD????????????????????????????????????????????????????????????????????????????????????????????????CD????????????????????????????????????????????????&FC; ???????????????????????????????????????????????????????????????????????????????????????????????????<guibutton>OK</guibutton> ????????????????????????????????????????????????????????????
  </para>

  <figure id="fig-installing-inprogress">
    <title>?????????????????????????????????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/installing-inprogress.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/installing-inprogress.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
          ?????????????????????????????????????????????
        </phrase>
      </textobject>
    </mediaobject>
  </figure>
    
  <para>
    ???????????????????????????????????????<guibutton>?????????</guibutton> ?????????????????????????????????????????????????????????????????????&FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-installtypes-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-installtypes">
  <title>???????????????????????????</title>

  <para>
    <indexterm><primary>???????????????????????????</primary></indexterm> <firstterm>???????????????????????????</firstterm> ???????????????????????? &FED; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <section id="ch-choosing-installtype">
    <title>??????????????????????????????????????????</title>

    <figure id="fig-install-types">
      <title>???????????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/install-types.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/install-types.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ???????????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <variablelist>
      <varlistentry>
	<term><guilabel>?????????????????????????????????</guilabel></term>
	<listitem>
	  <para>
            ???????????????????????????????????????????????????????????????????????????????????????, ?????????????????????????????????????????????, ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><guilabel>???????????????????????????</guilabel></term>
	<listitem>
	  <para>
            ???????????????????????????????????????<guilabel>?????????????????????????????????</guilabel> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><guilabel>????????????</guilabel></term>
	<listitem>
	  <para>
            ???????????????????????????????????????Apache?????????????????????Samba????????????????????????????????????????????????????????????, ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term><guilabel>????????????</guilabel></term>
	<listitem>
	  <para>
            ???????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>?????????????????????????????????</guilabel> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>????????????</guilabel> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
    </variablelist>

    <para>
      ?????????????????? <guibutton>???</guibutton> ???????????????????????????
    </para>

  </section>

  <section id="installtype-notes">
    <title>???????????????????????????</title>

    <para>
      &FC; ?????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <itemizedlist>
      <listitem>
	<para>
	  <indexterm>
	    <primary>SMTP (Simple Mail Transfer Protocol)</primary>
	  </indexterm> <firstterm>SMTP</firstterm> (Simple Mail Transfer
	  Protocol) ???????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  <indexterm>
	    <primary>NFS (Network File System)</primary>
	    <secondary>???????????????????????????????????????</secondary>
	  </indexterm> NFS(Network File System) ???????????????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  <indexterm>
	    <primary>CUPS (Common UNIX Printing System)</primary>
	  </indexterm> <firstterm>CUPS</firstterm>
	  (Common UNIX Printing System) ??????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  <indexterm>
	    <primary>SSH (Secure SHell)</primary>
	  </indexterm> <firstterm>SSH</firstterm>
	  (Secure SHell) ????????????????????????????????????
	</para>
      </listitem>
    </itemizedlist>

    <para>
      &FED; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FED; ????????????????????????NFS????????????????????????????????????NFS??????????????? <emphasis>??????</emphasis> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????, NFS, ?????????????????????????????????????????????????????? &FED; ???????????????????????????????????????????????????SSH???????????????????????????????????????????????????????????????
    </para>

    <tip>
      <title>????????????????????????</title>
      <para>
        ??????????????????????????????????????????????????????????????????<guilabel>????????????</guilabel> ??????????????????????????????????????????<guilabel>????????????????????????????????????</guilabel> ????????? <guilabel>??????</guilabel> ????????????????????????????????????????????????<guilabel>??????</guilabel> ????????????????????????????????????????????????????????????????????????, ??????, NFS, ?????????SSH???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
    </tip>

  </section>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-intro-ja_JP.xml ---
<!-- $Id: -->
<preface id="ch-intro">
  <title>????????????</title>

  <!--  removed until we begin working on the FC5 version
  &DRAFTNOTICE;  -->

  <para>
    &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>
  
  <caution>
    <title>&FC; ????????????????????????</title>
    <para>
      &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FC; ?????????????????????????????????????????????????????????????????? 
    </para>
  </caution>

  <para>
    ??????????????????????????????????????? &FC; ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FC; ??????????????????????????????????????????????????????Linux???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <para>
    ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<!-- Automating the installation process and
    configuring network installation servers will be described in
    separate tutorials.  [These tutorials will be added later. Until
    they exist, do not reference them. - PWF.] -->
  </para>

  <section id="sn-background">
    <title>??????</title>

    <para>
      &FC; ????????????????????????????????? &FP; ??????&FORMAL-RHI; ??????<indexterm>
	<primary>???????????????????????????</primary>
	<see>FOSS</see>
      </indexterm><indexterm>
	<primary>?????????????????????</primary>
	<see>FOSS</see>
      </indexterm>
      <indexterm>
	<primary>FOSS (free and open source software)</primary>
      </indexterm> <firstterm>free and open source software</firstterm>
      (FOSS) ????????????????????????????????????????????????&FP; ??? &FEX;???????????? &FC; ??????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      &FP; ?????????????????????????????????????????????<ulink
	url="http://fedora.redhat.com/">&FP-URL;</ulink> ?????????????????????????????????
      ????????????????????????????????????????????????????????????????????????????????????<ulink
	url="http://www.opensource.org/">http://www.opensource.org/</ulink> 
      ??? <ulink	url="http://www.gnu.org/philosophy/free-sw.html">http://www.gnu.org/philosophy/free-sw.html</ulink> ??????????????????????????????
    </para>

  </section>


  <section id="sn-before-begin">
    <title>??????????????????</title>
    
    <para>
      &FC; ????????????????????????????????????????????????????????????????????????CD, ??????????????????????????????DVD?????????????????????????????????????????????<firstterm>?????????????????????</firstterm>????????????????????????????????????????????????????????????????????????????????? &FC; ??? <firstterm>i386</firstterm>, <firstterm>ppc</firstterm>, ????????? <firstterm>x86_64</firstterm> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <variablelist>
      <varlistentry>
	<term>i386</term>
	<listitem>
	  <para>
            Intel??????x86????????????????????????????????????Intel Pentium, Pentium-MMX, Pentium Pro, Pentium-II, Pentium-III, Celeron, Pentium 4, Xeon ??????????????????????????????VIA C3/C3-m, Eden/Eden-N????????????AMD Athlon, AthlonXP, Duron, AthlonMP, Sempron??????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>ppc</term>
	<listitem>
	  <para>
            PowerPC??????????????????????????????Apple Power Macintosh, G3, G4, G5, IBM pSeries ??????????????????????????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term>x86_64</term>
	<listitem>
	  <para>
            Athlon64, Turion64, Opteron ????????????64bit??????????????????????????? EM64T ???????????? Intel 64bit ?????????????????????????????????
	  </para>
	</listitem>
      </varlistentry>
    </variablelist>

    <para>
      ????????????????????????????????????????????????????????????????????????
    </para>
 
    <itemizedlist>
      <listitem>
	<para>
          ?????????????????????????????????????????????
	</para>
      </listitem>
      <listitem>
	<para>
	  ?????? &IG; ????????????
	</para>
      </listitem>
    </itemizedlist>

    <para>
      ????????????????????????????????????????????????????????????????????????????????? &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
    
    <para>
      ?????????????????????????????????????????????????????? HTML ??? ???????????????????????? ????????????????????????????????????????????????????????? &IG; ?????????????????????????????????????????????????????????<ulink url="http://fedora.redhat.com/docs/">&FDPDOCS-URL;</ulink>???????????????????????????????????????
    </para>

    <section id="sn-installing-network-configurations">
      <title>????????????????????????</title>

      <para>
        ?????????????????? &FC; ??? <primary>DHCP (Dynamic Host Control Protocol)</primary> <firstterm>DHCP</firstterm> (Dynamic Host Configuration Protocol) ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????DHCP?????????????????????????????????????????????????????????DHCP?????????????????????????????????????????????????????????????????????????????????????????????, ???????????????????????????????????????????????????
      </para>

      <para>
        ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<xref linkend="sn-installing-networkinstallation" /> ??? <xref linkend="sn-installing-managed-network" /> ??????????????????????????????
      </para>

      <note>
	<title>??????????????????</title>
	<para>
          &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
      </note>

    </section>
    
    <section id="sn-installing-asaserver">
      <title>?????????????????? &FC; ???????????????????????????</title>
      
      <para>
        &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>?????????</guilabel> ?????????????????????????????????????????????????????????????????????????????????<xref linkend="ch-installtypes"/> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>

    </section>


    <section id="sn-installing-networkinstallation">
      <title>??????????????????????????????????????? &FC; ???????????????????????????</title>

      <para>
        ??????????????????????????????????????????????????????????????? &FC; ???????????????????????????????????????????????????????????????????????????????????????
      </para>
      <itemizedlist>
	<listitem>
	  <para>
	    ??????????????????
	  </para>
	</listitem>
	<listitem>
	  <para>
            ???????????????????????????????????????????????????????????????FTP, HTTP, ?????????NFS)
	  </para>
	</listitem>
	<listitem>
	  <para>
            ??????????????????????????????????????????
	  </para>
	</listitem>
      </itemizedlist>

      <para>
        <firstterm>PXE</firstterm> (Pre-boot eXecution Environment) ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????DVD, ??????????????????CD???????????????????????????CD, ????????????????????????USB????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
      
      <para>
        PXE ( <firstterm>netboot</firstterm> ?????????????????????) ??????PC??????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FC; ??????????????????????????????PXE?????????????????????????????????????????????????????????????????????????????????????????????
      </para>

      <para>
          ????????????????????????????????????????????????????????????????????????????????????????????? <xref
	  linkend="ch-beginninginstallation"/> ???????????????????????????
      </para>
      
    </section>
    

    <section id="sn-installing-managed-network">
      <title> ??????????????????????????????????????? &FC; ???????????????????????????</title>

      <para>
        ?????????????????????????????????????????????????????????????????????????????????????????????<firstterm>??????????????????????????????</firstterm>?????????????????????????????????&FC; ??????????????????Kerberos, NIS, Hesiod, ???????????? <trademark class="registered">Microsoft</trademark> <trademark class="registered">Windows</trademark> ?????????????????????????????????????????????????????????????????????????????????&FC; ???LDAP?????????????????????????????????????????????????????????
      </para>

	<!--
	
	<para>
	  The process of configuring your &FC; system to use network
	  authentication services is explained in a separate tutorial.
	</para>

	[When this tutorial exists, remove these comments.]

	-->

      <caution>
	<title>????????????????????????????????????????????????</title>
	<para>
          ????????????????????????????????????????????????????????????????????????????????????????????????????????? &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
	</para>
      </caution>

    </section>

  </section>
  
</preface>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "preface")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-ja_JP.xml ---
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;

<!ENTITY VERSION "1.0"> <!-- version for this document -->

<!ENTITY BOOKID "fedora-install-guide-en-&VERSION; (2005-06-10-T16:20-0700)"> <!-- change date here and VERSION entity everytime a change is made-->

<!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">

<!-- Bugzilla bug number for the draft notice -->
<!ENTITY BUG-NUM "129911">
<!ENTITY FCLOCALVER "5 test1">
<!ENTITY DOCLOCALVER "1.0">
<!ENTITY DRAFTNOTICE SYSTEM "../docs-common/common/draftnotice-en.xml">

<!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-ja_JP.xml">
<!ENTITY BEGINNINGINSTALLATION SYSTEM "fedora-install-guide-beginninginstallation-ja_JP.xml">
<!ENTITY OTHERINSTALLMETHODS SYSTEM "fedora-install-guide-other-instmethods-ja_JP.xml">
<!ENTITY LOCALE SYSTEM "fedora-install-guide-locale-ja_JP.xml">
<!ENTITY UPGRADING SYSTEM "fedora-install-guide-upgrading-ja_JP.xml">
<!ENTITY INSTALLTYPES SYSTEM "fedora-install-guide-installtypes-ja_JP.xml">
<!ENTITY DISKPARTITIONING SYSTEM "fedora-install-guide-diskpartitioning-ja_JP.xml">
<!ENTITY BOOTLOADER SYSTEM "fedora-install-guide-bootloader-ja_JP.xml">
<!ENTITY NETWORKCONFIG SYSTEM "fedora-install-guide-networkconfig-ja_JP.xml">
<!ENTITY FIREWALLCONFIG SYSTEM "fedora-install-guide-firewallconfig-ja_JP.xml">
<!ENTITY TIMEZONE SYSTEM "fedora-install-guide-timezone-ja_JP.xml">
<!ENTITY ROOTPASSWORD SYSTEM "fedora-install-guide-rootpassword-ja_JP.xml">
<!ENTITY PACKAGESELECTION SYSTEM "fedora-install-guide-packageselection-ja_JP.xml">
<!ENTITY ABOUTTOINSTALL SYSTEM "fedora-install-guide-abouttoinstall-ja_JP.xml">
<!ENTITY INSTALLINGPACKAGES SYSTEM "fedora-install-guide-installingpackages-ja_JP.xml">
<!ENTITY FIRSTBOOT SYSTEM "fedora-install-guide-firstboot-ja_JP.xml">
<!ENTITY NEXTSTEPS SYSTEM "fedora-install-guide-nextsteps-ja_JP.xml">
<!ENTITY ACKNOWLEDGEMENTS SYSTEM "fedora-install-guide-acknowledgements-ja_JP.xml">

]>

<book id="book" lang="en">
  <bookinfo>
    <title>&FC; &FCLOCALVER; &IG;</title>
    <!-- Remove DOCLOCALVER for release -->
    <copyright>
      <year>2005</year>
      <holder>&FORMAL-RHI;</holder>
      <holder>Stuart Ellis</holder>
      <holder>Paul W. Frields</holder> 
    </copyright>
    <authorgroup>
      <author>
	<surname>Ellis</surname>
	<firstname>Stuart</firstname>
      </author>
      <author>
	<surname>Frields</surname>
	<firstname>Paul</firstname>
	<othername role="mi">W.</othername>
      </author>
    </authorgroup>
    &LEGALNOTICE;
    <revhistory>
      <revision>
	<revnumber>0.6.2</revnumber>
	<date>2005-04-30</date>
	<authorinitials>StuartEllis</authorinitials>
	<authorinitials>PaulWFrields</authorinitials>
	<revdescription>
	  <para>
	    ????????????CVS????????????????????????????????????????????????????????????????????????????????????????????????????????????
	  </para>
	</revdescription>
      </revision>
      <revision>
	<revnumber>0.6.3</revnumber>
	<date>2005-05-10</date>
	<authorinitials>PaulWFrields</authorinitials>
	<authorinitials>StuartEllis</authorinitials>
	<revdescription>
	  <para>
	    ????????????????????????????????????"nextstep"??????????????????
	  </para>
	</revdescription>
      </revision>
      <revision>
	<revnumber>0.7</revnumber>
	<date>2005-05-15</date>
	<authorinitials>StuartEllis</authorinitials>
	<authorinitials>PaulWFrields</authorinitials>
	<revdescription>
	  <para>
	    ????????????????????????????????????????????????????????????
	  </para>
	</revdescription>
      </revision>
      <revision>
	<revnumber>1.0rc1</revnumber>
	<date>2005-06-08</date>
	<authorinitials>KarstenWade</authorinitials>
	<revdescription>
	  <para>
	    ????????????????????????????????????????????????????????????????????????
	  </para>
	</revdescription>
      </revision>
      <revision>
	<revnumber>1.0</revnumber>
	<date>2005-06-10</date>
	<authorinitials>KarstenWade</authorinitials>
	<revdescription>
	  <para>
	    ???????????????????????????
	  </para>
	</revdescription>
      </revision>

    </revhistory>
  </bookinfo>

  &INTRODUCTION;

  &BEGINNINGINSTALLATION;

  &OTHERINSTALLMETHODS;

  &LOCALE;

  &UPGRADING;

  &INSTALLTYPES;

  &DISKPARTITIONING;

  &BOOTLOADER;

  &NETWORKCONFIG;

  &FIREWALLCONFIG;

  &TIMEZONE;

  &ROOTPASSWORD;

  &PACKAGESELECTION;

  &ABOUTTOINSTALL;

  &INSTALLINGPACKAGES;

  &FIRSTBOOT;

  &NEXTSTEPS;

  &ACKNOWLEDGEMENTS;

  <index id="generated-index">
  </index>

</book>

<!--
Local variables:
mode: xml
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-locale-ja_JP.xml ---
<!-- $Id: -->
<chapter id="ch-installer-locale">
  <title>?????????????????????</title>

  <para>
    ????????????????????????????????????????????????????????????????????????????????????????????????????????????GUI???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????GUI????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <important>
    <para>
      ??????HTTP,FTP????????????????????????????????????????????????????????????????????????????????????????????????????????????128MB?????????????????????????????????????????????
    </para>
  </important>

  <section id="sn-installer-language">
    <title>???????????????</title>

    <para>
      ???????????????????????????????????????&FED; ????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-lang-selection">
      <title>??????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/lang-selection.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/lang-selection.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ??????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ???????????????????????????????????????????????????<guibutton>Next</guibutton> ?????????????????????
    </para>

    <note>
     <title>??????????????????????????????????????????????????????</title>
      <para>
        ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ?????????????????? <xref linkend="sn-lang-packages"></xref> ??????????????????????????????
      </para>
    </note>

  </section>


  <section id="sn-installer-keyboard">
    <title>????????????????????????</title>

    <para>
      ???????????????????????????????????????&FED; ??????????????????????????????????????????????????????????????????????????????????????????
    </para>
      
    <figure id="fig-keyb-conf">
      <title>??????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/keyb-conf.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/keyb-conf.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ??????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ?????????????????????????????????????????????????????????????????????<guibutton>???</guibutton> ?????????????????????
    </para>

  </section>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-networkconfig-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-networkconfig">
  <title>???????????????????????????</title>

  <para>
    &FED; ?????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <para>
    &FED; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <indexterm>
      <primary>DHCP (Dynamic Host Configuration Protocol)</primary>
    </indexterm> <firstterm>DHCP</firstterm> (Dynamic Host Configuration Protocol) ????????????????????????????????????????????????????????????&FC; ????????????????????????????????????????????????????????????????????????????????????????????????DHCP ????????????????????????????????????
  </para>

  <para>
    DHCP ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <figure id="fig-net-config-dhcp">
    <title>??????????????????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/net-config-dhcp.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/net-config-dhcp.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	  ??????????????????????????????
        </phrase>
      </textobject>
    </mediaobject>
  </figure>


  <section id="sn-network-devices">
    <title>??????????????????????????????</title>

    <para>
      &FED; ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <firstterm>IP????????????</firstterm> <indexterm><primary>IP ????????????</primary></indexterm> ???????????????????????????????????????????????????????????????????????????????????????????????? <indexterm><primary>DHCP (Dynamic Host Configuration Protocol)</primary></indexterm> ???????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ?????????IP???????????????????????????????????????<guilabel>??????????????????????????????</guilabel> ???????????????????????????????????????????????????????????? <guibutton>??????</guibutton> ?????????????????????????????? &FED; ???????????????????????????????????????????????????????????????<guilabel>DHCP?????????????????????</guilabel> ????????????????????????????????????????????? <emphasis>?????????</emphasis> ????????????<guilabel>IP????????????</guilabel> ???????????? <guilabel>??????????????????</guilabel> ?????????????????????????????? <guilabel>OK</guilabel> ?????????????????????
    </para>

    <para>
      ????????????????????????????????????????????????DHCP ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????DHCP ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
      
    <para>
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>????????????????????????????????????</guilabel> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <note>
      <title>??????????????????</title>
      <para>
        <guilabel>??????????????????????????????</guilabel>?????????<indexterm>
          <primary>?????????</primary>
        </indexterm> ????????? ????????????????????????????????????????????????????????????????????????????????????????????? <application>??????????????????????????????????????????</application> ????????? <application>????????????????????????</application> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????(ISP) ????????????????????????????????????
      </para>
    </note>

  </section>


  <section id="sn-computer-hostname">
    <title>????????????????????????????????????</title>

    <para>
      ????????????????????????????????????DHCP ????????????????????????????????????????????????????????? <indexterm>
        <primary>????????????</primary>
      </indexterm> <firstterm>????????????</firstterm> ???????????????????????????????????????????????????????????????????????????<guilabel>????????????</guilabel> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<replaceable>machine1.example.com</replaceable> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? "??????????????????" ?????? <replaceable>machine1</replaceable> ????????????<indexterm>
        <primary>???????????????</primary>
      </indexterm> ??????????????? ??? <replaceable>example.com</replaceable> ?????????
    </para>

    <tip>
      <title>?????????????????????</title>
      <para>
        ????????????????????? ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????, ????????????????????????????????????????????????????????????
      </para>
    </tip>

  </section>


  <section id="sn-network-misc-settings">
    <title>??????????????????</title>

    <para>
      ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????IP??????????????????????????????
    </para>

    <para>
      <firstterm>??????????????????</firstterm><indexterm><primary>??????????????????</primary></indexterm> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ?????? <indexterm>
        <primary>?????????</primary>
        <see>??????????????????</see>
      </indexterm> <firstterm>?????????</firstterm> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????IP??????????????? <guilabel>??????????????????</guilabel> ???????????????????????????
    </para>

    <para>
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <indexterm>
        <primary>DNS (Domain Name Service)</primary>
      </indexterm> <firstterm>DNS</firstterm> (Domain Name Service) ??????????????????????????????????????????DNS??????????????????IP??????????????????????????????????????????&FC; ?????????????????????????????????DNS?????????????????????????????????????????????????????????DNS????????????????????????????????????????????????????????????????????????DNS???????????????????????????????????????????????????DNS????????????????????????????????????<guilabel>1????????? DNS</guilabel>???<guilabel>2????????? DNS</guilabel>???????????????<guilabel>3????????? DNS</guilabel> ??????????????????????????????IP??????????????????????????????????????????
    </para>

    <para>
      ????????????????????????????????????????????????????????????<guibutton>???</guibutton> ???????????????????????????
    </para>

  </section>
</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-nextsteps-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-next-steps">
  <title>?????????????????????</title>

  <para>
    &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>


    <section id="sn-web-help">
      <title>Web????????????????????????</title>

      <para>
        &FC; ???????????????????????????&FP; ???Web????????????????????????????????????
      </para>
    <!-- institutional shyness of the word official, odd legal standing -->
      <para>
	<ulink
	  url="http://fedora.redhat.com/docs/">http://fedora.redhat.com/docs/</ulink>
      </para>

      <para>
	The Linux Documentation Project (LDP) ????????????????????????????????????????????????????????????
      </para>

      <para>
	<ulink
	  url="http://www.tldp.org/">http://www.tldp.org/</ulink>
      </para>

    <para>
      &FC; ???????????????????????????&RHEL; ?????????????????????????????????????????????????????????
    </para>

    <para>
      <ulink
	url="http://www.redhat.com/docs/manuals/enterprise/">http://www.redhat.com/docs/manuals/enterprise/</ulink>
    </para>

      <para>
        ????????????????????????????????? &FED; ????????????????????????????????????HOWTO?????????Web????????????????????????????????????Google????????????????????????????????????????????????????????????????????????????????????????????????
      </para>

      <para>
	<ulink
	  url="http://www.google.com/linux/">http://www.google.com/linux/</ulink>
      </para>

    </section>


  <section id="sn-community-help">
   <title>?????????????????????????????????</title>

   <para>
        &FED; ??????????????????????????????????????????????????????????????????Web??????????????????Linux Users Groups(LUGs)???????????????????????????????????????????????????????????????
   </para>

   <para>
        ?????????????????????????????????Web ??????????????????
   </para>

   <para>
	<ulink
	  url="http://forums.fedoraforum.org/">http://forums.fedoraforum.org/</ulink>
   </para>

    </section>


  <section id="sn-community">
   <title>&FED; ???????????????????????????????????????</title>

   <para>
      &FP; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FC; ????????????????????????????????????????????????????????????????????????&RH; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
   </para>

      <para>
	????????????????????????????????????????????????????????????????????????????????????
      </para>

      <para>
	<ulink
	  url="http://fedora.redhat.com/participate/">http://fedora.redhat.com/participate/</ulink>
      </para>

    </section>


</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-other-instmethods-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-other-install-methods">
  <title>??????????????????????????????</title>

  <para>
    ???????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>
  <orderedlist>
    <listitem>
      <para>
        PXE????????????USB???????????????????????????????????????
      </para>
    </listitem>
    <listitem>
      <para>
        <prompt>boot:</prompt> ????????????????????? <option>askmethod</option> ??????????????????????????????
      </para>
    </listitem>
  </orderedlist>

  <figure id="fig-install-method">
    <title>?????????????????????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/install-method.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/install-method.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	  ?????????????????????????????????
        </phrase>
      </textobject>
    </mediaobject>
  </figure>

  <para>
    ?????????????????????????????????????????????????????????????????????<guibutton>OK</guibutton> ?????????????????????
  </para>

  <note>
    <title>CD/DVD ?????????</title>
    <para>
      ??????CD???DVD??????????????? &FED; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
  </note>


  <section id="sn-install-method-server">
    <title>?????????????????????????????????????????????????????????</title>

    <para>
      &FC; ??????FTP, HTTP????????????<indexterm>
        <primary>NFS (Network File System)</primary>
        <secondary>NFS??????????????????????????????</secondary>
      </indexterm> NFS ????????????????????????????????????????????????????????????????????????????????????????????????????????????
      <!-- These installation methods
      require a properly configured server.  Setting up an installation
      server is detailed in a separate tutorial. [This comment can be
      removed when the tutorial exists. - PWF.] -->
    </para>


    <section id="sn-installer-tcpip">
      <title>TCP/IP?????????</title>

      <para>
        ???????????????????????????????????????????????????????????? ??????????????????????????????????????????????????????????????? DHCP ??????????????????????????????????????????????????? DHCP ???????????????????????????<guibutton>Use dynamic IP configuration</guibutton> ??????????????????????????????????????????????????????????????????????????????????????? <guibutton>OK</guibutton> ?????????????????????
      </para>

      <figure id="fig-inst-ipsetup">
	<title>TCP/IP ????????????????????????</title>
	<mediaobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/inst-ipsetup.eps" format="EPS"/>
	  </imageobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/inst-ipsetup.png" format="PNG"/>
	  </imageobject>
	  <textobject>
	    <phrase>
	      TCP/IP ????????????????????????
	    </phrase>
	  </textobject>
	</mediaobject>
      </figure>

      <para>
        ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>

    </section>


    <section id="sn-installer-service-settings">
      <title>???????????????????????????????????????????????????</title>

      <para>
        FTP, HTTP, ????????? NFS ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????IP????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>

      <figure id="fig-ftp-setup">
	<title>FTP ????????????????????????</title>
	<mediaobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/ftp-setup.eps" format="EPS"/>
	  </imageobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/ftp-setup.png" format="PNG"/>
	  </imageobject>
	  <textobject>
	    <phrase>
	      FTP ????????????????????????
	    </phrase>
	  </textobject>
	</mediaobject>
      </figure>

      <para>
        FTP????????????????????????????????????????????????????????????????????????FTP?????????????????????????????????????????????????????????FTP??????????????????FTP???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guibutton>OK</guibutton> ?????????????????????
      </para>

      <figure id="fig-ftp-setup-further">
	<title>???????????????FTP???????????????????????????????????????</title>
	<mediaobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/ftp-setup-further.eps" format="EPS"/>
	  </imageobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/ftp-setup-further.png" format="PNG"/>
	  </imageobject>
	  <textobject>
	    <phrase>
	      ???????????????FTP???????????????????????????????????????
	    </phrase>
	  </textobject>
	</mediaobject>
      </figure>

    </section>

  </section>


  <section id="sn-installing-from-harddrive">
    <title>???????????????????????????????????????????????????</title>

    <para>
      &FED; ???????????????????????????????????????ISO???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????USB?????????????????????????????????????????????ISO?????????????????????????????????????????????????????????????????????????????????<indexterm><primary>ext2</primary><see>????????????????????????</see></indexterm><indexterm><primary>file systems</primary><secondary>ext2</secondary></indexterm> <firstterm>ext2</firstterm>??? <indexterm><primary>ext3</primary><see>file systems</see></indexterm><indexterm><primary>file systems</primary><secondary>ext3</secondary></indexterm><firstterm>ext3</firstterm> ????????? <indexterm><primary>vfat</primary><see>file systems</see></indexterm><indexterm><primary>file systems</primary><secondary>vfat</secondary></indexterm> <firstterm>vfat</firstterm> ???????????????????????!
 ????????????????????????????????????????????????????????????????&FED; ???????????????<systemitem class="filesystem">vfat</systemitem> ??????????????????????????????????????????????????????????????? FAT-16???FAT-32 ????????????????????????????????????????????????????????????????????????????????????????????????????????? <systemitem class="filesystem">vfat</systemitem> (FAT-32)?????????????????????????????????Microsoft Windows???????????????????????????????????????????????????????????????????????????????????? <systemitem class="filesystem">vfat</systemitem> ?????????????????????????????????????????????????????????
    </para>

    <note>
      <title>FAT-16???FAT-32 ??? <systemitem
	  class="filesystem">vfat</systemitem></title>
      <para>
        ?????????????????????????????????????????????????????????????????????&FED; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????Windows ???????????????????????????????????????????????????????????????????????????????????????<application>???????????????????????????</application> ???????????????????????????Linux ????????????????????????????????????????????????????????????????????????????????????<command>fdisk</command> ???????????????????????????????????????????????????
      </para>
    </note>

    <para>
      LVM(Logical Volume Management) ???????????????????????????????????????????????????ISO????????????????????????????????????????????????????????????????????????????????????????????????????????? <xref linkend="sn-partitioning-general" /> ??????????????????????????????
    </para>

    <para>
      ??????????????????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-hdd-instmethod">
      <title>????????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/hdd-instmethod.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/hdd-instmethod.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ????????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ?????????????????????????????????????????????????????????ISO?????????????????????????????????????????????????????????????????????????????????????????????IDE????????????????????????????????????<filename>/dev/hd</filename> ????????????????????????????????????SCSI ????????? USB ????????????????????????????????? <filename>/dev/sd</filename> ???????????????????????????????????????????????????????????????????????? <filename>/dev/hda</filename> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <filename>/dev/sda1</filename> ????????????????????????????????????????????????
    </para>

    <para>
      ?????????<guilabel>?????????????????????????????????????????????</guilabel> ??????????????????????????????ISO?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ??????????????? <guibutton>OK</guibutton> ?????????????????????
    </para>

  </section>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-packageselection-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-packageselection">
  <title>????????????????????????</title>

  <para>
    &FED; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<xref linkend="ch-installtypes" /> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>????????????</guilabel> ???????????????????????????????????????????????????&FED; ??? <guilabel>?????????????????????????????????</guilabel> ???????????????????????????????????????
  </para>

  <tip>
    <title>????????????????????????</title>
    <para>
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <application>?????????????????????</application> ?????????????????????????????????????????????????????????????????????????????????????????????
      <menuchoice>
	<guimenu>Desktop</guimenu>
	<guisubmenu>System Settings</guisubmenu>
	<guimenuitem>Add/Remove Applications</guimenuitem>
      </menuchoice> ?????????????????????
    </para>
  </tip>


  <section id="sn-defaultpackages">
    <title>???????????????????????????????????????????????????</title>

    <para>
      ?????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-package-default">
      <title>?????????????????????????????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/package-default.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/package-default.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ?????????????????????????????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ?????????????????????????????????????????????????????????????????????<guilabel>?????????????????????????????????????????????????????????</guilabel> ?????????????????????<guilabel>???</guilabel> ???????????????????????????????????????<xref linkend="ch-abouttoinstall" /> ??????????????????
    </para>

    <para>
      ?????????????????????????????????????????????????????????<guilabel>??????????????????????????????????????????????????????????????????????????????</guilabel> ?????????????????????<guilabel>???</guilabel> ?????????????????????????????????<xref linkend="sn-packagegroups" /> ??????????????????
    </para>

  </section>


  <section id="sn-packagegroups">
    <title>????????????????????????????????????</title>

    <para>
?????????&FC; ?????????????????????????????????????????????????????????????????????????????????????????????????????? <indexterm><primary>???????????????????????????</primary></indexterm><firstterm>???????????????????????????</firstterm> ???????????????????????????
    </para>

    <figure id="fig-package-selection">
      <title>??????????????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/package-selection.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/package-selection.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ??????????????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <emphasis>????????????????????????</emphasis> ????????????????????????????????????
    </para>

    <para>
      ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>??????</guilabel> ?????????????????????????????????&FC; ??????????????????????????????????????????????????????????????????????????????????????? <guilabel>?????????????????????</guilabel> ????????????????????????????????? ??????????????????????????????????????????????????????????????????????????????????????????<guilabel>??????????????????????????????</guilabel> ??????????????????????????????
    </para>

    <para>
      &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-package-selection-details">
      <title>???????????????????????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/package-selection-details.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/package-selection-details.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ???????????????????????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

  </section>


  <section id="sn-lang-packages">
    <title>???????????????????????????</title>

    <para>
      ???????????? &FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>?????????????????????</guilabel> ????????????????????????????????????????????????????????????
    </para>

    <warning>
      <title>???????????????</title>
      <para>
        ????????????????????????????????????????????? <emphasis>??????</emphasis> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
    </warning>

  </section>


  <section id="sn-extreme-packagegroups">
    <title><guilabel>?????????</guilabel> ???????????? <guilabel>??????</guilabel> ??????????????????</title>

    <para>
      <guilabel>?????????</guilabel> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      <guilabel>?????????</guilabel> ?????????????????????&FC; ???????????????????????? <emphasis>??????</emphasis> ???????????????????????????????????????????????????&FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <caution>
      <title>?????????????????????</title>
      <para>
        <guilabel>?????????</guilabel> ?????????????????????????????????????????????????????????6.9Gb?????????????????????????????????????????????????????????????????????????????????????????????175Mb??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
    </caution>

    <para>
      <guilabel>??????</guilabel> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ????????????????????????????????????????????????<guilabel>???</guilabel> ?????????????????????????????????&FC; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

  </section>
</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-rootpassword-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-rootpassword">
  <title>root????????????????????????</title>

  <para>
    &FED; ??????????????????????????????????????? <indexterm><primary>root ???????????????</primary></indexterm> <firstterm><systemitem class="username">root</systemitem></firstterm> ???????????????????????????????????????????????????????????????Linux?????????????????????<systemitem class="username">root</systemitem> ?????????????????? &SEL; ??????????????????????????????????????????root?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <systemitem class="username">root</systemitem> ????????????????????????????????????
  </para>

  <important>
    <title><systemitem class="username">root</systemitem>
      ???????????????????????????????????????</title>
    <para>
      <systemitem class="username">root</systemitem> ????????? &FC; ?????????????????????????????????????????????????????????????????????<systemitem class="username">root</systemitem> ????????????????????????????????????????????????????????????????????????????????????????????????
    </para>
  </important>

  <para>
    &FED; ??????????????????????????????????????????<systemitem class="username">root</systemitem> ?????????????????????????????????6?????????????????????????????????????????????????????????<systemitem class="username">root</systemitem> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <itemizedlist>
    <listitem>
      <para>
        ??????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
    </listitem>
    <listitem>
      <para>
        ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? 
      </para>
    </listitem>
    <listitem>
      <para>
        ???????????????????????????????????????????????????????????????
      </para>
    </listitem>
  </itemizedlist>

  <para>
    ?????????????????????????????????????????????????????????
  </para>

  <itemizedlist>
    <listitem>
      <para>
	<systemitem>f9*@1Ls99A</systemitem>
      </para>
    </listitem>
    <listitem>
      <para>
	<systemitem>HL8$391%%rb</systemitem>
      </para>
    </listitem>
    <listitem>
      <para>
	<systemitem>Iwtb,10^th</systemitem>
      </para>
    </listitem>
  </itemizedlist>

  <para>
    <guilabel>Root ???????????????</guilabel>????????????????????? <systemitem class="username">root</systemitem> ?????????????????????????????????????????????&FED; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>??????</guilabel> ????????????????????????????????????????????????????????????
  </para>

  <figure id="fig-set-rootpw">
    <title>Root??????????????????????????????</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/root-passwd.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/root-passwd.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	  Root??????????????????????????????
        </phrase>
      </textobject>
    </mediaobject>
  </figure>

  <para>
    root????????????????????????????????????<guibutton>???</guibutton> ???????????????????????????????????????
  </para>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-timezone-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-timezone">
  <title>???????????????????????????</title>

  <para>
    ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <indexterm><primary>NTP (Network Time Protocol)</primary></indexterm> NTP (Network Time Protocol) ???????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <section id="sn-selecting-timezone">
    <title>???????????????????????????</title>

    <para>
      &FED; ???????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-timezone">
      <title>??????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/timezone.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/timezone.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ??????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FED; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>X</guilabel> ???????????????????????????
    </para>

    <para>
      ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

  </section>

  <section id="sn-utc">
    <title>??????????????? (UTC)</title>

    <para>
      <indexterm><primary>UTC (Universal Co-ordinated time)</primary></indexterm> ?????????????????????<indexterm><primary>GMT (Greenwich Mean Time)</primary><see>UTC</see></indexterm> ????????????????????????(GMT)????????????????????????????????????
    </para>

    <para>
      &FC; ????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>?????????????????????????????????UTC?????????</guilabel> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FC; ???????????????????????????UTC??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????Unix????????????????????????????????????????????????????????????????????????????????????
    </para>

    <caution>
      <title>Window???????????????????????????</title>
      <para>
        ???????????????????????????Microsoft Windows???????????????????????????<guilabel>???????????????????????????UTC?????????</guilabel> ?????????????????????????????????????????????????????????Microsoft????????????????????????????????????????????????UTC????????????????????????????????????BIOS?????????????????????????????????????????????&FC; ??????????????????????????????????????????????????????????????????
      </para>
    </caution>

    <para>
      ????????????????????? <guibutton>???</guibutton> ?????????????????????
    </para>

  </section>
</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE fedora-install-guide-upgrading-ja_JP.xml ---
<!-- $Id: -->

<chapter id="ch-upgrading-system">
  <title>???????????????????????????????????????????????????</title>

  <para>
    ??????????????????????????????????????????????????????????????? &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  </para>

  <section id="sn-upgrade-examine">
    <title>?????????????????????????????????????????????</title>

    <para>
      ????????????????????? &FC; ??? &RHL; ?????????????????????????????????????????????????????????????????????????????????
    </para>

    <figure id="fig-upgrade-examine">
      <title>????????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/upgrade-examine.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/upgrade-examine.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ????????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <guibutton>???</guibutton> ?????????????????????
    </para>

    <note>
      <title>??????????????????????????????????????????????????????</title>
      <para>
        ????????? &FC; ????????? &RHL; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
      </para>
    </note>

  </section>

  <section id="sn-upgrading-bootloader">
    <title>????????????????????????????????????????????????????????????</title>

    <para>
      <indexterm><primary>?????????????????????</primary><secondary>?????????????????????</secondary></indexterm> &FC; ????????????????????????????????????????????????????????????????????????????????????????????? <indexterm><primary>?????????????????????</primary><seealso>GRUB</seealso></indexterm><firstterm>?????????????????????</firstterm> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<xref linkend="ch-bootloader" /> ??????????????????????????????
    </para>


    <figure id="fig-upgrade-bootloader">
      <title>???????????????????????????????????????????????????</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/upgrade-bootloader.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/upgrade-bootloader.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    ???????????????????????????????????????????????????
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      Linux?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<guilabel>????????????????????????????????????</guilabel> ????????????????????????????????????????????????????????????????????? &FC; ????????? &RHL; ??????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      <firstterm>GRUB</firstterm> ??? &FC; ???????????????????????????????????????????????????????????????????????????????????? <trademark>BootMagic</trademark>, <trademark>System Commander</trademark>, ????????????Microsoft Windows??????????????????????????????????????????????????????????????????????????????????????????&FC; ?????????????????????????????????????????????????????????????????????????????????????????????????????? <guilabel>??????????????????????????????????????????</guilabel> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
    </para>

    <para>
      ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????GRUB????????????????????????????????????<guilabel>?????????????????????????????????????????????</guilabel> ??????????????????????????????
    </para>

    <para>
      ??????????????????<guibutton>???</guibutton> ?????????????????????????????????????????????
    </para>

  </section>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Sun Nov  6 01:23:24 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat,  5 Nov 2005 20:23:24 -0500
Subject: release-notes intro-it.xml, 1.1, 1.2 package-movement-it.xml, 1.2,
	1.3 project-overview-it.xml, 1.1, 1.2
Message-ID: <200511060123.jA61NOj1028153@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28132

Modified Files:
	intro-it.xml package-movement-it.xml project-overview-it.xml 
Log Message:



Index: intro-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/intro-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- intro-it.xml	4 Nov 2005 19:56:08 -0000	1.1
+++ intro-it.xml	6 Nov 2005 01:23:15 -0000	1.2
@@ -22,13 +22,13 @@
   <para>
     Ulteriori importanti informazioni su questa release potrebbero essere rese
     disponibili su <ulink
-      url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>. 
+      url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>.
     Gli utenti sono avvisati di controllare questo url regolarmente per gli aggiornamenti.
   </para>
   <para>
     Per riportare errori o altre richieste su queste release notes,
     inviate un bug report usando questo <ulink url="&BUG-URL;">
-      bugzilla template precompilato</ulink>.
+      template bugzilla precompilato</ulink>.
   </para>
 <!-- This is just to tweaky to HTML and will make people think it's b0rked
   <para>


Index: package-movement-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-movement-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- package-movement-it.xml	5 Nov 2005 12:22:39 -0000	1.2
+++ package-movement-it.xml	6 Nov 2005 01:23:15 -0000	1.3
@@ -14,8 +14,8 @@
 sed -e 's,^,* ,g' -e 's,$,\n,g' /tmp/diff > diffwiki</command>
 </screen>
   <section>
-    <title>Modifiche del pacchetto</title>
-    <para>Al 21st September 2005 </para>
+    <title>Pacchetti modificati</title>
+    <para>Al 21st Settembre 2005 </para>
     <para>[106429] MAKEDEV-3.19-1 -> [115423] MAKEDEV-3.19-4 </para>
     <para>[111566] <ulink
 	url='/ImageMagick'>ImageMagick</ulink>-6.2.2.0-2 -> [112246]
@@ -933,9 +933,9 @@
     <para>[106079] prelink-0.3.4-3 -> [117615] prelink-0.3.6-1 </para>
     <para>[110767] netpbm-10.27-3 -> [116518] netpbm-10.29-1 </para>
     <section id="sn-packages-added">
-      <title>Packages Added</title>
+      <title>Pacchetti aggiunti</title>
       <para>
-	These packages have been added to &FC; for this release notes.
+	Questi pacchetti sono stati aggiunti a &FC; per questa release notes.
       </para>
       <para>scim-anthy-0.6.1-1.fc5 </para>
       <para>struts-1.2.4-2jpp_3fc </para>
@@ -1023,9 +1023,9 @@
       <para>libiec61883-1.0.0-8.fc5 </para>
     </section>
     <section>
-      <title>Packages Removed</title>
+      <title>Pacchetti Rimossi</title>
       <para>
-	These packages have been removed:
+	Questi pacchetti sono stati rimossi:
       </para>
       <para>ccs-0.25-0.17 </para>
       <para>cman-1.0-0.pre33.15 </para>


Index: project-overview-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/project-overview-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project-overview-it.xml	4 Nov 2005 20:02:41 -0000	1.1
+++ project-overview-it.xml	6 Nov 2005 01:23:15 -0000	1.2
@@ -1,101 +1,97 @@
   <section id="sn-whatitis">
-    <title>An Overview of the &PROJ;</title>
+    <title>Una descrizione del &PROJ;</title>
     <para>
-      The goal of the &PROJ; is to work with the Linux community to
-      build a complete, general-purpose operating system exclusively
-      from open source software.  Development is done in a public forum.
-      The project produces time-based releases of &DISTRO; approximately
-      2-3 times a year, with a public release schedule.  The &RH;
-      engineering team continues to participate in building &DISTRO;
-      and invites and encourages more outside participation than was
-      possible in the past.  By using this more open process, we hope to
-      provide an operating system more in line with the ideals of free
-      software and more appealing to the open source community.
+      L'obiettivo del &PROJ; ?? di lavorare con la comunit?? Linux per
+      creare un sistema operativo completo, general-purpose esclusivamente
+      da software open source.  Lo sviluppo ?? compiuto in un forum pubbllico.
+      Il progetto produce delle releases su base temporale di &DISTRO; approssimativamente
+      2-3 volte l'anno, con uno scadenziario pubblico delle release.  Le squadre
+      di ingegneri &RH; continuano a participare alla costruzione della &DISTRO;
+      ed invitano ed incoraggiano pi?? partecipanti esterni di quanto era
+      possibile in passato.  Utilizzando questo processo pi?? aperto, speriamo di
+      fornire un sistema operativo molto pi?? in linea con gli ideali di software
+      libero e molto pi?? appetibile alla comunit?? open source.
     </para>
     <para>
-      For more information, refer to the &PROJ; website:
+      Per maggiori informazioni, fate riferimento al sito web di &PROJ;:
     </para>
     <para>
       <ulink
 	url="http://fedora.redhat.com/">http://fedora.redhat.com/</ulink>
     </para>
     <para>
-      In addition to the website, the following mailing lists are
-      available:
+      In aggiunta al sito, sono disponibili le seguenti mailing lists:
     </para>
     <itemizedlist>
       <listitem>
         <para>
-	  fedora-list at redhat.com &mdash; For users of &DISTRO; releases
+	  fedora-list at redhat.com &mdash; Per gli utenti delle releases di &DISTRO;
 	</para>
       </listitem>
       <listitem>
         <para>
-	  fedora-test-list at redhat.com &mdash; For testers of &DISTRO;
-	  test releases
+	  fedora-test-list at redhat.com &mdash; Per i testers delle test releases di &DISTRO;
 	</para>
       </listitem>
       <listitem>
         <para>
-	  fedora-devel-list at redhat.com &mdash; For developers,
-	  developers, developers
+	  fedora-devel-list at redhat.com &mdash; Per gli sviluppatori,
+	  sviluppatori, sviluppatori
 	</para>
       </listitem>
       <listitem>
         <para>
-	  fedora-docs-list at redhat.com &mdash; For participants of the
-	  Documentation Project
+	  fedora-docs-list at redhat.com &mdash; Per i partecipanti al Documentation Project
 	</para>
       </listitem>
     </itemizedlist>
     <para>
-      To subscribe to any of these lists, send an email with the word
-      "subscribe" in the subject to
+      Per sottoscrivere ad una di queste liste, spedisci un email con la parola
+      "subscribe" nel soggetto a
       <computeroutput><replaceable>&lt;listname&gt;</replaceable>-request</computeroutput>
-      (where
+      (dove
       <computeroutput><replaceable>&lt;listname&gt;</replaceable></computeroutput>
-      is one of the above list names.)
+      ?? una delle sopraelencate liste.)
     </para>
     <para>
-      Alternately, you can subscribe through the Web interface:
+      Alternativamente, puoi sottoscriverti mediante l'interfaccia Web:
     </para>
     <para>
       <ulink url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
     </para>
     <para>
-      If you have subscribed in the past to rhl-list, rhl-beta-list,
-      rhl-devel-list, or rhl-docs-list, your subscriptions have been
-      retained.
-    </para>
-    <para>
-      The &PROJ; also includes an IRC (Internet Relay Chat) channel.  IRC is
-      a real-time, text-based form of communication.  With it, you can have
-      conversations with multiple people in an open channel or chat with someone
-      privately one-on-one.
-    </para>
-    <para>
-      To talk with other &PROJ; participants via IRC, access freenode IRC
-      network.  Initially, you can use <filename>irc.freenode.net</filename> as
-      the IRC server, although you may decide to select a server that is
-      geographically closer to you.  Refer to the freenode website (<ulink
-      url="http://www.freenode.net/">http://www.freenode.net/</ulink>) for more
-      information.  &PROJ; participants frequent the
-      <filename>#fedora</filename> channel, while &PROJ; developers can often be
-      found on the <filename>#fedora-devel</filename> channel.  Some of the
-      larger projects may have their own channels as well; this information can
-      be found on the project pages.
-    </para>
-    <para>
-      In order to talk on the <filename>#fedora</filename> channel, you
-      will need to register your nickname (<firstterm>nick</firstterm>).
-      Instructions are given when you <command>/join</command> the
-      channel.
+      Se sei stato sottoscritto in passato alle rhl-list, rhl-beta-list,
+      rhl-devel-list, o rhl-docs-list, le tue sottoscrizioni saranno
+      mantenute.
+    </para>
+    <para>
+      Il &PROJ; include anche un canale IRC (Internet Relay Chat).  IRC ?? una
+      forma di comunicazione real-time, basata su testo.  Con essa, puoi avere
+      conversazioni con pi?? persone contemporaneamente in un canale aqperto o
+      chattare privatamente con qualcuno uno-a-uno.
+    </para>
+    <para>
+      Per parlare con gli altri partecipanti al &PROJ; via IRC, accedi alla freenode IRC
+      network.  Inizialmente, potresti usare <filename>irc.freenode.net</filename> come
+      IRC server, anche se potresti decidere di selezionare un server che ti sia
+      geograficamente pi?? vicino.  Fai riferimento al sito web di freenode (<ulink
+      url="http://www.freenode.net/">http://www.freenode.net/</ulink>) per ulteriori
+      informazioni.  I partecipanti a &PROJ; frequentano il canale
+      <filename>#fedora</filename>, mentre gli sviluppatori &PROJ; possono spesso essere
+      trovati sul canale <filename>#fedora-devel</filename>.  Alcuni dei progetti
+      pi?? grandi possono anche avere i propri canali; queste informazioni si possono
+      trovare sulle pagine del progetto.
+    </para>
+    <para>
+      Per poter parlare sul canale <filename>#fedora</filename>, dovrai
+      registrare il tuo nickname (<firstterm>nick</firstterm>).
+      Ti verranno date istruzioni quando farai il <command>/join</command> al
+      cannale.
     </para>
     <note>
-      <title>Note</title>
+      <title>Nota</title>
       <para>
-	&RH; has no control over the &PROJ; IRC channels or their
-	content.
+	&RH; non ha controllo sui canali IRC di &PROJ; o i loro contenuti.
       </para>
     </note>
   </section>



From fedora-docs-commits at redhat.com  Sun Nov  6 04:52:01 2005
From: fedora-docs-commits at redhat.com (Yoshinari Takaoka (mumumu))
Date: Sat,  5 Nov 2005 23:52:01 -0500
Subject: install-guide fedora-install-guide-abouttoinstall-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-bootloader-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-diskpartitioning-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-firewallconfig-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-firstboot-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-installingpackages-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-installtypes-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-locale-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-networkconfig-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-other-instmethods-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-packageselection-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-rootpassword-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-timezone-ja_JP.xml, 1.1,
	1.2 fedora-install-guide-upgrading-ja_JP.xml, 1.1, 1.2
Message-ID: <200511060452.jA64q1RE003325@cvs-int.fedora.redhat.com>

Author: mumumu

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3291

Modified Files:
	fedora-install-guide-abouttoinstall-ja_JP.xml 
	fedora-install-guide-bootloader-ja_JP.xml 
	fedora-install-guide-diskpartitioning-ja_JP.xml 
	fedora-install-guide-firewallconfig-ja_JP.xml 
	fedora-install-guide-firstboot-ja_JP.xml 
	fedora-install-guide-installingpackages-ja_JP.xml 
	fedora-install-guide-installtypes-ja_JP.xml 
	fedora-install-guide-locale-ja_JP.xml 
	fedora-install-guide-networkconfig-ja_JP.xml 
	fedora-install-guide-other-instmethods-ja_JP.xml 
	fedora-install-guide-packageselection-ja_JP.xml 
	fedora-install-guide-rootpassword-ja_JP.xml 
	fedora-install-guide-timezone-ja_JP.xml 
	fedora-install-guide-upgrading-ja_JP.xml 
Log Message:
changed fileref attribute of imagedata from *.png, *.eps to *-ja_JP.png, *-ja_JP.eps


Index: fedora-install-guide-abouttoinstall-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-abouttoinstall-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-abouttoinstall-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-abouttoinstall-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -18,10 +18,10 @@
     <title>???????????????????????????????????????</title>
     <mediaobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/about-to-install.eps" format="EPS"/>
+        <imagedata align="center" fileref="./figs/about-to-install-ja_JP.eps" format="EPS"/>
       </imageobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/about-to-install.png" format="PNG"/>
+        <imagedata align="center" fileref="./figs/about-to-install-ja_JP.png" format="PNG"/>
       </imageobject>
       <textobject>
         <phrase>


Index: fedora-install-guide-bootloader-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-bootloader-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-bootloader-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-bootloader-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -26,10 +26,10 @@
     </title>
     <mediaobject>
       <imageobject>
-        <imagedata align="center" fileref="figs/bootloader-config.eps" format="EPS"/>
+        <imagedata align="center" fileref="figs/bootloader-config-ja_JP.eps" format="EPS"/>
       </imageobject>
       <imageobject>
-        <imagedata align="center" fileref="figs/bootloader-config.png" format="PNG"/>
+        <imagedata align="center" fileref="figs/bootloader-config-ja_JP.png" format="PNG"/>
       </imageobject>
       <textobject>
         <phrase>?????????????????????????????????</phrase>
@@ -48,10 +48,10 @@
       <title>??????????????????????????????</title>
       <mediaobject>
         <imageobject>
-          <imagedata align="center" fileref="figs/bootloader-change.eps" format="EPS"/>
+          <imagedata align="center" fileref="figs/bootloader-change-ja_JP.eps" format="EPS"/>
         </imageobject>
         <imageobject>
-          <imagedata align="center" fileref="figs/bootloader-change.png" format="PNG"/>
+          <imagedata align="center" fileref="figs/bootloader-change-ja_JP.png" format="PNG"/>
         </imageobject>
         <textobject>
           <phrase>??????????????????????????????</phrase>
@@ -113,10 +113,10 @@
       <title>???????????????????????????????????????????????????????????????????????????</title>
       <mediaobject>
         <imageobject>
-          <imagedata align="center" fileref="figs/bootloader-others.eps" format="EPS"/>
+          <imagedata align="center" fileref="figs/bootloader-others-ja_JP.eps" format="EPS"/>
         </imageobject>
         <imageobject>
-          <imagedata align="center" fileref="figs/bootloader-others.png" format="PNG"/>
+          <imagedata align="center" fileref="figs/bootloader-others-ja_JP.png" format="PNG"/>
         </imageobject>
         <textobject>
           <phrase>???????????????????????????????????????????????????????????????????????????</phrase>
@@ -149,10 +149,10 @@
       <title>???????????????????????????????????????</title>
       <mediaobject>
         <imageobject>
-          <imagedata align="center" fileref="figs/bootloader-password.eps" format="EPS"/>
+          <imagedata align="center" fileref="figs/bootloader-password-ja_JP.eps" format="EPS"/>
         </imageobject>
         <imageobject>
-          <imagedata align="center" fileref="figs/bootloader-password.png" format="PNG"/>
+          <imagedata align="center" fileref="figs/bootloader-password-ja_JP.png" format="PNG"/>
         </imageobject>
         <textobject>
           <phrase>??????????????????????????????????????????????????????</phrase>
@@ -213,10 +213,10 @@
       <title>????????????????????????????????????????????????</title>
       <mediaobject>
         <imageobject>
-          <imagedata align="center" fileref="figs/bootloader-advanced.eps" format="EPS"/>
+          <imagedata align="center" fileref="figs/bootloader-advanced-ja_JP.eps" format="EPS"/>
         </imageobject>
         <imageobject>
-          <imagedata align="center" fileref="figs/bootloader-advanced.png" format="PNG"/>
+          <imagedata align="center" fileref="figs/bootloader-advanced-ja_JP.png" format="PNG"/>
         </imageobject>
         <textobject>
           <phrase>????????????????????????????????????????????????</phrase>


Index: fedora-install-guide-diskpartitioning-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-diskpartitioning-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-diskpartitioning-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-diskpartitioning-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -12,10 +12,10 @@
     </title>
     <mediaobject>
       <imageobject>
-        <imagedata align="center" fileref="figs/partitioning-setup.eps" format="EPS"/>
+        <imagedata align="center" fileref="figs/partitioning-setup-ja_JP.eps" format="EPS"/>
       </imageobject>
       <imageobject>
-        <imagedata align="center" fileref="figs/partitioning-setup.png" format="PNG"/>
+        <imagedata align="center" fileref="figs/partitioning-setup-ja_JP.png" format="PNG"/>
       </imageobject>
       <textobject>
         <phrase> ????????????????????????????????????????????????</phrase>
@@ -41,10 +41,10 @@
     </title>
     <mediaobject>
       <imageobject>
-        <imagedata align="center" fileref="figs/partitioning-automatic.eps" format="EPS"/>
+        <imagedata align="center" fileref="figs/partitioning-automatic-ja_JP.eps" format="EPS"/>
       </imageobject>
       <imageobject>
-        <imagedata align="center" fileref="figs/partitioning-automatic.png" format="PNG"/>
+        <imagedata align="center" fileref="figs/partitioning-automatic-ja_JP.png" format="PNG"/>
       </imageobject>
       <textobject>
         <phrase>??????????????????????????????????????????</phrase>
@@ -283,10 +283,10 @@
       </title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="figs/disk-setup.eps" format="EPS"/>
+	  <imagedata align="center" fileref="figs/disk-setup-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="figs/disk-setup.png" format="PNG"/>
+	  <imagedata align="center" fileref="figs/disk-setup-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>???????????????????????????????????????</phrase>


Index: fedora-install-guide-firewallconfig-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-firewallconfig-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-firewallconfig-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-firewallconfig-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -11,10 +11,10 @@
     <title>??????????????????????????????</title>
     <mediaobject>
       <imageobject>
-	<imagedata align="center" fileref="./figs/firewall.eps" format="EPS"/>
+	<imagedata align="center" fileref="./figs/firewall-ja_JP.eps" format="EPS"/>
       </imageobject>
       <imageobject>
-	<imagedata align="center" fileref="./figs/firewall.png" format="PNG"/>
+	<imagedata align="center" fileref="./figs/firewall-ja_JP.png" format="PNG"/>
       </imageobject>
       <textobject>
 	<phrase>


Index: fedora-install-guide-firstboot-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-firstboot-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-firstboot-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-firstboot-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -11,10 +11,10 @@
     <title>??????????????????</title>
     <mediaobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/fboot-welcome.eps" format="EPS"/>
+        <imagedata align="center" fileref="./figs/fboot-welcome-ja_JP.eps" format="EPS"/>
       </imageobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/fboot-welcome.png" format="PNG"/>
+        <imagedata align="center" fileref="./figs/fboot-welcome-ja_JP.png" format="PNG"/>
       </imageobject>
       <textobject>
         <phrase>
@@ -47,10 +47,10 @@
       <title>?????????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-licence.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/fboot-licence-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-licence.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/fboot-licence-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>
@@ -82,10 +82,10 @@
       <title>??????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-time.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/fboot-time-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-time.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/fboot-time-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>
@@ -163,10 +163,10 @@
       <title>?????????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-display.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/fboot-display-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-display.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/fboot-display-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>
@@ -184,10 +184,10 @@
       <title>?????????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-display-monitor.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/fboot-display-monitor-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-display-monitor.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/fboot-display-monitor-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>
@@ -226,10 +226,10 @@
       <title>????????????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-user.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/fboot-user-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-user.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/fboot-user-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>
@@ -279,10 +279,10 @@
       <title>????????????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-sound.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/fboot-sound-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-sound.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/fboot-sound-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>
@@ -336,10 +336,10 @@
       <title>?????????CD ??????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-cds.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/fboot-cds-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-cds.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/fboot-cds-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>
@@ -357,10 +357,10 @@
       <title>??????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-finish.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/fboot-finish-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/fboot-finish.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/fboot-finish-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>


Index: fedora-install-guide-installingpackages-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-installingpackages-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-installingpackages-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-installingpackages-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -11,10 +11,10 @@
     <title>?????????????????????????????????????????????</title>
     <mediaobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/installing-inprogress.eps" format="EPS"/>
+        <imagedata align="center" fileref="./figs/installing-inprogress-ja_JP.eps" format="EPS"/>
       </imageobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/installing-inprogress.png" format="PNG"/>
+        <imagedata align="center" fileref="./figs/installing-inprogress-ja_JP.png" format="PNG"/>
       </imageobject>
       <textobject>
         <phrase>


Index: fedora-install-guide-installtypes-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-installtypes-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-installtypes-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-installtypes-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -14,10 +14,10 @@
       <title>???????????????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/install-types.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/install-types-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/install-types.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/install-types-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>


Index: fedora-install-guide-locale-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-locale-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-locale-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-locale-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -61,10 +61,10 @@
       <title>??????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/keyb-conf.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/keyb-conf-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/keyb-conf.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/keyb-conf-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>


Index: fedora-install-guide-networkconfig-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-networkconfig-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-networkconfig-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-networkconfig-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -21,10 +21,10 @@
     <title>??????????????????????????????</title>
     <mediaobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/net-config-dhcp.eps" format="EPS"/>
+        <imagedata align="center" fileref="./figs/net-config-dhcp-ja_JP.eps" format="EPS"/>
       </imageobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/net-config-dhcp.png" format="PNG"/>
+        <imagedata align="center" fileref="./figs/net-config-dhcp-ja_JP.png" format="PNG"/>
       </imageobject>
       <textobject>
         <phrase>


Index: fedora-install-guide-other-instmethods-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-other-instmethods-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-other-instmethods-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-other-instmethods-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -23,10 +23,10 @@
     <title>?????????????????????????????????</title>
     <mediaobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/install-method.eps" format="EPS"/>
+        <imagedata align="center" fileref="./figs/install-method-ja_JP.eps" format="EPS"/>
       </imageobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/install-method.png" format="PNG"/>
+        <imagedata align="center" fileref="./figs/install-method-ja_JP.png" format="PNG"/>
       </imageobject>
       <textobject>
         <phrase>
@@ -74,10 +74,10 @@
 	<title>TCP/IP ????????????????????????</title>
 	<mediaobject>
 	  <imageobject>
-	    <imagedata align="center" fileref="./figs/inst-ipsetup.eps" format="EPS"/>
+	    <imagedata align="center" fileref="./figs/inst-ipsetup-ja_JP.eps" format="EPS"/>
 	  </imageobject>
 	  <imageobject>
-	    <imagedata align="center" fileref="./figs/inst-ipsetup.png" format="PNG"/>
+	    <imagedata align="center" fileref="./figs/inst-ipsetup-ja_JP.png" format="PNG"/>
 	  </imageobject>
 	  <textobject>
 	    <phrase>
@@ -105,10 +105,10 @@
 	<title>FTP ????????????????????????</title>
 	<mediaobject>
 	  <imageobject>
-	    <imagedata align="center" fileref="./figs/ftp-setup.eps" format="EPS"/>
+	    <imagedata align="center" fileref="./figs/ftp-setup-ja_JP.eps" format="EPS"/>
 	  </imageobject>
 	  <imageobject>
-	    <imagedata align="center" fileref="./figs/ftp-setup.png" format="PNG"/>
+	    <imagedata align="center" fileref="./figs/ftp-setup-ja_JP.png" format="PNG"/>
 	  </imageobject>
 	  <textobject>
 	    <phrase>
@@ -126,10 +126,10 @@
 	<title>???????????????FTP???????????????????????????????????????</title>
 	<mediaobject>
 	  <imageobject>
-	    <imagedata align="center" fileref="./figs/ftp-setup-further.eps" format="EPS"/>
+	    <imagedata align="center" fileref="./figs/ftp-setup-further-ja_JP.eps" format="EPS"/>
 	  </imageobject>
 	  <imageobject>
-	    <imagedata align="center" fileref="./figs/ftp-setup-further.png" format="PNG"/>
+	    <imagedata align="center" fileref="./figs/ftp-setup-further-ja_JP.png" format="PNG"/>
 	  </imageobject>
 	  <textobject>
 	    <phrase>


Index: fedora-install-guide-packageselection-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-packageselection-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-packageselection-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-packageselection-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -31,10 +31,10 @@
       <title>?????????????????????????????????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/package-default.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/package-default-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/package-default.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/package-default-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>
@@ -66,10 +66,10 @@
       <title>??????????????????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/package-selection.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/package-selection-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/package-selection.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/package-selection-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>
@@ -95,10 +95,10 @@
       <title>???????????????????????????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/package-selection-details.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/package-selection-details-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/package-selection-details.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/package-selection-details-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>


Index: fedora-install-guide-rootpassword-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-rootpassword-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-rootpassword-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-rootpassword-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -67,10 +67,10 @@
     <title>Root??????????????????????????????</title>
     <mediaobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/root-passwd.eps" format="EPS"/>
+        <imagedata align="center" fileref="./figs/root-passwd-ja_JP.eps" format="EPS"/>
       </imageobject>
       <imageobject>
-        <imagedata align="center" fileref="./figs/root-passwd.png" format="PNG"/>
+        <imagedata align="center" fileref="./figs/root-passwd-ja_JP.png" format="PNG"/>
       </imageobject>
       <textobject>
         <phrase>


Index: fedora-install-guide-timezone-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-timezone-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-timezone-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-timezone-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -18,10 +18,10 @@
       <title>??????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/timezone.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/timezone-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/timezone.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/timezone-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>


Index: fedora-install-guide-upgrading-ja_JP.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-upgrading-ja_JP.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-upgrading-ja_JP.xml	5 Nov 2005 19:38:03 -0000	1.1
+++ fedora-install-guide-upgrading-ja_JP.xml	6 Nov 2005 04:51:54 -0000	1.2
@@ -18,10 +18,10 @@
       <title>????????????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/upgrade-examine.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/upgrade-examine-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/upgrade-examine.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/upgrade-examine-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>
@@ -56,10 +56,10 @@
       <title>???????????????????????????????????????????????????</title>
       <mediaobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/upgrade-bootloader.eps" format="EPS"/>
+	  <imagedata align="center" fileref="./figs/upgrade-bootloader-ja_JP.eps" format="EPS"/>
 	</imageobject>
 	<imageobject>
-	  <imagedata align="center" fileref="./figs/upgrade-bootloader.png" format="PNG"/>
+	  <imagedata align="center" fileref="./figs/upgrade-bootloader-ja_JP.png" format="PNG"/>
 	</imageobject>
 	<textobject>
 	  <phrase>



From fedora-docs-commits at redhat.com  Sun Nov  6 04:54:06 2005
From: fedora-docs-commits at redhat.com (Yoshinari Takaoka (mumumu))
Date: Sat,  5 Nov 2005 23:54:06 -0500
Subject: install-guide/figs about-to-install-ja_JP.png, NONE,
 1.1 bootloader-advanced-ja_JP.png, NONE, 1.1 bootloader-change-ja_JP.png,
 NONE, 1.1 bootloader-config-ja_JP.png, NONE, 1.1 bootloader-others-ja_JP.png,
 NONE, 1.1 bootloader-password-ja_JP.png, NONE, 1.1 disk-setup-ja_JP.png,
 NONE, 1.1 fboot-cds-ja_JP.png, NONE, 1.1 fboot-display-ja_JP.png, NONE,
 1.1 fboot-display-monitor-ja_JP.png, NONE, 1.1 fboot-finish-ja_JP.png, NONE,
 1.1 fboot-licence-ja_JP.png, NONE, 1.1 fboot-sound-ja_JP.png, NONE,
 1.1 fboot-time-ja_JP.png, NONE, 1.1 fboot-user-ja_JP.png, NONE,
 1.1 fboot-welcome-ja_JP.png, NONE, 1.1 firewall-ja_JP.png, NONE,
 1.1 ftp-setup-further-ja_JP.png, NONE, 1.1 ftp-setup-ja_JP.png, NONE,
 1.1 inst-ipsetup-ja_JP.png, NONE, 1.1 install-method-ja_JP.png, NONE,
 1.1 install-types-ja_JP.png, NONE, 1.1 installing-inprogress-ja_JP.png, NONE,
 1.1 keyb-conf-ja_JP.png, NONE, 1.1 net-config-dhcp-ja_JP.png, NONE,
 1.1 package-default-ja_JP.png, NONE, 1.1 package-selection-details-ja_JP.png,
 NONE, 1.1 package-selection-ja_JP.png, NONE, 1.1!
 partitioning-automatic-ja_JP.png, NONE, 1.1 partitioning-setup-ja_JP.png,
 NONE, 1.1 root-passwd-ja_JP.png, NONE, 1.1 timezone-ja_JP.png, NONE,
 1.1 upgrade-bootloader-ja_JP.png, NONE, 1.1 upgrade-examine-ja_JP.png, NONE,
 1.1
Message-ID: <200511060454.jA64s63q003406@cvs-int.fedora.redhat.com>

Author: mumumu

Update of /cvs/docs/install-guide/figs
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3356

Added Files:
	about-to-install-ja_JP.png bootloader-advanced-ja_JP.png 
	bootloader-change-ja_JP.png bootloader-config-ja_JP.png 
	bootloader-others-ja_JP.png bootloader-password-ja_JP.png 
	disk-setup-ja_JP.png fboot-cds-ja_JP.png 
	fboot-display-ja_JP.png fboot-display-monitor-ja_JP.png 
	fboot-finish-ja_JP.png fboot-licence-ja_JP.png 
	fboot-sound-ja_JP.png fboot-time-ja_JP.png 
	fboot-user-ja_JP.png fboot-welcome-ja_JP.png 
	firewall-ja_JP.png ftp-setup-further-ja_JP.png 
	ftp-setup-ja_JP.png inst-ipsetup-ja_JP.png 
	install-method-ja_JP.png install-types-ja_JP.png 
	installing-inprogress-ja_JP.png keyb-conf-ja_JP.png 
	net-config-dhcp-ja_JP.png package-default-ja_JP.png 
	package-selection-details-ja_JP.png 
	package-selection-ja_JP.png partitioning-automatic-ja_JP.png 
	partitioning-setup-ja_JP.png root-passwd-ja_JP.png 
	timezone-ja_JP.png upgrade-bootloader-ja_JP.png 
	upgrade-examine-ja_JP.png 
Log Message:
initial japanese figure files for html output



From fedora-docs-commits at redhat.com  Sun Nov  6 08:51:34 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sun,  6 Nov 2005 03:51:34 -0500
Subject: docs-common/bin tidy-bowl,1.3,1.4
Message-ID: <200511060851.jA68pY2m010002@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9966/docs-common/bin

Modified Files:
	tidy-bowl 
Log Message:
Allow XML written in one of the Romance languages to be prettyprinted
using the Tidy Bowl infrastructure.  We need to keep non-latin1 characters
from passing though "xmlformat", but it doesn't matter what word the latin1
characters spell ;-)  N.B.: you could also read "latin1" as "iso-8859-1" 
and friends.



Index: tidy-bowl
===================================================================
RCS file: /cvs/docs/docs-common/bin/tidy-bowl,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- tidy-bowl	25 Oct 2005 20:30:24 -0000	1.3
+++ tidy-bowl	6 Nov 2005 08:51:27 -0000	1.4
@@ -45,9 +45,9 @@
 for fn in $@
 do
 	case "${fn}" in
-	*-[Ee][Nn].[Xx][Mm][Ll] )
+	*-de.xml | *-en.xml | *-fr-xml | *-it.xml )
 		# Make sure we can find the input file
-		# /bin/echo "$0: English XML file ${fn} prettyprinted."
+		# /bin/echo "$0: XML file ${fn} prettyprinted."
 		if [ ! -f "${fn}" ]; then
 			/bin/echo $0 "Cannot find '${fn}'"
 			exit 1
@@ -59,9 +59,9 @@
 			exit 1
 		fi
 		;;
-	*.[Xx][Mm][Ll] )
-		# A non-English XML file.  What to do, what to do?
-		# /bin/echo "$0: Non-English XML file ${fn} left unchanged."
+	*.xml )
+		# A non-Romance XML file.  What to do, what to do?
+		# /bin/echo "$0: Non-Romance XML file ${fn} left unchanged."
 		;;
 	* )
 		# Some other kind of file.  DO NOTHING!!!



From fedora-docs-commits at redhat.com  Sun Nov  6 09:06:05 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sun,  6 Nov 2005 04:06:05 -0500
Subject: release-notes splash-it.xml,1.1,1.2
Message-ID: <200511060906.jA696583011810@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11796

Modified Files:
	splash-it.xml 
Log Message:



Index: splash-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- splash-it.xml	4 Nov 2005 20:02:41 -0000	1.1
+++ splash-it.xml	6 Nov 2005 09:05:30 -0000	1.2
@@ -1,24 +1,24 @@
 <section id="sn-splash">
-  <title>Welcome to &FC; &LOCALVER;</title>
+  <title>Benvenuti in &FC; &LOCALVER;</title>
   <caution>
-    <title>Information Out-of-Date</title>
+    <title>Informazioni non aggiornate</title>
     <para>
-      The content in this section needs to be updated for &DISTRO;
+      Il contenuto in questa sezione deve essere aggiornato per &DISTRO;
       &DISTROVER;
     </para>
   </caution>
   <para>
-    &FC; is a completely free, user friendly, and secure general purpose
-    platform based on Linux.  The &FP; is an open source project that
-    pioneers leading edge technology and concepts sponsored by &RH; and
-    supported by the &FED; community.
+    &FC; ?? una piattaforma basata su Linux completamente gratutita, amichevole, sicura e
+    general purpose.  &FP; ?? un progetto open source che
+    esplora le ultime tecnologie e concetti sponsorizzato da &RH; e
+    supportato dalla comunit?? &FED;.
   </para>
   <tip>
-    <title>Latest Release Notes on the Web</title>
+    <title>Ultime Release Notes sul Web</title>
     <para>
-      These release notes may be updated.  Visit <ulink
+      Queste release notes devono essere aggiornate.  Visita <ulink
 	url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>
-      to view the latest release notes for &DISTRO; &DISTROVER;.
+      per vedere le ultimerelease notes per &DISTRO; &DISTROVER;.
     </para>
   </tip>
 
@@ -36,7 +36,7 @@
   </note>  
 -->
   <para>
-    Refer to these webpages to find out more information about &FED;:
+    Fa riferimento a queste pagine web per cercare maggiori informazioni su &FED;:
   </para>
   <itemizedlist>
 <!-- FIXME Return when the section is updated
@@ -48,24 +48,24 @@
 -->
     <listitem>
       <para>
-	<xref linkend="sn-intro"/> &mdash; Technical release notes
+	      <xref linkend="sn-intro"/> &mdash; Release notes tecniche
       </para>
     </listitem>
     <listitem>
       <para>
-	Help and Support (<ulink
+	Aiuto e supporto (<ulink
 	  url="http://fedora.redhat.com/participate/communicate/">http://fedora.redhat.com/participate/communicate/</ulink>) 
       </para>
     </listitem>
     <listitem>
       <para>
-	Participate in the &FP; (<ulink
+	Participa al &FP; (<ulink
 	  url="http://fedora.redhat.com/participate/">http://fedora.redhat.com/participate/</ulink>) 
       </para>
     </listitem>
     <listitem>
       <para>
-	About the &FP; (<ulink
+	Informazioni sul &FP; (<ulink
 	  url="http://fedora.redhat.com/about/">http://fedora.redhat.com/about/</ulink>)
       </para>
     </listitem>



From fedora-docs-commits at redhat.com  Sun Nov  6 09:46:22 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sun,  6 Nov 2005 04:46:22 -0500
Subject: release-notes xorg-it.xml,1.1,1.2
Message-ID: <200511060946.jA69kMuX015638@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15621

Modified Files:
	xorg-it.xml 
Log Message:



Index: xorg-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/xorg-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xorg-it.xml	4 Nov 2005 20:02:41 -0000	1.1
+++ xorg-it.xml	6 Nov 2005 09:46:14 -0000	1.2
@@ -1,26 +1,26 @@
 <section id="sn-xwindows">
-  <title>X Window System (Graphics)</title>
+  <title>Sistema X Window (Grafico)</title>
   <caution>
-    <title>Information Out-of-Date</title>
+    <title>Informazioni non aggiornate</title>
     <para>
-      The content in this section needs to be updated for &DISTRO;
+      Il contenuto di questa sezione deve essere aggiornato per &DISTRO;
       &DISTROVER;
     </para>
   </caution>
   <para>
-    This section contains information related to the X Window System
-    implementation provided with &DISTRO;.
+    Questa sezione contiene le informazioni relative all'implementazione del
+    sistema X Window fornito con &DISTRO;.
   </para>
   <section id="sn-xwindows-xorg">
     <title><filename>xorg-x11</filename></title>
     <para>
-      Users new to the X.org X11 implementation should take note of a
-      few differences between it and the XFree86.org X11 implementation
-      which shipped in previous &RH; and &FED; operating systems. In
-      particular, the names of some files have changed:
+      Gli utenti che sono nuovi all'implementazione di X.org X11 dovranno prendere nota di
+      poche differenze tra lui e l'implementazione XFree86.org X11
+      che veniva rilasciata nei precedenti sistemi operativi &RH; e &FED;. In
+      particolare, i nomi di alcuni files sono cambiati:
     </para>
     <para>
-      X Server Binary:
+      Binari X Server:
     </para>
     <itemizedlist>
       <listitem>
@@ -31,7 +31,7 @@
       </listitem>
     </itemizedlist>
     <para>
-      X Server Configuration File:
+      File di configurazione X Server:
     </para>
     <itemizedlist>
       <listitem>
@@ -43,7 +43,7 @@
       </listitem>
     </itemizedlist>
     <para>
-      X Server Log File:
+      File di log X Server:
     </para>
     <itemizedlist>
       <listitem>
@@ -56,67 +56,66 @@
       </listitem>
     </itemizedlist>
     <para>
-      When configuring or troubleshooting your X server
-      configuration, be sure that you are using the correct
-      files.
+      Quando configuri o risolvi le problematiche della configurazione
+      del tuo X server, sii sicuro di usare i files giusti.
     </para>
     <para>
-      There has been some confusion regarding font-related issues
-      under the X Window System in recent versions of &DISTRO; (and
-      versions of &RHL; before it.)  At the present time, there are two
-      font subsystems, each with different characteristics:
+      C'?? stata un po di confusione reguardante le problematiche inerenti i font
+      sotto il sistema X Window nelle recenti versioni di &DISTRO; (e
+      versioni di &RHL; prima di lui.)  Oggi, ci sono due
+      subsistemi di font, ciascuno con caratteristiche differenti:
     </para>
     <itemizedlist>
       <listitem>
-	<para>The original (15+ year old) subsystem is referred to as
-	  the <firstterm>core X font subsystem</firstterm>.  Fonts
-	  rendered by this subsystem are not anti-aliased, are handled
-	  by the X server, and have names such as:
+	<para>Il subsistema originale (vecchio pi?? di 15 anni) fa riferimento al
+	  <firstterm>sottosistema core X font</firstterm>.  I fonts
+	  renderizzati da questo sottosistema non sono anti-aliased, sono manipolati
+	  dall'X server, ed hanno nomi tipo:
 	  <computeroutput>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</computeroutput>
 	</para>
       </listitem>
       <listitem>
 	<para>
-	  The newer font subsystem is known as
-	  <firstterm>fontconfig</firstterm>, and allows applications
-	  direct access to the font files.  Fontconfig is often used
-	  along with the <filename>Xft</filename> library, which allows
-	  applications to render fontconfig fonts to the screen with
-	  antialiasing. Fontconfig uses more human-friendly names such
-	  as: <computeroutput>Luxi Sans-10</computeroutput>
+	  Il nuovo subsistema di font ?? conosciuto come
+	  <firstterm>fontconfig</firstterm>, e permette alle applicazioni
+	  accesso diretto ai files dei font.  Fontconfig ?? spesso usato
+	  insieme alla libreria <filename>Xft</filename>, che permette
+	  alle applicazioni di renderizzare le fonti fontconfig sullo schermo con
+	  l'antialiasing. Fontconfig usa dei nomi pi?? amichevoli per l'uomo tipo:
+	  <computeroutput>Luxi Sans-10</computeroutput>
 	</para>
       </listitem>
     </itemizedlist>
     <para>
-      Over time, fontconfig and <filename>Xft</filename> will replace
-      the core X font subsystem.  At the present time, applications
-      using the Qt 3 or GTK 2 toolkits (which would include KDE and
-      GNOME applications) use the fontconfig and Xft font subsystem;
-      almost everything else uses the core X fonts.
+      Nel tempo, fontconfig e <filename>Xft</filename> sostituiranno
+      il subsistema core X font.  Attualmente, le applicazioni
+      che usano i toolkits Qt 3 o GTK 2 (che includono le applicazioni KDE e
+      GNOME) usano il subsistema di font fontconfig ed Xft;
+      quasi tutto il resto usa il core X fonts.
     </para>
     <para>
-      In the future, &FC; may support only fontconfig/Xft in
-      place of the XFS font server as the default local font access
-      method.
+      Nel futuro, &FC; supporter?? solo fontconfig/Xft al
+      posto del XFS font server come impostazione predefinita come metodo per l'accesso
+      ai font locali.
     </para>
     <note>
-      <title>Note</title>
+      <title>Nota</title>
       <para>
-	An exception to the font subsystem usage outlined above is
-	OpenOffice.org, which uses its own font rendering technology.
+	Un eccezione al subsistema dei font delineato sopra ??
+	OpenOffice.org, che usa la propria tecnologia di font rendering.
       </para>
     </note>
     <para>
-      The steps to add new fonts to &DISTRO; &DISTROVER; depend on the
-      fonts subsystem this is going to use the new fonts.  For the core X
-      font subsystem:
+      I passi per aggiungere nuove fonti a &DISTRO; &DISTROVER; dipendono dal
+      subsistema che dovr?? usare le nuove fonti.  Per il subsistema core X
+      font:
     </para>
 
     <procedure>
       <step>
 	<para>
-	  Create the <filename>/usr/share/fonts/local/</filename>
-	  directory (if it doesn't already exist):
+	  Crea la directory <filename>/usr/share/fonts/local/</filename>
+	  (se non esiste gi??):
 	</para>
 <screen>
 <command>mkdir /usr/share/fonts/local/</command>
@@ -124,16 +123,16 @@
       </step>
       <step>
 	<para>
-	  Copy the new font file into
+	  Copia la nuova fonte in
 	  <filename>/usr/share/fonts/local/</filename>
 	</para>
       </step>
       <step>
 	<para>
-	  Update the font information by issuing the following commands
-	  (note that, due to formatting restrictions, the following
-	  commands may appear on more than one line; in use, each
-	  command should be entered on a single line):
+	  Aggiorna le informazioni dei font eseguendo i seguenti comandi
+	  (nota che, a causa delle restrizioni sulla formattazione, i seguenti
+	  comandi potrebbero sembrare apparire su pi?? di una linea; quando li usi, ciascun
+	  comando dovr?? essere inserito su una singola linea):
 	</para>
 <screen>
 <command>ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</command>
@@ -142,9 +141,9 @@
       </step>
       <step>
 	<para>
-	  If you had to create
-	  <filename>/usr/share/fonts/local/</filename>, you must then
-	  add it to the X font server (<command>xfs</command>) path:
+	  Se hai creato
+	  <filename>/usr/share/fonts/local/</filename>, dovrai quindi
+	  aggiungere il percorso all'X font server (<command>xfs</command>):
 	</para>
 <screen>
 <command>chkfontpath --add /usr/share/fonts/local/</command>
@@ -152,46 +151,46 @@
       </step>
     </procedure>
     <para>
-      Adding new fonts to the fontconfig font subsystem is more
-      straightforward; the new font file only needs to be copied into
-      the <filename>/usr/share/fonts/</filename> directory (individual
-      users can modify their personal font configuration by copying the
-      font file into the <filename>~/.fonts/</filename> directory).
+      Aggiungere nuove fonti al subsistema fontconfig ?? pi?? semplice;
+      le nuove fonti hanno necessit?? di essere copiate nella
+      directory <filename>/usr/share/fonts/</filename> (individualmente
+      gli utenti possono modificare la loro configurazione di fornti copiandole nella
+      directory <filename>~/.fonts/</filename>).
     </para>
     <para>
-      After the new font has been copied, use
-      <command>fc-cache</command> to update the font information cache:
+      Dopo che le nuove fonti sono state copiate, usa
+      <command>fc-cache</command> per aggiornare le informazioni della cache:
     </para>
 <screen>
 <command>fc-cache <replaceable>&lt;directory&gt;</replaceable></command>
 </screen>
     <para>
-      (Where
+      (Dove
       <command><replaceable>&lt;directory&gt;</replaceable></command>
-      would be either the <filename>/usr/share/fonts/</filename> or
-      <filename>~/.fonts/</filename> directories.)
+      potr?? essere sia la directory <filename>/usr/share/fonts/</filename> che
+      <filename>~/.fonts/</filename>.)
     </para>
     <para>
-      Individual users may also install fonts graphically, by browsing
+      Individualmente gli utenti potranno installare fonts graficamente, navigando
       <command>fonts:///</command> in
-      <application>Nautilus</application>, and dragging the new font
-      files there.
+      <application>Nautilus</application>, e trascinando i nuovi files di font
+      qui.
     </para>
     <note>
-      <title>Note</title>
+      <title>Nota</title>
       <para>
-	If the font filename ends with "<filename>.gz</filename>", it
-	has been compressed with <command>gzip</command>, and must be
-	decompressed (with the <command>gunzip</command> command) before
-	the fontconfig font subsystem can use the font.
+	Se il nome del file finisce con l'estensione "<filename>.gz</filename>", ??
+	stato compresso con <command>gzip</command>, e deve essere
+	decompresso (con il comando <command>gunzip</command>) prima
+	che il subsistema fontconfig possa usare il font.
       </para>
     </note>      
     <para>
-      Due to the transition to the new font system based on
-      fontconfig/Xft, GTK+ 1.2 applications are not affected by any
-      changes made via the <guilabel>Font Preferences</guilabel> dialog.
-      For these applications, a font can be configured by adding the
-      following lines to the file <filename>~/.gtkrc.mine</filename>:
+      A causa della transizione al nuovo sistema di font basato su
+      fontconfig/Xft, le applicazioni GTK+ 1.2 non possono beneficiare dei
+      cambiamenti fatti mediante la finestra di dialogo <guilabel>Font Preferences</guilabel>.
+      Per queste applicazioni, un font pu?? essere configurato aggiungendo le
+      seguenti linee al file <filename>~/.gtkrc.mine</filename>:
     </para>
 <screen>    
 <computeroutput>style "user-font" {
@@ -200,10 +199,10 @@
 widget_class "*" style "user-font"</computeroutput>
 </screen>
     <para>
-      (Where
+      (Dove
       <command><replaceable>&lt;font-specification&gt;</replaceable></command> 
-      represents a font specification in the style used by traditional X
-      applications, such as
+      rappresenta le specifiche della fonte nello stile usato dalle applicazioni X
+      tradizionali, tipo
       "<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>".)
     </para>
   </section>



From fedora-docs-commits at redhat.com  Sun Nov  6 12:53:15 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sun,  6 Nov 2005 07:53:15 -0500
Subject: release-notes README-it.xml,1.1,1.2
Message-ID: <200511061253.jA6CrFFI020961@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20944

Modified Files:
	README-it.xml 
Log Message:



Index: README-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/README-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README-it.xml	4 Nov 2005 20:02:41 -0000	1.1
+++ README-it.xml	6 Nov 2005 12:53:08 -0000	1.2
@@ -20,59 +20,59 @@
 
 <article id="index" lang="en" arch="x86;x86_64" os="test;final">
   <articleinfo>
-    <title>&DISTRO; &DISTROVER; README</title>
+    <title>LEGGIMI &DISTRO; &DISTROVER;</title>
     <copyright>
       <year>2005</year>
       <holder>&FORMAL-RHI;</holder>
     </copyright>
     <legalnotice id="legalnotice">
-      <para>The contents of this CD-ROM are Copyright &copy; 2005 &PROJ; and
-        others.  Refer to the End User License Agreement and individual
-        copyright notices in each source package for distribution terms.</para>
-
-      <para>&NAME;, &RH;, &RH; Network, the &RH; "Shadow Man" logo, RPM, Maximum
-        RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover,
-        RHmember, RHmember More, Rough Cuts, Rawhide and all &RH;-based
-        trademarks and logos are trademarks or registered trademarks of
-        &FORMAL-RHI; in the United States and other countries.</para>
+      <para>I contenuti di questo CD-ROM sono Copyright &copy; 2005 &PROJ; ed
+        altri.  Fa riferimento all'End User License Agreement ed alle note di
+        copyright individuali in ciascun pacchetto per le regole di distribuzione.</para>
+
+      <para>&NAME;, &RH;, &RH; Network, il logo &RH; "Shadow Man", RPM, Maximum
+        RPM, il logo RPM, Linux Library, PowerTools, Linux Undercover,
+        RHmember, RHmember More, Rough Cuts, Rawhide e tutti i marchi e loghi &RH;-based
+        sono marchi o marchi registrati di
+	&FORMAL-RHI; negli Stati Uniti e negli altri paesi.</para>
 
-      <para>Linux is a registered trademark of Linus Torvalds.</para>
+      <para>Linux ?? un marchio registrato di Linus Torvalds.</para>
 
-      <para>Motif and UNIX are registered trademarks of The Open Group.</para>
+      <para>Motif e UNIX sono registrati de The Open Group.</para>
 
-      <para>Intel and Pentium are registered trademarks of Intel
-        Corporation. Itanium and Celeron are trademarks of Intel
+      <para>Intel e Pentium sono marchi registrati della Intel
+        Corporation. Itanium e Celeron sono marchi della Intel
         Corporation.</para>
 
-      <para>AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of Advanced
+      <para>AMD, AMD Athlon, AMD Duron, ed AMD K6 sono marchi di Advanced
         Micro Devices, Inc.</para>
 
-      <para>Windows is a registered trademark of Microsoft Corporation.</para>
+      <para>Windows ?? un marchio registrato di Microsoft Corporation.</para>
 
-      <para>SSH and Secure Shell are trademarks of SSH Communications Security,
+      <para>SSH e Secure Shell sono marchi di SSH Communications Security,
         Inc.</para>
 
-      <para>FireWire is a trademark of Apple Computer Corporation.</para>
+      <para>FireWire un marchio di Apple Computer Corporation.</para>
 
-      <para>All other trademarks and copyrights referred to are the property of
-        their respective owners.</para>
+      <para>Tutti gli altri marchi e copyrights a cui si fa riferimento sono propriet??
+        dei rispettivi proprietari.</para>
 
-      <para>The GPG fingerprint of the <computeroutput>"Fedora Project
-        &lt;fedora at redhat.com&gt;"</computeroutput> key is:</para>
+      <para>La chiave GPG fingerprint del <computeroutput>"Fedora Project
+        &lt;fedora at redhat.com&gt;"</computeroutput> ??:</para>
 
       <para>CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2</para>
     </legalnotice>
   </articleinfo>
 
   <section id="dir-org">
-    <title>DIRECTORY ORGANIZATION</title>
+    <title>ORGANIZZAZIONE DELLE DIRECTORY</title>
 
-    <para>&DISTRO; is delivered on multiple CD-ROMs consisting of installation
-      CD-ROMs and source code CD-ROMs.</para>
+    <para>&DISTRO; ?? distribuita su CD-ROMs multipli che consistono in
+      CD-ROMs di installazione e CD-ROMs di codice sorgente.</para>
 
-    <para>The first installation CD-ROM can be directly booted into the
-      installation on most modern systems, and contains the following directory
-      structure (where <filename>/mnt/cdrom</filename> is the mount point of the
+    <para>Il primo CD-ROM pu?? avviare direttamente l'installazione
+      nella maggior parte dei sistemi moderni, e contiene la seguente struttura di
+      directory (dove <filename>/mnt/cdrom</filename> ?? il mount point del
       CD-ROM):</para>
 
     <screen arch="x86">
@@ -80,15 +80,15 @@
 <computeroutput>
 /mnt/cdrom
   |----> Fedora
-  |        |----> RPMS         -- binary packages
-  |        `----> base         -- information on this release of Fedora
-  |                               Core used by the installation process
-  |----> images                -- boot and driver disk images
-  |----> isolinux              -- files necessary to boot from CD-ROM
-  |----> README                -- this file
-  |----> RELEASE-NOTES         -- the latest information about this release
-  |                               of Fedora Core
-  `----> RPM-GPG-KEY           -- GPG signature for packages from Red Hat
+  |        |----> RPMS         -- pacchetti dei binary
+  |        `----> base         -- informazioni su questa release di Fedora
+  |                               Core usata nel processo d'installazione
+  |----> images                -- immagini di boot e dischi driver
+  |----> isolinux              -- files necessary all'avvio da CD-ROM
+  |----> README                -- questo file
+  |----> RELEASE-NOTES         -- Le ultime informazioni su questa release
+  |                               di Fedora Core
+  `----> RPM-GPG-KEY           -- Firma GPG per i pacchetti da Red Hat
 </computeroutput>
     </screen>
 <!-- repetitive for the moment
@@ -109,29 +109,28 @@
 </computeroutput>
   </screen>
     -->
-    <para>The remaining Installation CD-ROMs are similar to Installation CD-ROM
-      1, except that only the <filename>Fedora</filename> subdirectory is
-      present.</para>
+    <para>I rimanenti CD-ROMs d'installazione sono simili al CD 1, eccettuato il fatto
+	che ?? presente solo la subdirectory <filename>Fedora</filename>.</para>
 
-    <para>The directory layout of each source code CD-ROM is as follows:</para>
+    <para>Il layout delle directory per ogni CD-ROM dei sorgenti ?? il seguente:</para>
 
     <screen>
 <computeroutput>
 /mnt/cdrom
-  |----> SRPMS                 -- source packages
-  `----> RPM-GPG-KEY           -- GPG signature for packages from Red Hat
+  |----> SRPMS                 -- pacchetti sorgenti
+  `----> RPM-GPG-KEY           -- Firma GPG per i pacchetti da Red Hat
 </computeroutput>
     </screen>
 
-    <para>If you are setting up an installation tree for NFS, FTP, or HTTP
-      installations, you need to copy the <filename>RELEASE-NOTES</filename>
-      files and all files from the <filename>Fedora</filename> directory on
-      discs 1-3.  On Linux and Unix systems, the following process will properly
-      configure the /target/directory on your server (repeat for each disc):</para>
+    <para>Se stai impostando un albero di directory per l'installazione NFS, FTP, o HTTP,
+      devi copiare i files delle <filename>RELEASE-NOTES</filename> e tutti
+      i files della directory <filename>Fedora</filename> sui dischi
+      1-3.  Sui sistemi Linux e Unix, il seguente processo configura
+      in modo appropriato la /target/directory sul tuo server (ripetere per ogni disco):</para>
 
     <orderedlist>
       <listitem>
-        <para>Insert disc</para>
+        <para>Inserire il disco</para>
       </listitem>
 
       <listitem>
@@ -145,7 +144,7 @@
 
       <listitem>
         <para><command>cp /mnt/cdrom/RELEASE-NOTES* /target/directory</command>
-          (Do this only for disc 1)</para>
+          (Solo per il disco 1)</para>
       </listitem>
 
       <listitem>
@@ -155,60 +154,59 @@
   </section>
 
   <section id="installing">
-    <title>INSTALLING</title>
+    <title>INSTALLAZIONE</title>
 
-    <para>Many computers can now automatically boot from CD-ROMs. If you have
-      such a machine (and it is properly configured) you can boot the &DISTRO;
-      CD-ROM directly.  After booting, the &DISTRO; installation program will
-      start, and you will be able to install your system from the CD-ROM.</para>
-
-    <para arch="x86;x86_64"><!-- <remark os="test">(x86;x86_64)</remark> --> The
-      <filename>images/</filename> directory contains the file
-      <filename>boot.iso</filename>.  This file is an ISO image that can be used
-      to boot the &DISTRO; installation program.  It is a handy way to start
-      network-based installations without having to use multiple diskettes.  To
-      use <filename>boot.iso</filename>, your computer must be able to boot from
-      its CD-ROM drive, and its BIOS settings must be configured to do so.  You
-      must then burn <filename>boot.iso</filename> onto a recordable/rewriteable
-      CD-ROM.</para>
-
-    <para arch="x86;x86_64"><!-- <remark os="test">(x86;x86_64)</remark> --> Another image
-      file contained in the <filename>images/</filename> directory is
-      <filename>diskboot.img</filename>.  This file is designed for use with USB
-      pen drives (or other bootable media with a capacity larger than a diskette
-      drive).  Use the <command>dd</command> command to write the image.</para>
+    <para>Molti computers possono essere avviati automaticamente dai CD-ROMs. Se hai
+      una macchina di questo tipo (ed ?? configurata nel modo appropriato) puoi avviare il
+      CD-ROM di &DISTRO; direttamente.  Dopo l'avvio, il programma d'instalazione di &DISTRO;
+      sar?? eseguito, e sarai in grado di installare il tuo sistema dal CD-ROM.</para>
+
+    <para arch="x86;x86_64"><!-- <remark os="test">(x86;x86_64)</remark> --> La
+      directory <filename>images/</filename> contiene il file
+      <filename>boot.iso</filename>.  Questo file ?? un immagine ISO che pu?? essere usata
+      per avviare il programma d'installazione di &DISTRO;.  E' un modo agevole di avviare
+      installazioni network-based senza dover ricorrere a molteplici dischi.  Per
+      usare <filename>boot.iso</filename>, il tuo computer deve essere in grado di avviarsi dal
+      suo drive CD-ROM, e le sue impostazioni del BIOS devono essere configurate per farlo.  Devi
+      quindi masterizzare la <filename>boot.iso</filename> su un CD-ROM recordable/rewriteable.</para>
+
+    <para arch="x86;x86_64"><!-- <remark os="test">(x86;x86_64)</remark> --> Un'altro file
+      immagine contenuto nella directory <filename>images/</filename> ??
+      <filename>diskboot.img</filename>.  Questo file ?? disegnato per essere utilizzato con i
+      pen drives USB (o altri media avviabili con una capacit?? pi?? grande di un floppy disk),
+      Usa il comando <command>dd</command> per scrivere l'immagine.</para>
 
     <note arch="x86;x86_64">
 
-      <title>Note</title>
+      <title>Nota</title>
       <!-- <remark os="test">(x86;x86_64)</remark> -->
 
-      <para>The ability to use this image file with a USB pen drive depends on
-        the ability of your system's BIOS to boot from a USB device.</para>
+      <para>La capacit?? di usare questo file immagine con un pen drive USB dipende
+	dall'abilit?? del BIOS del tuo sistema di avviarsi da una periferica USB.</para>
         </note>
   </section>
 
   <section id="get-help">
-    <title>GETTING HELP</title>
+    <title>OTTENERE AIUTO</title>
 
-    <para>For those that have web access, see <ulink
+    <para>Coloro che hanno accesso al web, vedano <ulink
         url="http://fedora.redhat.com">http://fedora.redhat.com</ulink>.  In
-        particular, access to &PROJ; mailing lists can be found at:</para>
+        particolare, l'accesso alla mailing list di &PROJ; pu?? essere trovato su:</para>
 
     <para><ulink
     url="https://listman.redhat.com/mailman/listinfo/">https://listman.redhat.com/mailman/listinfo/</ulink></para>
   </section>
 
   <section id="export-ctl">
-    <title>EXPORT CONTROL</title>
+    <title>CONTROLLO SULL'ESPORTAZIONE</title>
 
-    <para>The communication or transfer of any information received with this
-      product may be subject to specific government export approval.  User shall
-      adhere to all applicable laws, regulations and rules relating to the
-      export or re-export of technical data or products to any proscribed
-      country listed in such applicable laws, regulations and rules unless
-      properly authorized.  The obligations under this paragraph shall survive
-      in perpetuity.</para>
+    <para>La comunicazione o trasferimento di qualsiasi informazione ricevuta con
+      questo prodotto potrebbe essere soggetta a specifica approvazione del governo.
+      Gli utenti dovrebbero aderire a tutte le leggi applicabili, regolamenti e regole
+      relative all'esportazione o riesportazione di dati tecnici e prodotti per ogni paese
+      proscritto in quel tipo di leggi, regolamenti e regole a meno di
+      essere opportunamente autorizzato.  Gli obblighi di questo paragrafo saranno validi
+      perpetuamente.</para>
   </section>
 <!--
   <section id="s1-test" os="test">



From fedora-docs-commits at redhat.com  Sun Nov  6 22:32:34 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sun,  6 Nov 2005 17:32:34 -0500
Subject: release-notes package-movement-it.xml,1.3,1.4
Message-ID: <200511062232.jA6MWYDq005143@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5126/release-notes

Modified Files:
	package-movement-it.xml 
Log Message:



Index: package-movement-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-movement-it.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- package-movement-it.xml	6 Nov 2005 01:23:15 -0000	1.3
+++ package-movement-it.xml	6 Nov 2005 22:32:25 -0000	1.4
@@ -1,5 +1,5 @@
 <section id="sn-package-movement">
-  <title>Packages Movement</title>
+  <title>Movimenti dei pacchetti</title>
   <!-- 
   FIXME
   Necessita dell'aggiornamento dell'intero contenuto di FC4.



From fedora-docs-commits at redhat.com  Wed Nov  9 21:17:53 2005
From: fedora-docs-commits at redhat.com (Elliot Lee (sopwith))
Date: Wed,  9 Nov 2005 16:17:53 -0500
Subject: owners owners.list,1.9,1.10
Message-ID: <200511092117.jA9LHr6c005115@cvs-int.fedora.redhat.com>

Author: sopwith

Update of /cvs/docs/owners
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5095

Modified Files:
	owners.list 
Log Message:
Send website bugs to the whole list


Index: owners.list
===================================================================
RCS file: /cvs/docs/owners/owners.list,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- owners.list	20 Oct 2005 20:00:45 -0000	1.9
+++ owners.list	9 Nov 2005 21:17:45 -0000	1.10
@@ -41,7 +41,7 @@
 # Content delivery and infrastructure components
 #
 
-Fedora Documentation|fedora-websites|Problems and requests for all formal Fedora Project websites.  This list is currently: fedoraproject.org and fedora.redhat.com.|nman64 at n-man.com|kwade at redhat.com|
+Fedora Documentation|fedora-websites|Problems and requests for all formal Fedora Project websites.  This list is currently: fedoraproject.org and fedora.redhat.com.|webmaster at fedora.redhat.com|kwade at redhat.com|
 
 #
 # Specific FDP document components



From fedora-docs-commits at redhat.com  Wed Nov  9 23:42:05 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Wed,  9 Nov 2005 18:42:05 -0500
Subject: mirror-tutorial mirror-tutorial-en.xml,1.14,1.15
Message-ID: <200511092342.jA9Ng5Rd009050@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9033

Modified Files:
	mirror-tutorial-en.xml 
Log Message:
Added security information from Stuart Ellis (#169584) with trivial edits


Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- mirror-tutorial-en.xml	17 Oct 2005 02:23:08 -0000	1.14
+++ mirror-tutorial-en.xml	9 Nov 2005 23:41:58 -0000	1.15
@@ -6,8 +6,8 @@
 %FEDORA-ENTITIES-EN;
 
 <!ENTITY BOOKNAME "mirror-tutorial">
-<!ENTITY BOOKVERSION "0.34">
-<!ENTITY BOOKDATE "2005-10-16">
+<!ENTITY BOOKVERSION "0.35">
+<!ENTITY BOOKDATE "2005-11-09">
 <!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)"> <!-- change version of manual and date here -->
 
 <!ENTITY BUG-NUM "130125">
@@ -182,6 +182,16 @@
 	  </para>
 	</revdescription>
       </revision>
+      <revision>
+	<revnumber>0.35</revnumber>
+	<date>2005-11-09</date>
+	<authorinitials>PaulWFrields</authorinitials>
+	<revdescription>
+	  <para>
+	    Added some security info and fixes (#169584).
+	  </para>
+	</revdescription>
+      </revision>
     </revhistory>
   </articleinfo>
 
@@ -267,7 +277,8 @@
       <title>Acknowledgements</title>
       <para>
 	Karsten Wade provided editorial services and kept the style
-	crisp and consistent.
+	crisp and consistent.  Stuart Ellis provided some additional
+	security-related information.
       </para>
     </section>
   </section>
@@ -993,82 +1004,159 @@
     <title>Server Configuration</title>
 
     <para>
-      This section gives guidance on setting up a HTTP (Web) server that
-      provides installation and update mirror services.
+      This section describes how to set up a HTTP (Web) server to
+      support &FED; installation and software management applications.
     </para>
 
-    <section id="sn-setting-up-apache">
-      <title>Setting Up Apache</title>
+    <section id="sn-installing-apache">
+      <title>Installing The Apache Web Server</title>
+      <para>
+        &FC; provides the Apache server in the
+        <filename>httpd</filename> package.  The
+        <filename>httpd</filename> package is included on &FED; systems
+        installed with the <guilabel>Server</guilabel> installation
+        type.  You may have installed it later in order to run websites
+        or Web applications. &FEX; also offers alternative HTTP servers,
+        which are beyond the scope of this document.
+      </para>
+      <para>
+        To install the <filename>httpd</filename> package, if you have
+        not already done so, use the following command:
+      </para>
+
+<screen>
+<userinput>su -c 'yum install httpd'</userinput>
+</screen>
 
       <para>
-	The HTTP service, provided by the Apache server in the
-	<filename>httpd</filename> package, is the easiest service to
-	configure.  You can also use Apache to offer post-installation
-	functions such as updates or installing additional packages.  To
-	install the <filename>httpd</filename> package, if you have not
-	already done so, use the following command:
+        Enter the password for the
+        <systemitem class="username">root</systemitem> account when
+        prompted.
+      </para>
+      <para>
+        To start the service, use the following command:
       </para>
 
 <screen>
-<userinput>su - -c "yum install httpd"</userinput>
+<userinput>su -c '/sbin/service httpd start'</userinput>
 </screen>
 
       <para>
-	Next, create a configuration file
-	<filename>/etc/httpd/conf.d/mirror.conf</filename> for your
-	mirror files.  The following listing is an example:
+        Enter the password for the
+        <systemitem class="username">root</systemitem> account when
+        prompted.
+      </para>
+      <para>
+        To enable this service to load automatically at boot time, use
+        the following command:
       </para>
 
-      <example>
-	<title>Apache 2.x configuration file for installation
-	  mirror</title>
+<screen>
+<userinput>su -c '/sbin/chkconfig --level 345 httpd on'</userinput>
+</screen>
+
+      <para>
+        Enter the password for the
+        <systemitem class="username">root</systemitem> account when
+        prompted.
+      </para>
+      <para>
+        The default firewall configuration for &FED; blocks access from
+        remote systems. To enable other systems to connect to your HTTP
+        service, use the
+        <application>system-config-securitylevel</application> utility:
+      </para>
+      <procedure>
+        <step>
+          <para>
+            Choose <menuchoice> <guimenu>Desktop</guimenu>
+            <guisubmenu>System Settings</guisubmenu>
+            <guimenuitem>Security Level</guimenuitem> </menuchoice>.
+          </para>
+        </step>
+        <step>
+          <para>
+            Enter the password for the
+            <systemitem class="username">root</systemitem> account when
+            prompted.
+          </para>
+        </step>
+        <step>
+          <para>
+            Select <guilabel>WWW (HTTP)</guilabel> from the list of
+            services.
+          </para>
+        </step>
+        <step>
+          <para>
+            When prompted, select <guilabel>Yes</guilabel> to update the
+            firewall configuration.
+          </para>
+        </step>
+      </procedure>
+    </section>
+    <section id="sn-configuring-apache">
+      <title>Configuring The Apache Web Server</title>
+      <para>
+        To enable HTTP access to the files in your mirror directory,
+        create the configuration file
+        <filename>/etc/httpd/conf.d/mirror.conf</filename>. The
+        following listing is an example:
+       </para>
+       <example>
+        <title>Apache 2.x configuration file for &FED; mirror</title>
 
 <screen>
-<computeroutput><![CDATA[# The name at which the installation tree will be shared, 
+<computeroutput><![CDATA[# The name at which the mirror will be shared, 
 # followed by the name of the root directory of that tree.
 Alias /mirror /var/www/mirror
 
-# Share options for the installation tree. 
+# Share options for the mirror. 
 # Only allow connections from localhost and 
 # IP addresses which start with 192.168.1
-
-<Directory /var/www/mirror>
-   AllowOverride None 
-   Order Deny,Allow 
-   Deny from all 
-   Allow from 127.0.0.1 192.168.1
-   Options Indexes
-</Directory>]]></computeroutput>
+    <Directory /var/www/mirror>
+      AllowOverride None
+      Order Deny,Allow
+      Deny from all
+      Allow from 127.0.0.1 192.168.1
+      Options Indexes
+    </Directory>]]></computeroutput>
 </screen>
 
       </example>
-
       <para>
-	To start the <command>httpd</command> service, use the following
-	command:
+        You must use root privileges to create or copy files in the
+        directory <filename>/etc/httpd/conf.d/</filename>.
       </para>
-
-<screen>
-<userinput>/sbin/service httpd start</userinput>
-</screen>
-
       <para>
-	To enable that server by default at boot time, use the following
-	command:
+        To update an active <command>httpd</command> service with a new
+        configuration, use the following command:
       </para>
 
 <screen>
-<userinput>chkconfig httpd on</userinput>
+<userinput>/sbin/service httpd reload</userinput>
 </screen>
 
       <para>
-	Your clients may now visit any area of your mirror by using the
-	URL
-	http://<replaceable>server.mydomain.org</replaceable>/mirror/<replaceable>path</replaceable>.
+        Enter the password for the
+        <systemitem class="username">root</systemitem> account when
+        prompted.
       </para>
-
-    </section>
-
+      <para>
+         Your clients may now visit any area of your mirror by using the
+         URL
+         http://<replaceable>server.mydomain.org</replaceable>/mirror/<replaceable>path</replaceable>.
+       </para>
+      <note>
+        <title>Apache and &SEL;</title>
+        <para>
+          The default &SEL; configuration for &FED; permits Apache to
+          use files in the <filename>/var/www/</filename> directory. If
+          you build your mirror in another directory, you may need to
+          modify the &SEL; policy.
+        </para>
+      </note>
+     </section>
     <section id="sn-solving-dependencies">
       <title>Solving Dependencies</title>
       <para>
@@ -1097,7 +1185,7 @@
       <para>
       The Yellow Dog Updater Modified, or
 	<emphasis>yum</emphasis><indexterm> <primary>yum</primary>
-      </indexterm>, is a Python-based system for computing and solving
+	</indexterm>, is a Python-based system for computing and solving
 	RPM dependencies. A <command>yum</command> client retrieves a
 	cache of headers from its repository server, as well as a list
 	of available RPM packages and their exact locations on the
@@ -1246,7 +1334,7 @@
 	  <listitem>
 	    <para>
 	      Official updates to the distribution; for example,
-	      <filename>/var/mirror/fedora/linux/core/updates/&FCVER;/</filename>. 
+	      <filename>/var/www/mirror/fedora/linux/core/updates/&FCVER;/</filename>. 
 	      Once again, for <command>yum-arch</command> use
 	      <command>-l</command> and/or <command>-s</command> if
 	      appropriate.



From fedora-docs-commits at redhat.com  Wed Nov  9 23:42:37 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Wed,  9 Nov 2005 18:42:37 -0500
Subject: docs-common/bin xmlformat-fdp.conf,1.6,1.7
Message-ID: <200511092342.jA9NgbMJ009073@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9056

Modified Files:
	xmlformat-fdp.conf 
Log Message:
Make indexterm a little less ugly


Index: xmlformat-fdp.conf
===================================================================
RCS file: /cvs/docs/docs-common/bin/xmlformat-fdp.conf,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- xmlformat-fdp.conf	11 Oct 2005 22:23:36 -0000	1.6
+++ xmlformat-fdp.conf	9 Nov 2005 23:42:29 -0000	1.7
@@ -75,7 +75,7 @@
   normalize = yes
 
 indexterm
-  format = block
+  format = inline
   normalize = no
 
 primary secondary



From fedora-docs-commits at redhat.com  Thu Nov 10 21:21:16 2005
From: fedora-docs-commits at redhat.com (Andrew Martynov (andrmart))
Date: Thu, 10 Nov 2005 16:21:16 -0500
Subject: release-notes daemons-ru.xml, NONE, 1.1 database-servers-ru.xml,
	NONE, 1.1 desktop-ru.xml, NONE, 1.1 development-tools-ru.xml,
	NONE, 1.1 entertainment-ru.xml, NONE, 1.1 feedback-ru.xml,
	NONE, 1.1 file-servers-ru.xml, NONE, 1.1 file-systems-ru.xml,
	NONE, 1.1 hardware-reqs-ru.xml, NONE, 1.1 i18n-ru.xml, NONE,
	1.1 install-notes-ru.xml, NONE, 1.1 intro-ru.xml, NONE,
	1.1 java-package-ru.xml, NONE, 1.1 kernel-ru.xml, NONE,
	1.1 legacynotice-ru.xml, NONE, 1.1 legacy-ru.xml, NONE,
	1.1 legalnotice-content-ru.xml, NONE,
	1.1 legalnotice-relnotes-ru.xml, NONE,
	1.1 legalnotice-section-ru.xml, NONE, 1.1 misc-server-ru.xml,
	NONE, 1.1 multimedia-ru.xml, NONE, 1.1 networking-ru.xml, NONE,
	1.1 overview-ru.xml, NONE, 1.1 package-movement-ru.xml, NONE,
	1.1 package-notes-ru.xml, NONE, 1.1 printing-ru.xml, NONE,
	1.1 project-overview-ru.xml, NONE, 1.1 RELEASE-NOTES-ru.xml,
	NONE, 1.1 samba-ru.xml, NONE, 1.1 security-ru.xml, NONE,
	1.1 server-tools-ru.xml, NONE, 1.1 splash-ru.xml, NONE,
	1.1 web-servers-ru.xml, NONE, 1.1 xorg-ru.xml, NONE, 1.1
Message-ID: <200511102121.jAALLG4s020200@cvs-int.fedora.redhat.com>

Author: andrmart

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20150

Added Files:
	daemons-ru.xml database-servers-ru.xml desktop-ru.xml 
	development-tools-ru.xml entertainment-ru.xml feedback-ru.xml 
	file-servers-ru.xml file-systems-ru.xml hardware-reqs-ru.xml 
	i18n-ru.xml install-notes-ru.xml intro-ru.xml 
	java-package-ru.xml kernel-ru.xml legacynotice-ru.xml 
	legacy-ru.xml legalnotice-content-ru.xml 
	legalnotice-relnotes-ru.xml legalnotice-section-ru.xml 
	misc-server-ru.xml multimedia-ru.xml networking-ru.xml 
	overview-ru.xml package-movement-ru.xml package-notes-ru.xml 
	printing-ru.xml project-overview-ru.xml RELEASE-NOTES-ru.xml 
	samba-ru.xml security-ru.xml server-tools-ru.xml splash-ru.xml 
	web-servers-ru.xml xorg-ru.xml 
Log Message:
First translation based on FC4 Russian Release Notes made by Inventa


--- NEW FILE daemons-ru.xml ---
<section id="sn-daemons">
  <title
>System Services</title>
  <caution>
    <title
>Information Out-of-Date</title>
    <para
>The content in this section needs to be updated for &DISTRO; &DISTROVER; </para>
  </caution>
  <section id="sn-daemons-updatedb">
    <title
><filename
>cron</filename
> and <filename
>slocate</filename
></title>
    <para
>The <command
>updatedb</command
> utility is no longer automatically run by <command
>cron</command
> to create and update the database of files used by <command
>slocate</command
>. Updating this database is an intensive process that users of workstations and laptops may find disruptive. </para>
    <para
>To enable daily updates of the <command
>slocate</command
> database, edit the file <filename
>/etc/updatedb.conf</filename
> as follows: </para>
     
    <screen
>DAILY_UPDATE=yes
    </screen>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->
    


--- NEW FILE database-servers-ru.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE desktop-ru.xml ---
<section id="sn-desktop">
  <title
>Desktop</title>
  <itemizedlist>
    <title
>Notes</title>
    <listitem>
      <para
>GNOME 2.12 and KDE 3.4.2 Major highlight
      </para>
    </listitem>
    <listitem>
      <para
>The current test release has GNOME 2.12.1, together with
	some previews of technology from the forthcoming GNOME 2.14:
      </para>
      <itemizedlist>
        <listitem>
          <para
>gnome-power-manager: brings the Hardware Abstraction
	    Layer to the world of laptop batteries and UPS units - these
	    things should "Just Work", with a simple UI  (naturally, in
	    a test release, they might not)
	  </para>
        </listitem>
        <listitem>
          <para
>gnome-screensaver: giving a fresh UI to screensavers and
	    the <guilabel
>Lock Screen</guilabel
> dialog
	  </para>
        </listitem>
        <listitem>
          <para
>Memory optimizations in the fontconfig and
	    shared-mime-info packages (these now use shared
	    memory-mapped caches for this data).  Both of these caches
	    are still somewhat experimental.
	  </para>
        </listitem>
      </itemizedlist>
    </listitem>
  <para>
    Test feedback on these experimental packages is especially
    appreciated.
  </para>
  <para>
    GNOME 2.12 has removed the terminal option from the desktop root
    menu. nautilus-open-terminal in Fedora Extras repository provides a
    enhanced replacement. It is also mentioned in the GNOME 2.12 release
    notes itself but we might highlight it since the package is provided
    with the extras repository.
  </para>
  <para>
    Screensavers not installed by default anymore. Should explain why
    and provide commands to install them.
  </para>
  <para
>MCS SELinux is in rawhide. Major highlight
    (<emphasis
>tentative</emphasis
> - not sure about classification of
    this change)
  </para>
  <caution>
    <title
>OpenOffice and upgrading from test releases</title>
    <para>
      If you choose to go counter to the recommendation to <emphasis
	role='strong'
>not</emphasis
> upgrade from a previous test
      release, you may encounter a problem with <ulink
	url='/OpenOffice'
>OpenOffice</ulink
> following the upgrade.
    </para>
    <para>
      To resolve this, you must do the following command <emphasis
	role='strong'
>before</emphasis
> doing the upgrade:
    </para>
<screen
>
<command>rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
</screen>
  </caution>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE development-tools-ru.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "This header makes editing XML easier">
 <!ENTITY DISTRO      "DISTRO">
 <!ENTITY DISTROVER   "DISTROVER">

]>
-->
<!-- Content commented out, no update performed by beat writer yet.
<section id="sn-devel">
  <title>
    Development Tools
  </title>
  <section id="sn-devel-gcc">
    <title
>GCC Compiler Collection</title>
    <para>
      &DISTRO; &DISTROVER; has been built using  <abbrev
>GCC</abbrev>
      4.0, which is included with the distribution.
    </para>
    <itemizedlist>
      <title
>Caveats</title>
      <listitem>
        <para>
          <abbrev
>GDB</abbrev
> 6.1 or newer is needed to debug binaries
	  unless compiled using the <parameter
	    class="option"
>-fno-var-tracking</parameter
> compilation
	  option.
        </para>
      </listitem>
      <listitem>
        <para>
          The <parameter class="option"
>-fwritable-strings</parameter>
	  option is no longer accepted.
        </para>
      </listitem>
      <listitem>
        <para>
          English-language diagnostic messages now use Unicode quotes;
	  if you cannot read this, set your <envar
>LC_CTYPE</envar>
	  environment variable to &quot;<filename
>C</filename
>&quot; or
	  change your terminal emulator.
        </para>
      </listitem>
      <listitem>
        <para>
          The <filename
>specs</filename
> file is no longer installed on
	  most systems. Ordinary users will not notice, but developers
	  who need to alter the file can use the <parameter
	    class="option"
>-dumpspecs</parameter
> option to generate the
	  file for editing.
        </para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title
>Code Generation</title>
      <listitem>
        <para>
          The <abbrev
>SSA</abbrev
> code optimizer is now included and
	  brings with it better constant propagation, partial redundancy
	  elimination, load and store code motion, strength reduction,
	  dead storage elimination, better detection of unreachable
	  code, and tail recursion by accumulation.
        </para>
      </listitem>
      <listitem>
        <para>
          Autovectorization is supported. This technique achieves higher
	  performance for repetitive loop code, in some circumstances.
        </para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title
>Language Extentions</title>
      <listitem>
        <para>
          A <computeroutput
>sentinel</computeroutput
> attribute has been
	  added so that the compiler will now issue a warning if a
	  function such as <function
>execl(char *path, const char *arg,
	    ...)</function
>, which requires a <literal
>NULL</literal>
	  list terminator is missing the <literal
>NULL</literal
>.
        </para>
      </listitem>
      <listitem>
        <para>
          The <wordasword
>cast-as-lvalue</wordasword
>,
	  <wordasword
>conditional-expression-as-lvalue</wordasword
>, and
	  <wordasword
>compund-expression-as-lvalue</wordasword>
	  extentions have been removed.
        </para>
      </listitem>
      <listitem>
        <para>
          The <computeroutput
>#pragma pack()</computeroutput
> semantics
	  have been brought closer to those used by other compilers.
        </para>
      </listitem>
      <listitem>
        <para>
          Taking the address of a variable declared with the
	  <computeroutput
>register</computeroutput
> modifier now
	  generates an error instead of a warning.
        </para>
      </listitem>
      <listitem>
        <para>
          Arrays of incomplete element types now generate an error. This
	  implies no forward reference to structure definitions.
        </para>
      </listitem>
      <listitem>
        <para>
          The basic compiler, without any optimization (<parameter
	    class="option"
>-O0</parameter
>), has been measured as much
	  as 25% faster in real-world code.
        </para>
      </listitem>
      <listitem>
        <para>
          Libraries may now contain function-scope static variables in
	  multi-threaded programs. The <parameter
	    class="option"
>-fno-threadsafe-statics</parameter
> can be
	  used by embedded developers to turn off this feature, but
	  ordinary users should never do this.
        </para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title
>Java</title>
      <listitem>
	<para>
          To avoid naming conflicts: <filename
>rmic</filename
> is now
	  <filename
>grmic</filename
>; <filename
>rmiregistry</filename>
	  is now <filename
>grmiregistry</filename
>; and
	  <filename
>jar</filename
> is now <filename
>fastjar</filename
>.
        </para>
      </listitem>
      <listitem>
	<para>
	  The <application
>GCJ</application
> compiler can now be used as
	  a just-in-time (<abbrev
>JIT</abbrev
>) tool by using the
	  <filename
>gnu.jit</filename
> facilities.
	</para>
      </listitem>
      <listitem>
	<para>
	  More support of the <abbrev
>AWT</abbrev
> and
	  <abbrev
>SWING</abbrev
> packages have been added.
	</para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title
>FORTRAN</title>
      <listitem>
	<para>
	  The <abbrev
>GNU</abbrev
> <application
>FORTRAN 77</application>
	  front end has been replaced by a new <application
>FORTRAN
	    90/95</application
> recognizer.
	</para>
      </listitem>
    </itemizedlist>
    <itemizedlist>
      <title
>Eclipse Development Environment</title>
      <listitem>
	<para>
	  Eclipse 3.1M6 has been compiled as a native application.
	</para>
      </listitem>
      <listitem>
	<para>
	  The C Development Tool (<abbrev
>CDT</abbrev
>) has been
	  included.
	</para>
      </listitem>
    </itemizedlist>
  </section>
</section>
-->

<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE entertainment-ru.xml ---
<section id="sn-entertainment">
  <title
>???????? ?? ??????????????????????</title>
  <para
>&FC; and &FEX; provide a selection of games that cover a variety of genres. By default, &FC;includes a small package of games for GNOME (called <filename
>gnome-games</filename
>). For a list of other games that are available for installation through <command
>yum</command
>, open a terminal and enter the following command: </para>
<screen
><command>yum groupinfo "Games and Entertainment"</command>
</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://fedora.redhat.com/docs/yum/"
>http://fedora.redhat.com/docs/yum/</ulink>
    </para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE feedback-ru.xml ---
  <section id="sn-test" os="test">
    <title
>Release Notes Feedback Procedure</title>

    <para
>(This section will disappear when the final &DISTRO; release is created.)</para>

    <para
>If you feel that these release notes could be improved in some way, you can provide feedback directly to the author. If you see a URL in the release notes that looks like this:</para>

    <para
>%%% https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=<replaceable
>&lt;bug-number&gt;</replaceable
> %%% </para>

    <para
>You can click on the URL and submit feedback on that particular section of the release notes. Your feedback will be added as a comment to an existing bug report.</para>

    <para
>If the section of the release notes that you have feedback for does not have one of these URLs (or you are submitting a request for entirely new content), you can click on the following link (this only works for the HTML version, of course &mdash; the URL is much too long to include in the text):</para>

    <para
><ulink
    url="https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Core&amp;op_sys=Linux&amp;version=devel&amp;component=fedora-release&amp;component_text=&amp;rep_platform=All&amp;priority=normal&amp;bug_severity=normal&amp;bug_status=NEW&amp;assigned_to=&amp;cc=&amp;estimated_time=0.0&amp;bug_file_loc=http%3A%2F%2F&amp;short_desc=FC3%20release%20notes%20--%20&amp;comment=Please%20add%20a%20descriptive%20phrase%20to%20the%20summary%2C%20and%20more%20in-depth%0D%0Adescription%20here%20%28be%20sure%20to%20note%20any%20arch-specific%20issues%29%3A%0D%0A%0D%0A&amp;keywords=&amp;dependson=&amp;blocked=114398&amp;maketemplate=Remember%20values%20as%20bookmarkable%20template&amp;form_name=enter_bug"
>Click here to submit new release notes feedback</ulink
></para>

    <para
>If you would like to review the changes that have been already submitted for this document, use the following link:</para>

    <para
><ulink
    url="http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398"
>http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398</ulink
></para>

    <para
>As bugs are posted for the various parts of the release notes, subsequent test versions of these release notes will contain links similar to the one described earlier.</para>

    <para
>Thank you (in advance) for your feedback!</para>

  </section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE file-servers-ru.xml ---
<section id="sn-file-servers">
  <title
>File Servers</title>
  <caution>
    <title
>Information Out-of-Date</title>
    <para
>The content in this section needs to be updated for &DISTRO; &DISTROVER; </para>
  </caution>
  <para
>This section refers to file transfer and sharing servers. Please refer to the &WEB-SERVERS; and &SAMBA; sections for information on HTTP (Web) file transfer and Samba (Windows) file sharing. </para>
  <section id="sn-file-servers-netatalk-suite">
    <title
>Netatalk (Macintosh Compatibility)</title>
    <para
>This section contains information related to Netatalk, a suite of software that enables Linux to interact with Macintosh systems using the AppleTalk network protocols. </para>
    <section id="sn-file-servers-netatalk-package">
      <title
><filename
>netatalk</filename
></title>
      <para
>&DISTRO; &DISTROVER; includes version 2 of Netatalk. <emphasis
>Upgrading from Netatalk version 1 to version 2 may result in data loss</emphasis
>. Version 2 of Netatalk uses a different method to store file resource forks from the previous version, and may require a different file name encoding scheme. Please read the documentation and plan your migration before upgrading. </para>
      <para
>Upgrade information is available directly from the Netatalk site: </para>
      <para>
	<ulink
	  url="http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html"
>http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html</ulink>
      </para>
      <para
>The documentation is also included in the <filename
>netatalk</filename
> package. Refer to either <filename
>/usr/share/doc/netatalk-<replaceable
>version</replaceable
>/doc/htmldocs/upgrade.html</filename
>, or <filename
>/usr/share/doc/netatalk-<replaceable
>version</replaceable
>/doc/Netatalk-Manual.pdf</filename
> (numbered page 25, document page 33). </para>
    </section>
  </section>
</section>

<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE file-systems-ru.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE hardware-reqs-ru.xml ---
<section id="sn-hardware-reqs">
  <title
>???????????????????? ?? ????????????????????????</title>
  <para
> ?????????????????? ???????????????????? ???????????????????? ?????????????????????? ???????????????????? ?? ????????????????????????, ???????????????????????? ?????? ???????????????? ?????????????????? &DISTRO; &DISTROVER;. </para>
  <note>
    <title
>??????????????????</title>
    <para
>?????? ?????????????????? ?????????????????? ?????????????????? ??/?????? ?????????????????????????? ?????????? ?????????????????? ?????????? ???????? ???????????????????? ??????????????????????????/?????????????? ???????????? ???????????????????? ???????????????????????? (?? ??????????????????, ?????????? ?? ?????????????? ????????). </para>
  </note>
<!-- Something like this needs to be said, but this really needs a -->
<!-- better treatment and probably a new section devoted to help resources.
  <para>
    This section does not address hardware compatability.  To find out
    about using a specific piece of hardware with &FC; &LOCALVER; 
  </para>
-->
  <section>
    <title
>???????????????????? ?? ????????????????????</title>

    <para
>?? ???????? ?????????????? ?????????????????? ???????????????????????? ??????????????????????, ?????????????????????? ?????? ???????????? &DISTRO; &DISTROVER;.</para>

    <note arch="x86">
      <title
>??????????????????</title>

      <para
>?????????????????? ???????????????????????? ?????????????????????? ???????????????????? ?? ???????????????? ?????????????????????? Intel. ???????????? ???????????????????? (?? ??????????????????, ???????????????????????? ???????????????????? AMD, Cyrix ?? VIA), ?????????????????????? ?? ?????????????????????????? ?????????????????? ?????????????????????? Intel, ?????????? ?????????? ???????????????????????????? ?? &DISTRO;.</para>
    </note>

    <itemizedlist arch="x86">
      <listitem>
	<para
>??????????????: ?????????? Pentium &mdash; &FC; &LOCALVER; ???????????????????????????? ?????? ?????????????????????? Pentium 4, ???? ???????????????????????? ?? ???????????? ???????????????????? (?????????? ???????????? Pentium, Pentium Pro, Pentium II, Pentium III, ?? ?????????? ?????????????? AMD ?? VIA). ?????? ???????? ?????????????? ????-???? ????????, ?????? ?????????????????????? ?????? ?????????????????????? ???????????? Pentium ???????????????????????? ???????????? ???? ???????????????????????????????????? ?????????????????????? ?????????????? ????????????, ?? ?????????????????????? Pentium 4 ?????????????????????? ???????????????????? (?? ???????? ???? ?????????????? ?????? ?????????? ???????????????? ????????????????????), ?????? ?? ?????????????????????? ?????? ??????????????????. </para>
      </listitem>

      <listitem>
	<para
>?????????????????????????? ?????? ???????????????????? ????????????: ?????????????????? 200 ?????? ???????????? Pentium ?????? ??????????</para>
      </listitem>

      <listitem>
	<para
>?????????????????????????? ?????? ??????????????: ?????????????????? 400 ?????? ???????????? Pentium II ?????? ??????????</para>
      </listitem>
    </itemizedlist>

    <itemizedlist arch="x86_64">
      <listitem>
	<para
>???????????????????? AMD64 (?? Athlon64, ?? Opteron)</para>
      </listitem>

      <listitem>
	<para
> ???????????????????? Intel ?? ???????????????????? ???????????????????? ?????????????????????? ???????????? <trademark class="registered"
>Intel</trademark
> Extended Memory 64 Technology (<trademark class="registered"
>Intel</trademark
> EM64T)</para>
      </listitem>
    </itemizedlist>
  </section>
  <section>
    <title
>???????????????????? ?? ???????????????????????? ???? ?????????????? ??????????</title>

    <para
>?? ???????? ?????????????? ???????????????????????? ???????????????????????? ???? ?????????????? ??????????, ?????????????????????? ?????? ?????????????????? &DISTRO; &DISTROVER;.</para>

    <note>
      <title
>??????????????????</title>

      <para
>?? ?????????????????????????? ???????? ?????????????????????? ?? ?????????????????? ???????????????????????? ?????????????????????? ????????????, ???????????????????? ???????????????? &DISTRO; &DISTROVER; <emphasis
>??????????</emphasis
> ???????????????????? ??????????????????. ???????????? ?????? ???????????? ?????????? ?????????????????? ?????????????????? ???????????????????? ???????????????????????????? ???????????????? ????????????????????????. ???????????? ?????????? ???????????????????????? ?????????????????????????? ?????????????? ?????????? <filename
>/Fedora/base/stage2.img</filename
> (???? CD-ROM 1) ???????? ???????????? ???????????? ?? ???????????????? <filename
>/var/lib/rpm</filename
> ?? ?????????????????????????? ??????????????.</para>

        <!-- Update these figures every release -->
      <para
>?? ???????????????? ?????????????????? ?????? ????????????????, ?????? ?????? ?????????????????????? ?????????????????? ?????????? ?????????????????????????? ?????????????????????????? 90 ??????????, ?? ?????? ???????????? ?????????????????? ??? ?????????????????????????? 175 ??????????.</para>

      <para
>??????????, ???? ?????????????????? ?? ??????, ?????? ???????????? ???????????????????????? ???????? ???????????????? ?????????? ???? ??????????, ???????????? ?????????? ?????? ???????????????????? ???????????? ?????????????? ???????????? ???????? ???????????????? ?????? ?????????????? 5% ?????????????????? ????????????????????????.</para>
    </note>

      <!-- Get actual numbers from installer, multiply by 1.1, and round -->
      <!-- up to the nearest 10MB or .1GB -->
    <para
>???????????????????? ?? 32-???????????? ???????????????? x86: </para>
    <itemizedlist arch="x86">
      <listitem>
	<para
>???????????????????? ?????????????????? (??????????????????????): 620 ??????????</para>
      </listitem>

      <listitem>
	<para
>????????????: 1,1 ??????????</para>
      </listitem>

      <listitem>
	<para
>???????????????????????? ??????????????????: 2,3 ??????????</para>
      </listitem>

      <listitem>
	<para
>?????????????? ??????????????: 3,0 ??????????</para>
      </listitem>

      <listitem>
	<para
>???????????????????? ?????????????????? (????????????): 6,9 ??????????</para>
      </listitem>
    </itemizedlist>
    <para
>???????????????????? ?? 64-???????????? ???????????????? x86_64: </para>
    <itemizedlist arch="x86_64">
      <listitem>
	<para
>???????????????????? ?????????????????? (??????????????????????): 900 ??????????</para>
      </listitem>

      <listitem>
	<para
>????????????: 1,5 ??????????</para>
      </listitem>

      <listitem>
	<para
>???????????????????????? ??????????????????: 2,7 ??????????</para>
      </listitem>

      <listitem>
	<para
>?????????????? ??????????????: 3,4 ??????????</para>
      </listitem>

      <listitem>
	<para
>???????????????????? ?????????????????? (????????????): 7,5 ??????????</para>
      </listitem>
    </itemizedlist>
  </section>

  <section>
    <title
>???????????????????? ?? ????????????</title>

    <para
>?? ???????? ?????????????? ???????????????????????? ???????????? ????????????, ?????????????????????? ?????? ?????????????????? &DISTRO; &DISTROVER;.</para>
    <para
>???????????????????? ?? 32-???????????? ???????????????? x86: </para>
    <itemizedlist arch="x86">
      <listitem>
	<para
>?????????????? ?????? ???????????????????? ????????????: 64 ??????????</para>
      </listitem>

      <listitem>
	<para
>?????????????? ?????? ????????????????????????: 192 ??????????</para>
      </listitem>

      <listitem>
	<para
>?????????????????????????? ?????? ??????????????: 256 ??????????</para>
      </listitem>
    </itemizedlist>
    <para
>???????????????????? ?? 64-???????????? ???????????????? x86_64: </para>
    <itemizedlist arch="x86_64">
      <listitem>
	<para
>?????????????? ?????? ???????????????????? ????????????: 128 ??????????</para>
      </listitem>

      <listitem>
	<para
>?????????????? ?????? ????????????????????????: 256 ??????????</para>
      </listitem>

      <listitem>
	<para
>?????????????????????????? ?????? ??????????????: 512 ??????????</para>
      </listitem>
    </itemizedlist>
  </section>
  <section id="sn-hardware-reqs-ppc">
    <title
>???????????????????? ?? ???????????????????????? PPC</title>
    <para
> ?? ???????? ?????????????? ???????????????????????? ?????????????????????? ???????????????????? ?? ???????????????????????? PowerPC (PPC), ???????????????????? ?????? ?????????????????? &FC; &LOCALVER;. </para>
    <itemizedlist>
      <listitem>
	<para
>??????????????: PowerPC G3 / POWER4 </para>
      </listitem>
      <listitem>
	<para
>&FC; &LOCALVER; ???????????????????????? ???????????? ?????????????????? <quote
>New World</quote
> ?????????????????????? Apple?? Power Macintosh, ?????????????????????? ?? 1999 ??. ?????? ?????????? ???????????????????????? 64-???????????? ?????????????????? G5 ?? ???????????????????? POWER ?? IBM eServer pSeries. ?? ?????????????????? ?????????? 32-???????????? ?????????????? IBM?? RS/6000T ???? ????????????????????????????. </para>
      </listitem>
      <listitem>
	<para
>?????????????????????????? ?????? ???????????????????? ????????????: ?????????????????? G3 ???????????????? 233 ?????? ?????? ?????????? </para>
      </listitem>
      <listitem>
	<para
>?????????????????????????? ?????? ??????????????: ?????????????????? G3 ???????????????? 400 ?????? ?????? ?????????? </para>
      </listitem>
    </itemizedlist>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE i18n-ru.xml ---
<section id="sn-i18n">
  <title
>?????????????????????????????????????? (i18n)</title>
  <para
>SCIM has replaced all the other input methods. Major highlight. </para>
  <section>
    <title
>???????????????? ??????????????????</title>
    <para
>?? ???????? ???????????? ???????????????? ???????????????????? ???? ?????????????????? ?? ?????????????? &DISTRO; ?????????????????? ????????????. </para>
    <section>
      <title
>?????????????? ?????????? IIIMF</title>
      <para
>IIIMF is the Internet/Intranet Input Method Framework. In &FC; &LOCALVER; the <filename
>iiimf</filename
> package is updated to version 12.2. </para>
      <variablelist>
	<varlistentry>
	  <term
>File Path Changes</term>
	  <listitem>
	    <para
>The names and locations of some files in the <filename
>iiimf</filename
> packages have changed. </para>
	    <para
>The IIIMF server has been renamed from <filename
>/usr/sbin/htt</filename
> to <filename
>/usr/bin/iiimd</filename
>, and the XIM bridge client renamed from <filename
>httx</filename
> to <filename
>iiimx</filename
>. The <filename
>init.d</filename
> script name has not changed: it is still called <filename
>iiim</filename
>. All the global system configuration files are now located under <filename
>/etc/iiim/</filename
>. </para>
	    <para
>Language Engine (LE) developers should note that LE modules and their data now live under <filename
>${libdir}/iiim/le/<filename
>&lt;LE_NAME&gt;</filename
>/</filename
>, while runtime data is stored under <filename
>/var/lib/iiim/le/<replaceable
>&lt;LE_NAME&gt;</replaceable
>/</filename
>. </para>
	    <para
>For more information on the exact path and file location changes, please refer to Fedora IIIMF FAQ: </para>
	    <para
><ulink url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html"
>http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink
>. </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term
>Hotkeys</term>
	  <listitem>
	    <para
>Trigger keys, such as <keycombo
><keycap
>Ctrl</keycap
><keycap
>Space</keycap
></keycombo
> used to activate Input Methods, are now configurable with the command-line tool <command
>iiimf-le-tools</command
>. This feature is only supported by GTK2 applications currently. For other applications using XIM the trigger key can be changed using an X resource. Refer to the IIIMF FAQ at <ulink url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html"
>http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink
> for more details on how to change trigger hotkeys. </para>
	    <para
>Note that the keyname refers to the X key symbol name. For example, if you want to activate with <keycombo
><keycap
>Ctrl</keycap
><keycap
>@</keycap
></keycombo
>, you need to specify '&lt;Control&gt;at' as the keyname not '&lt;Control&gt;@'. </para>
	    <para
>The per-user configuration of hotkeys does not work currently with &SEL; in enforcing mode due to lack of &SEL; policy. In this case, the hotkey can only be changed in the system-wide configuration. </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term
>Qt Support</term>
	  <listitem>
	    <para
>A Qt immodule for <filename
>iiimf</filename
> is now included. This immodule works but lacks a status window and is considered experimental. Therefore, the default for Qt applications is to continue using XIM for IIMF input. </para>
	    <para
>If you wish to try the immodule in a Qt application, first install the <filename
>iiimf-qt</filename
> package, start the application, then click mouse button-3 in an input area and select <guimenuitem
>iiimqcf</guimenuitem
> from the <guisubmenu
>Select Input Method</guisubmenu
>' submenu. </para>
	  </listitem>
	</varlistentry>
      </variablelist>
    </section>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE install-notes-ru.xml ---
<section id="sn-anaconda">
  <title
>??????????????????, ???????????????????? ??????????????????</title>
  <para
>?? ???????? ?????????????? ???????????????? ?????????????? ???????????????????????? Anaconda (?????????????????? ?????????????????? &DISTRO;) ?? ?????????? ?????????????????? &DISTRO; &DISTROVER; ?? ??????????. </para>
  <note>
    <title
>??????????????????</title>
    <para
>???????? ???? ???????????????? ?????????????????? DVD ISO-?????????? &DISTRO; &DISTROVER;, ?????????????? ?? ??????, ?????? ???? ?????? ?????????????????? ???????????????? ???????????? ?????????? ???????????????? ?? ?????????????? ???????????????? ???????????? ?????? 2 ????????????. ????????????????, <command
>wget</command
> ?????????????????? ???????? ???????????? ?? ?????????????? <computeroutput
>File size limit exceeded</computeroutput
>. </para>
    <para
>?????????????????? ?????? ???????????????? ???????????? <command
>curl</command
>?? <command
>ncftpget</command
> ???? ?????????? ???????????? ?????????????????????? ?? ?????????? ?????????????? ?????????????????? ??????????, ?????????????? 2 ??????????. </para>
    <para
>?????????????? ?????????? ?????????? ?????????? ?????????????????? ?? ?????????????? Bittorrent. ?????????? ???????????? ?? ??????, ?????? ???????????????? ?? ???????????????????????? ???????? torrent, ???????????????????? ???? ???????? Web-????????: </para>
    <para>
      <ulink
	url="http://torrent.fedoraproject.org/"
>http://torrent.fedoraproject.org/</ulink>
    </para>
  </note>
  <section id="sn-install-notes-ppc">
    <title
>?????????????????? ???? ?????????????????? ???? ?????????????????? PPC</title>
    <section>
      <title
>???????????????????? ?? ???????????????????????? PPC</title>
      <para
>?? ???????? ?????????????? ???????????????????????? ?????????????????????? ???????????????????? ?? ???????????????????????? PowerPC (PPC), ???????????????????? ?????? ?????????????????? &DISTRO; &DISTROVER;. </para>
      <itemizedlist>
	<listitem>
	  <para
>??????????????: PowerPC G3 / POWER4 </para>
	</listitem>
	<listitem>
	  <para
>&DISTRO; &DISTROVER; ???????????????????????? ???????????? ?????????????????? "New World" ?????????????????????? Apple Power Macintosh, ?????????????????????? ?? 1999 ??. </para>
	</listitem>
	<listitem>
	  <para
>&DISTRO; &DISTROVER; ?????????? ???????????????????????? IBM eServer pSeries, IBM RS/6000 ?? ???????????? Genesi Pegasos II.</para>
	</listitem>
	<listitem>
	  <para
>?????????????????????????? ?????? ???????????????????? ????????????: ?????????????????? G3 ???????????????? 233 ?????? ?????? ??????????, 64 ?????????? ??????.</para>
	</listitem>
	<listitem>
	  <para
>?????????????????????????? ?????? ??????????????: ?????????????????? G3 ???????????????? 400 ?????? ?????? ??????????, 128?????????? ??????.</para>
	</listitem>
      </itemizedlist>
      <para
>DVD ?????? ???????????? CD ?????????????????????????? ???????????? &FC; ???????????? ?????????????????????? ???? ???????????????????????????? ????????????????????????. ?????????? ??????????, ???????????? ?????????????????????? ??????????????-???????????? ?????????? ?????????? ???? DVD ?????? ???????????? CD ?? ???????????????? <filename
>images/</filename
>. ???? ???????????? ?????????????????????? ?? ?????????????????????? ???? ????????????????????????: </para>
      <variablelist>
	<title
>?????????????????? ???????????????????????? ???????????? ?? ?????????????????????? ???? ????????????????????????</title>
	<varlistentry>
	  <term
>Apple Macintosh </term>
	  <listitem>
	    <para
>The bootloader should automatically boot the appropriate 32-bit or 64-bit installer. Power management support, including sleep and backlight level management, is present in the <filename
>apmud</filename
> package, which is in &FEX;. &FEX; for &FC; is configured by default for yum. Following installation, <filename
>apmud</filename
> can be installed by running the command <command
>yum install apmud</command
> in a terminal. </para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term
>64-bit IBM eServer pSeries (POWER4/POWER5)</term>
	  <listitem>
	    <para
>After using OpenFirmware to boot the CD, the bootloader (<command
>yaboot</command
>) should automatically boot the 64-bit installer. </para>
	  </listitem
>        
	</varlistentry>
	<varlistentry>
	  <term
>32-bit CHRP (IBM RS/6000 and others)</term>
	  <listitem>
	    <para
>After using OpenFirmware to boot the CD, select the <filename
>linux32</filename
> boot image at the <prompt
>boot:</prompt
> prompt to start the 32-bit installer. Otherwise, the 64-bit installer is started, which does not work.</para>
	  </listitem>
	</varlistentry>
	<varlistentry>
	  <term
>Genesi Pegasos II</term>
	  <listitem>
	    <para
>As of &DISTRO; &DISTROVER;, firmware with full support for ISO9660 file systems is not yet released for the Pegasos. However, the network boot image can be used. At the OpenFirmware prompt, enter the command: </para>
<screen
><command>boot cd: /images/netboot/ppc32.img</command> 
</screen
>          
	    <para
>You will also need to configure OpenFirmware on the Pegasos manually to make the installed &FC; system bootable. To do this, you need to set the <envar
>boot-device</envar
> and <envar
>boot-file</envar
> environment variables appropriately. </para>
	  </listitem
>        
	</varlistentry>
	<varlistentry>
	  <term
>???????????????? ???? ????????</term>
	  <listitem>
	    <para
>?? ???????????????? images/netboot/ ???????????? ?????????????????? ?????????????? ???????????? ?????????????????????????? ???????? ?? ramdisk. ?????? ?????????????????????????? ?????? ???????????????? ???? ???????? ?? ???????????????????????????? TFTP, ???? ?????????? ???????????????????????????? ?? ?????????? ??????????????????. </para>
	    <para
>The command <command
>yaboot</command
> supports tftp booting for IBM eServer pSeries and Apple Macintosh. &FED; recommends using yaboot over the netboot images. </para>
	</listitem>
	</varlistentry>
      </variablelist>
    </section>
  </section>
  <section>
    <title
>?????????????????? ???? Anaconda</title>
    
    <itemizedlist>
      <listitem>
	<para
>?????????????????? ?????????????????? &DISTRO; ?????????? ?????????????????????? ?????????????????? ?????????????????????? ???????????????? ??????????????????????. ?????? ?????????? ?????????????? ?????? ?????????????????? ?? CD, DVD ?????? ISO-????????????, ???????????????????????????? ???? ?????????????? ?????????? ?????? ?? ????????. &RH; ?????????????????????? ?????? ?????????????????? ?????? ???????????????? ?????????????????????? ???? ???????????? ???????????????? ??????????????????, ?? ???? ?????????????? ???????????????? ???? ?????????????? ?????????????????????? (?????????????? ???????????????????? ???????????? ???? ?????????? ???????? ?????????????? ?? ?????????????? ?????????????????????? ??????????????-??????????????). ?????????? ???????????????? ?????? ????????????????, ?????????????? <command
>linux mediacheck</command
> ?? ?????????????????????? <prompt
>boot:</prompt
>. </para>
	<para
>?????????????? <command
>mediacheck</command
> ?????????? ?????????????????????????? ?? ?????????? ???????????????? ???? ???????????? ?? ???? ?????????????????? ???????????????????? ????????????. ?????? ?????????? ?????????????????? ???? ???????? ???????????????? ???????????? ????????????, ?????????????? ?????? ???????????????? ???????????? ???? ISO-???????????? ???????????????????? ??????????????????????. ?????????? ?????????????? <command
>mediacheck</command
> ???????????????? ??????????, ?????????????????????? ?? ????????????????????: </para>
<screen
>linux ide=nodma
</screen>
	<para
>???????????? ?????? ?????????????????? ??????????????????, ?????????????????? ??????????, ???????????????????????????????? ???????????????? <command
>sha1sum</command
>. ?????? ?????????? ?????????????????? ?????????? ?? ???????????????? ?????? ???????????????????????? ???? ???????????????? ISO-??????????????. </para>
      </listitem>
      <listitem arch="x86">
<!--	<remark os="test"
>%%% <ulink
	    url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654"
>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654</ulink
> 
	  %%%</remark>
-->
	<para
>?????????? ?????????? ???????????????????? &DISTRO; ?????????? ???????? ?????????????????? ???????????????? ????????????, ?????? ?????????? ?????????????? <command
>memtest86</command
> ?? ?????????????????????? <prompt
>boot:</prompt
>. ?????? ???????? ?????????? ???????????????? ?????????????????? ?????????????????? Memtest86, ?????????????????????? ????????????. ???????????????? ???????????? Memtest86 ?????????????????????? ???? ?????????????? ?????????????? <keycap
>Esc</keycap
>. </para>
	<para
>??????????????????: ?????????? ???????????????????????? ?????? ??????????????????????, ???? ???????????? ?????????????????????? ?? ?????????????? ??????????????-?????????? (?????? ?????????? ????????????????????????????). </para>
      </listitem>
      <listitem>
<!--	<remark os="test"
>%%% <ulink
	    url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627"
>https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627</ulink
> 
	  %%%</remark>
-->
	<para
>?????????????? &DISTRO; &DISTROVER; ???????????????????????? ?????????????????????? ?????????????????? ?????????? ???????? ???? FTP ?? HTTP. ????????????, ?????? ?????? ?????? ?????????? ???????????????????? ???????????????????? ?????????? ?????????????????? ?????????????????? ?? ??????, ?????????????????????? ?????????????????? ?????????? ?????????????????????? ???????????? ???? ??????????????????????, ???????????????????? ?????????? ?????? 128 ?????????? ???????????? (?????? ??????????????????????, ?????????????????????? ?? ?????????????? ??????????????-??????????, ?????????????????????? ???????? ??????????). ???? ??????????????????????, ?????????????? 128 ?????????? ???????????? ?????? ?????? ????????????, ????-???????????????? ?????????? ?????????????????????? ?????????????????? ?? ?????????????????? ????????????. </para>
      </listitem>
    </itemizedlist>
  </section>
  <section>
    <title
>??????????????, ???????????????????? ??????????????????</title>
    <itemizedlist>
      <listitem>
	<para
>?? ?????????????????? ???????????????????? ?????????????????????????? (???????????????? ?????? ???????????????? LCD-????????????????) ?????? ?????????????? ?????????????????? ?????????????????? &DISTRO; ???? ???????????? ?????????????????????? ?? ????????????????????. ???????????????????? ???????????? ????, ???????????????????????? ?????????????????? ?? ?????????????? ?? ?????????????????? ???????????? ???????????????????? ???????????????? "<command
>nofb</command
>". </para>

	<note>
	  <title
>??????????????????</title>
	  <para
>?????????????????????? ?????????????????? ???? ??????????????????, ???????????????? ?????? ?????????????????? ??????????, ???????????????????? ?? ???????????????????? "<command
>nofb</command
>", ???????????????? ???? ???????????????????? ??????????, ?? ??????????, ???? ?????????? ?????????????????? ?? ?????????????????????? ????????????, ???????????????????????? ???? ?????????????????? ????????. </para>
	</note
>   
      </listitem>
      <listitem arch="x86">
	<para
>?????? ?????????????????? &DISTRO; ?? ??????????????-?????????? ???? ?????????????????? ?????????????????? <trademark class="registered"
>VAIO</trademark
> ?????????? ???????????????????? ????????????????. ?? ???????? ?????????????? ?????????????????????????? ?????????????????? ?? ???????????????? ?? ?????????????????? ???????????? ???????????????????? ?????????????????? ????????????????: </para>
<screen
><!-- <remark os="test">(x86)</remark> -->
<command>pci=off ide1=0x180,0x386</command>
</screen>
	<para
>???????? ???????????????? ???????????????? ?????????????????? ??????????????????; ?????? ????????????????????, ???? ?????????????????? ????-???? ?????????? ??????????????????, ?????????? ?????????????????? ?????? ???????????? ?????????????? &DISTRO;. </para>
      </listitem>
      <listitem>
	<para
>????????????????, ?????? ???? ?????????? ?????????????????? ???? ???????????????? ???????? ?? ???????????????????????????????? ??????????????????????. ????????????, ?????????????????? ?????????????????? ?? ??????, ?????? ?????????? ???????? ?????????????????? ???????????????? ?? X ?????????? ???????????????????? ??????????????????. ???????????????????????????? ???????????????????? ?????????????????? ?? ???????????????? ???????????? 119474: </para>
	<para>
	  <ulink
	    url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474"
>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474</ulink>
	</para>
      </listitem>
      <listitem arch="x86">
	<para
>???????? ????????????????, ?????? ?????? ???????????????????? ?? ???????????? &RHL; 7.<replaceable
>&lt;x&gt;</replaceable
>, 8.0, 9 ?? &FC; 1, 2, 3 ?????????????????????????? ???????????? ?????????????????? ???????????????????????????? ?????????? ?????????????????????????? ?? ????????????????, ???????????????????????????????? ???????????????? &FP;. ?? ???????????????? ?????????????? ?????????? ???????????????? Ximian GNOME. </para>
	<para
>???????????????? ?? Ximian GNOME ?????????????????? ????-???? ?????????????????? ???????????? ?????????? ???????????????????????? RPM-???????????????? &RHL; (?????? ?????????????? &PROJ;) ?? RPM-???????????????? Ximian. ?????? ???????????????????????? ???? ????????????????????????????. ?????????????????? ???????????? ?????? ???????????????? ?????????? ???????????????????? ??????????????????: </para>
	<orderedlist numeration="loweralpha">
	  <listitem>
	    <para
>???? ???????????????????? ?????????????? &DISTRO; ?????????????? ???? ?????????????? Ximian GNOME.  </para>
	  </listitem>
	  <listitem>
	    <para
>???????????????? ??????????????, ?? ?????????? ???????????????????? ???????????????????????????? Ximian GNOME. </para>
	  </listitem>
	  <listitem>
	    <para
>???????????????? ???????? ??????????????, ?? ?????????? ???????????????????? ?????????????? ?????? ???????????????????? RPM-???????????? Ximian, ?????????????? ???? ???????????????????????????????? RPM-???????????????? &DISTRO;. </para>
	  </listitem>
	</orderedlist
>	
	<para
>???? <emphasis
>????????????</emphasis
> ?????????????????? ???????????????? ???????????? ?????????? ???? ?????????????????? ????????????????. ???? ???????????? ??????????, ???? ???????????????? ???????????????????????? ???????????????????????? ?????????? GNOME. </para>
      </listitem>
    </itemizedlist>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE intro-ru.xml ---
<section id="sn-intro">
  <title
>???????????????? ?? ?????????????????????? ?????????????????? ?? ????????????</title>
  <para
>???????????? &PROJ; &mdash; ?????????????? ?????????????????????????????? ????????????, ?????????????????? &RH;, ???????????????? ?????? ??????????????, ?????????????????????? ???????????????????? ????????????????????????, ?? ?????????????????? ???????????????????????? ??????????????. ?????????? ???? ?????????????????????? ?????????? ?????????????? ???????????????? &DISTRO; &mdash; ?????????????????? ???????????????????????? ?????????????? ???????????? ????????????????????, ?????????????????????? ?????????????????????????? ???? ???????????????????????? ?????????????????????? ?? ???????????????? ??????????. </para>
  <note>
    <title
>??????????????????</title>
    <para
>&FC; &mdash; ????????????, ???????????????????????????? ??????????????????????. </para>
    <para
>&FC; ???? ???????????????? ?????????????????????? ???????????????????????????? ?????????????????? &FORMAL-RHI;. </para>
  </note>
  <para
>???? ???????????????????????????? ?????????????????????? ???????????????????? ?? <xref linkend="sn-overview"/>. </para>
  <para
>???????????????????????????? ???????????? ???????????????????? ???? ???????? ???????????? ?????????? ???????? ?????????????????? ???? ???????????? <ulink url="http://fedora.redhat.com/docs/release-notes/"
>http://fedora.redhat.com/docs/release-notes/</ulink
>. ?????????????????????????? ?????????????????? ?????????????????? ?????? ???????????? ???? ?????????????? ????????????????????. </para>
  <para
> ?????????? ?????????????????? ?????????????????? ???? ???????????? ?????? ???????????? ???????????????????????? ???????? ?????????????????? ?? ????????????, ???????????????????????????? <ulink url="&BUG-URL;"
>???????????????????????????? ???????????????? bugzilla</ulink
>. </para>
<!-- This is just to tweaky to HTML and will make people think it's b0rked
  <para>
    <ulink
    url="&BUG-URL;"
>&BUG-URL;</ulink>
  </para>
-->
  <para
> ?????????????? ???? ???????????? <ulink url="&TINY-BUG-URL;"
>&TINY-BUG-URL;</ulink
> ???? ?????????????????? ?? ?????? ???? ???????????????????????????? ?????????????? bugzilla. </para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE java-package-ru.xml ---
<section id="sn-java-packages">
  <title
>???????????????????????? ???????????????????????? ???????????? Java</title>
  <caution>
    <title
>???????????????????????? ???????????????????????? ???????????? Java</title>
    <para
>???????????????????? ?????????????? ?????????????? ?????????????? ?????????????????????????? ?? &DISTRO; &DISTROVER; </para>
  </caution>
  <para
>?????????????????????????? &FC; &LOCALVER; ???? ?????????????????????????? ???????????????????????? RPM-??????????, ?????????????????????????? Sun. ???????????????? ???????????????? <computeroutput
>Provides</computeroutput
> (??????????????????????????) ?????????? ???????????? ?????????????????????? ?? ??????????????, ?????????????????????????? ?? ??????????????, ???????????????????? ??  &FC; &LOCALVER;. ???? ???????? ?????????????? Sun Java ?????????? ?????????????????? ?? ?????????????????????????? ?????????????? ???????????????? ???? ???????????????????? ??????????????. </para>
  <para
>???????????????????????? &FC; &LOCALVER; ???????????? ???????? ???????????????????????? RPM ?? jpackage.org, ???????? ?????????????? ???????????????????? tarball-?????????? Sun Java ?? <filename
>/opt</filename
>. ???? ?????????????????????? ???????????????????????? ?????????????????????????? Sun Java 1.5+. </para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE kernel-ru.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "These FAKE ENTITIES are just to make editing easier">
 <!ENTITY FC            "FC">
 <!ENTITY LOCALVER      "LOCALVER">
 <!ENTITY DISTRO        "DISTRO">
 <!ENTITY DISTROVER     "DISTROVER">

]>
-->
<section id="sn-kernel">
  <title
>???????? Linux </title>
  <section id="sn-kernel-lotsa">
    <title
>????????????</title>
    <para
>The distribution is based on the 2.6 series of the Linux kernel. &FC; may include additional patches for improvements, bug fixes, or additional features. For this reason, the &FC; kernel may not be line-for-line equivalent to the vanilla<firstterm
></firstterm
> kernel from the <ulink url="http://www.kernel.org"
><filename
>kernel.org</filename
></ulink
> website. </para>
    <para
>You may obtain a list of any such patches by using the command on the &FC; package: </para>
<screen width="56"
><command>rpm <parameter class="option">-qpl</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
</screen>
  </section>
  <section id="sn-kernel-flavors">
    <title
>?????????????????????????? ????????</title>
    <para
>&FC; includes the following kernel builds: </para>
    <itemizedlist>
      <listitem>
        <para
>Native kernel, in both uniprocessor and <abbrev
>SMP</abbrev
> varieties. Configured sources are available in the <filename
>kernel-devel-<replaceable
>version</replaceable
>.<replaceable
>arch</replaceable
>.rpm</filename
> package. </para>
      </listitem>
      <listitem>
        <para
>Virtual kernel for use with the <application
>Xen</application
> emulator package. Configured sources are available in the <filename
>kernel-xen0-devel-<replaceable
>version</replaceable
>.<replaceable
>arch</replaceable
>.rpm</filename
> package. </para>
      </listitem>
    </itemizedlist>
    <para
>Sources for both kernel flavors may be installed at the same time. The files are installed into the <filename
>/usr/src/kernels/<replaceable
>version</replaceable
>[-xen0]-<replaceable
>arch</replaceable
>/</filename
> tree. Use the command: </para>
<screen width="56"
><command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename></command>
</screen>
    <para
>as appropriate. </para>
    <tip>
      <title
>Following Generic Textbooks About the Linux Kernel</title>
      <para
>Many of the tutorials, examples, and textbooks about Linux kernel development assume the kernel sources are installed under the <filename
>/usr/src/linux</filename
> directory. If you make a symbolic link, as shown below, you should be able to use those learning materials with the &FC; packages. Install the appropriate kernel sources, as shown earlier, and then: </para>
<screen width="56"
><command>ln <parameter class="option">-s</parameter> <filename>/usr/src/kernels/kernel-<replaceable>all-the-rest</replaceable></filename> <filename>/usr/src/linux</filename></command>
</screen>
    </tip>
  </section>
  <!--
  <tip>
    <title
>Using <command
>yum</command
> to Remove Kernel
    Packages</title>
    <para>
      &FC; &LOCALVER; contains support for clustering systems using CMAN and GFS.
      These kernels require assistance from some user-space packages.
      These packages are not removed when using <command
>rpm
      -e</command
> to remove older versions of the kernel packages.
    </para>
    <para>
      When using <command
>rpm -e kernel-<replaceable
>version</replaceable
> </command
> to remove the kernel, you must also remove the assisting user-space packages.  You may wish to consider a dependency resolving tool such as <command
>yum remove kernel-<replaceable
>version</replaceable
> </command
>.
      This automatically removes any dependent packages.
    </para>
  </tip>
  -->
  <section id="sn-kernel-exploding">
    <title
>???????????????????? ?? ???????????????????? ???????? </title>
    <para
>&DISTRO; &DISTROVER; does not include the <filename
>kernel-source</filename
> package provided by older versions. Instead, configured sources are available as described in <xref linkend="sn-kernel-flavors"/>. Users that require access to &FC; original kernel sources can find them in the <filename
>kernel</filename
> <filename
>.src.rpm</filename
> package. To create an exploded source tree from this file, perform the following steps: </para>
    <important>
    <title
>These Instructions Refer to the Currently-running Kernel!</title>
      <para
>To simplify the following directions, the assumption is that you want to configure the kernel sources to match your currently-running kernel. In the steps below, you must understand that the phrase <replaceable
>version</replaceable
> refers to the kernel version shown by this command: </para>
<screen width="56"
><command>uname <parameter class="option">-r</parameter></command>
</screen>
    </important>
    <procedure id="sn-kernel-exploding-steps">
      <step>
        <para
>Obtain the <filename
>kernel-<replaceable
>version</replaceable
>.src.rpm</filename
> file from one of the following sources: </para>
        <itemizedlist>
          <listitem>
            <para
>The <filename
>SRPMS/</filename
> directory on the appropriate <wordasword
>SRPMS</wordasword
> <abbrev
>CD</abbrev
> <filename
>ISO</filename
> image. </para>
          </listitem>
          <listitem>
            <para
>The FTP site where you got the kernel package. </para>
          </listitem>
          <listitem>
            <para
>By running the following command: </para>
<!-- FIXME up2date is sorta deprecated for FC, how to do this with yum? -->
<screen width="56"
><command>up2date <parameter class="option">--get-source</parameter> <filename>kernel</filename></command>
</screen>
          </listitem>
        </itemizedlist>
      </step>
      <step>
        <para
>Install <filename
>kernel-<replaceable
>version</replaceable
>.src.rpm</filename
> using the command: </para>
<screen width="56"
><command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
</screen>
        <para
>This writes the <abbrev
>RPM</abbrev
> contents into <filename
>/usr/src/redhat/SOURCES</filename
> and <filename
>/usr/src/redhat/SPECS</filename
>. </para>
      </step>
      <step>
        <para
>Prepare the kernel sources using the commands: </para>
<screen width="56"
><command>cd <filename>/usr/src/redhat/SPECS</filename></command>
<command>rpmbuild <parameter class="option">-bp --target $(arch)</parameter> <filename>kernel-2.6.spec</filename></command>
</screen>
        <para
>The kernel source tree is located in the <filename
>/usr/src/redhat/BUILD/kernel-</filename
><replaceable
>version</replaceable
> directory. It is common practice to move the resulting <filename
>linux-<replaceable
>version</replaceable
></filename
> directory to the <filename
>/usr/src</filename
> tree; while not strictly necessary, doing so matches you with the generally-available documentation. </para>
<screen width="56"
><command>cd <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
<command>mv <filename>linux-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
<command>cd <filename>/usr/src</filename></command>
<command>ln <parameter class="option">-s</parameter> <filename>./linux-<replaceable>version</replaceable></filename> <filename>linux</filename></command>
<command>cd <filename>/usr/src/linux</filename></command>
</screen>
      </step>
      <step>
        <para
>The configurations for the specific kernels shipped in &DISTRO; &DISTROVER; are in the <filename
>configs/</filename
> directory. For example, the i686 SMP configuration file is named <filename
>configs/kernel-<replaceable
>version</replaceable
>-i686-smp.config</filename
>. Issue the following command to place the desired configuration file in the proper place for building: </para>
<screen width="56"
><command>cp <filename>configs/<replaceable>desired-config-file</replaceable></filename> <filename>.config</filename></command>
</screen>
        <para
>You can also find the <filename
>.config</filename
> file that matches your current kernel configuration in the <filename
>/lib/modules/</filename
><replaceable
>version</replaceable
><filename
>/build/.config</filename
> file. </para>
      </step>
      <step>
        <para
>Every kernel gets a name based on its version number. This is the value the <command
>uname -r</command
> command displays. The kernel name is defined by the first four lines of the kernel <filename
>Makefile</filename
>. To protect the innocent, the <filename
>Makefile</filename
> has been changed to generate a kernel with a different name from that of the running kernel. Before a module can be accepted by the running kernel, that module must have been compiled for a kernel with the correct name. To do this, you must edit the kernel <filename
>Makefile</filename
> </para>
        <para
>For example, if the <command
>uname -r</command
> returns the string <systemitem class="osname"
>2.6.11-1.234_FC4</systemitem
>, change the <systemitem class="macro"
>EXTRAVERSION</systemitem
> definition from this: </para>
<screen width="60"
>EXTRAVERSION = -prep
</screen>
        <para
>to this: </para>
<screen width="60"
>EXTRAVERSION = -1.234_FC4
</screen>
        <para
>That is, substitute everything from the final dash onward. </para>
      </step>
      <step>
        <para
>Issue the following command: </para>
<screen width="56"
><command>make oldconfig</command>
</screen>
      </step>
    </procedure>
    <para
>You can then proceed as usual. </para>
  </section>
  <section id="sn-kernel-3rdparty">
    <title
>???????????????????? ???????????? ?????????????? ????????</title>
    <para
>An exploded source tree is <emphasis
>not</emphasis
> required to build a kernel module, such as your own device driver, against the currently in-use kernel. </para>
    <para
>For example, to build the <filename
>foo.ko</filename
> module, create the following <filename
>Makefile</filename
> in the directory containing the <filename
>foo.c</filename
> file: </para>
<programlisting width="56"
>obj-m := foo.o

KDIR  := /lib/modules/$(shell uname -r)/build
PWD   := $(shell pwd)

default:
    $(MAKE) -C $(KDIR) M=$(PWD) modules
</programlisting>
      <para
>Issue the <command
>make</command
> command to build the <filename
>foo.ko</filename
> module. </para>
  </section>
  <section id="sn-kernel-coop">
    <title
>?????????????????????? ???????? ???? ???????????? ???????????????????????? ????????????????????????</title>
    <para
>&DISTRO; adds support for clustered systems. This requires a special kernel that works in conjunction with some user-space utilities, such as management daemons. Consequently, to remove such a kernel, perhaps after an update, you <emphasis
>cannot</emphasis
> simply use the <command
>rpm -e kernel-<replaceable
>version</replaceable
></command
> command as in earlier distributions because these user space packages depend on the kernel package. You may either list both the kernel package and its user space dependent packages on the <command
>rpm -e</command
> command, or you may wish to use the <command
>yum remove kernel-<replaceable
>version</replaceable
></command
> command instead since <command
>yum</command
> automatically removes dependent packages if necessary. </para>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE legacynotice-ru.xml ---
<note>
  <title
>LEGACY DOCUMENT</title
>  
  <para
>This document relates to a version of &FC; that is no longer supported by the &FP;. Changes in later versions of &FC; may have made this document inaccurate. Please check the &FDP; website at &FDPDOCS-URL; for a current version before you continue reading this document. </para>

  <para
>This version of the document will not be changed or amended, except to correct errors that may result in data loss or a system security weakness. If you believe that you have found such an error, please report it via &BZ; in bug &BUG-NUM;. </para>
</note>


--- NEW FILE legacy-ru.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE legalnotice-content-ru.xml ---

  <para
>Permission is granted to copy, distribute, and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is available at <ulink url="http://www.gnu.org/licenses/fdl.html"
>http://www.gnu.org/licenses/fdl.html</ulink
>. </para>

  <para>
    This document may be copied and distributed in any medium, either
    commercially or noncommercially, provided that the GNU Free Documentation
    License (FDL), the copyright notices, and the license notice saying the GNU
    FDL applies to the document are reproduced in all copies, and that you add
    no other conditions whatsoever to those of the GNU FDL.
  </para>

  <para>
    Garrett LeSage created the admonition graphics (note, tip, important,
    caution, and warning).
    Tommy Reynolds <email
>Tommy.Reynolds at MegaCoder.com</email
> created the callout graphics.
    They all may be freely redistributed with documentation
    produced for the &PROJECT;.
    </para>

  <para>
    &BOOKID;
  </para>

  <para>
    &RH; and the &RH; "Shadow Man" logo are registered trademarks of
    &FORMAL-RHI; in the United States and other countries.
  </para>

<!-- Changing to match RHEL usage, changes are drawn directly from existing -->
<!-- lawyer-approved changes within the RHEL legalnotice:
  <para>
    &RH;, &RH; Network, the &RH; "Shadow Man" logo, RPM, Maximum RPM, the RPM logo, Linux
    Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts,
    Rawhide and all &RH;-based trademarks and logos are trademarks or registered
    trademarks of &FORMAL-RHI; in the United States and other countries.
  </para>

  <para>
    Linux is a registered trademark of Linus Torvalds.
  </para>

  <para>
    Motif and UNIX are registered trademarks of The Open Group.
  </para>

  <para>
    Intel and Pentium are registered trademarks of Intel Corporation. Itanium
    and Celeron are trademarks of Intel Corporation.
  </para>

  <para>
    AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of Advanced Micro
    Devices, Inc.
  </para>

  <para>
    Windows is a registered trademark of Microsoft Corporation.
  </para>

  <para>
    SSH and Secure Shell are trademarks of SSH Communications Security, Inc.
  </para>

  <para>
    FireWire is a trademark of Apple Computer Corporation.
  </para>
-->
  <para>
    All other trademarks and copyrights referred to are the property of their
    respective owners.
  </para>


--- NEW FILE legalnotice-relnotes-ru.xml ---


--- NEW FILE legalnotice-section-ru.xml ---
<!-- 

  Use this legalnotice for no-chunks/single-page HTML output.  It is an optional
  usage to move the bulk of the legalnotice to another location in the document.

  If you use this legalnotice, you must include a call to the
  LEGALNOTICE-NOCHUNKS or LEGALNOTICE-RELNOTES.  This gets the legal material in
  the proper <legalnotice /> container.SECTION entity, or include a similar <section> in your document.
  The call to LEGALNOTICE-SECTION must happen where a <section> is otherwise
  allowed.  One good location is immediately following an introduction.

  -->
  <section id="sn-legalnotice">
    <title>?????????????????????? ??????????????????????</title>
    &LEGALNOTICE-CONTENT;
  </section>


--- NEW FILE misc-server-ru.xml ---
<section id="sn-misc-server-notes">
  <title
>Miscellaneous Notes</title>
  <para
>This section contains information related to packages that do not fit in any of the preceeding categories. </para>
  <section id="sn-misc-notes-openoffice">
    <title
>OpenOffice and upgrading from test releases</title>
    <para
>If you choose to go counter to the recommendation to <emphasis
>not</emphasis
> upgrade from a previous test release, you may encounter a problem with OpenOffice following the upgrade. </para>
    <para
>To resolve this, you must do the following command <emphasis
>before</emphasis
> doing the upgrade: </para>
    <para>
      <command
>rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
    </para>
  </section>
</section>

<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE multimedia-ru.xml ---
<section id="sn-multimedia">
  <title
>??????????????????????</title>
  <para
>&FC; includes applications for assorted multimedia functions, including playback, recording, and editing. Additional packages are available through the &FEX; repository. </para>
  <variablelist>
    <varlistentry>
      <term
>?????????????????????? ??????????????????????????</term>
      <listitem>
	<para
>By default, &FC; installs with <filename
>rhythmbox</filename
>, <filename
>totem</filename
>, and <application
>Helix Player</application
> (<command
>hxplay</command
>) for media playback. In addition, many other programs are available in the &FC; and &FEX; repositories, including the popular xmms package. Both GNOME and KDE also have specific sets of programs that can be used with a variety of formats. Other popular programs, such as Adobe/Macromedia's Flash Player, Real Player, VLC, MPlayer, and Xine, can also be installed, but are excluded from the &FED; repositories since they are not compatible with &FED;'s licensing or are usually distributed with support for restricted formats. For more on this, refer to <xref linkend="sn-multimedia-excluded"/>. </para>
	<para
>&FC; is also equipped to take full advantage of the Advanced Linux Sound Architecture (ALSA) sound system. This means that many programs can play sound simultaneously, which was once difficult on Linux systems. When all multimedia software is configured to use ALSA for sound support, this old limitation disappears. For more information about ALSA, visit the project website: </para>
	<para>
	  <ulink url='http://www.alsa-project.org/'
>http://www.alsa-project.org/</ulink>
	</para>
      </listitem
>    
    </varlistentry>
    <varlistentry>
      <term
>Ogg and Xiph.Org Foundation Formats</term>
      <listitem>
	<para
>Fedora includes complete support for the Ogg media container format, the Vorbis audio, Theora video, Speex audio, and FLAC lossless audio formats. More information on these formats and how to use them can be found at the Xiph.Org Foundation's web site: </para>
	<para>
	  <ulink url='http://www.xiph.org/'
>http://www.xiph.org/</ulink>
	</para>
      </listitem
>   
    </varlistentry>
    <varlistentry>
      <term
>MP3 &amp; DVD Support</term>
      <listitem>
	<para
>&FC; and &FEX; cannot include support for MP3 or DVD playback or recording, because the MP3 and MPEG (DVD) formats are patented, and the patent owners have not provided the necessary licenses. For more information, refer to <xref linkend="sn-multimedia-excluded"/>. </para>
      </listitem>
    </varlistentry>
  </variablelist>
  <section id="sn-multimedia-excluded">
    <title
>?????????????????????? ???? ?????? ???????????? ?? ??????????????????????</title>
    <para
>Several programs are excluded from &FC; and &FEX; due to licensing issues. These include programs that provide MP3 and DVD support, Flash Player and Real Player. Users who wish to use these programs or restricted formats have to acquire additional packages from third-party repositories. Many of the multimedia applications in the Fedora repositories support plugins, so support for new formats can be easily added or removed. For more on this subject, please see: </para>
    <para>
      <ulink url='http://fedoraproject.org/wiki/ForbiddenItems'
>http://fedoraproject.org/wiki/ForbiddenItems</ulink>
    </para>
  </section>
  <section id="sn-multimedia-cd-dvd-burning">
    <title
>???????????????????? ?? ???????????? CD ?? DVD</title>
    <para
>Tools are included in &FC; and &FEX; for easily mastering and burning CDs and DVDs. Tools that can be used from the console include <command
>cdrecord</command
>, <command
>readcd</command
>, <command
>mkisofs</command
>, and other typical Linux applications. For GNOME users, the <filename
>xcdroast</filename
> package from &FC; and the <filename
>graveman</filename
> package from &FEX; allow easy preparation of audio and data discs. For KDE users, the <filename
>k3b</filename
> package provides a very robust tool for these tasks. </para>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE networking-ru.xml ---
<section id="sn-networking">
  <title
>Networking</title>
  <variablelist>
    <title
>Major Kernel Changes 2.6.11 - 2.6.14</title>
    <varlistentry>
      <term
>IPv4 Address Promotion</term>
      <listitem>
      <para
>Starting with version 2.6.12 of the kernel a new feature has been added called named address promotion. It allows secondary IPv4 addresses to be promoted to primary addresses. Usually when the primary address is deleted all secondary addresses are deleted as well. By enabling the new <command
>sysctl</command
> <option
>net.ipv4.conf.all.promote_secondaries</option
> (or one of the interface specific variants) this behaviour can be changed to promote one of the secondary addresses to be the new primary address. </para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term
>Configurable Source Address for ICMP Errors</term>
      <listitem>
	<para
>The current behaviour when selecting the source address for ICMP error messages is to use the address of the interface the ICMP error is going to be sent out. Kernel version 2.6.12 introduces a new <command
>sysctl</command
> <option
>net.ipv4.icmp_errors_use_inbound_ifaddr</option
> which allows to change this behaviour to use the address of the interface which has received the original packet causing the error. </para>
	<para
>For example, the kernel receives an ICMP echo request on <computeroutput
>eth0</computeroutput
>. Because the new <command
>sysctl</command
> option is enabled, this causes the ICMP echo reply to be sent out via <computeroutput
>eth1</computeroutput
>. The address of <computeroutput
>eth0</computeroutput
> is used when the default behaviour would use the address of <computeroutput
>eth</computeroutput
>. </para>
	<para
>This may ease network debugging in asynchronous routing setups. </para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term
>LC-Trie Based Routing Lookup Algorithm</term>
      <listitem>
	<para
>A new routing lookup algorithm called <firstterm
>trie</firstterm
> has been added. It is intended for large routing tables and shows a clear performance improvement over the original hash implementation at the cost of increased memory consumption and complexity. </para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term
>Pluggable Congestion Control Algorithm Infrastructure</term>
      <listitem>
	<para
>TCP congestion control algorithms are now pluggable and thus modular. The legacy <firstterm
>new RENO</firstterm
> algorithm stays default and acts as fallback algorithm. During the period of this work the following new congestion control algorithms have been added: </para>
	<itemizedlist>
	  <listitem>
	    <para
>High Speed TCP congestion control. </para>
	  </listitem>
	  <listitem>
	    <para
>TCP Hybla congestion avoidance. </para>
	  </listitem>
	  <listitem>
	    <para
>H-TCP congestion control. </para>
	  </listitem>
	  <listitem>
	    <para
>Scalable TCP congestion control. </para>
	  </listitem>
	</itemizedlist>
	<para
>All existing congestion control modules have been converted to this new infrastructure and the BIC congestion control has received enhancements from BICTCP 1.1 to handle low latency links. </para>
	<note>
	  <title
>Affecting the Congestion Control Algorithm</title>
	  <para
>An interesting addition for developers is that the congestion control algorithm is socket specific and can be changed via the socket option <option
>TCP_CONGESTION</option
>. </para>
	</note>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term
>Queue Avoidance upon Carrier Loss</term>
      <listitem>
      <para
>When a network driver notices a carrier loss, for example when the cable is pulled out, the driver stops the queue in front of the driver. This has been causing the packets to be queued at the queueing discipline layer for an unbound period of time causing unexpected effects. In order to prevent this effect, the core networking stack now ceases to accept any packets for queueing for any device that is operationally down, that is, has its queue disabled. </para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term
>DCCP Protocol Support</term>
      <listitem>
	<para
>Kernel version 2.6.14-rc1 was the first version to receive support for the DCCP protocol. The implementation is still experimental but known to work. Work to make userspace applications aware of this new protocol has started. </para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term
>Wireless</term>
      <listitem>
	<para
>A new driver named HostAP has been added to 2.6.14-rc1 allowing the emulation of a wireless access point in software. Currently this driver only works for Intersil Prism2-based cards (PC Card/PCI/PLX). Support for wireless cards Intel(R) PRO/Wireless 2100 and 2200 has been added. </para>
      </listitem>
    </varlistentry>
    <varlistentry>
      <term
>Miscellaneous</term>
      <listitem>
	<itemizedlist>
	  <listitem>
	    <para
>A lot of TCP Segmentation Offloading (TSO) related fixes have been included. </para>
	  </listitem>
	  <listitem>
	    <para
>A new textsearch infrastructure has been added useable with the corresponding iptables and extended match. </para>
	  </listitem>
	  <listitem>
	    <para
>Both the IPv4 and IPv6 multicast joining interface visible by userspace have been reworked and brought up to the latest standards. </para>
	  </listitem>
	  <listitem>
	    <para
>The SNMPv2 MIB counter ipInAddrErrors is finally supported for IPv4. </para>
	  </listitem>
	  <listitem>
	    <para
>Various new socket options proposed in Advanced API (RFC3542) have been added. </para>
	  </listitem>
	</itemizedlist>
      </listitem
> 
    </varlistentry>
  </variablelist>
  <section sn="kernel-userspace-tools">
    <title
>Userspace Tools</title>
    <title
>iproute</title>
    <para
>The IPv4 address deletion algorithm did not take the prefix length into account up to kernel version 2.6.12. Since this has changed the iproute2 tool now issues a warning if no prefix length is provided to warn about possible unintended deletions: </para>
<screen
>ip addr list dev eth0
4: eth0: &lt;BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    inet 10.0.0.3/24 scope global eth0
su -c 'ip addr del 10.0.0.3 dev eth0'
Warning: Executing wildcard deletion to stay compatible with old
      scripts. Explicitly specify the prefix length (10.0.0.3/32) to
      avoid this warning. This special behaviour is likely to disappear
      in further releases, fix your scripts!
</screen>
    <para
>The correct method of deleting the address and thus avoiding the warning is: </para>
<screen
>su -c 'ip addr del 10.0.0.3/24 dev eth0'
</screen>
    <para
>It has not been possible to tell if an interface is down administratively or because no carrier can be found (cable unplugged). The flag <computeroutput
>NO-CARRIER</computeroutput
> has been introduced that shows up as a link flag if the link is administratively up but no carrier can be found. </para>
    <para
>The <command
>ip</command
> command now supports a batch mode via the argument <option
>-batch</option
> just like the <command
>tc</command
> command to speed up batches of tasks. </para>
  </section>
</section>

<!-- cruft, but saved just in case :)
  <para>
   This section contains information relating to network connectivity.
  </para>
  <section id="sn-networking-networkmanager">
    <title
><filename
>NetworkManager</filename
></title>
    <para>
      The <command
>NetworkManager</command
> service allows computers
      such as laptops to automatically manage changing network
      connections.  It includes support for wireless networking.
    </para>
    <para>
      You must manually enable the <command
>NetworkManager</command>
      service.  To do so, type the following in a terminal window:
    </para>
<screen
>
su -c '/sbin/chkconfig --level 345 NetworkManager on; /sbin/service NetworkManager start'
su -c '/sbin/chkconfig --level 345 NetworkManagerDispatcher on; /sbin/service NetworkManagerDispatcher start'
</screen>
    <para>
      Enter the root password when prompted.
    </para>
    <para>
      Use the <application
>Network Monitor</application
> desktop applet
      to monitor and configure <command
>NetworkManager</command
>.  To load the
      applet in GNOME, right-click on the panel and select:
    </para>
    <para>
     <guimenuitem
>Add to Panel...</guimenuitem
><guimenuitem
>Network
     Monitor</guimenuitem>
    </para>
    <para>
      <command
>NetworkManager</command
> uses BIND to proxy DNS requests.
      Enabling the <command
>NetworkManager</command
> service also loads the
      <command
>named</command
> service as well.  By default BIND is
      configured as a cacheing service for the local system, and does
      not accept connections from other systems.  
    </para>
    <para>
	Note that some wireless network cards require drivers or firmware
	that cannot be included with &DISTRO;.  This software must be
	installed separately for <command
>NetworkManager</command
> to function.
    </para>
-->
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE overview-ru.xml ---
<section id="sn-overview">
  <title
>?????????? ???????? ????????????</title>
  <caution>
    <title
>???????????????????? ????????????????</title>
    <para
>???????????????????? ?????????????? ?????????????? ?????????????? ?????????????????????????? ?? &DISTRO; &DISTROVER; </para>
  </caution>
<!--
  <para>
    The following list includes brief summaries of some of the more
    significant aspects of &DISTRO; &DISTROVER;:
  </para>
  <itemizedlist>
    <listitem>
      <para>
	&DISTRO; &DISTROVER; contains the following changes:
      </para>
      <itemizedlist>
	<listitem>
	  <para>
	    Support for the PowerPC (PPC) architecture.
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GCC 4.0
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GNOME 2.10
	  </para>
	</listitem>
	<listitem>
	  <para>
	    KDE 3.4 &mdash; includes new accessibility features.  You
	    can manage these new features in <guimenu
>KDS Control
	      Center</guimenu
><guisubmenu
>Regional &amp;
	      Accessibility</guisubmenu
><guisubmenu
>Accessibility</guisubmenu
>.
	  </para>
	</listitem>
	<listitem>
	  <para>
	    Native Eclipse 3.1M6 (part of a free Java stack)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    MySQL 4.1
	  </para>
	</listitem>
	<listitem>
	  <para>
	    PHP 5.0
	  </para>
	</listitem>
	<listitem>
	  <para>
	    Xen 2 (virtualization to run multiple versions of an OS)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GFS 6.1-0.pre22 (cluster file system)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    Evince 0.2.1 (universal document viewer)
	  </para>
	</listitem>
	<listitem>
	  <para>
	    GDM 2.6 - Includes early login capability
	  </para>
	</listitem>
	<listitem>
	  <para>
	    &SEL; &mdash; This release includes coverage for 80 new
	    daemons by the targeted policy.  There are changes to the
	    handling of Booleans.  The targeted policy is enabled by
	    default.  For more information, refer to:  <ulink
	      url="http://fedora.redhat.com/docs/selinux-faq/"
>http://fedora.redhat.com/docs/selinux-faq/</ulink
>. 
	    This is the complete list of daemons covered by the targeted
	    policy:
	  </para>
	  <itemizedlist>
	    <listitem>
	      <para>
		<command
>NetworkManager</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>amanda</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>apache</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>apmd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>arpwatch</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>auditd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>bluetooth</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>canna</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>cardmgr</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>checkpolicy</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>chkpwd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>compat</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>comsat</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>consoletype</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>cpucontrol</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>cpuspeed</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>crond</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>cups</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>cvs</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>cyrus</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>dbskkd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>dbusd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>dhcpc</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>dhcpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>dictd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>dmidecode</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>dovecot</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>fingerd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>fsadm</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>ftpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>getty</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>hald</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>hostname</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>hotplug</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>howl</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>hwclock</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>i18n_input</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>ifconfig</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>inetd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>init</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>initrc</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>innd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>kerberos</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>klogd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>ktalkd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>kudzu</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>ldconfig</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>load_policy</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>login</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>lpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>mailman</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>modutil</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>mta</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>mysqld</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>named</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>netutils</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>nscd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>ntpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>portmap</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>postgresql</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>ppd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>privoxy</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>radius</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>radvd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>restorecon</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>rlogind</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>rpcd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>rpm</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>rshd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>rsync</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>samba</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>saslauthd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>sendmail</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>setfiles</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>slapd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>snmpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>squid</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>ssh</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>stunnel</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>syslogd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>telnetd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>tftpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>udev</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>updfstab</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>uucpd</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>webalizer</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>winbind</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>xdm</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>ypbind</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>ypserv</command>
	      </para>
	    </listitem>
	    <listitem>
	      <para>
		<command
>zebra</command>
	      </para>
	    </listitem>
	  </itemizedlist>
	</listitem>
      </itemizedlist>
    </listitem>
  </itemizedlist>
-->
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE package-movement-ru.xml ---


--- NEW FILE package-notes-ru.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "This header makes editing XML easier">
 <!ENTITY DISTRO "DISTRO">
 <!ENTITY DISTROVER "DISTROVER">
 <!ENTITY FEX "FEX">
 <!ENTITY FP "FP">
 <!ENTITY FC "FC">
 <!ENTITY LOCALVER "LOCALVER">
 <!ENTITY RHL "RHL">
 <!ENTITY SERVER-TOOLS SYSTEM "/dev/null">
 <!ENTITY KERNEL SYSTEM "/dev/null">
 <!ENTITY SECURITY SYSTEM "/dev/null">
 <!ENTITY SEL SYSTEM "/dev/null">
 <!ENTITY PRINTING SYSTEM "/dev/null">
 <!ENTITY DATABASE-SERVERS SYSTEM "/dev/null">
 <!ENTITY MULTIMEDIA SYSTEM "/dev/null">
 <!ENTITY WEB-SERVERS SYSTEM "/dev/null">
 <!ENTITY SAMBA SYSTEM "/dev/null">
 <!ENTITY XORG SYSTEM "/dev/null">
 <!ENTITY DEVELOPMENT-TOOLS SYSTEM "./development-tools.xml">

]>
-->
<section id="sn-package-notes">
  <title
>?????????????????? ?? ??????????????</title>
  <!--
  FIXME
  Needs updating of entire contents for FC5.
  -->
  <para
>?????????????????? ?????????????? ???????????????? ???????????????????? ?? ??????????????, ?????????????? ?????????????????????? ???????????????????????? ???????????????????? ?? &DISTRO; &DISTROVER;. ?????? ???????????????? ?????? ?????????????? ?? ???? ???? ????????????, ?????? ?? ?? Anaconda. </para>
  <caution>
    <title
>???????????????????? ????????????????</title>
    <para
>???????????????????? ?????????????? ?????????????? ?????????????? ?????????????????????????? ?? &DISTRO; &DISTROVER; </para>
  </caution>
  <section id="sn-basic-components">
    <title
>???????????????? ????????????????????</title>
    <para
>?? ???????? ???????????? ???????????????? ????????????????????, ?????????????????????? ?? ???????????????? ?????????????????????? ??????????????. </para>
    <section>
      <title
>?????????????????? &FEX;</title>
      <para
>&FEX; &mdash; ?????????? ???????????????? ?????????????? &FP;, ?? ???????????? ?????????????? ???????????????????? ???????????????????????? ?????????????? ?????????????????? ??????????????, ?????????????????????? &FC;. ?????????????????? &FEX; ???? ?????????????????? ???????????????? ?? &FC;, ?????????????? ?? ???????????? &LOCALVER;. </para>
      <para
>???????????? ???????????? ?? &FEX; ?????????? ???? ????????????: </para>
      <para>
	<ulink
	  url="http://fedoraproject.org/wiki/Extras"
>http://fedoraproject.org/wiki/Extras</ulink>
      </para>
      <para
> ???????? ?????? ?????????????????? ???????????????????? ??????????-???????????? ??????????????????, ???????????????????? ?? Fedora Extras, ???? ???????????? ?????????????????????????????? <command
>yum</command
>. </para>
<screen
><command
>yum install <replaceable
>&lt;packagename&gt;</replaceable
></command
>
</screen>
      <para
>?????????? <replaceable
>&lt;packagename&gt;</replaceable
> &mdash; ?????? ????????????, ?????????????? ???? ???????????? ????????????????????. ????????????????, ???????? ???? ???????????? ???????????????????? ?????????? <filename
>abiword</filename
>, ?????????????????? ?????????????? <command
>yum install abiword</command
>, ?? ?????? ?????????????????????????? ?????????????????? ?????????? ?? ?????? ?????? ??????????????????????. </para>
    </section>
    <section id="sn-audit-daemon">
      <title
>???????????? ???????????? <command
>auditd</command
> ?? ?????????? ????????????????</title>
      <para
>?????????? ????????????, auditd, ???????????? ???? ?????????????????? ??????????????. ?????????? auditd ????????????????, ???????? ???????????????????? ?????????????????? ???????????? ?? ???????? <filename
>/var/log/audit/audit.log</filename
>. ???????????????????? ?????????? ?????????? ?????????????????????? ?? <filename
>/etc/auditd.conf</filename
>. </para>
      <para
>?????????????????? AVC ?????? &SEL; ???????????????????????? ?????????? ???????????????????????????? ????????????. ???????????? ?????? ?????????????????? ?????????????????? ?? ?????????? <filename
>/var/log/audit/audit.log</filename
>. </para>
      <para
>?????????? auditd ???? ????????????????, ???????? ???????????????? ?????????????????? ???????????? ?? syslog. ?????? ?????????????? ???????????? ???????????????? ?? <filename
>/var/log/messages</filename
> ?? ???? ?????????? ?????????????????????? ?? ?????????????? <command
>dmesg</command
>. </para>
      <para
>???????????? ???????????????????? ???????????? ???????????????????????????? ?? PAM. ?????? ??????????????????, ???????????? ???????????????????? ???? ???????????? ?? ?????????????? ?????? ???????????????????? ???????????????? ?????????????? ???????????? ????????????????????????, ?????????? ???????????????? ?????????????????? ????????????. </para>
      <para
>?????????? ???????????????? ?????????? ?? ????????, ???? ???????????? ???? ?????????? ???????????????? ???????????????? ???????? ???????????????? <parameter
>audit=1</parameter
>. ?????????? ???????????????? ?????????? ?? ???? ?????????? ????????????????????, ?????? ?????????? ???????????????????????????? ?????????????????? ????????????????: </para>
<screen
><command
>auditctl -e 1</command
>
</screen>
    </section>
    <section id="sn-nptl">
      <title
>LinuxThreads ?? NPTL</title>
      <para
>?? ???????????? ???????????????????? ???????????? ???? ?????????????????? ???????????????????? ???????????????????? LinuxThreads, ??????, ???????????????????????????????? ?? ???????????????????????????? ?? &FC; &LOCALVER;, ???????????? ?????????????????????????? ???????????????????? ?????????????????? ?? ???????????????????? NPTL. </para>
      <para
>?? ???????????????????? ????????????????, ?????????????? ?? &RHL; 9, ???? ?????????????????? ???????????????????????????? ???????????????????? ?????????????? LinuxThreads, ?????? ?????? ?? ???????????????? ???????????????????????? ???????????? ??????????????????????????. ???????????????????????? ???????????????????? NPTL ?????????????????????? ?? ???????????????????? ?????????????????? ?????????????????????????? (?????????? ???????????????????????? <parameter
>-fexception</parameter
>, ???????? ?? ???????? C) ?? ?? ??????, ?????? ???????????? ?????? ?????????????????????? ???????????????????? ?????????????????????? ?? ???????????????????????? ???????????????? ???????????????????????????? ????????????????????. ?????????????? ??????????????, ?????? ???????????? ???? ?????????? ???????????????????????? <option
>-I/usr/include/nptl</option
> ?? <option
>-L/usr/lib{,64}/nptl</option
>. ????????????????, ?????? <parameter
>lib{,64}</parameter
> ?????????????? ???????????????????????? ?????? lib64 ???? ????????????????????, ?????? DSO ?????????????????????? ?? ?????????????????? <filename
>lib64/</filename
>, ?? <filename
>lib/</filename
> &mdash; ???? ??????????????????. </para>
      <para
>?? &FC; &LOCALVER; ?????? ?????? ???????????????? ?????????????? ??????, ???????????????????????? ?????????????????????? LinuxThreads. ?????? ?????????? ?????????? ???????????????????? ?????????? <filename
>linuxthreads-devel</filename
> ?? ???????????????? ?????????????????????? ???????????????? </para>
<screen
><option
>-I/usr/include/linuxthreads -L/usr/lib{,64}/linuxthreads</option
>
</screen>
       
      <para
>?????????? ???? ?????????? ???????????????? ???????????? glibc ?? libpgthread DSH, ?????????????????? ???????????????????? ?????????????????? ?????????? ????????????????????. ???????????? ???? ?????????? ???????????? ???????????????????? ?? ?????????????????? ?????????????????? ????????????????????: </para>
<screen
><envar
>LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads</envar
>
</screen>
      <para
>?????? ???????????????????????????? ???????????????????? ????????????????????, ?????? ?????? ???????????????????? ?????????????? ???????????????????? ???????????? ?? ??????????????. ??????????????, ????????????????, ???????????????? ??????????????????, ?????????????? ???? ?????????? ????????????????, ???????? ?????? ???????????????????? ?????????????????? ???????????????????? <envar
>DT_RPATH</envar
> (???????????????????????????????? ???????????????? <envar
>LD_LIBRARY_PATH</envar
>). </para>
      <para
>?????? ?????? ?????????????????? ???????????? ????????????????, ?????????????????? ???? LinuxThreads. ???? ?????? ?????????????? ??????????????????. </para>
      <important>
	<title
>??????????</title>
	<para
>?? FC5 ???? ?????????? ?????????????????? LinuxThreads ?? ?????????? ?????????????????????? ???????????????????? ?????? ?????????????????? ?? ??????, ?????????? ?????? ???????????????????????? NPTL. </para>
      </important>
      <para
>?? ??????????-????, ?????????????? ?? ?????????????????????????? NPTL ???? ???????????????????? ????????????????. </para>
    </section>
    <section>
      <title
>?????????????????? ???????? ???????????? <filename
>slocate</filename
></title>
      <para
>?????? ???????? ????????????, ???????????? ?????????????? <command
>locate</command
>, ???????????? ???? ?????????????????? ???? ??????????????????. ???????? ???? ???????????? ???????????????????????? <command
>locate</command
>, ?????????????????? ???????????????? ???????? ????????, ?????????? ?????? ?????????????????? <computeroutput
>DAILY_UPDATE</computeroutput
> ?? <filename
>/etc/updatedb.conf</filename
> ???????????????? <option
>yes</option
>. </para>
    </section>
    <section>
      <title
>?????????????????? ???????????????? ???????????????????????? ?? <filename
>openssh</filename
></title>
      <para
>?? &FC; &LOCALVER; ?????????????? ?????????? OpenSSH ???????????? 3.9, ?? ?????????????? ?????????????? ???????????????? ???????????????????? ?? ???????????????? ???????????? <filename
>~/.ssh/config</filename
>. ???????? ???????????????????? ?????? ???????????????? ?????? ?????????? ?????????? ???????????? ??????????????, <command
>ssh</command
> ???????????????? ???? ??????????. </para>
      <para
>?????????????????? ?? ??????, ?????? <filename
>~/.ssh/config</filename
> ?????????????????????? ?????????????????? ???????????????? <filename
>~/</filename
>, ?? ???????????????????? ?????????? ???????????????? 600. </para>
<screen
>ls -l ~/.ssh/config
-rw-------  1 username username 400 May  5 18:44 /home/username/.ssh/config
</screen>
      <para
>?????????????? <filename
>~/</filename
> &mdash; ?????????????? ?????????????????? ?????????????????? ???????????????? ????????????????????????, ???????????? <filename
>/home/username/</filename
>. </para>
      <para
>?????????? ??????????, OpenSSH ?????? ?????????????????????? ?? ???????????????? ?????????? ???? ?????????????????????? ???? ?????????????????? ?????????????????????????????? X11. ?????????? ?????????????????? ?????????????????????????????? X11, ???????????????????? ?????????????? ???????????????? <option
>-X</option
> ?????? <option
>-Y</option
>, ???????? ???????????????????? ???????????????? <option
>ForwardX11</option
> ?? ?????????? <filename
>~/.ssh/config</filename
>. </para>
      <para
>?????????????????? ???????????????? <command
>ssh</command
>, ?????????????????? ?? ???????????? <option
>-X</option
>, ????????????????. ?? OpenSSH 3.8 ?? ?????????? ?????????????????????????????? X11 ?????????????????????? ??????, ?????? ???????????????????? ???? ?????????????????? ???????????????? ?????? ???????????????????????? ??????????????. ?????????? ?????? ?????????????????????????????? X11 ???????????????????? ???????????? ???????????????? ?????? ???????????????????? ??????????????. ?????????????????? ????????????????????, ???? ???????????? ????????????????, ???????????? ?????????????????????????? ??????????????????. ?????????? ?????????????????????????? X11, ?????????? ???????????????????? ???????????????? ?????? ???????????????????? ??????????????, ???????????????? ssh ?? ???????????? <option
>-Y</option
> ???????????? <option
>-X</option
>, ?????? ?????????????? ???????????????? <option
>ForwardX11Trusted</option
> ?? ?????????? <option
>~/.ssh/config</option
>. </para>
    </section>
    <section id="sn-perl">
      <title
>?????????????????????????? ???????????? ?????? ???????????????? ?????????????????????????? Perl</title>
      <para
>?????????????????????????? ???????????? ?????? ???????????????? ?????????????????????????? <filename
>perl-5.8.0</filename
>, <filename
>perl-5.8.1</filename
> ?? <filename
>perl-5.8.2</filename
> ???????? ??????????????. ???????? ???? ?????????????????????? perl-????????????, ???????????????????????????????? ?????????? ?????????????? ???????????????? perl, ???? ???????????? ?????????????????????????????????? ????, ?????????????????? <filename
>perl-5.8.6</filename
>, ???????????????????? ?? &FC; &LOCALVER;. </para>
    </section>
&SERVER-TOOLS; &JAVA-PACKAGE; </section>
  <section id="sn-packages-core">
    <title
>???????????????? ????????????????????????</title>
    <para
>?? ???????? ?????????????? ?????????????? ???????????????? ???????????????????? ?????????????? &DISTRO;, ?????????????? ????????. </para>
    <section>
      <title
>yum</title>
      <para
>???????????? yum ???????????????????? ???????? ???????????? sqllite, ?????????????????? ???????? ???????????????????????????????????? ?????????????? ????????????????????. </para>
      <para
>?????????????????? Fedora Extras ???????????? ???? ?????????????????? ????????????????. </para>
    </section>
&KERNEL; &SECURITY; </section>
&DEVELOPMENT-TOOLS; &I18N; &PRINTING; &MULTIMEDIA; &ENTERTAINMENT; &WEB-SERVERS; &SAMBA; &XORG; &ENTERTAINMENT; </section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE printing-ru.xml ---
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE project-overview-ru.xml ---
  <section id="sn-whatitis">
    <title
>?????????? ?????????????? &PROJ;</title>
    <para
>?????????? ?????????????? &PROJ; ???????????????? ???????????????????? ?? ?????????????? Linux-???????????????????? ????????????, ?????????????????????????? ???????????????????????? ??????????????, ?????????????????? ???????????? ???? ???????????????????????? ?????????????????????? ?? ???????????????? ???????????????? ??????????. ???????????????????? ???????????????????? ?? ???????????????? ????????????. ???????????? ?????????????????? ?????????????????? ???????????? ?????????????? &DISTRO; ???????????????? 2-3 ???????? ?? ??????, ?? ???????????????????????? ?? ?????????????????????? ??????????????????????. ?????????????? ?????????????????? ???????????????? &RH; ???????????????????? ?????????????? ?? ???????????????????? &DISTRO;, ???????????????????? ?? ???????????????????? ???????????? ????????????????????, ?????? ?????? ???????? ???????????????? ??????????. ???????? ?????????? ???????????????? ??????????????, ?????? ???? ????????????????, ???????????????? ?? ????????????!
 ?????????? ???????????????????????? ??????????????, ?????????? ?????????????????????????????? ?????????????? ???????????????????? ???????????????????????? ?????????????????????? ?? ?????????? ?????????????????????????????? ?????? open-source ????????????????????. </para>
    <para
>???? ???????????????????????????? ?????????????????????? ???????????????????? ???? ??????-???????? ?????????????? &PROJ;: </para>
    <para>
      <ulink
	url="http://fedora.redhat.com/"
>http://fedora.redhat.com/</ulink>
    </para>
    <para
>???????????? ??????-??????????, ???????????????????? ?????????? ?????????????????? ???????????? ????????????????: </para>
    <itemizedlist>
      <listitem>
        <para
>fedora-list at redhat.com &mdash;  ?????? ?????????????????????????? ???????????? &DISTRO; </para>
      </listitem>
      <listitem>
        <para
>fedora-test-list at redhat.com &mdash; ?????? ???????????????? ?????????????? ???????????? &DISTRO; </para>
      </listitem>
      <listitem>
        <para
>fedora-devel-list at redhat.com &mdash; ?????? ??????????????????????????, ??????????????????????????, ?????????????????????????? </para>
      </listitem>
      <listitem>
        <para
>fedora-docs-list at redhat.com &mdash; ?????? ???????????????????? ?????????????? ???????????????????????? </para>
      </listitem>
    </itemizedlist>
    <para
>?????????? ?????????????????????? ???? ???????? ???? ???????? ??????????????, ?????????????????? ???????????????? ?????????????????? ???? ???????????? "subscribe" ?? ???????? ?????????????????? ???? ???????????? <computeroutput
><replaceable
>&lt;listname&gt;</replaceable
>-request</computeroutput
> (?????? <computeroutput
><replaceable
>&lt;listname&gt;</replaceable
></computeroutput
> &mdash; ???????? ???? ?????????????????????? ???????? ????????). </para>
    <para
>?????????? ???? ???????????? ?????????????????????? ?? ?????????? Web-??????????????????: </para>
    <para>
      <ulink url="http://www.redhat.com/mailman/listinfo/"
>http://www.redhat.com/mailman/listinfo/</ulink>
    </para>
    <para
>???????? ???? ???????? ?????????????????? ???? ???????????????? rhl-list, rhl-beta-list, rhl-devel-list ?????? rhl-docs-list ?? ??????????????, ???????? ???????????????? ?????????? ??????????????????. </para>
    <para
>?????????????? &PROJ; ?????????? ???????????????? ?????????????????? ?????????? IRC (Internet Relay Chat). IRC ??? ?????? ?????????? ?????????????? ?? ???????????????? ??????????????, ???????????????????????? ?????????????????? ??????????????????. ?????????????????????? IRC ???? ???????????? ???????????????????? ?? ?????????????????????? ???????????? ???? ???????????????? ???????????? ?????? ?????????????????????????? ?? ??????-???? ????????-????-????????. </para>
    <para
>?????????? ???????????????????? ?? ?????????????? ?????????????????????? ?????????????? &PROJ; ?????????? IRC, ???????????????????????? ?? ???????? IRC. ?????? ???????????? ???? ???????????? ???????????????????????? ?? ???????????????? IRC-?????????????? irc.freenode.net, ???????? ???????????? ?????????? ?????????????? ????????????, ?????????????????????????? ?????????? ?? ?????? ??????????????????????????. ???? ???????????????????????????? ?????????????????????? ???????????????????? ?? ??????-?????????? (<ulink url="http://www.freenode.net/"
>http://www.freenode.net/</ulink
>). ?????????????????? ?????????????? &PROJ; ??? ?????????????????????? ???????????? <filename
>#fedora</filename
>, ?? ?????????????????????????? ?????????????? ?????????? ?????????? ?????????? ???? ???????????? <filename
>#fedora-devel</filename
>. ?????????????????? ?????????????? ?????????????? ?????????? ?????????? ?????????? ?????????????????????? ????????????; ???????????????????? ???? ???????? ?????????? ?????????? ???? ?????????????????? ???????? ????????????????. </para>
    <para
>?????? ????????, ?????????? ???????????????? ???? ???????????? <filename
>#fedora</filename
>, ?????? ?????????????????????? ???????????????????????????????? ?????? ?????????????????? (<firstterm
>????????????????</firstterm
>). ?????????????????????????????? ???????????????????? ???? ????????????????, ?????????????????????????? ?? ???????????? (<command
>/join</command
>). </para>
    <note>
      <title
>??????????????????</title>
      <para
>???????????????? &RH; ???? ?????????????????? IRC-???????????????? ?????????????? &PROJ; ?????? ???? ????????????????????. </para>
    </note>
  </section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


***** Error reading new file: [Errno 2] No such file or directory: 'RELEASE-NOTES-ru.xml'

--- NEW FILE samba-ru.xml ---
<section id="sn-samba">
  <title
>Samba (?????????????????????????? ?? ???????????????? ???????????????? Windows)</title>
  
  <para
>This section contains information related to Samba, the suite of software that enables Linux to interact with Microsoft Windows systems. </para>

  <para
>Browsing of Windows shares (also known as SMB browsing) fails on &DISTRO; &DISTROVER; systems that have the standard firewall configured. This is most easily noticed in the failure of the desktop to display shares. </para>

  <para
>The firewall disrupts the broadcast mode of SMB browsing, which is the default. There are two workarounds: </para>

  <itemizedlist>
    <listitem>
      <para
>Configure a WINS server on the network, and set the "wins server" option in smb.conf to the address of the WINS server. </para>
    </listitem>
    <listitem>
      <para
>Disable the firewall. </para>
    </listitem>
  </itemizedlist>

  <warning>
    <title
>Disabling the firewall may make your system vulnerable</title
>  
    <para
>Make sure you fully understand the risks before undertaking this step. </para>
  </warning>

  <para
>For additional information, refer to the following bug report: </para>
  
  <para>
    <ulink url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478"
>https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478</ulink>
  </para>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE security-ru.xml ---
<section id="sn-security">
  <title
>????????????????????????</title>
  <para
>?? ???????? ?????????????? ???????????????????? ?????????????????? ???????????????? ???????????????????????? ???? &FC;. </para>
  <para
><computeroutput
>Pam_stack</computeroutput
> is deprecated. More details available from fedora-test-list (<ulink url="http://www.redhat.com/mailman/listinfo/fedora-test-list"
>http://www.redhat.com/mailman/listinfo/fedora-test-list</ulink
> </para>
  <section id="sn-security-highlights">
    <title
>Security Highlights</title>
    <para
>?? ???????? ?????????????? ???????????????????? ?????????????????? ???????????????? ???????????????????????? ???? &FC;. </para>
    <para
>???????????? ???????????????? ?????????????????????? ???????????????? ??????????????????????????????, ?? ???????????????????????? ???????? <filename
>/etc/pki/</filename
>. ????????????????????????, ?????????????????????? ????????????????????, ???????????? ?????????????????????? ???????? ???????????????? ??????????????????????. </para>
    <para
>OpenSSL: the <filename
>/usr/share/ssl/</filename
> contents have moved to <filename
>/etc/pki/tls/</filename
> and <filename
>/etc/pki/CA/</filename
>. </para
>        
    <para
>Dovecot: A dovecot-openssl.cnf file is automatically installed in <filename
>/etc/pki/dovecot/</filename
>. </para>
  </section>
  <section id="sn-security-selinux-changes">
    <title
>SELinux Changes</title>
    <para
>MCS SELinux is in somewhere. Major highlight. For more information, read this informative article: </para>
    <para>
      <ulink
	url="http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/msg00001.html"
>http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/msg00001.html</ulink>
    </para>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE server-tools-ru.xml ---
<section id="sn-server-sys-config">
  <title
>?????????????????????? ?????????????????? ?????????????? ?? ??????????????</title>
  <caution>
    <title
>???????????????????? ????????????????</title>
    <para
>???????????????????? ?????????????? ?????????????? ?????????????? ?????????????????????????? ?? &DISTRO; &DISTROVER; </para>
  </caution>
  <para
>?? ???????? ?????????????? ???????????????????? ?????????????????? ?? ???????????????????? ?????????????????? ?????????????????????? ?????????????? ?????????????????? ?????????????? ?? ?????????????? ?? &FC;. </para>
  <section id="sn-system-config-lvm">
    <title
><application
>system-config-lvm</application
></title>
    <para
>?????????? ???????????????????? LVM <application
>system-config-lvm</application
> ???????????????? ?????????????????? ?????????????????????? ????????????. </para>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE splash-ru.xml ---
<section id="sn-splash">
  <title
>?????????? ???????????????????? ?? &FC; &LOCALVER;</title>
  <caution>
    <title
>???????????????????? ????????????????</title>
    <para
>???????????????????? ?????????????? ?????????????? ?????????????? ?????????????????????????? ?? &DISTRO; &DISTROVER; </para>
  </caution>
  <para
>&FC; &mdash; ?????????????????? ????????????????????, ?????????????????????????? ???????????????????????? ?? ???????????????????? ?????????????????????????? ??????????????????, ???????????????????? ???? Linux. ???????????? &FP; &mdash; ???????????? ?? ???????????????? ??????????, ???????????????????????? &RH; ?? ???????????????????????????? ?????????????????????? &FED;, ?? ???????????? ???????????????? ???????????????????? ?????????? ?????????????????? ???????????????????? ?? ??????????????????. </para>
  <tip>
    <title
>?????????? ?????????? ?????????????????? ?? ?????????????? ?????????????????? ?? ????????</title>
    <para
>?????? ?????????????????? ?? ?????????????? ?????????? ???????? ??????????????????. ???????????????? ???????????????? <ulink url="http://fedora.redhat.com/docs/release-notes/"
>http://fedora.redhat.com/docs/release-notes/</ulink
> ?????? ?????????????????? ?????????? ?????????? ?????????????????? ?? ?????????????? &DISTRO; &DISTROVER; </para>
  </tip>

<!-- save for when the FIG is actually updated
  <note>
    <title
>Installation Guide Updated</title>
    <para>
      New for this release is the <citetitle
>&FC; &LOCALVER;
	&IG;</citetitle
>.  This guide is useful for users of all levels
      and can be found at this URL:
    </para>
    <para>
      <ulink url="http://fedora.redhat.com/docs/fedora-install-guide-en/"
>http://fedora.redhat.com/docs/fedora-install-guide-en/</ulink>
    </para>
  </note
>  
-->
  <para
>?????????? ???????????????? ???????????????????????????? ???????????????????? ?? &FED;, ???????????????????? ?? ?????????????????? Web-??????????????????: </para>
  <itemizedlist>
<!-- FIXME Return when the section is updated
    <listitem>
      <para>
	<xref linkend="sn-new-in-fc"/>
      </para>
    </listitem>
-->
    <listitem>
      <para
><xref linkend="sn-intro"/> &mdash; ?????????????????????? ?????????????????? ?? ???????????? </para>
    </listitem>
    <listitem>
      <para
>?????????????? ?? ?????????????????? (<ulink url="http://fedora.redhat.com/participate/communicate/"
>http://fedora.redhat.com/participate/communicate/</ulink
>) </para>
    </listitem>
    <listitem>
      <para
>?????????????? ?? ?????????????? &FP; (<ulink url="http://fedora.redhat.com/participate/"
>http://fedora.redhat.com/participate/</ulink
>) </para>
    </listitem>
    <listitem>
      <para
>?? ?????????????? &FP; (<ulink url="http://fedora.redhat.com/about/"
>http://fedora.redhat.com/about/</ulink
>) </para>
    </listitem>
  </itemizedlist>
<!-- commented out until the content can be updated
  <section id="sn-new-in-fc">
    <title
>New in &FC; &LOCALVER;</title>
    <para>
      &FC; &LOCALVER; is the latest version of the free and popular &FC;
      platform with a number of unique features and significant
      improvements over previous versions.  This section provides an
      overview of the major highlights in this release.
    </para>
    <itemizedlist>
      <listitem>
	<para>
	  Desktop Enhancements &mdash; The &FED; desktop brings to you
	  the latest software such as GNOME 2.10 and KDE 3.4 with a new
	  look and feel.  GNOME has the new simple and elegant Clearlooks
	  default theme that is inspired by the classic Red Hat
	  Bluecurve theme, as shown in <xref
	  linkend="ex-desktop-screenshot-clearlooks"/>.
	</para>
	<example id="ex-desktop-screenshot-clearlooks">
	  <title
>New desktop featuring Clearlooks and Evince</title>
	  <mediaobject id="txt-fedora-desktop-screenshot">
	    <imageobject>
	      <imagedata fileref="./figs/Fedora_Desktop.eps" format="EPS"/>
	    </imageobject>
	    <imageobject>
	      <imagedata fileref="./figs/Fedora_Desktop.png" format="PNG"/>
	    </imageobject>
	    <textobject>
	      <para>
		Screenshot of Fedora desktop showing Firefox in the
		background and the new universal document viewer Evince
		in the foreground.  Evince is displaying Lawrence
		Lessig's Free Culture.
	      </para>
	    </textobject>
	  </mediaobject>
	</example
>      
      </listitem>
      <listitem>
	<para>
	  Improved Productivity
	</para>
	<itemizedlist>
	  <listitem>
	    <para>
	      Evince (<ulink
		url="http://www.gnome.org/projects/evince/"
>http://www.gnome.org/projects/evince/</ulink
>) 
	      is a document viewer for multiple document formats such as
	      pdf, postscript, and many others.  Evince replaces a whole
	      category of document viewers with a single simple
	      application.
	    </para>
	  </listitem>
	  <listitem>
	    <para>
	      OpenOffice.org 2.0 (<ulink
		url="http://www.openoffice.org/product2/index.html"
>http://www.openoffice.org/product2/index.html</ulink
>) 
	      is an office productivity suite.  This latest version
	      includes several enhancements such as improved Microsoft
	      Office compatibility, completely revamped Impress
	      presentation software, and native support for the
	      OpenDocument format. This version also introduces Base, a
	      fully integrated database management software. You can
	      find the extensive list of new features at <ulink
		url="http://marketing.openoffice.org/2.0/featureguide.html"
>http://marketing.openoffice.org/2.0/featureguide.html</ulink
>.</para>
	  </listitem>
	  <listitem>
	    <para>
	      Eclipse 3.1 is an open and extensible software development
	      platform that is an Integrated Development Environment
	      (<acronym
>IDE</acronym
>) useful for programming in any
	      language. 
	    </para>
	  </listitem>
	</itemizedlist>
      </listitem>
      <listitem>
	<para>
	  Support for PowerPC (PPC) Architecture &mdash; Refer to <xref
	    linkend="sn-hardware-reqs-ppc"/> and <xref
	    linkend="sn-install-notes-ppc"/>.
	</para>
      </listitem>
      <listitem>
	<para>
	  Improved Security &mdash; &SEL; is a security architecture
	  that protects applications and users through finely grained
	  mandatory security controls.  The default targeted policy has
	  been improved to cover 80 additional daemons. You can read
	  more in the technical release notes
	  <xref linkend="sn-overview"/>.
	</para>
      </listitem>
      <listitem>
	<para>
	  Integrated Clustering Technology &mdash; Global File System
	  (<acronym
>GFS</acronym
>) is an open source clustering file
	  system that allows a cluster of Linux servers to share a
	  common storage pool. &FC; &LOCALVER; has integrated GFS within
	  the system to manage your storage in an efficient way.  You
	  can read more at <ulink
	    url="http://www.redhat.com/software/rha/gfs/"
>http://www.redhat.com/software/rha/gfs/</ulink
> 
	  and <ulink
	    url="http://www.redhat.com/docs/manuals/enterprise/"
>http://www.redhat.com/docs/manuals/enterprise/</ulink
>.
	</para>
      </listitem>
      <listitem>
	<para>
	  Built-in Virtualization &mdash; Xen is a virtual machine that
	  can securely run multiple operating systems in their own
	  sandboxed domains.  Xen has been integrated into &FC; to work
	  in a seamless fashion.  You can read more about Xen at <ulink
	    url="http://fedora.redhat.com/projects/virtualization/"
>http://fedora.redhat.com/projects/virtualization/</ulink
>.
	</para>
      </listitem>
      <listitem>
	<para>
	  Solid Platform &mdash; &FC; &LOCALVER; includes and integrates
	  the latest 4.0 version of GNU Compiler Collection, which has a
	  rewritten optimization infrastructure and improved support for
	  a native open source Java software stack.  This stack includes
	  parts of OpenOffice.org 2.0., Eclipse, and Apache Jakarta,
	  among others.
	</para>
      </listitem>
    </itemizedlist>
  </section>
  <section id="sn-why-no-mp3">
    <title
>MP3 Codecs and Other Patented or Closed Source Software</title>
    <para>
      This section is a brief explanation of why certain software is not
      included in &FC; or &FEX;.  This information was drawn directly
      from the canonical wiki page:
    </para>
    <para>
      <ulink
	url="http://fedoraproject.org/wiki/ForbiddenItems"
>http://fedoraproject.org/wiki/ForbiddenItems</ulink>
    </para>
    <para>
      A frequent question of the &FP; is why certain items are not
      included in &FC; or &FEX;. This briefly explains some of the
      reasons.
    </para>
    <para>
      Other items, such as file systems support, requires community
      participation.  For more information, refer to <ulink
	url="http://fedoraproject.org/wiki/Wishlist"
>http://fedoraproject.org/wiki/Wishlist</ulink>
    </para>
    <variablelist>
      <varlistentry>
	<term
>NTFS</term>
	<listitem>
	  <para>
	    NTFS Support is not included in the &FC; kernel because of
	    patent concerns. Using a file system natively supported by
	    Linux such as ext3 is a better option. If you must share
	    files between Windows and Linux on a single system, use
	    FAT/FAT32 (vfat) instead. For sharing across a network,
	    Samba is a good option.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term
>MP3 encode/decode functionality</term>
	<listitem>
	  <para>
	    MP3 support is not included in any &FC; application because
	    MP3 is heavily patented in several regions including the
	    United States. The patent holder is unwilling to give an
	    unrestricted patent grant, as required by the GPL. Other
	    platforms might have paid the royalty and/or included
	    proprietary software. Other Linux distributions not based in
	    a region affected by the patent might ship MP3
	    decoders/encoders. However, &FC; cannot and does not ship
	    MP3 decoders/encoders in order to serve the goal of shipping
	    only free and open source software. Using other open source
	    formats such as Ogg Vorbis (a lossy codec that has better
	    quality than MP3) or FLAC (a lossless codec) is highly
	    recommended.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term
>NVIDIA 3D drivers</term>
	<listitem>
	  <para>
	    The NVIDIA 3D drivers are closed source. &FC; does not
	    include proprietary binaries. Consider using an Intel or any
	    other manufacturer that supports open source cards with full
	    specifications and/or source code.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term
>ATI 3D drivers</term>
	<listitem>
	  <para>
	    The ATI 3D drivers are closed source. &FC; does not include
	    proprietary binaries. Consider using an Intel or any other
	    manufacturer that supports open source cards with full
	    specifications and/or source code.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term
>RealPlayer</term>
	<listitem>
	  <para>
	    RealPlayer is a closed source application. &FC; does not
	    include proprietary binaries. Consider using open source
	    codecs that do not have patent restrictions.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term
>DVD video playback</term>
	<listitem>
	  <para>
	    DVD video playback (of CSS encrypted DVDs) may violate the
	    US DMCA (refer to <ulink
	      url="http://en.wikipedia.org/wiki/DMCA"
>http://en.wikipedia.org/wiki/DMCA</ulink
>) 
	    because it may be considered circumventing an encryption
	    mechanism. Additionally, MPEG2 is a patented codec, so even
	    DVDs without encryption cannot be played. Consider using
	    open source unencrypted mediums such as Ogg Theora formats.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term
>Mono</term>
	<listitem>
	  <para>
	    Mono packages are not currently included due to potential
	    legal issues. (Pending more input.) Applications can be
	    written in other languages that are open source, such as
	    Python, Perl, or Ruby. Java is cross-platform and GCJ is a
	    relatively mature open source implementation of it. These
	    are not direct one-to-one equivalents with .NET but might
	    serve your purpose.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term
>Cryptology (mcrypt)</term>
	<listitem>
	  <para>
	    Some cryptology related packages such as mcrypt are not
	    included within &FC; due to US export restrictions. Consider
	    using non-restricted cryptographical methods instead.
	  </para>
	</listitem>
      </varlistentry>
      <varlistentry>
	<term
>szip</term>
	<listitem>
	  <para>
	    The szip license is too restrictive for inclusion in &FEX;.
	    Use other open source alternatives.
	  </para>
	</listitem>
      </varlistentry>
    </variablelist>
    <para>
      In conclusion:
    </para>
    <itemizedlist>
      <listitem>
	<para
> If it is proprietary, it cannot be included in &FED;.
	</para>
      </listitem>
      <listitem>
	<para>
	  If it is legally encumbered, it cannot be included in &FED;.
	</para>
      </listitem>
      <listitem>
	<para>
	  If it violates US Federal law, it cannot be included in &FED;.
	</para>
      </listitem>
    </itemizedlist>
    <para>
      Of course, the logical followup is: "But I want to get foo and do
      bar, how can I do one of the items listed above?"
    </para>
    <para>
      The unofficial <ulink
	url="http://fedorafaq.org"
>http://fedorafaq.org</ulink
> provides
      useful answers on commonly asked questions. However, these are
      completely unsupported by the &FP;. The &FP; encourages using free
      and open source software.
    </para>
    <para>
      The binary only drivers can be acquired from the vendors. You can
      find many interesting things with Google.
    </para>
  </section>
-->
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE web-servers-ru.xml ---
<section id="sn-web-servers">
  <title
>Web-??????????????</title>
  <para
>?? ???????? ???????????? ???????????????? ????????????????????, ?????????????????????? ?? Web-??????????????????????. </para>
  <section>
    <title
><command
>httpd</command
></title>
    <para
>The following changes have been made to the default <command
></command
>httpd configuration: </para>
    <itemizedlist>
      <listitem>
	<para
>The <computeroutput
>mod_cern_meta</computeroutput
> and <computeroutput
>mod_asis</computeroutput
> modules are no longer loaded by default. </para>
      </listitem>
      <listitem>
	<para
>The <computeroutput
>mod_ext_filter</computeroutput
> module is now loaded by default </para>
      </listitem>
    </itemizedlist>
  </section>
</section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- NEW FILE xorg-ru.xml ---
<section id="sn-xwindows">
  <title
>?????????????? X Window (??????????????????????)</title>
  <caution>
    <title
>???????????????????? ????????????????</title>
    <para
>???????????????????? ?????????????? ?????????????? ?????????????? ?????????????????????????? ?? &DISTRO; &DISTROVER; </para>
  </caution>
  <para
>???????? ???????????? ???????????????? ????????????????????, ???????????????????? ???????????????????? ?????????????? X Window, ???????????????????? ?? &DISTRO;. </para>
  <section id="sn-xwindows-xorg">
    <title
><filename
>xorg-x11</filename
></title>
    <para
>Users new to the X.org X11 implementation should take note of a few differences between it and the XFree86.org X11 implementation which shipped in previous &RH; and &FED; operating systems. In particular, the names of some files have changed: </para>
    <para
>X Server Binary: </para>
    <itemizedlist>
      <listitem>
	<para
>XFree86 X11: <filename
>XFree86</filename
></para>
      </listitem>
      <listitem>
	<para
>X.org X11: <filename
>Xorg</filename
></para>
      </listitem>
    </itemizedlist>
    <para
>X Server Configuration File: </para>
    <itemizedlist>
      <listitem>
	<para
>XFree86 X11: <filename
>/etc/X11/XF86Config</filename
></para>
      </listitem>
      <listitem>
	<para
>X.org X11: <filename
>/etc/X11/xorg.conf</filename
></para>
      </listitem>
    </itemizedlist>
    <para
>X Server Log File: </para>
    <itemizedlist>
      <listitem>
	<para
>XFree86 X11: <filename
>/var/log/XFree86.<replaceable
>$DISPLAY</replaceable
>.log</filename
></para>
      </listitem>
      <listitem>
	<para
>X.org X11: <filename
>/var/log/Xorg.<replaceable
>$DISPLAY</replaceable
>.log</filename
></para>
      </listitem>
    </itemizedlist>
    <para
>When configuring or troubleshooting your X server configuration, be sure that you are using the correct files. </para>
    <para
>There has been some confusion regarding font-related issues under the X Window System in recent versions of &DISTRO; (and versions of &RHL; before it.) At the present time, there are two font subsystems, each with different characteristics: </para>
    <itemizedlist>
      <listitem>
	<para
>The original (15+ year old) subsystem is referred to as the <firstterm
>core X font subsystem</firstterm
>. Fonts rendered by this subsystem are not anti-aliased, are handled by the X server, and have names such as: <computeroutput
>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</computeroutput
> </para>
      </listitem>
      <listitem>
	<para
>The newer font subsystem is known as <firstterm
>fontconfig</firstterm
>, and allows applications direct access to the font files. Fontconfig is often used along with the <filename
>Xft</filename
> library, which allows applications to render fontconfig fonts to the screen with antialiasing. Fontconfig uses more human-friendly names such as: <computeroutput
>Luxi Sans-10</computeroutput
> </para>
      </listitem>
    </itemizedlist>
    <para
>Over time, fontconfig and <filename
>Xft</filename
> will replace the core X font subsystem. At the present time, applications using the Qt 3 or GTK 2 toolkits (which would include KDE and GNOME applications) use the fontconfig and Xft font subsystem; almost everything else uses the core X fonts. </para>
    <para
>In the future, &FC; may support only fontconfig/Xft in place of the XFS font server as the default local font access method. </para>
    <note>
      <title
>??????????????????</title>
      <para
>An exception to the font subsystem usage outlined above is OpenOffice.org, which uses its own font rendering technology. </para>
    </note>
    <para
>The steps to add new fonts to &DISTRO; &DISTROVER; depend on the fonts subsystem this is going to use the new fonts. For the core X font subsystem: </para>

    <procedure>
      <step>
	<para
>Create the <filename
>/usr/share/fonts/local/</filename
> directory (if it doesn't already exist): </para>
<screen
><command>mkdir /usr/share/fonts/local/</command>
</screen>
      </step>
      <step>
	<para
>Copy the new font file into <filename
>/usr/share/fonts/local/</filename
> </para>
      </step>
      <step>
	<para
>Update the font information by issuing the following commands (note that, due to formatting restrictions, the following commands may appear on more than one line; in use, each command should be entered on a single line): </para>
<screen
><command>ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</command>
<command>mkfontdir /usr/share/fonts/local/</command>
</screen>
      </step>
      <step>
	<para
>If you had to create <filename
>/usr/share/fonts/local/</filename
>, you must then add it to the X font server (<command
>xfs</command
>) path: </para>
<screen
><command>chkfontpath --add /usr/share/fonts/local/</command>
</screen>
      </step>
    </procedure>
    <para
>Adding new fonts to the fontconfig font subsystem is more straightforward; the new font file only needs to be copied into the <filename
>/usr/share/fonts/</filename
> directory (individual users can modify their personal font configuration by copying the font file into the <filename
>~/.fonts/</filename
> directory). </para>
    <para
>After the new font has been copied, use <command
>fc-cache</command
> to update the font information cache: </para>
<screen
><command>fc-cache <replaceable>&lt;directory&gt;</replaceable></command>
</screen>
    <para
>(Where <command
><replaceable
>&lt;directory&gt;</replaceable
></command
> would be either the <filename
>/usr/share/fonts/</filename
> or <filename
>~/.fonts/</filename
> directories.) </para>
    <para
>Individual users may also install fonts graphically, by browsing <command
>fonts:///</command
> in <application
>Nautilus</application
>, and dragging the new font files there. </para>
    <note>
      <title
>??????????????????</title>
      <para
>If the font filename ends with "<filename
>.gz</filename
>", it has been compressed with <command
>gzip</command
>, and must be decompressed (with the <command
>gunzip</command
> command) before the fontconfig font subsystem can use the font. </para>
    </note
>      
    <para
>Due to the transition to the new font system based on fontconfig/Xft, GTK+ 1.2 applications are not affected by any changes made via the <guilabel
>Font Preferences</guilabel
> dialog. For these applications, a font can be configured by adding the following lines to the file <filename
>~/.gtkrc.mine</filename
>: </para>
<screen
><computeroutput>style "user-font" {
fontset = "<replaceable>&lt;font-specification&gt;</replaceable>"
}
widget_class "*" style "user-font"</computeroutput>
</screen>
    <para
>(Where <command
><replaceable
>&lt;font-specification&gt;</replaceable
></command
> represents a font specification in the style used by traditional X applications, such as "<computeroutput
>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput
>".) </para>
  </section>
</section>

<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Thu Nov 10 22:30:14 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Thu, 10 Nov 2005 17:30:14 -0500
Subject: rpm-guide rpm-guide-advanced-packaging-en.xml, 1.3,
	1.4 rpm-guide-creating-rpms-en.xml, 1.3,
	1.4 rpm-guide-customizing-rpm-en.xml, 1.2,
	1.3 rpm-guide-dependencies-en.xml, 1.2,
	1.3 rpm-guide-extra-packaging-tools-en.xml, 1.3,
	1.4 rpm-guide-management-software-en.xml, 1.3,
	1.4 rpm-guide-online-resources-en.xml, 1.3,
	1.4 rpm-guide-other-linuxes-en.xml, 1.3,
	1.4 rpm-guide-other-os-en.xml, 1.3,
	1.4 rpm-guide-packaging-guidelines-en.xml, 1.3,
	1.4 rpm-guide-programming-c-en.xml, 1.3,
	1.4 rpm-guide-programming-perl-en.xml, 1.3,
	1.4 rpm-guide-programming-python-en.xml, 1.4,
	1.5 rpm-guide-rpmbuild-en.xml, 1.3,
	1.4 rpm-guide-scripting-en.xml, 1.3,
	1.4 rpm-guide-specfile-syntax-en.xml, 1.2,
	1.3 rpm-guide-specfiles-en.xml, 1.3,
	1.4 rpm-guide-transactions-en.xml, 1.3,
	1.4 rpm-guide-using-rpm-db-en.xml, 1.3,
	1.4 rpm-guide-using-rpm-en.xml, 1.3, 1.4
Message-ID: <200511102230.jAAMUEc5022057@cvs-int.fedora.redhat.com>

Author: elliss

Update of /cvs/docs/rpm-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22002

Modified Files:
	rpm-guide-advanced-packaging-en.xml 
	rpm-guide-creating-rpms-en.xml 
	rpm-guide-customizing-rpm-en.xml rpm-guide-dependencies-en.xml 
	rpm-guide-extra-packaging-tools-en.xml 
	rpm-guide-management-software-en.xml 
	rpm-guide-online-resources-en.xml 
	rpm-guide-other-linuxes-en.xml rpm-guide-other-os-en.xml 
	rpm-guide-packaging-guidelines-en.xml 
	rpm-guide-programming-c-en.xml 
	rpm-guide-programming-perl-en.xml 
	rpm-guide-programming-python-en.xml rpm-guide-rpmbuild-en.xml 
	rpm-guide-scripting-en.xml rpm-guide-specfile-syntax-en.xml 
	rpm-guide-specfiles-en.xml rpm-guide-transactions-en.xml 
	rpm-guide-using-rpm-db-en.xml rpm-guide-using-rpm-en.xml 
Log Message:
Bulk replaced "Chapter X" and "Appendix Y" references with links




Index: rpm-guide-advanced-packaging-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-advanced-packaging-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-advanced-packaging-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-advanced-packaging-en.xml	10 Nov 2005 22:30:06 -0000	1.4
@@ -75,7 +75,7 @@
       Cross Reference
     </para>
     <para>
-      Chapter 6 covers more on dependencies. The Obsoletes dependencies
+      <xref linkend="ch-dependencies"/>  covers more on dependencies. The Obsoletes dependencies
       are usually only used when a package is renamed, such as the
       apache package becoming the httpd package, starting in &RH;
       Linux 8.0. The httpd package obsoletes the apache package.
@@ -345,7 +345,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 14 covers a common problem of handling circular
+        <xref linkend="ch-packaging-guidelines"/>  covers a common problem of handling circular
         dependencies using prerequisites.
       </para>
     </sect2>
@@ -408,7 +408,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 14 covers how to turn off the automatic generation of
+        <xref linkend="ch-packaging-guidelines"/>  covers how to turn off the automatic generation of
         dependencies.
       </para>
     </sect2>
@@ -532,7 +532,7 @@
       removed.
     </para>
     <para>
-      The anonftp package, mentioned in Chapter 6, has a lot of
+      The anonftp package, mentioned in <xref linkend="ch-dependencies"/> , has a lot of
       triggers. Many of these set up a number of commands to be locally
       available to the anonftp package. This networking package is also
       closely tied to the version of the C library, glibc, as shown in
@@ -866,7 +866,7 @@
     </para>
     <para>
       *Control the tests used to verify each file, as described in
-      Chapter 10
+      <xref linkend="ch-specfiles"/> 
     </para>
     <para>
       *Create a verify script that performs other tests
@@ -898,7 +898,7 @@
       Cross Reference
     </para>
     <para>
-      See Chapter 5 for more on package verification.
+      See <xref linkend="ch-using-rpm-db"/>  for more on package verification.
     </para>
   </sect1>
   <sect1>
@@ -1187,7 +1187,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 10 covers the %setup macro and lists the available
+        <xref linkend="ch-specfiles"/>  covers the %setup macro and lists the available
         options.
       </para>
     </sect2>
@@ -1207,7 +1207,7 @@
       Cross Reference
     </para>
     <para>
-      Chapter 19 covers using RPM on other versions of Linux.
+      <xref linkend="ch-other-linuxes"/>  covers using RPM on other versions of Linux.
     </para>
     <para>
       With a relocatable package, though, you allow the user to redefine
@@ -1295,7 +1295,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 4 covers how to install or upgrade packages into
+        <xref linkend="ch-using-rpm"/>  covers how to install or upgrade packages into
         different directories using the --relocate and --prefix options.
       </para>
     </sect2>
@@ -1356,7 +1356,7 @@
       Cross Reference
     </para>
     <para>
-      See Chapter 21 for more on macro file locations, and Chapters 19
+      See <xref linkend="ch-customizing-rpm"/>  for more on macro file locations, and Chapters 19
       and 20 for more on using RPM on other versions of Linux and other
       operating systems, respectively.
     </para>
@@ -1417,7 +1417,7 @@
       </para>
       <para>
         Many of the macros you will test this way are set up with the
-        --with command-line parameter. See Chapter 19 for details.
+        --with command-line parameter. See <xref linkend="ch-other-linuxes"/>  for details.
       </para>
     </sect2>
     <sect2>
@@ -1537,7 +1537,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 21 covers RPM architecture and operating system names.
+        <xref linkend="ch-customizing-rpm"/>  covers RPM architecture and operating system names.
       </para>
       <para>
         You can pass more than one architecture name, separated by


Index: rpm-guide-creating-rpms-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-creating-rpms-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-creating-rpms-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-creating-rpms-en.xml	10 Nov 2005 22:30:06 -0000	1.4
@@ -196,7 +196,7 @@
         number of bundles.
       </para>
       <para>
-        As covered in Chapter 2, a major tenet of the philosophy behind
+        As covered in <xref linkend="ch-intro-rpm"/> , a major tenet of the philosophy behind
         RPM is to start with pristine???unmodified--sources. You may
         need to patch or customize the sources for your environment, but
         you can always go back to the original sources.
@@ -791,7 +791,7 @@
         Cross Reference
       </para>
       <para>
-        See Chapter 21 for more on the use of the rpmrc settings.
+        See <xref linkend="ch-customizing-rpm"/>  for more on the use of the rpmrc settings.
       </para>
       <para>
         For now, it is easiest to just change to the /usr/src/redhat
@@ -1544,7 +1544,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 12 covers a number of addition options for the rpmbuild
+        <xref linkend="ch-rpmbuild"/>  covers a number of addition options for the rpmbuild
         command that you can use to customize the build.
       </para>
     </sect2>
@@ -1636,7 +1636,7 @@
       Cross Reference
     </para>
     <para>
-      See the on "Verifying Installed RPM Packages" section in Chapter 5
+      See the on "Verifying Installed RPM Packages" section in <xref linkend="ch-using-rpm-db"/> 
       for more on the -V option.
     </para>
   </sect1>


Index: rpm-guide-customizing-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-customizing-rpm-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-guide-customizing-rpm-en.xml	26 Oct 2005 01:54:11 -0000	1.2
+++ rpm-guide-customizing-rpm-en.xml	10 Nov 2005 22:30:06 -0000	1.3
@@ -61,7 +61,7 @@
     </para>
     <para>
       The macro syntax is used in the query formats introduced in
-      Chapter 5.
+      <xref linkend="ch-using-rpm-db"/> .
     </para>
     <sect2>
       <title>Defining macros</title>
@@ -176,7 +176,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 10 covers spec files.
+          <xref linkend="ch-specfiles"/>  covers spec files.
         </para>
         <para>
           In addition to these options, you can use a syntax of %{-a} to
@@ -746,7 +746,7 @@
       Cross Reference
     </para>
     <para>
-      Chapter 5 covers the query format.
+      <xref linkend="ch-using-rpm-db"/>  covers the query format.
     </para>
     <para>
       For example, the following entry defines the --requires and ???R
@@ -792,7 +792,7 @@
       </para>
       <para>
         The command_name must be the name passed to the C poptGetContext
-        function, covered in Chapter 16.
+        function, covered in <xref linkend="ch-programming-c"/> .
       </para>
       <para>
         Follow this with alias and then the option. You will need
@@ -882,7 +882,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 16 shows how to program with the popt library.
+        <xref linkend="ch-programming-c"/>  shows how to program with the popt library.
       </para>
     </sect2>
     <sect2>


Index: rpm-guide-dependencies-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-dependencies-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-guide-dependencies-en.xml	26 Oct 2005 01:54:11 -0000	1.2
+++ rpm-guide-dependencies-en.xml	10 Nov 2005 22:30:06 -0000	1.3
@@ -97,7 +97,7 @@
       <para>
         Package dependencies and capabilities are very important when
         creating spec files for building your own RPM packages, the
-        subject of Chapter 10.
+        subject of <xref linkend="ch-specfiles"/> .
       </para>
       <para>
         When you install a package, the capability information is stored
@@ -147,7 +147,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 4 covers ways to force the rpm command to do what you
+        <xref linkend="ch-using-rpm"/>  covers ways to force the rpm command to do what you
         want, although this can cause problems if you try to force the
         issue and remove a crucial package. In virtually all cases, do
         not use any of the force options, as this can cause problems
@@ -235,7 +235,7 @@
       <para>
         The RPM system will prevent you from installing packages that
         conflict with other packages. You can force the issue, using the
-        techniques described in Chapter 4, and override the RPM system.
+        techniques described in <xref linkend="ch-using-rpm"/> , and override the RPM system.
         But in most cases, you should not install packages that
         conflict.
       </para>
@@ -305,7 +305,7 @@
     </para>
     <para>
       There are quite a few more options you can use with the rpm ???q
-      command for querying packages. See Chapter 5 for more on querying
+      command for querying packages. See <xref linkend="ch-using-rpm-db"/>  for more on querying
       packages and package files.
     </para>
     <sect2>
@@ -465,7 +465,7 @@
         Always check what a package requires before installing the
         package. You can also use the --test option when trying to
         install the package to first test whether the installation can
-        proceed. See Chapter 4 for details on installing packages and
+        proceed. See <xref linkend="ch-using-rpm"/>  for details on installing packages and
         the --test option. The rpm command will perform all these checks
         for you anyway. Checking in advance, though, with the --test
         option, helps avoid dependency hell with circular dependencies.
@@ -751,7 +751,7 @@
         won???t work with another.
       </para>
       <para>
-        The force options discussed in Chapter 4 allow you to override
+        The force options discussed in <xref linkend="ch-using-rpm"/>  allow you to override
         conflicts, if absolutely necessary. In most cases, though, a
         conflict presents you with the choice to install one or the
         other of the packages, but not both.


Index: rpm-guide-extra-packaging-tools-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-extra-packaging-tools-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-extra-packaging-tools-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-extra-packaging-tools-en.xml	10 Nov 2005 22:30:06 -0000	1.4
@@ -346,7 +346,7 @@
         Cross Reference
       </para>
       <para>
-        See Appendix G for more on the GNU GPL, or General Public
+        See <xref linkend="ch-licensing"/>  for more on the GNU GPL, or General Public
         License.
       </para>
       <para>
@@ -870,7 +870,7 @@
         RUST appears to have stopped, so extension of RUST to become a
         more generally useful IDE for RPM generation is not likely to
         happen. However, the project is licensed under the GNU GPL
-        (Appendix G), so it might be resumed by another developer or
+        (<xref linkend="ch-licensing"/> ), so it might be resumed by another developer or
         team of developers.
       </para>
     </sect2>
@@ -915,7 +915,7 @@
       </para>
       <para>
         For more discussion of the future of RPM, you can turn to
-        Chapter 22.
+        <xref linkend="ch-rpm-evolution"/> .
       </para>
     </sect2>
     <sect2>
@@ -953,7 +953,7 @@
       </para>
       <para>
         RPM ships with an rpm2cpio utility that can be used to convert
-        RPM package files to cpio files. (Chapter 3 introduces the
+        RPM package files to cpio files. (<xref linkend="ch-rpm-overview"/>  introduces the
         rpm2cpio utility.) For example, if you have a source RPM package
         file and want to extract its files without having to install it,
         you can process it through rpm2cpio. The rpm2cpio command takes


Index: rpm-guide-management-software-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-management-software-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-management-software-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-management-software-en.xml	10 Nov 2005 22:30:06 -0000	1.4
@@ -441,7 +441,7 @@
       <para>
         With rpm2html, each package is displayed as a single HTML page
         that describes the package using information much like that
-        returned by the rpm -qi command, covered in Chapter 4. The HTML
+        returned by the rpm -qi command, covered in <xref linkend="ch-using-rpm"/> . The HTML
         page also lists the capabilities the package requires and those
         it provides. This shows the needed dependency information.
         Finally, the page includes a download link to download the RPM
@@ -551,7 +551,7 @@
           Cross Reference
         </para>
         <para>
-          See Chapter 10 for more on RPM spec files.
+          See <xref linkend="ch-specfiles"/>  for more on RPM spec files.
         </para>
       </sect3>
       <sect3>


Index: rpm-guide-online-resources-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-online-resources-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-online-resources-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-online-resources-en.xml	10 Nov 2005 22:30:06 -0000	1.4
@@ -354,10 +354,10 @@
         Cross Reference
       </para>
       <para>
-        Appendix F lists links for a number of text editors.
+        <xref linkend="ch-development-tools"/>  lists links for a number of text editors.
       </para>
       <para>
-        *The rpmlint tool mentioned in Chapter 13 is available at
+        *The rpmlint tool mentioned in <xref linkend="ch-extra-packaging-tools"/>  is available at
         http://people.mandrakesoft.com/~flepied/projects/rpmlint/.
       </para>
       <para>
@@ -561,7 +561,7 @@
         Cross Reference
       </para>
       <para>
-        Appendix F lists links for a number of Integrated Development
+        <xref linkend="ch-development-tools"/>  lists links for a number of Integrated Development
         Environments, or IDEs, aimed at programmers.
       </para>
     </sect2>


Index: rpm-guide-other-linuxes-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-other-linuxes-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-other-linuxes-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-other-linuxes-en.xml	10 Nov 2005 22:30:06 -0000	1.4
@@ -140,7 +140,7 @@
         The only real solution to this problem is to turn off dependency
         checks on installing, with the --nodeps option. Then you must
         check manually that your system really does provide all the
-        necessary dependencies. Use the techniques shown in Chapter 6 to
+        necessary dependencies. Use the techniques shown in <xref linkend="ch-dependencies"/>  to
         verify all the dependencies are met on your system.
       </para>
       <para>
@@ -200,7 +200,7 @@
       <para>
         You can use the rpm -qf command to query which package owns a
         given file. You can use the rpm -q --whatprovides command to
-        query for which package provides a given capability. Chapter 6
+        query for which package provides a given capability. <xref linkend="ch-dependencies"/> 
         covers more on dependencies.
       </para>
       <para>
@@ -263,7 +263,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 4 covers the --badreloc option.
+        <xref linkend="ch-using-rpm"/>  covers the --badreloc option.
       </para>
       <para>
         But, while the --badreloc option will relocate the files in a
@@ -457,7 +457,7 @@
         As much as possible, depend on your own RPM macros. You can
         define your macros in terms of vendor-specific macros using
         conditional statements in your spec files, a topic covered in
-        Chapter 11. You can also read examples in the ???Build
+        <xref linkend="ch-advanced-packaging"/> . You can also read examples in the ???Build
         Environment and Macros??? section of this chapter.
       </para>
       <para>
@@ -478,7 +478,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 10 covers the spec file format. Chapter 11 covers making
+        <xref linkend="ch-specfiles"/>  covers the spec file format. <xref linkend="ch-advanced-packaging"/>  covers making
         relocatable packages.
       </para>
       <para>
@@ -580,7 +580,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 21 covers RPM macros.
+          <xref linkend="ch-customizing-rpm"/>  covers RPM macros.
         </para>
         <para>
           The macros that specifically help you with platform


Index: rpm-guide-other-os-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-other-os-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-other-os-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-other-os-en.xml	10 Nov 2005 22:30:07 -0000	1.4
@@ -115,7 +115,7 @@
       Cross Reference
     </para>
     <para>
-      See Chapter 2 for more on the philosophy behind RPM.
+      See <xref linkend="ch-intro-rpm"/>  for more on the philosophy behind RPM.
     </para>
     <para>
       If you decide to use RPM on a non-Linux system, the first step is
@@ -945,7 +945,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 21 covers RPM customization.
+          <xref linkend="ch-customizing-rpm"/>  covers RPM customization.
         </para>
         <para>
           Initializing the RPM database creates the necessary structure
@@ -1038,7 +1038,7 @@
         <para>
           You need to provide a spec file header to make a complete spec
           file. This header should contain the Summary, Name, Version,
-          and Release settings, at least. Chapter 10 covers these spec
+          and Release settings, at least. <xref linkend="ch-specfiles"/>  covers these spec
           file tags.
         </para>
         <para>
@@ -1234,7 +1234,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 9 covers how to run the rpmbuild command, and Chapter
+          <xref linkend="ch-creating-rpms"/>  covers how to run the rpmbuild command, and Chapter
           10 covers spec files in detail.
         </para>
       </sect3>
@@ -1342,7 +1342,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 21 covers how to customize the RPM settings and macros,
+        <xref linkend="ch-customizing-rpm"/>  covers how to customize the RPM settings and macros,
         along with the popt aliases.
       </para>
       <para>
@@ -1406,7 +1406,7 @@
         Cross Reference
       </para>
       <para>
-        See Chapter 21 for more on how to customize the rc and macro
+        See <xref linkend="ch-customizing-rpm"/>  for more on how to customize the rc and macro
         settings.
       </para>
       <para>
@@ -1420,8 +1420,8 @@
         Cross Reference
       </para>
       <para>
-        See Chapter 19 for more information on setting up a build
-        environment for RPMs. Chapter 19 focuses on other Linux systems,
+        See <xref linkend="ch-other-linuxes"/>  for more information on setting up a build
+        environment for RPMs. <xref linkend="ch-other-linuxes"/>  focuses on other Linux systems,
         but many of the same techniques apply.
       </para>
       <para>
@@ -1522,7 +1522,7 @@
         Cross Reference
       </para>
       <para>
-        See Chapter 12 for more on using the --target option to the
+        See <xref linkend="ch-rpmbuild"/>  for more on using the --target option to the
         rpmbuild command.
       </para>
       <para>
@@ -1542,7 +1542,7 @@
         Cross Reference
       </para>
       <para>
-        See Chapter 19 for information on how to turn off the automatic
+        See <xref linkend="ch-other-linuxes"/>  for information on how to turn off the automatic
         generation of dependencies.
       </para>
       <para>


Index: rpm-guide-packaging-guidelines-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-packaging-guidelines-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-packaging-guidelines-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-packaging-guidelines-en.xml	10 Nov 2005 22:30:07 -0000	1.4
@@ -238,7 +238,7 @@
       </para>
       <para>
         If you do need a directory installed as part of your package,
-        use the %dir directive, described in Chapter 10.
+        use the %dir directive, described in <xref linkend="ch-specfiles"/> .
       </para>
     </sect2>
     <sect2>
@@ -254,7 +254,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 4 covers how to install or upgrade packages while
+        <xref linkend="ch-using-rpm"/>  covers how to install or upgrade packages while
         ignoring dependency checks. In general, you do not want to
         ignore these checks.
       </para>
@@ -343,7 +343,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 10 covers the spec file.
+          <xref linkend="ch-specfiles"/>  covers the spec file.
         </para>
         <para>
           Keeping your patches separate from the original sources makes
@@ -370,7 +370,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 17 covers Python programming.
+          <xref linkend="ch-rpm-programming-python"/>  covers Python programming.
         </para>
         <para>
           This last division is important. The Python RPM draws in as a
@@ -481,7 +481,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 13 covers RPM-building tools. Appendix F covers the
+          <xref linkend="ch-extra-packaging-tools"/>  covers RPM-building tools. <xref linkend="ch-development-tools"/>  covers the
           Eclipse Integrated Development Environment.
         </para>
         <para>
@@ -562,7 +562,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 12 covers signing packages.
+          <xref linkend="ch-rpmbuild"/>  covers signing packages.
         </para>
       </sect3>
       <sect3>


Index: rpm-guide-programming-c-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-c-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-programming-c-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-programming-c-en.xml	10 Nov 2005 22:30:07 -0000	1.4
@@ -115,7 +115,7 @@
         Cross Reference
       </para>
       <para>
-        See Chapter 8 for more on the &RH; package management tool.
+        See <xref linkend="ch-management-software"/>  for more on the &RH; package management tool.
       </para>
       <para>
         The gcc package requires a number of capabilities. Make sure you
@@ -131,7 +131,7 @@
         Cross Reference
       </para>
       <para>
-        Appendix F covers Linux text editors and development tools.
+        <xref linkend="ch-development-tools"/>  covers Linux text editors and development tools.
       </para>
       <para>
         Once you have a C programming environment set up, you next need
@@ -185,7 +185,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 17 covers programming RPM with Python.
+        <xref linkend="ch-rpm-programming-python"/>  covers programming RPM with Python.
       </para>
       <para>
         In addition to rpmlib.h, the header file rpmcli.h defines a
@@ -346,7 +346,7 @@
       </para>
       <para>
         You can use the rpm command and the queries introduced in
-        Chapter 5 to determine exactly where the header files are
+        <xref linkend="ch-using-rpm-db"/>  to determine exactly where the header files are
         located. Simply execute the following command:
       </para>
       <para>
@@ -531,7 +531,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 21 covers customizing RPM.
+        <xref linkend="ch-customizing-rpm"/>  covers customizing RPM.
       </para>
       <para>
         Your C programs need to access these RPM system settings to
@@ -832,7 +832,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 21 covers macros in depth. In your C programs, your
+          <xref linkend="ch-customizing-rpm"/>  covers macros in depth. In your C programs, your
           code will likely need to expand the value of macros to place
           data in the proper directories, determine the platform
           architecture, and so on.
@@ -1013,13 +1013,13 @@
       </para>
       <para>
         This example defines rpm --requires as really a query using the
-        --qf or --queryformat options covered in Chapter 5.
+        --qf or --queryformat options covered in <xref linkend="ch-using-rpm-db"/> .
       </para>
       <para>
         Cross Reference
       </para>
       <para>
-        See Chapter 21 for more on defining popt aliases.
+        See <xref linkend="ch-customizing-rpm"/>  for more on defining popt aliases.
       </para>
     </sect2>
     <sect2>
@@ -2268,7 +2268,7 @@
       Cross Reference
     </para>
     <para>
-      Chapter 17 covers the Python RPM API.
+      <xref linkend="ch-rpm-programming-python"/>  covers the Python RPM API.
     </para>
     <sect2>
       <title>Opening RPM files</title>
@@ -2308,7 +2308,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 3 introduces the lead and signature.
+        <xref linkend="ch-rpm-overview"/>  introduces the lead and signature.
       </para>
       <para>
         Even if your programs don???t want to examine the lead or
@@ -2555,7 +2555,7 @@
       <para>
         When you call headerGetEntry, you must identify the tag you want
         from the header. This tag is an identifier for the --queryformat
-        tags introduced in Chapter 5. The file rpmlib.h lists the
+        tags introduced in <xref linkend="ch-using-rpm-db"/> . The file rpmlib.h lists the
         various tags, such as RPMTAG_NAME, RPMTAG_VERSION, and
         RPMTAG_RELEASE.
       </para>


Index: rpm-guide-programming-perl-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-perl-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-programming-perl-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-programming-perl-en.xml	10 Nov 2005 22:30:07 -0000	1.4
@@ -74,7 +74,7 @@
     Cross Reference
   </para>
   <para>
-    Many of the RPM tools covered in Chapter 8 are written in Perl.
+    Many of the RPM tools covered in <xref linkend="ch-management-software"/>  are written in Perl.
   </para>
   <sect1>
     <title>Getting and Using the Perl RPM Modules</title>
@@ -160,7 +160,7 @@
       </para>
       <para>
         These are the same tags introduced with the --queryformat option
-        to the rpm command discussed in Chapter 5.
+        to the rpm command discussed in <xref linkend="ch-using-rpm-db"/> .
       </para>
       <para>
         The tag subroutine returns the value of a given tag. For
@@ -1167,7 +1167,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 5 covers more on these tags.
+          <xref linkend="ch-using-rpm-db"/>  covers more on these tags.
         </para>
       </sect3>
       <sect3>
@@ -1526,7 +1526,7 @@
       packages that are older than the designated master system.
       RPM::Make, also part of the RPM-Tools bundle, helps create RPM
       packages from a Perl script. This module does not support all the
-      spec file options described in Chapter 10, but it can help you
+      spec file options described in <xref linkend="ch-specfiles"/> , but it can help you
       make simple packages.
     </para>
     <para>


Index: rpm-guide-programming-python-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-python-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-programming-python-en.xml	31 Oct 2005 23:18:20 -0000	1.4
+++ rpm-guide-programming-python-en.xml	10 Nov 2005 22:30:07 -0000	1.5
@@ -45,7 +45,7 @@
       Cross Reference
     </para>
     <para>
-      Appendix H covers Linux text editors and development tools.
+      <xref linkend="ch-development-tools"/>  covers Linux text editors and development tools.
     </para>
     <para>
       If you want to make a graphical user interface in your Python
@@ -67,7 +67,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 4 covers installing packages.
+        <xref linkend="ch-using-rpm"/>  covers installing packages.
       </para>
     </sect2>
     <sect2>
@@ -250,7 +250,7 @@
   <sect1>
     <title>Programming with the RPM Database</title>
     <para>
-      Compared to the RPM C API, discussed in Chapter 16, the Python API
+      Compared to the RPM C API, discussed in <xref linkend="ch-programming-c"/> , the Python API
       is much simpler and requires many fewer programming statements to
       get your job done.
     </para>
@@ -388,7 +388,7 @@
           Cross Reference
         </para>
         <para>
-          See Chapter 5 for more on initializing, rebuilding, and
+          See <xref linkend="ch-using-rpm-db"/>  for more on initializing, rebuilding, and
           verifying RPM databases.
         </para>
         <para>
@@ -701,7 +701,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 5 covers query formats.
+          <xref linkend="ch-using-rpm-db"/>  covers query formats.
         </para>
         <para>
           The basic syntax is as follows:
@@ -1187,7 +1187,7 @@
         For more on these patterns, see the online manual pages for
         fnmatch(3), glob(7), regcomp(3), regex(7), and strcmp(3). The
         pattern method calls rpmdbSetIteratorRE from the C API, covered
-        in the ???Database Iterators??? section in Chapter 16.
+        in the ???Database Iterators??? section in <xref linkend="ch-programming-c"/> .
       </para>
       <para>
         To query for all packages starting with py, for example, you can
@@ -1620,7 +1620,7 @@
   <sect1>
     <title>Dependency Comparisons</title>
     <para>
-      Dependency sets, first introduced in Chapter 16 on C programming,
+      Dependency sets, first introduced in <xref linkend="ch-programming-c"/>  on C programming,
       allow you to compare the dependencies between two packages. One of
       the most common uses for this is to compare a package file against
       a version on disk to see if the package file holds a newer version
@@ -1739,7 +1739,7 @@
     </para>
     <para>
       The Python script in Listing 17-5 is essentially the same as the
-      longer C program vercompare.c in Listing 16-4 in Chapter 16.
+      longer C program vercompare.c in Listing 16-4 in <xref linkend="ch-programming-c"/> .
     </para>
     <para>
       This script takes in a package file name on the command line,
@@ -3044,7 +3044,7 @@
       This chapter introduces the high-level RPM API for Python
       programming. You can use this API from Python scripts to perform
       RPM functionality, just as you can write C programs using the RPM
-      C API covered in Chapter 16.
+      C API covered in <xref linkend="ch-programming-c"/> .
     </para>
     <para>
       In general, the Python API is simpler and requires fewer code


Index: rpm-guide-rpmbuild-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-rpmbuild-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-rpmbuild-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-rpmbuild-en.xml	10 Nov 2005 22:30:07 -0000	1.4
@@ -66,7 +66,7 @@
       Note
     </para>
     <para>
-      As mentioned in Chapter 9, previous versions of the RPM system
+      As mentioned in <xref linkend="ch-creating-rpms"/> , previous versions of the RPM system
       used the rpm command with a -b, for build, option. This option is
       no longer supported. Use the rpmbuild command to build RPMs.
     </para>
@@ -369,7 +369,7 @@
       </para>
       <para>
         The --target option sets the target architecture at build time.
-        Chapter 4 covers how you can use the --ignoreos and --ignorearch
+        <xref linkend="ch-using-rpm"/>  covers how you can use the --ignoreos and --ignorearch
         options when installing RPMs to ignore the operating system and
         architecture that is flagged within the RPM. Of course, this
         works only if you are installing on a compatible architecture.
@@ -551,7 +551,7 @@
         rpmbuild -tBuildStage compressed_tar_archive
       </para>
       <para>
-        The -t option is a lot like the -b option covered in Chapter 9,
+        The -t option is a lot like the -b option covered in <xref linkend="ch-creating-rpms"/> ,
         except -t tells rpmbuild to build an RPM from a compressed tar
         archive instead of from an RPM spec file. You still need a spec
         file. These commands just assume that the spec file is located
@@ -724,7 +724,7 @@
       Cross Reference
     </para>
     <para>
-      Chapter 10 covers the spec file in depth.
+      <xref linkend="ch-specfiles"/>  covers the spec file in depth.
     </para>
     <para>
       Because they are RPMs themselves, source RPMs act like other RPMs.
@@ -752,7 +752,7 @@
     <para>
       Once installation is complete, you can use the rpmbuild command to
       create a binary RPM from the sources in the source RPM, using the
-      -b command-line options introduced in Chapter 9. The next sections
+      -b command-line options introduced in <xref linkend="ch-creating-rpms"/> . The next sections
       show more shortcuts with source RPMs.
     </para>
     <sect2>
@@ -1361,7 +1361,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 21 covers RPM macros and the $HOME/.rpmmacros file.
+        <xref linkend="ch-customizing-rpm"/>  covers RPM macros and the $HOME/.rpmmacros file.
       </para>
       <para>
         Inside the file, change the %gpg_path macro to the .gnupg


Index: rpm-guide-scripting-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-scripting-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-scripting-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-scripting-en.xml	10 Nov 2005 22:30:07 -0000	1.4
@@ -224,9 +224,9 @@
       Cross Reference
     </para>
     <para>
-      This chapter covers shell scripting. Chapter 16 covers C
-      programming. Chapter 17 covers Python scripting and programming,
-      and Chapter 18 covers Perl scripting.
+      This chapter covers shell scripting. <xref linkend="ch-programming-c"/>  covers C
+      programming. <xref linkend="ch-rpm-programming-python"/>  covers Python scripting and programming,
+      and <xref linkend="ch-programming-perl"/>  covers Perl scripting.
     </para>
   </sect1>
   <sect1>
@@ -252,7 +252,7 @@
       </para>
       <para>
         This script has a two-part command. The rpm ???qa part queries
-        all RPM packages, as covered in Chapter 4. The grep rpm part
+        all RPM packages, as covered in <xref linkend="ch-using-rpm"/> . The grep rpm part
         finds only packages with rpm in their names. This is a very
         simple script, but it can serve to show how to work with
         scripts.
@@ -267,7 +267,7 @@
       <para>
         If you???re new to Linux, you???ll notice there???s no program
         named Notepad.exe. There are, though, a plethora of Linux text
-        editors to choose from. See Appendix F for a listing of Linux
+        editors to choose from. See <xref linkend="ch-development-tools"/>  for a listing of Linux
         text-editing tools.
       </para>
     </sect2>


Index: rpm-guide-specfile-syntax-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-specfile-syntax-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-guide-specfile-syntax-en.xml	26 Oct 2005 01:54:11 -0000	1.2
+++ rpm-guide-specfile-syntax-en.xml	10 Nov 2005 22:30:07 -0000	1.3
@@ -149,14 +149,14 @@
       </para>
       <para>
         Avoid percent signs, %, in comments, which may get interpreted
-        as RPM macros. See Chapter 10 for details.
+        as RPM macros. See <xref linkend="ch-specfiles"/>  for details.
       </para>
     </sect2>
     <sect2>
       <title>Build settings</title>
       <para>
         The BuildArchitectures tag names the architectures that a binary
-        RPM will run on. See Chapter 21 for a description of the
+        RPM will run on. See <xref linkend="ch-customizing-rpm"/>  for a description of the
         architecture settings. A special value of noarch indicates a
         package that is not dependent on a particular architecture, such
         as a Perl or Python script.
@@ -180,7 +180,7 @@
       <title>Dependency tags</title>
       <para>
         Dependency tags define all the dependencies for the package, as
-        described in Chapter 6.
+        described in <xref linkend="ch-dependencies"/> .
       </para>
       <para>
         For each dependency, you can specify a capability name alone.
@@ -324,7 +324,7 @@
         Cross Reference
       </para>
       <para>
-        See the section on Defining Macros in Spec Files in Chapter 21
+        See the section on Defining Macros in Spec Files in <xref linkend="ch-specfile-syntax"/> 
         for more on this subject.
       </para>
       <para>


Index: rpm-guide-specfiles-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-specfiles-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-specfiles-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-specfiles-en.xml	10 Nov 2005 22:30:07 -0000	1.4
@@ -196,7 +196,7 @@
     <sect2>
       <title>Storing spec files on disk</title>
       <para>
-        As discussed in Chapter 9, the rpmbuild command expands source
+        As discussed in <xref linkend="ch-creating-rpms"/> , the rpmbuild command expands source
         RPMs to the /usr/src/redhat directory. Under this directory, the
         RPM system assumes five subdirectories, listed in Table 10-1.
       </para>
@@ -291,7 +291,7 @@
         Cross Reference
       </para>
       <para>
-        These directories are the default directories. See Chapter 21
+        These directories are the default directories. See <xref linkend="ch-specfile-syntax"/> 
         for changing RPM default values. In addition, these are the
         defaults for &RHL;. See Chapters 19 and 20 for
         discussions on other versions of Linux and other non-Linux
@@ -432,7 +432,7 @@
         <para>
           Many graphical installation tools divide packages by these
           categories, so you want to fit into the existing group names
-          if possible. (See Chapter 5 for more on querying group
+          if possible. (See <xref linkend="ch-using-rpm-db"/>  for more on querying group
           information from RPMs.) The official list of groups are
           located in the file /usr/share/doc/rpm-4.1/GROUPS for RPM 4.1,
           and in a similar location for other RPM versions.
@@ -822,7 +822,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 14 discusses packaging guidelines and best practices.
+        <xref linkend="ch-packaging-guidelines"/>  discusses packaging guidelines and best practices.
         Starting from pristine sources is one of the best practices.
       </para>
       <para>
@@ -849,7 +849,7 @@
       Cross Reference
     </para>
     <para>
-      Chapter 9 covers make and other Linux build tools.
+      <xref linkend="ch-creating-rpms"/>  covers make and other Linux build tools.
     </para>
     <para>
       In RPM terms, building the package is split into four steps:
@@ -907,7 +907,7 @@
       <para>
         Table 10-2 summarizes the %setup command-line parameters. Many
         of these options apply mostly for subpackages, a topic covered
-        in Chapter 11.
+        in <xref linkend="ch-advanced-packaging"/> .
       </para>
       <para>
         Table 10-2 Command-line parameters for %setup
@@ -1215,7 +1215,7 @@
       </para>
       <para>
         If you intend to support relocatable packages, covered in
-        Chapter 11, you will likely need to pass a --prefix option to
+        <xref linkend="ch-advanced-packaging"/> , you will likely need to pass a --prefix option to
         the configure script. For example:
       </para>
       <para>
@@ -1370,7 +1370,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 11 covers triggers, another form of script that gets run
+        <xref linkend="ch-advanced-packaging"/>  covers triggers, another form of script that gets run
         when packages are installed or removed.
       </para>
       <para>
@@ -1879,7 +1879,7 @@
         Cross Reference
       </para>
       <para>
-        See Chapter 5 for more on package verification.
+        See <xref linkend="ch-using-rpm-db"/>  for more on package verification.
       </para>
       <para>
         The %verify directive names the tests to include or not include.
@@ -2110,7 +2110,7 @@
       </para>
       <para>
         You can also store this setting in a macro file so that it
-        applies for all packages you build. See Chapter 21 for more on
+        applies for all packages you build. See <xref linkend="ch-customizing-rpm"/>  for more on
         macro files.
       </para>
       <para>
@@ -2475,7 +2475,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 15 covers shell scripting with RPM.
+        <xref linkend="ch-scripting"/>  covers shell scripting with RPM.
       </para>
       <para>
         With parameters, you can expand the normal definition of a macro


Index: rpm-guide-transactions-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-transactions-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-transactions-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-transactions-en.xml	10 Nov 2005 22:30:07 -0000	1.4
@@ -152,7 +152,7 @@
       Cross Reference
     </para>
     <para>
-      The gnorpm command is covered in Chapter 8. The rpmrebuild package
+      The gnorpm command is covered in <xref linkend="ch-management-software"/> . The rpmrebuild package
       is covered in the "Saving Old Packages" section in this chapter.
     </para>
     <para>
@@ -322,7 +322,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 5 describes the --queryformat option.
+          <xref linkend="ch-using-rpm-db"/>  describes the --queryformat option.
         </para>
         <para>
           There is also a transaction ID for removal, the REMOVETID. You
@@ -494,12 +494,12 @@
       </para>
       <para>
         Before running the --rollback option, backup your RPM database
-        as described in Chapter 5.
+        as described in <xref linkend="ch-using-rpm-db"/> .
       </para>
       <para>
         Because of all these limitations, rollbacks do not work in all
         situations. In place of the --rollback option, you can use the
-        query shortcuts introduced in Chapter 5 and find the packages
+        query shortcuts introduced in <xref linkend="ch-using-rpm-db"/>  and find the packages
         you have installed recently (if that is what you want to roll
         back). In this case, you can use the rpm command to remove the
         packages you want to get rid of and reinstall the packages you


Index: rpm-guide-using-rpm-db-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-db-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-using-rpm-db-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-using-rpm-db-en.xml	10 Nov 2005 22:30:07 -0000	1.4
@@ -64,7 +64,7 @@
   <sect1>
     <title>Querying the RPM Database</title>
     <para>
-      In Chapter 4, you saw that the rpm command usually takes one major
+      In <xref linkend="ch-using-rpm"/> , you saw that the rpm command usually takes one major
       command-line option to tell it the operation to perform and a
       myriad of command-line options to customize the operation. The rpm
       command may also take the name of one or more RPM package files or
@@ -115,7 +115,7 @@
       <para>
         You can provide the whole package name to the rpm command, which
         includes the name, the version, and the RPM package number, as
-        discussed in Chapter 3. You can also just provide the name and
+        discussed in <xref linkend="ch-rpm-overview"/> . You can also just provide the name and
         version number, as shown previously, or just the base name of
         the package.
       </para>
@@ -370,7 +370,7 @@
         </para>
         <para>
           You can also use the --pipe option to the rpm command,
-          introduced in Chapter 4. With this option, your command
+          introduced in <xref linkend="ch-using-rpm"/> . With this option, your command
           becomes:
         </para>
         <para>
@@ -380,7 +380,7 @@
           Cross Reference
         </para>
         <para>
-          Chapter 17 covers programming with the RPM system with the
+          <xref linkend="ch-rpm-programming-python"/>  covers programming with the RPM system with the
           Python scripting language.
         </para>
         <para>
@@ -1479,7 +1479,7 @@
         Cross Reference
       </para>
       <para>
-        See Chapter 4 for more on installing RPMs.
+        See <xref linkend="ch-using-rpm"/>  for more on installing RPMs.
       </para>
     </sect2>
     <sect2>
@@ -2173,7 +2173,7 @@
         A great many of the command-line options to the rpm command are
         defined as popt aliases. These popt aliases define the rpm
         command-line options in terms of longer query format strings.
-        See Chapter 21 for more information on popt.
+        See <xref linkend="ch-customizing-rpm"/>  for more information on popt.
       </para>
       <para>
         You can add items to the query string and use C language
@@ -2309,7 +2309,7 @@
         <title>Querying for Package Information</title>
         <para>
           Many of the query format tags refer to package-information
-          data stored in the RPM header, introduced in Chapter 3. Table
+          data stored in the RPM header, introduced in <xref linkend="ch-rpm-overview"/> . Table
           5-3 lists the package-information tags.
         </para>
         <para>
@@ -3493,7 +3493,7 @@
           Cross Reference
         </para>
         <para>
-          See Appendix D for a listing of all the tags in an RPM file.
+          See <xref linkend="ch-package-structure"/>  for a listing of all the tags in an RPM file.
         </para>
       </sect3>
     </sect2>
@@ -3678,9 +3678,9 @@
       Querying Package Files Remotely
     </para>
     <para>
-      As shown in Chapter 4, you can access RPM package files over a
+      As shown in <xref linkend="ch-using-rpm"/> , you can access RPM package files over a
       network using FTP or HTTP connections. To query remote files, use
-      the same rules as shown in Chapter 4, with the following syntax:
+      the same rules as shown in <xref linkend="ch-using-rpm"/> , with the following syntax:
     </para>
     <para>
       rpm -qp ftp://username:password at hostname:port/path/to/rpm/file
@@ -4204,7 +4204,7 @@
         Cross Reference
       </para>
       <para>
-        Chapter 12 covers another option for verifying a package file,
+        <xref linkend="ch-rpmbuild"/>  covers another option for verifying a package file,
         the rpm ???K command.
       </para>
       <para>
@@ -4222,7 +4222,7 @@
   <sect1>
     <title>Working With the RPM Database</title>
     <para>
-      As mentioned in Chapter 3, the RPM database is stored in
+      As mentioned in <xref linkend="ch-rpm-overview"/> , the RPM database is stored in
       /var/lib/rpm. The files in that directory are Berkeley DB files,
       as shown by the file command:
     </para>


Index: rpm-guide-using-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-using-rpm-en.xml	31 Oct 2005 23:18:20 -0000	1.3
+++ rpm-guide-using-rpm-en.xml	10 Nov 2005 22:30:07 -0000	1.4
@@ -111,7 +111,7 @@
       <para/>
       <para>
         Almost all installation steps use the rpm command with the ???U
-        option, short for upgrade, as introduced in Chapter 3. The basic
+        option, short for upgrade, as introduced in <xref linkend="ch-rpm-overview"/> . The basic
         syntax is:
       </para>
       <para>
@@ -144,7 +144,7 @@
       </para>
       <para>
         This warning comes from the fact that the package was signed,
-        but the key was not found. Chapter 12 covers signing packages.
+        but the key was not found. <xref linkend="ch-rpmbuild"/>  covers signing packages.
         In most cases, warnings such as this one are not that serious.
         Errors, though, should be treated seriously.
       </para>
@@ -1454,7 +1454,7 @@
           configuration file on disk. This is where the rpm command
           starts working with some upgrade rules. Note that this special
           processing only applies to files marked as configuration files
-          within the RPM. Chapter 10 covers how to mark files as
+          within the RPM. <xref linkend="ch-specfiles"/>  covers how to mark files as
           configuration files.
         </para>
         <para>
@@ -1689,7 +1689,7 @@
         example, rarely come with source code. In this case, obviously,
         no source RPMs are available. Or, a source RPM for a commercial
         application may provide no source code, but still provide a way
-        to build the resulting application. See Chapter 10 for more on
+        to build the resulting application. See <xref linkend="ch-specfiles"/>  for more on
         the source files and options for not including the sources in a
         source RPM.
       </para>
@@ -1992,7 +1992,7 @@
       Cross Reference
     </para>
     <para>
-      See Chapter 21 for more on the --showrc option.
+      See <xref linkend="ch-customizing-rpm"/>  for more on the --showrc option.
     </para>
     <para>
       The --version option tells the rpm command to print out the



From fedora-docs-commits at redhat.com  Fri Nov 11 15:33:29 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Fri, 11 Nov 2005 10:33:29 -0500
Subject: mirror-tutorial mirror-tutorial-en.xml,1.15,1.16
Message-ID: <200511111533.jABFXTmM020441@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20424

Modified Files:
	mirror-tutorial-en.xml 
Log Message:
Update information on repo files (#172815)


Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- mirror-tutorial-en.xml	9 Nov 2005 23:41:58 -0000	1.15
+++ mirror-tutorial-en.xml	11 Nov 2005 15:33:22 -0000	1.16
@@ -6,8 +6,8 @@
 %FEDORA-ENTITIES-EN;
 
 <!ENTITY BOOKNAME "mirror-tutorial">
-<!ENTITY BOOKVERSION "0.35">
-<!ENTITY BOOKDATE "2005-11-09">
+<!ENTITY BOOKVERSION "0.36">
+<!ENTITY BOOKDATE "2005-11-11">
 <!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)"> <!-- change version of manual and date here -->
 
 <!ENTITY BUG-NUM "130125">
@@ -192,6 +192,17 @@
 	  </para>
 	</revdescription>
       </revision>
+      <revision>
+	<revnumber>0.36</revnumber>
+	<date>2005-11-11</date>
+	<authorinitials>PaulWFrields</authorinitials>
+	<revdescription>
+	  <para>
+	    Added some additional information about repository
+	    configuration (#172815).
+	  </para>
+	</revdescription>
+      </revision>
     </revhistory>
   </articleinfo>
 
@@ -804,7 +815,7 @@
 	  <para>
 	    If you are not exceedingly careful in using these switches, it is
 	    possible to delete large portions of your mirrored data. Fixing this
-	    problem might simply require performing the copying steps outlined
+	    problem might require performing the copying steps outlined
 	    in <xref linkend="sn-copying-original-distribution"/> above. On the
 	    other hand, if you are also careless about your destination path,
 	    and you are running as root, you could put your entire system at
@@ -1192,7 +1203,7 @@
 	server. It can do this via HTTP or FTP, as well as using
 	standard file system calls (either local or remote via NFS). The
 	client computes solutions to any package dependencies using the
-	downloaded header information, and simply requests all necessary
+	downloaded header information, and requests all necessary
 	RPM packages once it has finished. The <command>yum</command>
 	command relies on <command>rpm</command> functions to perform
 	many of the computations involved in the process.
@@ -1361,10 +1372,10 @@
 
     <example>
       <title>Example
-      <filename>/etc/yum.repos.d/fedora.repo</filename></title>
+      <filename>/etc/yum.repos.d/fedora-mirror.repo</filename></title>
 
 <screen>
-<computeroutput>[base]
+<computeroutput>[mirror]
 name=Fedora Core $releasever - $basearch - Base
 baseurl=http://server.mydomain.net/mirror/fedora/linux/core/$releasever/$basearch
 enabled=1
@@ -1382,9 +1393,22 @@
     </para>
 
     <para>
-      For more information about these configuration files, refer to the
-      "Software Management with <command>yum</command>" tutorial online
-      at <ulink url="http://fedora.redhat.com/docs/yum/"/>.
+      If you want clients to use your mirror in place of the official
+      repositories, disable the existing repositories.  To do this, edit
+      the client's file for the official repository to include the
+      directive <userinput>enabled=0</userinput>.  You will need
+      <systemitem class="username">root</systemitem> access to edit
+      these files.
+    </para>
+
+    <para>
+      Many repositories provide their own installable RPM packages
+      containing these configuration files.  When a user installs the
+      RPM, the new files in <filename>/etc/yum.repos.d/</filename>
+      reference that repository.  These packages simplify the addition
+      of new repositories for end users.  Whether you use such a package
+      yourself will depend on the number and skill set of clients your
+      repository serves.
     </para>
 
   </section>



From fedora-docs-commits at redhat.com  Fri Nov 11 16:58:55 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Fri, 11 Nov 2005 11:58:55 -0500
Subject: mirror-tutorial mirror-tutorial-en.xml,1.16,1.17
Message-ID: <200511111658.jABGwt2n022964@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22945

Modified Files:
	mirror-tutorial-en.xml 
Log Message:
Additional createrepo info (#172819)


Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- mirror-tutorial-en.xml	11 Nov 2005 15:33:22 -0000	1.16
+++ mirror-tutorial-en.xml	11 Nov 2005 16:58:48 -0000	1.17
@@ -199,7 +199,7 @@
 	<revdescription>
 	  <para>
 	    Added some additional information about repository
-	    configuration (#172815).
+	    configuration (#172815, #172819).
 	  </para>
 	</revdescription>
       </revision>
@@ -1314,6 +1314,22 @@
 </screen>
 
 	<para>
+	  To create repository data for package groups in addition to
+	  the package files, use the <command>createrepo -g</command>
+	  command.  The <option>-g</option> option requires a parameter
+	  which points to the group file, <emphasis>relative</emphasis>
+	  to the given location of the package data.  The following
+	  command creates the package group data corresponding to the
+	  repository directly above.  Note the relative location of the
+	  group file
+	  <filename>/var/www/mirror/fedora/linux/core/&FCVER;i386/os/Fedora/base/comps.xml</filename>.
+	</para>
+
+<screen>
+<userinput>createrepo -g Fedora/base/comps.xml /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput>
+</screen>
+
+	<para>
 	  You may have certain clients who update their version of
 	  <command>yum</command> in a non-prescribed way. To minimize
 	  problems for your clients, create both kinds of repository



From fedora-docs-commits at redhat.com  Mon Nov 14 21:55:13 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Mon, 14 Nov 2005 16:55:13 -0500
Subject: rpm-guide rpm-guide-advanced-packaging-en.xml, 1.4,
	1.5 rpm-guide-creating-rpms-en.xml, 1.4,
	1.5 rpm-guide-intro-packaging-en.xml, 1.4,
	1.5 rpm-guide-other-os-en.xml, 1.4,
	1.5 rpm-guide-package-structure-en.xml, 1.2,
	1.3 rpm-guide-programming-c-en.xml, 1.4,
	1.5 rpm-guide-rpmbuild-en.xml, 1.4,
	1.5 rpm-guide-specfile-syntax-en.xml, 1.3,
	1.4 rpm-guide-specfiles-en.xml, 1.4,
	1.5 rpm-guide-transactions-en.xml, 1.4,
	1.5 rpm-guide-using-rpm-en.xml, 1.4, 1.5
Message-ID: <200511142155.jAELtDBB011119@cvs-int.fedora.redhat.com>

Author: elliss

Update of /cvs/docs/rpm-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11082

Modified Files:
	rpm-guide-advanced-packaging-en.xml 
	rpm-guide-creating-rpms-en.xml 
	rpm-guide-intro-packaging-en.xml rpm-guide-other-os-en.xml 
	rpm-guide-package-structure-en.xml 
	rpm-guide-programming-c-en.xml rpm-guide-rpmbuild-en.xml 
	rpm-guide-specfile-syntax-en.xml rpm-guide-specfiles-en.xml 
	rpm-guide-transactions-en.xml rpm-guide-using-rpm-en.xml 
Log Message:
Completed replacement of "Chapter X" with links



Index: rpm-guide-advanced-packaging-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-advanced-packaging-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-advanced-packaging-en.xml	10 Nov 2005 22:30:06 -0000	1.4
+++ rpm-guide-advanced-packaging-en.xml	14 Nov 2005 21:55:05 -0000	1.5
@@ -1356,9 +1356,7 @@
       Cross Reference
     </para>
     <para>
-      See <xref linkend="ch-customizing-rpm"/>  for more on macro file locations, and Chapters 19
-      and 20 for more on using RPM on other versions of Linux and other
-      operating systems, respectively.
+      See <xref linkend="ch-customizing-rpm"/> for more on macro file locations, and <xref linkend="ch-other-linuxes"/> and <xref linkend="ch-other-os"/> for more on using RPM on other versions of Linux and other operating systems, respectively.
     </para>
     <para>
       RPM supports a number of ways to make parts of your spec file


Index: rpm-guide-creating-rpms-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-creating-rpms-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-creating-rpms-en.xml	10 Nov 2005 22:30:06 -0000	1.4
+++ rpm-guide-creating-rpms-en.xml	14 Nov 2005 21:55:05 -0000	1.5
@@ -1095,7 +1095,7 @@
           This example skips the install and uninstall script sections,
           as well as a verification section. There are also no triggers
           defined in this RPM spec file. All of these topics are covered
-          in Chapters 10 and 11.
+          in <xref linkend="ch-specfiles"/> and <xref linkend="ch-advanced-packaging"/>.
         </para>
         <para>
           Once you have written your spec file, and placed the files in
@@ -1552,8 +1552,7 @@
   <sect1>
     <title>Verifying Your RPMS</title>
     <para>
-      After you've built an RPM, you can use the techniques from Chapter
-      5 to verify the RPM. You can also use the ???bl option to the
+      After you've built an RPM, you can use the techniques from <xref linkend="ch-using-rpm-db"/> to verify the RPM. You can also use the ???bl option to the
       rpmbuild command to verify the list of files in the RPM. Use a
       command like the following:
     </para>


Index: rpm-guide-intro-packaging-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-intro-packaging-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-intro-packaging-en.xml	31 Oct 2005 23:18:20 -0000	1.4
+++ rpm-guide-intro-packaging-en.xml	14 Nov 2005 21:55:05 -0000	1.5
@@ -402,7 +402,7 @@
       <title>Change of Name</title>
 <!-- SE: Don't replace "&RH;" with an entity here: we don't want the text to change -->
       <para>
-        RPM was originally called &RH; Package Manager. After
+        RPM was originally called Red Hat Package Manager. After
         adoption by other Linux distributions, the name has changed to
         simply the RPM Package Manager. The RPM initials remain the
         same.
@@ -411,11 +411,11 @@
     <para>
       As the original name implies, RPM was developed by &FORMAL-RHI;,
       the major Linux distributor in the United States. Even though the
-      original name seems to point to a &RH;-only solution, most Linux
+      original name seems to point to a Red Hat-only solution, most Linux
       distributions use the RPM software. The RPM software provides a
       foundation needed by Linux system administrators throughout the
       world. You can even use RPM on other operating systems, both Linux
-      and non-Linux, as covered in Chapters 19 and 20, respectively.
+      and non-Linux, as covered in <xref linkend="ch-other-linuxes"/> and <xref linkend="ch-other-os"/>, respectively.
     </para>
     <para>
       The RPM system provides all of the features needed to manage


Index: rpm-guide-other-os-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-other-os-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-other-os-en.xml	10 Nov 2005 22:30:07 -0000	1.4
+++ rpm-guide-other-os-en.xml	14 Nov 2005 21:55:05 -0000	1.5
@@ -1234,8 +1234,7 @@
           Cross Reference
         </para>
         <para>
-          <xref linkend="ch-creating-rpms"/>  covers how to run the rpmbuild command, and Chapter
-          10 covers spec files in detail.
+          <xref linkend="ch-creating-rpms"/> covers how to run the rpmbuild command, and <xref linkend="ch-specfiles"/> covers spec files in detail.
         </para>
       </sect3>
       <sect3>


Index: rpm-guide-package-structure-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-package-structure-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-guide-package-structure-en.xml	26 Oct 2005 01:54:11 -0000	1.2
+++ rpm-guide-package-structure-en.xml	14 Nov 2005 21:55:05 -0000	1.3
@@ -34,8 +34,7 @@
     Cross Reference
   </para>
   <para>
-    Chapters 16, 17, and 18 cover programming with C, Python, and Perl,
-    respectively.
+    <xref linkend="ch-programming-c"/>, <xref linkend="ch-rpm-programming-python"/>, and <xref linkend="ch-programming-perl"/> cover programming with C, Python, and Perl, respectively.
   </para>
   <para>
     The RPM package format described here has been standardized as part


Index: rpm-guide-programming-c-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-c-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-programming-c-en.xml	10 Nov 2005 22:30:07 -0000	1.4
+++ rpm-guide-programming-c-en.xml	14 Nov 2005 21:55:05 -0000	1.5
@@ -2176,8 +2176,7 @@
       </para>
       <para>
         All in all, the popt library provides a handy library for
-        processing command-line options and aliases, covered in Chapter
-        21.
+        processing command-line options and aliases, covered in <xref linkend="ch-customizing-rpm"/>.
       </para>
     </sect2>
     <sect2>


Index: rpm-guide-rpmbuild-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-rpmbuild-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-rpmbuild-en.xml	10 Nov 2005 22:30:07 -0000	1.4
+++ rpm-guide-rpmbuild-en.xml	14 Nov 2005 21:55:05 -0000	1.5
@@ -45,8 +45,7 @@
     <title>Building RPMs with the rpmbuild Command</title>
     <para>
       The rpmbuild command provides a workhorse command for building
-      RPMs in all sorts of ways. The basic syntax, as shown in Chapter
-      9, is:
+      RPMs in all sorts of ways. The basic syntax, as shown in <xref linkend="ch-creating-rpms"/>, is:
     </para>
     <para>
       rpmbuild -bBuildStage spec_file


Index: rpm-guide-specfile-syntax-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-specfile-syntax-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-specfile-syntax-en.xml	10 Nov 2005 22:30:07 -0000	1.3
+++ rpm-guide-specfile-syntax-en.xml	14 Nov 2005 21:55:05 -0000	1.4
@@ -662,7 +662,7 @@
     <title>Build Sections</title>
     <para>
       After providing information about the package, you need to define
-      the build stages, as described in Chapters 10 and 12.
+      the build stages, as described in <xref linkend="ch-specfiles"/> and <xref linkend="ch-rpmbuild"/>.
     </para>
     <sect2>
       <title>Build preparation</title>


Index: rpm-guide-specfiles-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-specfiles-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-specfiles-en.xml	10 Nov 2005 22:30:07 -0000	1.4
+++ rpm-guide-specfiles-en.xml	14 Nov 2005 21:55:05 -0000	1.5
@@ -196,9 +196,10 @@
     <sect2>
       <title>Storing spec files on disk</title>
       <para>
-        As discussed in <xref linkend="ch-creating-rpms"/> , the rpmbuild command expands source
-        RPMs to the /usr/src/redhat directory. Under this directory, the
-        RPM system assumes five subdirectories, listed in Table 10-1.
+        As discussed in <xref linkend="ch-creating-rpms"/> , the
+        rpmbuild command expands source RPMs to the /usr/src/redhat
+        directory. Under this directory, the RPM system assumes five
+        subdirectories, listed in Table 10-1.
       </para>
       <para>
         Table 10-1 Default RPM directories
@@ -291,11 +292,13 @@
         Cross Reference
       </para>
       <para>
-        These directories are the default directories. See <xref linkend="ch-specfile-syntax"/> 
-        for changing RPM default values. In addition, these are the
-        defaults for &RHL;. See Chapters 19 and 20 for
-        discussions on other versions of Linux and other non-Linux
-        operating systems, respectively.
+        These directories are the default directories. See
+        <xref linkend="ch-specfile-syntax"/> for changing RPM default
+        values. In addition, these are the defaults for &RHL;. See
+        <xref linkend="ch-other-linuxes"/> and
+        <xref linkend="ch-other-linuxes"/> for discussions on other
+        versions of Linux and other non-Linux operating systems,
+        respectively.
       </para>
       <para>
         With the knowledge of the spec file syntax covered in the
@@ -432,15 +435,15 @@
         <para>
           Many graphical installation tools divide packages by these
           categories, so you want to fit into the existing group names
-          if possible. (See <xref linkend="ch-using-rpm-db"/>  for more on querying group
-          information from RPMs.) The official list of groups are
-          located in the file /usr/share/doc/rpm-4.1/GROUPS for RPM 4.1,
-          and in a similar location for other RPM versions.
+          if possible. (See <xref linkend="ch-using-rpm-db"/> for more
+          on querying group information from RPMs.) The official list of
+          groups are located in the file /usr/share/doc/rpm-4.1/GROUPS
+          for RPM 4.1, and in a similar location for other RPM versions.
         </para>
         <para>
           The Distribution: directive is used by Linux distribution
-          vendors such as &RH; to identify that the package is part
-          of a given distribution, or was built for a particular
+          vendors such as &RH; to identify that the package is part of a
+          given distribution, or was built for a particular
           distribution. Most packages created outside of the Linux
           vendors don???t provide this directive.
         </para>
@@ -615,8 +618,9 @@
           Cross Reference
         </para>
         <para>
-          Chapters 19 and 20 cover RPMs on other versions of Linux and
-          other operating systems, respectively.
+          <xref linkend="ch-other-linuxes"/> and
+          <xref linkend="ch-other-os"/> cover RPMs on other versions of
+          Linux and other operating systems, respectively.
         </para>
       </sect3>
     </sect2>
@@ -822,8 +826,9 @@
         Cross Reference
       </para>
       <para>
-        <xref linkend="ch-packaging-guidelines"/>  discusses packaging guidelines and best practices.
-        Starting from pristine sources is one of the best practices.
+        <xref linkend="ch-packaging-guidelines"/> discusses packaging
+        guidelines and best practices. Starting from pristine sources is
+        one of the best practices.
       </para>
       <para>
         Similar to the sources directives, you can define a Nopatch:
@@ -849,7 +854,8 @@
       Cross Reference
     </para>
     <para>
-      <xref linkend="ch-creating-rpms"/>  covers make and other Linux build tools.
+      <xref linkend="ch-creating-rpms"/> covers make and other Linux
+      build tools.
     </para>
     <para>
       In RPM terms, building the package is split into four steps:
@@ -1215,8 +1221,8 @@
       </para>
       <para>
         If you intend to support relocatable packages, covered in
-        <xref linkend="ch-advanced-packaging"/> , you will likely need to pass a --prefix option to
-        the configure script. For example:
+        <xref linkend="ch-advanced-packaging"/> , you will likely need
+        to pass a --prefix option to the configure script. For example:
       </para>
       <para>
         %build
@@ -1370,8 +1376,9 @@
         Cross Reference
       </para>
       <para>
-        <xref linkend="ch-advanced-packaging"/>  covers triggers, another form of script that gets run
-        when packages are installed or removed.
+        <xref linkend="ch-advanced-packaging"/> covers triggers, another
+        form of script that gets run when packages are installed or
+        removed.
       </para>
       <para>
         Start your scripts with the RPM section marker for the given
@@ -1879,7 +1886,8 @@
         Cross Reference
       </para>
       <para>
-        See <xref linkend="ch-using-rpm-db"/>  for more on package verification.
+        See <xref linkend="ch-using-rpm-db"/> for more on package
+        verification.
       </para>
       <para>
         The %verify directive names the tests to include or not include.
@@ -2110,8 +2118,8 @@
       </para>
       <para>
         You can also store this setting in a macro file so that it
-        applies for all packages you build. See <xref linkend="ch-customizing-rpm"/>  for more on
-        macro files.
+        applies for all packages you build. See
+        <xref linkend="ch-customizing-rpm"/> for more on macro files.
       </para>
       <para>
         While the Fascist build policy may be an annoyance, it can prove
@@ -2475,7 +2483,7 @@
         Cross Reference
       </para>
       <para>
-        <xref linkend="ch-scripting"/>  covers shell scripting with RPM.
+        <xref linkend="ch-scripting"/> covers shell scripting with RPM.
       </para>
       <para>
         With parameters, you can expand the normal definition of a macro


Index: rpm-guide-transactions-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-transactions-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-transactions-en.xml	10 Nov 2005 22:30:07 -0000	1.4
+++ rpm-guide-transactions-en.xml	14 Nov 2005 21:55:05 -0000	1.5
@@ -152,7 +152,8 @@
       Cross Reference
     </para>
     <para>
-      The gnorpm command is covered in <xref linkend="ch-management-software"/> . The rpmrebuild package
+      The gnorpm command is covered in
+      <xref linkend="ch-management-software"/> . The rpmrebuild package
       is covered in the "Saving Old Packages" section in this chapter.
     </para>
     <para>
@@ -322,7 +323,8 @@
           Cross Reference
         </para>
         <para>
-          <xref linkend="ch-using-rpm-db"/>  describes the --queryformat option.
+          <xref linkend="ch-using-rpm-db"/> describes the --queryformat
+          option.
         </para>
         <para>
           There is also a transaction ID for removal, the REMOVETID. You
@@ -499,11 +501,11 @@
       <para>
         Because of all these limitations, rollbacks do not work in all
         situations. In place of the --rollback option, you can use the
-        query shortcuts introduced in <xref linkend="ch-using-rpm-db"/>  and find the packages
-        you have installed recently (if that is what you want to roll
-        back). In this case, you can use the rpm command to remove the
-        packages you want to get rid of and reinstall the packages you
-        want to restore.
+        query shortcuts introduced in <xref linkend="ch-using-rpm-db"/>
+        and find the packages you have installed recently (if that is
+        what you want to roll back). In this case, you can use the rpm
+        command to remove the packages you want to get rid of and
+        reinstall the packages you want to restore.
       </para>
       <para>
         In many cases, this manual approach is safest, and you will have
@@ -527,8 +529,9 @@
       The package created by the --repackage option is not a complete
       RPM package. You can use the rpmbuild command to make it into a
       complete package, but by itself, it will not be a complete
-      package. See Chapters 10, 11, and 12 for more on building
-      packages.
+      package. See <xref linkend="ch-specfiles"/>,
+      <xref linkend="ch-advanced-packaging"/>, and
+      <xref linkend="ch-rpmbuild"/> for more on building packages.
     </para>
     <para/>
     <para>
@@ -547,8 +550,8 @@
       Note
     </para>
     <para>
-      The up2date name comes from the &RH; service for keeping a
-      system up to date with regard to package versions.
+      The up2date name comes from the &RH; service for keeping a system
+      up to date with regard to package versions.
     </para>
     <para>
       For example, say you have a package, jikes (a Java programming


Index: rpm-guide-using-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-using-rpm-en.xml	10 Nov 2005 22:30:07 -0000	1.4
+++ rpm-guide-using-rpm-en.xml	14 Nov 2005 21:55:05 -0000	1.5
@@ -79,7 +79,9 @@
       Cross Reference
     </para>
     <para>
-      Chapters 9 and 12 cover building RPMs from source RPMs.
+      <xref linkend="ch-creating-rpms"/> and
+      <xref linkend="ch-rpmbuild"/> cover building RPMs from source
+      RPMs.
     </para>
     <para>
       The rpm command provides three main operations for upgrading and
@@ -111,8 +113,8 @@
       <para/>
       <para>
         Almost all installation steps use the rpm command with the ???U
-        option, short for upgrade, as introduced in <xref linkend="ch-rpm-overview"/> . The basic
-        syntax is:
+        option, short for upgrade, as introduced in
+        <xref linkend="ch-rpm-overview"/> . The basic syntax is:
       </para>
       <para>
         rpm -U package_name
@@ -144,9 +146,9 @@
       </para>
       <para>
         This warning comes from the fact that the package was signed,
-        but the key was not found. <xref linkend="ch-rpmbuild"/>  covers signing packages.
-        In most cases, warnings such as this one are not that serious.
-        Errors, though, should be treated seriously.
+        but the key was not found. <xref linkend="ch-rpmbuild"/> covers
+        signing packages. In most cases, warnings such as this one are
+        not that serious. Errors, though, should be treated seriously.
       </para>
       <para>
         Note
@@ -971,12 +973,11 @@
         </para>
         <para>
           Note that when you purchase an upgraded version of Linux, such
-          as &RHL;, all the packages with the product should be
-          properly aligned with each other as to versions. This
-          alignment problem is an issue that the Linux vendors, such as
-          &RH;, need to take care of. The main problems occur when
-          you need packages beyond those offered with your Linux
-          distribution.
+          as &RHL;, all the packages with the product should be properly
+          aligned with each other as to versions. This alignment problem
+          is an issue that the Linux vendors, such as &RH;, need to take
+          care of. The main problems occur when you need packages beyond
+          those offered with your Linux distribution.
         </para>
         <para>
           To combine some of these options, you can use --force, which
@@ -1037,11 +1038,11 @@
         </para>
         <para>
           The --aid option depends on a separate package that contains
-          an RPM database with all packages installed. For &RH;
-          Linux, this package is rpmdb-redhat. This separate database,
-          built as if all packages were installed (all packages that
-          come with &RHL; in this case), allows the rpm command
-          to search for which packages would solve dependencies.
+          an RPM database with all packages installed. For &RH; Linux,
+          this package is rpmdb-redhat. This separate database, built as
+          if all packages were installed (all packages that come with
+          &RHL; in this case), allows the rpm command to search for
+          which packages would solve dependencies.
         </para>
       </sect3>
       <sect3>
@@ -1174,8 +1175,8 @@
         </para>
         <para>
           In addition to pre- and post-installation scripts, the RPM
-          system supports triggers, a topic covered in detail in Chapter
-          11.
+          system supports triggers, a topic covered in detail in
+          <xref linkend="ch-advanced-packaging"/>.
         </para>
         <para>
           During installation, you can tell the rpm command not to
@@ -1454,8 +1455,8 @@
           configuration file on disk. This is where the rpm command
           starts working with some upgrade rules. Note that this special
           processing only applies to files marked as configuration files
-          within the RPM. <xref linkend="ch-specfiles"/>  covers how to mark files as
-          configuration files.
+          within the RPM. <xref linkend="ch-specfiles"/> covers how to
+          mark files as configuration files.
         </para>
         <para>
           If the file on disk is identical to the file in the original
@@ -1689,9 +1690,9 @@
         example, rarely come with source code. In this case, obviously,
         no source RPMs are available. Or, a source RPM for a commercial
         application may provide no source code, but still provide a way
-        to build the resulting application. See <xref linkend="ch-specfiles"/>  for more on
-        the source files and options for not including the sources in a
-        source RPM.
+        to build the resulting application. See
+        <xref linkend="ch-specfiles"/> for more on the source files and
+        options for not including the sources in a source RPM.
       </para>
       <para>
         Open-source Software
@@ -1992,7 +1993,8 @@
       Cross Reference
     </para>
     <para>
-      See <xref linkend="ch-customizing-rpm"/>  for more on the --showrc option.
+      See <xref linkend="ch-customizing-rpm"/> for more on the --showrc
+      option.
     </para>
     <para>
       The --version option tells the rpm command to print out the



From fedora-docs-commits at redhat.com  Tue Nov 15 00:13:11 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Mon, 14 Nov 2005 19:13:11 -0500
Subject: yum-software-management yum-software-management-en.xml,1.48,1.49
Message-ID: <200511150013.jAF0DBRs017204@cvs-int.fedora.redhat.com>

Author: elliss

Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17177

Modified Files:
	yum-software-management-en.xml 
Log Message:
- Fixed bug 166122
- Revised information on Fedora repositories to mention development repositories
- Renamed "Manual Installation" section for clarity
- Updated section on proxy servers



Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- yum-software-management-en.xml	13 Oct 2005 11:34:47 -0000	1.48
+++ yum-software-management-en.xml	15 Nov 2005 00:13:03 -0000	1.49
@@ -4,7 +4,7 @@
 <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
 %FEDORA-ENTITIES-EN;
 
-<!ENTITY BOOKID "yum-software-management-1.0.3 (2005-10-13)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKID "yum-software-management-1.0.4 (2005-11-15)"> <!-- change version of manual and date here -->
 
 <!-- Bugzilla bug number for the draft notice -->
 <!ENTITY BUG-NUM "155190">
@@ -68,35 +68,45 @@
         </revdescription>
       </revision>
       <revision>
-	<revnumber>1.0.1</revnumber>
-	<date>2005-08-18</date>
-	<authorinitials>StuartEllis</authorinitials>
-	<revdescription>
-	  <para>
-	    Added information on installing without repository and
-	    manually adding keys.
-	  </para>
-	</revdescription>
+        <revnumber>1.0.1</revnumber>
+        <date>2005-08-18</date>
+        <authorinitials>StuartEllis</authorinitials>
+        <revdescription>
+          <para>
+            Added information on installing without repository and
+            manually adding keys.
+          </para>
+        </revdescription>
+      </revision>
+      <revision>
+        <revnumber>1.0.2</revnumber>
+        <date>2005-08-26</date>
+        <authorinitials>StuartEllis</authorinitials>
+        <revdescription>
+          <para>
+            Fix localinstall information.
+          </para>
+        </revdescription>
       </revision>
       <revision>
-	<revnumber>1.0.2</revnumber>
-	<date>2005-08-26</date>
-	<authorinitials>StuartEllis</authorinitials>
-	<revdescription>
-	  <para>
-	    Fix localinstall information.
-	  </para>
-	</revdescription>
+        <revnumber>1.0.3</revnumber>
+        <date>2005-10-13</date>
+        <authorinitials>PaulWFrields</authorinitials>
+        <revdescription>
+          <para>
+            Fix wording (#170584).
+          </para>
+        </revdescription>
       </revision>
       <revision>
-	<revnumber>1.0.3</revnumber>
-	<date>2005-10-13</date>
-	<authorinitials>PaulWFrields</authorinitials>
-	<revdescription>
-	  <para>
-	    Fix wording (#170584).
-	  </para>
-	</revdescription>
+        <revnumber>1.0.4</revnumber>
+        <date>2005-11-15</date>
+        <authorinitials>StuartEllis</authorinitials>
+        <revdescription>
+          <para>
+            Updated section on proxy servers. Fixed #166122.
+          </para>
+        </revdescription>
       </revision>
     </revhistory>
   </articleinfo>
@@ -184,12 +194,11 @@
     <section id="sn-yum-additional-resources">
       <title>Additional Resources</title>
       <indexterm>
-        <primary>yum</primary>
-        <secondary>documentation</secondary>
-      </indexterm>
-      <indexterm>
-        <primary>yum</primary>
-        <secondary>man pages</secondary>
+      <primary>yum</primary>
+      <secondary>documentation</secondary>
+      </indexterm> <indexterm>
+      <primary>yum</primary>
+      <secondary>man pages</secondary>
       </indexterm>
       <para>
         The <command>yum</command> utility has features and options not
@@ -203,19 +212,12 @@
 man yum.conf</userinput>
 </screen>
       <indexterm>
-        <primary>yum</primary>
-        <secondary>web sites</secondary>
-      </indexterm>
-      <indexterm>
-        <primary>yum</primary>
-        <secondary>mailing lists</secondary>
+      <primary>yum</primary>
+      <secondary>web sites</secondary>
+      </indexterm> <indexterm>
+      <primary>yum</primary>
+      <secondary>mailing lists</secondary>
       </indexterm>
-<!-- Hopefully this is not too confusing below.  This is sort of a -->
-<!-- grammar/usage issue. If you use a variablelist, you don't want to -->
-<!-- use sentences, but rather headings, in the term area.  Alternately, -->
-<!-- if you like sentences, just use a para instead for the whole -->
-<!-- collection of links. [PWF] -->
-<!-- SE: Multiple links in a paragraph is pretty ugly. Not that I like this layout either :)  -->
       <para>
         Other useful <command>yum</command> resources on the Internet
         include:
@@ -255,6 +257,17 @@
           </listitem>
         </varlistentry>
       </variablelist>
+      <tip>
+        <title>Check &BZ; First</title>
+        <para>
+          If you encounter a persistent error with a specific operation,
+          visit &BZ-URL; and review the bug reports for the package or
+          packages involved. An error in a package may cause all
+          <command>yum</command> operations that rely on that package to
+          fail. Please file bug reports for &FED; packages, including
+          <command>yum</command>, on this &BZ; web site.
+        </para>
+      </tip>
     </section>
   </section>
 
@@ -264,8 +277,8 @@
     <section id="sn-about-packages">
       <title>About Packages</title>
       <indexterm>
-        <primary>packages</primary>
-        <secondary>defined</secondary>
+      <primary>packages</primary>
+      <secondary>defined</secondary>
       </indexterm>
       <para>
         &FED; software and documentation is supplied in the form of
@@ -287,13 +300,23 @@
         the public keys for approved package sources. The system
         administrator configures these approved package sources.
       </para>
+
+      <note>
+        <title>All &FED; Packages are Open Source Software</title>
+
+        <para>
+          All of the software provided by the &FP; is open source
+          software. You may download and install &FED; packages on as
+          many systems as desired.
+        </para>
+      </note>
     </section>
 
     <section id="sn-about-repositories">
       <title>About Repositories</title>
       <indexterm>
-        <primary>repositories</primary>
-        <secondary>defined</secondary>
+      <primary>repositories</primary>
+      <secondary>defined</secondary>
       </indexterm>
       <para>
         A <firstterm>repository</firstterm> is a prepared directory or
@@ -307,48 +330,71 @@
       </para>
 
       <para>
-        The package management utilities in &FC; are already configured
-        to use a network of servers that provide three repositories:
+        A network of servers provide several repositories for each
+        version of &FED;. The package management utilities in &FC; are
+        already configured to use three of these repositories:
       </para>
 
-      <itemizedlist>
-        <listitem>
-          <para>
-            The packages that make up &FC;, as it is released on disc
-          </para>
-        </listitem>
-        <listitem>
-          <para>
-            Updated versions of &FC; software
-          </para>
-        </listitem>
-        <listitem>
-          <para>
-            A large selection of additional software, known as &FEX;
-          </para>
-        </listitem>
-      </itemizedlist>
+      <variablelist>
+        <varlistentry>
+          <term>
+	    Base
+	  </term>
+          <listitem>
+            <para>
+              The packages that make up a &FC; release, as it is on disc
+            </para>
+          </listitem>
+        </varlistentry>
+
+        <varlistentry>
+          <term>
+	    Updates
+	  </term>
+          <listitem>
+            <para>
+              Updated versions of packages that are provided in Base
+            </para>
+          </listitem>
+        </varlistentry>
+
+        <varlistentry>
+          <term>
+	    &EX;
+	  </term>
+          <listitem>
+            <para>
+              Packages for a large selection of additional software
+            </para>
+          </listitem>
+        </varlistentry>
+      </variablelist>
 
       <note>
         <title>Previous Versions of &FED;</title>
 
         <para>
-          &FED; &FCLOCALVER; automatically supports all three
-          repositories. You must manually configure &FED; 3 systems to
-          use &FEX;, as noted in
+          &FED; &FCLOCALVER; automatically supports the three
+          repositories listed above. You must manually configure &FED; 3
+          systems to use &FEX;, as noted in
           <xref linkend="sn-using-repositories"/>.
         </para>
       </note>
 
-      <note>
-        <title>All &FED; Packages are Open Source Software</title>
+      <warning>
+        <title>&FED; Development Repositories</title>
 
         <para>
-          All of the software provided by the &FP; is open source
-          software. You may download and install software from the &FP;
-          network of repositories on as many systems as desired.
+          &FC; also includes settings for several alternative
+          repositories. These provide packages for various types of test
+          system, and replace one or more of the standard repositories.
+          Only enable support for one of the following repositories if
+          you test or develop &FED; software:
+          <filename>fedora-devel</filename> (Rawhide),
+          <filename>fedora-extras-devel</filename>, and
+          <filename>updates-testing</filename>.
         </para>
-      </note>
+      </warning>
 
       <para>
         Third-party software developers also provide repositories for
@@ -357,8 +403,8 @@
         <xref linkend="sn-using-repositories"/>.
       </para>
       <indexterm>
-        <primary>package groups</primary>
-        <secondary>defined</secondary>
+      <primary>package groups</primary>
+      <secondary>defined</secondary>
       </indexterm>
       <para>
         You may also use the <firstterm>package groups</firstterm>
@@ -408,8 +454,8 @@
     <section id="sn-about-dependencies">
       <title>About Dependencies</title>
       <indexterm>
-        <primary>dependencies</primary>
-        <secondary>defined</secondary>
+      <primary>dependencies</primary>
+      <secondary>defined</secondary>
       </indexterm>
       <para>
         Some of the files installed on a &FED; distribution are
@@ -436,17 +482,16 @@
     <section id="sn-package-names">
       <title>Understanding Package Names</title>
       <indexterm>
-        <primary>packages</primary>
-        <secondary>hardware compatibility</secondary>
-      </indexterm>
-      <indexterm>
-        <primary>packages</primary>
-        <secondary>naming</secondary>
+      <primary>packages</primary>
+      <secondary>hardware compatibility</secondary>
+      </indexterm> <indexterm>
+      <primary>packages</primary>
+      <secondary>naming</secondary>
       </indexterm>
       <para>
         Each package file has a long name that indicates several key
-        pieces of information. This is the full name of the
-        <filename>tsclient</filename> package supplied with &FC;:
+        pieces of information. For example, this is the full name of a
+        <filename>tsclient</filename> package:
       </para>
 <screen>
 <filename>tsclient-0.132-6.i386.rpm</filename>
@@ -582,18 +627,16 @@
   <section id="sn-software-management-tools">
     <title>Software Management Tools in &FC;</title>
     <indexterm>
-      <primary>Add/Remove Applications utility</primary>
-    </indexterm>
-    <indexterm>
-      <primary>Alert Icon</primary>
-    </indexterm>
-    <indexterm>
-      <primary>up2date</primary>
+    <primary>Add/Remove Applications utility</primary>
+    </indexterm> <indexterm>
+    <primary>Alert Icon</primary>
+    </indexterm> <indexterm>
+    <primary>up2date</primary>
     </indexterm>
     <para>
       The <command>yum</command> utility is a complete software
-      management system. &FC; also includes several other
-      applications that can supplement <command>yum</command>.
+      management system. &FC; also includes several other applications
+      that can supplement <command>yum</command>.
     </para>
 
     <para>
@@ -644,8 +687,8 @@
   <section id="sn-managing-packages">
     <title>Managing Software with <command>yum</command></title>
     <indexterm>
-      <primary>yum</primary>
-      <secondary>software management</secondary>
+    <primary>yum</primary>
+    <secondary>software management</secondary>
     </indexterm>
     <para>
       Use the <command>yum</command> utility to modify the software on
@@ -778,7 +821,7 @@
     <para>
       Check the public key, and then press <keycap>y</keycap> to import
       the key and authorize the key for use. If you press
-      <keycap>N</keycap> or <keycap>Enter</keycap> ,
+      <keycap>N</keycap> or <keycap>Enter</keycap>,
       <command>yum</command> stops without installing any packages.
     </para>
 
@@ -789,6 +832,13 @@
       packages required for the transaction are successfully downloaded
       and verified, <command>yum</command> applies them to your system.
     </para>
+
+    <para>
+      Every completed transaction records the affected packages in the
+      log file <filename>/var/log/yum.log</filename>. You may only read
+      this file with <systemitem class="username">root</systemitem>
+      access.
+    </para>
     <tip>
       <title>Downloads are Cached</title>
       <para>
@@ -803,12 +853,11 @@
     <section id="sn-yum-installing-withrepositories">
       <title>Installing New Software with <command>yum</command></title>
       <indexterm>
-        <primary>installing software</primary>
-        <see>software, installing</see>
-      </indexterm>
-      <indexterm>
-        <primary>software</primary>
-        <secondary>installing</secondary>
+      <primary>installing software</primary>
+      <see>software, installing</see>
+      </indexterm> <indexterm>
+      <primary>software</primary>
+      <secondary>installing</secondary>
       </indexterm>
       <para>
         To install the package <filename>tsclient</filename>, enter the
@@ -854,12 +903,11 @@
     <section id="sn-yum-updating-withrepositories">
       <title>Updating Software with <command>yum</command></title>
       <indexterm>
-        <primary>updating</primary>
-        <secondary>software packages</secondary>
-      </indexterm>
-      <indexterm>
-        <primary>software</primary>
-        <secondary>updating</secondary>
+      <primary>updating</primary>
+      <secondary>software packages</secondary>
+      </indexterm> <indexterm>
+      <primary>software</primary>
+      <secondary>updating</secondary>
       </indexterm>
       <para>
         To update the <filename>tsclient</filename> package to the
@@ -913,11 +961,10 @@
     <section id="sn-yum-removing-software">
       <title>Removing Software with <command>yum</command></title>
       <indexterm>
-        <primary>removing software</primary>
-      </indexterm>
-      <indexterm>
-        <primary>software</primary>
-        <secondary>removing</secondary>
+      <primary>removing software</primary>
+      </indexterm> <indexterm>
+      <primary>software</primary>
+      <secondary>removing</secondary>
       </indexterm>
       <para>
         To remove software, <command>yum</command> examines your system
@@ -968,12 +1015,11 @@
   <section id="sn-searching-packages">
     <title>Searching for Packages with <command>yum</command></title>
     <indexterm>
-      <primary>packages</primary>
-      <secondary>locating</secondary>
-    </indexterm>
-    <indexterm>
-      <primary>searching</primary>
-      <secondary>for packages</secondary>
+    <primary>packages</primary>
+    <secondary>locating</secondary>
+    </indexterm> <indexterm>
+    <primary>searching</primary>
+    <secondary>for packages</secondary>
     </indexterm>
     <para>
       Use the search features of <command>yum</command> to find software
@@ -1126,12 +1172,11 @@
   <section id="sn-updating-your-system">
     <title>Updating Your System with <command>yum</command></title>
     <indexterm>
-      <primary>updating</primary>
-      <secondary>full system</secondary>
-    </indexterm>
-    <indexterm>
-      <primary>yum</primary>
-      <secondary>updating full system</secondary>
+    <primary>updating</primary>
+    <secondary>full system</secondary>
+    </indexterm> <indexterm>
+    <primary>yum</primary>
+    <secondary>updating full system</secondary>
     </indexterm>
     <para>
       Use the <option>update</option> option to upgrade all of your
@@ -1153,7 +1198,7 @@
     <section id="sn-automatic-updating">
       <title>Automatically Updating Your System</title>
       <indexterm>
-        <primary>automatic updating</primary>
+      <primary>automatic updating</primary>
       </indexterm>
       <para>
         The <filename>yum</filename> package supplied with &FC; includes
@@ -1187,15 +1232,13 @@
   <section id="sn-using-repositories">
     <title>Using Other Software Repositories</title>
     <indexterm>
-      <primary>&FEX;</primary>
-    </indexterm>
-    <indexterm>
-      <primary>repositories</primary>
-      <secondary>finding</secondary>
-    </indexterm>
-    <indexterm>
-      <primary>searching</primary>
-      <secondary>for repositories</secondary>
+    <primary>&FEX;</primary>
+    </indexterm> <indexterm>
+    <primary>repositories</primary>
+    <secondary>finding</secondary>
+    </indexterm> <indexterm>
+    <primary>searching</primary>
+    <secondary>for repositories</secondary>
     </indexterm>
     <para>
       &FED; systems automatically use the &FP; repositories. These
@@ -1230,8 +1273,8 @@
     <section id="sn-adding-repositories">
       <title>Adding a Repository as a Package Source</title>
       <indexterm>
-        <primary>repositories</primary>
-        <secondary>adding to yum</secondary>
+      <primary>repositories</primary>
+      <secondary>adding to yum</secondary>
       </indexterm>
       <para>
         To add an extra repository, place a definition file in the
@@ -1287,8 +1330,8 @@
     <section id="sn-authorizing-package-sources">
       <title>Manually Authorizing Package Sources</title>
       <indexterm>
-        <primary>public keys</primary>
-        <secondary>adding</secondary>
+      <primary>public keys</primary>
+      <secondary>adding</secondary>
       </indexterm>
       <para>
         To manually add a public key to your <command>rpm</command>
@@ -1334,12 +1377,11 @@
     <section id="sn-compat-repositories">
       <title>Understanding Repository Compatibility</title>
       <indexterm>
-        <primary>packages</primary>
-        <secondary>software compatibility</secondary>
-      </indexterm>
-      <indexterm>
-        <primary>repositories</primary>
-        <secondary>compatibility</secondary>
+      <primary>packages</primary>
+      <secondary>software compatibility</secondary>
+      </indexterm> <indexterm>
+      <primary>repositories</primary>
+      <secondary>compatibility</secondary>
       </indexterm>
       <para>
         The &FEX; repository provides packages which are built to the
@@ -1394,6 +1436,78 @@
     </section>
   </section>
 
+  <section id="sn-yum-installing-frompackage">
+    <title>Installing Software from an Isolated Package</title>
+    <indexterm>
+    <primary>installing software</primary>
+    <secondary>from a package</secondary>
+    <see>software, installing from a package</see>
+    </indexterm> <indexterm>
+    <primary>software</primary>
+    <secondary>installing from a package</secondary>
+    </indexterm>
+    <para>
+      Use repositories and the standard <command>yum</command> commands
+      to locate and install new software, unless the software package is
+      not available from any repository. In these cases, use the
+      <option>localinstall</option> function to install the software
+      from the package file.
+    </para>
+
+    <important>
+      <title>Public Key is Required</title>
+
+      <para>
+        Ensure that the public key for the package source has been
+        imported before you install a package without a repository.
+        Refer to <xref linkend="sn-authorizing-package-sources"/>.
+      </para>
+    </important>
+
+    <para>
+      Enter this command to install the package
+      <filename>tsclient-0.132-4.i386.rpm</filename>:
+    </para>
+<screen>
+<userinput>su -c 'yum localinstall <replaceable>tsclient-0.132-4.i386.rpm</replaceable>'</userinput>
+</screen>
+    <para>
+      At the prompt, enter the
+      <systemitem
+	class="username">root</systemitem> password.
+    </para>
+
+    <note>
+      <title>Previously Installed Software is Updated</title>
+
+      <para>
+        If the package provides a later version of software that is
+        already installed on your system, <command>yum</command> updates
+        the installed software.
+      </para>
+    </note>
+
+    <para>
+      If the package requires software that is not installed on your
+      system, <command>yum</command> attempts to meet the dependencies
+      with packages from the configured repositories. You may need to
+      manually download and install additional packages in order to
+      satisfy all of the dependencies.
+    </para>
+
+    <caution>
+      <title>Maintaining Manually Installed Software</title>
+
+      <para>
+        If you install software that is not provided by a repository,
+        <command>yum update</command> cannot automatically upgrade it as
+        new versions become available. To ensure that you have the
+        latest packages, subscribe to e-mail or RSS services that notify
+        you when new versions are released.
+      </para>
+    </caution>
+  </section>
+
   <section id="sn-yum-maintenance">
     <title>Maintaining <command>yum</command></title>
 
@@ -1409,12 +1523,11 @@
     <section id="sn-removing-sources">
       <title>Disabling or Removing Package Sources</title>
       <indexterm>
-        <primary>repositories</primary>
-        <secondary>disabling in yum</secondary>
-      </indexterm>
-      <indexterm>
-        <primary>repositories</primary>
-        <secondary>removing from yum</secondary>
+      <primary>repositories</primary>
+      <secondary>disabling in yum</secondary>
+      </indexterm> <indexterm>
+      <primary>repositories</primary>
+      <secondary>removing from yum</secondary>
       </indexterm>
       <para>
         Set <command>enable=0</command> in a definition file to prevent
@@ -1526,8 +1639,8 @@
     <section id="sn-yum-clearance">
       <title>Clearing the <command>yum</command> Caches</title>
       <indexterm>
-        <primary>yum</primary>
-        <secondary>cleaning caches</secondary>
+      <primary>yum</primary>
+      <secondary>cleaning caches</secondary>
       </indexterm>
       <para>
         By default, <command>yum</command> retains the packages and
@@ -1558,114 +1671,61 @@
     </section>
   </section>
 
-<!-- SE: The sections below are important, but only for certain situations - they do not represent the normal use of yum. Perhaps they should be explicitly marked as appendices ?  -->
-
-  <section id="sn-yum-installing-frompackage">
-    <title>Manually Installing Software</title>
-    <indexterm>
-      <primary>installing software</primary>
-      <secondary>from a package</secondary>
-      <see>software, installing from a package</see>
-    </indexterm>
+  <section id="sn-yum-proxy-server">
+    <title>Using <command>yum</command> with a Proxy Server</title>
     <indexterm>
-      <primary>software</primary>
-      <secondary>installing from a package</secondary>
+    <primary>proxy server</primary>
+    </indexterm> <indexterm>
+    <primary>yum</primary>
+    <secondary>using with a proxy server</secondary>
     </indexterm>
     <para>
-      Use repositories and the standard <command>yum</command> commands
-      to locate and install new software, unless the software package is
-      not available from any repository. In these cases, use the
-      <option>localinstall</option> function to install the software
-      from the package file.
+      By default, <command>yum</command> accesses network repositories
+      with HTTP. All <command>yum</command> HTTP operations use
+      HTTP/1.1, and are compatible with web proxy servers that support
+      this standard. You may also access FTP repositories, and configure
+      <command>yum</command> to use an FTP proxy server. The
+      <filename>squid</filename> package provides a proxy service for
+      both HTTP/1.1 and FTP connections.
     </para>
-
-    <important>
-      <title>Public Key is Required</title>
-
+    <tip>
+      <title>Modifying <command>yum</command> for Network Compatibility</title>
       <para>
-        Ensure that the public key for the package source has been
-        imported before you install a package without a repository.
-        Refer to <xref linkend="sn-authorizing-package-sources"/>.
+        Refer to the <command>man</command> page for
+        <filename>yum.conf</filename> for information on HTTP settings
+        that may be modified for compatibility with nonstandard web
+        proxy servers. Alternatively, configure <command>yum</command>
+        to use an FTP proxy server, and access repositories that support
+        FTP. The &FED; repositories support both HTTP and FTP.
       </para>
-    </important>
-
-    <para>
-      Enter this command to install the package
-      <filename>tsclient-0.132-4.i386.rpm</filename>:
-    </para>
-<screen>
-<userinput>su -c 'yum localinstall <replaceable>tsclient-0.132-4.i386.rpm</replaceable>'</userinput>
-</screen>
-    <para>
-      At the prompt, enter the
-      <systemitem
-	class="username">root</systemitem> password.
-    </para>
-
-    <note>
-      <title>Previously Installed Software is Updated</title>
+    </tip>
+    <section id="sn-yum-proxy-server-global">
+      <title>Configuring Proxy Server Access</title>
 
       <para>
-        If the package provides a later version of software that is
-        already installed on your system, <command>yum</command> updates
-        the installed software.
+        To enable all <command>yum</command> operations to use a proxy
+        server, specify the proxy server details in
+        <filename>/etc/yum.conf</filename>. The <option>proxy</option>
+        setting must specify the proxy server as a complete URL,
+        including the TCP port number. If your proxy server requires a
+        username and password, specify these by adding
+        <option>proxy_username</option> and
+        <option>proxy_password</option> settings.
       </para>
-    </note>
-
-    <para>
-      If the package requires software that is not installed on your
-      system, <command>yum</command> attempts to meet the dependencies
-      with packages from the configured repositories. You may need to
-      manually download and install additional packages in order to
-      satisfy all of the dependencies.
-    </para>
-
-    <caution>
-      <title>Maintaining Manually Installed Software</title>
 
       <para>
-        If you install software that is not provided by a repository,
-        <command>yum update</command> cannot automatically upgrade it as
-        new versions become available. To ensure that you have the
-        latest packages, subscribe to e-mail or RSS services that notify
-        you when new versions are released.
-      </para>
-    </caution>
-  </section>
-
-  <section id="sn-yum-proxy-server">
-    <title>Using <command>yum</command> with a Proxy Server</title>
-    <indexterm>
-      <primary>proxy server</primary>
-    </indexterm>
-    <indexterm>
-      <primary>yum</primary>
-      <secondary>using with a proxy server</secondary>
-    </indexterm>
-    <para>
-      You may access repositories through standard web proxy servers. If
-      your system accesses the Internet through a web proxy server,
-      specify the proxy server details in
-      <filename>/etc/yum.conf</filename>. The <option>proxy</option>
-      setting must specify the proxy server as a complete URL, including
-      the TCP port number. If your proxy server requires a username and
-      password, specify these by adding <option>proxy_username</option>
-      and <option>proxy_password</option> settings.
-    </para>
-
-    <para>
-      The settings below enable <command>yum</command> to use the proxy
-      server
-      <systemitem
+        The settings below enable <command>yum</command> to use the
+        proxy server
+        <systemitem
 	class="systemname">mycache.mydomain.com</systemitem>,
-      connecting to port 3128, with the username
-      <systemitem
+        connecting to port 3128, with the username
+        <systemitem
 	class="username">yum-user</systemitem> and the
-      password <systemitem>qwerty</systemitem>.
-    </para>
+        password <systemitem>qwerty</systemitem>.
+      </para>
 
-    <example id="config-file-httpproxy">
-      <title>Configuration File Settings for Using A Proxy Server</title>
+      <example id="config-file-httpproxy">
+        <title>Configuration File Settings for Using A Proxy Server</title>
 <screen>
 <computeroutput># The proxy server - proxy server:port number
 proxy=http://mycache.mydomain.com:3128
@@ -1673,67 +1733,72 @@
 proxy_username=yum-user
 proxy_password=qwerty</computeroutput>
 </screen>
-    </example>
+      </example>
 
-    <note>
-      <title>Global Settings</title>
+      <note>
+        <title>Global Settings</title>
 
-      <para>
-        If you define a proxy server in
-        <filename>/etc/yum.conf</filename>, <emphasis>all</emphasis>
-        users connect to the proxy server with those details when using
-        <command>yum</command>.
-      </para>
-    </note>
+        <para>
+          If you define a proxy server in
+          <filename>/etc/yum.conf</filename>, <emphasis>all</emphasis>
+          users connect to the proxy server with those details when
+          using <command>yum</command>.
+        </para>
+      </note>
+    </section>
 
-    <para>
-      To enable proxy access for a specific user, add the lines in the
-      example box below to the user's shell profile. For the default
-      <command>bash</command> shell, the profile is the file
-      <filename>~/.bash_profile</filename>. The settings below enable
-      <command>yum</command> to use the proxy server
-      <systemitem
+    <section id="sn-yum-proxy-server-peruser">
+      <title>Configuring Proxy Server Access for a Single User</title>
+
+      <para>
+        To enable proxy access for a specific user, add the lines in the
+        example box below to the user's shell profile. For the default
+        <command>bash</command> shell, the profile is the file
+        <filename>~/.bash_profile</filename>. The settings below enable
+        <command>yum</command> to use the proxy server
+        <systemitem
 	class="systemname">mycache.mydomain.com</systemitem>,
-      connecting to port 3128.
-    </para>
+        connecting to port 3128.
+      </para>
 
-    <example id="profile-script-httpproxy">
-      <title>Profile Settings for Using a Proxy Server</title>
+      <example id="profile-script-httpproxy">
+        <title>Profile Settings for Using a Proxy Server</title>
 <screen>
 <computeroutput># The Web proxy server used by this account
 http_proxy="http://mycache.mydomain.com:3128"
 export http_proxy</computeroutput>
 </screen>
-    </example>
+      </example>
 
-    <para>
-      If the proxy server requires a username and password, add these to
-      the URL. To include the username
-      <systemitem class="username">yum-user</systemitem> and the
-      password <systemitem>qwerty</systemitem>, add these settings:
-    </para>
+      <para>
+        If the proxy server requires a username and password, add these
+        to the URL. To include the username
+        <systemitem class="username">yum-user</systemitem> and the
+        password <systemitem>qwerty</systemitem>, add these settings:
+      </para>
 
-    <example id="profile-script-httpproxy-withpassword">
-      <title>Profile Settings for a Secured Proxy Server</title>
+      <example id="profile-script-httpproxy-withpassword">
+        <title>Profile Settings for a Secured Proxy Server</title>
 <screen>
 <computeroutput># The Web proxy server, with the username and password for this account
 http_proxy="http://yum-user:qwerty at mycache.mydomain.com:3128"
 export http_proxy</computeroutput>
 </screen>
-    </example>
+      </example>
 
-    <note>
-      <title>The <option>http_proxy</option> Environment Variable</title>
+      <note>
+        <title>The <option>http_proxy</option> Environment Variable</title>
 
-      <para>
-        The <command>http_proxy</command> environment variable is also
-        used by <command>curl</command> and other utilities. Although
-        <command>yum</command> itself may use
-        <command>http_proxy</command> in either upper-case or
-        lower-case, <command>curl</command> requires the name of the
-        variable to be in lower-case.
-      </para>
-    </note>
+        <para>
+          The <command>http_proxy</command> environment variable is also
+          used by <command>curl</command> and other utilities. Although
+          <command>yum</command> itself may use
+          <command>http_proxy</command> in either upper-case or
+          lower-case, <command>curl</command> requires the name of the
+          variable to be in lower-case.
+        </para>
+      </note>
+    </section>
   </section>
 
 <!-- SE: This is at the end of the document, since it looks out of place in section 1 -->



From fedora-docs-commits at redhat.com  Tue Nov 15 14:28:14 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 15 Nov 2005 09:28:14 -0500
Subject: mirror-tutorial mirror-tutorial-en.xml,1.17,1.18
Message-ID: <200511151428.jAFESExq010153@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10134

Modified Files:
	mirror-tutorial-en.xml 
Log Message:
Fixed commands to use su, removed slightly misleading language


Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- mirror-tutorial-en.xml	11 Nov 2005 16:58:48 -0000	1.17
+++ mirror-tutorial-en.xml	15 Nov 2005 14:28:05 -0000	1.18
@@ -1275,7 +1275,7 @@
 	</para>
 
 <screen>
-<userinput>yum-arch -l -s /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput>
+<userinput>su -c 'yum-arch -l -s /var/www/mirror/fedora/linux/core/&FCVER;/i386/os'</userinput>
 </screen>
 
 	<para>
@@ -1295,8 +1295,7 @@
 	  <command>yum</command> (and possibly other repository client
 	  programs). The <command>createrepo</command> command stores
 	  this data in a folder named <filename>repodata</filename>.
-	  Just as with <command>yum-arch</command>, run
-	  <command>createrepo</command> against the directory
+	  Run <command>createrepo</command> against the directory
 	  <emphasis>under which</emphasis> you want the
 	  <filename>repodata</filename> directory to appear. The
 	  <command>createrepo</command> program also searches
@@ -1310,7 +1309,7 @@
 	</para>
 
 <screen>
-<userinput>createrepo /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput>
+<userinput>su -c 'createrepo /var/www/mirror/fedora/linux/core/&FCVER;/i386/os'</userinput>
 </screen>
 
 	<para>
@@ -1326,7 +1325,7 @@
 	</para>
 
 <screen>
-<userinput>createrepo -g Fedora/base/comps.xml /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput>
+<userinput>su -c 'createrepo -g Fedora/base/comps.xml /var/www/mirror/fedora/linux/core/&FCVER;/i386/os'</userinput>
 </screen>
 
 	<para>



From fedora-docs-commits at redhat.com  Tue Nov 15 14:42:40 2005
From: fedora-docs-commits at redhat.com (Yuan Yijun (bbbush))
Date: Tue, 15 Nov 2005 09:42:40 -0500
Subject: yum-software-management yum-software-management-zh_CN.xml, NONE,
	1.1 Makefile, 1.5, 1.6
Message-ID: <200511151442.jAFEgeNn010245@cvs-int.fedora.redhat.com>

Author: bbbush

Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10226

Modified Files:
	Makefile 
Added Files:
	yum-software-management-zh_CN.xml 
Log Message:



--- NEW FILE yum-software-management-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
<!ENTITY BOOKID "yum-software-management-1.0.4 (2005-11-15)">
<!-- change version of manual and date here --><!-- Bugzilla bug number for the draft notice --><!ENTITY BUG-NUM "155190">
<!ENTITY FCLOCALVER "4">
]>
<article id="yum-software-management" lang="zh_CN">
  <articleinfo><title>?????? <command>yum</command> ????????????</title><copyright><year>2005</year><holder>Stuart Ellis</holder></copyright><copyright><year>2005</year><holder>bbbush (bbbush.yuan at gmail.com)</holder></copyright><authorgroup><author><surname>Ellis</surname><firstname>Stuart</firstname></author></authorgroup> &LEGALNOTICE; <revhistory><revision><revnumber>0.4</revnumber><date>2005-06-01</date><authorinitials>StuartEllis</authorinitials><revdescription><para>?????? CVS???</para></revdescription></revision><revision><revnumber>0.5</revnumber><date>2005-07-19</date><authorinitials>StuartEllis</authorinitials><revdescription><para>??? &FC; &FCLOCALVER; ?????????</para></revdescription></revision><revision><revnumber>0.6</revnumber><date>2005-07-25</date><authorinitials>PaulWFrields</authorinitials><revdescription><para>?????????????????????????????? BETA???</para></revdescription></revision><revision><revnumber>1.0</revnumber><date>2005-08-13</date><authorinitials!
 >PaulWFrields</authorinitials><revdescription><para>??????????????????????????????</para></revdescription></revision><revision><revnumber>1.0.1</revnumber><date>2005-08-18</date><authorinitials>StuartEllis</authorinitials><revdescription><para>??????????????????????????????????????????????????????????????????</para></revdescription></revision><revision><revnumber>1.0.2</revnumber><date>2005-08-26</date><authorinitials>StuartEllis</authorinitials><revdescription><para>??????????????????????????????</para></revdescription></revision><revision><revnumber>1.0.3</revnumber><date>2005-10-13</date><authorinitials>PaulWFrields</authorinitials><revdescription><para>???????????? (#170584)???</para></revdescription></revision><revision><revnumber>1.0.4</revnumber><date>2005-11-15</date><authorinitials>StuartEllis</authorinitials><revdescription><para>??????????????????????????????????????? #166122???</para></revdescription></revision></revhistory></articleinfo>

  <section id="sn-introduction">
    <title>??????</title>

    <section id="sn-purpose">
      <title>??????</title>

      <para>????????????????????? &FED; ?????????????????????????????????????????????????????? &FED; ????????????????????????????????? <command>yum</command> ??????????????????</para>
    </section>

    <section id="sn-software-management-audience">
      <title>??????</title>

      <para>???????????????????????????????????? &FED; ?????????</para>
    </section>

    <section id="sn-software-management-usingdoc">
      <title>??????????????????</title>

      <para>?????????????????? <command>yum</command> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <command>yum</command> ??????????????? <xref linkend="sn-software-management-concepts"/>??????????????? Linux ??????????????? <xref linkend="sn-managing-packages"/> ?????????</para>

      <note>
        <title>??????????????? &FED;</title>

        <para>?????????????????? <command>yum</command> ?????????????????? &FED; &FCLOCALVER; ???????????? &FED; 3 ????????????????????? <xref linkend="sn-authorizing-package-sources"/> ???????????????????????? <command>yum</command>???</para>
      </note>

      <para>????????????????????????????????????????????? <filename>tsclient</filename>??????????????? &FC; ?????????<filename>tsclient</filename> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <menuchoice><guimenu>Applications</guimenu><guisubmenu>Internet</guisubmenu><guimenuitem>Terminal Server Client</guimenuitem></menuchoice> ???????????????????????????????????????????????? <filename>tsclient</filename> ????????????????????????????????????&FED; ????????????????????????????????? <filename>MySQL Database</filename> ??????</para>

      <important>
        <title>????????? root ????????????</title>

        <para>??????????????? <systemitem class="username">root</systemitem> ?????????????????????????????????  &FED; ??????????????????????????????????????????????????? <systemitem class="username">root</systemitem> ??????????????????????????? <systemitem class="username">root</systemitem> ???????????????????????? <command>su <option>-c</option></command> ??????????????????????????????</para>
      </important>
    </section>

    <section id="sn-yum-additional-resources">
      <title>????????????</title>
      <indexterm>
      <primary>yum</primary>
      <secondary>??????</secondary>
      </indexterm> <indexterm>
      <primary>yum</primary>
      <secondary>?????????</secondary>
      </indexterm>
      <para>????????????????????? <command>yum</command> ??????????????????????????????????????? <command>man</command> ???????????? <command>yum(8)</command> ??? <filename>yum.conf(5)</filename> ?????????????????????????????????</para>
<screen>
<userinput>man yum
man yum.conf</userinput>
</screen>
      <indexterm>
      <primary>yum</primary>
      <secondary>??????</secondary>
      </indexterm> <indexterm>
      <primary>yum</primary>
      <secondary>????????????</secondary>
      </indexterm>
      <para>??????????????????????????? <command>yum</command> ???????????????</para>

      <variablelist>
        <varlistentry>
          <term>????????????</term>
          <listitem>
            <para>
              <ulink url="http://linux.duke.edu/projects/yum/"/>
            </para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term>?????????????????????</term>
          <listitem>
            <para>
              <ulink url="https://lists.dulug.duke.edu/mailman/listinfo/yum/"/>
            </para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term>?????????????????????</term>
          <listitem>
            <para>
              <ulink url="https://lists.dulug.duke.edu/pipermail/yum-devel/"/>
            </para>
          </listitem>
        </varlistentry>
      </variablelist>
      <tip>
        <title>???????????? &BZ;</title>
        <para>?????????????????????????????????????????????????????? &BZ-URL; ???????????????????????????????????????????????????????????????????????????????????????????????????????????? <command>yum</command> ????????????????????? &BZ; ????????????????????? &FED; ???????????????????????????</para>
      </tip>
    </section>
  </section>

  <section id="sn-software-management-concepts">
    <title>??????????????????</title>

    <section id="sn-about-packages">
      <title>???????????????</title>
      <indexterm>
      <primary>?????????</primary>
      <secondary>??????</secondary>
      </indexterm>
      <para>&FED; ????????????????????????????????? RPM <firstterm>?????????</firstterm> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????&FED; ????????????????????? &FC; ???????????????????????????????????????????????????????????????</para>

      <para>?????????????????????????????????????????????????????????????????????????????????????????? GPG <firstterm>??????</firstterm> ????????????????????????<command>yum</command> ??? <command>rpm</command> ????????????????????? <firstterm>keyring</firstterm>?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>

      <note>
        <title>&FED; ????????????????????????????????????</title>

        <para>&FP; ????????????????????????????????????????????????????????? &FED; ????????????????????????????????????????????????</para>
      </note>
    </section>

    <section id="sn-about-repositories">
      <title>????????????</title>
      <indexterm>
      <primary>??????</primary>
      <secondary>??????</secondary>
      </indexterm>
      <para><firstterm>??????</firstterm> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <command>yum</command>?????????????????????????????????????????????????????? RPM ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>

      <para>????????????????????????????????????????????? &FED; ??????????????????????????????&FC; ????????????????????????????????????????????????????????????????????????</para>

      <variablelist>
        <varlistentry>
          <term>Base</term>
          <listitem>
            <para>?????? &FC; ???????????????????????????????????????</para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term>Updates</term>
          <listitem>
            <para>Base ?????????????????????????????????</para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term>&EX;</term>
          <listitem>
            <para>???????????????????????????</para>
          </listitem>
        </varlistentry>
      </variablelist>

      <note>
        <title>??????????????? &FED;</title>

        <para>&FED; &FCLOCALVER; ?????????????????????????????????????????? &FED; 3 ?????????????????????????????????????????? &FEX;??????????????? <xref linkend="sn-using-repositories"/> ?????????</para>
      </note>

      <warning>
        <title>&FED; ????????????</title>

        <para>&FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FED; ????????????????????????????????????<filename>fedora-devel</filename> (Rawhide), <filename>fedora-extras-devel</filename>, ??? <filename>updates-testing</filename>???</para>
      </warning>

      <para>???????????????????????????????????????????????????????????????????????? &FED; ??????????????????????????????????????? &FED; ????????????????????????????????????????????? <xref linkend="sn-using-repositories"/>???</para>
      <indexterm>
      <primary>?????????</primary>
      <secondary>??????</secondary>
      </indexterm>
      <para>???????????? &FED; ??????????????? <firstterm>?????????</firstterm> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
<!-- SE: Some repositories use groups and some don't: I've tried to put this nicely. -->
<!-- SE: Using the admonition for this is not optimal, it just doesn't fit anywhere else. -->
      <note>
        <title>??????????????????</title>

        <para>??????????????? &FED; ???????????????????????????????????????????????? <command>su -c 'yum grouplist'</command>???</para>
      </note>

      <para>???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>

      <caution>
        <title>?????????????????????????????????</title>

        <para>??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FED; ????????????????????????</para>

        <para>??????????????? <command>yum</command> ????????????????????????????????????????????????????????? <command>yum</command> ?????????????????????????????????????????????????????? <xref linkend="sn-yum-installing-frompackage"/>???</para>
      </caution>
    </section>

    <section id="sn-about-dependencies">
      <title>??????????????????</title>
      <indexterm>
      <primary>????????????</primary>
      <secondary>??????</secondary>
      </indexterm>
      <para>&FED; ??????????????????????????????????????? <firstterm>???</firstterm>???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <firstterm>??????</firstterm>???????????????????????????????????????&FED; ????????????????????????????????????????????? RPM ??????????????????????????????????????? RPM ????????????</para>

      <para><command>yum</command> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<command>yum</command> ??????????????????????????????????????????</para>
    </section>

    <section id="sn-package-names">
      <title>?????????????????????</title>
      <indexterm>
      <primary>?????????</primary>
      <secondary>???????????????</secondary>
      </indexterm> <indexterm>
      <primary>?????????</primary>
      <secondary>??????</secondary>
      </indexterm>
      <para>????????????????????????????????????????????????????????????????????????????????????????????????????????? &FC; ??? <filename>tsclient</filename> ?????????????????????</para>
<screen>
<filename>tsclient-0.132-6.i386.rpm</filename>
</screen>
      <para>????????????????????????????????????????????????????????????????????????</para>

      <itemizedlist>
        <listitem>
          <para>??????????????????<filename>tsclient</filename></para>
        </listitem>
        <listitem>
          <para>???????????????????????????????????????????????????<filename>tsclient-0.132-6</filename></para>
<!-- In what instances is the release number not needed?  For many -->
<!-- package updates, only the release number might change. Although it -->
<!-- might be superfluous, it's never *bad* to include it, right? [PWF] -->
        </listitem>
        <listitem>
          <para>???????????????????????????????????????<filename>tsclient.i386</filename></para>
        </listitem>
      </itemizedlist>

      <para>?????????????????????<command>yum</command> ??? <filename>??????.??????</filename> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <emphasis>??????</emphasis> ?????????</para>

      <variablelist>
        <varlistentry>
          <term>i386</term>
          <listitem>
            <para>????????????????????? Intel ???????????????</para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term>noarch</term>
          <listitem>
            <para>??????????????????</para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term>ppc</term>
          <listitem>
            <para>?????? PowerPC ??????????????? Apple Power Macintosh</para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term>x86_64</term>
          <listitem>
            <para>?????? 64 ??? Intel ?????????????????? Opterons</para>
          </listitem>
        </varlistentry>
      </variablelist>

      <para>????????????????????????????????? Intel ????????????????????? <option>i386</option>, <option>i586</option>, <option>i686</option> ??? <option>x86_64</option> ?????????????????????????????????????????????????????? Intel ?????????VIA C3 ???????????????????????????????????????????????? <option>i586</option> ?????????????????????????????? Intel ????????????????????????????????????????????????????????? AMD ?????????????????????????????? <option>i686</option> ????????????</para>

      <para>??? <command>yum</command> ??????????????????????????????????????????????????????<command>yum</command> ????????????????????????????????????????????????????????????????????????????????????</para>

      <para>???????????????????????????????????????????????????????????????????????? <command>yum</command> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
      <tip>
        <title>???????????????</title>
        <para>???????????? <command>yum</command> ?????????????????????????????????????????????????????????<replaceable>name</replaceable>, <replaceable>name.architecture</replaceable>, <replaceable>name-version</replaceable>, <replaceable>name-version-release</replaceable>, <replaceable>name-version-release.architecture</replaceable>, ??? <replaceable>epoch:name-version-release.architecture</replaceable>???</para>
      </tip>
    </section>
  </section>

  <section id="sn-software-management-tools">
    <title>&FC; ????????????????????????</title>
    <indexterm>
    <primary>??????/????????????????????????</primary>
    </indexterm> <indexterm>
    <primary>????????????</primary>
    </indexterm> <indexterm>
    <primary>up2date</primary>
    </indexterm>
    <para><command>yum</command> ?????????????????????????????????????????????&FC; ?????????????????????????????????????????? <command>yum</command> ????????????</para>

    <para>???????????????????????? <application>Alert Icon</application>?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <application>up2date</application> ??????????????????????????????????????????????????????</para>

    <para>&FC; ?????????????????? <application>system-config-packages</application> ???????????????????????????????????????????????????????????????????????? <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guimenuitem>Add/Remove Applications</guimenuitem></menuchoice>?????? <application>up2date</application> ??? <command>yum</command> ?????????<application>system-config-packages</application> ???????????? &FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>

    <para>??????????????? <command>rpm</command> ?????????????????????????????????????????? RPM ?????????????????????????????????????????????????????????????????????????????????????????? <command>rpm</command> ????????????????????????????????????????????????????????????????????????????????????????????????<command>yum</command> ?????????????????????????????????</para>

    <caution>
      <title>?????????????????????</title>

      <para><application>up2date</application> ??? <command>yum</command> ?????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    </caution>
  </section>

  <section id="sn-managing-packages">
    <title>?????? <command>yum</command> ????????????</title>
    <indexterm>
    <primary>yum</primary>
    <secondary>????????????</secondary>
    </indexterm>
    <para>?????? <command>yum</command> ?????????????????????????????????????????????????????????</para>

    <para>
      <itemizedlist>
        <listitem>
          <para>????????????????????????</para>
        </listitem>
        <listitem>
          <para>??????????????????????????????????????????</para>
        </listitem>
        <listitem>
          <para>????????????????????????????????????</para>
        </listitem>
        <listitem>
          <para>??????????????????????????????????????????</para>
        </listitem>
      </itemizedlist>
    </para>
<!-- SE: This duplicates text from the admonition in sn-about-repositories.  It's here as well because the Fedora site has a link straight to this section -->
    <important>
      <title>????????????????????????????????????</title>

      <para>??????????????? <command>yum</command> ????????????????????????????????????????????????????????? <command>yum</command> ?????????????????????????????????????????????????????? <xref linkend="sn-yum-installing-frompackage"/>???</para>
    </important>

    <para>?????? <command>yum</command> ????????????????????????????????????????????????????????????/????????????</para>

    <para>?????????????????????<command>yum</command> ???????????????????????????????????????????????????????????????????????????????????????????????????<command>yum</command> ?????????????????????????????????????????????????????????????????????</para>

    <para>???????????????????????????<command>yum</command> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>

    <example id="yum-transaction-format">
      <title><command>yum</command> ?????????????????????</title>

      <para>????????????????????? <filename>tsclient</filename> ???????????????</para>
<screen>
<computeroutput>=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
 tsclient                i386       0.132-6          base              247 k
Installing for dependencies:
 rdesktop                i386       1.4.0-2          base              107 k

Transaction Summary
=============================================================================
Install      2 Package(s)
Update       0 Package(s)
Remove       0 Package(s)
Total download size: 355 k
Is this ok [y/N]:</computeroutput>
</screen>
    </example>

    <para>??????????????????????????????????????? <keycap>y</keycap> ????????????????????????????????? <keycap>N</keycap> ??? <keycap>Enter</keycap>(??????)???<command>yum</command> ????????????????????????????????????</para>

    <note>
      <title>???????????????</title>

      <para><command>yum</command> ????????????????????????????????????????????????????????????????????????????????????</para>
    </note>

    <para><command>yum</command> ????????????????????????????????????????????????????????? <command>rpm</command> ?????????????????????</para>

    <example id="yum-publickey-import">
      <title><command>yum</command> ?????????????????????</title>

      <para>????????????????????????????????????</para>
<screen>
<computeroutput>warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
public key not available for tsclient-0.132-6.i386.rpm
Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
Importing GPG key 0x4F2A6FD2 "Fedora Project &lt;fedora at redhat.com&gt;"
Is this ok [y/N]:</computeroutput>
</screen>
    </example>

    <para>????????????????????????????????? <keycap>y</keycap> ??????????????????????????????????????????????????? <keycap>N</keycap> ??? <keycap>Enter</keycap>(??????)???<command>yum</command> ????????????????????????????????????</para>

    <para>?????????????????????????????????????????????<command>yum</command> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<command>yum</command> ????????????????????????????????????</para>

    <para>??????????????????????????????????????? <filename>/var/log/yum.log</filename> ????????????????????????????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>
    <tip>
      <title>???????????????</title>
      <para><command>yum</command> ??????????????????????????????????????????????????????????????????????????????????????? <filename>/var/cache/yum/</filename> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    </tip>
    <section id="sn-yum-installing-withrepositories">
      <title>?????? <command>yum</command> ???????????????</title>
      <indexterm>
      <primary>????????????</primary>
      <see>???????????????</see>
      </indexterm> <indexterm>
      <primary>??????</primary>
      <secondary>??????</secondary>
      </indexterm>
      <para>??????????????? <filename>tsclient</filename>??????????????????</para>
<screen>
<userinput>su -c 'yum install <replaceable>tsclient</replaceable>'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <para>?????????????????? <filename>MySQL Database</filename>??????????????????</para>
<screen>
<userinput>su -c 'yum groupinstall "<replaceable>MySQL Database</replaceable>"'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <important>
        <title>????????????????????????</title>

        <para>????????????????????????????????????&FED; ???????????????????????????????????????????????????????????????????????????????????????????????? <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guisubmenu>Server Settings</guisubmenu><guimenuitem>Services</guimenuitem></menuchoice>?????????????????????????????? <command>chkconfig</command> ??? <command>service</command>???</para>
      </important>
    </section>

    <section id="sn-yum-updating-withrepositories">
      <title>?????? <command>yum</command> ????????????</title>
      <indexterm>
      <primary>??????</primary>
      <secondary>?????????</secondary>
      </indexterm> <indexterm>
      <primary>??????</primary>
      <secondary>??????</secondary>
      </indexterm>
      <para>????????? <filename>tsclient</filename> ?????????????????????????????????</para>
<screen>
<userinput>su -c 'yum update <replaceable>tsclient</replaceable>'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <important>
        <title>?????????????????????????????????</title>

        <para>????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
      </important>

      <para>?????????????????? <filename>MySQL Database</filename> ????????????????????????????????????</para>
<screen>
<userinput>su -c 'yum groupupdate "<replaceable>MySQL Database</replaceable>"'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <note>
        <title>??????????????????</title>

        <para>??????????????? &FED; ????????????????????????????????? <xref linkend="sn-updating-your-system"/> ?????????????????????</para>
      </note>
    </section>

    <section id="sn-yum-removing-software">
      <title>?????? <command>yum</command> ????????????</title>
      <indexterm>
      <primary>????????????</primary>
      </indexterm> <indexterm>
      <primary>??????</primary>
      <secondary>??????</secondary>
      </indexterm>
      <para>??????????????????<command>yum</command> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>

      <para>????????? <filename>tsclient</filename> ????????????????????????</para>
<screen>
<userinput>su -c 'yum remove <replaceable>tsclient</replaceable>'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <para>?????????????????? <filename>MySQL Database</filename> ????????????????????????????????????</para>
<screen>
<userinput>su -c 'yum groupremove "<replaceable>MySQL Database</replaceable>"'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <note>
        <title>????????????????????????????????????</title>

        <para>??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
      </note>
    </section>
  </section>

  <section id="sn-searching-packages">
    <title>?????? <command>yum</command> ????????????</title>
    <indexterm>
    <primary>?????????</primary>
    <secondary>??????</secondary>
    </indexterm> <indexterm>
    <primary>??????</primary>
    <secondary>?????????</secondary>
    </indexterm>
    <para>?????? <command>yum</command> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>

    <para>???????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>

    <section id="sn-searching-packages-byname">
      <title>??????????????????????????????</title>

      <para>?????????????????????????????? <option>list</option> ???????????????????????? <filename>tsclient</filename>??????????????????</para>
<screen>
<userinput>su -c 'yum list <replaceable>tsclient</replaceable>'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <para>??????????????????????????????????????????????????????????????????????????????????????????????????? <filename>tsclient</filename> ??? 0.132 ?????????????????????</para>
<screen>
<userinput>su -c 'yum list <replaceable>tsclient-0.132</replaceable>'</userinput>
</screen>
      <note>
        <title>?????????????????????</title>

        <para>?????? <xref linkend="sn-package-names"/>????????????????????????????????????????????????????????????????????????</para>
      </note>
    </section>

    <section id="sn-searching-packages-advanced">
      <title>????????????</title>

      <para>?????????????????????????????????????????? <option>search</option> ??? <option>provides</option> ????????????????????????????????? <command>yum</command> ???????????????????????????????????????????????????????????????????????????</para>

      <para><option>search</option> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? PalmPilots ???????????????????????????</para>
<screen>
<userinput>su -c 'yum search <replaceable>PalmPilot</replaceable>'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <para><option>provides</option> ???????????????????????????????????????????????????????????????????????? <option>search</option> ??????????????????????????? <command>yum</command> ?????????????????????????????????????????????</para>

      <para>??????????????????????????? <filename>libneon</filename> ????????????????????????</para>
<screen>
<userinput>su -c 'yum provides <replaceable>libneon</replaceable>'</userinput>
</screen>
      <para>???????????????????????? MTA (Mail Transport Agent, ??????????????????) ?????????????????????????????? <filename>mta</filename> ???????????????</para>
<screen>
<userinput>su -c 'yum provides <replaceable>MTA</replaceable>'</userinput>
</screen>
      <para>??????????????????????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <para>???????????????????????????????????????????????????????????????<option>?</option> ???????????????????????????<option>*</option> ?????? 0 ????????????????????????????????????????????????????????? (<option>\</option>)???</para>

      <para>??? <option>list</option> ??????????????? <filename>tsc</filename> ???????????????????????????</para>
<screen>
<userinput>su -c 'yum list <replaceable>tsc\*</replaceable>'</userinput>
</screen>
      <tip>
        <title>???????????????</title>
        <para>?????? Perl ??? Python ?????????????????????????????????????????????</para>
      </tip>
    </section>

    <section id="sn-package-matches">
      <title>????????????</title>

      <para>?????? <command>yum</command> ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>

      <para>??????????????? <filename>shadowutils</filename> ??? <filename>shadow-util</filename> ????????????????????? <filename>shadow-utils</filename> ?????????????????????????????? <filename>shadow-util\?</filename> ??? <filename>shadow\*</filename>??????????????????????????????????????????????????????</para>
    </section>
  </section>

  <section id="sn-updating-your-system">
    <title>?????? <command>yum</command> ??????????????????</title>
    <indexterm>
    <primary>??????</primary>
    <secondary>????????????</secondary>
    </indexterm> <indexterm>
    <primary>yum</primary>
    <secondary>??????????????????</secondary>
    </indexterm>
    <para>?????? <option>update</option> ????????????????????? &FED; ?????????????????????????????????????????????????????????</para>

    <para>????????????????????????????????????????????????</para>
<screen>
<userinput>su -c 'yum update'</userinput>
</screen>
    <para>????????????????????? <systemitem class="username">root</systemitem> ????????????</para>

    <section id="sn-automatic-updating">
      <title>????????????????????????</title>
      <indexterm>
      <primary>????????????</primary>
      </indexterm>
      <para>&FC; ?????? <filename>yum</filename> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
<screen>
<userinput>su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <note>
        <title>??????????????????????????????</title>

        <para>??????????????????????????? <command>yum</command> ?????????????????????????????????????????? <filename>/etc/rc.d/init.d/yum</filename>?????????????????????????????? <filename>/etc/cron.daily/yum.cron</filename>?????????????????? <command>cron</command> ???????????????????????????????????????????????????????????????</para>
      </note>
    </section>
  </section>

  <section id="sn-using-repositories">
    <title>????????????????????????</title>
    <indexterm>
    <primary>&FEX;</primary>
    </indexterm> <indexterm>
    <primary>??????</primary>
    <secondary>??????</secondary>
    </indexterm> <indexterm>
    <primary>??????</primary>
    <secondary>??????</secondary>
    </indexterm>
    <para>&FED; ?????????????????? &FP; ???????????????????????? &FEX;???????????????????????? &FC; ??????????????????</para>

    <note>
      <title>??????????????? &FC; ??? &FEX; ??????</title>

      <para>????????????????????? &FED; 3 ???????????? &FEX;????????? <ulink url="http://fedora.redhat.com/projects/extras/"/> ????????????????????? &FED; 1 ??? &FED; 2 ?????????????????????????????? <ulink url="http://www.fedora.us/"/>???</para>
    </note>

    <para>?????? &FP; ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FED; ???????????????????????????<ulink url="http://www.jpackage.org/"/> ???????????? Java ?????????????????????</para>

    <section id="sn-adding-repositories">
      <title>??????????????????????????????</title>
      <indexterm>
      <primary>??????</primary>
      <secondary>??????</secondary>
      </indexterm>
      <para>?????????????????????????????????????????????????????? <filename>/etc/yum.repos.d/</filename> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
      <tip>
        <title>?????????????????????</title>
        <para>?????????????????????????????? <filename>.repo</filename> ?????????</para>
      </tip>
      <para>???????????? <systemitem class="username">root</systemitem> ??????????????????????????????????????????????????????????????? <filename>example.repo</filename>??????????????????</para>
<screen>
<userinput>su -c 'cp example.repo /etc/yum.repos.d/'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <para>????????????????????????????????????????????? <command>gpgkey</command> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <xref linkend="sn-authorizing-package-sources"/>???</para>

      <note>
        <title>????????? <application>up2date</application> ??????</title>

        <para>??? &FED; 4 ?????????<command>yum</command> ????????????????????? <application>up2date</application> ???????????? &FED; 3 ??????????????????????????????????????????????????? <application>up2date</application> ??????????????????????????????????????????????????? <filename>/etc/sysconfig/rhn/sources</filename>???</para>
      </note>
    </section>

    <section id="sn-authorizing-package-sources">
      <title>????????????????????????</title>
      <indexterm>
      <primary>??????</primary>
      <secondary>??????</secondary>
      </indexterm>
      <para>???????????? <command>rpm</command> ????????????????????????????????? <command>rpm</command> ??? <option>import</option> ???????????????????????? <filename>GPG-PUB-KEY.asc</filename>??????????????????</para>
<screen>
<userinput>su -c 'rpm --import <replaceable>GPG-PUB-KEY.asc</replaceable>'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <para>???????????????????????????????????????????????????????????????????????? <wordasword>www.therepository.com</wordasword> ???????????? <filename>GPG-PUB-KEY.asc</filename>??????????????????</para>
<screen>
<userinput>su -c 'rpm --import <replaceable>http://www.therepository.com/GPG-PUB-KEY.asc</replaceable>'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ????????????</para>

      <important>
        <title>??? &FED; 3 ????????? &FED; ??????</title>

        <para>?????? &FED; 3 ???????????? <command>rpm</command> ??????????????? &FED; ???????????????????????? <command>su -c 'rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora'</command>???</para>
      </important>
    </section>

    <section id="sn-compat-repositories">
      <title>?????????????????????</title>
      <indexterm>
      <primary>?????????</primary>
      <secondary>???????????????</secondary>
      </indexterm> <indexterm>
      <primary>??????</primary>
      <secondary>?????????</secondary>
      </indexterm>
      <para>&FEX; ???????????????????????? &FC; ???????????????????????????????????????????????????????????? &FP; ?????????????????????????????????????????????????????????????????????</para>

      <para>????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? &FED; ????????????????????????????????????</para>

      <para>????????????????????????????????????????????????????????? &FP; ????????????????????????????????? &FP; ??????????????????????????????????????????????????????????????????????????????????????????</para>

      <caution>
        <title>??????????????????</title>

        <para>?????????????????????????????????????????????????????????<command>yum</command> ??????????????????</para>
      </caution>

      <para>?????????????????? &FED; ????????????????????????????????????????????? &FED; ?????????????????????????????????????????????????????????????????? &FED; ?????????</para>
      <tip>
        <title>???????????? <command>yum</command> ??????????????????</title>
        <para>??? <command>yum</command> 2.1 ???????????????????????????????????????????????????????????? &FED; 3 ??????????????????????????????????????????????????????????????? &FED; ??????????????????????????????????????????????????????????????? <command>yum</command> ????????????????????????????????????????????? <filename>repodata/</filename> ???????????????</para>
      </tip>
    </section>
  </section>

  <section id="sn-yum-installing-frompackage">
    <title>?????????????????????????????????????????????</title>
    <indexterm>
    <primary>????????????</primary>
    <secondary>????????????</secondary>
    <see>????????????????????????</see>
    </indexterm> <indexterm>
    <primary>??????</primary>
    <secondary>????????????????????????</secondary>
    </indexterm>
    <para>???????????????????????? <command>yum</command> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????? <option>localinstall</option> ???????????????????????????????????????</para>

    <important>
      <title>???????????????</title>

      <para>?????????????????????????????????????????????????????????????????????????????????????????? <xref linkend="sn-authorizing-package-sources"/>???</para>
    </important>

    <para>?????????????????? <filename>tsclient-0.132-4.i386.rpm</filename>??????????????????</para>
<screen>
<userinput>su -c 'yum localinstall <replaceable>tsclient-0.132-4.i386.rpm</replaceable>'</userinput>
</screen>
    <para>????????????????????? <systemitem class="username">root</systemitem> ????????????</para>

    <note>
      <title>?????????????????????????????????</title>

      <para>???????????????????????????????????????????????????<command>yum</command> ??????????????????????????????</para>
    </note>

    <para>???????????????????????????????????????????????????<command>yum</command> ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>

    <caution>
      <title>??????????????????????????????</title>

      <para>?????????????????????????????????????????????????????????????????????<command>yum update</command> ??????????????????????????????????????????????????????????????????????????????????????????????????? RSS ???????????????????????????????????????????????????</para>
    </caution>
  </section>

  <section id="sn-yum-maintenance">
    <title>?????? <command>yum</command></title>

    <para><command>yum</command> ?????????????????????????????????????????? <command>yum</command> ?????????????????????????????????????????????????????????????????????????????????????????? <command>yum</command> ????????????????????????????????????????????????</para>

    <section id="sn-removing-sources">
      <title>???????????????????????????</title>
      <indexterm>
      <primary>??????</primary>
      <secondary>??????</secondary>
      </indexterm> <indexterm>
      <primary>??????</primary>
      <secondary>??????</secondary>
      </indexterm>
      <para>????????????????????????????????? <command>enable=0</command> ???????????? <command>yum</command> ?????????????????????<command>yum</command> ????????????????????????????????????????????????</para>

      <para>???????????????????????????</para>
      <procedure>
        <step>
          <para>??? <filename>/etc/yum.repos.d/</filename> ?????????????????????????????????</para>
        </step>
        <step>
          <para>??? <filename>/var/cache/yum/</filename> ???????????????????????????????????????</para>
        </step>
      </procedure>
<!-- What with the "web of trust," removing GPG keys is not really -->
<!-- something we should encourage. Having an extra GPG key in the RPM -->
<!-- database is not a vulnerability, nor does it hamper the system in -->
<!-- any way.  These are probably a couple of reasons Seth didn't build -->
<!-- this function into yum as part of "clean all," for example.  Since -->
<!-- we just had several admonitions against people running the rpm -->
<!-- command on its own anyway, I would just omit this part -->
<!-- completely. [PWF] -->
<!--

      <important>
        <title>Remove Unneeded Public Keys</title>

        <para>
          If you will not be using any further packages from a provider,
	  remove their public key from the <command>rpm</command>
	  keyring using the procedure described in
          <xref linkend="sn-removing-publickeys" />.
        </para>
      </important>
    </section>

    <section id="sn-removing-publickeys">
      <title>Removing Public Keys</title>
      <indexterm>
        <primary>public keys, removing</primary>
      </indexterm>
      <para>
        To remove a public key from the keyring you first must determine
        the full name of the key, as it registered in
        <command>rpm</command>. Run this command to view the details of
        the public keys on the <command>rpm</command> keyring:
      </para>
<screen>
<userinput>rpm -qi gpg-pubkey-*</userinput>
</screen>
      <para>
        Locate the heading for the relevant public key. The public key
        headings follow this format:
      </para>

      <example id="publickey-header-format">
        <title>Format of <command>rpm</command> Public Key Headers</title>
<screen>
<computeroutput>Name        : gpg-pubkey                   Relocations: (not relocatable)
Version     : 4f2a6fd2                          Vendor: (none)
Release     : 3f9d9d3b                      Build Date: Wed 15 Jun 2005 09:55:33 PM BST
Install Date: Wed 15 Jun 2005 09:55:33 PM BST      Build Host: localhost
Group       : Public Keys                   Source RPM: (none)
Size        : 0                                License: pubkey
Signature   : (none)
Summary     : gpg(Fedora Project &lt;fedora at redhat.com&gt;)
Description :</computeroutput>
</screen>
      </example>

      <para>
        Add the <option>Version</option> and <option>Release</option>
        attributes to <option>gpg-pubkey-</option> to make the complete
        name of the key, in the form
        <option>gpg-pubkey-Version_number-Release_number</option>. The
        <command>rpm</command> identification for the &FP; public key
        shown above is: <option>gpg-pubkey-4f2a6fd2-3f9d9d3b</option>.
      </para>

      <para>
        Once you know the identification name of the key, use the
        command <command>rpm <option>-e</option></command> to remove it.
        To remove the &FP; public key shown above the exact command
        would be:
      </para>
<screen>
<userinput>su -c 'rpm -e <replaceable>gpg-pubkey-4f2a6fd2-3f9d9d3b</replaceable>'</userinput>
</screen>
      <para>
        Enter the password for the
        <systemitem class="username">root</systemitem> account when
        prompted.
      </para>

-->
    </section>

    <section id="sn-yum-clearance">
      <title>?????? <command>yum</command> ??????</title>
      <indexterm>
      <primary>yum</primary>
      <secondary>????????????</secondary>
      </indexterm>
      <para>??????????????????<command>yum</command> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
<screen>
<userinput>su -c 'yum clean headers'</userinput>
</screen>
      <para>???????????????????????????????????????????????????</para>
<screen>
<userinput>su -c 'yum clean packages'</userinput>
</screen>
      <para>????????????????????? <systemitem class="username">root</systemitem> ??????????????????</para>

      <para>????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????</para>
    </section>
  </section>

  <section id="sn-yum-proxy-server">
    <title>??????????????????????????? <command>yum</command></title>
    <indexterm>
    <primary>???????????????</primary>
    </indexterm> <indexterm>
    <primary>yum</primary>
    <secondary>??????????????????????????????</secondary>
    </indexterm>
    <para>??????????????????<command>yum</command> ?????? HTTP ???????????????????????????????????? <command>yum</command> HTTP ??????????????? HTTP/1.1??????????????????????????? web ????????????????????????????????????????????? FTP ?????????????????? <command>yum</command> ?????? FTP ??????????????????<filename>squid</filename> ???????????????????????? HTTP/1.1 ??? FTP ????????????????????????</para>
    <tip>
      <title>???????????????????????? <command>yum</command></title>
      <para>????????? <filename>yum.conf</filename> ?????????????????????????????? HTTP ??????????????????????????? web ??????????????????????????????????????? <command>yum</command> ?????? FTP ???????????????????????? FTP ?????????&FED; ?????????????????? HTTP ??? FTP???</para>
    </tip>
    <section id="sn-yum-proxy-server-global">
      <title>???????????????????????????</title>

      <para>??????????????? <command>yum</command> ?????????????????????????????????????????? <filename>/etc/yum.conf</filename> ????????????????????????????????????<option>proxy</option> ??????????????????????????????????????????????????? URL????????? TCP ????????????????????????????????????????????????????????????????????????????????? <option>proxy_username</option> ??? <option>proxy_password</option> ???????????????????????????</para>

      <para>?????????????????? <command>yum</command> ????????????????????? <systemitem class="systemname">mycache.mydomain.com</systemitem>?????????????????? 3128???????????? <systemitem class="username">yum-user</systemitem>????????? <systemitem>qwerty</systemitem>???</para>

      <example id="config-file-httpproxy">
        <title>?????????????????????????????????????????????</title>
<screen>
<computeroutput># ??????????????? - proxy server:port number
proxy=http://mycache.mydomain.com:3128
# ?????? yum ?????????????????????
proxy_username=yum-user
proxy_password=qwerty</computeroutput>
</screen>
      </example>

      <note>
        <title>????????????</title>

        <para>???????????? <filename>/etc/yum.conf</filename> ???????????????????????????<emphasis>??????</emphasis> ??????????????? <command>yum</command> ?????????????????????????????????????????????</para>
      </note>
    </section>

    <section id="sn-yum-proxy-server-peruser">
      <title>????????????????????????????????????</title>

      <para>?????????????????????????????????????????????????????????????????????????????????????????????????????? shell ??????????????????????????? <command>bash</command> shell??????????????? <filename>~/.bash_profile</filename> ???????????????????????? <command>yum</command> ????????????????????? <systemitem class="systemname">mycache.mydomain.com</systemitem>?????????????????? 3128???</para>

      <example id="profile-script-httpproxy">
        <title>???????????????????????????????????????</title>
<screen>
<computeroutput># ????????????????????????????????????
http_proxy="http://mycache.mydomain.com:3128"
export http_proxy</computeroutput>
</screen>
      </example>

      <para>????????????????????????????????????????????????????????????????????? URL????????????????????? <systemitem class="username">yum-user</systemitem>????????? <systemitem>qwerty</systemitem>??????????????????</para>

      <example id="profile-script-httpproxy-withpassword">
        <title>?????????????????????????????????????????????</title>
<screen>
<computeroutput># ????????????????????????????????????????????????/??????
http_proxy="http://yum-user:qwerty at mycache.mydomain.com:3128"
export http_proxy</computeroutput>
</screen>
      </example>

      <note>
        <title>???????????? <option>http_proxy</option></title>

        <para>???????????? <command>http_proxy</command> ?????? <command>curl</command> ?????????????????????????????? <command>yum</command> ?????????????????????????????? <command>http_proxy</command>???<command>curl</command> ???????????????????????????????????????</para>
      </note>
    </section>
  </section>

<!-- SE: This is at the end of the document, since it looks out of place in section 1 -->

  <section id="sn-acknowledgements">
    <title>??????</title>

    <para>Paul Frields ?????????????????????Timothy Murphy ????????? BETA ?????????</para>
  </section>

  <index id="generated-index"/>
</article>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->


Index: Makefile
===================================================================
RCS file: /cvs/docs/yum-software-management/Makefile,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- Makefile	18 Sep 2005 22:44:53 -0000	1.5
+++ Makefile	15 Nov 2005 14:42:32 -0000	1.6
@@ -8,7 +8,7 @@
 # Copyright 2005 Tommy Reynolds, MegaCoder.com
 ###############################################################################
 
-LANGUAGES       	= en
+LANGUAGES       	= en zh_CN
 DOCBASE        		= yum-software-management
 XMLEXTRAFILES-en	=
 



From fedora-docs-commits at redhat.com  Tue Nov 15 22:32:39 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 15 Nov 2005 17:32:39 -0500
Subject: docs-common/bin active,NONE,1.1
Message-ID: <200511152232.jAFMWdt9026954@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26924/bin

Added Files:
	active 
Log Message:
This file will track folders for docs that should be built in any bulk action for DocsRawhide.



--- NEW FILE active ---
documentation-guide
stateless-linux
selinux-faq
install-guide
release-notes
developer-guide
mirror-tutorial
jargon-buster
rpm-guide
yum-software-management
translation-guide-windows
selinux-apache
translation-guide



From fedora-docs-commits at redhat.com  Tue Nov 15 23:10:53 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 15 Nov 2005 18:10:53 -0500
Subject: docs-common Makefile.common,1.12,1.13
Message-ID: <200511152310.jAFNArsQ028646@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28596

Modified Files:
	Makefile.common 
Log Message:
Added one new target, "showvars".  The new target is used to grab variables from inside the document-specific makefiles for use in external bash scripts.  Additional variables can be added to the list.



Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- Makefile.common	30 Oct 2005 19:15:40 -0000	1.12
+++ Makefile.common	15 Nov 2005 23:10:46 -0000	1.13
@@ -51,7 +51,7 @@
 # PUT NO TARGETS BEFORE THIS ONE, not even in your base Makefile
 # In a properly-constructed Makefile, this will be the default target
 
-TARGETS=all tarball pdf html html-nochunks clean distclean
+TARGETS=all tarball pdf html html-nochunks clean distclean showvars
 .PHONY:	${TARGETS}
 
 all::	html html-nochunks tarball # pdf
@@ -141,6 +141,10 @@
 distclean clean:: $(foreach LANG,${LANGUAGES},${DOCBASE}-${LANG}-clean)
 
 $(foreach LANG,${LANGUAGES},$(eval $(call CLEAN_template,${LANG})))
+
+showvars::
+	@echo "DOCBASE=\"$(DOCBASE)\""
+	@echo "LANGUAGES=\"$(LANGUAGES)\""
 #
 #########################################################################
 # End of Makefile.common



From fedora-docs-commits at redhat.com  Tue Nov 15 23:20:31 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 15 Nov 2005 18:20:31 -0500
Subject: stateless-linux Makefile,1.2,1.3
Message-ID: <200511152320.jAFNKVfe028878@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/stateless-linux
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28853

Modified Files:
	Makefile 
Log Message:
Fix stateless-linux howto Makefile to new standards


Index: Makefile
===================================================================
RCS file: /cvs/docs/stateless-linux/Makefile,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Makefile	28 Jun 2005 22:33:46 -0000	1.2
+++ Makefile	15 Nov 2005 23:20:24 -0000	1.3
@@ -1,31 +1,26 @@
 ###############################################################################
 # Makefile for RHLP docs project
 # Created by: Tammy Fox <tfox at redhat.com>
-# Last edited by: Tammy Fox <tfox at redhat.com>
+# Last edited by: Tommy Reynolds <Tommy.Reynolds at MegaCoder.com>
 # WARNING: need passivetex 1.24 for pdf generation to work
 # License: GPL
 # Copyright 2003 Tammy Fox, Red Hat, Inc.
+# Copyright 2005 Tommy Reynolds, MegaCoder.com
 ###############################################################################
 
-XSLPDF         = ../docs-common/xsl/main-pdf.xsl
-XSLHTML        = ../docs-common/xsl/main-html.xsl
-LANG	       = en
-DOCNAME        = stateless-linux-HOWTO-$(LANG)
-XMLFILE        = $(DOCNAME).xml
+LANGUAGES      		= en
+DOCBASE			= stateless-linux-HOWTO
+XMLEXTRAFILES-en	=
 
 ######################################################
 include ../docs-common/Makefile.common
 ######################################################
-html: 
-	@xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
-	@mkdir -p $(DOCNAME)/stylesheet-images
-	@cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images
-	@cp ../docs-common/css/fedora.css $(DOCNAME)
 
-
-pdf:
-	@xmlto pdf -x $(XSLPDF) $(XMLFILE)
-######################################################
-
-clean: 
-	@rm -rfv *.html *.pdf *.tex $(DOCNAME) $(DOCNAME).tar.gz
+# If you want to add additional steps to any of the 
+# targets defined in "Makefile.common", be sure to use
+# a double-colon in your rule here.  For example, to 
+# print the message "FINISHED AT LAST" after building 
+# the HTML document version, uncomment the following 
+# line:
+#${DOCNAME}/index.html::
+#	echo FINISHED AT LAST



From fedora-docs-commits at redhat.com  Tue Nov 15 23:25:12 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 15 Nov 2005 18:25:12 -0500
Subject: translation-guide-windows Makefile,1.2,1.3
Message-ID: <200511152325.jAFNPCjW029042@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/translation-guide-windows
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29025

Modified Files:
	Makefile 
Log Message:
Fix Makefile to current standards


Index: Makefile
===================================================================
RCS file: /cvs/docs/translation-guide-windows/Makefile,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Makefile	28 Jun 2005 21:52:45 -0000	1.2
+++ Makefile	15 Nov 2005 23:25:05 -0000	1.3
@@ -1,32 +1,26 @@
 ###############################################################################
 # Makefile for RHLP docs project
 # Created by: Tammy Fox <tfox at redhat.com>
-# Last edited by: Sarah Wang <sarahs at redhat.com>
+# Last edited by: Tommy Reynolds <Tommy.Reynolds at MegaCoder.com>
 # WARNING: need passivetex 1.24 for pdf generation to work
 # License: GPL
 # Copyright 2003 Tammy Fox, Red Hat, Inc.
+# Copyright 2005 Tommy Reynolds, MegaCoder.com
 ###############################################################################
 
-XSLPDF         = ../docs-common/xsl/main-pdf.xsl
-XSLHTML        = ../docs-common/xsl/main-html.xsl
-LANG	       = en
-DOCNAME        = translate-in-windows-$(LANG)
-XMLFILE        = $(DOCNAME).xml
+LANGUAGES      		= en
+DOCBASE			= translate-in-windows
+XMLEXTRAFILES-en	=
 
 ######################################################
 include ../docs-common/Makefile.common
 ######################################################
-html:
-	@xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
-	@mkdir -p $(DOCNAME)/stylesheet-images
-	@cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images
-	@cp ../docs-common/css/fedora.css $(DOCNAME)
-	@cp -r figs/ $(DOCNAME)/
 
-
-pdf:
-	@xmlto pdf -x $(XSLPDF) $(XMLFILE)
-######################################################
-
-clean: 
-	@rm -rfv *.html *.pdf *.tex $(DOCNAME) $(DOCNAME).tar.gz
+# If you want to add additional steps to any of the 
+# targets defined in "Makefile.common", be sure to use
+# a double-colon in your rule here.  For example, to 
+# print the message "FINISHED AT LAST" after building 
+# the HTML document version, uncomment the following 
+# line:
+#${DOCNAME}/index.html::
+#	echo FINISHED AT LAST



From fedora-docs-commits at redhat.com  Tue Nov 15 23:26:12 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 15 Nov 2005 18:26:12 -0500
Subject: translation-guide Makefile,1.3,1.4
Message-ID: <200511152326.jAFNQCGQ029065@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/translation-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29048

Modified Files:
	Makefile 
Log Message:
Fix Makefile to current standards


Index: Makefile
===================================================================
RCS file: /cvs/docs/translation-guide/Makefile,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Makefile	28 Jun 2005 21:49:10 -0000	1.3
+++ Makefile	15 Nov 2005 23:26:03 -0000	1.4
@@ -1,31 +1,26 @@
 ###############################################################################
 # Makefile for RHLP docs project
 # Created by: Tammy Fox <tfox at redhat.com>
-# Last edited by: Sarah Wang <sarahs at redhat.com>
+# Last edited by: Tommy Reynolds <Tommy.Reynolds at MegaCoder.com>
 # WARNING: need passivetex 1.24 for pdf generation to work
 # License: GPL
 # Copyright 2003 Tammy Fox, Red Hat, Inc.
+# Copyright 2005 Tommy Reynolds, MegaCoder.com
 ###############################################################################
 
-XSLPDF         = ../docs-common/xsl/main-pdf.xsl
-XSLHTML        = ../docs-common/xsl/main-html.xsl
-LANG	       = en
-DOCNAME        = translation-guide-en
-XMLFILE        = $(DOCNAME).xml
+LANGUAGES      		= en
+DOCBASE			= translation-guide
+XMLEXTRAFILES-en	=
 
 ######################################################
 include ../docs-common/Makefile.common
 ######################################################
-html: 
-	@xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
-	@mkdir -p $(DOCNAME)/stylesheet-images
-	@cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images
-	@cp ../docs-common/css/fedora.css $(DOCNAME)
 
-
-pdf-%:
-	@xmlto pdf -x $(XSLPDF) $(XMLFILE)
-######################################################
-
-clean: 
-	@rm -rfv *.html *.pdf *.tex $(DOCNAME) $(DOCNAME).tar.gz
+# If you want to add additional steps to any of the 
+# targets defined in "Makefile.common", be sure to use
+# a double-colon in your rule here.  For example, to 
+# print the message "FINISHED AT LAST" after building 
+# the HTML document version, uncomment the following 
+# line:
+#${DOCNAME}/index.html::
+#	echo FINISHED AT LAST



From fedora-docs-commits at redhat.com  Tue Nov 15 23:31:07 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 15 Nov 2005 18:31:07 -0500
Subject: selinux-apache Makefile,1.2,1.3
Message-ID: <200511152331.jAFNV7ux029144@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/selinux-apache
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29125

Modified Files:
	Makefile 
Log Message:
Fix Makefile to current standards


Index: Makefile
===================================================================
RCS file: /cvs/docs/selinux-apache/Makefile,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Makefile	28 Jun 2005 22:14:42 -0000	1.2
+++ Makefile	15 Nov 2005 23:30:58 -0000	1.3
@@ -1,31 +1,26 @@
 ###############################################################################
 # Makefile for RHLP docs project
 # Created by: Tammy Fox <tfox at redhat.com>
-# Last edited by: Tammy Fox <tfox at redhat.com>
+# Last edited by: Tommy Reynolds <Tommy.Reynolds at MegaCoder.com>
 # WARNING: need passivetex 1.24 for pdf generation to work
 # License: GPL
 # Copyright 2003 Tammy Fox, Red Hat, Inc.
+# Copyright 2005 Tommy Reynolds, MegaCoder.com
 ###############################################################################
 
-XSLPDF         = ../docs-common/xsl/main-pdf.xsl
-XSLHTML        = ../docs-common/xsl/main-html.xsl
-LANG	       = en
-DOCNAME        = selinux-apache-$(LANG)
-XMLFILE        = $(DOCNAME).xml
+LANGUAGES      		= en
+DOCBASE			= selinux-apache
+XMLEXTRAFILES-en	=
 
 ######################################################
 include ../docs-common/Makefile.common
 ######################################################
-html: 
-	@xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
-	@mkdir -p $(DOCNAME)/stylesheet-images
-	@cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images
-	@cp ../docs-common/css/fedora.css $(DOCNAME)
 
-
-pdf:
-	@xmlto pdf -x $(XSLPDF) $(XMLFILE)
-######################################################
-
-clean: 
-	@rm -rfv *.html *.pdf *.tex $(DOCNAME) $(DOCNAME).tar.gz
+# If you want to add additional steps to any of the 
+# targets defined in "Makefile.common", be sure to use
+# a double-colon in your rule here.  For example, to 
+# print the message "FINISHED AT LAST" after building 
+# the HTML document version, uncomment the following 
+# line:
+#${DOCNAME}/index.html::
+#	echo FINISHED AT LAST



From fedora-docs-commits at redhat.com  Wed Nov 16 01:58:22 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 15 Nov 2005 20:58:22 -0500
Subject: release-notes Makefile,1.6,1.7
Message-ID: <200511160158.jAG1wMNj032694@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32677/release-notes

Modified Files:
	Makefile 
Log Message:
Updated LANGUAGES to cover new translations


Index: Makefile
===================================================================
RCS file: /cvs/docs/release-notes/Makefile,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- Makefile	3 Nov 2005 15:22:14 -0000	1.6
+++ Makefile	16 Nov 2005 01:58:14 -0000	1.7
@@ -10,7 +10,7 @@
 #
 # Document-specific definitions.
 #
-LANGUAGES      	= en
+LANGUAGES      	= en it ja_JP ru zh_CN
 DOCBASE        	= RELEASE-NOTES
 
 define XMLEXTRAFILES_template



From fedora-docs-commits at redhat.com  Wed Nov 16 01:59:12 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 15 Nov 2005 20:59:12 -0500
Subject: selinux-faq Makefile,1.3,1.4
Message-ID: <200511160159.jAG1xCxQ032722@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/selinux-faq
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32705

Modified Files:
	Makefile 
Log Message:
Fix Makefile to current standards


Index: Makefile
===================================================================
RCS file: /cvs/docs/selinux-faq/Makefile,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Makefile	29 Jun 2005 14:51:37 -0000	1.3
+++ Makefile	16 Nov 2005 01:59:05 -0000	1.4
@@ -1,19 +1,26 @@
 ###############################################################################
 # Makefile for RHLP docs project
 # Created by: Tammy Fox <tfox at redhat.com>
-# Last edited by: Tammy Fox <tfox at redhat.com>
+# Last edited by: Tommy Reynolds <Tommy.Reynolds at MegaCoder.com>
 # WARNING: need passivetex 1.24 for pdf generation to work
 # License: GPL
 # Copyright 2003 Tammy Fox, Red Hat, Inc.
+# Copyright 2005 Tommy Reynolds, MegaCoder.com
 ###############################################################################
-# test commit
-XSLPDF         = ../docs-common/xsl/main-pdf.xsl
-XSLHTML        = ../docs-common/xsl/main-html.xsl
-XSLHTMLNOCHUNKS= ../docs-common/xsl/main-html-nochunks.xsl
-LANG	       = en
-DOCNAME        = selinux-faq-$(LANG)
-XMLFILE        = $(DOCNAME).xml
+
+LANGUAGES      		= en
+DOCBASE			= selinux-faq
+XMLEXTRAFILES-en	=
 
 ######################################################
 include ../docs-common/Makefile.common
 ######################################################
+
+# If you want to add additional steps to any of the 
+# targets defined in "Makefile.common", be sure to use
+# a double-colon in your rule here.  For example, to 
+# print the message "FINISHED AT LAST" after building 
+# the HTML document version, uncomment the following 
+# line:
+#${DOCNAME}/index.html::
+#	echo FINISHED AT LAST



From fedora-docs-commits at redhat.com  Wed Nov 16 02:00:20 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 15 Nov 2005 21:00:20 -0500
Subject: docs-common/bin bulkbuild,NONE,1.1
Message-ID: <200511160200.jAG20Ku9032762@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32746

Added Files:
	bulkbuild 
Log Message:
bulkbuild


--- NEW FILE bulkbuild ---
#!/bin/bash
#
# Pull all active FDP docs from CVS, build and install HTML in
# folder $HOME/fdpdocs-html
#

NOW="$(date +%Y%m%d%H%M%S)"
FDPDIR="${HOME}/fdpdocs-cvs${NOW}"
HTMLDIR="${HOME}/fdpdocs-html"
# Do this anonymously for now
ANONCVS=":pserver:anonymous at cvs.fedora.redhat.com:2401/cvs/docs"

mkdir "${FDPDIR}" || ( echo "Could not mkdir ${FDPDIR}" ; exit 254 )
mkdir "${HTMLDIR}" || ( echo "Could not mkdir ${FDPDIR}" ; exit 254 )
pushd "${FDPDIR}" >/dev/null || ( echo "Could not pushd ${FDPDIR}" ; exit 253 )

cvs -d $ANONCVS login
cvs -qz3 -d $ANONCVS co docs-common

for DOC in `cat docs-common/bin/active`; do
    cvs -qz3 -d $ANONCVS co $DOC
    pushd "$DOC" >/dev/null || (echo "Couldn't cd to $DOCDIR" ; exit 252 )
    make showvars > tmpvars
    . tmpvars
    rm -f tmpvars
    make html
    for LANG in $LANGUAGES ; do
	DESTDIR="${HTMLDIR}/${DOCBASE}/${LANG}"
	mkdir -p "${DESTDIR}"
	cp -a "${DOCBASE}-${LANG}"/* "${DESTDIR}"
    done
    popd >/dev/null
done
    

popd >/dev/null
echo -n "OK to remove temp dir ${FDPDIR} [y/n]? "
read -sn1 REPLY
case $REPLY in
    y|Y )
	rm -rf "${FDPDIR}"
	echo
	;;
    * )
	echo "... not removed."
	;;
esac



From fedora-docs-commits at redhat.com  Wed Nov 16 02:02:41 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 15 Nov 2005 21:02:41 -0500
Subject: docs-common/bin bulkbuild,1.1,1.2
Message-ID: <200511160202.jAG22fOH001817@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1803

Modified Files:
	bulkbuild 
Log Message:
Should have put a message in the initial checkin, but the comment below says what I would have, had I remebered.


Index: bulkbuild
===================================================================
RCS file: /cvs/docs/docs-common/bin/bulkbuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- bulkbuild	16 Nov 2005 02:00:13 -0000	1.1
+++ bulkbuild	16 Nov 2005 02:02:10 -0000	1.2
@@ -1,7 +1,12 @@
 #!/bin/bash
 #
 # Pull all active FDP docs from CVS, build and install HTML in
-# folder $HOME/fdpdocs-html
+# folder $HOME/fdpdocs-html.
+#
+# This script is not designed to be run inside a local CVS repository;
+# it is only stored here for convenience and upkeep.  It may be used
+# in DocsRawhide as part of a build system of some sort.  On the other
+# hand, it may be vaporized.
 #
 
 NOW="$(date +%Y%m%d%H%M%S)"



From fedora-docs-commits at redhat.com  Thu Nov 17 12:44:03 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 17 Nov 2005 07:44:03 -0500
Subject: mirror-tutorial mirror-tutorial-en.xml,1.18,1.19
Message-ID: <200511171244.jAHCi3dr006445@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6428

Modified Files:
	mirror-tutorial-en.xml 
Log Message:
Fixed createrepo and yum-arch command issues (#172819)



Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- mirror-tutorial-en.xml	15 Nov 2005 14:28:05 -0000	1.18
+++ mirror-tutorial-en.xml	17 Nov 2005 12:43:56 -0000	1.19
@@ -6,8 +6,8 @@
 %FEDORA-ENTITIES-EN;
 
 <!ENTITY BOOKNAME "mirror-tutorial">
-<!ENTITY BOOKVERSION "0.36">
-<!ENTITY BOOKDATE "2005-11-11">
+<!ENTITY BOOKVERSION "0.37">
+<!ENTITY BOOKDATE "2005-11-17">
 <!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)"> <!-- change version of manual and date here -->
 
 <!ENTITY BUG-NUM "130125">
@@ -203,6 +203,16 @@
 	  </para>
 	</revdescription>
       </revision>
+      <revision>
+	<revnumber>0.37</revnumber>
+	<date>2005-11-17</date>
+	<authorinitials>PaulWFrields</authorinitials>
+	<revdescription>
+	  <para>
+	    Fixed createrepo and yum-arch command issues (#172819).
+	  </para>
+	</revdescription>
+      </revision>
     </revhistory>
   </articleinfo>
 
@@ -1263,27 +1273,31 @@
       <section id="sn-yum-arch">
 	<title><command>yum-arch</command></title>
 	<para>
-	  A directory which supports older versions of
-	  <command>yum</command> (before 2.2) is named
-	  <filename>headers</filename>. It is created by using the
-	  command <command>yum-arch</command>, which is run against the
-	  directory <emphasis>under which</emphasis> you want the
-	  <filename>headers</filename> directory to appear. The
+	  The <command>yum-arch</command> command creates a directory
+	  named <filename>headers/</filename> which supports older
+	  versions of <command>yum</command> (before 2.2). The
 	  <command>yum-arch</command> program searches recursively
-	  through that directory and any subdirectories for RPM
-	  packages, and includes them in the header data.
+	  through a target directory and any subdirectories for RPM
+	  packages, and includes them in the header data.  The
+	  <command>yum-arch</command> command always creates the
+	  <filename>headers/</filename> directory in the current working
+	  directory.  Therefore you should change your working directory
+	  to the directory where you want <filename>headers/</filename>
+	  to appear.
 	</para>
 
 <screen>
-<userinput>su -c 'yum-arch -l -s /var/www/mirror/fedora/linux/core/&FCVER;/i386/os'</userinput>
+<userinput>cd /var/www/mirror/fedora/linux/core/&FCVER;/i386/os
+su -c 'yum-arch -ls .'</userinput>
 </screen>
 
 	<para>
-	  The <command>-l</command> switch follows symbolic links. The
+	  Enter the root password at the prompt.  The
+	  <command>-l</command> switch follows symbolic links. The
 	  <command>-s</command> switch includes SRPMS (source RPM
 	  packages) in the header list. The command above creates the
 	  <command>yum</command> header cache in the directory
-	  <filename>/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/headers</filename>.
+	  <filename>/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/headers/</filename>.
 	</para>
       </section>
 



From fedora-docs-commits at redhat.com  Fri Nov 18 15:14:46 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 18 Nov 2005 10:14:46 -0500
Subject: sudo-tutorial Makefile,1.1.1.1,1.2 sudo-tutorial-en.xml,1.2,1.3
Message-ID: <200511181514.jAIFEk65024650@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/sudo-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24631

Modified Files:
	Makefile sudo-tutorial-en.xml 
Log Message:
Updated to new docs-common/ build setup.



Index: Makefile
===================================================================
RCS file: /cvs/docs/sudo-tutorial/Makefile,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- Makefile	11 May 2005 16:50:26 -0000	1.1.1.1
+++ Makefile	18 Nov 2005 15:14:38 -0000	1.2
@@ -1,29 +1,22 @@
 ###############################################################################
-# Makefile for RHLP docs project
-# Created by: Tammy Fox <tfox at redhat.com>
-# Last edited by: Tammy Fox <tfox at redhat.com>
-# WARNING: need Apache FOP >= 0.20.5  for pdf generation to work
-# License: GPL
-# Copyright 2005 Tommy Reynolds <Tommy.Reynolds at MegaCoder.com>
-###############################################################################
-
-XSLPDF         = ../xsl/main-pdf.xsl
-XSLHTML        = ../xsl/main-html.xsl
-LANG	       = en
-DOCNAME        = sudo-tutorial-$(LANG)
-XMLFILE        = $(DOCNAME).xml
-
+#
+# Document-specific definitions.
+#
+LANGUAGES      	= en
+DOCBASE        	= sudo-tutorial
+#
+XMLEXTRAFILES-en=
+#
 ######################################################
-html: 
-	xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
-	mkdir -p $(DOCNAME)/stylesheet-images
-	cp ../stylesheet-images/*.png $(DOCNAME)/stylesheet-images
-	cp ../css/fedora.css $(DOCNAME)
-
-
-awt pdf:
-	xmlto $@ -x $(XSLPDF) $(XMLFILE)
+include ../docs-common/Makefile.common
+######################################################
+#
+# If you want to add additional steps to any of the 
+# targets defined in "Makefile.common", be sure to use
+# a double-colon in your rule here.  For example, to 
+# print the message "FINISHED AT LAST" after building 
+# the HTML document version, uncomment the following 
+# line:
+#${DOCBASE}-en/index.html::
+#	echo FINISHED AT LAST
 ######################################################
-
-clean: 
-	${RM} -rfv *.html *.pdf *.tex $(DOCNAME)


Index: sudo-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/sudo-tutorial/sudo-tutorial-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- sudo-tutorial-en.xml	9 Jun 2005 16:06:26 -0000	1.2
+++ sudo-tutorial-en.xml	18 Nov 2005 15:14:38 -0000	1.3
@@ -3,7 +3,7 @@
 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
 
-<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../common/fedora-entities-en.xml">
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
 %FEDORA-ENTITIES-EN;
 
 <!ENTITY BOOKID "sudo-tutorial-0.1 (2005-04-03)"> <!-- change version of manual and date here -->



From fedora-docs-commits at redhat.com  Sat Nov 19 03:22:24 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 18 Nov 2005 22:22:24 -0500
Subject: docs-common/man/man1 tidy-bowl.1,1.1,1.2
Message-ID: <200511190322.jAJ3MO2N014904@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/man/man1
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14887

Modified Files:
	tidy-bowl.1 
Log Message:
Added i18n notes about tidy-bowl refusing to prettyprint a locale until
it has been expressly permitted to do so.



Index: tidy-bowl.1
===================================================================
RCS file: /cvs/docs/docs-common/man/man1/tidy-bowl.1,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- tidy-bowl.1	17 Aug 2005 07:58:02 -0000	1.1
+++ tidy-bowl.1	19 Nov 2005 03:22:16 -0000	1.2
@@ -1,4 +1,4 @@
-.TH TIDY-BOWL 1 "2005-08-17" "GPL" "megacoder"
+.TH TIDY-BOWL 1 "2005-11-18" "GPL" "megacoder"
 .SH NAME
 tidy-bowl \- xml pretty printer
 .SH SYNOPSIS
@@ -113,6 +113,16 @@
 .BR tidy-bowl( 1 )
 is not true filter.
 The file name suffix must be ".xml", in any case combination.
+.SH INTERNATIONALIZATION CONCERNS
+.LP
+At this time,
+.BR tidy-bowl( 1 )
+only understands Romance languages such as English, German, and Italian.
+It will probably do horrible things to non-latin1 languages such as Mongolian.
+.BR Tidy-bowl( 1 )
+checks the locale encoded in each 
+.B XML
+filename and skips any questionable files.
 .SH SEE ALSO
 .BR xmlformat( 1 ),
 .SH AUTHOR



From fedora-docs-commits at redhat.com  Sat Nov 19 07:19:49 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 02:19:49 -0500
Subject: release-notes RELEASE-NOTES-master-it.xml,1.1,NONE
Message-ID: <200511190719.jAJ7Jngl021567@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21552/release-notes

Removed Files:
	RELEASE-NOTES-master-it.xml 
Log Message:



--- RELEASE-NOTES-master-it.xml DELETED ---



From fedora-docs-commits at redhat.com  Sat Nov 19 09:42:53 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 04:42:53 -0500
Subject: selinux-faq selinux-faq-it.xml,NONE,1.1
Message-ID: <200511190942.jAJ9grf6025546@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/selinux-faq
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25530/selinux-faq

Added Files:
	selinux-faq-it.xml 
Log Message:



--- NEW FILE selinux-faq-it.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

<!-- *************** Bring in Fedora entities *************** -->
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;

<!ENTITY BOOKID "selinux-faq-1.3-8 (2005-01-20-T16:20-0800)"> <!-- version of manual and date -->

<!-- ************** local entities *********** -->
<!ENTITY APACHE "Apache HTTP">
<!ENTITY LOCALVER "3">  <!-- Set value to your choice, when guide version is out -->
<!-- of sync with FC release, use instead of FEDVER or FEDTESTVER  -->
<!ENTITY BUG-URL
"https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&percnt;20Core&amp;op_sys=Linux&amp;version=fc3&amp;component=fedora-docs&amp;component_text=&amp;rep_platform=All&amp;priority=normal&amp;bug_severity=normal&amp;bug_status=NEW&amp;assigned_to=kwade&percnt;40redhat.com&amp;cc=&amp;estimated_time=0.0&amp;bug_file_loc=http&percnt;3A&percnt;2F&percnt;2Ffedora.redhat.com&percnt;2Fdocs&percnt;2Fselinux-faq-fc3&percnt;2F&amp;short_desc=SELinux&percnt;20FAQ&percnt;20-&percnt;20&percnt;5Bsummarize&percnt;20FAQ&percnt;20change&percnt;20or&percnt;20addition&percnt;5D&amp;comment=Description&percnt;20of&percnt;20change&percnt;2FFAQ&percnt;20addition.&percnt;20&percnt;20If&percnt;20a&percnt;20change&percnt;2C&percnt;20include&percnt;20the&percnt;20original&percnt;0D&percnt;0Atext&percnt;20first&percnt;2C&percnt;20then&percnt;20the&percnt;20changed&percnt;20text&percnt;3A&percnt;0D&percnt;0A&percnt;0D&percnt;0A&percnt;0D&percnt;0A&percnt;0D&percnt;0AVersion-Release&percnt!
 ;20of&percnt;20FAQ&percnt;20&percnt;28found&percnt;20on&percnt;0D&percnt;0Ahttp&percnt;3A&percnt;2F&percnt;2Ffedora.redhat.com&percnt;2Fdocs&percnt;2Fselinux-faq-fc3&percnt;2Fln-legalnotice.html&percnt;29&percnt;2C&percnt;0D&percnt;0Afor&percnt;20example&percnt;3A&percnt;0D&percnt;0A&percnt;0D&percnt;0A&percnt;20&percnt;20selinux-faq-1.3-8&percnt;20&percnt;282005-01-20-T16&percnt;3A20-0800&percnt;29&percnt;0D&percnt;0A&percnt;0D&percnt;0A&percnt;0D&percnt;0A&percnt;0D&percnt;0A&percnt;0D&percnt;0A&percnt;0D&percnt;0A&percnt;0D&percnt;0A&percnt;0D&percnt;0A&amp;keywords=&amp;dependson=&amp;blocked=118757&percnt;20&percnt;20&amp;maketemplate=Remember&percnt;20values&percnt;20as&percnt;20bookmarkable&percnt;20template&amp;form_name=enter_bug">
]>

<article id="selinux-faq" lang="it">
  <articleinfo>
    <title>&FC; &LOCALVER; &SEL; FAQ</title>
    <copyright>
      <year>2004</year>
      <holder>&FORMAL-RHI;</holder>
    </copyright>
    <authorgroup>
      <author>
        <surname>Wade</surname>
        <firstname>Karsten</firstname>
      </author>
      <!-- Italian locale by tombo at adamantio.net -->
    </authorgroup>
    &LEGALNOTICE;
  </articleinfo>

  <section id="s-selinux-faq">
    <title>&SEL; Note e FAQ</title>
    <para>
      Le informazioni in questa FAQ sono pregevoli per coloro che sono nuovi a &SEL;. Il 
      loro valore ?? apprezzabile anche se siete nuovi alle ultime implementazioni di &SEL; in &FC;, poich??
      alcuni comportamenti potrebbero essere differenti da come sapete.
    </para>
    <note>
      <title>Questa FAQ ?? specifica per &FC; &LOCALVER;</title>
      <para>
        Se state cercando le FAQ per &FC; 2, fate riferimento a <ulink
          url="http://fedora.redhat.com/docs/selinux-faq-fc2/" />.
      </para>
    </note>
    <para>
      Per maggiori informazioni su come funziona &SEL;, come usare &SEL; su distribuzioni 
      Linux generiche e specifiche, e come scrivere policy, queste sono risorse utili:
    </para>
    <itemizedlist id="external-link-list">
      <title>Lista Link Esterni</title>
      <listitem>
        <para>
          NSA &SEL; main website &mdash; <ulink
	    url="http://www.nsa.gov/selinux/" />
        </para>
      </listitem>
      <listitem>
        <para>
          NSA &SEL; FAQ &mdash; <ulink
	    url="http://www.nsa.gov/selinux/info/faq.cfm" />
        </para>
      </listitem>
      <listitem>
	<para>
	  &SEL; community page &mdash; <ulink
	    url="http://selinux.sourceforge.net" />
	</para>
      </listitem>
      <listitem>
        <para>
          UnOfficial FAQ &mdash; <ulink
	    url="http://www.crypt.gen.nz/selinux/faq.html" />
        </para>
      </listitem>
      <listitem>
        <para>
          Writing SE Linux policy HOWTO &mdash; <ulink
	    url="https://sourceforge.net/docman/display_doc.php?docid=21959&amp;group_id=21266"
	    />
        </para>
      </listitem>
      <listitem>
        <para>
          Getting Started with SE Linux HOWTO: the new SE Linux (Debian) &mdash;
	  <ulink
	    url="https://sourceforge.net/docman/display_doc.php?docid=20372&amp;group_id=21266" />
        </para>
      </listitem>
      <listitem>
        <para>
          On IRC &mdash; irc.freenode.net, #fedora-selinux
        </para>
      </listitem>
      <listitem>
        <para>
          &FED; mailing list &mdash; <ulink
	    url="mailto:fedora-selinux-list at redhat.com" />;
	  leggi gli archivi o sottoscriviti su <ulink
	    url="http://www.redhat.com/mailman/listinfo/fedora-selinux-list" />
        </para>
      </listitem>
    </itemizedlist>
    <tip>
      <title>Fare cambiamenti/aggiunte alla &FED; &SEL; FAQ</title>
      <para>
        Questa FAQ ?? disponibile su <ulink
          url="http://fedora.redhat.com/docs/selinux-faq-fc3/">http://fedora.redhat.com/docs/selinux-faq-fc3/</ulink>.
      </para>
      <para>
        Per modifiche o aggiunte alle &FED; &SEL; FAQ, usate questo <ulink
          url="&BUG-URL;">bugzilla template</ulink>, che precompila la maggior parte del
        rapporto d'errore. Le patches dovranno essere un <command>diff -u</command> rispetto all'XML,
	disponibile dal CVS (fate riferimento a <ulink
          url="http://fedora.redhat.com/projects/docs/" /> per dettagli su come 
        ottenere il modulo fedora-docs/selinux-faq via CVS anonimo; puoi avere
        solo il modulo <filename>fedors-docs/selinux-faq</filename> se non vuoi
        l'intero albero <filename>fedora-dcs</filename>.) Altrimenti,
        semplice testo che mostri prima e dopo ?? sufficiente.
      </para>
      <para>
	Per avere una lista di tutti i rapporti d'errore inerenti questa FAQ, fate riferimento a <ulink
	  url="https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=118757">https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=118757</ulink>.
      </para>
    </tip>

    <qandaset defaultlabel="qanda" id="selinux-faq-list">
      <?dbhtml toc="1"?>  
      <qandadiv id="faq-div-understanding-selinux">
        <title>Comprendere &SEL;</title>
        <qandaentry>
          <question>
            <para>
              Cos'?? &SEL;?
            </para>
          </question>
          <answer>
            <para>
              &SEL; (<firstterm>Security-Enhanced Linux</firstterm>) in &FC; ??
	      un implementazione del <firstterm>mandatory access
                control</firstterm> nel kernel di Linux che usa il
              <firstterm>Linux Security Modules</firstterm>
	      (<abbrev>LSM</abbrev>) framework. La sicurezza standard di Linux ?? basata su un modello
	      definito come <firstterm>discretionary access control</firstterm>.
            </para>
            <itemizedlist>
              <listitem>
                <para>
                  Discretionary access control (<abbrev>DAC</abbrev>) &mdash;
                  questo ?? il modello base della sicurezza di Linux, e non fornisce protezione
                  da software corrotto o malevolo eseguito come utente normale o
                  root. Gli utenti possono assegnare rischiosi livelli di accesso ai files
                  che possiedono.
                </para>
              </listitem>
              <listitem>
                <para>
                  Mandatory access control (<abbrev>MAC</abbrev>) &mdash; pieno
                  controllo su tutte le iterazioni del software. Policy definite
                  amministrativamente controllano da vicino le iterazioni fra utenti e processi
                  con il sistema, e forniscono protezione da software
                  corrotto o malevolo eseguito sotto qualsiasi utente.
                </para>
              </listitem>
            </itemizedlist>
            <para>
              In un modello DAC, i file e le risorse decisionali sono basate solamente
	      sull'identit?? utente e il proprietario degli oggetti.  Ogni utente e programma
	      eseguito da quell'utente ha completa discrezione sugli oggetti dell'utente.
              Software malizioso o difettoso pu?? fare qualsiasi cosa con i files e
              le risosrse controllate attraverso l'utente che ha avviato i processi.
              Se l'utente ?? il super-user o l'applicazione ??
              <command>setuid</command> o <command>setgid</command> root,
              il processo pu?? avere un livello di controllo root sull'intero file
              system.
            </para>
            <para>
              Un sistema MAC non soffre di questi problemi.  Primo, puoi
              definire-amministrativamente una policy di sicurezza su tutti i processi ed
              oggetti.  Secondo, puoi controllare tutti i processi e gli oggetti, nel
              caso di &SEL; mediante il kernel.  Terzo, le decisioni sono basate su
              tutte le informazioni di sicurezza rilevanti disponibili, e non solo sulla
              identit?? utente autenticata.
            </para>
            <para>
              Il MAC sotto &SEL; permette di fornire permessi granulari per tutti i
	      <firstterm>soggetti</firstterm> (utenti, programmi, processi) ed
	      <firstterm>oggetti</firstterm> (files, devices). In pratica,
	      pensa ai soggetti come processi, ed gli oggetti come lo scopo di un
	      operazione di un processo. Puoi garantire con sicurezza ad un processo solo i
	      permessi che gli occorrono per eseguire la sua funzione, e niente di pi??.
            </para>
            <para>
              L'implementazione di &SEL; usa un <firstterm>role-based access
                control</firstterm> (<abbrev>RBAC</abbrev>), che fornisce
	      un astrazione di controllo a livello-utente basata su ruoli, e sui
	      <firstterm><trademark class="registered">Type
                  Enforcement</trademark></firstterm> (<abbrev>TE</abbrev>). TE
              usa una tabella (matrice) per manipolare i controlli di accesso, applicando le regole
	      della policy basate sui tipi di processi ed oggetti.  I tipi di processo
	      sono chiamati domini, ed un riferimento incrociato sulla matrice dei
	      domini dei processi e del tipo degli oggetti definisce la loro interazione.
	      Questo pu?? fornire un controllo estremamente granulare per gli attori in un sistema
	      Linux.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
               Cos'?? una policy &SEL;?
            </para>
          </question>
          <answer>
            <para>
              La policy &SEL; descrive i permessi di accesso per tutti i soggetti
	      e gli oggetti, esempio, l'intero sistema degli utenti, programmi, e
	      processi ed i files ed i devices su cui agiscono. La policy di  &FC; ??
	      contenuta in un pacchetto, con una pacchetto sorgente associato. Attualmente
	      i pacchetti che contengono le policy sono:
            </para>
            <itemizedlist>
              <listitem>
                <para><filename>selinux-policy-strict-<replaceable>&lt;version-arch&gt;</replaceable>.rpm</filename> 
                  and
                  <filename>selinux-policy-strict-sources-<replaceable>&lt;version-arch&gt;</replaceable>.rpm</filename>
                </para>
              </listitem>
              <listitem>
                <para>
                  <filename>selinux-policy-targeted-<replaceable>&lt;version-arch&gt;</replaceable>.rpm</filename> 
                  and
                  <filename>selinux-policy-targeted-sources-<replaceable>&lt;version-arch&gt;</replaceable>.rpm</filename>
                </para>
              </listitem>
            </itemizedlist>
            <para>
              I sorgenti delle policy risiedono in
	      <filename>/etc/selinux/<replaceable>policyname</replaceable>/src/policy</filename>,
	      quando sono installati, ed i files binari delle policy in
	      <filename>/etc/selinux/<replaceable>policyname</replaceable>/policy</filename>.
	      Il sorgente delle policy non ?? necessario per le installazioni ultra-minimali. La
	      policy per i tipi ed i domini ?? configurata separatamente dal
	      contesto di sicurezza per i soggetti e gli oggetti.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
<!-- https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133403 thanks to -->
<!-- dwalsh for supplying the source FAQs -->
          <question>
            <para>
              Cos'?? la policy targeted di &SEL;?
            </para>
          </question>
          <answer>
            <para>
              Inizialmente, quando &SEL; fu incluso in Fedora Core, la policy strict di NSA
	      fu applicata. A scopo di prova, ci?? aiut?? a trovare
	      centinaia di problemi nella strict policy. In seguito, ?? divenne
	      ovvio che applicare una singola strict policy ai molti ambienti
	      degli utenti &FED; non era fattibile. Amministrare una singola
	      strict policy per qualsiasi cosa diversa dal'installazione standard
	      avrebbe richiesto un esperienza locale superiore.
            </para>
            <para>
              A questo punto, gli sviluppatori &SEL; rividero le loro scelte, e
	      decisero di adottare una strategia differente. Fu deciso di creare una
	      policy che puntasse a bloccare specifici demoni, specialmente
	      quelli pi?? vulnerabili agli attacchi o pi?? devastanti per il sistema se corrotti o
	      compromessi. Al resto del sistema ?? consentita l'esecuzione come fosse sotto
	      la sicurezza standard di Linux, esempio, funzionare lo stesso se &SEL; ?? abilitato o meno.
            </para>
            <para>
              Sotto la policy targeted, molti processi sono eseguiti nel
	      dominio <computeroutput>unconfined_t</computeroutput>. Come implica
	      il nome, questi processi non sono per lo pi?? confinati dalla
	      policy &SEL;. Questi sono comunque ancora governati dalla sicurezza
	      standard di Linux/UNIX.
            </para>
            <para>
              Specifici demoni di rete hanno policy scritte per loro, e la
	      policy <computeroutput>unconfined_t</computeroutput> transita
	      su queste policies quando l'applicazione viene avviata. Per esempio, al
	      boot del sistema, <command>init</command> viene eseguito sotto la
	      policy <computeroutput>unconfined_t</computeroutput>, ma quando viene
	      avviato <command>named</command>, ?? transitato sotto il dominio
	      <computeroutput>named_t</computeroutput> ed ?? bloccato dalla policy appropriata.
            </para>
            <para>
	      Per maggiori informazioni sull'abilitazione e disabilitazione delle policy targeted
	      per ogni demone specifico, fate riferimento a <xref
	      linkend="using-s-c-securitylevel"/>.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
<!-- https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133403 thanks to -->
<!-- dwalsh for supplying the source FAQs -->
          <question>
            <para>
              Che demoni sono protetti dalla targeted policy?
            </para>
          </question>
          <answer>
            <para>
	      Attualmente, la lista dei demoni ?? <command>dhcpd</command>,
              <command>httpd</command> (<filename>apache.te</filename>),
              <command>named</command>, <command>nscd</command>,
              <command>ntpd</command>, <command>portmap</command>,
              <command>snmpd</command>, <command>squid</command>, and
	      <command>syslogd</command>. I files di policy per questi demoni si
              trovano in
              <filename>/etc/selinux/targeted/src/policy/domains/program</filename>.
            </para>
            <para>
              In futuro, molti demoni saranno aggiunti alla policy di protezione
	      targeted.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Che demoni aggiungerete alla targeted policy? Che ne dite
	      di Sendmail, Postfix, MySQL, o PostgreSQL?
            </para>
          </question>
          <answer>
            <para>
              Gli sviluppatori di &SEL; vorrebbero aggiungere eventualmente ftp e gli agenti di
	      posta elettronica alla targeted policy. Ad esempio, <command>vsftpd</command> potrebbe
	      funzionare in modo simile a <command>login</command>: dopo il log-in, un nuovo processo ?? eseguito sotto il contesto dell'utente (contesto utente reale o anonimo).
            </para>
            <para>
              Un problema con gli agenti di posta elettronica ?? che hanno spesso hanno bisogno di
	      manipolare files nelle home directory utente. Un obbiettivo della targeted policy
	      ?? quello di evitare problemi di etichettatura nelle home directory degli utenti.
	      Ci si sta ancora lavorando su.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              E la policy strict? Funzioner?? comunque?
            </para>
          </question>
          <answer>
            <para>
              La policy strict su  &FC; <emphasis>funziona</emphasis>. La sfida ??
	      con gli ambienti unici di utenti differenti. Per farla funzionare
	      nel tuo ambiente, avrai bisogno di aggiustare sia la policy
	      che i tuoi sistemi.
            </para>
            <para>
              Per aiutare a rendere semplice l'uso della strict policy, gli sviluppatori di  &SEL;
	      hanno lavorato sul rendere il cambiamento da un policy all'altra
	      semplice. Per esempio,
	      <command>system-config-securitylevel</command> fa una rietichettatura
	      negli scripts di avvio.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Cosa sono i file contexts?
            </para>
          </question>
          <answer>
            <para>
              I file contexts sono usati dal comando <command>setfiles</command>
	      per rendere persistenti le etichette che descrivono il contesto di sicurezza
	      per un file o una directory.
            </para>
            <para>
              &FC; ?? rilasciato con lo script <command>fixfiles</command> che
	      supporta tre opzioni: <option>check</option>,
	      <option>restore</option>, e <option>relabel</option>. Questo
	      permette agli utenti di rietichettare il file system senza aver installato il
	      pacchetto <filename>selinux-policy-targeted-sources</filename>.
	      L'uso della linea di comando ?? molto pi?? amichevole rispetto
	      al comando <command>setfiles</command> standard.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come posso vedere il contesto di sicurezza di un file, un utente, o un processo?
            </para>
          </question>
          <answer>
            <para>
              La nuova opzione <option>-Z</option> ?? il metodo piu immediato per
	      mostrare il contesto di un soggetto o di un oggetto:
            </para>
<screen>
<command>ls -alZ <replaceable>file.foo</replaceable> 
id -Z 
ps -eZ</command>
</screen>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Che differenza c'?? fra un <firstterm>dominio</firstterm> ed
              un <firstterm>tipo</firstterm>?
            </para>
          </question>
          <answer>
            <para>
              Non c'?? differenza fra un dominio ed un tipo, comunque
	      il dominio ?? qualche volta usato per riferisi al tipo di un processo.
	      L'uso del dominio in questo modo discende dal tradizionale modello TE, dove
	      i domini ed i tipi sono separati.
            </para>
          </answer>
        </qandaentry>
      </qandadiv>
      <qandadiv id="faq-div-controlling-selinux">
        <title>Controllare &SEL;</title>
        <qandaentry>
          <question>
            <para>
              Come installo o non installo &SEL;?
            </para>
          </question>
          <answer>
            <para>
              Il programma di installazione si comporta basandosi sulle scelte che fai nella
	      schermata di <guilabel>Configurazione del Firewall</guilabel>. Di base
	      la policy applicata ?? la targeted, che per scelta predefinita ?? attiva.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come cambio la policy che sto usando?
            </para>
          </question>
          <answer>
            <caution>
              <title>Cambiare policy non ?? una cosa da prendere alla leggera.</title>
              <para>
                A meno che tu non stia provando una nuova policy su una macchina test a
		scopo di ricerca, dovresti seriamente considerare la situazione
		prima di cambiare policy su un sistema in produzione.
              </para>
              <para>
                Il modo di cambiare policy ?? semplice. Questo ?? un metodo abbastanza
		sicuro, ma deve prima essere provato su un sistema test.
              </para>
            </caution>
            <para>
              Un metodo ?? quello di usare
	      <command>system-config-securitylevel</command> per cambiare la
	      policy e impostare il filesystem da rietichettare.
            </para>
            <para>
              La seguente ?? la procedura manuale:
            </para>
            <procedure>
              <step>
                <para>
                  Edita <filename>/etc/selinux/config</filename> e cambia il
                  tipp di policy in
                  <computeroutput>SELINUXTYPE=<replaceable>policyname</replaceable></computeroutput>.
                </para>
              </step>
              <step>
                <para>
                  Per essere sicuri che tu possa avere un sistema funzionante dopo un reboot, setta
		  il modo a <computeroutput>SELINUX=permissive</computeroutput>. In questo modo
		  SELinux sar?? eseguito sotto la corretta policy, ma ti permetter?? di fare
		  il login se c'?? qualche problema, tipo il contesto di un file non correttamente
		  etichettato.
                </para>
              </step>
              <step>
                <para>
                  Di agli init scripts di rietichettare il sistema al riavvio con il
                  comando <command>touch /.autorelabel</command>.
                </para>
              </step>
              <step>
                <para>
                  Riavvia il sistema.  Un riavvio pulito sotto la nuova policy
                  permetter?? a tutti i processi del sistema di avviarsi nel contesto
                  appropriato, e rivelare qualsiasi problema nel cambiamento di policy.
                </para>
              </step>
              <step>
                <para>
                  Conferma che i tuoi cambiamenti abbiano effetto con il comando
                  <command>sestatus -v</command>.  Con il nuovo sistema avviato
                  in modalit?? <computeroutput>permissive</computeroutput>, controlla
                  <filename>/var/log/messages</filename> per i messaggi
                  <computeroutput>avc:  denied</computeroutput>.  Questi
                  possono indicare un problema che deve essere risolto affinch?? il sistema
                  possa funzionare senza difficolt?? sotto la nuova policy.
                </para>
              </step>
              <step>
                <para>
                  Quando sei soddisfatto che il sistema sia stabile sotto la
                  nuova policy, abilita l'enforcing cambiando
                  <computeroutput>SELINUX=enforcing</computeroutput>.  Puoi
                  sia riavviare che eseguire <command>setenforce 1</command> per passare
                  in enforcing in tempo reale.
                </para>
              </step>
            </procedure>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come eseguo il back up dei files da un file system &SEL;?
            </para>
          </question>
          <answer>
            <para>
              Puoi usare l'utilit?? <command>star</command>, che supporta
              gli attributi estesi che contengono le etichette dei contesti di sicurezza.
              Specifica il formato <option>-xattr</option> e <option>exustar</option>
              quando creai gli archivi.
            </para>
<screen>
<command>ls -Z /var/log/maillog</command>
-rw-------  root   root    system_u:object_r:var_log_t   /var/log/maillog
<command>cd /var/log
star -xattr -H=exustar -c -f maillog.star ./maillog*</command>
</screen>
            <caution>
              <title>I percorsi assoluti possono sovrascrivere i dati esistenti</title>
              <para>
                Se usi un percorso assoluto, come
                <filename>/var/log/maillog</filename>, quando decompatti l'archivio
                con <command>star -c
                -f</command>, i files verranno ripristinati nello stesso percorso in
                cui erano stati archiviati.  Il file <filename>maillog</filename> tenter??
                di scriverli in <filename>/var/log/maillog</filename>.  Potresti
                ricevere un avviso da <command>star</command> se i
                files che stanno per essere sovrascritti hanno una data pi?? recente, ma non potrai
                contare su questo comportamento.
              </para>
              <para>
                Considera attentamente come costruire gli argomenti d'archiviazione.
              </para>
            </caution>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come posso installare la policy strict per default con il kickstart?
            </para>
          </question>
          <answer>
            <procedure>
              <step>
                <para>
                  Sotto la sezione <computeroutput>%packages</computeroutput>,
                  aggiungete <filename>selinux-policy-strict</filename>.
                </para>
              </step>
              <step>
                <para>
                  Sotto la sezione <computeroutput>%post</computeroutput>,
                  aggiungete quanto segue:
                </para>
<screen>
<computeroutput>lokkit -q --selinuxtype=strict
touch /.autorelabel</computeroutput>
</screen>
              </step>
            </procedure>
          </answer>
        </qandaentry>
        <qandaentry id="using-s-c-securitylevel" xreflabel="How to use system-config-securitylevel">
          <question>
            <para>
              Come abilito/disabilito la protezione &SEL; per uno specifico demone sotto
	      la policy targeted?
            </para>
          </question>
          <answer>
            <para>
              Usa <command>system-config-securitylevel</command> per controllare i
	      valori Booleani di specifici demoni. Per esempio, se ritieni
	      di aver bisogno di sisabilitare &SEL; per Apache per eseguirlo correttamente nel tuo
	      ambiente, puoi disabilitare il valore in
	      <command>system-config-securitylevel</command>. Questo disattiva la
	      transizione della policy definita in
	      <filename>apache.te</filename>, lasciando rimanere <command>httpd</command>
	      sotto la regolare sicurezza Linux.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come faccio funzionare una directory utente <filename>public_html</filename>
              sotto &SEL;?
            </para>
          </question>
          <answer>
            <para>
              Questo processo presume che hai abilitato le directories HTML pubbliche per gli utenti
              nella configurazione HTTP di Apache
              (<filename>/etc/httpd/conf/httpd.conf</filename>).  Questo processo
              copre solo il servizio di contenuti Web statici.  Per maggiori informazioni
              su &APACHE; e &SEL;, riferitevi a <ulink
                url="http://fedora.redhat.com/docs/selinux-apache-fc3/" />.
            </para>
            <procedure>
              <step>
                <para>
                  Se non l'hai gi??, avrai necessit?? di creare la
                  directory <filename>public_html</filename> e popolarla con
                  i files e le cartelle che dovranno essere servite.
                </para>
<screen>
<command>cd ~
mkdir public_html
cp /path/to/content ~/public_html</command>
</screen>
              </step>
              <step>
                <para>
                  A questo punto, <command>httpd</command> ?? configurato per servire
                  i contenuti, ma tu continuerai a ricevere un errore <computeroutput>403
                    forbidden</computeroutput>.  Questo poich?? ad
                  <command>httpd</command> non ?? consentito di leggere i tipi
                  di sicurezza per le directory ed i files che vengono creati nelle
                  directory home degli utenti.  Per risolvere questo, cambiate i contesti
                  di sicurezza della cartella e dei suoi contenuti ricursivamente usando
                  l'opzione <option>-R</option>:
                </para> 
<screen>
<command>ls -Z -d public_html/</command>
<computeroutput>drwxrwxr-x  auser    auser    user_u:object_r:user_home_t      public_html</computeroutput>
<command>chcon -R -t httpd_user_content_t public_html/
ls -Z -d public_html/</command>
<computeroutput>drwxrwxr-x  auser    auser    user_u:object_r:httpd_user_content_t public_html/</computeroutput>
<command>ls -Z public_html/</command>
<computeroutput>-rw-rw-r--  auser    auser    user_u:object_r:httpd_user_content_t bar.html
-rw-rw-r--  auser    auser    user_u:object_r:httpd_user_content_t baz.html
-rw-rw-r--  auser    auser    user_u:object_r:httpd_user_content_t foo.html</computeroutput>
</screen>
                <para>
                  Potrai notare qualche tempo dopo che il campo user, impostato
                  a <computeroutput>user_u</computeroutput>, ?? cambiato in
                  <computeroutput>system_u</computeroutput>.  Ci?? non
                  avr?? effetto su come funziona la policy targeted; il campo che conta
                  ?? il campo tipo.
                </para>
              </step>
              <step>
                <para>
                  Adesso sarai in grado di servire pagine web statiche. Se
                  continuerai ad avere errori, controlla di vedere che la Booleana che
                  abilita le home directories utente sia abilitata.  Questo pu?? essere impostato
                  usando <application>system-config-securitylevel</application>,
                  sotto il tab <guilabel>&SEL;</guilabel> all'interno dell'area <guilabel>Modifica la
                    Policy &SEL;</guilabel>, abilitando <computeroutput>Permetti
                  ad HTTPD di leggere le home directories</computeroutput>.  I cambiamenti avranno
                  effetto immediato.
                </para>
              </step>
            </procedure>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come disabilito &SEL; all'avvio?
            </para>
          </question>
          <answer>
            <para>
              Aggiungi <option>selinux=0</option> alla linea di comando del tuo kernel.
            </para>
            <caution>
              <title>Sta attento quando disabiliti &SEL;</title>
              <para>
                Sta veramente attento nell'usare questa opzione.  Se esegui l'avvio con
		<option>selinux=0</option>, ogni file che hai creato mentre &SEL; ??
		disabilitato non avr?? le informazioni di contesto &SEL;. Dovrai come minimo
		rietichettare il file system, ed ?? possibile che
                non sarai in grado di avviare il sistema con <option>selinux=1</option>,
                necessitando un avvio in modalit?? single-user per il ripristino.
              </para>
              <para>
                Come alternativa a <option>selinux=0</option>, prova ad usare
                <computeroutput>SELINUX=disabled</computeroutput> in
                <filename>/etc/selinux/config</filename>.
              </para>
            </caution>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come pongo l'enforcing on/off all'avvio?
            </para>
          </question>
          <answer>
            <para>
              Puoi specificare la modalit?? &SEL; usando il file di configurazione
	      <filename>/etc/sysconfig/selinux</filename>.
            </para>
<screen>
<computeroutput># This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing - SELinux security policy is enforced.
#       permissive - SELinux prints warnings instead of enforcing.
#       disabled - No SELinux policy is loaded.
SELINUX=<replaceable>enforcing</replaceable>
# SELINUXTYPE= type of policy in use. Possible values are:
#       targeted - Only targeted network daemons are protected.
#       strict - Full SELinux protection.
SELINUXTYPE=<replaceable>targeted</replaceable>
</computeroutput>
</screen>
            <para>
              Impostando il valore su <computeroutput>enforcing</computeroutput> ??
              uguale ad aggiungere <option>enforcing=1</option> alla linea di comando
	      quando avvii il kernel per attivare l'enforcing, mentre impostando
              il valore su <computeroutput>permissive</computeroutput> ?? come
              aggiungere <option>enforcing=0</option> per disattivare l'enforcing.
              Nota che il <emphasis role="bold">parametro della linea di comando del kernel
                prevarica il file di configurazione</emphasis>.
            </para>
            <para>
              Comunque, impostare il valore su
              <computeroutput>disabled</computeroutput> non ?? lo stesso di
              <option>selinux=0</option> nel parametro di avvio del kernel.  Invece di
              disabilitare pienamente &SEL; nel kernel, l'impostazione
	      <computeroutput>disabled</computeroutput> disabilita l'enforcing
	      e salta il caricamento della policy.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come disabilito temporaneamente la modalit?? di enforcing senza dover
	      riavviare?
            </para>
          </question>
          <answer>
            <para>
              Questa situazione solitamente insorge quando non puoi eseguire un operazione
              che viene prevenuta dalla policy.  Esegui il comando
              <command>setenforce 0</command> per disabilitare la modalit?? di enforcing in
	      tempo reale.  Quando hai terminato, esegui <command>setenforce 1</command>
              per riattivare l'enforcing.
            </para>
            <note>
              <title>E' richiesto il ruolo <computeroutput>sysadm_r</computeroutput></title>
              <para>
                Devi lanciare il comando <command>setenforce</command> con
		il ruolo <computeroutput>sysadm_r</computeroutput>; per farlo,
                usa il comando <command>newrole</command>. Alternativamente, se
                cambi su root usando <command>su -</command>, otterrai il ruolo
                <computeroutput>sysadm_r</computeroutput> automaticamente.
              </para>
            </note>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come pongo l'auditing alle system-call on/off all'avvio?
            </para>
          </question>
          <answer>
            <para>
              Aggiungi <option>audit=1</option> alla linea di comando del kernel per attivare
              l'auditing alle system-call.  Aggiungi <option>audit=0</option> alla
              linea di comando del kernel per disattivare l'auditing alle system-call.
            </para>
            <para>
              L'auditing alle system-call ?? disattivato per impostazione predefinita. Quando ?? attivato,
	      fornisce informazioni sulle system-call che erano in esecuzione quando SELinux
	      genera un messaggio <computeroutput>denied</computeroutput>.  Questo
	      pu?? essere d'aiuto quando fai il debugging della policy.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come disabilito temporaneamente l'auditing alle system-call senza dover
	      riavviare?
            </para>
          </question>
          <answer>
            <para>
              Questa opzione al momento non ?? supportata. In futuro, verr?? fornita un utilit??
	      per amministrare l'auditing.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come ottengo informazioni sullo status della mia installazione &SEL;?
            </para>
          </question>
          <answer>
            <para>
              Come root, esegui il comando <command>/usr/sbin/sestatus
                -v</command>.  Per maggiori informazioni, fa riferimento alla
	      pagina di manuale di
              <filename>sestatus(8)</filename>.
            </para>
          </answer>
        </qandaentry>
      </qandadiv>
      <qandadiv id="faq-div-resolving-problems">
        <title>Risoluzione dei problemi</title>
        <qandaentry>
          <question>
            <para>
              La mia applicazione non funziona come mi aspettavo e sto vedendo
	      dei messaggi <computeroutput>avc: denied</computeroutput>, come
	      risolvo?
            </para>
          </question>
          <answer>
            <para>
              Questo messaggio vuol dire che l'attuale policy SELinux non permette
	      all'applicazione di fare qualcosa. C'?? un numero di ragioni
	      per cui ci?? pu?? succedere.
            </para>
            <para>
              Primo, uno dei files a cui l'applicazione prova ad accedere potrebbe
	      essere etichettato male.  Se il messaggio AVC si riferisce ad un file specifico,
	      controlla la sua etichetta corrente con <command>ls -alZ
                <replaceable>/path/to/file</replaceable></command>.  Se vi sembra
	      sbagliata, potrete provare ad usare <command>restorecon -v
                <replaceable>/path/to/file</replaceable></command>. Se hai
	      un gran numero di dinieghi relativi a files, potresti voler usare
              <command>fixfiles relabel</command>, o eseguire
              <command>restorecon</command> con l'opzione <option>-R</option>
              per rietichettare recursivamente il percorso di una directory.
            </para>
            <para>
              Altre volte, i dinieghi possono essere dovuti ad un cambiamento nella
	      configurazione del programma non ammesso dalla policy. Per esempio, se
	      vuoi far si che Apache ascolti anche sulla port 8800, questo richieder?? un
	      cambiamento nella policy di sicurezza, <filename>apache.te</filename>. Vedi
	      <xref linkend="external-link-list"/> per maggiori informazioni sulla
	      scrittura delle policy.
            </para>
            <para>
	      Se hai difficolt?? nel far funzionare un'applicazione specifica
	      come Apache, vedi <xref linkend="using-s-c-securitylevel"/> 
	      to work, see <xref linkend="using-s-c-securitylevel"/> per
	      sapere come disabilitare l'enforcement solo per quell'applicazione.
            </para>
          </answer>
        </qandaentry>
<!--	<qandaentry>
	  <question>
	    <para>
	      I'm trying to upgrade from &FC; &FCVER; to &FC; &LOCALVER;, and
	      the installer keeps crashing with an &SEL; error.
	    </para>
	  </question>
	  <answer>
	    <para>
	      This occurs because Anaconda finds an existing
	      <filename>/selinux</filename> directory.  This problem has been
	      fixed in the latest version of the installer.
	    </para>
	    <para>
	      To work around this bug, either remove the directory just prior to
	      upgrading, <command>rm -rf /selinux</command>, or during an
	      install, switch to tty2 before packages start being upgraded, and
	      do <command>rm -rf /mnt/sysimage/selinux</command>.
	    </para>
	  </answer>
	</qandaentry>
-->
        <qandaentry>
          <question>
            <para>
              Ho installato &FC; su un sistema con una partizione
	      <filename>/home</filename> gi?? esistente, ed ora non posso fare il log in.
            </para>
          </question>
          <answer>
            <para>
              La tua partizione <filename>/home</filename> non ?? etichettata
              correttamente.  Puoi facilmente risolvere questo problema in due modi.
            </para>
            <para>
              Se vuoi solamente rietichettare <filename>/home</filename>
	      ricorsivamente:
            </para>
<screen>
<command>/sbin/restorecon -v -R /home</command>
</screen>
            <para>
	      Se vuoi essere sicuro che non ci siano altri files non correttamente
	      rietichettati, puoi rietichettare l'intero filesystem:
            </para>
<screen>
<command>/sbin/fixfiles relabel</command>
</screen>
            <para>
              Dovrai avere installato il pacchetto <filename>policycoreutils</filename>
	      per usare <command>fixfiles</command>.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Dopo aver rietichettato la mia <filename>/home</filename> usando
	      <command>setfiles</command> o <command>fixfiles</command>, sar??
	      ancora in grado di leggere <filename>/home</filename> con un
	      sistema con &SEL; non abilitato?
            </para>
          </question>
          <answer>
            <para>
              Puoi leggere i files da una distribuzione senza &SEL;, o una con
	      &SEL; disabilitato. Comunque, i files creati dal sistema privo di &SEL;
	      non avranno un contesto di sicurezza, nemmeno l'avr?? qualsiasi files che
	      rimuoverai e ricreerai. Questo potrebbe essere un problema con files tipo
	      <filename>~/.bashrc</filename>. Dovrai rietichettare la tua
	      <filename>/home</filename> quando ritornerai a &FC;.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come posso condividere directories usando NFS tra &FC; e sistemi
	      non-&SEL;
            </para>
          </question>
          <answer>
            <para>
              NFS supporta in modo trasparente molti tipi di file system, e pu??
	      essere usato per condividere directories tra sistemi &SEL; e non-&SEL;.
            </para>
            <para>
              Quando monti un file system non-&SEL; via NFS, per impostazione predefinita &SEL;
	      tratter?? tutti i files nella condivisione come avessero contesto
	      <computeroutput>nfs_t</computeroutput>. Potrai prevaricare il contesto predefinito
	      impostandolo manualmente usando l'opzione
	      <option>context=</option>.  Ad esempio, questo far??
	      apparire i files nella directory NFS montata con un contesto di 
	      <computeroutput>system_u:object_r:tmp_t</computeroutput> in &SEL;:
            </para>
<screen>
<command>mount -t nfs -o context=system_u:object_r:tmp_t server:/shared/foo /mnt/foo</command>
</screen>

            <para>
              Quando &SEL; esporta un file system via NFS, i files creati avranno
	      il contesto della directory dove sono stati creati. In altre
	      parole, la presenza di &SEL; sul sistema remoto che ha montato la condivisione non ha
	      effetto sui contesti di sicurezza locali.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come posso creare un nuovo account utente Linux con la home directory utente
	      avente il contesto appropriato?
            </para>
          </question>
          <answer>
	    <!-- wtf was I trying to say here?
	    <para>
	      This depends on the policy you are running.  A very restrictive
	      policy requires you to change
	    </para>
	    -->
            <para>
              Puoi creare il nuovo utente con il comando standard
	      <command>useradd</command>. Prima dovrai diventare root;
	      sotto la policy strict avrai bisogno di cambiare al ruolo
	      <computeroutput>sysadm_r</computeroutput>. Questo cambio di contesto
	      ?? stato incorporato nel comando <command>su</command> ed
	      avviene automaticamente. Per la policy targeted, non avrai bisogno
	      di cambiare ruolo, rimanendo in
              <computeroutput>unconfined_t</computeroutput>:
            </para>
<screen>
<command>su - root
id -Z
root:system_r:unconfined_t
useradd auser
ls -Z /home
drwx------  auser   auser   root:object_r:user_home_dir_t /home/auser</command>  
</screen>
            <para>
              Il contesto iniziale per una nuova directory utente ha un identit?? di
              <computeroutput>root</computeroutput>.  In seguinto la rietichettatura del
              file system cambier?? l'identit?? a
              <computeroutput>system_u</computeroutput>.  Queste sono funzionalmente
              le stesse poich?? il ruolo ed il tipo sono identici
              (<computeroutput>object_r:user_home_dir_t</computeroutput>.)
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Tutte le altre documentazioni su &SEL; affermano che il
              comando <command>su</command> cambier?? solamente l'identit?? Linux
              e <emphasis>non</emphasis> il ruolo di sicurezza.
            </para>
          </question>
          <answer>
            <para>
              Il team di sviluppo di &FC; ha preso una direzione leggermente differente
              rispetto alla pratica di &SEL; esistente.  Le transizioni del contesto di sicurzza adesso
              sono integrate in <command>su</command> via
              <computeroutput>pam_selinux</computeroutput>.  Questo semplifica
              enormemente l'uso del sistema.
            </para>
            <para>
              In pratica, ?? come combinare il tradizionale
	      <command>su</command> con il <command>newrole</command> di &SEL;,
              in un singolo passo invece di due.
            </para>
            <para>
              Altre forme di cambio d'identit?? di Linux/<trademark
                class="registered">UNIX</trademark>, per esempio
              <command>setuid(2)</command>, non causano un cambio d'identit??
	      &SEL;.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Sto avendo alcune difficolt?? con errori <command>avc</command> che riempiono
	      i miei logs per un programma in particolare. Come scelgo escluderne l'audit
	      d'accesso?
            </para>
          </question>
          <answer>
            <para>
              Per esempio, se volevi escludere l'audit di <command>dmesg</command>,
	      potresti inserire questa riga nel tuo file
              <filename>/etc/selinux/targeted/src/policy/dmesg.te</filename>
            </para>
<screen>
<computeroutput>dontaudit dmesg_t userdomain:fd { use };</computeroutput>
</screen>
            <para>
              Questo eliminer?? l'output d'errore dal terminale per tutti
	      gli userdomains (<varname>user</varname>, <varname>staff</varname>  e
	      <varname>sysadm</varname>).
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Anche avviando in modalit?? permissive, ho un gran numero di
	      messaggi <computeroutput>avc denied</computeroutput>.
            </para>
          </question>
          <answer>
            <para>
              In modalit?? non-enforcing, avrai
	      <emphasis>pi??</emphasis> messaggi che in modalit?? enforcing. Ci??
	      avviene poich?? il kernel sta loggando ogni diniego di accesso come fossi
	      in modalit?? enforcing. Siccome non hai restrizioni, puoi
	      fare pi?? cose, che danno come risultato pi?? log di
	      diniego.
            </para>
            <para>
              Per esempio, se un applicazione eseguita sotto la modalit?? enforcing ha
	      il divieto provare a leggere un certo numero di files in una directory, essa
	      verr?? fermata all'inizio dell'azione. In
	      modalit?? non-enforcing, l'applicazione non viene fermata dal traversare
	      l'albero della directory, e ricever?? un messaggio di diniego per ogni
	      file letto nella directory.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Ho un particolare diniego di premesso solo quando &SEL; ?? in modalit??
	      enforcing, ma non vedo nessun messaggio di audit in
	      <filename>/var/log/messages</filename>. Come posso identificare la
	      causa di questi dinieghi silenziosi?
            </para>
          </question>
          <answer>
            <para>
              La ragione pi?? comune per un diniego silenzioso ?? quando la policy
	      contiene un esplicita regola di <computeroutput>dontaudit</computeroutput>
	      per sopprimere i messaggi di audit. La
	      regola di <computeroutput>dontaudit</computeroutput> ?? spesso usata
	      quando un segnale di diniego benigno riempie gli audit logs.
            </para>
            <para>
              Per vedere il tuo particolare diniego, dovrai abilitare
	      l'auditing di tutte le regole <computeroutput>dontaudit</computeroutput>:
            </para>
<screen>
<command>cd /etc/selinux/targeted/src/policy 
make enableaudit
make load</command>
</screen>
            <caution>
              <title>Abilitare l'output di <computeroutput>dontaudit</computeroutput>
                ?? verboso</title>
              <para>
                Abilitare l'auditing di tutte
		le regole <computeroutput>dontaudit</computeroutput> produrr??
		un gran numero di informazioni audit, molte delle quali
		irrilevanti per il tuo diniego.
              </para>
              <para>
                Usa questa tecnica solo se stai cercando un
		messaggio di diniego che sembra avvenire silenziosamente.
		Probabilmente desidererai ri-abilitare
		le regole <computeroutput>dontaudit</computeroutput> il pi?? presto
		possibile.
              </para>
            </caution>
            <para>
              Per ri-abilitare le regole <computeroutput>dontaudit</computeroutput>,
	      fai cos??:
            </para>
<screen>
<command>cd /etc/selinux/targeted/src/policy
make clean 
make load</command>
</screen>
<!-- commented out just in case it needs to be rewritten and included:
         <para>
           Another reason for getting silent denials is on an
           <function>exec</function> when a domain transition would
           normally occur, but the new domain is not authorized for
           the current role.
         </para>
         <para>
           At present, these errors are only logged when &SEL; is
           running in permissive mode.  This has been fixed in the
           upstream Linux kernel so that it will log an audit message.
           The current &FC; test kernel does not yet include this
           change.
         </para>
from ssmalley:

The Fedora kernel now includes the change, so the transition failures
now show up as security_compute_sid messages (also handled via the audit
framework).  Example message below for a policy that failed to authorize
sysadm_r for system_chkpwd_t (an error from an earlier policy that has
been fixed):

audit(1083674459.837:0): security_compute_sid:  invalid context root:sysadm_r:system_chkpwd_t for scontext=root:sysadm_r:newrole_t tcontext=system_u:object_r:chkpwd_exec_t tclass=process

-->
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Perch?? non vedo l'output quando eseguo certi demoni in modalit??
	      debug o interattiva?
            </para>
          </question>
          <answer>
            <para>
              &SEL; disabilita intenzionalmente l'accesso ai dispositivi tty per impedire
              ai demoni la comunicazione verso il terminale di controllo.
              Questa comunicazione ?? un potenziale buco nella sicurezza poich?? questi
              demoni possono inserire comandi nei terminali di controllo.  Un
	      programma bacato o compromesso potrebbe causare seri problemi con
	      questo.
            </para>
            <para>
              Ci sono alcuni modi per permetterti di catturare lo STDOUT da questi demoni.  Un
              metodo ?? quello di eseguire il pipe dell'output al comando cat.
            </para>
<screen>
<command>snmpd -v | cat</command>
</screen>
            <para>
              Quando fai il debug di un demone, potresti voler disattivare la transizione
              del demone al suo dominio specifico.  Puoi farlo usando
              <application>system-config-securitylevel</application> o
              <command>setsebool</command> dalla linea di comando.
            </para>
            <para>
              Un opzione finale ?? quella di disattivare la modalit?? di enforcing durante il debug.
	      Puoi farlo con <command>setenforce 0</command>, usando
              <command>setenforce 1</command> per ri-abilitare &SEL; quando hai
              terminato il debug.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Quando eseguo un upgrade del pacchetto delle policy (per esempio, usando
	      <command>yum</command>), cosa succede con la policy; ??
	      automaticamente aggiornata?
            </para>
          </question>
          <answer>
            <para>
              Le policy si ricaricano da sole quando il pacchetto ?? aggiornato. Questo sostituisce
	      il comando manuale <command>make load</command>.
            </para>
            <para>
              In certe situazioni, pu?? essere necessario rietichettare il file
	      system. Questo potrebbe accadere per fissare gli errori di &SEL; qualora i
	      contesti dei files divenissero invalidi, o quando l'update della policy
	      fa dei cambiamenti ai <varname>file_contexts</varname>.
            </para>
            <para>
              Dopo aver rietichettato il filesystem, un <command>reboot</command> non
	      ?? necessario, ma ?? utile per assicurare che ogni processo e programma
	      sia eseguito nel dominio appropriato. Questo ?? altamente dipendente dai
	      cambiamenti nella policy aggiornata.
            </para>
            <para>
              Se hai installato i pacchetti sorgente delle policy, es.
	      <filename>selinux-policy-strict</filename>, puoi eseguire questi
	      comandi per rietichettare il file system.
            </para>
<screen>
<command>cd /etc/selinux/targeted/src/policy
make
make relabel
reboot</command>
</screen>
            <para>
              Se non stai usando i sorgenti delle policy, un altro approccio ?? usare il
	      comando <command>fixfiles</command> o avvantaggiarsi del
	      meccanismo <filename>/.autorelabel</filename>:
            </para>
<screen>
<command>fixfiles relabel
reboot</command>
</screen>
<screen>
<command>touch /.autorelabel
reboot</command>
</screen>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Se la policy rilasciata con il pacchetto di un applicazione cambia in
	      modo da richiedere la rietichettatura, potr?? RPM gestire la rietichettatura dei files
	      posseduti dal pacchetto?
            </para>
          </question>
          <answer>
            <para>
              Si. I contesti di sicurezza per i files posseduti dal pacchetto sono
	      immagazzinati nei dati dell'header del pacchetto. I contesti dei files
	      sono impostati direttamente dopo la copia <command>cpio</command>, appena i
	      files del pacchetto sono poggiati sul disco.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Che relazioni intercorrono fra il pacchetto policy e policy 
	      source?
            </para>
          </question>
          <answer>
            <!--
              thanks to "Gene C." <czar czarc net> for authoring the
              original answer in
              http://www.redhat.com/archives/fedora-test-list/2004-April/msg00755.html
            -->
            <para>
              Un pacchetto policy come
	      <filename>selinux-policy-targeted</filename> ?? un requisito per
	      un installazione &SEL; funzionante, mentre un pacchetto sorgente come
	      <filename>selinux-policy-targeted-sources</filename> ??
	      richiesto se vuoi modificare la policy predefinita.
            </para>
            <para>
              Il pacchetto policy ha i files minimi necessari per definire
	      la policy di sicurezza di &SEL;. Viene tenuto di ridotte dimensioni
	      per avere minimi requisiti di installazione.
            </para>
            <para>
              Il pacchetto dei sorgenti della policy contiene le definizioni sorgente in
	      <filename>/etc/selinux/<replaceable>policyname</replaceable>/src/policy</filename>
	      che sono richiesti per creare i files
	      <filename>/etc/selinux/<replaceable>policyname</replaceable>/contexts/*</filename>
	      e
	      <filename>/etc/selinux/<replaceable>policyname</replaceable>/policy/policy.<replaceable>version</replaceable></filename>.
	      <replaceable>version</replaceable> ?? il numero di versione della
	      policy.
            </para>
            <para>
              La scelta di quali pacchetti installare ?? basata sul tipo di
	      installazione. Se intendi usare solo la configurazione di sicurezza predefinita
	      dagli sviluppatori  &FC;, avrai bisogno solo del pacchetto
	      policy. Se vorrai adattare la tua policy di sicurezza in qualsiasi
	      modo, o vorrai eseguire <command>setools</command>, avrai bisogno
	      di installare il pacchetto di sorgenti della policy.
            </para>
            <para>
              Installando o aggiornando i pacchetti della policy, la nuova policy
	      verr?? caricata non appena intallati i nuovi files. In modo analogo, installando o aggiornando il
	      pacchetto di sorgenti della policy ricreer?? sia il file
	      <filename>policy.<replaceable>version</replaceable></filename>
	      che il file <filename>file_contexts</filename>, quindi
	      verranno ricaricati come policy attuale effettiva.
            </para>

            <!-- not sure if currently still an issue, or how to rephrase
                 <caution>
                 <title>Caution</title>
                 <para>
                 If you have locally modified any of the policy sources, you want to be cautious about updating <filename>policy</filename> or <filename>policy-sources</filename>.  Make 
                 updating policy and/or policy-sources can have
                 interesting (but not particularly desirable)
                 effects. See
                 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=118604
                 </para>
                 </caution>
            -->
          </answer>
        </qandaentry>
        <qandaentry>
          <!-- 
            http://www.redhat.com/archives/fedora-selinux-list/2004-May/msg00061.html
          -->
          <question>
            <para>
              Perch?? i files
              <filename>/etc/selinux/<replaceable>policyname</replaceable>/policy/policy.&lt;<replaceable>version</replaceable>&gt;</filename> 
              e
              <filename>/etc/selinux/<replaceable>policyname</replaceable>/src/policy/policy.&lt;<replaceable>version</replaceable>&gt;</filename> 
              sono differenti (sizes, md5sums, dates)?
            </para>
          </question>
          <answer>
            <para>
              Quando installi un pacchetto policy, i files binari pre-compilati della policy
	      sono inseriti direttamente in <filename>/etc/selinux</filename>.
	      Quando un pacchetto sorgente policy ?? installato o aggiornato, i files binari
	      della policy vengono compilati in
              <filename>/etc/selinux/<replaceable>policyname</replaceable>/src/policy</filename>, 
              quindi spostati in
              <filename>/etc/selinux/<replaceable>policyname</replaceable>/policy/</filename>. 
	      I differenti ambienti di compilazione creeranno files finali che hanno
	      differenti dimensioni, md5sums, e date.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
               I nuovi pacchetti policy potranno disabilitere il mio sistema?
            </para>
          </question>
          <answer>
            <para>
              C'?? la possibilit?? che cambiamenti nei pacchetti della policy o nella
	      policy rilasciata con un pacchetto applicativo possano causare errori,
	      pi?? dinieghi, o altri comportamenti sconosciuti. Per rimediare, puoi
	      scoprire quale pacchetto causa il problema ripristinando policy e pacchetti
	      applicativi uno alla volta. Se non vuoi tornare
	      ad una pacchetto precedente, i files di configurazione della vecchia
	      versione sono salvati con l'estensione di <filename>.rpmsave</filename>.
	      Assicurati di consultare le mailing lists, bugzilla, ed IRC per aiutarti
	      ad uscire dal problema. Se sei capace, scrivi un fix o una policy
	      per risolvere il problema.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come posso aiutare a scrivere una policy?
            </para>
          </question>
          <answer>
            <para>
              Il tuo aiuto ?? apprezzato infinitamente.  Puoi cominciare entrando a far parte della
              &SEL; mailing list, <ulink
                url="mailto:fedora-selinux-list at redhat.com">fedora-selinux-list at redhat.com</ulink>; 
	      puoi sottoscriverti e leggere gli archivi su <ulink
                url="http://www.redhat.com/mailman/listinfo/fedora-selinux-list">http://www.redhat.com/mailman/listinfo/fedora-selinux-list</ulink>. 
	      Le FAQ non ufficiali hanno qualche informazione generica su come scrivere
	      le policy (<ulink
                url="http://sourceforge.net/docman/display_doc.php?docid=14882&amp;group_id=21266#BSP.1">http://sourceforge.net/docman/display_doc.php?docid=14882&amp;group_id=21266#BSP.1</ulink>). 
	      Un'altra nuova risorsa ?? il Writing SE Linux policy HOWTO (<ulink
                url="https://sourceforge.net/docman/display_doc.php?docid=21959&amp;group_id=21266">https://sourceforge.net/docman/display_doc.php?docid=21959&amp;group_id=21266</ulink>).
            </para>
            <para>
              Il meglio su cui puoi scommettere ?? dare un occhiata ai files di policy in <filename>/etc/selinux/<replaceable>policyname</replaceable>/src/policy/</filename>
	      e provare a sperimentare. Osserva i messaggi <computeroutput>avc
                denied</computeroutput> in <filename>/var/log/messages</filename> per avere degli indizzi.
            </para>
            <para>
              Uno strumento utile per uno scrittore di policy ??
	      <command>/usr/bin/audit2allow</command>, che traduce
	      i messaggi <computeroutput>avc</computeroutput> provenienti da
	      <filename>/var/log/messages</filename> in regole che possono essere usate
	      da &SEL;.  Queste regole dovranno ovviamente essere rifinite.
            </para>
            <para>
              Il comando <command>audit2allow</command> pu?? ricevere l'input con
	      tre metodi.  Il metodo predefinito ?? dallo standard input
	      (<firstterm>STDIN</firstterm>).  Usando l'opzione <option>-i</option>
	      legge l'input da <filename>/var/log/messages</filename>,
	      e con l'opzione <option>-d</option> legge l'input dall'output
	      di <command>dmesg</command>.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              La mia console ?? inondata da messaggi, come li fermo?
            </para>
          </question>
          <answer>
            <para>
              Per riottenere il controllo, disattiva i messaggi del kernel nella console
	      usando <command>dmesg -n 1</command>.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Posso provare la policy predefinita senza installare il pacchetto
	      di sorgenti della policy?
            </para>
          </question>
          <answer>
            <para>
              Puoi provare la policy predefinita di &SEL; installando solamente
	      i pacchetti <filename>selinux-policy-<replaceable>policyname</replaceable></filename>
	      e <filename>policycoreutils</filename>. Senza il
	      pacchetto dei sorgenti della policy installato, il comando <command>fixfiles</command>
	      automatizzer?? la rietichettatura del file system.
            </para>
            <para>
              Il comando <command>fixfiles relabel</command> ?? l'equivalente
	      di <command>make relabel</command>. Durante la rietichettatura,
	      canceller?? tutti i files in <filename>/tmp</filename>,
	      ripulendo i files che potrebbero avere vecchie etichette di contesto.
            </para>
            <para>
              Altri comandi sono <command>fixfiles check</command>, che controlla
	      i files con etichette errate, e <command>fixfiles restore</command>,
	      che fissa i files mal etichettati ma non cancella i files in
	      <filename>/tmp</filename>.  <command>fixfiles</command> non
	      accetta una lista di directories come argomento, il suo scopo ??
	      rietichettare l'intero filesystem.  Se hai bisogno di rietichettare
	      un percorso specifico di directory, usa <command>restorecon</command>.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Sto avendo difficolt?? nel far funzionare un applicazione KDE sotto &SEL;.
            </para>
          </question>
          <answer>
            <para>
              Gli eseguibili KDE appaiono sempre come <command>kdeinit</command>, che
	      limita ci?? che pu?? essere fatto con la policy di &SEL;. Questo perch?? ogni
	      applicazione KDE viene eseguita nel dominio per <command>kdeinit</command>.
            </para>
            <para>
              I problemi spesso vengono fuorui quando si installa &SEL; perch?? non ??
	      possibile rietichettare <filename>/tmp</filename> e
	      <filename>/var/tmp</filename>.  Non c'?? un buon metodo di
	      determinare quale file dovrebbe avere quale contesto.
            </para>
            <para>
              La soluzione ?? quella di eseguire un pieno log out da KDE e rimuovere tutti i files
	      temporanei di KDE:
            </para>
<screen>
<command>rm -rf	/var/tmp/kdecache-<replaceable>&lt;username&gt;</replaceable>
rm -rf /var/tmp/<replaceable>&lt;other_kde_files&gt;</replaceable></command>
</screen>
            <para>
              Al prossimo login, il problema dovrebbe essere risolto.
            </para>
          </answer>
        </qandaentry>
	<qandaentry>
	  <question>
	    <para>
	      Perch?? <computeroutput>SELINUX=disabled</computeroutput> non
	      funziona per me?
	    </para>
          </question>
          <answer>
            <para>
              Fa attenzione agli spazi vuoti nel file
              <filename>/etc/sysconfig/selinux</filename>.  Il codice ?? molto
              sensibile agli spazi vuoti, anche ai tabulatori.
            </para>
          </answer>
        </qandaentry>
      </qandadiv>
      <qandadiv id="faq-div-deploying-selinux">
        <title>Implementare &SEL;</title>
        <qandaentry>
          <question>
            <para>
              Che file systems posso usare per &SEL;?
            </para>
          </question>
          <answer>
            <para>
              Il file system deve supportare le estichette
              <computeroutput>xattr</computeroutput> nel giusto
              namespace <parameter>security.*</parameter>.  Oltre a
	      ext2/ext3, XFS ha recentemente aggiunto il supporto per le necessarie
	      etichette.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Come incide &SEL; sulle prestazioni del sistema?
            </para>
          </question>
          <answer>
            <para>
              Questa ?? una variabile difficile da quantificare, ed ?? pesantemente
	      dipendente dalla grandezza del sistema su cui &SEL; sta girando. L'ultima
	      volta che le prestazioni sono state misurate, l'incidenza era circa del 7% per
	      codice completamente non raffinato. I cambiamenti da allora sembrerebbero essere
	      peggiorati in alcuni casi, tipo nel networking. Le performance
	      e l'affinamento di SELinux sono una priorit?? del team di sviluppo.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Di che tipo di implementazioni/applicazioni/systemi, etc. dovr?? tener conto
	      per l'uso con  &SEL;?
            </para>
          </question>
          <answer>
            <para>
              Inizialmente, &SEL; servir?? ai server affacciati su Internet che eseguono
	      poche, funzioni specializzate, dove ?? critico mantenere
	      una sicurezza estremamente stretta. Una simile macchina ?? tipicamente
	      priva di software extra e servizi, ed esegue un servizio
	      molto mirato od un gruppo di servizi, come un Web server o un mail
	      server.
            </para>
            <para>
              In questi servers di nicchia, potrai bloccare la policy molto strettamente.
	      Questo sar?? facilitato dal piccolo numero di interazioni con
	      gli altri componenti. In modo simile, una macchina dedicata che
	      esegue un applicazione specialistica di terze parti sar?? un buon cadidato.
            </para>
            <para>
              In futuro, &SEL; ?? orientato a tutti gli ambienti. Per questo,
	      la comunit?? e gli <abbrev>ISV</abbrev>s
	      (<firstterm>independent software vendors</firstterm>) dovranno
	      lavorare con gli sviluppatori &SEL; per produrre le policy necessarie. Finora,
	      ?? stata scritta una <firstterm>strict policy</firstterm> molto restrittiva,
	      analogamente ad una <firstterm>targeted policy</firstterm> che mira
	      a specifici, demoni vulnerabili.
            </para>
          </answer>
        </qandaentry>
        <qandaentry>
          <question>
            <para>
              Che effetto ha &SEL; sulle applicazioni di terze parti?
            </para>
          </question>
          <answer>
            <para>
              Uno degli scopi nell'implementare la policy targeted di &SEL; in &FC; ??
	      quello di permettere ad applicazioni di terze parti di funzionare senza modifiche. Questo
	      funziona perch?? la targeted policy ?? trasparente a quelle
	      applicazioni che non prova a controllare e che ricadono
	      nella sicurezza di Linux standard.  Queste applicazioni non saranno
	      eseguite in maniera extra sicura.  Una policy deve essere scritta per
	      far si che queste applicazioni siano protette dal MAC.
            </para>
            <para>
              Ci sono talmente tante variazioni nelle applicazioni di terze parti che ??
	      impossibile predire come si comporterebbero con &SEL;, anche
	      eseguendo la targeted policy. Le problematiche insorgenti possono talvolta essere
	      fissate nella policy.  Puoi capitare che &SEL; ti mostri problemi
	      di sicurezza con la tua applicazione che non sapevi di avere, richiedendo
	      una modifica dell'applicazione per poter funzionare sotto  &SEL;.
            </para>
            <para>
              Un importante valore che i testers ed utenti di &FC; porteranno alla
	      comunit?? ?? l'estensivo testing di applicazioni di terze parti. Tenendo
	      questo a mente, sei pregato di riportare le tue esperienze sull'appropriata
	      mailing list (<ulink
                url="mailto:fedora-selinux-list at redhat.com">fedora-selinux-list at redhat.com</ulink>)
	      per discuterne.
            </para>
          </answer>
        </qandaentry>
      </qandadiv>
    </qandaset>
  </section>
</article>




From fedora-docs-commits at redhat.com  Sat Nov 19 18:24:26 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Sat, 19 Nov 2005 13:24:26 -0500
Subject: install-guide Makefile,1.11,1.12
Message-ID: <200511191824.jAJIOQJs009723@cvs-int.fedora.redhat.com>

Author: kwade

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9706

Modified Files:
	Makefile 
Log Message:
Hoping I'm using this new Makefile correctly, I get errors during the build but it builds anyway, as is the way of HTML.  Please confirm I've done the right thing.  One advantage is, now the other languages should become available through Docs Rawhide.


Index: Makefile
===================================================================
RCS file: /cvs/docs/install-guide/Makefile,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- Makefile	21 Sep 2005 01:17:52 -0000	1.11
+++ Makefile	19 Nov 2005 18:24:19 -0000	1.12
@@ -1,19 +1,99 @@
 ###############################################################################
 # Makefile for RHLP docs project
 # Created by: Tammy Fox <tfox at redhat.com>
-# Last edited by: Tammy Fox <tfox at redhat.com>
+# Last edited by: Tommy Reynolds <Tommy.Reynolds at MegaCoder.com>
 # WARNING: need passivetex 1.24 for pdf generation to work
 # License: GPL
 # Copyright 2003 Tammy Fox, Red Hat, Inc.
+# Copyright 2005 Tommy Reynolds, MegaCoder.com
 ###############################################################################
+#
+# Document-specific definitions.
+#
+LANGUAGES      	= en ja_JP zh_CN
+DOCBASE        	= fedora-install-guide
 
-LANGUAGES       	= en
-DOCBASE	        	= fedora-install-guide
-XMLEXTRAFILES-en        =
+define XMLEXTRAFILES_template
+XMLEXTRAFILES-$(1)=fedora-install-guide-abouttoinstall-$(1).xml fedora-install-guide-acknowledgements-$(1).xml fedora-install-guide-beginninginstallation-$(1).xml fedora-install-guide-bootloader-$(1).xml fedora-install-guide-diskpartitioning-$(1).xml fedora-install-guide-$(1).xml fedora-install-guide-firewallconfig-$(1).xml fedora-install-guide-firstboot-$(1).xml fedora-install-guide-installingpackages-$(1).xml fedora-install-guide-installtypes-$(1).xml fedora-install-guide-intro-$(1).xml fedora-install-guide-locale-$(1).xml fedora-install-guide-networkconfig-$(1).xml fedora-install-guide-nextsteps-$(1).xml fedora-install-guide-other-instmethods-$(1).xml fedora-install-guide-packageselection-$(1).xml fedora-install-guide-rootpassword-$(1).xml fedora-install-guide-timezone-$(1).xml fedora-install-guide-upgrading-$(1).xml
+endef
 
+$(foreach LANG,${LANGUAGES},$(eval $(call XMLEXTRAFILES_template,${LANG})))
+
+#
 ######################################################
 include ../docs-common/Makefile.common
 ######################################################
-$(DOCNAME)/index.html::
-	mkdir -p $(DOCNAME)/figs
-	cp figs/*.png figs/*.eps $(DOCNAME)/figs
+#
+# If you want to add additional steps to any of the 
+# targets defined in "Makefile.common", be sure to use
+# a double-colon in your rule here.  For example, to 
+# print the message "FINISHED AT LAST" after building 
+# the HTML document version, uncomment the following 
+# line:
+#${DOCBASE}-en/index.html::
+#	echo FINISHED AT LAST
+######################################################
+# Some packaging specific vars
+VERSION=$(shell grep BOOKID $(DOCBASE)-en.xml | sed 's/<!ENTITY BOOKID "[^0-9\.]\+//' | sed 's/ .\+//')
+DATE=${shell grep BOOKID $(DOCBASE)-en.xml | sed 's/.\+(//' | sed 's/).\+//' }
+NOW=$(shell date +"%a %b %e %Y")
+SPECIN=../docs-common/packaging/fedora-doc.spec.in.common
+OMFIN=../docs-common/packaging/fedora-doc.omf.in.common
+DESKTOPIN=../docs-common/packaging/fedora-doc.desktop.in.common
+DOCSPEC=$(PWD)/SPECS/$(DOCBASE).spec
+DOCOMF=$(PWD)/SOURCES/fedora-doc-$(DOCBASE)-C.omf
+DOCDESKTOP=$(PWD)/SOURCES/fedora-doc-$(DOCBASE).desktop
+DOCSRCTAR=$(PWD)/SOURCES/$(DOCBASE)-$(VERSION).src.tar.gz
+TITLE=$(shell ../docs-common/packaging/titlegrab.py $(DOCBASE)-en.xml | sed 's/^ \+//')
+######################################################
+# Some RPM flags...
+######################################################
+RPMFLAGS=--define "docbase $(DOCBASE)" --define "version $(VERSION)" --define "_topdir $(PWD)"
+######################################################
+
+
+clean::
+	rm -rf fedora-doc-$(DOCBASE)*.rpm
+
+
+rpm: clean
+#
+# Make RPM-compliant tarball of source XML and other stuff
+	mkdir $(DOCBASE)-$(VERSION)
+	find . -maxdepth 1 -type f ! \( -name '*~' -o -name 'Makefile*' \) \
+		| cpio -pamdv $(DOCBASE)-$(VERSION)
+	find . -maxdepth 1 -type d ! \( -name '$(DOCBASE)-$(VERSION)' \
+		-o -name 'CVS' -o -name '*~' -o -name '$(DOCBASE)*' \) \
+		| cpio -pamdv $(DOCBASE)-$(VERSION)
+#
+# Make RPM build tree; don't rely on local user's setup
+	mkdir -p {BUILD,RPMS/noarch,SOURCES,SPECS,SRPMS}
+	tar -zcvf $(DOCSRCTAR) $(DOCBASE)-$(VERSION)
+	rm -rf $(DOCBASE)-$(VERSION)/
+#
+# Make rpmlint happy with a changelog entry
+# FIXME: Maybe more magic would make this stickier; pity
+#        I'm no magician...
+	sed 's/\(%changelog\)/\1\n* $(NOW) Fedora Docs Project <fedora-docs-list at redhat.com> - $(VERSION)-1\n- Update to version $(VERSION)\n/' \
+		$(SPECIN) > $(DOCSPEC)
+#
+# Fill in files
+# FIXME:  Needs to be multiplexed for LANGUAGES (see above)
+	cp $(OMFIN) $(DOCOMF)
+	cp $(DESKTOPIN) $(DOCDESKTOP)
+	sed -i 's/@VERSION@/$(VERSION)/g' $(DOCOMF)
+	sed -i 's/@DATE@/$(DATE)/g' $(DOCOMF)
+	sed -i 's/@TITLE@/$(TITLE)/g' $(DOCOMF)
+	sed -i 's/@DOCBASE@/$(DOCBASE)/g' $(DOCOMF)
+	sed -i 's/@VERSION@/$(VERSION)/g' $(DOCDESKTOP)
+	sed -i 's/@DATE@/$(DATE)/g' $(DOCDESKTOP)
+	sed -i 's/@TITLE@/$(TITLE)/g' $(DOCDESKTOP)
+	sed -i 's/@DOCBASE@/$(DOCBASE)/g' $(DOCDESKTOP)
+#
+# Do the build...
+#
+	rpmbuild -bb $(RPMFLAGS) $(DOCSPEC)
+	mv RPMS/noarch/*.rpm .
+	rpmbuild --clean --rmsource $(RPMFLAGS) $(DOCSPEC)
+	rm -rf {BUILD,RPMS,SOURCES,SPECS,SRPMS}
+	rm -rf $(DOCBASE)-$(VERSION)



From fedora-docs-commits at redhat.com  Sat Nov 19 20:22:42 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:22:42 -0500
Subject: docs-common/common bugreporting-it.xml,NONE,1.1
Message-ID: <200511192022.jAJKMgNV013134@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13110/docs-common/common

Added Files:
	bugreporting-it.xml 
Log Message:



--- NEW FILE bugreporting-it.xml ---
<tip>
  <title>Comunicare un errore sul Documento</title>

  <para>
    Per comunicare un errore o un omissione su questo documento, inviate un rapporto d'errore in &BZ;
    su &BZ-URL;.  Quando invii il tuo errore, seleziona "&BZ-PROD;" come
    <systemitem>Product</systemitem>, e seleziona il titolo di questo documento come
    <systemitem>Component</systemitem>.  La versione di questo documento ??
    &BOOKID;.
  </para>

  <para>
    I manutentori di questo documento riceveranno automaticamente il tuo rapporto d'errore.
    A favore dell'intera comunit?? &FED;, grazie per averci aiutato ad
    aggiornarci.
  </para>
</tip>



From fedora-docs-commits at redhat.com  Sat Nov 19 20:23:00 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:23:00 -0500
Subject: docs-common/common cvs-it.xml,NONE,1.1
Message-ID: <200511192023.jAJKN0Hf013158@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13140/docs-common/common

Added Files:
	cvs-it.xml 
Log Message:



--- NEW FILE cvs-it.xml ---
<!-- $Id: -->

<!--
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "This header makes editing XML easier"  >
 <!ENTITY FC          "Fedora Core"                           >
 <!ENTITY RH          "Red Hat"                               >

]>
-->

<chapter id="ch-cvs">
  <title>CVS</title>
  <para>
    Il Concurrent Versions System (<application>CVS</application>)
    fornisce un framework dove molteplici utenti possono editare gli stessi files.
    Come puoi immaginare, se un gruppo di utenti edita i files in una singola
    directory, il chaos regner??. Usando <application>CVS</application>,
    comunque, un gruppo di persone pu?? lavorare con sicurezza sullo stesso gruppo di files.
    <application>CVS</application> mantiene la copia master dei files,
    e registra chi ha cambiato cosa e quando in un depositorio centrale. Se
    insorgssero dei conflitti, <application>CVS</application> te lo far?? sapere.
    <application>CVS</application> ?? spesso usato affinch?? i programmatori possano
    condividere codice, ma funziona bene anche per la documentazione.
  </para>
  <indexterm>
    <primary>cvs</primary>
  </indexterm>
  <section id="sn-cvs-overview">
    <title>Come funziona CVS</title>
    <indexterm>
      <primary>cvs</primary>
      <secondary>come funziona</secondary>
    </indexterm>
    <indexterm>
      <primary>cvs</primary>
      <secondary>descrizione</secondary>
    </indexterm>
    <para>
      In molti casi, ogni gruppo di files che costituisce un pacchetto o un progetto
      ?? immagazzinato come un <firstterm>module</firstterm> sul CVS server.
    </para>

    <para>
      Quando lavori con i files dal <application>CVS</application>, dovrai eseguire il
      <firstterm>checkout</firstterm> di una copia del modulo sul
      file system locale. Dopo aver modificato uno o pi?? files, dovrai inviarli con un
      <firstterm>commit</firstterm> al repositorio centrale
      <application>CVS</application> server.
    </para>

    <para>
      Con <application>CVS</application> puoi editare un file senza
      prima ottenere il permesso o il locking del file. La parte
      <wordasword>concurrent</wordasword> del nome
      <application>CVS</application> viene dalla sua capacit?? di
      permettere diverse differenti persone di editare differenti parti dello stesso
      file. Siccome nessuno dei cambiamenti si sovrappone,
      <application>CVS</application> pu?? registrare correttamente i loro cambiamenti.
      In caso di cambiamenti duplicati, questi sono marcati chiaramente nei files
      e gli autori devono risolvere il problema da soli.
    </para>

    <para>
      Quando commetti i cambiamenti, solo i cambiamenti ai files che il server sa
      sono commessi. In altre parole, se crei un file nel checkout locale
      di un modulo, il nuovo file non ?? automaticamente
      inviato al server. Devi prima <firstterm>add</firstterm> il
      file al repositorio quindi eseguire il commit. Se rimuovi un file
      dal tuo checkout locale di un modulo, dovrai specificare che vuoi
      rimuoverlo dal repositorio sul CVS server e quindi
      eseguire il commit della rimozione del file.
    </para>

    <para>
      I comandi specifici per eseguire queste operazioni sono discussi in
      <xref linkend="sn-cvs-cvscommands"></xref>.
    </para>

    <para>
      Se qualcuno ha modificato il file nel tempo fra intercorso fra l'ultima volta
      che l'hai catturato dal CVS e quando hai provato ad eseguire il commit di un cambiamento,
      <application>CVS</application> prover?? ad incollare i cambiamenti alla
      copia master sul <application>CVS</application> server. Se
      il contenuto che hai cambiato ?? in una locazione differente nel file
      rispetto la contenuto cambiato da qualcun'altro, l'azione del commit
      andr?? avanti senza alcun <firstterm>conflitto</firstterm>.
      Se qualcuno modifica lo stesso contenuto che hai gi?? cambiato tu
      e provi a fare un commit, vedrai un messaggio che ?? avvenuto
      il conflitto su un file. Cos??, dovrai fare l'
      <firstterm>update</firstterm> dei tuoi files di frequente. E' una buona pratica
      aggiornarli prima di iniziare a modificarli.
      Fa riferimento a <xref linkend="sn-cvs-cvscommands-conflicts"></xref> per
      le istruzioni su come risolvere i conflitti.
    </para>
  </section>
  <section id="sn-cvs-preparation">
    <title>Preparazione all'uso di CVS</title>
    <indexterm>
      <primary>cvs</primary>
      <secondary>preparazione all'uso</secondary>
    </indexterm>
    <para>
      Prima di usare <application>CVS</application>, hai bisogno di stabilire
      un account con il <application>CVS</application> server. Dopo
      aver ottenuto un account, non dovrai pi?? fare nuovamente queste
      cose.
    </para>

    <section id="sn-cvs-rpm-check">
      <title>E' CVS installato sul tuo sitema</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>installazione RPM</secondary>
      </indexterm>
      <para>
        Devi aver installato il pacchetto <application>CVS</application>
        <abbrev>RPM</abbrev>. Verifica la sua presenza
        digitando il comando:
      </para>
<screen><prompt>$ </prompt><command>rpm -q cvs</command></screen>
      <para>
        e vedi un output simile a
        <computeroutput>cvs-1.11.19-1</computeroutput>, allora il pacchetto
        ?? installato. Un messaggio simile a <computeroutput>package cvs
        is not installed</computeroutput> vuol dire che devi instllare il
        pacchetto <application>cvs</application> prima di continuare. Se
        non sai come fare, consulta il tuo amministratore di sistema
        che potr?? intallarlo per te.
      </para>
    </section>

    <section id="sn-cvs-generate-keys">
      <title>Generazione dell chiavi SSH</title>
      <indexterm>
        <primary>OpenSSH</primary>
        <secondary>chiavi di autorizzazione</secondary>
      </indexterm>
      <para>
        Il <application>CVS</application> server usa chiavi
        <application>SSH</application> Protocol 2 per autenticare
        gli utenti. Cos??, devi generare un paio di chiavi prima di richiedere
        un account <application>CVS</application>. Se hai gi??
        una chiave <application>SSH</application> <abbrev>DSA</abbrev>,
        puoi saltare questo passaggio.
      </para>
      <tip>
        <title>Tip</title>
        <para>
          Hai gi?? una chiave <abbrev>DSA</abbrev> se hai il
          file <filename>~/.ssh/id_dsa.pub</filename> sul sistema.
        </para>
        <para>
          Se la tua chiave <abbrev>DSA</abbrev> esistente non richiede una
          <wordasword>passphrase</wordasword>, sei fortemente incoraggiato a
          generrne una che richieda una passphrase.
        </para>
      </tip>
      <para>
        Usa i seguenti passi per generare una chiave <abbrev>DSA</abbrev>
        usata da <application>SSH</application> Protocol 2. E'
	necessaria per un account <application>CVS</application> su
        <computeroutput>cvs.fedora.redhat.com</computeroutput>.
      </para>
      <orderedlist>
        <indexterm>
          <primary>OpenSSH</primary>
          <secondary><command>ssh-keygen</command>
          </secondary>
        </indexterm>
        <indexterm>
          <primary><command>ssh-keygen</command>
          </primary>
        </indexterm>
        <listitem>
          <para>
            Per generare una chiave
            <acronym>DSA</acronym>
            per funzionare con il protocollo versione 2.0, allo shell prompt,
            digita il comando:
          </para>
<screen><prompt>$ </prompt><command>ssh-keygen -t dsa</command></screen>
          <para>
            Accetta la posizione predefinita per la locazione del file
            <filename>~/.ssh/id_dsa</filename>. Sei fortemente incoraggiato all'urgenza
            di definire ed usare una <firstterm>passphrase</firstterm> per
            aumentare la sicurezza della tua chiave. Immetti una passphrase
            differente dalla password del tuo password e confermala
            reinserendola nuovamente.
          </para>
        </listitem>
        <listitem>
          <para>
            Copia la nuova chiave nel file corretto digitando i
            seguenti comandi allo shell prompt.
          </para>
<screen><prompt>$ </prompt><command>cat ~/.ssh/id_dsa.pub&gt;&gt;~/.ssh/authorized_keys</command></screen>
          <note>
            <para>
              Controlla con attenzione questo comando prima di premere il tasto
              <guibutton>ENTER</guibutton>.
              Se <filename>~/.ssh/authorized_keys</filename>
              esiste gi??, i contenuti di
              <filename>~/.ssh/id_dsa.pub</filename> verranno appesi alla
              fine del file <filename>~/.ssh/authorized_keys</filename>.
            </para>
          </note>
        </listitem>
        <listitem>
          <para>
            Cambia i permessi della tua directory <filename>~/.ssh</filename>
            e delle tue chiavi con i comandi:
          </para>
<screen><prompt>$ </prompt><command>chmod 755 ~/.ssh</command>
<prompt>$ </prompt><command>chmod 644 ~/.ssh/authorized_keys</command></screen>
        </listitem>
      </orderedlist>
      <tip>
        <title>Tip</title>
        <para>
          Puoi far si che il sistema ricordi la passphrase cos?? da
          non doverla digitare ogni volta che accedi al
          <application>CVS</application> server. Fa riferimento alla
          documentazione del programma <application>ssh-add</application>.
        </para>
      </tip>
    </section>
  </section>
  <section id="sn-cvs-config">
    <title>Configurazione per l'accesso CVS</title>
    <indexterm>
      <primary>cvs</primary>
      <secondary>configurazione per l'accesso</secondary>
    </indexterm>
    <indexterm>
      <primary>cvs</primary>
      <secondary>CVSROOT</secondary>
    </indexterm>
    <indexterm>
      <primary>cvs</primary>
      <secondary>CVS_RSH</secondary>
    </indexterm>
    <indexterm>
      <primary>CVSROOT</primary>
    </indexterm>
    <indexterm>
      <primary>CVS_RSH</primary>
    </indexterm>
    <indexterm>
      <primary>cvs</primary>
      <secondary><filename>.cvsrc</filename>
      </secondary>
    </indexterm>
    <indexterm>
      <primary><filename>.cvsrc</filename>
      </primary>
    </indexterm>
    <section id="sn-cvs-config-cvsrc">
      <title>Evitare digitazioni ripetitive</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>evitare digitazioni ripetitive</secondary>
      </indexterm>
      <para>
        Molti comandi <application>CVS</application> hanno bisogno di
        certe opzioni per operare in modo consistente. Invece di
        digitarle ogni volta che il comando ?? usato, puoi salvare gli
        switches in un file che <application>CVS</application> legger??
        prima di eseguire la linea di comando.
      </para>

      <para>
        Crea un file chiamato <filename>~/.cvsrc</filename> nella tua home
        directory. Dovr?? contenere i seguenti comandi, uno per
        riga:
<screen><computeroutput>cvs -z3
diff -uNp
rdiff -uNp
update -dP</computeroutput></screen>
      </para>
    </section>

    <section id="sn-cvs-config-anon">
      <title>Configurare un accesso CVS Read-Only</title>
      <indexterm>
        <primary>cvs</primary>
	<secondary>configurare un accesso Read-Only</secondary>
      </indexterm>
      <indexterm>
        <primary>cvs</primary>
        <secondary>accesso anonimo</secondary>
      </indexterm>
      <para>
        If your goal is to download the various &FC; documents and to
        render them on your system, you only need read-only access to
        the <application>CVS</application> repository. Follow the
        instructions in this section and then skip directly to
        <xref linkend="sn-cvs-cvscommands-co"/>.
      </para>

      <para>
        Change directories to where you want your files from
        <application>CVS</application> to be located, and execute the
        following commands:
      </para>
<screen><prompt>$ </prompt><command>export CVSROOT=:pserver:cvs.fedora.redhat.com:/cvs/docs</command>
<prompt>$ </prompt><command>cvs login</command>
<prompt>$ </prompt><command>cvs checkout docs-common</command> <replaceable>module-name</replaceable>
<prompt>$ </prompt><command>cvs checkout</command> <replaceable>module-name</replaceable>
<prompt>$ </prompt><command>cd</command> <replaceable>module-name</replaceable></screen>
      <para>
        Once you have checked the module out, it doesn't matter what
        your
        <envar>CVSROOT</envar>
        is set to because it is stored in the file
        <filename>CVS/Root</filename> for each directory in your local
        repository. As long as your current working directory has a
        <filename>CVS/</filename> directory, the
        <application>CVS</application> program will automatically locate
        the &FC; repository.
      </para>
    </section>

    <section id="sn-cvs-config-author">
      <title>Configuring Read/Write CVS Access</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>configuring read/write access</secondary>
      </indexterm>
      <indexterm>
        <primary>cvs</primary>
        <secondary>configuring access for authors</secondary>
      </indexterm>
      <para>
        To author a new document or to change an existing one, you must
        obtain full read/write access to the &FC; Docs
        <application>CVS</application> repository. For the full details
        on this process, refer to the
        <ulink url="http://fedoraproject.org/wiki/DocsProject/NewWriters"><filename>http://fedoraproject.org/wiki/DocsProject/NewWriters</filename>
        </ulink> web site. Below is a summary:
      </para>

      <itemizedlist>
        <listitem>
          <para>
            Subscribe to the
            <ulink url="https://listman.redhat.com/mailman/listinfo/fedora-docs-list"><filename>fedora-docs-list</filename>
            </ulink>, which is the main forum for the project.
          </para>
        </listitem>
        <listitem>
          <para>
            Generate a GNU Privacy Guard (<abbrev>GPG</abbrev>) key to
            identify yourself to the project.
          </para>
        </listitem>
        <listitem>
          <para>
            Register for a
            <ulink url="http://bugzilla.redhat.com/"><filename>Bugzilla</filename>
            </ulink> account, if you do not have one already.
            <filename>Bugzilla</filename> is how we keep track of bugs,
            changes and projects.
          </para>
        </listitem>
        <listitem>
          <para>
            Post a
            <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">self
            introduction</ulink> to the list.
          </para>
        </listitem>
      </itemizedlist>

      <para>
        After your
        <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">self
        introduction</ulink> has been approved your
        <application>CVS</application> access will be granted.
      </para>

      <para>
        Every author, and that includes you once your self introduction
        has been received, has a unique
        <envar>$CVSROOT</envar>
        to access the <application>CVS</application> repository:
      </para>
<screen><prompt>$ </prompt><command>export CVSROOT=:ext:</command><replaceable>yourname</replaceable><command>@cvs.fedora.redhat.com:/cvs/docs</command>
<prompt>$ </prompt><command>export CVS_RSH=/usr/bin/ssh</command></screen>
      <para>
        With the
        <envar>$CVSROOT</envar>
        and
        <envar>$CVS_RSH</envar>
        environment variables in place, you can access the repository:
      </para>
<screen><prompt>$ </prompt><command>cvs co -c</command></screen>
      <para>
        You will be asked for the passphrase for your
        <application>SSH</application> key. Press
        <guibutton>ENTER</guibutton>
        and you should receive a list of modules already in the
        repository.
      </para>
    </section>
  </section>
  <section id="sn-cvs-cvscommands">
    <title>Basic CVS Commands</title>
    <indexterm>
      <primary>cvs</primary>
      <secondary>commands</secondary>
    </indexterm>
    <para>
      After configuring your system to work with CVS, checkout the
      modules you will be working on.
    </para>
    <tip>
      <title>Tip</title>
      <para>
        To see if you need a correctly-set
        <envar>$CVSROOT</envar>
        variable, or the <option>-m </option>
        <replaceable>repository</replaceable> command line switch, see
        if you have a <filename>CVS/</filename> subdirectory in your
        working directory.
      </para>
      <para>
        If you have a <filename>CVS/</filename> directory,
        <application>CVS</application> ignores any
        <envar>$CVSROOT</envar>
        or <option>-m</option> command line switch.
      </para>
    </tip>
    <section id="sn-cvs-cvscommands-co">
      <title>Checking Out Modules</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>checking out modules</secondary>
      </indexterm>
      <para>
        You only need to checkout a module once. After a local copy of
        the module is on your system, it is on your system.
      </para>

      <para>
        To checkout a module, use the following command:
      </para>
<screen><prompt>$ </prompt><command>cvs co</command>  <replaceable>&lt;module-name&gt;</replaceable></screen>
      <para>
        For example, to checkout the
        <computeroutput>example-tutorial</computeroutput> module, change
        to your work directory, and execute the following command:
      </para>
<screen><prompt>$ </prompt><command>cvs co example-tutorial</command></screen>
      <para>
        A directory called <filename>example-tutorial/</filename> is
        created in the current directory.
      </para>

      <para>
        If a branch name is not specified when checking out a module, it
        is referred to as the <firstterm>HEAD</firstterm> of the
        <application>CVS</application> module.
      </para>

      <section id="sn-cvs-cvscommands-co-branch">
        <title>Checking Out Branches of Modules</title>
        <indexterm>
          <primary>cvs</primary>
          <secondary>check out modules</secondary>
          <tertiary>checking out branches</tertiary>
        </indexterm>
        <para>
          Think of a <application>CVS</application> branch as a version
          of the files for a particular version of a manual or package.
        </para>

        <para>
          To checkout a branch of a module, use the following command:
        </para>
<screen><prompt>$ </prompt><command>cvs co</command> <option>-d</option>  <replaceable>&lt;directory&gt;</replaceable> <option>-r</option>  <replaceable>&lt;branchname&gt;</replaceable> <replaceable>&lt;module-name&gt;</replaceable></screen>
        <para>
          A directory named <replaceable>&lt;directory&gt;</replaceable>
          is created, and the files for the
          <replaceable>&lt;branchname&gt;</replaceable> branch of the
          <replaceable>&lt;module-name&gt;</replaceable> module are
          copied in the directory.
        </para>

        <para>
          For example, to checkout a branch named BRANCH-VERSION-1.2
          from the <computeroutput>mymodule</computeroutput> module, use
          the command:
        </para>
<screen><prompt>$ </prompt><command>cvs co -d mymodule-1.2 -r BRANCH-VERSION-1.2 mymodule</command></screen>
        <para>
          The BRANCH-VERSION-1.2 branch of the module is checked out in
          the <filename>mymodule-1.2</filename> directory on your
          system.
        </para>

        <para>
          To determine which branches and tags exist for a file, use the
          command:
        </para>
<screen><prompt>$ </prompt><command>cvs status</command> <option>-v</option> <replaceable>&lt;filename&gt;</replaceable></screen>
        <para>
          For example, the status of the file
          <filename>foo.sgml</filename> is as follows:
        </para>
<screen>
<computeroutput>
===================================================================
File: foo.sgml    Status: Up-to-date

   Working revision:    1.47
   Repository revision: 1.47    /cvs/docs/custom-guide/rhl-cg-en.sgml,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)

   Existing Tags:
        BRANCH-VERSION-1.2              (branch: 1.25.2)
</computeroutput>
</screen>
        <para>
          Only tags marked as branches in the second column under the
          <computeroutput>Existing Tags</computeroutput> section can be
          checked out as a branch.
        </para>
      </section>
    </section>

    <section id="sn-cvs-cvscommands-up">
      <title>Updating Files</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>updating files</secondary>
      </indexterm>
      <para>
        To retrieve the latest versions of the files in a module, change
        to the directory that contains the files for the module and
        execute the command:
      </para>
<screen><command>cvs update</command></screen>
      <para>
        The latest versions of all the files in the module are
        downloaded into your local copy. If you notice a file conflict,
        refer to <xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
      </para>
    </section>

    <section id="sn-cvs-cvscommands-commit">
      <title>Committing Files</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>committing files</secondary>
      </indexterm>
      <para>
        After modifying files in your local version of a module, commit
        them to save the changes on the <application>CVS</application>
        server:
      </para>
<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> &quot;<replaceable>some log message</replaceable>&quot; <replaceable>filename</replaceable></screen>
      <note>
        <para>
          If you would prefer to write your log message with your
          favorite text editor, as defined by the $VISUAL or the $EDITOR
          environment variable, just omit the <userinput>-m &quot;some
          log message&quot;</userinput>. The buffer will already contain
          comments describing the change; you do not need to delete them
          as you enter your own text.
        </para>
      </note>

      <para>
        The log message should be as descriptive as possible so that you
        and anyone else working on the module understands what changed.
        Using a log message such as <userinput>updated some
        files</userinput> does not accurately describe what has changed
        and will not help you in the future. If you are correcting a
        bug, use the <application>Bugzilla</application> reference.
      </para>

      <para>
        The <replaceable>&lt;filename&gt;</replaceable> can be one
        filename, a series of filenames separated by spaces, or a group
        of filenames specified using wildcards such as
        <filename>*.png</filename> or <filename>foo-*.sgml</filename>.
      </para>

      <para>
        If no filename or group of filenames is specified in the
        <command>commit</command> command, all outstanding changes of
        any kind are committed to the server. The command is recursive
        and will include changes in any subdirectories of the module.
        Use caution when issuing the <command>commit</command> command
        without any filenames because you might not remember exactly
        what files changed.
      </para>

      <para>
        If you notice a file conflict, refer to
        <xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
      </para>
    </section>

    <section id="sn-cvs-cvscommands-add">
      <title>Adding Files</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>adding files</secondary>
      </indexterm>
      <para>
        To add a file to a module, create the file in your local copy
        then execute the following command:
      </para>
<screen><prompt>$ </prompt><command>cvs add</command>  <replaceable>file-to-add</replaceable></screen>
      <para>
        After adding the file, you must <command>commit</command> the
        <command>add</command> to copy it to the server:
      </para>
<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> &quot;<replaceable>some log message</replaceable>&quot; <replaceable>file-to-add</replaceable></screen>
    </section>

    <section id="sn-cvs-cvscommands-admin">
      <title>Managing Binary Files</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>binary files</secondary>
      </indexterm>
      <para>
        The most commonly-archived files are simple text files but
        sometimes binary files are also archived. The
        <application>cvs</application> program recognizes most common
        filename extentions such as <filename>.png</filename> or
        <filename>.jpg</filename>, so <application>cvs</application>
        usually &quot;does the right thing&quot;.
      </para>

      <para>
        When a copy of a file is checked out of the repository,
        <application>cvs</application> scans it for special keywords,
        such as &quot;<computeroutput>$id:$</computeroutput>&quot; and
        replaces the string with a generated value, such as the file
        version number.
      </para>

      <para>
        This keyword substitution usually corrupts binary files, so it
        must be turned off if <application>cvs</application> does not
        recognize your file as binary. To mark your file as being
        binary, and thus needing the keyword expansion turned off, use
        the command:
      </para>
<screen width="60"><prompt>$ </prompt><command>cvs</command> <option>admin</option> <option>-kk</option> <replaceable>filename</replaceable></screen>
      <para>
        Note that the file must already be checked in to the
        <abbrev>CVS</abbrev> repository before the
        <option>admin</option> command can be used. This is OK, since
        the keyword expansion is done as the file is checked out and
        copied to the local directory, not when the file is committed to
        the repository.
      </para>
      <tip>
        <title>Recovering a binary file</title>
        <para>
          If you check a binary file into the repository and then find
          it corrupted when it is checked out, do not panic. Simply use
          the <option>admin</option> command as described above, delete
          your local file copy, and check it out again.
        </para>
      </tip>
    </section>

    <section id="sn-cvs-cvscommands-rm">
      <title>Removing Files</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>removing files</secondary>
      </indexterm>
      <para>
        If a file is no longer needed in the module, use the
        <command>remove</command> command to remove it from your local
        copy and then <command>commit</command> the removal to the
        server. Even though the file is removed from current version of
        the module, an archived copy is still kept on the server and can
        be retrieved at any time with the <command>add</command>
        command.
      </para>
<screen><prompt>$ </prompt><command>cvs rm -f</command>  <replaceable>file-to-remove</replaceable></screen>
      <para>
        After removing the file, you must <command>commit</command> the
        removal:
      </para>
<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option>&quot;<replaceable>some log message</replaceable>&quot; <replaceable>file-to-remove</replaceable></screen>
      <para>
        You can not use wildcards in the <command>commit</command>
        command to identify removed files. They must be specified with a
        exact filename.
      </para>

      <para>
        If you need to rename a file, it is best to rename the file on
        the <application>CVS</application> server so that the history of
        the file is preserved. If you need to rename a file, send an
        email to
        <ulink url="mailto:cvsdocs-administrator at fedora.redhat.com"><filename>cvsdocs-administrator at fedora.redhat.com</filename>
        </ulink> asking to have the file renamed.
      </para>
    </section>

    <section id="sn-cvs-cvscommands-status">
      <title>Status of Files</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>status of files</secondary>
      </indexterm>
      <para>
        Sometimes it is necessary to view the
        <firstterm>status</firstterm> of a file in a
        <application>CVS</application> module. To view the status of a
        file, use the command:
      </para>
<screen><prompt>$ </prompt><command>cvs status</command>  <replaceable>filename</replaceable></screen>
      <para>
        The status report of a repository file is as follows:
      </para>

      <variablelist>
        <varlistentry>
          <term><computeroutput>Up-to-date</computeroutput></term>
          <listitem>
            <para>
              Your revision of the file is identical to the latest
              revision on the <application>CVS</application> server.
            </para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term><computeroutput>Locally Modified</computeroutput></term>
          <listitem>
            <para>
              You have updated to the latest revision from the server,
              but then you modified the file on your system.
            </para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term><computeroutput>Locally Added</computeroutput></term>
          <listitem>
            <para>
              You added the file with the <command>cvs add</command>
              command but have not yet committed the addition of the
              file.
            </para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term><computeroutput>Locally Removed</computeroutput></term>
          <listitem>
            <para>
              You removed the file with the <command>cvs
              remove</command> command but have not yet committed the
              removal.
            </para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term><computeroutput>Needs Checkout</computeroutput></term>
          <listitem>
            <para>
              A newer version of the file is on the server and needs to
              be retrieved. Even though the status includes the word
              checkout, it really means that you need to update your
              files with the <command>cvs update</command> command.
            </para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term><computeroutput>Needs Patch</computeroutput></term>
          <listitem>
            <para>
              The revision in your local checkout needs a patch to be
              the latest revision from the server. Issue the
              <command>cvs update</command> command to resolve.
            </para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term><computeroutput>Needs Merge</computeroutput></term>
          <listitem>
            <para>
              A newer revision exists on the server and your local
              version contains modification not yet committed. This
              status usually occurs if you don't have the latest
              revision of the file and edit it anyway.
            </para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term><computeroutput>File had conflicts on merge</computeroutput></term>
          <listitem>
            <para>
              Similar to <computeroutput>Needs Merge</computeroutput>,
              except when you tried to issue the <command>cvs
              update</command> command, the differences could not be
              resolved automatically. Refer to
              <xref linkend="sn-cvs-cvscommands-conflicts"></xref> for
              more information on resolving conflicts.
            </para>
          </listitem>
        </varlistentry>

        <varlistentry>
          <term><computeroutput>Unknown</computeroutput></term>
          <listitem>
            <para>
              The <application>CVS</application> server does not know
              anything about this file. It has neither been added nor
              removed locally and has never been committed to the
              server. This status usually occurs for files you should
              not commit to <application>CVS</application> such as
              <filename>generated-index.sgml</filename> or for files
              that you want to add to the repository but have not yet
              issued the <command>cvs add</command> command.
            </para>
          </listitem>
        </varlistentry>
      </variablelist>
    </section>

    <section id="sn-cvs-cvscommands-conflicts">
      <title>Resolving Conflicts</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>resolving conflicts</secondary>
      </indexterm>
      <para>
        If you modify a file and the same region is modified by someone
        else and committed first, you will probably see a message
        similar to the following when committing the file or updating
        your local copy of the module:
      </para>
<screen>
<computeroutput>
RCS file: /cvs/docs/module-name/filename.sgml,v
retrieving revision 1.12
retrieving revision 1.13
Merging differences between 1.12 and 1.13 into filename.sgml
rcsmerge: warning: conflicts during merge
cvs server: conflicts found in filename.sgml
C filename.sgml
</computeroutput>
</screen>
      <para>
        To resolve the conflict, open the file, search for
        <computeroutput>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</computeroutput>
        and determine which version of the content is correct. For
        example:
      </para>
<screen>
<computeroutput>
&lt;para&gt;
Some sentence.
&lt;&lt;&lt;&lt;&lt;&lt;&lt; filename.sgml
A sentence that was changed in the working copy.
=======
A same sentence that was changed differently and committed.
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1.13
&lt;/para&gt;
</computeroutput>
</screen>
      <para>
        The content between the
        <computeroutput>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</computeroutput>,
        and the <computeroutput>=======</computeroutput> is the content
        from your working copy. The content between the
        <computeroutput>=======</computeroutput> and the
        <computeroutput>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</computeroutput> is
        the content from the server.
      </para>

      <para>
        Resolve the conflict by editing your copy, and commit the file.
      </para>
    </section>

    <section id="sn-cvs-cvscommands-summary">
      <title>Summary</title>
      <indexterm>
        <primary>cvs</primary>
        <secondary>commands</secondary>
        <tertiary>summary of</tertiary>
      </indexterm>
      <para>
        All commands assume you are in the proper directory for the
        <application>CVS</application> module.
      </para>
      <table frame="all" id="tb-cvs-basic-commands">
        <title>Basic CVS Commands</title>
        <tgroup cols="2">
          <colspec colnum="1" colname="shortcut" colwidth="30"/>
          <colspec colnum="2" colname="description" colwidth="60"/>
          <thead>
            <row>
              <entry>Command</entry>
              <entry>Description</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry><command>cvs checkout
        <replaceable>&lt;module-name&gt;</replaceable></command>
      or <command>cvs co <replaceable>&lt;module-name&gt;</replaceable></command>
              </entry>
              <entry>Creates a directory called
      <replaceable>&lt;module-name&gt;</replaceable> with the contents of the
      module in the directory</entry>
            </row>
            <row>
              <entry><command>cvs co -d <replaceable>&lt;directory&gt;</replaceable> -r <replaceable>&lt;branchname&gt;</replaceable><replaceable>&lt;module-name&gt;</replaceable></command>
              </entry>
              <entry>Creates the <replaceable>&lt;directory&gt;</replaceable> directory
      with the contents of the <replaceable>&lt;branchname&gt;</replaceable>
      branch of the <replaceable>&lt;module-name&gt;</replaceable> module</entry>
            </row>
            <row>
              <entry><command>cvs update</command> or <command>cvs up</command>
              </entry>
              <entry>Update your files with the latest files from the CVS server</entry>
            </row>
            <row>
              <entry><command>cvs add <replaceable>&lt;filename&gt;</replaceable></command>
              </entry>
              <entry>Add a new file "filename" to the CVS server</entry>
            </row>
            <row>
              <entry><command>cvs commit -m "My message"
        <replaceable>&lt;filename&gt;</replaceable></command>
              </entry>
              <entry>Update file <replaceable>&lt;filename&gt;</replaceable> with the
      latest copy from your computer</entry>
            </row>
            <row>
              <entry><command>cvs log <replaceable>&lt;filename&gt;</replaceable></command>
              </entry>
              <entry>View the commit messages for the file <replaceable>&lt;filename&gt;</replaceable>
              </entry>
            </row>
            <row>
              <entry><command>cvs status <replaceable>&lt;filename&gt;</replaceable></command>
              </entry>
              <entry>View status of the file, such as <computeroutput>Locally
        Modified</computeroutput>
              </entry>
            </row>
            <row>
              <entry><command>cvs status -v <replaceable>&lt;filename&gt;</replaceable></command>
              </entry>
              <entry>View existing tags and branches for file</entry>
            </row>
            <row>
              <entry><command>cvs diff <replaceable>&lt;filename&gt;</replaceable></command>
              </entry>
              <entry>Show diff of the working copy of the file and the latest
      version of the file for the branch</entry>
            </row>
            <row>
              <entry><command>cvs diff -r1.1 -r1.2 <replaceable>&lt;filename&gt;</replaceable></command>
              </entry>
              <entry>Show diff of version 1.1 and 1.2 for file</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
      <para>
        For more information, read the CVS manual available on your
        system at
        <filename>/usr/share/doc/cvs-<replaceable>&lt;version-number&gt;</replaceable>/cvs.ps</filename>
        (the CVS version might vary) and visit the CVS webpage available
        at
        <ulink url="http://www.cvshome.org/">http://www.cvshome.org/</ulink>.
      </para>
      <tip>
        <title>Tip</title>
        <para>
          Since <application>CVS</application> is using
          <application>ssh</application> to connect to the
          <application>CVS</application> server, you will be prompted
          your password before performing your
          <application>CVS</application> request. If you want to
          configure your machine so that you do not have to enter a
          password, refer to the
          <ulink url="http://redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-openssh-client-config.html"><citetitle>&RH;
          Linux 9 Customization Guide</citetitle> </ulink> for details
          about using <command>ssh-agent</command>.
        </para>
      </tip>
    </section>
  </section>
</chapter>



From fedora-docs-commits at redhat.com  Sat Nov 19 20:23:16 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:23:16 -0500
Subject: docs-common/common deprecatednotice-it.xml,NONE,1.1
Message-ID: <200511192023.jAJKNGRW013183@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13167/docs-common/common

Added Files:
	deprecatednotice-it.xml 
Log Message:



--- NEW FILE deprecatednotice-it.xml ---
<note>
  <title>DOCUMENTO DEPRECATO</title>  
  <para>
    Questo documento non ?? pi?? supportato dal &FDP;.  Uno o pi?? delle
    seguenti situazioni pu?? essere accaduta:
  </para>

  <itemizedlist>
    <listitem>
      <para>
	Cambiamenti in Fedora possono aver reso questo documento inaccurate.
      </para>
    </listitem>
    <listitem>
      <para>
	E' disponibile un documento molto pi?? rilevante.
      </para>
    </listitem>
    <listitem>
      <para>
	Questo documento potrebbe essere stato incluso in un documento differente.
      </para>
    </listitem>
  </itemizedlist>

  <para>
    Fa riferimento alla storia delle revisioni per maggiori informazioni.
  </para>
</note>



From fedora-docs-commits at redhat.com  Sat Nov 19 20:23:30 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:23:30 -0500
Subject: docs-common/common draftnotice-it.xml,NONE,1.1
Message-ID: <200511192023.jAJKNUOW013205@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13189/docs-common/common

Added Files:
	draftnotice-it.xml 
Log Message:



--- NEW FILE draftnotice-it.xml ---
<note>
  <title>DRAFT</title>  
  <para>
    Questa ?? una versione draft del documento. E' soggetta a cambiamento in qualsiasi momento
    e potrebbe non esserne ancora stata provata l'accuratezza tecnica. Se trovi qualsiasi
    errore, sei pregato di comunicarli via Bugzilla sul bug &BUG-NUM;.
  </para>
</note>



From fedora-docs-commits at redhat.com  Sat Nov 19 20:23:45 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:23:45 -0500
Subject: docs-common/common fedora-entities-it.xml,NONE,1.1
Message-ID: <200511192023.jAJKNjTq013227@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13211/docs-common/common

Added Files:
	fedora-entities-it.xml 
Log Message:



***** Error reading new file: [Errno 2] No such file or directory: 'fedora-entities-it.xml'



From fedora-docs-commits at redhat.com  Sat Nov 19 20:24:00 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:24:00 -0500
Subject: docs-common/common legacynotice-it.xml,NONE,1.1
Message-ID: <200511192024.jAJKO02J013249@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13233/docs-common/common

Added Files:
	legacynotice-it.xml 
Log Message:



--- NEW FILE legacynotice-it.xml ---
<note>
  <title>DOCUMENTO LEGACY</title>  
  <para>
    Questo documento ?? relativo a una versione di &FC; che non ?? pi??
    supportata dal &FP;.  Cambiamenti nelle ultime versioni di &FC; possono aver reso questo
    documento inaccurato.  Sei pregato di controllare il sito web di &FDP; su
    &FDPDOCS-URL; per la versione attuale prima di continuare a leggere questo
    documento.
  </para>

  <para>
    Questa versione del documento non sar?? cambiato o emendato, eccetto
    per la correzione di errori che possono indurre in perdita di dati o a debolezze nel sistema
    di sicurezza.  Se credi di aver trovato un errore, sei pregato di
    riferirlo mediante &BZ; sul bug &BUG-NUM;.
  </para>
</note>



From fedora-docs-commits at redhat.com  Sat Nov 19 20:24:15 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:24:15 -0500
Subject: docs-common/common legalnotice-content-it.xml,NONE,1.1
Message-ID: <200511192024.jAJKOFVF013272@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13256/docs-common/common

Added Files:
	legalnotice-content-it.xml 
Log Message:



--- NEW FILE legalnotice-content-it.xml ---

  <para>
    Sono garatiti i permessi di copiare, distribuire, e/o modificare questo documento sotto
    i termini della GNU Free Documentation License, Versione 1.2 o qualsiasi successiva
    versione pubblicata dalla Free Software Foundation; con nessuna Invariant
    Sections, nessuna Front-Cover Texts, e nessuna Back-Cover Texts.  Una copia della
    licenza ?? disponibile su <ulink
    url="http://www.gnu.org/licenses/fdl.html">http://www.gnu.org/licenses/fdl.html</ulink>.
  </para>

  <para>
    Questo documento pu?? essere copiato e distribuito in qualsiasi media, sia
    commerciale che non commerciale, premettendo che la GNU Free Documentation
    License (FDL), le note sul copyright, e le note di licenza che dicono che la GNU
    FDL che si applicano al documento sono riprodotte in tutte le copie, e che tu non
    abbia aggiunto nessun altra condizione di sorta a quelle della GNU FDL.
  </para>

  <para>
    Garrett LeSage hanno creato le grafiche di ammonizione (note, tip, important,
    caution, e warning).
    Tommy Reynolds <email>Tommy.Reynolds at MegaCoder.com</email> ha creato la grafica di callout.
    Tutte queste possono essere liberamente distribuite con la documentazione
    prodotta per il &PROJECT;.
    </para>

  <para>
    &BOOKID;
  </para>

  <para>
    &RH; ed il logo &RH; "Shadow Man" sono marchi registrati di
    &FORMAL-RHI; negli Stati United ed in altri paesi.
  </para>

<!-- Changing to match RHEL usage, changes are drawn directly from existing -->
<!-- lawyer-approved changes within the RHEL legalnotice:
  <para>
    &RH;, &RH; Network, the &RH; "Shadow Man" logo, RPM, Maximum RPM, the RPM logo, Linux
    Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts,
    Rawhide and all &RH;-based trademarks and logos are trademarks or registered
    trademarks of &FORMAL-RHI; in the United States and other countries.
  </para>

  <para>
    Linux is a registered trademark of Linus Torvalds.
  </para>

  <para>
    Motif and UNIX are registered trademarks of The Open Group.
  </para>

  <para>
    Intel and Pentium are registered trademarks of Intel Corporation. Itanium
    and Celeron are trademarks of Intel Corporation.
  </para>

  <para>
    AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of Advanced Micro
    Devices, Inc.
  </para>

  <para>
    Windows is a registered trademark of Microsoft Corporation.
  </para>

  <para>
    SSH and Secure Shell are trademarks of SSH Communications Security, Inc.
  </para>

  <para>
    FireWire is a trademark of Apple Computer Corporation.
  </para>
-->
  <para>
    Tutti gli altri marchi e copyrights a cui si fa riferimento sono propriet?? dei
    rispettivi proprietari.
  </para>



From fedora-docs-commits at redhat.com  Sat Nov 19 20:24:30 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:24:30 -0500
Subject: docs-common/common legalnotice-it.xml,NONE,1.1
Message-ID: <200511192024.jAJKOU66013294@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13278/docs-common/common

Added Files:
	legalnotice-it.xml 
Log Message:



--- NEW FILE legalnotice-it.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "This header makes editing XML easier" >

]>
-->
<legalnotice id="legalnotice">
&LEGALNOTICE-CONTENT;
</legalnotice>



From fedora-docs-commits at redhat.com  Sat Nov 19 20:24:44 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:24:44 -0500
Subject: docs-common/common legalnotice-relnotes-it.xml,NONE,1.1
Message-ID: <200511192024.jAJKOiNu013316@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13300/docs-common/common

Added Files:
	legalnotice-relnotes-it.xml 
Log Message:



--- NEW FILE legalnotice-relnotes-it.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "This header makes editing XML easier" >

]>
-->

<!-- 

  Use this legalnotice for no-chunks/single-page HTML output.  It is an optional
  usage to move the bulk of the legalnotice to another location in the document.

  If you use this legalnotice, you must include a call to the
  LEGALNOTICE-SECTION entity, or include a similar <section> in your document.
  The call to LEGALNOTICE-SECTION must happen where a <section> is otherwise
  allowed.  One good location is immediately following an introduction.

  -->

<legalnotice id="legalnotice">
  <para>
    Questo documento ?? rilasciato sotto i termini della GNU Free Documentation
    License.  Per maggiori dettagli, leggi le note legali complete su <xref
    linkend="sn-legalnotice" />.
  </para>
  <tip>
    <title>Le ultime note di rilascio sul Web</title>
    <para>
      Queste note di rilascio possono essere aggiornate.  Visita <ulink
	url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>
      per vedere le ultime note di rilascio per &DISTRO; &DISTROVER;.
    </para>
  </tip>
</legalnotice>



From fedora-docs-commits at redhat.com  Sat Nov 19 20:25:02 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:25:02 -0500
Subject: docs-common/common legalnotice-section-it.xml,NONE,1.1
Message-ID: <200511192025.jAJKP2WQ013338@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13322/docs-common/common

Added Files:
	legalnotice-section-it.xml 
Log Message:



--- NEW FILE legalnotice-section-it.xml ---
<!-- 

  Use this legalnotice for no-chunks/single-page HTML output.  It is an optional
  usage to move the bulk of the legalnotice to another location in the document.

  If you use this legalnotice, you must include a call to the
  LEGALNOTICE-NOCHUNKS or LEGALNOTICE-RELNOTES.  This gets the legal material in
  the proper <legalnotice /> container.SECTION entity, or include a similar <section> in your document.
  The call to LEGALNOTICE-SECTION must happen where a <section> is otherwise
  allowed.  One good location is immediately following an introduction.

  -->
  <section id="sn-legalnotice">
    <title>Note legali</title>
    &LEGALNOTICE-CONTENT;
  </section>



From fedora-docs-commits at redhat.com  Sat Nov 19 20:25:17 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:25:17 -0500
Subject: docs-common/common obsoletenotice-it.xml,NONE,1.1
Message-ID: <200511192025.jAJKPHfn013360@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13344/docs-common/common

Added Files:
	obsoletenotice-it.xml 
Log Message:



--- NEW FILE obsoletenotice-it.xml ---
<note>
  <title>DOCUMENTO OBSOLETO</title>  
  <para>
    Questo documento ?? relativo a una versione di &FC; che non ?? pi??
    supportata.  Cambiamenti nelle ultime versioni di &FC; possono aver reso questo
    documento inaccurato.  Sei pregato di controllare il sito web di &FDP; su
    &FDPDOCS-URL; per la versione attuale prima di continuare a leggere questo
    documento.
  </para>

  <para>
    Questa versione del documento non sar?? cambiato o emendato.
  </para>
</note>



From fedora-docs-commits at redhat.com  Sat Nov 19 20:38:16 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 15:38:16 -0500
Subject: docs-common/common fedora-entities-it.ent,NONE,1.1
Message-ID: <200511192038.jAJKcGxU013399@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13383/docs-common/common

Added Files:
	fedora-entities-it.ent 
Log Message:



***** Error reading new file: [Errno 2] No such file or directory: 'fedora-entities-it.ent'



From fedora-docs-commits at redhat.com  Sat Nov 19 21:06:29 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 16:06:29 -0500
Subject: release-notes RELEASE-NOTES-it.xml,1.2,1.3
Message-ID: <200511192106.jAJL6TWh014984@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14965/release-notes

Modified Files:
	RELEASE-NOTES-it.xml 
Log Message:



Index: RELEASE-NOTES-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- RELEASE-NOTES-it.xml	5 Nov 2005 15:02:18 -0000	1.2
+++ RELEASE-NOTES-it.xml	19 Nov 2005 21:05:38 -0000	1.3
@@ -34,9 +34,9 @@
 
 
 <!-- *************** COMMON FDP entities *************** -->
-<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-it.ent">
  %FEDORA-ENTITIES-EN;
- <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
+ <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-it.xml">
 
  <!-- *************** Local entities *************** -->
 



From fedora-docs-commits at redhat.com  Sat Nov 19 21:56:58 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 19 Nov 2005 16:56:58 -0500
Subject: selinux-faq selinux-faq-it.xml,1.1,1.2
Message-ID: <200511192156.jAJLuwqV015145@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/selinux-faq
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15128/selinux-faq

Modified Files:
	selinux-faq-it.xml 
Log Message:



Index: selinux-faq-it.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/selinux-faq-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- selinux-faq-it.xml	19 Nov 2005 09:42:45 -0000	1.1
+++ selinux-faq-it.xml	19 Nov 2005 21:56:49 -0000	1.2
@@ -3,7 +3,7 @@
  "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
 
 <!-- *************** Bring in Fedora entities *************** -->
-<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-it.ent">
 %FEDORA-ENTITIES-EN;
 
 <!ENTITY BOOKID "selinux-faq-1.3-8 (2005-01-20-T16:20-0800)"> <!-- version of manual and date -->



From fedora-docs-commits at redhat.com  Sun Nov 20 15:28:24 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 20 Nov 2005 10:28:24 -0500
Subject: example-tutorial example-tutorial-it.xml,NONE,1.1
Message-ID: <200511201528.jAKFSOT0017187@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17171

Added Files:
	example-tutorial-it.xml 
Log Message:
Created bogus new i18n file for testing; don\'t waste time translating this.


--- NEW FILE example-tutorial-it.xml ---
<!-- $Id: -->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;

<!ENTITY BOOKNAME "example-tutorial">
<!ENTITY BOOKVERSION "0.14"> <!-- change version here -->
<!ENTITY BOOKDATE "2005-09-18"> <!-- change revision date here -->
<!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)">
<!ENTITY BUG-NUM "000000"> <!-- use this only while in draft stage -->

]>

<!-- This file is just a copy of the English version, only here for testing -->
<!-- Makefile locale capabilities.  Nobody really needs to translate this -->
<!-- yet. -->


<article id="example-tutorial" lang="it">
  <articleinfo>
    <title>Example Tutorial</title>
    <copyright>
      <year>2003, 2005</year>
      <holder>&FORMAL-RHI;</holder>
      <holder>Tammy Fox</holder>
    </copyright>
    <authorgroup>
      <author>
  <surname>Fox</surname>
  <firstname>Tammy</firstname>
      </author>
      <editor>
  <surname>Frields</surname>
  <firstname>Paul</firstname>
  <othername role="mi">W.</othername>
      </editor>
    </authorgroup>
    &LEGALNOTICE;
    <revhistory>
      <revision>
	<revnumber>0.13</revnumber>
	<date>2005-09-18</date>
	<authorinitials>PaulWFrields</authorinitials>
	<revdescription>
	  <para>
	    Add revision history.
	  </para>
	</revdescription>
      </revision>
    </revhistory>
  </articleinfo>

  <section id="sn-some-section">
    <title>Some Section</title>

    <indexterm>
      <primary>Index term</primary>
    </indexterm>

    <para>
      This is an example section. You should not use sect1, sect2, etc., since
      those tags will make sections less modular &mdash; that is, harder to
      relocate without changing a lot of other markup.
    </para>
    <para>
      Keep text within the <command>title</command> tags on the same line as the
      tags. Nesting the title on a separate line from the enclosing tags results
      in extra spaces in HTML rendering.
    </para>

    <warning>
      <title>Warning</title>
      <para>
        Example of an admonition.
      </para>
    </warning>

    <para>
      This paragraph illustrates the use of command syntax to accomplish a
      task. Note that specific filenames denoting versions should be
      avoided. To install any RPM package, use the following syntax:
    </para>
<screen>
<userinput><command>rpm -ivh <replaceable>pkgname</replaceable>-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</command></userinput>
</screen>
    <para>
      Notice that the <command>screen</command> section is entirely
      left-justified with no preceding indent. This is necessary to ensure
      proper rendering in PDFs. Also notice that the entire
      <command>command</command> has been surrounded by
      <command>userinput</command> since the user types this
      command. Computer output would be enclosed in
      <command>computeroutput</command> tags, as in the following
      sample.
    </para>
<screen>
<userinput><command>grep snmptrap /etc/services</command></userinput>
<computeroutput>snmptrap        162/udp         snmp-trap       # Traps for SNMP</computeroutput>
</screen>
    <para>
      Lines should be broken <emphasis>exactly</emphasis> as they are
      on-screen. Also, note that spaces inside <command>screen</command> tags
      are automatically treated as non-breaking.
    </para>
    <tip>
      <title>Fill modes and <command>screen</command> tags</title>
      <para>
  Using automatic or manual fill commands in Emacs/PSGML will sometimes
  mangle <command>screen</command> sections. Use care when performing fill
  operations, and check the results.
      </para>
    </tip>
  </section>

  <section>
    <title>Callout Example</title>
      <programlisting id="pl-callout">
Line 1 <co id="pl-callout-L1"/>
Line 2
Line 3
Line 4 <co id="pl-callout-L4"/>
      </programlisting>
      <calloutlist>
        <callout arearefs="pl-callout-L1">
          <para>
            Here is a callout.
          </para>
        </callout>
        <callout arearefs="pl-callout-L4">
          <para>
            The second callout.
          </para>
        </callout>
      </calloutlist>
  </section>

<index id="generated-index"></index>
</article>

<!--
Local variables:
mode: xml
End:
-->



From fedora-docs-commits at redhat.com  Sun Nov 20 18:29:46 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sun, 20 Nov 2005 13:29:46 -0500
Subject: docs-common/common cvs-it.xml,1.1,1.2
Message-ID: <200511201829.jAKITk1c022713@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22696/docs-common/common

Modified Files:
	cvs-it.xml 
Log Message:
Translation complete


Index: cvs-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/cvs-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- cvs-it.xml	19 Nov 2005 20:22:53 -0000	1.1
+++ cvs-it.xml	20 Nov 2005 18:29:38 -0000	1.2
@@ -293,17 +293,17 @@
         <secondary>accesso anonimo</secondary>
       </indexterm>
       <para>
-        If your goal is to download the various &FC; documents and to
-        render them on your system, you only need read-only access to
-        the <application>CVS</application> repository. Follow the
-        instructions in this section and then skip directly to
+        Se il tuo obbiettivo ?? scaricare i vari documenti &FC; e
+        renderizzarli sul tuo sistema, hai bisogno solo di un accesso read-only
+        al depositorio <application>CVS</application>. Segui le
+        instruzioni in questa sezione quindi salta direttamente a
         <xref linkend="sn-cvs-cvscommands-co"/>.
       </para>
 
       <para>
-        Change directories to where you want your files from
-        <application>CVS</application> to be located, and execute the
-        following commands:
+        Cambia directories dove vuoi che vengano collocati i files dal
+        <application>CVS</application>, ed esegui i
+	seguenti comandi:
       </para>
 <screen><prompt>$ </prompt><command>export CVSROOT=:pserver:cvs.fedora.redhat.com:/cvs/docs</command>
 <prompt>$ </prompt><command>cvs login</command>
@@ -311,204 +311,204 @@
 <prompt>$ </prompt><command>cvs checkout</command> <replaceable>module-name</replaceable>
 <prompt>$ </prompt><command>cd</command> <replaceable>module-name</replaceable></screen>
       <para>
-        Once you have checked the module out, it doesn't matter what
-        your
+        Una volta eseguito il check-out del modulo, non importa quale
         <envar>CVSROOT</envar>
-        is set to because it is stored in the file
-        <filename>CVS/Root</filename> for each directory in your local
-        repository. As long as your current working directory has a
-        <filename>CVS/</filename> directory, the
-        <application>CVS</application> program will automatically locate
-        the &FC; repository.
+        ?? impostata perch?? ?? registrata nel file
+        <filename>CVS/Root</filename> per ogni directory nel tuo depositorio
+	locale. Finch?? la tua directory di lavoro ha una directory
+        <filename>CVS/</filename>, il programma
+        <application>CVS</application> localizzer?? automaticamente
+        il repositorio &FC;.
       </para>
     </section>
 
     <section id="sn-cvs-config-author">
-      <title>Configuring Read/Write CVS Access</title>
+      <title>Configurazione accesso CVS Read/Write</title>
       <indexterm>
         <primary>cvs</primary>
-        <secondary>configuring read/write access</secondary>
+        <secondary>configurazione accesso read/write</secondary>
       </indexterm>
       <indexterm>
         <primary>cvs</primary>
-        <secondary>configuring access for authors</secondary>
+        <secondary>configurare gli accessi per gli autori</secondary>
       </indexterm>
       <para>
-        To author a new document or to change an existing one, you must
-        obtain full read/write access to the &FC; Docs
-        <application>CVS</application> repository. For the full details
-        on this process, refer to the
+        Per scrivere un nuovo documento o modificarne uno esistente, devi
+        ottenere  pieno accesso read/write al repositorio
+	<application>CVS</application> della Documentazione di  &FC;.
+	Per i dettagli completi su questo procedimento, fa riferimento al
+	sito web
         <ulink url="http://fedoraproject.org/wiki/DocsProject/NewWriters"><filename>http://fedoraproject.org/wiki/DocsProject/NewWriters</filename>
-        </ulink> web site. Below is a summary:
+        </ulink>. Segue un sommario:
       </para>
 
       <itemizedlist>
         <listitem>
           <para>
-            Subscribe to the
+            Sotoscriviti alla
             <ulink url="https://listman.redhat.com/mailman/listinfo/fedora-docs-list"><filename>fedora-docs-list</filename>
-            </ulink>, which is the main forum for the project.
+            </ulink>, che ?? il forum principale del progetto.
           </para>
         </listitem>
         <listitem>
           <para>
-            Generate a GNU Privacy Guard (<abbrev>GPG</abbrev>) key to
-            identify yourself to the project.
+            Genera una chiave GNU Privacy Guard (<abbrev>GPG</abbrev>) per
+            identificarti nel progetto.
           </para>
         </listitem>
         <listitem>
           <para>
-            Register for a
+            Registrati per un account in
             <ulink url="http://bugzilla.redhat.com/"><filename>Bugzilla</filename>
-            </ulink> account, if you do not have one already.
-            <filename>Bugzilla</filename> is how we keep track of bugs,
-            changes and projects.
+            </ulink>, se non ne hai gi?? uno.
+            <filename>Bugzilla</filename> ?? il modo con cui teniamo traccia degli errori,
+            cambiamenti e progetti.
           </para>
         </listitem>
         <listitem>
           <para>
-            Post a
-            <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">self
-            introduction</ulink> to the list.
+            Posta un
+            <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">auto
+            introduzione</ulink> alla lista.
           </para>
         </listitem>
       </itemizedlist>
 
       <para>
-        After your
-        <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">self
-        introduction</ulink> has been approved your
-        <application>CVS</application> access will be granted.
+        Dopo che la tua
+        <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">auto
+        introduzione</ulink> ?? stata approvata il tuo accesso
+        <application>CVS</application> verr?? garantito.
       </para>
 
       <para>
-        Every author, and that includes you once your self introduction
-        has been received, has a unique
+        Ogni autore, e questo ti include una volta che la tua auto introduzione
+        ?? stat ricevuta, ha un unico
         <envar>$CVSROOT</envar>
-        to access the <application>CVS</application> repository:
+        per accedere al repositorio <application>CVS</application>:
       </para>
 <screen><prompt>$ </prompt><command>export CVSROOT=:ext:</command><replaceable>yourname</replaceable><command>@cvs.fedora.redhat.com:/cvs/docs</command>
 <prompt>$ </prompt><command>export CVS_RSH=/usr/bin/ssh</command></screen>
       <para>
-        With the
+        Con le variabili ambiente
         <envar>$CVSROOT</envar>
-        and
+        e
         <envar>$CVS_RSH</envar>
-        environment variables in place, you can access the repository:
+        impostate, puoi accedera al repositorio:
       </para>
 <screen><prompt>$ </prompt><command>cvs co -c</command></screen>
       <para>
-        You will be asked for the passphrase for your
-        <application>SSH</application> key. Press
+        Ti verr?? richiesta la passphrase per la tua chiave
+        <application>SSH</application>. Premi
         <guibutton>ENTER</guibutton>
-        and you should receive a list of modules already in the
-        repository.
+        e riceverai la lista dei moduli presenti nel
+        repositorio.
       </para>
     </section>
   </section>
   <section id="sn-cvs-cvscommands">
-    <title>Basic CVS Commands</title>
+    <title>Comandi CVS di base</title>
     <indexterm>
       <primary>cvs</primary>
-      <secondary>commands</secondary>
+      <secondary>comandi</secondary>
     </indexterm>
     <para>
-      After configuring your system to work with CVS, checkout the
-      modules you will be working on.
+      Dopo aver configurato il sistema per funzionare con CVS, esegui il checkout
+      dei moduli su cui lavorerai.
     </para>
     <tip>
       <title>Tip</title>
       <para>
-        To see if you need a correctly-set
-        <envar>$CVSROOT</envar>
-        variable, or the <option>-m </option>
-        <replaceable>repository</replaceable> command line switch, see
-        if you have a <filename>CVS/</filename> subdirectory in your
-        working directory.
+        Per vedere se hai impostato correttamente la variabile
+        <envar>$CVSROOT</envar>,
+        o lo switch della linea di comando <option>-m </option>
+        <replaceable>repository</replaceable>, vedi
+        se hai una subdirectory <filename>CVS/</filename> nella tua
+        directory di lavoro.
       </para>
       <para>
-        If you have a <filename>CVS/</filename> directory,
-        <application>CVS</application> ignores any
+        Se hai una directory <filename>CVS/</filename>,
+        <application>CVS</application> ignorera qualsiasi
         <envar>$CVSROOT</envar>
-        or <option>-m</option> command line switch.
+        o switch della linea di comando <option>-m</option>.
       </para>
     </tip>
     <section id="sn-cvs-cvscommands-co">
-      <title>Checking Out Modules</title>
+      <title>Fare il checkout dei moduli</title>
       <indexterm>
         <primary>cvs</primary>
-        <secondary>checking out modules</secondary>
+        <secondary>eseguire il checkout dei moduli</secondary>
       </indexterm>
       <para>
-        You only need to checkout a module once. After a local copy of
-        the module is on your system, it is on your system.
+        Devi fare il checkout di un modulo una volta. Dopo che la copia del
+        modulo ?? sul tuo sistema, ?? sul tuo sistema.
       </para>
 
       <para>
-        To checkout a module, use the following command:
+        Per fare il checkout di un modulo, usa il seguente comando:
       </para>
 <screen><prompt>$ </prompt><command>cvs co</command>  <replaceable>&lt;module-name&gt;</replaceable></screen>
       <para>
-        For example, to checkout the
-        <computeroutput>example-tutorial</computeroutput> module, change
-        to your work directory, and execute the following command:
+        Per esempio, per fare il checkout del modulo
+        <computeroutput>example-tutorial</computeroutput>, cambia
+        la tua directory di lavoro, ed esegui il seguente comando:
       </para>
 <screen><prompt>$ </prompt><command>cvs co example-tutorial</command></screen>
       <para>
-        A directory called <filename>example-tutorial/</filename> is
-        created in the current directory.
+        Verr?? creata una directory chiamata <filename>example-tutorial/</filename>
+        nela directory corrente.
       </para>
 
       <para>
-        If a branch name is not specified when checking out a module, it
-        is referred to as the <firstterm>HEAD</firstterm> of the
-        <application>CVS</application> module.
+        Se non viene specificato un nome del ramo durante il checking del modulo,
+        verr?? riferito al <firstterm>HEAD</firstterm> del modulo
+        <application>CVS</application>.
       </para>
 
       <section id="sn-cvs-cvscommands-co-branch">
-        <title>Checking Out Branches of Modules</title>
+        <title>Fare il checkout dei rami dei moduli</title>
         <indexterm>
           <primary>cvs</primary>
-          <secondary>check out modules</secondary>
-          <tertiary>checking out branches</tertiary>
+          <secondary>eseguire il checkout dei moduli</secondary>
+          <tertiary>eseguire il checkout dei rami</tertiary>
         </indexterm>
         <para>
-          Think of a <application>CVS</application> branch as a version
-          of the files for a particular version of a manual or package.
+          Pensa ad un ramo <application>CVS</application> come una versione
+          dei files per una particolare versione del pacchetto o manuale.
         </para>
 
         <para>
-          To checkout a branch of a module, use the following command:
+          Per fare il checkout di un ramo di un modulo, usa il seguente comando:
         </para>
 <screen><prompt>$ </prompt><command>cvs co</command> <option>-d</option>  <replaceable>&lt;directory&gt;</replaceable> <option>-r</option>  <replaceable>&lt;branchname&gt;</replaceable> <replaceable>&lt;module-name&gt;</replaceable></screen>
         <para>
-          A directory named <replaceable>&lt;directory&gt;</replaceable>
-          is created, and the files for the
-          <replaceable>&lt;branchname&gt;</replaceable> branch of the
-          <replaceable>&lt;module-name&gt;</replaceable> module are
-          copied in the directory.
+          Una directory chiamata <replaceable>&lt;directory&gt;</replaceable>
+          viene creata, ed i files per il ramo
+          <replaceable>&lt;branchname&gt;</replaceable> del modulo
+          <replaceable>&lt;module-name&gt;</replaceable> sono
+          copiati nella directory.
         </para>
 
         <para>
-          For example, to checkout a branch named BRANCH-VERSION-1.2
-          from the <computeroutput>mymodule</computeroutput> module, use
-          the command:
+          Per esempio, per fare il checkout di un ramo denominato BRANCH-VERSION-1.2
+          dal modulo <computeroutput>mymodule</computeroutput>, usa
+          il comando:
         </para>
 <screen><prompt>$ </prompt><command>cvs co -d mymodule-1.2 -r BRANCH-VERSION-1.2 mymodule</command></screen>
         <para>
-          The BRANCH-VERSION-1.2 branch of the module is checked out in
-          the <filename>mymodule-1.2</filename> directory on your
-          system.
+          Verr?? eseguito il checkout del ramo BRANCH-VERSION-1.2 del modulo nella
+          directory <filename>mymodule-1.2</filename> sul tuo
+          sistema.
         </para>
 
         <para>
-          To determine which branches and tags exist for a file, use the
-          command:
+          Per determinare quale ramo e tags esiste per un file, usa il
+          comando:
         </para>
 <screen><prompt>$ </prompt><command>cvs status</command> <option>-v</option> <replaceable>&lt;filename&gt;</replaceable></screen>
         <para>
-          For example, the status of the file
-          <filename>foo.sgml</filename> is as follows:
+          Per esempio, lo status del file
+          <filename>foo.sgml</filename> ?? il seguente:
         </para>
 <screen>
 <computeroutput>
@@ -526,207 +526,206 @@
 </computeroutput>
 </screen>
         <para>
-          Only tags marked as branches in the second column under the
-          <computeroutput>Existing Tags</computeroutput> section can be
-          checked out as a branch.
+          Solo dei tags marcati come rami nella seconda colonna sotto la
+	  sezione <computeroutput>Existing Tags</computeroutput> si pu?? eseguire
+          il checkout come ramo.
         </para>
       </section>
     </section>
 
     <section id="sn-cvs-cvscommands-up">
-      <title>Updating Files</title>
+      <title>Aggiornare i files</title>
       <indexterm>
         <primary>cvs</primary>
-        <secondary>updating files</secondary>
+        <secondary>aggiornare i files</secondary>
       </indexterm>
       <para>
-        To retrieve the latest versions of the files in a module, change
-        to the directory that contains the files for the module and
-        execute the command:
+        Per ricevere l'ultima versione di un file in un modulo, cambia
+        nella directory che contiene i files per il modulo ed
+        esegui il comando:
       </para>
 <screen><command>cvs update</command></screen>
       <para>
-        The latest versions of all the files in the module are
-        downloaded into your local copy. If you notice a file conflict,
-        refer to <xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
+        Le ultime versioni di tutti i files ne modulo sono
+        scaricate nella tua copia locale. Se noti un conflitto di file,
+        fa riferimento a <xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
       </para>
     </section>
 
     <section id="sn-cvs-cvscommands-commit">
-      <title>Committing Files</title>
+      <title>Eseguire il commit dei files</title>
       <indexterm>
         <primary>cvs</primary>
-        <secondary>committing files</secondary>
+        <secondary>eseguire il commit dei files</secondary>
       </indexterm>
       <para>
-        After modifying files in your local version of a module, commit
-        them to save the changes on the <application>CVS</application>
+        Dopo aver modificato i files nella tua versione locale di un modulo, esegui il commit
+        per salvare i cambiamenti sul <application>CVS</application>
         server:
       </para>
-<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> &quot;<replaceable>some log message</replaceable>&quot; <replaceable>filename</replaceable></screen>
+<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> &quot;<replaceable>alcuni messaggi di log</replaceable>&quot; <replaceable>filename</replaceable></screen>
       <note>
         <para>
-          If you would prefer to write your log message with your
-          favorite text editor, as defined by the $VISUAL or the $EDITOR
-          environment variable, just omit the <userinput>-m &quot;some
-          log message&quot;</userinput>. The buffer will already contain
-          comments describing the change; you do not need to delete them
-          as you enter your own text.
+          Se preferisci scrivere il tuo messaggio di log con il tuo editor
+          di testo preferito, come definito dalla variabile ambiente $VISUAL o
+	  $EDITOR, ometti semplicemente la <userinput>-m &quot;alcuni
+          messaggi di log&quot;</userinput>. Il buffer conterr?? gi??
+          alcuni commenti che descrivono i cambiamenti; non ?? necessario cancellarli
+          quando inserirai il tuo testo.
         </para>
       </note>
 
       <para>
-        The log message should be as descriptive as possible so that you
-        and anyone else working on the module understands what changed.
-        Using a log message such as <userinput>updated some
-        files</userinput> does not accurately describe what has changed
-        and will not help you in the future. If you are correcting a
-        bug, use the <application>Bugzilla</application> reference.
+        I messaggi di log dovranno essere pi?? descrittivi possibile affinch??
+        chiunque altro lavori al modulo capisca cos'?? stato cambiato.
+        Usare un messaggio di log tipo <userinput>aggiornati alcuni
+        files</userinput> non descrive accuratamente cosa ?? stato cambiato
+        e non ti aiuter?? in futuro. Se hai corretto un
+        errore, fa riferimento a <application>Bugzilla</application>.
       </para>
 
       <para>
-        The <replaceable>&lt;filename&gt;</replaceable> can be one
-        filename, a series of filenames separated by spaces, or a group
-        of filenames specified using wildcards such as
-        <filename>*.png</filename> or <filename>foo-*.sgml</filename>.
+        Il <replaceable>&lt;filename&gt;</replaceable> pu?? essere un
+        filename, una serie si filenames separati da spazi, o un gruppo
+        di filenames specificati usando una wildcards tipo
+        <filename>*.png</filename> o <filename>foo-*.sgml</filename>.
       </para>
 
       <para>
-        If no filename or group of filenames is specified in the
-        <command>commit</command> command, all outstanding changes of
-        any kind are committed to the server. The command is recursive
-        and will include changes in any subdirectories of the module.
-        Use caution when issuing the <command>commit</command> command
-        without any filenames because you might not remember exactly
-        what files changed.
+        Se nessun filename o gruppo di filenames ?? specificato nel
+	comando <command>commit</command>, tutti i cambiamenti eccezionali
+	di qualsiasi tipo sono commessi al server. Il comando ?? recursivo
+        ed includer?? i cambiamenti in ogni subdirectories del modulo.
+        Usa cautela qunado esegui il comando <command>commit</command>
+	senza nessun filenames poich?? potresti non ricordare esattamente
+        quali files sono cambiano.
       </para>
 
       <para>
-        If you notice a file conflict, refer to
+        Se noti un conflitto di file, fa riferimento a
         <xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
       </para>
     </section>
 
     <section id="sn-cvs-cvscommands-add">
-      <title>Adding Files</title>
+      <title>Aggiungere files</title>
       <indexterm>
         <primary>cvs</primary>
-        <secondary>adding files</secondary>
+        <secondary>aggiungere files</secondary>
       </indexterm>
       <para>
-        To add a file to a module, create the file in your local copy
-        then execute the following command:
+        Per aggiungere un file ad un modulo, crea il file sulla tua copia locale
+        quindi esegui il seguente comando:
       </para>
 <screen><prompt>$ </prompt><command>cvs add</command>  <replaceable>file-to-add</replaceable></screen>
       <para>
-        After adding the file, you must <command>commit</command> the
-        <command>add</command> to copy it to the server:
+        Dopo aver aggiunto il file, devi eseguire un <command>commit</command>
+        dell'<command>add</command> per copiarlo sul server:
       </para>
-<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> &quot;<replaceable>some log message</replaceable>&quot; <replaceable>file-to-add</replaceable></screen>
+<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> &quot;<replaceable>qualche messaggio di log</replaceable>&quot; <replaceable>file-da-aggiungere</replaceable></screen>
     </section>
 
     <section id="sn-cvs-cvscommands-admin">
-      <title>Managing Binary Files</title>
+      <title>Amministrare i files binari</title>
       <indexterm>
         <primary>cvs</primary>
-        <secondary>binary files</secondary>
+        <secondary>files binari</secondary>
       </indexterm>
       <para>
-        The most commonly-archived files are simple text files but
-        sometimes binary files are also archived. The
-        <application>cvs</application> program recognizes most common
-        filename extentions such as <filename>.png</filename> or
-        <filename>.jpg</filename>, so <application>cvs</application>
-        usually &quot;does the right thing&quot;.
+        I files comunemente pi?? archiviati sono di semplice testo ma
+        qualche volta sono archiviati anche files binari. Il programma
+        <application>cvs</application> determina le estensioni dei
+	files pi?? comuni tipo <filename>.png</filename> o
+        <filename>.jpg</filename>, cos?? di solito <application>cvs</application>
+        &quot;fa la cosa giusta&quot;.
       </para>
 
       <para>
-        When a copy of a file is checked out of the repository,
-        <application>cvs</application> scans it for special keywords,
-        such as &quot;<computeroutput>$id:$</computeroutput>&quot; and
-        replaces the string with a generated value, such as the file
-        version number.
+        Quando si esegue il checkout della copia di un file del repositorio,
+        il <application>cvs</application> lo scansisce per parole chiavi speciali,
+        tipo &quot;<computeroutput>$id:$</computeroutput>&quot; e
+        sostituisce le stringhe con un valore generato, tipo il numero di versione
+	del file.
       </para>
 
       <para>
-        This keyword substitution usually corrupts binary files, so it
-        must be turned off if <application>cvs</application> does not
-        recognize your file as binary. To mark your file as being
-        binary, and thus needing the keyword expansion turned off, use
-        the command:
+        Questa sostituzione di keyword di solito corrompe i files binari, cos??
+        deve essere disattivata se <application>cvs</application> non
+        reconosce i tuoi files come binari. Per marcare il tuo file come
+        binario, e quindi disattivare l'espansione dell keyword, usa
+        il comando:
       </para>
 <screen width="60"><prompt>$ </prompt><command>cvs</command> <option>admin</option> <option>-kk</option> <replaceable>filename</replaceable></screen>
       <para>
-        Note that the file must already be checked in to the
-        <abbrev>CVS</abbrev> repository before the
-        <option>admin</option> command can be used. This is OK, since
-        the keyword expansion is done as the file is checked out and
-        copied to the local directory, not when the file is committed to
-        the repository.
+        Nota che il file deve gi?? essere nel repositorio
+        <abbrev>CVS</abbrev> prima di poter usare il comando
+        <option>admin</option>. Questo ?? OK, fino a che
+        l'espansione delle keyword ?? fatta appena il file viene sottoposto a checkout e
+        copiato nella directory locale, non quando il file viene commesso al
+        repositorio.
       </para>
       <tip>
-        <title>Recovering a binary file</title>
+        <title>Ripristinare un file binario</title>
         <para>
-          If you check a binary file into the repository and then find
-          it corrupted when it is checked out, do not panic. Simply use
-          the <option>admin</option> command as described above, delete
-          your local file copy, and check it out again.
+          Se esegui il check di un file binario nel repositorio e trovi
+          che sia corrotto durante il checkout, non aver paura. Usa semplicemente
+          il comando <option>admin</option> come descritto sopra, cancella
+          la tua copia locale del file, ed esegui nuovamente il checkout.
         </para>
       </tip>
     </section>
 
     <section id="sn-cvs-cvscommands-rm">
-      <title>Removing Files</title>
+      <title>Rimuovere i files</title>
       <indexterm>
         <primary>cvs</primary>
-        <secondary>removing files</secondary>
+        <secondary>rimuovere i files</secondary>
       </indexterm>
       <para>
-        If a file is no longer needed in the module, use the
-        <command>remove</command> command to remove it from your local
-        copy and then <command>commit</command> the removal to the
-        server. Even though the file is removed from current version of
-        the module, an archived copy is still kept on the server and can
-        be retrieved at any time with the <command>add</command>
-        command.
+        Se un file non ?? pi?? necessario nel modulo, usa il
+        comando <command>remove</command> per rimuoverlo dalla tua copia
+        locale poi esegui il <command>commit</command> per rimuoverlo dal
+        server. Anche se il file ?? rimosso dalla versione corrente del
+        modulo, una copia archiviata ?? ancora lasciata sul server e pu??
+        essere recuperato in qualsiasi momento con il comando <command>add</command>.
       </para>
 <screen><prompt>$ </prompt><command>cvs rm -f</command>  <replaceable>file-to-remove</replaceable></screen>
       <para>
-        After removing the file, you must <command>commit</command> the
-        removal:
+        Dopo la rimozione del file, devi eseguire il <command>commit</command> della
+        rimozione:
       </para>
-<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option>&quot;<replaceable>some log message</replaceable>&quot; <replaceable>file-to-remove</replaceable></screen>
+<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option>&quot;<replaceable>qualche messagiio di log</replaceable>&quot; <replaceable>file-da-rimuovere</replaceable></screen>
       <para>
-        You can not use wildcards in the <command>commit</command>
-        command to identify removed files. They must be specified with a
-        exact filename.
+        Non puoi usare wildcards nel eseguire il <command>commit</command>
+        per identificare files rimossi. Essi devono essere specificati con il nome
+	di file esatto.
       </para>
 
       <para>
-        If you need to rename a file, it is best to rename the file on
-        the <application>CVS</application> server so that the history of
-        the file is preserved. If you need to rename a file, send an
-        email to
+        Se necessiti di rinominare un file, ?? meglio rinominarlo sul
+        <application>CVS</application> server affinch?? la storia del
+        file possa essere preservata. Se hai bisogno di rinominare un file, manda un
+        email a
         <ulink url="mailto:cvsdocs-administrator at fedora.redhat.com"><filename>cvsdocs-administrator at fedora.redhat.com</filename>
-        </ulink> asking to have the file renamed.
+        </ulink> chiedendo di voler rinominare un file.
       </para>
     </section>
 
     <section id="sn-cvs-cvscommands-status">
-      <title>Status of Files</title>
+      <title>Status dei files</title>
       <indexterm>
         <primary>cvs</primary>
-        <secondary>status of files</secondary>
+        <secondary>status dei files</secondary>
       </indexterm>
       <para>
-        Sometimes it is necessary to view the
-        <firstterm>status</firstterm> of a file in a
-        <application>CVS</application> module. To view the status of a
-        file, use the command:
+        Qualche volta ?? necessario vedere lo
+        <firstterm>status</firstterm> di un file in un
+        modulo <application>CVS</application>. Per vedere lo status di un
+        file, usa il comando:
       </para>
 <screen><prompt>$ </prompt><command>cvs status</command>  <replaceable>filename</replaceable></screen>
       <para>
-        The status report of a repository file is as follows:
+        Il rapporto dello status di un file nel repositorio ?? come segue:
       </para>
 
       <variablelist>
@@ -734,8 +733,8 @@
           <term><computeroutput>Up-to-date</computeroutput></term>
           <listitem>
             <para>
-              Your revision of the file is identical to the latest
-              revision on the <application>CVS</application> server.
+              La tua revisione del file ?? identica all'ultima
+              revisione sul <application>CVS</application> server.
             </para>
           </listitem>
         </varlistentry>
@@ -744,8 +743,8 @@
           <term><computeroutput>Locally Modified</computeroutput></term>
           <listitem>
             <para>
-              You have updated to the latest revision from the server,
-              but then you modified the file on your system.
+              Hai aggiornato il file all'ultima versione dal server,
+              ma poi hai modificatio il file sul tuo sistema.
             </para>
           </listitem>
         </varlistentry>
@@ -754,8 +753,8 @@
           <term><computeroutput>Locally Added</computeroutput></term>
           <listitem>
             <para>
-              You added the file with the <command>cvs add</command>
-              command but have not yet committed the addition of the
+              Hai aggiunto il file con il comando <command>cvs add</command>
+              ma non hai ancora eseguito il commit per l'aggiunta del
               file.
             </para>
           </listitem>
@@ -765,9 +764,9 @@
           <term><computeroutput>Locally Removed</computeroutput></term>
           <listitem>
             <para>
-              You removed the file with the <command>cvs
-              remove</command> command but have not yet committed the
-              removal.
+              Hai rimosso il file con il comando <command>cvs
+              remove</command> ma non hai ancora eseguito il commit per la
+              rimozione.
             </para>
           </listitem>
         </varlistentry>
@@ -776,10 +775,10 @@
           <term><computeroutput>Needs Checkout</computeroutput></term>
           <listitem>
             <para>
-              A newer version of the file is on the server and needs to
-              be retrieved. Even though the status includes the word
-              checkout, it really means that you need to update your
-              files with the <command>cvs update</command> command.
+              Sul server c'?? una nuova versione del file ed necessita di
+              essere recuperata. Anche se lo status include la parola
+              checkout, vuoldire che hai bisogno di aggiornare
+              i files con il comando <command>cvs update</command>.
             </para>
           </listitem>
         </varlistentry>
@@ -788,9 +787,9 @@
           <term><computeroutput>Needs Patch</computeroutput></term>
           <listitem>
             <para>
-              The revision in your local checkout needs a patch to be
-              the latest revision from the server. Issue the
-              <command>cvs update</command> command to resolve.
+              La revisione del tuo checkout locale necessita di una patch per
+              essere l'ultima versione dal server. Esegui il
+              comando <command>cvs update</command> per risolvere.
             </para>
           </listitem>
         </varlistentry>
@@ -799,10 +798,10 @@
           <term><computeroutput>Needs Merge</computeroutput></term>
           <listitem>
             <para>
-              A newer revision exists on the server and your local
-              version contains modification not yet committed. This
-              status usually occurs if you don't have the latest
-              revision of the file and edit it anyway.
+              Esiste una nuova revisione sul server e la tua versione di copia
+              locale contiene modifiche di cui non hai fatto ancora il commit. Questo
+              status di solito avviene se non hai l'ultima revisione
+              del file ed lo editi lo stesso.
             </para>
           </listitem>
         </varlistentry>
@@ -811,12 +810,12 @@
           <term><computeroutput>File had conflicts on merge</computeroutput></term>
           <listitem>
             <para>
-              Similar to <computeroutput>Needs Merge</computeroutput>,
-              except when you tried to issue the <command>cvs
-              update</command> command, the differences could not be
-              resolved automatically. Refer to
-              <xref linkend="sn-cvs-cvscommands-conflicts"></xref> for
-              more information on resolving conflicts.
+              Simile a <computeroutput>Needs Merge</computeroutput>,
+              eccetto che quando hai provato ad eseguire il comando <command>cvs
+              update</command>, le differenze non potevano essere
+              risolte automaticamente. Fa riferimento a
+              <xref linkend="sn-cvs-cvscommands-conflicts"></xref> per
+              maggiori informazioni sulla risoluzione dei conflitti.
             </para>
           </listitem>
         </varlistentry>
@@ -825,14 +824,14 @@
           <term><computeroutput>Unknown</computeroutput></term>
           <listitem>
             <para>
-              The <application>CVS</application> server does not know
-              anything about this file. It has neither been added nor
-              removed locally and has never been committed to the
-              server. This status usually occurs for files you should
-              not commit to <application>CVS</application> such as
-              <filename>generated-index.sgml</filename> or for files
-              that you want to add to the repository but have not yet
-              issued the <command>cvs add</command> command.
+              Il <application>CVS</application> server non sa nulla
+	      su questo file. Il file non ?? stato aggiunto ne
+              rimosso loclamente e non ?? mai stato commesso al
+              server. Questo status di solito sussiste per i files che di cui non
+              vorresti fare il commit al <application>CVS</application> tipo
+              i <filename>generated-index.sgml</filename> o per quei files
+              che vorresti aggiungere al repositorio ma dei quali non hai
+              ancora impartito il comando <command>cvs add</command>.
             </para>
           </listitem>
         </varlistentry>
@@ -840,16 +839,16 @@
     </section>
 
     <section id="sn-cvs-cvscommands-conflicts">
-      <title>Resolving Conflicts</title>
+      <title>Risoluzione dei conflitti</title>
       <indexterm>
         <primary>cvs</primary>
-        <secondary>resolving conflicts</secondary>
+        <secondary>risoluzione dei conflitti</secondary>
       </indexterm>
       <para>
-        If you modify a file and the same region is modified by someone
-        else and committed first, you will probably see a message
-        similar to the following when committing the file or updating
-        your local copy of the module:
+        Se modifichi un file e la stessa regione ?? modificata da qualcun'altro
+        che esegue il commitprima di te, probabilmente vedrai un messaggio
+	simile al seguente quando eseguirai il commit o l'aggiornamento
+        della tua copia locale del modulo:
       </para>
 <screen>
 <computeroutput>
@@ -863,10 +862,10 @@
 </computeroutput>
 </screen>
       <para>
-        To resolve the conflict, open the file, search for
+        Per risolvere il conflitto, apri il file, cerca
         <computeroutput>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</computeroutput>
-        and determine which version of the content is correct. For
-        example:
+        e determina quale versione del contenuto ?? corretta. Per
+        esempio:
       </para>
 <screen>
 <computeroutput>
@@ -881,40 +880,40 @@
 </computeroutput>
 </screen>
       <para>
-        The content between the
+        Il contenuto fra le
         <computeroutput>&lt;&lt;&lt;&lt;&lt;&lt;&lt;</computeroutput>,
-        and the <computeroutput>=======</computeroutput> is the content
-        from your working copy. The content between the
-        <computeroutput>=======</computeroutput> and the
-        <computeroutput>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</computeroutput> is
-        the content from the server.
+         e le <computeroutput>=======</computeroutput> ?? il contenuto
+        della tua copia di lavoro. Il contenuto fra le
+        <computeroutput>=======</computeroutput> e le
+        <computeroutput>&gt;&gt;&gt;&gt;&gt;&gt;&gt;</computeroutput> ??
+        il contenuto dal server.
       </para>
 
       <para>
-        Resolve the conflict by editing your copy, and commit the file.
+        Resolvi il conflitto editando la tua copia, ed esegui il commit del file.
       </para>
     </section>
 
     <section id="sn-cvs-cvscommands-summary">
-      <title>Summary</title>
+      <title>Sommario</title>
       <indexterm>
         <primary>cvs</primary>
-        <secondary>commands</secondary>
-        <tertiary>summary of</tertiary>
+        <secondary>comandi</secondary>
+        <tertiary>sommario di</tertiary>
       </indexterm>
       <para>
-        All commands assume you are in the proper directory for the
-        <application>CVS</application> module.
+        Tutti i comandi assumono che tu sia nella directory appropriata per
+        il modulo <application>CVS</application>.
       </para>
       <table frame="all" id="tb-cvs-basic-commands">
-        <title>Basic CVS Commands</title>
+        <title>Comandi CVS di base</title>
         <tgroup cols="2">
           <colspec colnum="1" colname="shortcut" colwidth="30"/>
           <colspec colnum="2" colname="description" colwidth="60"/>
           <thead>
             <row>
-              <entry>Command</entry>
-              <entry>Description</entry>
+              <entry>Commando</entry>
+              <entry>Descrizione</entry>
             </row>
           </thead>
           <tbody>
@@ -923,87 +922,87 @@
         <replaceable>&lt;module-name&gt;</replaceable></command>
       or <command>cvs co <replaceable>&lt;module-name&gt;</replaceable></command>
               </entry>
-              <entry>Creates a directory called
-      <replaceable>&lt;module-name&gt;</replaceable> with the contents of the
-      module in the directory</entry>
+              <entry>Crea una directory chiamata
+      <replaceable>&lt;module-name&gt;</replaceable> con il contenuto del
+      modulo nella directory</entry>
             </row>
             <row>
               <entry><command>cvs co -d <replaceable>&lt;directory&gt;</replaceable> -r <replaceable>&lt;branchname&gt;</replaceable><replaceable>&lt;module-name&gt;</replaceable></command>
               </entry>
-              <entry>Creates the <replaceable>&lt;directory&gt;</replaceable> directory
-      with the contents of the <replaceable>&lt;branchname&gt;</replaceable>
-      branch of the <replaceable>&lt;module-name&gt;</replaceable> module</entry>
+              <entry>Crea la directory <replaceable>&lt;directory&gt;</replaceable>
+      con i contenuti del ramo <replaceable>&lt;branchname&gt;</replaceable>
+      del modulo <replaceable>&lt;module-name&gt;</replaceable></entry>
             </row>
             <row>
               <entry><command>cvs update</command> or <command>cvs up</command>
               </entry>
-              <entry>Update your files with the latest files from the CVS server</entry>
+              <entry>Aggiorna i tuoi files con gli ultimi files dal CVS server</entry>
             </row>
             <row>
               <entry><command>cvs add <replaceable>&lt;filename&gt;</replaceable></command>
               </entry>
-              <entry>Add a new file "filename" to the CVS server</entry>
+              <entry>Aggiunge un nuovo file "filename" al CVS server</entry>
             </row>
             <row>
               <entry><command>cvs commit -m "My message"
         <replaceable>&lt;filename&gt;</replaceable></command>
               </entry>
-              <entry>Update file <replaceable>&lt;filename&gt;</replaceable> with the
-      latest copy from your computer</entry>
+              <entry>Aggiorna il file <replaceable>&lt;filename&gt;</replaceable> con
+      l'ultima copia proveniente dal tuo computer</entry>
             </row>
             <row>
               <entry><command>cvs log <replaceable>&lt;filename&gt;</replaceable></command>
               </entry>
-              <entry>View the commit messages for the file <replaceable>&lt;filename&gt;</replaceable>
+              <entry>Mostra i messaggi di commit per il file <replaceable>&lt;filename&gt;</replaceable>
               </entry>
             </row>
             <row>
               <entry><command>cvs status <replaceable>&lt;filename&gt;</replaceable></command>
               </entry>
-              <entry>View status of the file, such as <computeroutput>Locally
+              <entry>Mostra lo status del file, tipo <computeroutput>Locally
         Modified</computeroutput>
               </entry>
             </row>
             <row>
               <entry><command>cvs status -v <replaceable>&lt;filename&gt;</replaceable></command>
               </entry>
-              <entry>View existing tags and branches for file</entry>
+              <entry>Mostra i tags esistenti ed i rami per il file</entry>
             </row>
             <row>
               <entry><command>cvs diff <replaceable>&lt;filename&gt;</replaceable></command>
               </entry>
-              <entry>Show diff of the working copy of the file and the latest
-      version of the file for the branch</entry>
+              <entry>Mostra la differenza della copia di lavoro del file e l'ultima
+      versione del file per il ramo</entry>
             </row>
             <row>
               <entry><command>cvs diff -r1.1 -r1.2 <replaceable>&lt;filename&gt;</replaceable></command>
               </entry>
-              <entry>Show diff of version 1.1 and 1.2 for file</entry>
+              <entry>Mostra la differenza fra le versioni 1.1 e 1.2 per il file</entry>
             </row>
           </tbody>
         </tgroup>
       </table>
       <para>
-        For more information, read the CVS manual available on your
-        system at
+        Per maggiori informazioni, leggi il manuale CVS disponibile sul tuo
+	sistema in
         <filename>/usr/share/doc/cvs-<replaceable>&lt;version-number&gt;</replaceable>/cvs.ps</filename>
-        (the CVS version might vary) and visit the CVS webpage available
-        at
+        (la versione CVS pu?? cambiare) e visita la pagian web di CVS disponibile
+        su
         <ulink url="http://www.cvshome.org/">http://www.cvshome.org/</ulink>.
       </para>
       <tip>
         <title>Tip</title>
         <para>
-          Since <application>CVS</application> is using
-          <application>ssh</application> to connect to the
-          <application>CVS</application> server, you will be prompted
-          your password before performing your
-          <application>CVS</application> request. If you want to
-          configure your machine so that you do not have to enter a
-          password, refer to the
+          Poich?? <application>CVS</application> usa
+          <application>ssh</application> per connettersi al
+          <application>CVS</application> server, ti verr?? richiesta
+          la password prima di eseguire una richiesta
+          <application>CVS</application>. Se vuoi configurare
+          la tua macchina affinch?? tu non abbia pi?? bisogno di
+          inserire la password, fa riferimento a
           <ulink url="http://redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-openssh-client-config.html"><citetitle>&RH;
-          Linux 9 Customization Guide</citetitle> </ulink> for details
-          about using <command>ssh-agent</command>.
+          Linux 9 Customization Guide</citetitle> </ulink> per i dettagli
+          sull'uso di <command>ssh-agent</command>.
         </para>
       </tip>
     </section>



From fedora-docs-commits at redhat.com  Sun Nov 20 19:20:23 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 20 Nov 2005 14:20:23 -0500
Subject: rpm-guide rpm-guide-using-rpm-en.xml,1.5,1.6
Message-ID: <200511201920.jAKJKNxE024856@cvs-int.fedora.redhat.com>

Author: elliss

Update of /cvs/docs/rpm-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24834

Modified Files:
	rpm-guide-using-rpm-en.xml 
Log Message:
Tagged to FDP standards.



View full diff with command:
/usr/bin/cvs -f diff  -kk -u -N -r 1.5 -r 1.6 rpm-guide-using-rpm-en.xml
Index: rpm-guide-using-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- rpm-guide-using-rpm-en.xml	14 Nov 2005 21:55:05 -0000	1.5
+++ rpm-guide-using-rpm-en.xml	20 Nov 2005 19:20:15 -0000	1.6
@@ -27,19 +27,20 @@
     installing a package, but there???s a lot more you can do. For
     example, you can install packages from remote sites using HTTP or
     FTP to download the package to install. There are quite a few other
-    rpm options you can use to get information and feedback on
-    installation, for example.
+    <command>rpm</command> options you can use to get information and
+    feedback on installation, for example.
   </para>
   <sect1>
-    <title>The rpm Command</title>
+    <title>The <command>rpm</command> Command</title>
     <para>
-      Just about everything you do with RPM requires the rpm command. As
-      a nice added benefit, just about everything you do with RPM
-      requires a single invocation of the rpm command. That means common
-      tasks such as installing and removing software can be done quickly
-      and efficiently. The basics of the rpm command are not very hard,
-      and you can perform the basic tasks within a few minutes of
-      reading this chapter.
+      Just about everything you do with RPM requires the
+      <command>rpm</command> command. As a nice added benefit, just
+      about everything you do with RPM requires a single invocation of
+      the <command>rpm</command> command. That means common tasks such
+      as installing and removing software can be done quickly and
+      efficiently. The basics of the <command>rpm</command> command are
+      not very hard, and you can perform the basic tasks within a few
+      minutes of reading this chapter.
     </para>
   </sect1>
   <sect1>
@@ -47,19 +48,20 @@
     <para>
       To install software, you need something to install. Typically,
       this is a file packaged as RPM, using a file-name extension of
-      .rpm. Of course, this isn???t required, but just about every RPM
-      package is stored in a file with a .rpm extension. For example,
-      the following file holds an RPM package, ready to be installed:
+      <filename>rpm</filename>. Of course, this isn???t required, but
+      just about every RPM package is stored in a file with a
+      <filename>rpm</filename> extension. For example, the following
+      file holds an RPM package, ready to be installed:
     </para>
     <para>
-      jikes-1.16-1.i386.rpm
+      <filename>jikes-1.16-1.i386.rpm</filename>
     </para>
     <para>
-      This package holds an application named jikes (a Java language
-      compiler application). From the discussion in the last two
-      chapters, you should be able to determine the version of the
-      program this RPM holds and which release of the RPM package this
-      represents.
+      This package holds an application named <command>jikes</command>
+      (a Java language compiler application). From the discussion in the
+      last two chapters, you should be able to determine the version of
+      the program this RPM holds and which release of the RPM package
+      this represents.
     </para>
     <para>
       Other RPMs hold sources, the program source codes used to create
@@ -67,194 +69,218 @@
       file holds a source RPM:
     </para>
     <para>
-      jikes-1.16-1.src.rpm
+      <filename>jikes-1.16-1.src.rpm</filename>
     </para>
     <para>
-      The src in the package name is short for source. This file-naming
-      convention is not required, but is used by just about all source
-      code packages. (Following conventions helps other administrators
-      know what to expect.)
-    </para>
-    <para>
-      Cross Reference
-    </para>
-    <para>
-      <xref linkend="ch-creating-rpms"/> and
-      <xref linkend="ch-rpmbuild"/> cover building RPMs from source
-      RPMs.
-    </para>
-    <para>
-      The rpm command provides three main operations for upgrading and
-      installing packages:
-    </para>
-    <para>
-      An upgrade operation means installing a new version of a package
-      and removing all previous versions of the same package. If you
-      have not installed a package previously, the upgrade operation
-      will install the package.
-    </para>
-    <para>
-      A freshen operation means to install a new version of a package
-      only if you have already installed another version of the package.
-    </para>
-    <para>
-      An install operation installs a package for the first time. It
-      also, through special command-line parameters, allows you to
-      install multiple versions of a package, usually not what you want.
-      So, in the vast majority of cases, you want to run the upgrade
-      operation for all package installations.
+      The <filename>src</filename> in the package name is short for
+      source. This file-naming convention is not required, but is used
+      by just about all source code packages. (Following conventions
+      helps other administrators know what to expect.)
     </para>
+    <note>
+      <title>Building Packages from Source RPMs</title>
+
+      <para>
+        Refer to <xref linkend="ch-creating-rpms"/> and
+        <xref linkend="ch-rpmbuild"/> for information on building RPMs
+        from source RPMs.
+      </para>
+    </note>
+    <para>
+      The <command>rpm</command> command provides three main operations
+      for upgrading and installing packages:
+    </para>
+    <variablelist>
+      <varlistentry>
+        <term>Upgrade</term>
+        <listitem>
+          <para>
+            An upgrade operation means installing a new version of a
+            package and removing all previous versions of the same
+            package. If you have not installed a package previously, the
+            upgrade operation will install the package.
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term>Freshen</term>
+        <listitem>
+          <para>
+            A freshen operation means to install a new version of a
+            package only if you have already installed another version
+            of the package.
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term>Install</term>
+        <listitem>
+          <para>
+            An install operation installs a package for the first time.
+            It also, through special command-line parameters, allows you
+            to install multiple versions of a package, usually not what
+            you want. So, in the vast majority of cases, you want to run
+            the upgrade operation for all package installations.
+          </para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
     <para>
       The following sections cover the command-line options that apply
       to these operations.
     </para>
     <sect2>
-      <title>Upgrading with the rpm command</title>
+      <title>Upgrading with the <command>rpm</command> command</title>
       <para/>
       <para>
-        Almost all installation steps use the rpm command with the ???U
-        option, short for upgrade, as introduced in
-        <xref linkend="ch-rpm-overview"/> . The basic syntax is:
+        Almost all installation steps use the <command>rpm</command>
+        command with the <option>???U</option> option, short for
+        upgrade, as introduced in <xref linkend="ch-rpm-overview"/> .
+        The basic syntax is:
       </para>
       <para>
-        rpm -U package_name
+        <command>rpm</command> <option>-U</option>
+        <replaceable>package_name</replaceable>
       </para>
       <para>
         For example:
       </para>
       <para>
-        rpm ???i jikes-1.16-1.i386.rpm
+<screen>
+<userinput>rpm ???i jikes-1.16-1.i386.rpm</userinput>
+</screen>
       </para>
       <para>
-        You can also use the --upgrade long option in place of -U.
+        You can also use the <option>--upgrade</option> long option in
+        place of <option>-U</option>.
[...2990 lines suppressed...]
+        <filename>rc</filename> settings.
+      </para>
+    </note>
+    <note>
+      <title>The <option>--showrc</option> Option</title>
+
+      <para>
+        See <xref linkend="ch-customizing-rpm"/> for more on the
+        <option>--showrc</option> option.
+      </para>
+    </note>
     <para>
-      /usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc:/etc/rpmrc:~/.rpmrc
-    </para>
-    <para>
-      Note
-    </para>
-    <para>
-      The ~/.rpmrc means to look in the user's home directory for a file
-      named .rpmrc.
-    </para>
-    <para>
-      You can use the --showrc option to list all the rc settings.
-    </para>
-    <para>
-      Cross Reference
-    </para>
-    <para>
-      See <xref linkend="ch-customizing-rpm"/> for more on the --showrc
-      option.
-    </para>
-    <para>
-      The --version option tells the rpm command to print out the
-      version number of the command and then exit. For example:
-    </para>
-    <para>
-      rpm --version
-    </para>
+      The <option>--version</option> option tells the
+      <command>rpm</command> command to print out the version number of
+      the command and then exit. For example:
+    </para>
+<screen>
+<userinput>rpm --version</userinput>
+</screen>
     <para>
       This command prints out a version number, like the following:
     </para>
+<screen>
+<computeroutput>RPM version 4.1</computeroutput>
+</screen>
     <para>
-      RPM version 4.1
-    </para>
-    <para>
-      The --dbpath option, mentioned previously, tells the rpm command
-      to use a different RPM database. This is useful when testing a
-      complete system install, where you want to change the RPM database
-      but don't want that to affect your running Linux system. In this
-      case, you can use a different RPM database and test out your
-      changes. The basic syntax for this option is:
+      The <option>--dbpath</option> option, mentioned previously, tells
+      the <command>rpm</command> command to use a different RPM
+      database. This is useful when testing a complete system install,
+      where you want to change the RPM database but don't want that to
+      affect your running Linux system. In this case, you can use a
+      different RPM database and test out your changes. The basic syntax
+      for this option is:
     </para>
     <para>
-      --dbpath directory_name
+      <option>--dbpath</option>
+      <replaceable>directory_name</replaceable>
     </para>
     <para>
-      The --pipe option tells the rpm command to send, or pipe, its
-      output to another program. The syntax for this option is:
+      The <option>--pipe</option> option tells the
+      <command>rpm</command> command to send, or pipe, its output to
+      another program. The syntax for this option is:
     </para>
     <para>
-      --pipe command_to_send_out_to
+      <option>--pipe</option>
+      <replaceable>command_to_send_out_to</replaceable>
     </para>
   </sect1>
   <sect1>
@@ -2035,40 +2023,38 @@
       common actions of installing, removing, and upgrading software.
     </para>
     <para>
-      The rpm ???e command removes packages. The rpm ???U command
+      The <command>rpm</command> <option>???e</option> command removes
+      packages. The <command>rpm</command> <option>???U</option> command
       upgrades packages by installing new packages and removing old
       versions of all the packages upgraded. RPM upgrades also work for
-      installing new packages. The rpm ???F command freshens packages.
-      This command only upgrades a package if an older version of the
-      package has already been installed. The rpm ???i command installs
-      packages.
-    </para>
-    <para>
-      Table 4-3 summarizes the rpm command-line options for installing,
-      removing, and upgrading packages.
+      installing new packages. The <command>rpm</command>
+      <option>???F</option> command freshens packages. This command only
+      upgrades a package if an older version of the package has already
+      been installed. The <command>rpm</command> <option>???i</option>
+      command installs packages.
     </para>
     <para>
-      Table 4-3 Installing, Removing, and Upgrading with the rpm command
-    </para>
-    <informaltable frame="all">
+      The table below summarizes the <command>rpm</command> command-line
+      options for installing, removing, and upgrading packages.
+    </para>
+    <table id="tb-rpm-command-options">
+      <title>Installing, Removing, and Upgrading with the <command>rpm</command>
+        command</title>
+      <colspec colnum="1" colname="Command"/>
+      <colspec colnum="2" colname="Usage"/>
       <tgroup cols="2">
-        <tbody>
+        <thead>
           <row>
-            <entry>
-              <para>
-                Command
-              </para>
-            </entry>
-            <entry>
-              <para>
-                Usage
-              </para>
-            </entry>
+            <entry>Command</entry>
+            <entry>Usage</entry>
           </row>
+        </thead>
+        <tbody>
           <row>
             <entry>
               <para>
-                rpm ???i install_options package_files
+                <command>rpm ???i <replaceable>install_options
+                package_files</replaceable></command>
               </para>
             </entry>
             <entry>
@@ -2080,7 +2066,8 @@
           <row>
             <entry>
               <para>
-                rpm ???e remove_options packages
+                <command>rpm ???e <replaceable>remove_options
+                packages</replaceable></command>
               </para>
             </entry>
             <entry>
@@ -2092,7 +2079,8 @@
           <row>
             <entry>
               <para>
-                rpm ???U install_options package_files
+                <command>rpm ???U <replaceable>install_options
+                package_files</replaceable></command>
               </para>
             </entry>
             <entry>
@@ -2105,7 +2093,8 @@
           <row>
             <entry>
               <para>
-                rpm ???Uvh install_options package_files
+                <command>rpm ???Uvh <replaceable>install_options
+                package_files</replaceable></command>
               </para>
             </entry>
             <entry>
@@ -2118,7 +2107,8 @@
           <row>
             <entry>
               <para>
-                rpm ???F install_options package_files
+                <command>rpm ???F <replaceable>install_options
+                package_files</replaceable></command>
               </para>
             </entry>
             <entry>
@@ -2129,7 +2119,7 @@
           </row>
         </tbody>
       </tgroup>
-    </informaltable>
+    </table>
     <para>
       Unfortunately, modern system management gets more complex than
       that. The next chapter delves into package dependencies and the



From fedora-docs-commits at redhat.com  Sun Nov 20 19:48:18 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 20 Nov 2005 14:48:18 -0500
Subject: install-guide fedora-install-guide-beginninginstallation-en.xml, 1.5,
	1.6 fedora-install-guide-intro-en.xml, 1.12, 1.13
Message-ID: <200511201948.jAKJmI2h024955@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24937

Modified Files:
	fedora-install-guide-beginninginstallation-en.xml 
	fedora-install-guide-intro-en.xml 
Log Message:
Beginning an attempt to make the IG's preface and opening chapters
into a better process flow for newbies.  This is a work in progress
and this commit, although it will build, is not the finished flow.  It
should give an idea of which way I'm heading with the revisions.  I'm
moving the information on preparing media to the preface, where we
handle "what you need to get started."  Then I am working on a
decision tree in the first couple of installation chapters to make it
easier for newbies to follow steps.  This is a difficult process due
to the multiplicity of options anaconda offers.  The FC4 version was
our best shot, and this one will hopefully improve on the last.




Index: fedora-install-guide-beginninginstallation-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-beginninginstallation-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-beginninginstallation-en.xml	27 May 2005 22:15:15 -0000	1.5
+++ fedora-install-guide-beginninginstallation-en.xml	20 Nov 2005 19:48:10 -0000	1.6
@@ -4,16 +4,23 @@
 
   <para>
     To begin installation of &FC;, boot the computer from the boot
-    media.  You may install from CD or DVD discs, USB pen drives, hard
-    drives, or network servers.
+    media.  The boot media provides the necessary programs and files to
+    start the installation program.  Once you start the installation
+    program, you may be able to install from a completely different
+    piece of media.
   </para>
 
-  <note>
-    <title>Installation from Diskettes</title>
+  <important>
+    <title>Choosing a Different Installation Source</title>
     <para>
-      There is no option to install &FC; from diskettes.
+      To choose a different source for installation, enter
+      <userinput>linux askmethod</userinput> at the
+      <computeroutput>boot:</computeroutput> prompt.  If you boot from
+      some types of media such as USB or the network, the installation
+      program <emphasis>always</emphasis> asks you to choose the
+      installation source.
     </para>
-  </note>
+  </important>
 
   <para>
     The <indexterm>
@@ -53,10 +60,10 @@
 
 
   <section id="sn-booting-from-disc">
-    <title>Booting from Disc</title>
+    <title>Booting from CD, DVD, or USB Media</title>
 
     <para>
-      To boot your computer from disc:
+      To boot your computer:
     </para>
 
     <procedure>
@@ -64,7 +71,8 @@
 	<para>Switch on the computer.</para>
       </step>
       <step>
-	<para>Insert the first disc into the CD or DVD drive.</para>
+	<para>Insert the first disc into the CD or DVD drive, or attach
+	  the USB media.</para>
       </step>
       <step>
 	<para>A boot screen appears, with a <prompt>boot:</prompt>
@@ -72,6 +80,15 @@
       </step>
     </procedure>
 
+    <note>
+      <title>BIOS Boot Order</title>
+      <para>
+	The BIOS contains settings that control the order of boot
+	devices.  If your PC boots from a device other than the &FC;
+	boot media, check the BIOS boot configuration.
+      </para>
+    </note>
+
     <figure id="fig-boot">
       <title>Boot Screen</title>
       <mediaobject>
@@ -127,90 +144,92 @@
 
     <para>
       When you issue a command at the <prompt>boot:</prompt> prompt, the
-      first stage of the installation program starts.  After it loads,
-      the following screen appears:
+      first stage of the installation program starts.
     </para>
 
-    <figure id="fig-media-test">
-      <title>Media Test Screen</title>
-      <mediaobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/media-test.eps" format="EPS"/>
-	</imageobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/media-test.png" format="PNG"/>
-	</imageobject>
-	<textobject>
-	  <phrase>
-	    Media test screen.
-	  </phrase>
-	</textobject>
-      </mediaobject>
-    </figure>
+    <section id="sn-media-testing">
+      <title>Testing CD and DVD Media</title>
 
-    <para>
-      Select <guibutton>OK</guibutton> to test the disc, or select
-      <guibutton>Skip</guibutton> to proceed with the installation
-      without testing the disc.
-    </para>
+      <figure id="fig-media-test">
+	<title>Media Test Screen</title>
+	<mediaobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/media-test.eps" format="EPS"/>
+	  </imageobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/media-test.png" format="PNG"/>
+	  </imageobject>
+	  <textobject>
+	    <phrase>
+	      Media test screen.
+	    </phrase>
+	  </textobject>
+	</mediaobject>
+      </figure>
 
-    <caution>
-      <title>Testing Discs</title>
       <para>
-	Test any discs which you have not previously tested.  A disc
-	error during the installation process may force you to restart
-	the entire procedure.
+	Select <guibutton>OK</guibutton> to test the disc, or select
+	<guibutton>Skip</guibutton> to proceed with the installation
+	without testing the disc.
       </para>
-    </caution>
 
-    <para>
-      After you test the first disc, another screen appears and shows
-      the result:
-    </para>
+      <caution>
+	<title>Testing Discs</title>
+	<para>
+	  Test any discs which you have not previously tested.  A disc
+	  error during the installation process may force you to restart
+	  the entire procedure.
+	</para>
+      </caution>
 
-    <figure id="fig-mediacheck-result">
-      <title>Media Check Result</title>
-      <mediaobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/mediacheck-result.eps" format="EPS"/>
-	</imageobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/mediacheck-result.png" format="PNG"/>
-	</imageobject>
-	<textobject>
-	  <phrase>
-	    Media check result.
-	  </phrase>
-	</textobject>
-      </mediaobject>
-    </figure>
+      <para>
+	After you test the first disc, another screen appears and shows
+	the result:
+      </para>
 
-    <para>
-      Select <guibutton>OK</guibutton>.  The following screen appears:
-    </para>
+      <figure id="fig-mediacheck-result">
+	<title>Media Check Result</title>
+	<mediaobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/mediacheck-result.eps" format="EPS"/>
+	  </imageobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/mediacheck-result.png" format="PNG"/>
+	  </imageobject>
+	  <textobject>
+	    <phrase>
+	      Media check result.
+	    </phrase>
+	  </textobject>
+	</mediaobject>
+      </figure>
 
-    <figure id="fig-mediacheck-next">
-      <title>Next Disc Screen</title>
-      <mediaobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/mediacheck-next.eps" format="EPS"/>
-	</imageobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/mediacheck-next.png" format="PNG"/>
-	</imageobject>
-	<textobject>
-	  <phrase>
-	    Next disc or continue.
-	  </phrase>
-	</textobject>
-      </mediaobject>
-    </figure>
+      <para>
+	Select <guibutton>OK</guibutton>.  The following screen appears:
+      </para>
 
-    <para>
-      Select <guibutton>Test</guibutton> to test the next disc in the
-      set, or <guibutton>Continue</guibutton> to proceed with the
-      installation.
-    </para>
+      <figure id="fig-mediacheck-next">
+	<title>Next Disc Screen</title>
+	<mediaobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/mediacheck-next.eps" format="EPS"/>
+	  </imageobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/mediacheck-next.png" format="PNG"/>
+	  </imageobject>
+	  <textobject>
+	    <phrase>
+	      Next disc or continue.
+	    </phrase>
+	  </textobject>
+	</mediaobject>
+      </figure>
+
+      <para>
+	Select <guibutton>Test</guibutton> to test the next disc in the
+	set, or <guibutton>Continue</guibutton> to proceed with the
+	installation.
+      </para>
 
 <!--
 
@@ -239,34 +258,15 @@
 
 -->
 
+    </section>
+
+
     <para>
       After you test your discs and select
       <guibutton>Continue</guibutton>, or if you choose to skip testing,
       the main graphical installation program loads.
     </para>
 
-    <para>
-      To boot from the disc, but install from another device or a
-      network server, use the <userinput>linux askmethod</userinput>
-      command at the <prompt>boot:</prompt> prompt.  &FC; also includes
-      a boot-only CD for this purpose, which is stored on the first &FC;
-      installation disc as an ISO file,
-      <filename>images/boot.iso</filename>.
-    </para>
-
-    <para>
-      To convert the ISO file into a physical CD, use the option in your
-      CD-writing program that burns a CD image file to a CD.  If you
-      copy the file itself to a CD instead, the disc will not boot or
-      work correctly.  Refer to your CD writing program documentation
-      for instructions.  If you are using Linux, use the following
-      command to burn a CD image file to a blank recordable CD:
-    </para>
-
-<screen>
-<userinput>cdrecord --device=<replaceable>cdwriter-device</replaceable> -tao -eject <replaceable>image-file.iso</replaceable></userinput>
-</screen>
-
     <note>
       <title>BIOS Boot Order</title>
       <para>
@@ -279,123 +279,6 @@
   </section>
 
 
-  <section id="sn-using-otherbootmedia">
-    <title>Using Other Removable Media</title>
-
-    <para>
-      To use a USB device such as a pen drive or Compact Flash card as
-      boot media, write the supplied image file to the device.  The
-      media must be large enough to contain the image.
-    </para>
-
-
-    <section id="sn-preparing-otherbootmedia">
-      <title>Preparing the Boot Media</title>
-
-      <warning>
-	<title>Data Loss</title>
-	<para>
-	  <emphasis>This procedure destroys data on the
-	    media.</emphasis> Back up any important information before
-	  you begin.  Some models of USB media use additional partitions
-	  or software to provide functions such as encryption.  This
-	  procedure may make it difficult or impossible to access these
-	  special areas on your boot media.
-	</para>
-      </warning>
-
-      <para>
-	The <filename>images/diskboot.img</filename> file on the first
-	&FC; installation disc is a boot image designed for USB media.
-	This file also appears on FTP and Web sites providing &FC;.
-      </para>
-
-      <para>
-	Several software utilities are available for Windows and Linux
-	that can write image files to a device.  Linux includes the
-	<command>dd</command> command for this purpose.  To write an
-	image file to boot media with <command>dd</command> on a current
-	version of &FC;:
-      </para>
-
-      <procedure>
-	<step>
-	  <para>
-	    Locate the image file.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    Attach or insert the media.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    Your system may automatically detect and open the media.  If
-	    that happens, close or unmount the media before continuing.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    Open a terminal window.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    In the terminal window, type the following command:
-
-<screen>
-<userinput>dd if=diskboot.img of=/dev/sda1</userinput>
-</screen>
-
-	  </para>
-	</step>
-      </procedure>
-
-    </section>
-
-
-    <section id="sn-booting-from-otherbootmedia">
-      <title>Booting from the Media</title>
-
-      <para>
-	Boot your computer with the prepared media:
-      </para>
-
-      <procedure>
-	<step>
-          <para>
-	    Attach or insert the media.
-	  </para>
-	</step>
-	<step>
-          <para>
-	    Switch on the computer.
-	  </para>
-	</step>
-	<step>
-          <para>
-	    A boot screen appears, with a <prompt>boot:</prompt> prompt
-	    at the bottom.  To begin, simply press the
-	    <keycap>Enter</keycap> key.
-	  </para>
-	</step>
-      </procedure>
-
-      <note>
-	<title>BIOS Boot Order</title>
-	<para>
-	  The BIOS contains settings that control the order of boot
-	  devices.  If your PC boots from a device other than the &FC;
-	  boot media, check the BIOS boot configuration.
-	</para>
-      </note>
-
-    </section>
-
-  </section>
-
-
   <section id="sn-booting-from-pxe">
     <title>Booting from the Network using PXE</title>
 
@@ -476,7 +359,6 @@
 
   </section>
 
-
 </chapter>
 
 <!--


Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- fedora-install-guide-intro-en.xml	12 Jun 2005 08:59:53 -0000	1.12
+++ fedora-install-guide-intro-en.xml	20 Nov 2005 19:48:10 -0000	1.13
@@ -277,6 +277,173 @@
     </section>
 
   </section>
+
+  <section id="sn-preparing-media">
+    <title>Preparing Media</title>
+
+    <para>
+      The types of boot media for &FED; include:
+    </para>
+
+    <itemizedlist>
+      <listitem>
+	<para>
+	  CD or DVD media (either installation disc #1 or a special
+	  boot-only disc)
+	</para>
+      </listitem>
+      <listitem>
+	<para>
+	  USB media
+	</para>
+      </listitem>
+      <listitem>
+	<para>
+	  Network interface (via PXE)
+	</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>
+      The types of installation source media for &FED; include:
+    </para>
+
+    <itemizedlist>
+      <listitem>
+	<para>
+	  CD or DVD media installation discs
+	</para>
+      </listitem>
+      <listitem>
+	<para>
+	  Hard disk
+	</para>
+      </listitem>
+      <listitem>
+	<para>
+	  Network installation tree via HTTP, FTP, or NFS
+	</para>
+      </listitem>
+    </itemizedlist>
+
+    <note>
+      <title>Installation from Diskettes</title>
+      <para>
+	There is no option to install &FC; from diskettes.
+      </para>
+    </note>
+
+    <para>
+      The &FC; distribution includes <firstterm>image files</firstterm>
+      for boot-only CD or DVD media and USB media. These files can be
+      converted into bootable media using standard Linux utilities or
+      third-party programs on other operating systems.
+    </para>
+
+    <note>
+      <title>CD or DVD Installation Media</title>
+      <para>
+	You may also use the first CD or DVD disc from the complete &FC;
+	distribution as boot media.  For instructions to download and
+	prepare this media, refer to <ulink
+	  url="http://fedora.redhat.com/download/"/>.  If you already
+	have the full set of &FC;, skip to <xref
+	linkend="sn-booting-from-disc"/>.
+      </para>
+    </note>
+
+    <section id="sn-preparing-cd-or-dvd-media">
+      <title>Preparing CD or DVD Boot Disc</title>
+
+      <para>
+	The <filename>images/boot.iso</filename> file on the first &FC;
+	installation disc is a boot image designed for CD and DVD media.
+	This file also appears on FTP and Web sites providing &FC;.
+      </para>
+
+      <para>
+	To convert the ISO file into a physical CD, use the option in
+	your CD-writing program that burns a CD image file to a CD. If
+	you copy the file itself to a CD instead, the disc will not boot
+	or work correctly.  Refer to your CD writing program
+	documentation for instructions.  If you are using Linux, use the
+	following command to burn a CD image file to a blank recordable
+	CD:
+      </para>
+
+<screen>
+<userinput>cdrecord --device=<replaceable>cdwriter-device</replaceable> -tao -eject <replaceable>image-file.iso</replaceable></userinput>
+</screen>
+
+    </section>
+    
+    <section id="sn-preparing-usb-media">
+      <title>Preparing USB Boot Media</title>
+
+      <warning>
+	<title>Data Loss</title>
+	<para>
+	  <emphasis>This procedure destroys data on the
+	    media.</emphasis> Back up any important information before
+	  you begin.  Some models of USB media use additional partitions
+	  or software to provide functions such as encryption.  This
+	  procedure may make it difficult or impossible to access these
+	  special areas on your boot media.
+	</para>
+      </warning>
+
+      <para>
+	The <filename>images/diskboot.img</filename> file on the first
+	&FC; installation disc is a boot image designed for USB media.
+	This file also appears on FTP and Web sites providing &FC;.
+      </para>
+
+      <para>
+	Several software utilities are available for Windows and Linux
+	that can write image files to a device.  Linux includes the
+	<command>dd</command> command for this purpose.  To write an
+	image file to boot media with <command>dd</command> on a current
+	version of &FC;:
+      </para>
+
+      <procedure>
+	<step>
+	  <para>
+	    Locate the image file.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    Attach or insert the media.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    Your system may automatically detect and open the media. If
+	    that happens, close or unmount the media before continuing.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    Open a terminal window.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    In the terminal window, type the following command:
+	  </para>
+
+<screen>
+<userinput>dd if=diskboot.img of=/dev/sda1</userinput>
+</screen>
+
+	</step>
+      </procedure>
+
+    </section>
+
+  </section>
+
   
 </preface>
 



From fedora-docs-commits at redhat.com  Sun Nov 20 19:51:38 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 20 Nov 2005 14:51:38 -0500
Subject: install-guide fedora-install-guide-intro-en.xml,1.13,1.14
Message-ID: <200511201951.jAKJpcnq025001@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24984

Modified Files:
	fedora-install-guide-intro-en.xml 
Log Message:
Replace draftnotice since it looks like we're getting started on FC5
version at this point.  Also comment out a seemingly out-of-place
section in the intro.  Any disagreements?




Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- fedora-install-guide-intro-en.xml	20 Nov 2005 19:48:10 -0000	1.13
+++ fedora-install-guide-intro-en.xml	20 Nov 2005 19:51:31 -0000	1.14
@@ -2,8 +2,8 @@
 <preface id="ch-intro">
   <title>Introduction</title>
 
-  <!--  removed until we begin working on the FC5 version
-  &DRAFTNOTICE;  -->
+<!--  removed until we begin working on the FC5 version -->
+  &DRAFTNOTICE;
 
   <para>
     &FC; is a complete desktop and server operating system created
@@ -175,6 +175,10 @@
 
     </section>
     
+<!--
+
+    Is it just me, or is this section really out of place? [PWF]
+
     <section id="sn-installing-asaserver">
       <title>Installing &FC; as a Server</title>
       
@@ -190,6 +194,7 @@
 
     </section>
 
+-->
 
     <section id="sn-installing-networkinstallation">
       <title>Installing from a Network Server</title>



From fedora-docs-commits at redhat.com  Sun Nov 20 19:55:40 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 20 Nov 2005 14:55:40 -0500
Subject: install-guide fedora-install-guide-intro-en.xml,1.14,1.15
Message-ID: <200511201955.jAKJteLx025048@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25031

Modified Files:
	fedora-install-guide-intro-en.xml 
Log Message:
Moved to BUG-REPORTING entity instead of DRAFTNOTICE since we use components instead of single bug numbers now


Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- fedora-install-guide-intro-en.xml	20 Nov 2005 19:51:31 -0000	1.14
+++ fedora-install-guide-intro-en.xml	20 Nov 2005 19:55:32 -0000	1.15
@@ -3,7 +3,7 @@
   <title>Introduction</title>
 
 <!--  removed until we begin working on the FC5 version -->
-  &DRAFTNOTICE;
+  &BUG-REPORTING;
 
   <para>
     &FC; is a complete desktop and server operating system created



From fedora-docs-commits at redhat.com  Sun Nov 20 22:06:49 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 20 Nov 2005 17:06:49 -0500
Subject: install-guide fedora-install-guide-beginninginstallation-en.xml, 1.6,
	1.7 fedora-install-guide-en.xml, 1.19, 1.20
Message-ID: <200511202206.jAKM6nYE030606@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30582

Modified Files:
	fedora-install-guide-beginninginstallation-en.xml 
	fedora-install-guide-en.xml 
Log Message:
Time to change some entities.  FCLOCALVER incremented since it looks
like we're gearing up for FC5.  Changed up a couple of others to beat
a path to the new standards.




Index: fedora-install-guide-beginninginstallation-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-beginninginstallation-en.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-beginninginstallation-en.xml	20 Nov 2005 19:48:10 -0000	1.6
+++ fedora-install-guide-beginninginstallation-en.xml	20 Nov 2005 22:06:30 -0000	1.7
@@ -108,11 +108,13 @@
 
     <para>
       If you hit <keycap>Enter</keycap>, the installation runs in
-      default mode.  In the default mode, the installation runs from CD
-      or DVD discs, and uses a graphical interface if possible. To
-      change the installation mode, at the <prompt>boot:</prompt>
-      prompt, type <userinput>linux</userinput> followed by one or more
-      of the following options:
+      default mode.  In the default mode, the installation uses a
+      graphical interface if possible.  If the installation program runs
+      from the &FC; installation CD or DVD media, in default mode it
+      uses these media as the installation source.  To change the
+      installation mode, at the <prompt>boot:</prompt> prompt, type
+      <userinput>linux</userinput> followed by one or more of the
+      following options:
     </para>
     <itemizedlist>
       <listitem>
@@ -131,7 +133,9 @@
 	<para>
 	  To retry installation because the installation aborted at an
 	  early stage, add the directive
-	  <userinput>acpi=off</userinput>.
+	  <userinput>acpi=off</userinput>.  ACPI is responsible for many
+	  kinds of installation errors.  If you turn ACPI off, you may
+	  be able to overcome some of these errors.
 	</para>
       </listitem>
     </itemizedlist>


Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- fedora-install-guide-en.xml	14 Jun 2005 22:36:46 -0000	1.19
+++ fedora-install-guide-en.xml	20 Nov 2005 22:06:30 -0000	1.20
@@ -4,17 +4,18 @@
 <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
 %FEDORA-ENTITIES-EN;
 
-<!ENTITY VERSION "1.0"> <!-- version for this document -->
-
-<!ENTITY BOOKID "fedora-install-guide-en-&VERSION; (2005-06-10-T16:20-0700)"> <!-- change date here and VERSION entity everytime a change is made-->
+<!ENTITY DOCNAME "fedora-install-guide">
+<!ENTITY DOCLANG "en">
+<!ENTITY DOCVERSION "1.01rc">
+<!ENTITY DOCDATE "2005-11-20">
+<!ENTITY BOOKID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)">
 
 <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
 
 <!-- Bugzilla bug number for the draft notice -->
 <!ENTITY BUG-NUM "129911">
-<!ENTITY FCLOCALVER "4">
-<!ENTITY DOCLOCALVER "1.0">
-<!ENTITY DRAFTNOTICE SYSTEM "../docs-common/common/draftnotice-en.xml">
+<!ENTITY FCLOCALVER "5">
+<!ENTITY DOCLOCALVER "1.0"> <!-- what's this for again? -->
 
 
 <!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-en.xml">



From fedora-docs-commits at redhat.com  Sun Nov 20 22:41:19 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 20 Nov 2005 17:41:19 -0500
Subject: install-guide fedora-install-guide-beginninginstallation-en.xml, 1.7,
	1.8 fedora-install-guide-en.xml, 1.20,
	1.21 fedora-install-guide-intro-en.xml, 1.15, 1.16
Message-ID: <200511202241.jAKMfJc9030965@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30946

Modified Files:
	fedora-install-guide-beginninginstallation-en.xml 
	fedora-install-guide-en.xml fedora-install-guide-intro-en.xml 
Log Message:
Bugger.  I need to back out these changes and then branch the IG to
FC5 before reinstituting them.  Sorry for the trouble.




Index: fedora-install-guide-beginninginstallation-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-beginninginstallation-en.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-beginninginstallation-en.xml	20 Nov 2005 22:06:30 -0000	1.7
+++ fedora-install-guide-beginninginstallation-en.xml	20 Nov 2005 22:41:12 -0000	1.8
@@ -4,23 +4,16 @@
 
   <para>
     To begin installation of &FC;, boot the computer from the boot
-    media.  The boot media provides the necessary programs and files to
-    start the installation program.  Once you start the installation
-    program, you may be able to install from a completely different
-    piece of media.
+    media.  You may install from CD or DVD discs, USB pen drives, hard
+    drives, or network servers.
   </para>
 
-  <important>
-    <title>Choosing a Different Installation Source</title>
+  <note>
+    <title>Installation from Diskettes</title>
     <para>
-      To choose a different source for installation, enter
-      <userinput>linux askmethod</userinput> at the
-      <computeroutput>boot:</computeroutput> prompt.  If you boot from
-      some types of media such as USB or the network, the installation
-      program <emphasis>always</emphasis> asks you to choose the
-      installation source.
+      There is no option to install &FC; from diskettes.
     </para>
-  </important>
+  </note>
 
   <para>
     The <indexterm>
@@ -60,10 +53,10 @@
 
 
   <section id="sn-booting-from-disc">
-    <title>Booting from CD, DVD, or USB Media</title>
+    <title>Booting from Disc</title>
 
     <para>
-      To boot your computer:
+      To boot your computer from disc:
     </para>
 
     <procedure>
@@ -71,8 +64,7 @@
 	<para>Switch on the computer.</para>
       </step>
       <step>
-	<para>Insert the first disc into the CD or DVD drive, or attach
-	  the USB media.</para>
+	<para>Insert the first disc into the CD or DVD drive.</para>
       </step>
       <step>
 	<para>A boot screen appears, with a <prompt>boot:</prompt>
@@ -80,15 +72,6 @@
       </step>
     </procedure>
 
-    <note>
-      <title>BIOS Boot Order</title>
-      <para>
-	The BIOS contains settings that control the order of boot
-	devices.  If your PC boots from a device other than the &FC;
-	boot media, check the BIOS boot configuration.
-      </para>
-    </note>
-
     <figure id="fig-boot">
       <title>Boot Screen</title>
       <mediaobject>
@@ -108,13 +91,11 @@
 
     <para>
       If you hit <keycap>Enter</keycap>, the installation runs in
-      default mode.  In the default mode, the installation uses a
-      graphical interface if possible.  If the installation program runs
-      from the &FC; installation CD or DVD media, in default mode it
-      uses these media as the installation source.  To change the
-      installation mode, at the <prompt>boot:</prompt> prompt, type
-      <userinput>linux</userinput> followed by one or more of the
-      following options:
+      default mode.  In the default mode, the installation runs from CD
+      or DVD discs, and uses a graphical interface if possible. To
+      change the installation mode, at the <prompt>boot:</prompt>
+      prompt, type <userinput>linux</userinput> followed by one or more
+      of the following options:
     </para>
     <itemizedlist>
       <listitem>
@@ -133,9 +114,7 @@
 	<para>
 	  To retry installation because the installation aborted at an
 	  early stage, add the directive
-	  <userinput>acpi=off</userinput>.  ACPI is responsible for many
-	  kinds of installation errors.  If you turn ACPI off, you may
-	  be able to overcome some of these errors.
+	  <userinput>acpi=off</userinput>.
 	</para>
       </listitem>
     </itemizedlist>
@@ -148,92 +127,90 @@
 
     <para>
       When you issue a command at the <prompt>boot:</prompt> prompt, the
-      first stage of the installation program starts.
+      first stage of the installation program starts.  After it loads,
+      the following screen appears:
     </para>
 
-    <section id="sn-media-testing">
-      <title>Testing CD and DVD Media</title>
+    <figure id="fig-media-test">
+      <title>Media Test Screen</title>
+      <mediaobject>
+	<imageobject>
+	  <imagedata align="center" fileref="./figs/media-test.eps" format="EPS"/>
+	</imageobject>
+	<imageobject>
+	  <imagedata align="center" fileref="./figs/media-test.png" format="PNG"/>
+	</imageobject>
+	<textobject>
+	  <phrase>
+	    Media test screen.
+	  </phrase>
+	</textobject>
+      </mediaobject>
+    </figure>
 
-      <figure id="fig-media-test">
-	<title>Media Test Screen</title>
-	<mediaobject>
-	  <imageobject>
-	    <imagedata align="center" fileref="./figs/media-test.eps" format="EPS"/>
-	  </imageobject>
-	  <imageobject>
-	    <imagedata align="center" fileref="./figs/media-test.png" format="PNG"/>
-	  </imageobject>
-	  <textobject>
-	    <phrase>
-	      Media test screen.
-	    </phrase>
-	  </textobject>
-	</mediaobject>
-      </figure>
+    <para>
+      Select <guibutton>OK</guibutton> to test the disc, or select
+      <guibutton>Skip</guibutton> to proceed with the installation
+      without testing the disc.
+    </para>
 
+    <caution>
+      <title>Testing Discs</title>
       <para>
-	Select <guibutton>OK</guibutton> to test the disc, or select
-	<guibutton>Skip</guibutton> to proceed with the installation
-	without testing the disc.
+	Test any discs which you have not previously tested.  A disc
+	error during the installation process may force you to restart
+	the entire procedure.
       </para>
+    </caution>
 
-      <caution>
-	<title>Testing Discs</title>
-	<para>
-	  Test any discs which you have not previously tested.  A disc
-	  error during the installation process may force you to restart
-	  the entire procedure.
-	</para>
-      </caution>
-
-      <para>
-	After you test the first disc, another screen appears and shows
-	the result:
-      </para>
+    <para>
+      After you test the first disc, another screen appears and shows
+      the result:
+    </para>
 
-      <figure id="fig-mediacheck-result">
-	<title>Media Check Result</title>
-	<mediaobject>
-	  <imageobject>
-	    <imagedata align="center" fileref="./figs/mediacheck-result.eps" format="EPS"/>
-	  </imageobject>
-	  <imageobject>
-	    <imagedata align="center" fileref="./figs/mediacheck-result.png" format="PNG"/>
-	  </imageobject>
-	  <textobject>
-	    <phrase>
-	      Media check result.
-	    </phrase>
-	  </textobject>
-	</mediaobject>
-      </figure>
+    <figure id="fig-mediacheck-result">
+      <title>Media Check Result</title>
+      <mediaobject>
+	<imageobject>
+	  <imagedata align="center" fileref="./figs/mediacheck-result.eps" format="EPS"/>
+	</imageobject>
+	<imageobject>
+	  <imagedata align="center" fileref="./figs/mediacheck-result.png" format="PNG"/>
+	</imageobject>
+	<textobject>
+	  <phrase>
+	    Media check result.
+	  </phrase>
+	</textobject>
+      </mediaobject>
+    </figure>
 
-      <para>
-	Select <guibutton>OK</guibutton>.  The following screen appears:
-      </para>
+    <para>
+      Select <guibutton>OK</guibutton>.  The following screen appears:
+    </para>
 
-      <figure id="fig-mediacheck-next">
-	<title>Next Disc Screen</title>
-	<mediaobject>
-	  <imageobject>
-	    <imagedata align="center" fileref="./figs/mediacheck-next.eps" format="EPS"/>
-	  </imageobject>
-	  <imageobject>
-	    <imagedata align="center" fileref="./figs/mediacheck-next.png" format="PNG"/>
-	  </imageobject>
-	  <textobject>
-	    <phrase>
-	      Next disc or continue.
-	    </phrase>
-	  </textobject>
-	</mediaobject>
-      </figure>
+    <figure id="fig-mediacheck-next">
+      <title>Next Disc Screen</title>
+      <mediaobject>
+	<imageobject>
+	  <imagedata align="center" fileref="./figs/mediacheck-next.eps" format="EPS"/>
+	</imageobject>
+	<imageobject>
+	  <imagedata align="center" fileref="./figs/mediacheck-next.png" format="PNG"/>
+	</imageobject>
+	<textobject>
+	  <phrase>
+	    Next disc or continue.
+	  </phrase>
+	</textobject>
+      </mediaobject>
+    </figure>
 
-      <para>
-	Select <guibutton>Test</guibutton> to test the next disc in the
-	set, or <guibutton>Continue</guibutton> to proceed with the
-	installation.
-      </para>
+    <para>
+      Select <guibutton>Test</guibutton> to test the next disc in the
+      set, or <guibutton>Continue</guibutton> to proceed with the
+      installation.
+    </para>
 
 <!--
 
@@ -262,15 +239,34 @@
 
 -->
 
-    </section>
-
-
     <para>
       After you test your discs and select
       <guibutton>Continue</guibutton>, or if you choose to skip testing,
       the main graphical installation program loads.
     </para>
 
+    <para>
+      To boot from the disc, but install from another device or a
+      network server, use the <userinput>linux askmethod</userinput>
+      command at the <prompt>boot:</prompt> prompt.  &FC; also includes
+      a boot-only CD for this purpose, which is stored on the first &FC;
+      installation disc as an ISO file,
+      <filename>images/boot.iso</filename>.
+    </para>
+
+    <para>
+      To convert the ISO file into a physical CD, use the option in your
+      CD-writing program that burns a CD image file to a CD.  If you
+      copy the file itself to a CD instead, the disc will not boot or
+      work correctly.  Refer to your CD writing program documentation
+      for instructions.  If you are using Linux, use the following
+      command to burn a CD image file to a blank recordable CD:
+    </para>
+
+<screen>
+<userinput>cdrecord --device=<replaceable>cdwriter-device</replaceable> -tao -eject <replaceable>image-file.iso</replaceable></userinput>
+</screen>
+
     <note>
       <title>BIOS Boot Order</title>
       <para>
@@ -283,6 +279,123 @@
   </section>
 
 
+  <section id="sn-using-otherbootmedia">
+    <title>Using Other Removable Media</title>
+
+    <para>
+      To use a USB device such as a pen drive or Compact Flash card as
+      boot media, write the supplied image file to the device.  The
+      media must be large enough to contain the image.
+    </para>
+
+
+    <section id="sn-preparing-otherbootmedia">
+      <title>Preparing the Boot Media</title>
+
+      <warning>
+	<title>Data Loss</title>
+	<para>
+	  <emphasis>This procedure destroys data on the
+	    media.</emphasis> Back up any important information before
+	  you begin.  Some models of USB media use additional partitions
+	  or software to provide functions such as encryption.  This
+	  procedure may make it difficult or impossible to access these
+	  special areas on your boot media.
+	</para>
+      </warning>
+
+      <para>
+	The <filename>images/diskboot.img</filename> file on the first
+	&FC; installation disc is a boot image designed for USB media.
+	This file also appears on FTP and Web sites providing &FC;.
+      </para>
+
+      <para>
+	Several software utilities are available for Windows and Linux
+	that can write image files to a device.  Linux includes the
+	<command>dd</command> command for this purpose.  To write an
+	image file to boot media with <command>dd</command> on a current
+	version of &FC;:
+      </para>
+
+      <procedure>
+	<step>
+	  <para>
+	    Locate the image file.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    Attach or insert the media.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    Your system may automatically detect and open the media.  If
+	    that happens, close or unmount the media before continuing.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    Open a terminal window.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    In the terminal window, type the following command:
+
+<screen>
+<userinput>dd if=diskboot.img of=/dev/sda1</userinput>
+</screen>
+
+	  </para>
+	</step>
+      </procedure>
+
+    </section>
+
+
+    <section id="sn-booting-from-otherbootmedia">
+      <title>Booting from the Media</title>
+
+      <para>
+	Boot your computer with the prepared media:
+      </para>
+
+      <procedure>
+	<step>
+          <para>
+	    Attach or insert the media.
+	  </para>
+	</step>
+	<step>
+          <para>
+	    Switch on the computer.
+	  </para>
+	</step>
+	<step>
+          <para>
+	    A boot screen appears, with a <prompt>boot:</prompt> prompt
+	    at the bottom.  To begin, simply press the
+	    <keycap>Enter</keycap> key.
+	  </para>
+	</step>
+      </procedure>
+
+      <note>
+	<title>BIOS Boot Order</title>
+	<para>
+	  The BIOS contains settings that control the order of boot
+	  devices.  If your PC boots from a device other than the &FC;
+	  boot media, check the BIOS boot configuration.
+	</para>
+      </note>
+
+    </section>
+
+  </section>
+
+
   <section id="sn-booting-from-pxe">
     <title>Booting from the Network using PXE</title>
 
@@ -363,6 +476,7 @@
 
   </section>
 
+
 </chapter>
 
 <!--


Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- fedora-install-guide-en.xml	20 Nov 2005 22:06:30 -0000	1.20
+++ fedora-install-guide-en.xml	20 Nov 2005 22:41:12 -0000	1.21
@@ -4,18 +4,17 @@
 <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
 %FEDORA-ENTITIES-EN;
 
-<!ENTITY DOCNAME "fedora-install-guide">
-<!ENTITY DOCLANG "en">
-<!ENTITY DOCVERSION "1.01rc">
-<!ENTITY DOCDATE "2005-11-20">
-<!ENTITY BOOKID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)">
+<!ENTITY VERSION "1.0"> <!-- version for this document -->
+
+<!ENTITY BOOKID "fedora-install-guide-en-&VERSION; (2005-06-10-T16:20-0700)"> <!-- change date here and VERSION entity everytime a change is made-->
 
 <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
 
 <!-- Bugzilla bug number for the draft notice -->
 <!ENTITY BUG-NUM "129911">
-<!ENTITY FCLOCALVER "5">
-<!ENTITY DOCLOCALVER "1.0"> <!-- what's this for again? -->
+<!ENTITY FCLOCALVER "4">
+<!ENTITY DOCLOCALVER "1.0">
+<!ENTITY DRAFTNOTICE SYSTEM "../docs-common/common/draftnotice-en.xml">
 
 
 <!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-en.xml">


Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- fedora-install-guide-intro-en.xml	20 Nov 2005 19:55:32 -0000	1.15
+++ fedora-install-guide-intro-en.xml	20 Nov 2005 22:41:12 -0000	1.16
@@ -2,8 +2,8 @@
 <preface id="ch-intro">
   <title>Introduction</title>
 
-<!--  removed until we begin working on the FC5 version -->
-  &BUG-REPORTING;
+  <!--  removed until we begin working on the FC5 version
+  &DRAFTNOTICE;  -->
 
   <para>
     &FC; is a complete desktop and server operating system created
@@ -175,10 +175,6 @@
 
     </section>
     
-<!--
-
-    Is it just me, or is this section really out of place? [PWF]
-
     <section id="sn-installing-asaserver">
       <title>Installing &FC; as a Server</title>
       
@@ -194,7 +190,6 @@
 
     </section>
 
--->
 
     <section id="sn-installing-networkinstallation">
       <title>Installing from a Network Server</title>
@@ -282,173 +277,6 @@
     </section>
 
   </section>
-
-  <section id="sn-preparing-media">
-    <title>Preparing Media</title>
-
-    <para>
-      The types of boot media for &FED; include:
-    </para>
-
-    <itemizedlist>
-      <listitem>
-	<para>
-	  CD or DVD media (either installation disc #1 or a special
-	  boot-only disc)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  USB media
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Network interface (via PXE)
-	</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>
-      The types of installation source media for &FED; include:
-    </para>
-
-    <itemizedlist>
-      <listitem>
-	<para>
-	  CD or DVD media installation discs
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Hard disk
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Network installation tree via HTTP, FTP, or NFS
-	</para>
-      </listitem>
-    </itemizedlist>
-
-    <note>
-      <title>Installation from Diskettes</title>
-      <para>
-	There is no option to install &FC; from diskettes.
-      </para>
-    </note>
-
-    <para>
-      The &FC; distribution includes <firstterm>image files</firstterm>
-      for boot-only CD or DVD media and USB media. These files can be
-      converted into bootable media using standard Linux utilities or
-      third-party programs on other operating systems.
-    </para>
-
-    <note>
-      <title>CD or DVD Installation Media</title>
-      <para>
-	You may also use the first CD or DVD disc from the complete &FC;
-	distribution as boot media.  For instructions to download and
-	prepare this media, refer to <ulink
-	  url="http://fedora.redhat.com/download/"/>.  If you already
-	have the full set of &FC;, skip to <xref
-	linkend="sn-booting-from-disc"/>.
-      </para>
-    </note>
-
-    <section id="sn-preparing-cd-or-dvd-media">
-      <title>Preparing CD or DVD Boot Disc</title>
-
-      <para>
-	The <filename>images/boot.iso</filename> file on the first &FC;
-	installation disc is a boot image designed for CD and DVD media.
-	This file also appears on FTP and Web sites providing &FC;.
-      </para>
-
-      <para>
-	To convert the ISO file into a physical CD, use the option in
-	your CD-writing program that burns a CD image file to a CD. If
-	you copy the file itself to a CD instead, the disc will not boot
-	or work correctly.  Refer to your CD writing program
-	documentation for instructions.  If you are using Linux, use the
-	following command to burn a CD image file to a blank recordable
-	CD:
-      </para>
-
-<screen>
-<userinput>cdrecord --device=<replaceable>cdwriter-device</replaceable> -tao -eject <replaceable>image-file.iso</replaceable></userinput>
-</screen>
-
-    </section>
-    
-    <section id="sn-preparing-usb-media">
-      <title>Preparing USB Boot Media</title>
-
-      <warning>
-	<title>Data Loss</title>
-	<para>
-	  <emphasis>This procedure destroys data on the
-	    media.</emphasis> Back up any important information before
-	  you begin.  Some models of USB media use additional partitions
-	  or software to provide functions such as encryption.  This
-	  procedure may make it difficult or impossible to access these
-	  special areas on your boot media.
-	</para>
-      </warning>
-
-      <para>
-	The <filename>images/diskboot.img</filename> file on the first
-	&FC; installation disc is a boot image designed for USB media.
-	This file also appears on FTP and Web sites providing &FC;.
-      </para>
-
-      <para>
-	Several software utilities are available for Windows and Linux
-	that can write image files to a device.  Linux includes the
-	<command>dd</command> command for this purpose.  To write an
-	image file to boot media with <command>dd</command> on a current
-	version of &FC;:
-      </para>
-
-      <procedure>
-	<step>
-	  <para>
-	    Locate the image file.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    Attach or insert the media.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    Your system may automatically detect and open the media. If
-	    that happens, close or unmount the media before continuing.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    Open a terminal window.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    In the terminal window, type the following command:
-	  </para>
-
-<screen>
-<userinput>dd if=diskboot.img of=/dev/sda1</userinput>
-</screen>
-
-	</step>
-      </procedure>
-
-    </section>
-
-  </section>
-
   
 </preface>
 



From fedora-docs-commits at redhat.com  Mon Nov 21 00:38:05 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 20 Nov 2005 19:38:05 -0500
Subject: docs-common/packaging fedora-doc.omf.in.common, 1.1,
	1.2 fedora-doc.spec.in.common, 1.1, 1.2
Message-ID: <200511210038.jAL0c51F002571@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2552

Modified Files:
	fedora-doc.omf.in.common fedora-doc.spec.in.common 
Log Message:
Minor tweaks only... make sure OMF references correct category for yelp, etc.


Index: fedora-doc.omf.in.common
===================================================================
RCS file: /cvs/docs/docs-common/packaging/fedora-doc.omf.in.common,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-doc.omf.in.common	3 Oct 2005 02:32:06 -0000	1.1
+++ fedora-doc.omf.in.common	21 Nov 2005 00:37:58 -0000	1.2
@@ -14,7 +14,7 @@
       @DATE@
     </date>
     <version identifier="@VERSION@" date="@DATE@" description="@DOCBASE at -@VERSION@ (@DATE@)"/>
-    <subject category="System|Other"/>
+    <subject category="General|Linux|Distributions|Other"/>
     <description>
       Official Fedora Documentation: @TITLE@
     </description>


Index: fedora-doc.spec.in.common
===================================================================
RCS file: /cvs/docs/docs-common/packaging/fedora-doc.spec.in.common,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-doc.spec.in.common	3 Oct 2005 02:32:06 -0000	1.1
+++ fedora-doc.spec.in.common	21 Nov 2005 00:37:58 -0000	1.2
@@ -25,8 +25,10 @@
 
 %prep
 %setup -q -n %{docbase}-%{version}
-%{__sed} -i 's!../docs-common/!../../docs-common/!' \
-	 $RPM_BUILD_DIR/%{docbase}-%{version}/%{docbase}-en.xml
+for i in $RPM_BUILD_DIR/%{docbase}-%{version}/%{docbase}*.xml
+do
+	%{__sed} -i 's!../docs-common/!../../docs-common/!' "$i"
+done
 
 
 %build



From fedora-docs-commits at redhat.com  Mon Nov 21 03:05:05 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Sun, 20 Nov 2005 22:05:05 -0500
Subject: docs-common/common legalnotice-relnotes-zh_CN.xml,NONE,1.1
Message-ID: <200511210305.jAL355Gv007647@cvs-int.fedora.redhat.com>

Author: kwade

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7629

Added Files:
	legalnotice-relnotes-zh_CN.xml 
Log Message:
thanks to Yuan Yijun -bbbush.yuan at gmail.com-.


--- NEW FILE legalnotice-relnotes-zh_CN.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "This header makes editing XML easier" >

]>
-->

<!-- 

  Use this legalnotice for no-chunks/single-page HTML output.  It is an optional
  usage to move the bulk of the legalnotice to another location in the document.

  If you use this legalnotice, you must include a call to the
  LEGALNOTICE-SECTION entity, or include a similar <section> in your document.
  The call to LEGALNOTICE-SECTION must happen where a <section> is otherwise
  allowed.  One good location is immediately following an introduction.

  -->

<legalnotice id="legalnotice">
  <para>
	??????????????? GNU Free Documentation License ????????????????????????????????????????????? <xref
    linkend="sn-legalnotice" />.
  </para>
  <tip>
    <title>????????????????????????????????????</title>
    <para>
      ???????????????????????????????????????????????? <ulink
	url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>
      ?????????????????? &DISTRO; &DISTROVER; ???????????????
    </para>
  </tip>
</legalnotice>



From bbbush.yuan at gmail.com  Mon Nov 21 03:18:09 2005
From: bbbush.yuan at gmail.com (Yuan Yijun)
Date: Mon, 21 Nov 2005 11:18:09 +0800
Subject: docs-common/common legalnotice-relnotes-zh_CN.xml,NONE,1.1
In-Reply-To: <200511210305.jAL355Gv007647@cvs-int.fedora.redhat.com>
References: <200511210305.jAL355Gv007647@cvs-int.fedora.redhat.com>
Message-ID: <76e72f800511201918y39100ack@mail.gmail.com>

Should I update the master file (RELEASE-NOTES-zh_CN.xml) or I could
do that until next freeze?

--
bbbush ^_^



From kwade at redhat.com  Mon Nov 21 06:53:47 2005
From: kwade at redhat.com (Karsten Wade)
Date: Sun, 20 Nov 2005 22:53:47 -0800
Subject: docs-common/common legalnotice-relnotes-zh_CN.xml,NONE,1.1
In-Reply-To: <76e72f800511201918y39100ack@mail.gmail.com>
References: <200511210305.jAL355Gv007647@cvs-int.fedora.redhat.com>
	<76e72f800511201918y39100ack@mail.gmail.com>
Message-ID: <1132556027.935.27.camel@erato.phig.org>

On Mon, 2005-11-21 at 11:18 +0800, Yuan Yijun wrote:
> Should I update the master file (RELEASE-NOTES-zh_CN.xml) or I could
> do that until next freeze?

How does it need updating?

- Karsten
-- 
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint:  2680 DBFD D968 3141 0115    5F1B D992 0E06 AD0E 0C41   
Content Services                          Fedora Documentation Project
http://www.redhat.com/docs   http://fedoraproject.org/wiki/DocsProject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-docs-commits/attachments/20051120/33204107/attachment.sig>

From fedora-docs-commits at redhat.com  Tue Nov 22 01:11:37 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 21 Nov 2005 20:11:37 -0500
Subject: install-guide fedora-install-guide-beginninginstallation-en.xml, 1.8,
	1.9 fedora-install-guide-en.xml, 1.21,
	1.22 fedora-install-guide-intro-en.xml, 1.16, 1.17
Message-ID: <200511220111.jAM1BbdS018921@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18902

Modified Files:
	fedora-install-guide-beginninginstallation-en.xml 
	fedora-install-guide-en.xml fedora-install-guide-intro-en.xml 
Log Message:
First group of changes for new IG, a good test for HEAD vs. FC-4-patches


Index: fedora-install-guide-beginninginstallation-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-beginninginstallation-en.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide-beginninginstallation-en.xml	20 Nov 2005 22:41:12 -0000	1.8
+++ fedora-install-guide-beginninginstallation-en.xml	22 Nov 2005 01:11:28 -0000	1.9
@@ -4,16 +4,23 @@
 
   <para>
     To begin installation of &FC;, boot the computer from the boot
-    media.  You may install from CD or DVD discs, USB pen drives, hard
-    drives, or network servers.
+    media.  The boot media provides the necessary programs and files to
+    start the installation program.  Once you start the installation
+    program, you may be able to install from a completely different
+    piece of media.
   </para>
 
-  <note>
-    <title>Installation from Diskettes</title>
+  <important>
+    <title>Choosing a Different Installation Source</title>
     <para>
-      There is no option to install &FC; from diskettes.
+      To choose a different source for installation, enter
+      <userinput>linux askmethod</userinput> at the
+      <computeroutput>boot:</computeroutput> prompt.  If you boot from
+      some types of media such as USB or the network, the installation
+      program <emphasis>always</emphasis> asks you to choose the
+      installation source.
     </para>
-  </note>
+  </important>
 
   <para>
     The <indexterm>
@@ -53,10 +60,10 @@
 
 
   <section id="sn-booting-from-disc">
-    <title>Booting from Disc</title>
+    <title>Booting from CD, DVD, or USB Media</title>
 
     <para>
-      To boot your computer from disc:
+      To boot your computer:
     </para>
 
     <procedure>
@@ -64,7 +71,8 @@
 	<para>Switch on the computer.</para>
       </step>
       <step>
-	<para>Insert the first disc into the CD or DVD drive.</para>
+	<para>Insert the first disc into the CD or DVD drive, or attach
+	  the USB media.</para>
       </step>
       <step>
 	<para>A boot screen appears, with a <prompt>boot:</prompt>
@@ -72,6 +80,15 @@
       </step>
     </procedure>
 
+    <note>
+      <title>BIOS Boot Order</title>
+      <para>
+	The BIOS contains settings that control the order of boot
+	devices.  If your PC boots from a device other than the &FC;
+	boot media, check the BIOS boot configuration.
+      </para>
+    </note>
+
     <figure id="fig-boot">
       <title>Boot Screen</title>
       <mediaobject>
@@ -91,11 +108,13 @@
 
     <para>
       If you hit <keycap>Enter</keycap>, the installation runs in
-      default mode.  In the default mode, the installation runs from CD
-      or DVD discs, and uses a graphical interface if possible. To
-      change the installation mode, at the <prompt>boot:</prompt>
-      prompt, type <userinput>linux</userinput> followed by one or more
-      of the following options:
+      default mode.  In the default mode, the installation uses a
+      graphical interface if possible.  If the installation program runs
+      from the &FC; installation CD or DVD media, in default mode it
+      uses these media as the installation source.  To change the
+      installation mode, at the <prompt>boot:</prompt> prompt, type
+      <userinput>linux</userinput> followed by one or more of the
+      following options:
     </para>
     <itemizedlist>
       <listitem>
@@ -114,7 +133,9 @@
 	<para>
 	  To retry installation because the installation aborted at an
 	  early stage, add the directive
-	  <userinput>acpi=off</userinput>.
+	  <userinput>acpi=off</userinput>.  ACPI is responsible for many
+	  kinds of installation errors.  If you turn ACPI off, you may
+	  be able to overcome some of these errors.
 	</para>
       </listitem>
     </itemizedlist>
@@ -127,90 +148,92 @@
 
     <para>
       When you issue a command at the <prompt>boot:</prompt> prompt, the
-      first stage of the installation program starts.  After it loads,
-      the following screen appears:
+      first stage of the installation program starts.
     </para>
 
-    <figure id="fig-media-test">
-      <title>Media Test Screen</title>
-      <mediaobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/media-test.eps" format="EPS"/>
-	</imageobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/media-test.png" format="PNG"/>
-	</imageobject>
-	<textobject>
-	  <phrase>
-	    Media test screen.
-	  </phrase>
-	</textobject>
-      </mediaobject>
-    </figure>
+    <section id="sn-media-testing">
+      <title>Testing CD and DVD Media</title>
 
-    <para>
-      Select <guibutton>OK</guibutton> to test the disc, or select
-      <guibutton>Skip</guibutton> to proceed with the installation
-      without testing the disc.
-    </para>
+      <figure id="fig-media-test">
+	<title>Media Test Screen</title>
+	<mediaobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/media-test.eps" format="EPS"/>
+	  </imageobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/media-test.png" format="PNG"/>
+	  </imageobject>
+	  <textobject>
+	    <phrase>
+	      Media test screen.
+	    </phrase>
+	  </textobject>
+	</mediaobject>
+      </figure>
 
-    <caution>
-      <title>Testing Discs</title>
       <para>
-	Test any discs which you have not previously tested.  A disc
-	error during the installation process may force you to restart
-	the entire procedure.
+	Select <guibutton>OK</guibutton> to test the disc, or select
+	<guibutton>Skip</guibutton> to proceed with the installation
+	without testing the disc.
       </para>
-    </caution>
 
-    <para>
-      After you test the first disc, another screen appears and shows
-      the result:
-    </para>
+      <caution>
+	<title>Testing Discs</title>
+	<para>
+	  Test any discs which you have not previously tested.  A disc
+	  error during the installation process may force you to restart
+	  the entire procedure.
+	</para>
+      </caution>
 
-    <figure id="fig-mediacheck-result">
-      <title>Media Check Result</title>
-      <mediaobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/mediacheck-result.eps" format="EPS"/>
-	</imageobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/mediacheck-result.png" format="PNG"/>
-	</imageobject>
-	<textobject>
-	  <phrase>
-	    Media check result.
-	  </phrase>
-	</textobject>
-      </mediaobject>
-    </figure>
+      <para>
+	After you test the first disc, another screen appears and shows
+	the result:
+      </para>
 
-    <para>
-      Select <guibutton>OK</guibutton>.  The following screen appears:
-    </para>
+      <figure id="fig-mediacheck-result">
+	<title>Media Check Result</title>
+	<mediaobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/mediacheck-result.eps" format="EPS"/>
+	  </imageobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/mediacheck-result.png" format="PNG"/>
+	  </imageobject>
+	  <textobject>
+	    <phrase>
+	      Media check result.
+	    </phrase>
+	  </textobject>
+	</mediaobject>
+      </figure>
 
-    <figure id="fig-mediacheck-next">
-      <title>Next Disc Screen</title>
-      <mediaobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/mediacheck-next.eps" format="EPS"/>
-	</imageobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/mediacheck-next.png" format="PNG"/>
-	</imageobject>
-	<textobject>
-	  <phrase>
-	    Next disc or continue.
-	  </phrase>
-	</textobject>
-      </mediaobject>
-    </figure>
+      <para>
+	Select <guibutton>OK</guibutton>.  The following screen appears:
+      </para>
 
-    <para>
-      Select <guibutton>Test</guibutton> to test the next disc in the
-      set, or <guibutton>Continue</guibutton> to proceed with the
-      installation.
-    </para>
+      <figure id="fig-mediacheck-next">
+	<title>Next Disc Screen</title>
+	<mediaobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/mediacheck-next.eps" format="EPS"/>
+	  </imageobject>
+	  <imageobject>
+	    <imagedata align="center" fileref="./figs/mediacheck-next.png" format="PNG"/>
+	  </imageobject>
+	  <textobject>
+	    <phrase>
+	      Next disc or continue.
+	    </phrase>
+	  </textobject>
+	</mediaobject>
+      </figure>
+
+      <para>
+	Select <guibutton>Test</guibutton> to test the next disc in the
+	set, or <guibutton>Continue</guibutton> to proceed with the
+	installation.
+      </para>
 
 <!--
 
@@ -239,34 +262,15 @@
 
 -->
 
+    </section>
+
+
     <para>
       After you test your discs and select
       <guibutton>Continue</guibutton>, or if you choose to skip testing,
       the main graphical installation program loads.
     </para>
 
-    <para>
-      To boot from the disc, but install from another device or a
-      network server, use the <userinput>linux askmethod</userinput>
-      command at the <prompt>boot:</prompt> prompt.  &FC; also includes
-      a boot-only CD for this purpose, which is stored on the first &FC;
-      installation disc as an ISO file,
-      <filename>images/boot.iso</filename>.
-    </para>
-
-    <para>
-      To convert the ISO file into a physical CD, use the option in your
-      CD-writing program that burns a CD image file to a CD.  If you
-      copy the file itself to a CD instead, the disc will not boot or
-      work correctly.  Refer to your CD writing program documentation
-      for instructions.  If you are using Linux, use the following
-      command to burn a CD image file to a blank recordable CD:
-    </para>
-
-<screen>
-<userinput>cdrecord --device=<replaceable>cdwriter-device</replaceable> -tao -eject <replaceable>image-file.iso</replaceable></userinput>
-</screen>
-
     <note>
       <title>BIOS Boot Order</title>
       <para>
@@ -279,123 +283,6 @@
   </section>
 
 
-  <section id="sn-using-otherbootmedia">
-    <title>Using Other Removable Media</title>
-
-    <para>
-      To use a USB device such as a pen drive or Compact Flash card as
-      boot media, write the supplied image file to the device.  The
-      media must be large enough to contain the image.
-    </para>
-
-
-    <section id="sn-preparing-otherbootmedia">
-      <title>Preparing the Boot Media</title>
-
-      <warning>
-	<title>Data Loss</title>
-	<para>
-	  <emphasis>This procedure destroys data on the
-	    media.</emphasis> Back up any important information before
-	  you begin.  Some models of USB media use additional partitions
-	  or software to provide functions such as encryption.  This
-	  procedure may make it difficult or impossible to access these
-	  special areas on your boot media.
-	</para>
-      </warning>
-
-      <para>
-	The <filename>images/diskboot.img</filename> file on the first
-	&FC; installation disc is a boot image designed for USB media.
-	This file also appears on FTP and Web sites providing &FC;.
-      </para>
-
-      <para>
-	Several software utilities are available for Windows and Linux
-	that can write image files to a device.  Linux includes the
-	<command>dd</command> command for this purpose.  To write an
-	image file to boot media with <command>dd</command> on a current
-	version of &FC;:
-      </para>
-
-      <procedure>
-	<step>
-	  <para>
-	    Locate the image file.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    Attach or insert the media.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    Your system may automatically detect and open the media.  If
-	    that happens, close or unmount the media before continuing.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    Open a terminal window.
-	  </para>
-	</step>
-	<step>
-	  <para>
-	    In the terminal window, type the following command:
-
-<screen>
-<userinput>dd if=diskboot.img of=/dev/sda1</userinput>
-</screen>
-
-	  </para>
-	</step>
-      </procedure>
-
-    </section>
-
-
-    <section id="sn-booting-from-otherbootmedia">
-      <title>Booting from the Media</title>
-
-      <para>
-	Boot your computer with the prepared media:
-      </para>
-
-      <procedure>
-	<step>
-          <para>
-	    Attach or insert the media.
-	  </para>
-	</step>
-	<step>
-          <para>
-	    Switch on the computer.
-	  </para>
-	</step>
-	<step>
-          <para>
-	    A boot screen appears, with a <prompt>boot:</prompt> prompt
-	    at the bottom.  To begin, simply press the
-	    <keycap>Enter</keycap> key.
-	  </para>
-	</step>
-      </procedure>
-
-      <note>
-	<title>BIOS Boot Order</title>
-	<para>
-	  The BIOS contains settings that control the order of boot
-	  devices.  If your PC boots from a device other than the &FC;
-	  boot media, check the BIOS boot configuration.
-	</para>
-      </note>
-
-    </section>
-
-  </section>
-
-
   <section id="sn-booting-from-pxe">
     <title>Booting from the Network using PXE</title>
 
@@ -476,7 +363,6 @@
 
   </section>
 
-
 </chapter>
 
 <!--


Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- fedora-install-guide-en.xml	20 Nov 2005 22:41:12 -0000	1.21
+++ fedora-install-guide-en.xml	22 Nov 2005 01:11:28 -0000	1.22
@@ -4,17 +4,18 @@
 <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
 %FEDORA-ENTITIES-EN;
 
-<!ENTITY VERSION "1.0"> <!-- version for this document -->
-
-<!ENTITY BOOKID "fedora-install-guide-en-&VERSION; (2005-06-10-T16:20-0700)"> <!-- change date here and VERSION entity everytime a change is made-->
+<!ENTITY DOCNAME "fedora-install-guide">
+<!ENTITY DOCLANG "en">
+<!ENTITY DOCVERSION "1.01rc">
+<!ENTITY DOCDATE "2005-11-20">
+<!ENTITY BOOKID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)">
 
 <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
 
 <!-- Bugzilla bug number for the draft notice -->
 <!ENTITY BUG-NUM "129911">
-<!ENTITY FCLOCALVER "4">
-<!ENTITY DOCLOCALVER "1.0">
-<!ENTITY DRAFTNOTICE SYSTEM "../docs-common/common/draftnotice-en.xml">
+<!ENTITY FCLOCALVER "5">
+<!ENTITY DOCLOCALVER "1.0"> <!-- what's this for again? -->
 
 
 <!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-en.xml">


Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- fedora-install-guide-intro-en.xml	20 Nov 2005 22:41:12 -0000	1.16
+++ fedora-install-guide-intro-en.xml	22 Nov 2005 01:11:28 -0000	1.17
@@ -2,8 +2,8 @@
 <preface id="ch-intro">
   <title>Introduction</title>
 
-  <!--  removed until we begin working on the FC5 version
-  &DRAFTNOTICE;  -->
+<!--  removed until we begin working on the FC5 version -->
+  &BUG-REPORTING;
 
   <para>
     &FC; is a complete desktop and server operating system created
@@ -175,6 +175,10 @@
 
     </section>
     
+<!--
+
+    Is it just me, or is this section really out of place? [PWF]
+
     <section id="sn-installing-asaserver">
       <title>Installing &FC; as a Server</title>
       
@@ -190,6 +194,7 @@
 
     </section>
 
+-->
 
     <section id="sn-installing-networkinstallation">
       <title>Installing from a Network Server</title>
@@ -277,6 +282,173 @@
     </section>
 
   </section>
+
+  <section id="sn-preparing-media">
+    <title>Preparing Media</title>
+
+    <para>
+      The types of boot media for &FED; include:
+    </para>
+
+    <itemizedlist>
+      <listitem>
+	<para>
+	  CD or DVD media (either installation disc #1 or a special
+	  boot-only disc)
+	</para>
+      </listitem>
+      <listitem>
+	<para>
+	  USB media
+	</para>
+      </listitem>
+      <listitem>
+	<para>
+	  Network interface (via PXE)
+	</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>
+      The types of installation source media for &FED; include:
+    </para>
+
+    <itemizedlist>
+      <listitem>
+	<para>
+	  CD or DVD media installation discs
+	</para>
+      </listitem>
+      <listitem>
+	<para>
+	  Hard disk
+	</para>
+      </listitem>
+      <listitem>
+	<para>
+	  Network installation tree via HTTP, FTP, or NFS
+	</para>
+      </listitem>
+    </itemizedlist>
+
+    <note>
+      <title>Installation from Diskettes</title>
+      <para>
+	There is no option to install &FC; from diskettes.
+      </para>
+    </note>
+
+    <para>
+      The &FC; distribution includes <firstterm>image files</firstterm>
+      for boot-only CD or DVD media and USB media. These files can be
+      converted into bootable media using standard Linux utilities or
+      third-party programs on other operating systems.
+    </para>
+
+    <note>
+      <title>CD or DVD Installation Media</title>
+      <para>
+	You may also use the first CD or DVD disc from the complete &FC;
+	distribution as boot media.  For instructions to download and
+	prepare this media, refer to <ulink
+	  url="http://fedora.redhat.com/download/"/>.  If you already
+	have the full set of &FC;, skip to <xref
+	linkend="sn-booting-from-disc"/>.
+      </para>
+    </note>
+
+    <section id="sn-preparing-cd-or-dvd-media">
+      <title>Preparing CD or DVD Boot Disc</title>
+
+      <para>
+	The <filename>images/boot.iso</filename> file on the first &FC;
+	installation disc is a boot image designed for CD and DVD media.
+	This file also appears on FTP and Web sites providing &FC;.
+      </para>
+
+      <para>
+	To convert the ISO file into a physical CD, use the option in
+	your CD-writing program that burns a CD image file to a CD. If
+	you copy the file itself to a CD instead, the disc will not boot
+	or work correctly.  Refer to your CD writing program
+	documentation for instructions.  If you are using Linux, use the
+	following command to burn a CD image file to a blank recordable
+	CD:
+      </para>
+
+<screen>
+<userinput>cdrecord --device=<replaceable>cdwriter-device</replaceable> -tao -eject <replaceable>image-file.iso</replaceable></userinput>
+</screen>
+
+    </section>
+    
+    <section id="sn-preparing-usb-media">
+      <title>Preparing USB Boot Media</title>
+
+      <warning>
+	<title>Data Loss</title>
+	<para>
+	  <emphasis>This procedure destroys data on the
+	    media.</emphasis> Back up any important information before
+	  you begin.  Some models of USB media use additional partitions
+	  or software to provide functions such as encryption.  This
+	  procedure may make it difficult or impossible to access these
+	  special areas on your boot media.
+	</para>
+      </warning>
+
+      <para>
+	The <filename>images/diskboot.img</filename> file on the first
+	&FC; installation disc is a boot image designed for USB media.
+	This file also appears on FTP and Web sites providing &FC;.
+      </para>
+
+      <para>
+	Several software utilities are available for Windows and Linux
+	that can write image files to a device.  Linux includes the
+	<command>dd</command> command for this purpose.  To write an
+	image file to boot media with <command>dd</command> on a current
+	version of &FC;:
+      </para>
+
+      <procedure>
+	<step>
+	  <para>
+	    Locate the image file.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    Attach or insert the media.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    Your system may automatically detect and open the media. If
+	    that happens, close or unmount the media before continuing.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    Open a terminal window.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    In the terminal window, type the following command:
+	  </para>
+
+<screen>
+<userinput>dd if=diskboot.img of=/dev/sda1</userinput>
+</screen>
+
+	</step>
+      </procedure>
+
+    </section>
+
+  </section>
+
   
 </preface>
 



From fedora-docs-commits at redhat.com  Tue Nov 22 12:44:51 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 22 Nov 2005 07:44:51 -0500
Subject: release-notes colophon-relnotes.xml,NONE,1.1
Message-ID: <200511221244.jAMCipgN008966@cvs-int.fedora.redhat.com>

Author: kwade

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8948

Added Files:
	colophon-relnotes.xml 
Log Message:
Finally a colophon for the relnotes, hail all us contributors.


--- NEW FILE colophon-relnotes.xml ---
<section id="sn-colophon">
  <title>&FC; Release Notes Colophon</title>
  <note>
    <title>Draft Colophon</title>
    <para>
      This is a draft, so it is incomplete and imperfect. 
    </para>
  </note>
  <para>As we use the term, colophon means: </para>
    <itemizedlist>
    <listitem>
      <para> A way to recognize contributors, while providing
	accountability. </para>
    </listitem>
    <listitem>
      <para> Explain tools and production methods. </para>
    </listitem>
  </itemizedlist>
  <section>
    <title>Contributors</title>
    <itemizedlist>
      <listitem>
	<para>
	  AndrewMartynov (translator, Russian) </para>
      </listitem>
      <listitem>
	<para>
	  AnthonyGreen (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  BobJensen
	</para>
      </listitem>
      <listitem>
	<para>
	  DaveMalcolm (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  DavidWoodhouse (beat writer) </para>
      </listitem>
      <listitem>
	<para>
	  FrancescoTombolini (translator, Italian) </para>
      </listitem>
      <listitem>
	<para>
	  GavinHenry (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  JensPetersen (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  JoeOrton (beat writer) </para>
      </listitem>
      <listitem>
	<para>
	  JoshBressers (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  KarstenWade (beat writer, editor-in-chief, publisher) </para>
      </listitem>
      <listitem>
	<para>
	  LuyaTshimbalanga (beat writer) </para>
      </listitem>
      <listitem>
	<para>
	  PatrickBarnes (beat writer, editor) </para>
      </listitem>
      <listitem>
	<para>
	  RahulSundaram (beat writer, editor) </para>
      </listitem>
      <listitem>
	<para>
	  SekineTatsuo (translator, Japanese) </para>
      </listitem>
      <listitem>
	<para>
	  SteveDickson (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  StuartElliss (editor)
	</para>
      </listitem>
      <listitem>
	<para>
	  ThomasGraf (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  TommyReynolds (tools)
	</para>
      </listitem>
      <listitem>
	<para>
	  YoshinariTakaoka (translator, tools) </para>
      </listitem>
      <listitem>
	<para>
	  YuanYijun (translator, Simplified Chinese) </para>
      </listitem>
    </itemizedlist>
  </section>
  <section>
    <title>Production Methods</title>
  </section>
  </section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Tue Nov 22 13:15:35 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 22 Nov 2005 08:15:35 -0500
Subject: release-notes colophon-relnotes-en.xml, NONE,
	1.1 colophon-relnotes.xml, 1.1, NONE
Message-ID: <200511221315.jAMDFZ2u010749@cvs-int.fedora.redhat.com>

Author: kwade

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10733

Added Files:
	colophon-relnotes-en.xml 
Removed Files:
	colophon-relnotes.xml 
Log Message:
D'oh.  You'd think I'd i18nize this file properly, but noooooo ... renaming to make it translatable.


--- NEW FILE colophon-relnotes-en.xml ---
<section id="sn-colophon">
  <title>&FC; Release Notes Colophon</title>
  <note>
    <title>Draft Colophon</title>
    <para>
      This is a draft, so it is incomplete and imperfect. 
    </para>
  </note>
  <para>As we use the term, colophon means: </para>
    <itemizedlist>
    <listitem>
      <para> A way to recognize contributors, while providing
	accountability. </para>
    </listitem>
    <listitem>
      <para> Explain tools and production methods. </para>
    </listitem>
  </itemizedlist>
  <section>
    <title>Contributors</title>
    <itemizedlist>
      <listitem>
	<para>
	  Andrew Martynov (translator, Russian) </para>
      </listitem>
      <listitem>
	<para>
	  Anthony Green (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Bob Jensen
	</para>
      </listitem>
      <listitem>
	<para>
	  Dave Malcolm (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  David Woodhouse (beat writer) </para>
      </listitem>
      <listitem>
	<para>
	  Francesco Tombolini (translator, Italian) </para>
      </listitem>
      <listitem>
	<para>
	  Gavin Henry (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Jens Petersen (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Joe Orton (beat writer) </para>
      </listitem>
      <listitem>
	<para>
	  Josh Bressers (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Karsten Wade (beat writer, editor-in-chief, publisher) </para>
      </listitem>
      <listitem>
	<para>
	  LuyaTshimbalanga (beat writer) </para>
      </listitem>
      <listitem>
	<para> 
	  PatrickBarnes (beat writer, editor) </para>
      </listitem>
      <listitem>
	<para>
	  Rahul Sundaram (beat writer, editor) </para>
      </listitem>
      <listitem>
	<para>
	  Sekine Tatsuo (translator, Japanese) </para>
      </listitem>
      <listitem>
	<para>
	  Steve Dickson (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Stuar tElliss (editor)
	</para>
      </listitem>
      <listitem>
	<para>
	  Thomas Graf (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Tommy Reynolds (tools)
	</para>
      </listitem>
      <listitem>
	<para>
	  Yoshinari Takaoka (translator, tools) </para>
      </listitem>
      <listitem>
	<para>
	  Yuan Yijun (translator, Simplified Chinese) </para>
      </listitem>
    </itemizedlist>
  </section>
  <section>
    <title>Production Methods</title>
  </section>
  </section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->


--- colophon-relnotes.xml DELETED ---



From fedora-docs-commits at redhat.com  Tue Nov 22 18:15:46 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Tue, 22 Nov 2005 13:15:46 -0500
Subject: release-notes colophon-relnotes-it.xml,NONE,1.1
Message-ID: <200511221815.jAMIFkOX019992@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19976/release-notes

Added Files:
	colophon-relnotes-it.xml 
Log Message:
italian translation added to cvs


--- NEW FILE colophon-relnotes-it.xml ---
<section id="sn-colophon">
  <title>&FC; Release Notes Colophon</title>
  <note>
    <title>Colophon preliminare</title>
    <para>
      E' preliminare, perci?? incompleta ed imperfetta. 
    </para>
  </note>
  <para>Per come lo intendiamo noi, colophon significa: </para>
    <itemizedlist>
    <listitem>
      <para> Un modo per dare riconoscenza ai contributori, e nel contempo
	le responsabilit??. </para>
    </listitem>
    <listitem>
      <para> Spiegazione degli strumenti e dei metodi di produzione. </para>
    </listitem>
  </itemizedlist>
  <section>
    <title>Contributori</title>
    <itemizedlist>
      <listitem>
	<para>
	  Andrew Martynov (translator, Russian) </para>
      </listitem>
      <listitem>
	<para>
	  Anthony Green (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Bob Jensen
	</para>
      </listitem>
      <listitem>
	<para>
	  Dave Malcolm (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  David Woodhouse (beat writer) </para>
      </listitem>
      <listitem>
	<para>
	  Francesco Tombolini (translator, Italian) </para>
      </listitem>
      <listitem>
	<para>
	  Gavin Henry (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Jens Petersen (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Joe Orton (beat writer) </para>
      </listitem>
      <listitem>
	<para>
	  Josh Bressers (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Karsten Wade (beat writer, editor-in-chief, publisher) </para>
      </listitem>
      <listitem>
	<para>
	  LuyaTshimbalanga (beat writer) </para>
      </listitem>
      <listitem>
	<para> 
	  PatrickBarnes (beat writer, editor) </para>
      </listitem>
      <listitem>
	<para>
	  Rahul Sundaram (beat writer, editor) </para>
      </listitem>
      <listitem>
	<para>
	  Sekine Tatsuo (translator, Japanese) </para>
      </listitem>
      <listitem>
	<para>
	  Steve Dickson (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Stuar tElliss (editor)
	</para>
      </listitem>
      <listitem>
	<para>
	  Thomas Graf (beat writer)
	</para>
      </listitem>
      <listitem>
	<para>
	  Tommy Reynolds (tools)
	</para>
      </listitem>
      <listitem>
	<para>
	  Yoshinari Takaoka (translator, tools) </para>
      </listitem>
      <listitem>
	<para>
	  Yuan Yijun (translator, Simplified Chinese) </para>
      </listitem>
    </itemizedlist>
  </section>
  <section>
    <title>Production Methods</title>
  </section>
  </section>
<!--
Local variables:
mode: xml
sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
fill-column: 72
End:
-->



From fedora-docs-commits at redhat.com  Wed Nov 23 05:38:33 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 23 Nov 2005 00:38:33 -0500
Subject: release-notes desktop-en.xml, 1.2, 1.3 development-tools-en.xml, 1.2,
	1.3 entertainment-en.xml, 1.1, 1.2 fedora.css, 1.2,
	1.3 file-servers-en.xml, 1.2, 1.3 i18n-en.xml, 1.1,
	1.2 install-notes-en.xml, 1.3, 1.4 kernel-en.xml, 1.2,
	1.3 multimedia-en.xml, 1.3, 1.4 project-overview-en.xml, 1.1, 1.2
Message-ID: <200511230538.jAN5cXu6008072@cvs-int.fedora.redhat.com>

Author: kwade

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8043

Modified Files:
	desktop-en.xml development-tools-en.xml entertainment-en.xml 
	fedora.css file-servers-en.xml i18n-en.xml 
	install-notes-en.xml kernel-en.xml multimedia-en.xml 
	project-overview-en.xml 
Log Message:
Past the kernel beat, in alpha order, snapshot of what has been updated from the wiki for fc5test1.


Index: desktop-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/desktop-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- desktop-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ desktop-en.xml	23 Nov 2005 05:38:24 -0000	1.3
@@ -3,70 +3,88 @@
   <itemizedlist>
     <title>Notes</title>
     <listitem>
-      <para>GNOME 2.12 and KDE 3.4.2 Major highlight
+      <para>GNOME 2.12 and KDE 3.4.2 are included in &FC; &FCVER;.
       </para>
     </listitem>
     <listitem>
-      <para>The current test release has GNOME 2.12.1, together with
-	some previews of technology from the forthcoming GNOME 2.14:
+      <para>This test release has GNOME 2.12.1, together with some
+	previews of technology from the forthcoming GNOME 2.14. Feedback
+	on these packages is especially appreciated.
       </para>
       <itemizedlist>
         <listitem>
-          <para>gnome-power-manager: brings the Hardware Abstraction
-	    Layer to the world of laptop batteries and UPS units - these
-	    things should "Just Work", with a simple UI  (naturally, in
-	    a test release, they might not)
+          <para><filename>gnome-power-manager</filename>:
+	    <application>GNOME Power Manager </application> is a session
+	    daemon for the GNOME desktop environment that makes it easy
+	    to manage power on your laptop or desktop system. It takes
+	    advantage of HAL (which provides a hardware abstraction
+	    layer) and DBUS (Inter Process Communication software)
+	    written and maintained by &FC; developers.
 	  </para>
         </listitem>
         <listitem>
-          <para>gnome-screensaver: giving a fresh UI to screensavers and
-	    the <guilabel>Lock Screen</guilabel> dialog
+          <para><filename>gnome-screensaver</filename>: Provides a
+	    integrated user interface to screensavers and the lock
+	    screen dialog.
 	  </para>
         </listitem>
         <listitem>
-          <para>Memory optimizations in the fontconfig and
-	    shared-mime-info packages (these now use shared
-	    memory-mapped caches for this data).  Both of these caches
-	    are still somewhat experimental.
+          <para>Memory optimizations in the
+	    <filename>fontconfig</filename> and
+	    <filename>shared-mime-info</filename> packages.  These now
+	    use shared memory-mapped caches for this data.
 	  </para>
         </listitem>
       </itemizedlist>
     </listitem>
-  <para>
-    Test feedback on these experimental packages is especially
-    appreciated.
-  </para>
-  <para>
-    GNOME 2.12 has removed the terminal option from the desktop root
-    menu. nautilus-open-terminal in Fedora Extras repository provides a
-    enhanced replacement. It is also mentioned in the GNOME 2.12 release
-    notes itself but we might highlight it since the package is provided
-    with the extras repository.
-  </para>
-  <para>
-    Screensavers not installed by default anymore. Should explain why
-    and provide commands to install them.
-  </para>
-  <para>MCS SELinux is in rawhide. Major highlight
-    (<emphasis>tentative</emphasis> - not sure about classification of
-    this change)
-  </para>
-  <caution>
-    <title>OpenOffice and upgrading from test releases</title>
-    <para>
-      If you choose to go counter to the recommendation to <emphasis
-	role='strong'>not</emphasis> upgrade from a previous test
-      release, you may encounter a problem with <ulink
-	url='/OpenOffice'>OpenOffice</ulink> following the upgrade.
-    </para>
-    <para>
-      To resolve this, you must do the following command <emphasis
-	role='strong'>before</emphasis> doing the upgrade:
-    </para>
+    <listitem>
+      <para>GNOME 2.12 has removed the
+	<guimenuitem>terminal</guimenuitem> option from the desktop
+	context menu. The package
+	<filename>nautilus-open-terminal</filename> in &FEX;
+	repository provides an enhanced replacement for those who require
+	it. You can install it using the following command:
+      </para>
 <screen>
-<command>rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
+<command>yum install nautilus-open-terminal</command>
 </screen>
-  </caution>
+    </listitem>
+    <listitem>
+      <para>Only the blank screensavers is installed by default, since
+      &FC; 4.
+      </para>
+      <para>
+	The primary issue is that some screensavers are known to not
+	work correctly or abruptly terminate the graphical interface.
+	This is particularly true for some of the OpenGL animated ones
+	provided within <filename></filename>xscreensaver-gl-extras
+	package.
+      </para>
+      <para>
+	In addition, the material content of the screensavers is
+	sometimes controversial or causes strong reactions.  It is
+	better, for the user experience, to not be surprised by the
+	nature of the screensavers.
+      </para>
+      <para>
+	Users who want the screensavers package can install it using the following
+	command.
+      </para>
+<screen>
+<command>yum install xscreensaver-extras xscreensaver-gl-extras</command>
+</screen>
+    </listitem>
+  </itemizedlist>
+  <note>
+    <title>Mouse configuration utility has changed</title>
+    <para>
+      The configuration utility
+      <application>system-config-mouse</application> has been dropped
+      from this release since synaptic and 3 button mouse configuration
+      is being done automatically during installation. Serial mice are
+      not formally supported in &FC; anymore.
+    </para>
+  </note>
 </section>
 <!--
 Local variables:


Index: development-tools-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/development-tools-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- development-tools-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ development-tools-en.xml	23 Nov 2005 05:38:24 -0000	1.3
@@ -9,11 +9,39 @@
 
 ]>
 -->
-<!-- Content commented out, no update performed by beat writer yet.
 <section id="sn-devel">
   <title>
     Development Tools
   </title>
+  <section id="sn-java-development">
+    <title>Java-like Environment</title>
+    <para>A Java-like free and open source environment is available
+      within the &FC; &FCVER; release.
+    </para>
+    <para>
+      It has three components: GNU Java runtime
+      (<filename>libgcj</filename>), the Eclipse Java compiler
+      (<command>ecj</command>), and a set of wrappers and links
+      (<filename>java-gcj-compat</filename>) that present the runtime
+      and compiler to the user in the same way as other Java
+      environments are presented.
+    </para>
+    <para>
+      Several major software packages such as Openoffice.org Base,
+      Eclipse, and Apache Tomcat, as well as several other Java software
+      packages included in this release, are compatible with this
+      environment.
+    </para>
+    <para>
+      For more information, refer to the FAQ:
+    </para>
+    <para>
+      <ulink
+	url='http://www.fedoraproject.org/wiki/JavaFAQ'>http://www.fedoraproject.org/wiki/JavaFAQ</ulink>
+    </para>
+  </section>
+
+<!-- Content commented out, no update performed by beat writer yet.
   <section id="sn-devel-gcc">
     <title>GCC Compiler Collection</title>
     <para>
@@ -176,8 +204,9 @@
       </listitem>
     </itemizedlist>
   </section>
-</section>
 -->
+</section>
+
 
 <!--
 Local variables:


Index: entertainment-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/entertainment-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- entertainment-en.xml	25 Oct 2005 08:34:00 -0000	1.1
+++ entertainment-en.xml	23 Nov 2005 05:38:24 -0000	1.2
@@ -2,7 +2,7 @@
   <title>Games and Entertainment</title>
   <para>
     &FC; and &FEX; provide a selection of games that cover a variety of
-    genres.  By default, &FC;includes a small package of games for GNOME
+    genres.  By default, &FC; includes a small package of games for GNOME
     (called <filename>gnome-games</filename>).  For a list of other
     games that are available for installation through
     <command>yum</command>, open a terminal and enter the following


Index: fedora.css
===================================================================
RCS file: /cvs/docs/release-notes/fedora.css,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora.css	25 Oct 2005 02:48:50 -0000	1.2
+++ fedora.css	23 Nov 2005 05:38:24 -0000	1.3
@@ -132,3 +132,7 @@
 	/* prevent inheritance */
 	margin-bottom: 0em;
 }
+
+p.title	{
+	text-align: center;
+}


Index: file-servers-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/file-servers-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- file-servers-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ file-servers-en.xml	23 Nov 2005 05:38:24 -0000	1.3
@@ -24,12 +24,18 @@
       <title><filename>netatalk</filename></title>
       <para>
 	&DISTRO; &DISTROVER; includes version 2 of Netatalk.
-	<emphasis>Upgrading from Netatalk version 1 to version 2 may
-	  result in data loss</emphasis>.    Version 2 of Netatalk uses
-	a different method to store file resource forks from the
-	previous version, and may require a different file name encoding
-	scheme.  Please read the documentation and plan your migration
-	before upgrading.
+      </para>
+      <caution>
+	<title>Take care when upgrading Netatalk versions</title>
+	<para>
+	  Upgrading from Netatalk version 1 to version 2 may result in
+	  data loss.
+	</para>
+      </caution>
+      <para>Version 2 of Netatalk uses a different method to store file
+	resource forks from the previous version, and may require a
+	different file name encoding scheme.  Read the documentation and
+	plan your migration before upgrading.
       </para>
       <para>
 	Upgrade information is available directly from the Netatalk


Index: i18n-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/i18n-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- i18n-en.xml	25 Oct 2005 08:34:00 -0000	1.1
+++ i18n-en.xml	23 Nov 2005 05:38:24 -0000	1.2
@@ -9,100 +9,13 @@
       This section includes information related to the support of
       various languages under &DISTRO;.
     </para>
-    <section>
-      <title>The IIIMF Input System</title>
+    <note>
+      <title>IIIMF replaced</title>
       <para>
-	IIIMF is the Internet/Intranet Input Method Framework.  In &FC;
-	&LOCALVER; the <filename>iiimf</filename> package is updated to
-	version 12.2.
+	SCIM has replaced IIIMF in Fedora Core in this
+	release.
       </para>
-      <variablelist>
-	<varlistentry>
-	  <term>File Path Changes</term>
-	  <listitem>
-	    <para>
-	      The names and locations of some files in the
-	      <filename>iiimf</filename> packages have changed.
-	    </para>
-	    <para>
-	      The IIIMF server has been renamed from
-	      <filename>/usr/sbin/htt</filename> to
-	      <filename>/usr/bin/iiimd</filename>, and the XIM bridge
-	      client renamed from <filename>httx</filename> to
-	      <filename>iiimx</filename>. The
-	      <filename>init.d</filename> script name has not changed:
-	      it is still called <filename>iiim</filename>. All the
-	      global system configuration files are now located under
-	      <filename>/etc/iiim/</filename>.
-	    </para>
-	    <para>
-	      Language Engine (LE) developers should note that LE
-	      modules and their data now live under
-	      <filename>${libdir}/iiim/le/<filename>&lt;LE_NAME&gt;</filename>/</filename>, 
-	      while runtime data is stored under
-	      <filename>/var/lib/iiim/le/<replaceable>&lt;LE_NAME&gt;</replaceable>/</filename>.
-	    </para>
-	    <para>
-	      For more information on the exact path and file location
-	      changes, please refer to Fedora IIIMF FAQ:
-	    </para>
-	    <para>
-	      <ulink
-		url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term>Hotkeys</term>
-	  <listitem>
-	    <para>
-	      Trigger keys, such as
-	      <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo> 
-	      used to activate Input Methods, are now configurable with
-	      the command-line tool <command>iiimf-le-tools</command>.
-	      This feature is only supported by GTK2 applications
-	      currently.  For other applications using XIM the trigger
-	      key can be changed using an X resource.  Refer to the
-	      IIIMF FAQ at <ulink
-		url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink> 
-	      for more details on how to change trigger hotkeys.
-	    </para>
-	    <para>
-	      Note that the keyname refers to the X key symbol name. For
-	      example, if you want to activate with
-	      <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>, 
-	      you need to specify '&lt;Control&gt;at' as the keyname not
-	      '&lt;Control&gt;@'.
-	    </para>
-	    <para>
-	      The per-user configuration of hotkeys does not work
-	      currently with &SEL; in enforcing mode due to lack of
-	      &SEL; policy.  In this case, the hotkey can only be
-	      changed in the system-wide configuration.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term>Qt Support</term>
-	  <listitem>
-	    <para>
-	      A Qt immodule for <filename>iiimf</filename> is now
-	      included.  This immodule works but lacks a status window
-	      and is considered experimental.  Therefore, the default
-	      for Qt applications is to continue using XIM for IIMF
-	      input.
-	    </para>
-	    <para>
-	      If you wish to try the immodule in a Qt application, first
-	      install the <filename>iiimf-qt</filename> package, start
-	      the application, then click mouse button-3 in an input
-	      area and select <guimenuitem>iiimqcf</guimenuitem> from
-	      the <guisubmenu>Select Input Method</guisubmenu>' submenu.
-	    </para>
-	  </listitem>
-	</varlistentry>
-      </variablelist>
-    </section>
+    </note>
   </section>
 </section>
 <!--


Index: install-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- install-notes-en.xml	25 Oct 2005 09:07:12 -0000	1.3
+++ install-notes-en.xml	23 Nov 2005 05:38:24 -0000	1.4
@@ -8,16 +8,17 @@
   <note>
     <title>Note</title>
     <para>
-      If you intend to download the &DISTRO; &DISTROVER; DVD ISO
-      image, keep in mind that not all file downloading tools can
-      accommodate files larger than 2GB in size.  For example,
-      <command>wget</command> will exit with a <computeroutput>File size
-	limit exceeded</computeroutput> error.
+      If you intend to download the &DISTRO; &DISTROVER; DVD ISO image,
+      keep in mind that not all file downloading tools can accommodate
+      files larger than 2GiB in size.  For example,
+      <command>wget</command> before version 1.9.1.16 in exits with a
+      <computeroutput>File size limit exceeded</computeroutput> error.
     </para>
     <para>
-      The <command>curl</command> and <command>ncftpget</command>
-      file downloading tools do not have this limitation, and can
-      successfully download files larger than 2GB.
+      The <command>wget</command> version 1.9.1-16 and lter,
+      <command>curl</command> and <command>ncftpget</command> file
+      downloading tools do not have this limitation, and can
+      successfully download files larger than 2GiB.
     </para>
     <para>
       Bittorrent is another method for downloading large files.  For
@@ -31,7 +32,7 @@
   </note>
   <section id="sn-install-notes-ppc">
     <title>PPC Installation Notes</title>
-    <section>
+    <section id="sn-ppc-hardware-reqs">
       <title>PPC Hardware Requirements</title>
       <para>
 	This section lists the minimum PowerPC (PPC) hardware needed
@@ -42,8 +43,9 @@
 	  <para>Minimum: PowerPC G3 / POWER4 </para>
 	</listitem>
 	<listitem>
-	  <para>&DISTRO; &DISTROVER; supports only the ???New World??? generation
-	    of Apple Power Macintosh, shipped circa 1999 onwards.
+	  <para>&DISTRO; &DISTROVER; supports only the ???New World???
+	    generation of <trademark class="trade">Apple</trademark>
+	    Power Macintosh, shipped circa 1999 onwards.
 	  </para>
 	</listitem>
 	<listitem>
@@ -51,11 +53,11 @@
 	    RS/6000, and Genesi Pegasos II machines.</para>
 	</listitem>
 	<listitem>
-	  <para>Recommended for text-mode: 233 MHz G3 or better, 64MB
+	  <para>Recommended for text-mode: 233 MHz G3 or better, 64MiB
 	    RAM.</para>
 	</listitem>
 	<listitem>
-	  <para>Recommended for graphical: 400 MHz G3 or better, 128MB
+	  <para>Recommended for graphical: 400 MHz G3 or better, 128MiB
 	    RAM.</para>
 	</listitem>
       </itemizedlist>
@@ -63,23 +65,22 @@
 	The DVD or first CD of the installation set of &FC; is set to be
 	bootable on supported hardware. In addition, bootable CD images
 	can be found in the <filename>images/</filename> directory of
-	the DVD or first CD. These will behave differently according to
-	the hardware:
+	the DVD or first CD. These behave differently according to the
+	hardware:
       </para>
       <variablelist>
 	<title>Boot Image Behavior by Hardware</title>
 	<varlistentry>
 	  <term>Apple Macintosh </term>
 	  <listitem>
-	    <para>The bootloader should automatically boot the
-	      appropriate 32-bit or 64-bit installer.  Power management
-	      support, including sleep and backlight level management,
-	      is present in the <filename>apmud</filename> package,
-	      which is in &FEX;. &FEX; for &FC; is configured by default
-	      for yum. Following installation,
-	      <filename>apmud</filename> can be installed by running the
-	      command <command>yum install apmud</command> in a
-	      terminal.
+	    <para>The bootloader automatically boots the appropriate
+	      32-bit or 64-bit installer.  Power management support,
+	      including sleep and backlight level management, is present
+	      in the <filename>apmud</filename> package, which is in
+	      &FEX;. &FEX; for &FC; is configured by default for yum.
+	      Following installation, <filename>apmud</filename> can be
+	      installed by running the command <command>yum install
+		apmud</command> in a terminal.
 	    </para>
 	  </listitem>
 	</varlistentry>
@@ -87,8 +88,8 @@
 	  <term>64-bit IBM eServer pSeries (POWER4/POWER5)</term>
 	  <listitem>
 	    <para>After using OpenFirmware to boot the CD, the
-	      bootloader (<command>yaboot</command>) should
-	      automatically boot the 64-bit installer.
+	      bootloader (<command>yaboot</command>) automatically boots
+	      the 64-bit installer.
 	    </para>
 	  </listitem>        
 	</varlistentry>
@@ -114,11 +115,11 @@
 <command>boot cd: /images/netboot/ppc32.img</command> 
 </screen>          
 	    <para>
-	      You will also need to configure OpenFirmware on the
-	      Pegasos manually to make the installed &FC; system
-	      bootable. To do this, you need to set the
-	      <envar>boot-device</envar> and <envar>boot-file</envar>
-	      environment variables appropriately.
+	      You also need to configure OpenFirmware on the Pegasos
+	      manually to make the installed &FC; system bootable. To do
+	      this, you need to set the <envar>boot-device</envar> and
+	      <envar>boot-file</envar> environment variables
+	      appropriately.
 	    </para>
 	  </listitem>        
 	</varlistentry>
@@ -126,12 +127,13 @@
 	  <term>Network booting</term>
 	  <listitem>
 	    <para>There are combined images containing the installer
-	      kernel and ramdisk in the images/netboot/ directory of the
+	      kernel and ramdisk in the
+	      <filename>images/netboot/</filename> directory of the
 	      install tree. These are intended for network booting with
 	      TFTP, but can be used in many ways.
 	    </para>
 	    <para>
-	      The command <command>yaboot</command> supports tftp
+	      The command <command>yaboot</command> supports TFTP
 	      booting for IBM eServer pSeries and Apple Macintosh. &FED;
 	      recommends using yaboot over the netboot images.
 	    </para>
@@ -140,7 +142,7 @@
       </variablelist>
     </section>
   </section>
-  <section>
+  <section id="sn-anaconda-notes">
     <title>Anaconda Notes</title>
     
     <itemizedlist>
@@ -175,10 +177,6 @@
 	</para>
       </listitem>
       <listitem arch="x86">
-<!--	<remark os="test">%%% <ulink
-	    url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654</ulink> 
-	  %%%</remark>
--->
 	<para>
 	  <!-- <remark os="test">(x86)</remark> --> Memory testing may be
 	  performed prior to installing &DISTRO; by entering
@@ -201,16 +199,70 @@
 	<para>
 	  &DISTRO; &DISTROVER; supports graphical FTP and HTTP
 	  installations.  However, due to the necessity of containing
-	  the installer image in RAM, only systems with more than 128MB
+	  the installer image in RAM, only systems with more than 128MiB
 	  of RAM (or systems booted from CD-ROM 1, which contains the
 	  installer image) can use the graphical installer.  Systems
-	  with 128MB or less will continue to use the text-based
+	  with 128MiB of RAM or less must continue to use the text-based
 	  installer.
 	</para>
       </listitem>
     </itemizedlist>
   </section>
-  <section>
+  <section id="sn-installer-changes">
+    <title>Changes In The Installer</title>
+    <itemizedlist>
+      <listitem>
+	<para>Support has been added for <command>yum</command> as the
+	  dependancy solver backend for software packages has been
+	  added.  Additional repositories are expected to be supported
+	  during installation in a future release.
+	</para>
+      </listitem>
+      <listitem>
+	<para>In this release, the installer checks the hardware
+	  capability and installs either the uniprocessor or SMP
+	  (Symmetric Multi Processor) kernel, as appropriate. Previous
+	  releases installed both the variants and used the appropriate
+	  one as default.
+	</para>
+      </listitem>
+      <listitem>
+	<para>Partition setting has been reworked to be more user
+	  friendly.
+	</para>
+      </listitem>
+      <listitem>
+	<para>Remote logging via <command>syslog</command> is supported
+	  in this release.  To enable, pass
+	  <option>syslog=host:port</option> at the boot prompt.
+	  Specifying the port is optional.
+	</para>
+      </listitem>
+      <listitem>
+	<para>Firewall/SELinux configuration has been moved to the final
+	  installation phase called
+	  <application>firstboot</application>.
+	</para>
+      </listitem>
+      <listitem>
+	<para>Rendering of HTML pages during install is now done using
+	  the <command>gtkhtml</command> widget for better capability.
+	</para>
+      </listitem>
+      <listitem>
+	<para>Kickstart has been refactored into its own package -
+	  <filename>pykickstart</filename> - containing parser and
+	  writers. As a result of this change, validation and extension
+	  of kickstart is now much easier.
+	</para>
+      </listitem>
+      <listitem>
+	<para>Serial mice are no long formally supported in the
+	  installer nor in &FC;. </para>
+      </listitem>
+    </itemizedlist>
+  </section>
+  <section id="sn-install-related-issues">
     <title>Installation-Related Issues</title>
     <itemizedlist>
       <listitem>
@@ -221,7 +273,6 @@
 	  the installation, and add the "<command>nofb</command>" option
 	  to the boot command line.
 	</para>
-
 	<note>
 	  <title>Note</title>
 	  <para>


Index: kernel-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/kernel-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- kernel-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ kernel-en.xml	23 Nov 2005 05:38:24 -0000	1.3
@@ -12,298 +12,258 @@
 ]>
 -->
 <section id="sn-kernel">
-  <title>
-    Linux Kernel
-  </title>
-  <section id="sn-kernel-lotsa">
+  <title>Linux Kernel</title>
+  <section id="sn-kernel-version">
     <title>Version</title>
     <para>
-      The distribution is based on the 2.6 series of the Linux kernel. &FC; may include
-      additional patches for improvements, bug fixes, or additional
-      features. For this reason, the &FC; kernel may not be
-      line-for-line equivalent to the vanilla<firstterm></firstterm> kernel from the
-      <ulink
-  url="http://www.kernel.org"><filename>kernel.org</filename></ulink>
+      This distribution is based on the 2.6 series of the Linux kernel.
+      &FC; may include patches for improvements, bug fixes, or
+      additional features. For this reason, the &FCl kernel may not be
+      line-for-line equivalent to the <firstterm>vanilla
+	kernel</firstterm> from the <ulink
+	url='http://www.kernel.org/'>http://www.kernel.org/</ulink>
       website.
     </para>
     <para>
-      You may obtain a list of any such patches by using the command on the &FC; package:
-    </para>
-<screen width="56">
-<command>rpm <parameter class="option">-qpl</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
+      You may obtain a list of any such patches by using this command
+      on the &FC; package:</para>
+<screen>
+<command>rpm -qpl kernel-&lt;version>.src.rpm</command>
 </screen>
   </section>
   <section id="sn-kernel-flavors">
     <title>Kernel Flavors</title>
-    <para>
-      &FC; includes the following kernel builds:
-    </para>
+    <para>&FC; includes the following kernel builds: </para>
     <itemizedlist>
       <listitem>
-        <para>Native kernel, in both uniprocessor and
-	  <abbrev>SMP</abbrev> varieties. Configured sources are
-	  available in the
+	<para>Native kernel, in both uniprocessor and SMP (Symmetric
+	  Multi Processor) varieties. Configured sources are available
+	  in the
 	  <filename>kernel-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename> 
-	  package.
-        </para>
+	  package. 
+	</para>
       </listitem>
       <listitem>
-        <para>
-          Virtual kernel for use with the <application>Xen</application>
-	  emulator package. Configured sources are available in the
+	<para>Virtual kernel for use with the Xen emulator package.
+	  Configured sources are available in the
 	  <filename>kernel-xen0-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename> 
-	  package.
-        </para>
+	  package. </para>
       </listitem>
     </itemizedlist>
     <para>
       Sources for both kernel flavors may be installed at the same time.
       The files are installed into the
-      <filename>/usr/src/kernels/<replaceable>version</replaceable>[-xen0]-<replaceable>arch</replaceable>/</filename>
-      tree. Use the command:
-    </para>
-<screen width="56">
-<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename></command>
-</screen>
-    <para>
+      <filename>/usr/src/kernels/<replaceable>version</replaceable>[-xen0]-<replaceable>arch</replaceable>/</filename> 
+      tree.  Use the command <command>rpm -Uvh
+	kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</command> 
       as appropriate.
     </para>
-    <tip>
-      <title>Following Generic Textbooks About the Linux Kernel</title>
+    <note> 
+      <title>No separate SMP kernel for x86_64</title>
       <para>
-        Many of the tutorials, examples, and textbooks about Linux
-	kernel development assume the kernel sources are installed under
-	the <filename>/usr/src/linux</filename> directory. If you make a
-	symbolic link, as shown below, you should be able to use those
-	learning materials with the &FC; packages. Install the
-	appropriate kernel sources, as shown earlier, and then:
+	The default kernels in x86_64 architecture provide the SMP
+	capability. There is no seperate SMP kernel available for this
+	architecture in &FC; &FCVER;.
       </para>
-<screen width="56">
-<command>ln <parameter class="option">-s</parameter> <filename>/usr/src/kernels/kernel-<replaceable>all-the-rest</replaceable></filename> <filename>/usr/src/linux</filename></command>
-</screen>
-    </tip>
+    </note>
   </section>
-  <!--
-  <tip>
-    <title>Using <command>yum</command> to Remove Kernel
-    Packages</title>
+  <section>
+    <title>Following Generic Textbooks</title>
     <para>
-      &FC; &LOCALVER; contains support for clustering systems using CMAN and GFS.
-      These kernels require assistance from some user-space packages.
-      These packages are not removed when using <command>rpm
-      -e</command> to remove older versions of the kernel packages.
+      Many of the tutorials, examples, and textbooks about Linux
+      kernel development assume the kernel sources are installed under
+      the <filename>/usr/src/linux/</filename> directory. If you make a symbolic
+      link, as shown below, you should be able to use those learning
+      materials with the &FC; packages. Install the appropriate
+      kernel sources, as shown earlier, and then do this:
     </para>
+<screen>
+<command>ln -s /usr/src/kernels/kernel-<replaceable>version</replaceable>-<replaceable>arch</replaceable> /usr/src/linux</command>
+</screen>
+  </section>
+  <section id="sn-kernel-dev">
+    <title>Preparing for Kernel Development</title>
     <para>
-      When using <command>rpm -e kernel-<replaceable>version</replaceable> </command> to remove the kernel, you must also remove the assisting user-space packages.  You may wish to consider a dependency resolving tool such as <command>yum remove kernel-<replaceable>version</replaceable> </command>.
-      This automatically removes any dependent packages.
+      &FC; &FCVER; does not include the <filename>kernel-source</filename>
+      package provided by older versions. Instead, configured sources
+      are available as described in <xref linkend="sn-kernel-flavors"/>.
+      Users that require access to &FC; original kernel sources
+      can find them in the kernel <filename>.src.rpm</filename> package.
     </para>
-  </tip>
-  -->
-  <section id="sn-kernel-exploding">
-    <title>
-      Preparing for Kernel Development
-    </title>
     <para>
-      &DISTRO; &DISTROVER; does not include the
-      <filename>kernel-source</filename> package provided by older
-      versions. Instead, configured sources are available as described
-      in <xref
-  linkend="sn-kernel-flavors"/>. Users that require access to &FC;
-      original kernel sources can find them in the
-      <filename>kernel</filename> <filename>.src.rpm</filename> package.
       To create an exploded source tree from this file, perform the
       following steps:
     </para>
-    <important>
-    <title>These Instructions Refer to the Currently-running Kernel!</title>
-      <para>
-	To simplify the following directions, the assumption is that you
+    <tip>
+      <title>Instructions refer to currently-running kernel</title>
+	<para>
+	To simplify the following directions, it is assumed that you
 	want to configure the kernel sources to match your
-	currently-running kernel. In the steps below, you must
-	understand that the phrase
-	<replaceable>version</replaceable> refers to the kernel
-	version shown by this command:
+	currently-running kernel. In the steps below, the phrase
+	<replaceable>version</replaceable> refers to the kernel version
+	shown by the command  <command>uname -r</command>. 
       </para>
-<screen width="56">
-<command>uname <parameter class="option">-r</parameter></command>
-</screen>
-    </important>
-    <procedure id="sn-kernel-exploding-steps">
+    </tip>
+    <procedure>
       <step>
-        <para>
-          Obtain the
+	<para>
+	  Obtain the
 	  <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename> 
 	  file from one of the following sources:
-        </para>
-        <itemizedlist>
-          <listitem>
-            <para>The <filename>SRPMS/</filename> directory on the
-	      appropriate <wordasword>SRPMS</wordasword>
-	      <abbrev>CD</abbrev> <filename>ISO</filename> image.
-              </para>
-          </listitem>
-          <listitem>
-            <para>The FTP site where you got the kernel package.
-            </para>
-          </listitem>
-          <listitem>
-            <para>By running the following command:
-            </para>
-<!-- FIXME up2date is sorta deprecated for FC, how to do this with yum? -->
-<screen width="56">
-<command>up2date <parameter class="option">--get-source</parameter> <filename>kernel</filename></command>
+	</para>
+	<itemizedlist>
+	  <listitem>
+	    <para>The SRPMS directory on the appropriate SRPMS CD iso
+	      image.
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>The FTP site where you got the kernel package.
+	    </para>
+	  </listitem>
+	</itemizedlist>
+	<para>
+	  Install by running this command:
+	</para>
+<screen>
+<command>yum install yum-utils yumdownloader --source kernel</command>
 </screen>
-          </listitem>
-        </itemizedlist>
       </step>
       <step>
-        <para>
-          Install
+	<para>
+	  Install
 	  <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename> 
-	  using the command:
-        </para>
-<screen width="56">
-<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
-</screen>
-        <para>
-          This writes the <abbrev>RPM</abbrev> contents into
+	  using the command <command>rpm -Uvh
+	    kernel-<replaceable>version</replaceable>.src.rpm</command>.
+	</para>
+	<para>
+	  This writes the RPM contents into
 	  <filename>/usr/src/redhat/SOURCES</filename> and
 	  <filename>/usr/src/redhat/SPECS</filename>.
-        </para>
+	</para>
       </step>
       <step>
-        <para>
-          Prepare the kernel sources using the commands:
-        </para>
-<screen width="56">
-<command>cd <filename>/usr/src/redhat/SPECS</filename></command>
-<command>rpmbuild <parameter class="option">-bp --target $(arch)</parameter> <filename>kernel-2.6.spec</filename></command>
-</screen>
-        <para>
-          The kernel source tree is located in the
-	  <filename>/usr/src/redhat/BUILD/kernel-</filename><replaceable>version</replaceable> 
+	<para>Prepare the kernel sources with these commands:
+	</para>
+<screen>
+<command>cd /usr/src/redhat/SPECS
+rpmbuild -bp --target $(arch) kernel-2.6.spec</command>
+</screen>
+	<para>
+	  The kernel source tree is then located in the
+	  <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable>/</filename> 
 	  directory. It is common practice to move the resulting
-	  <filename>linux-<replaceable>version</replaceable></filename>
-	  directory to the <filename>/usr/src</filename> tree; while not
-	  strictly necessary, doing so matches you with the
-	  generally-available documentation.
-        </para>
-<screen width="56">
-<command>cd <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
-<command>mv <filename>linux-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
-<command>cd <filename>/usr/src</filename></command>
-<command>ln <parameter class="option">-s</parameter> <filename>./linux-<replaceable>version</replaceable></filename> <filename>linux</filename></command>
-<command>cd <filename>/usr/src/linux</filename></command>
+	  <filename>linux-<replaceable>version</replaceable></filename> directory to the
+	  <filename>/usr/src/</filename> tree; while not strictly
+	  necessary, you can do this to match the generally-available kernel
+	  documentation.
+	</para>
+<screen>
+<command>cd /usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable>
+mv linux-<replaceable>version</replaceable> /usr/src/
+cd /usr/src\
+ln -s ./linux-<replaceable>version</replaceable> linux
+cd /usr/src/linux</command>
 </screen>
       </step>
       <step>
-        <para>
-          The configurations for the specific kernels shipped in
-	  &DISTRO; &DISTROVER; are in the <filename>configs/</filename>
-	  directory. For example, the i686 SMP configuration file is
-	  named
+	<para>
+	  The configurations for the specific kernels shipped in &FC;
+	  are in the <filename>configs/</filename> directory. For
+	  example, the i686 SMP configuration file is named
 	  <filename>configs/kernel-<replaceable>version</replaceable>-i686-smp.config</filename>. 
 	  Issue the following command to place the desired configuration
-	  file in the proper place for building:
-        </para>
-<screen width="56">
-<command>cp <filename>configs/<replaceable>desired-config-file</replaceable></filename> <filename>.config</filename></command>
-</screen>
-        <para>
-          You can also find the <filename>.config</filename> file that
+	  file in the proper place for building: <command>cp
+	    configs/<replaceable>desired-config-file</replaceable>
+	    .config</command>
+	</para>
+	<para>
+	  You can also find the <filename>.config</filename> file that
 	  matches your current kernel configuration in the
-	  <filename>/lib/modules/</filename><replaceable>version</replaceable><filename>/build/.config</filename> 
+	  <filename>/lib/modules/<replaceable>version</replaceable>/build/.config</filename> 
 	  file.
-        </para>
+	</para>
       </step>
       <step>
-        <para>
-          Every kernel gets a name based on its version number. This is
-	  the value the <command>uname -r</command> command displays.
-	  The kernel name is defined by the first four lines of the
-	  kernel <filename>Makefile</filename>. To protect the innocent,
-	  the <filename>Makefile</filename> has been changed to generate
-	  a kernel with a different name from that of the running
-	  kernel. Before a module can be accepted by the running kernel,
-	  that module must have been compiled for a kernel with the
-	  correct name.  To do this, you must edit the kernel
-	  <filename>Makefile</filename>
-        </para>
-        <para>
-          For example, if the <command>uname -r</command> returns the
-	  string <systemitem
-	    class="osname">2.6.11-1.234_FC4</systemitem>, change the
-	  <systemitem class="macro">EXTRAVERSION</systemitem> definition
-	  from this:
-        </para>
-<screen width="60">
+	<para>
+	  Every kernel gets a name based on its version number. This is
+	  the value displayed by the command <command>uname
+	    -r</command>. The kernel name is defined by the first four
+	  lines of the kernel Makefile. To protect from mistakes, the
+	  Makefile has been changed to generate a kernel with a
+	  different name from that of the running kernel. Before a
+	  module can be accepted by the running kernel, that module must
+	  have been compiled for a kernel with the correct name. To do
+	  this, you must edit the kernel Makefile.
+	</para>
+    <para>For example, if <command>uname -r</command> returns the string
+      <computeroutput>2.6.11-1.234_FC4</computeroutput>, change the
+      <envar>EXTRAVERSION</envar> definition from this:
+    </para>
+<screen>
 EXTRAVERSION = -prep
 </screen>
-        <para>
+	<para>
 	  to this:
 	</para>
-<screen width="60">
+<screen>
 EXTRAVERSION = -1.234_FC4
 </screen>
-        <para>
-          That is, substitute everything from the final dash onward.
-        </para>
-      </step>
+	<para>This represents everything from the final dash onward in the
+	  package name.
+	</para>
+      </step> 
       <step>
-        <para>
-          Issue the following command:
-        </para>
-<screen width="56">
+	<para>
+	  Issue the following command:
+	</para>
+<screen>
 <command>make oldconfig</command>
 </screen>
-      </step>
+	<para>You can then proceed as usual. </para></step>
     </procedure>
-    <para>
-      You can then proceed as usual.
-    </para>
   </section>
-  <section id="sn-kernel-3rdparty">
+  <section id="sn-kernel-modules-building">
     <title>Building Only Kernel Modules</title>
     <para>
-      An exploded source tree is <emphasis>not</emphasis> required to
-      build a kernel module, such as your own device driver, against the
-      currently in-use kernel.
-    </para>
-    <para>
-      For example, to build the <filename>foo.ko</filename> module,
-      create the following <filename>Makefile</filename> in the
+      An exploded source tree is not required to build a kernel module,
+      such as your own device driver, against the currently in-use
+      kernel. For example, to build the <filename>foo.ko</filename>
+      module, create the following <filename>Makefile</filename> in the
       directory containing the <filename>foo.c</filename> file:
     </para>
-<programlisting width="56">
+<screen>
 obj-m := foo.o
 
 KDIR  := /lib/modules/$(shell uname -r)/build
 PWD   := $(shell pwd)
 
-default:
-    $(MAKE) -C $(KDIR) M=$(PWD) modules
-</programlisting>
-      <para>
-      Issue the <command>make</command> command to build the
+ndefault:
+      $(MAKE) -C $(KDIR) M=$(PWD) modules
+</screen>
+    <para>Issue the <command>make</command> command to build the
       <filename>foo.ko</filename> module.
-    </para>
+</para>
   </section>
-  <section id="sn-kernel-coop">
+  <section id="kernel-user-space-depencies">
     <title>User Space Dependencies on the Kernel</title>
     <para>
-      &DISTRO; adds support for clustered systems. This requires a
-      special kernel that works in conjunction with some user-space
-      utilities, such as management daemons. Consequently, to remove
-      such a kernel, perhaps after an update, you
-      <emphasis>cannot</emphasis> simply use the <command>rpm -e
+      &PROD; &PRODVER; has support for clustered storage through the Red
+      Hat GFS file system. This requires a special kernel that works in
+      conjunction with some user-space utilities, such as management
+      daemons. Consequently, to remove such a kernel, perhaps after an
+      update, you cannot simply use the <command>rpm -e
 	kernel-<replaceable>version</replaceable></command> command as
       in earlier distributions because these user space packages depend
-      on the kernel package. You may either list both the kernel package
-      and its user space dependent packages on the <command>rpm
-	-e</command> command, or you may wish to use the <command>yum
-	remove kernel-<replaceable>version</replaceable></command>
-      command instead since <command>yum</command> automatically removes
-      dependent packages if necessary.
+      on the kernel package.
+    </para>
+    <para>
+      You may either list both the kernel package and its user space
+      dependent packages on the <command>rpm -e</command> command, or
+      you may wish to use the <command>yum remove
+	kernel-<replaceable>version</replaceable></command> command
+      instead since <command>yum</command> automatically removes
+      dependent packages if necessary. 
     </para>
   </section>
 </section>


Index: multimedia-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/multimedia-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- multimedia-en.xml	25 Oct 2005 09:07:12 -0000	1.3
+++ multimedia-en.xml	23 Nov 2005 05:38:24 -0000	1.4
@@ -69,12 +69,8 @@
     <para>
       Several programs are excluded from &FC; and &FEX; due to licensing
       issues.  These include programs that provide MP3 and DVD support,
-      Flash Player and Real Player.  Users who wish to use these
-      programs or restricted formats have to acquire additional
-      packages from third-party repositories.  Many of the multimedia
-      applications in the Fedora repositories support plugins, so
-      support for new formats can be easily added or removed.  For more
-      on this subject, please see:
+      Flash Player and Real Player.  For more on this subject, please
+      refer to:
     </para>
     <para>
       <ulink url='http://fedoraproject.org/wiki/ForbiddenItems'>http://fedoraproject.org/wiki/ForbiddenItems</ulink>


Index: project-overview-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/project-overview-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project-overview-en.xml	25 Oct 2005 02:48:50 -0000	1.1
+++ project-overview-en.xml	23 Nov 2005 05:38:24 -0000	1.2
@@ -47,27 +47,35 @@
 	  Documentation Project
 	</para>
       </listitem>
-    </itemizedlist>
-    <para>
-      To subscribe to any of these lists, send an email with the word
-      "subscribe" in the subject to
-      <computeroutput><replaceable>&lt;listname&gt;</replaceable>-request</computeroutput>
-      (where
-      <computeroutput><replaceable>&lt;listname&gt;</replaceable></computeroutput>
-      is one of the above list names.)
-    </para>
-    <para>
-      Alternately, you can subscribe through the Web interface:
-    </para>
-    <para>
-      <ulink url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
-    </para>
+    <listitem>
+      <para>
+	fedora-ambassadors-list at redehat.com &mdash; For community
+	members who represent the &PROJ; in public.
+      </para>
+    </listitem>
+  </itemizedlist>
+  <para>
+    To subscribe to any of these lists, send an email with the word
+    "subscribe" in the subject to
+    <computeroutput><replaceable>&lt;listname&gt;</replaceable>-request</computeroutput>
+    (where
+    <computeroutput><replaceable>&lt;listname&gt;</replaceable></computeroutput>
+    is one of the above list names.)
+  </para>
+  <para>
+    Alternately, you can subscribe through the Web interface:
+  </para>
+  <para>
+    <ulink url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
+  </para>
+  <!-- Aren't we quite past this?  Saving just in case we are not.
     <para>
       If you have subscribed in the past to rhl-list, rhl-beta-list,
       rhl-devel-list, or rhl-docs-list, your subscriptions have been
       retained.
     </para>
-    <para>
+  -->
+  <para>
       The &PROJ; also includes an IRC (Internet Relay Chat) channel.  IRC is
       a real-time, text-based form of communication.  With it, you can have
       conversations with multiple people in an open channel or chat with someone
@@ -88,7 +96,7 @@
     <para>
       In order to talk on the <filename>#fedora</filename> channel, you
       will need to register your nickname (<firstterm>nick</firstterm>).
-      Instructions are given when you <command>/join</command> the
+      Instructions are given when you first <command>/join</command> the
       channel.
     </para>
     <note>



From fedora-docs-commits at redhat.com  Wed Nov 23 06:29:14 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 23 Nov 2005 01:29:14 -0500
Subject: docs-common/images - New directory
Message-ID: <200511230629.jAN6TEmX009916@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/images
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9902/images

Log Message:
Directory /cvs/docs/docs-common/images added to the repository




From fedora-docs-commits at redhat.com  Wed Nov 23 06:30:31 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 23 Nov 2005 01:30:31 -0500
Subject: docs-common/images Makefile, NONE, 1.1 watermark.png, NONE,
	1.1 watermark.svg, NONE, 1.1
Message-ID: <200511230630.jAN6UVbC009945@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/images
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9927

Added Files:
	Makefile watermark.png watermark.svg 
Log Message:
Sample DRAFT watermark image, SVG source, and a Makefile to rule them all.



--- NEW FILE Makefile ---
.SUFFIXES: .png .svg

%.png: %.svg
	batik -m image/png -h 768 -w 1024 -d `pwd`/$@ file://`pwd`/$<

SVGFILES=watermark.svg
PNGFILES=${SVGFILES:.svg=.png}

all:	${PNGFILES}

clean:

distclean clobber: clean
	${RM} ${PNGFILES}

check:	${PNGFILES}
	xv ${PNGFILES}


--- NEW FILE watermark.svg ---
<?xml version="1.0"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
              "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"[
  <!ENTITY  bgColor   "rgb( 200, 200, 200 )" >
  <!ENTITY  fgColor   "rgb( 255, 100, 100 )" >
]>
<svg viewBox="0 0 1023 767" xmlns="http://www.w3.org/2000/svg" version="1.1">
  <title>Fedora Doc Project Watermark</title>
  <desc>The word DRAFT rendered in grey at 45 degrees</desc>
  <g fill="&bgColor;" font-family="Helvetica" font-size="1in" stroke="&bgColor;" stroke-width="10" text-anchor="start" transform="translate( 1, 1 )">
    <g transform="translate( 512, 384 ) rotate( -45 )">
      <text font-stretch="wider" text-anchor="middle" x="0" y="0">DRAFT</text>
      <text fill="&fgColor;" font-size="0.6in" font-stretch="wider" stroke="rgb( 230, 200, 200 )" stroke-width="1.5" text-anchor="middle" x="0" y="1in">Not for reference.</text>
    </g>
  </g>
</svg>



From fedora-docs-commits at redhat.com  Wed Nov 23 06:37:10 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 23 Nov 2005 01:37:10 -0500
Subject: docs-common/css fedora-draft.css,NONE,1.1 fedora.css,1.8,1.9
Message-ID: <200511230637.jAN6bAop009981@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/css
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9963

Modified Files:
	fedora.css 
Added Files:
	fedora-draft.css 
Log Message:
FDP stylesheet for DRAFT versions. Needs "/watermark.png" in top level
HTML directory, get from "../images".



--- NEW FILE fedora-draft.css ---
/*

CSS for Red Hat Linux Project docs from the Documentation Project

Written by Tammy Fox and Garrett LeSage

Copyright 2003 Tammy Fox, Garrett LeSage, and Red Hat, Inc.
Copywight 2005 Tommy Reynolds <Tommy.Reynolds at MegaCoder.com>

License: GPL

*/

body	{
	background-attachment	scroll;
	background-color:	#FEFEFF;
	background-image:	url('watermark.png');
	background-position:	top center;
	background-repeat:	repeat;
}

li p {
	display: inline;
}

div.table table {
	width: 95%;
	background-color: #DCDCDC;
	color: #000000;
	border-spacing: 0;
}

div.table table th {
	border: 1px solid #A9A9A9;
	background-color: #A9A9A9;
	color: #000000;
}

div.table table td {
	border: 1px solid #A9A9A9;
	background-color: #DCDCDC;
	color: #000000;
	padding: 0.5em;
	margin-bottom: 0.5em;
	margin-top: 2px;

}

div.note table, div.tip table, div.important table, div.caution table, div.warning table {
	width: 95%;
	border: 2px solid #D0D0B0;
	background-color: #FAF9E0;
	color: #000000;
	/* padding inside table area */
	padding: 0.5em;
	margin-bottom: 0.5em;
	margin-top: 0.5em;
}

.qandaset table {
	border-collapse: collapse;
}
.qandaset {
}
.qandaset tr.question {
}
.qandaset tr.question td {
	font-weight: bold;
	padding: 1em 1em 0;
}
.qandaset tr.answer td {
	padding: 0.25em 1em 1.5em;
}
.qandaset tr.question td, .qandaset tr.answer td {
}

hr {
	border: 0;
	border-bottom: 1px solid #ccc;
}

h1, h2, h3, h4 {
	font-family: luxi sans,sans-serif;
	color: #22437f;
	font-weight: bold;
}
h1 {
	font-size: 1.75em;
}

h2 {
	font-size: 1.25em;
}

h3 {
	font-size: 1.1em;
}

a:link {
	color: #900;
}
a:visited {
	color: #48468f;
}
a:hover {
	color: #f20;
}

code.screen, pre.screen {
	font-family: monospace;
	font-size: 1em;
	display: block;
	padding: 10px;
	border: 1px solid #bbb;
	background-color: #eee;
	color: #000;
	overflow: auto;
	border-radius: 2.5px;
	-moz-border-radius: 2.5px;
	margin: 0.5em 2em;
}

div.example {
	padding: 10px;
	border: 1px solid #bbb;
	margin: 0.5em 2em;
}

.procedure ol li {
	margin-bottom: 0.5em;
}
.procedure ol li li {
	/* prevent inheritance */
	margin-bottom: 0em;
}

.itemizedlist ul li {
	margin-bottom: 0.5em;
}
.itemizedlist ul li li {
	/* prevent inheritance */
	margin-bottom: 0em;
}

p.title	{
	text-align: center;
}


Index: fedora.css
===================================================================
RCS file: /cvs/docs/docs-common/css/fedora.css,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora.css	3 Nov 2005 15:31:40 -0000	1.8
+++ fedora.css	23 Nov 2005 06:37:03 -0000	1.9
@@ -10,6 +10,17 @@
 
 */
 
+/* 
+This "body" section is included for reference.  Diff with fedora-draft.css
+body	{
+	background-attachment	scroll;
+	background-color:	#FEFEFF;
+	background-image:	url('watermark.png');
+	background-position:	top center;
+	background-repeat:	repeat;
+}
+*/
+
 li p {
 	display: inline;
 }



From fedora-docs-commits at redhat.com  Wed Nov 23 06:40:33 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 23 Nov 2005 01:40:33 -0500
Subject: docs-common/bin use-draft-css,NONE,1.1
Message-ID: <200511230640.jAN6eXpS010025@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10007

Added Files:
	use-draft-css 
Log Message:
Shell script to switch to the "DRAFT" CSS stylesheet in an HTML directory.



--- NEW FILE use-draft-css ---
#!/bin/bash
########################################################################
# Tommy.Reynolds <Tommy.Reynolds at MegaCoder.com>
# International copyright secured (C) 2005, All rights reserved.
# This software is licensed under the GPL.
########################################################################
# Do surgery on the *.html files to reference the draft CSS stylesheet
#
# Use like this:
#
#	use-draft-css /path/to/docdir
#
########################################################################
# You will need to manually copy "../css/fedora-draft.css" and 
# "../images/watermark.png" into the HTML's top-level directory.
########################################################################
USAGE="usage: $(basename $0) /path/to/docdir"
SILENT=yes
while getopts v c
do
	case "${c}" in
	v )	SILENT="";;
	* )	echo "${USAGE}" >&2; exit 1;;
	esac
done
shift $(expr ${OPTIND} - 1)
if [ $# -gt 1 ]; then
	echo "${USAGE}" >&2
	exit 1
fi
find ${1:-.} -iname '*.html' -print					|
while read f; do
	[ "${SILENT}" ] || echo ${f}
	sed 's/href="fedora.css"/href="fedora-draft.css"/' ${f} >${f}.tmp
	mv ${f}.tmp ${f}
done



From fedora-docs-commits at redhat.com  Wed Nov 23 06:56:04 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 23 Nov 2005 01:56:04 -0500
Subject: release-notes legacy-en.xml, 1.1, 1.2 package-notes-en.xml, 1.4,
	1.5 security-en.xml, 1.2, 1.3 splash-en.xml, 1.3,
	1.4 web-servers-en.xml, 1.2, 1.3 xorg-en.xml, 1.2, 1.3
Message-ID: <200511230656.jAN6u4ic010144@cvs-int.fedora.redhat.com>

Author: kwade

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10120

Modified Files:
	legacy-en.xml package-notes-en.xml security-en.xml 
	splash-en.xml web-servers-en.xml xorg-en.xml 
Log Message:
Last of the transfer of content from the Wiki, time to tag, build, and post.


Index: legacy-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/legacy-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legacy-en.xml	25 Oct 2005 08:34:00 -0000	1.1
+++ legacy-en.xml	23 Nov 2005 06:55:57 -0000	1.2
@@ -1,3 +1,50 @@
+<section id="sn-legacy">
+    <title>Legacy Information</title>
+    
+  <note>
+    <title><command>Slocate</command> has been replaced with
+    <command>mlocate</command> in this release.</title>
+    <para>
+      The <command>/usr/bin/{locate,updatedb}</command>
+      implementation <command>slocate</command> was replaced by mlocate.
+    </para>
+  </note>
+    <itemizedlist>
+      <listitem>
+      <para>The <command>locate</command> command should be completely
+      compatible.
+      </para>
+      </listitem>
+    </itemizedlist>
+    <itemizedlist>
+      <listitem>
+      <para><filename>/etc/updatedb.conf</filename> is compatible for correct
+	configuration files
+      </para>
+    </listitem>.
+    <listitem>
+      <para>Syntax errors that <command>slocate</command> would not
+	detect are now reported.
+      </para>
+    </listitem>
+    <listitem>
+      <para>The <envar>DAILY_UPDATE</envar> variable is not
+	supported.
+      </para>
+    </listitem>
+    <listitem>
+      <para>The <command>updatedb</command> command is not compatible, custom
+	scripts using <command>updatedb</command> might have to be
+	changed.
+      </para>
+      </listitem>
+    </itemizedlist>
+  <para>
+    The LinuxThreads library, which has been deprecated in &FC; 4, is no
+    longer available in this release. NPTL has been the default
+    threading library since Red Hat Linux 9.
+  </para>
+</section>
 <!--
 Local variables:
 mode: xml


Index: package-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- package-notes-en.xml	25 Oct 2005 19:40:56 -0000	1.4
+++ package-notes-en.xml	23 Nov 2005 06:55:57 -0000	1.5
@@ -114,6 +114,7 @@
 <command>auditctl -e 1</command>
 </screen>
     </section>
+<!--
     <section id="sn-nptl">
       <title>LinuxThreads versus NPTL</title>
       <para>
@@ -178,6 +179,7 @@
 	In general, conversion to using NPTL has not been an issue.
       </para>
     </section>
+    -->
     <section>
       <title>Enabling the <filename>slocate</filename> Database</title>
       <para>
@@ -233,18 +235,7 @@
 	<option>~/.ssh/config</option> file.
       </para>
     </section>
-    <section id="sn-perl">
-      <title>Perl Binary Compat Symlinks</title>
-      <para>
-	Binary compat symlinks for <filename>perl-5.8.0</filename>,
-	<filename>perl-5.8.1</filename>, and
-	<filename>perl-5.8.2</filename> have been removed.  If you have
-	perl modules built with those older versions of perl, you need
-	to rebuild using the <filename>perl-5.8.6</filename> contained
-	in &FC; &LOCALVER;.
-      </para>
-    </section>
-    &SERVER-TOOLS;
+<!--    &SERVER-TOOLS; -->
     &JAVA-PACKAGE;
   </section>
   <section id="sn-packages-core">
@@ -253,16 +244,6 @@
       This section contains the most elemental components of &DISTRO;,
       including the kernel.
     </para>
-    <section>
-      <title>yum</title>
-      <para>
-	The sqllite database is now used by yum, and makes performance
-	noticeably faster.
-      </para>
-      <para>
-	The Fedora Extras repository is now enabled by default.
-      </para>
-    </section>
     &KERNEL;
     &SECURITY;
   </section>


Index: security-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/security-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- security-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ security-en.xml	23 Nov 2005 06:55:57 -0000	1.3
@@ -4,15 +4,44 @@
     This section highlights various security items from &FC;.
   </para>
   <para>
-    <computeroutput>Pam_stack</computeroutput> is deprecated. More
-    details available from fedora-test-list (<ulink
-    url="http://www.redhat.com/mailman/listinfo/fedora-test-list">http://www.redhat.com/mailman/listinfo/fedora-test-list</ulink>
+    <computeroutput>Pam_stack</computeroutput> is deprecated. Linux-PAM
+    0.78 and later contain the include directive that obsoletes the
+    <computeroutput>pam_stack</computeroutput> module.
+    <computeroutput>pam_stack</computeroutput> module usage is logged
+    with a deprecation warning.  It might be removed in a future
+    release.
   </para>
   <section id="sn-security-highlights">
     <title>Security Highlights</title>
     <para>
       This section highlights various security items from &FC;.
     </para>
+    <variablelist>
+      <varlistentry>
+	<term>Buffer Overflow detection and variable reordering</term>
+	<listitem>
+	  <para>For this release, all of the software in the &FC; and
+	    &FEX; software repositories is compiled using a security
+	    feature called <firstterm>fstack-protecter</firstterm>.
+	    fstack-protector puts a canary value on the stack of
+	    <computeroutput>key</computeroutput> functions.  Just before
+	    the return address and just before returning from that
+	    value, that canary value is verified.  If there was a buffer
+	    overflow, the canary no longer matches and the program
+	    aborts. The canary value is random for each time the
+	    application is started and makes it impossible to guess
+	    remotely. This is a security feature that has been
+	    backported from GCC 4.1 to the version of the GCC compiler
+	    used in &FC; &FCVER;. 
+	  </para>
+	  <para>
+	    This is in addition to using <envar>FORTIFY_SOURCE</envar>
+	    from &FC; 4 onwards.
+	  </para>
+	</listitem>
+      </varlistentry>    
+    
+    <section>
     <para>
       Digital certificates are now centralised in directories
       under <filename>/etc/pki/</filename>. Users performing an upgrade must


Index: splash-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- splash-en.xml	25 Oct 2005 09:07:12 -0000	1.3
+++ splash-en.xml	23 Nov 2005 06:55:57 -0000	1.4
@@ -1,18 +1,33 @@
 <section id="sn-splash">
   <title>Welcome to &FC; &LOCALVER;</title>
-  <caution>
-    <title>Information Out-of-Date</title>
-    <para>
-      The content in this section needs to be updated for &DISTRO;
-      &DISTROVER;
-    </para>
-  </caution>
   <para>
     &FC; is a completely free, user friendly, and secure general purpose
-    platform based on Linux.  The &FP; is an open source project that
-    pioneers leading edge technology and concepts sponsored by &RH; and
+    platform based on Linux that is always free for anyone to use,
+    modify, and distribute, now and forever.  The &FP; is an open source project that
+    pioneers leading edge technology and concepts, which is sponsored by &RH; and
     supported by the &FED; community.
   </para>
+  <caution>
+    <title>This is a test release, not intended for end-users</title>
+    <para>
+      This is a test release and is provided for developers and testers
+      to participate and provide feedback. It is not meant for end
+      users.
+    </para>
+    <para>
+      Subscribe to the fedora-test and fedora-devel mailings lists to
+      keep track of important changes in the current development
+      versions and provide feedback to the developers. &FP; requests you
+      to file bug reports and enhancements to provide a improved final
+      release to end users. For more information on this, refer to the
+      following document:
+    </para>
+    <para>
+      <ulink
+	url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'>http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink>. 
+      
+    </para>
+  </caution>
   <tip>
     <title>Latest Release Notes on the Web</title>
     <para>
@@ -39,13 +54,11 @@
     Refer to these webpages to find out more information about &FED;:
   </para>
   <itemizedlist>
-<!-- FIXME Return when the section is updated
     <listitem>
       <para>
 	<xref linkend="sn-new-in-fc"/>
       </para>
     </listitem>
--->
     <listitem>
       <para>
 	<xref linkend="sn-intro"/> &mdash; Technical release notes
@@ -70,6 +83,67 @@
       </para>
     </listitem>
   </itemizedlist>
+  <section id="sn-new-in-fc">
+    <title>What's New In &FC; &FCVER;</title>
+    <itemizedlist>
+      <listitem>
+        <para>Xen Virtualisation software and yum package manager are
+	  now well integrated within the &FED; installer. The installer
+	  interface is more streamlined.  Remote logging and improved
+	  support for tracebacks is included.
+	</para>
+      </listitem>
+      <listitem>
+        <para><application>Pup</application>, a graphical updater using
+	  yum, has replaced <application>rhn-applet</application>.
+	</para>
+      </listitem>
+      <listitem>
+        <para>GNOME 2.12 and KDE 3.4 desktop environments are
+        available.
+	</para>
+      </listitem>
+      <listitem>
+        <para>GNOME Power Manager and GNOME Screensaver are available as
+	  a technology preview within this release. 
+	</para>
+      </listitem>
+      <listitem>
+        <para>
+          OpenOffice.org 2.0 final release is included. OpenOffice.org
+	  now uses system versions for many of the libraries leading to
+	  increased performance and efficiency.
+	</para>
+      </listitem>
+      <listitem>
+        <para>Xorg X11R7 release candidate 2 has been included in this
+	  release.  This is the first modular version, which helps in
+	  providing additional features and bug fixes at a faster pace.
+	</para>
+      </listitem>
+      <listitem>
+        <para>Kernel 2.6.14 is included. Software suspend is enabled in this
+        release.
+	</para>
+      </listitem>
+      <listitem>
+        <para>SCIM has replaced IIMF in &FC; in this release.
+	</para>
+      </listitem>
+      <listitem>
+	<para>There are changes in the animated mouse cursor theme.
+	</para>
+      </listitem>
+      <listitem>
+        <para>&FP; now has a new logo.
+	</para>
+      </listitem>
+    </itemizedlist>
+    <para>The proposed plans for Fedora in this version are available
+      from <ulink
+	url='http://fedoraproject.org/wiki/RoadMap'>http://fedoraproject.org/wiki/RoadMap</ulink>.
+    </para>
+  </section>
 <!-- commented out until the content can be updated
   <section id="sn-new-in-fc">
     <title>New in &FC; &LOCALVER;</title>


Index: web-servers-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/web-servers-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- web-servers-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ web-servers-en.xml	23 Nov 2005 06:55:57 -0000	1.3
@@ -6,7 +6,7 @@
   <section>
     <title><command>httpd</command></title>
     <para>
-      The following changes have been made to the default <command></command>httpd
+      The following changes have been made to the default <command>httpd</command>
       configuration:
     </para>
     <itemizedlist>
@@ -18,7 +18,7 @@
       </listitem>
       <listitem>
 	<para>The <computeroutput>mod_ext_filter</computeroutput> module
-	  is now loaded by default
+	  is now loaded by default.
 	</para>
       </listitem>
     </itemizedlist>


Index: xorg-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/xorg-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- xorg-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ xorg-en.xml	23 Nov 2005 06:55:57 -0000	1.3
@@ -1,211 +1,162 @@
 <section id="sn-xwindows">
   <title>X Window System (Graphics)</title>
-  <caution>
-    <title>Information Out-of-Date</title>
-    <para>
-      The content in this section needs to be updated for &DISTRO;
-      &DISTROVER;
-    </para>
-  </caution>
-  <para>
-    This section contains information related to the X Window System
-    implementation provided with &DISTRO;.
-  </para>
-  <section id="sn-xwindows-xorg">
-    <title><filename>xorg-x11</filename></title>
-    <para>
-      Users new to the X.org X11 implementation should take note of a
-      few differences between it and the XFree86.org X11 implementation
-      which shipped in previous &RH; and &FED; operating systems. In
-      particular, the names of some files have changed:
-    </para>
-    <para>
-      X Server Binary:
-    </para>
-    <itemizedlist>
-      <listitem>
-	<para>XFree86 X11: <filename>XFree86</filename></para>
-      </listitem>
-      <listitem>
-	<para>X.org X11: <filename>Xorg</filename></para>
-      </listitem>
-    </itemizedlist>
-    <para>
-      X Server Configuration File:
-    </para>
-    <itemizedlist>
-      <listitem>
-	<para>XFree86 X11:
-	  <filename>/etc/X11/XF86Config</filename></para>
-      </listitem>
-      <listitem>
-	<para>X.org X11: <filename>/etc/X11/xorg.conf</filename></para>
-      </listitem>
-    </itemizedlist>
-    <para>
-      X Server Log File:
-    </para>
-    <itemizedlist>
-      <listitem>
-	<para>XFree86 X11:
-	  <filename>/var/log/XFree86.<replaceable>$DISPLAY</replaceable>.log</filename></para>
-      </listitem>
-      <listitem>
-	<para>X.org X11:
-	  <filename>/var/log/Xorg.<replaceable>$DISPLAY</replaceable>.log</filename></para>
-      </listitem>
-    </itemizedlist>
-    <para>
-      When configuring or troubleshooting your X server
-      configuration, be sure that you are using the correct
-      files.
-    </para>
-    <para>
-      There has been some confusion regarding font-related issues
-      under the X Window System in recent versions of &DISTRO; (and
-      versions of &RHL; before it.)  At the present time, there are two
-      font subsystems, each with different characteristics:
-    </para>
-    <itemizedlist>
-      <listitem>
-	<para>The original (15+ year old) subsystem is referred to as
-	  the <firstterm>core X font subsystem</firstterm>.  Fonts
-	  rendered by this subsystem are not anti-aliased, are handled
-	  by the X server, and have names such as:
-	  <computeroutput>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</computeroutput>
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  The newer font subsystem is known as
-	  <firstterm>fontconfig</firstterm>, and allows applications
-	  direct access to the font files.  Fontconfig is often used
-	  along with the <filename>Xft</filename> library, which allows
-	  applications to render fontconfig fonts to the screen with
-	  antialiasing. Fontconfig uses more human-friendly names such
-	  as: <computeroutput>Luxi Sans-10</computeroutput>
-	</para>
-      </listitem>
-    </itemizedlist>
-    <para>
-      Over time, fontconfig and <filename>Xft</filename> will replace
-      the core X font subsystem.  At the present time, applications
-      using the Qt 3 or GTK 2 toolkits (which would include KDE and
-      GNOME applications) use the fontconfig and Xft font subsystem;
-      almost everything else uses the core X fonts.
-    </para>
-    <para>
-      In the future, &FC; may support only fontconfig/Xft in
-      place of the XFS font server as the default local font access
-      method.
-    </para>
-    <note>
-      <title>Note</title>
+  <section>
+    <title>Docs/Beats/Xorg</title>
+    <para/>
+  </section>
+  <section>
+    <title>X Window System (Graphics)</title>
+    <para>This section contains information related to the X Window
+      System implementation provided with &FED;. 
+    </para>
+    <section id="sn-xorg-x11">
+      <title>xorg-x11</title>
+      <para>X.org X11 is an open source implementation of the X Window
+	System. It provides the basic low level functionality that full
+	fledged graphical user interfaces (GUIs) such as GNOME and KDE
+	are designed upon. </para>
+      <para>For more information about Xorg refer to <ulink
+	  url='http://xorg.freedesktop.org/wiki/'>http://xorg.freedesktop.org/wiki/</ulink>
+      </para>
+      <para>You can use
+	<guimenu>Applications</guimenu><guimenuitem>System
+	  Settings</guimenuitem><guimenuitem>Display</guimenuitem> or
+	run <command>system-config-display</command> to configure the
+	settings. The configuration file for Xorg is located in
+	<filename>/etc/X11/xorg.conf</filename>.
+      </para>
       <para>
-	An exception to the font subsystem usage outlined above is
-	OpenOffice.org, which uses its own font rendering technology.
+	Modular X.Org X11R7 RC2 was released into &FED; development
+	(<firstterm>rawhide</firstterm>) on November 16, 2005. This is
+	the first modular release of Xorg. Among several benefits,
+	modular Xorg enables users to receive updates at a faster pace,
+	while helping developers to develop and release specific
+	components in a rapid fashion.
       </para>
-    </note>
-    <para>
-      The steps to add new fonts to &DISTRO; &DISTROVER; depend on the
-      fonts subsystem this is going to use the new fonts.  For the core X
-      font subsystem:
-    </para>
-
-    <procedure>
-      <step>
-	<para>
-	  Create the <filename>/usr/share/fonts/local/</filename>
-	  directory (if it doesn't already exist):
-	</para>
-<screen>
-<command>mkdir /usr/share/fonts/local/</command>
-</screen>
-      </step>
-      <step>
-	<para>
-	  Copy the new font file into
-	  <filename>/usr/share/fonts/local/</filename>
-	</para>
-      </step>
-      <step>
-	<para>
-	  Update the font information by issuing the following commands
-	  (note that, due to formatting restrictions, the following
-	  commands may appear on more than one line; in use, each
-	  command should be entered on a single line):
-	</para>
-<screen>
-<command>ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</command>
-<command>mkfontdir /usr/share/fonts/local/</command>
-</screen>
-      </step>
-      <step>
-	<para>
-	  If you had to create
-	  <filename>/usr/share/fonts/local/</filename>, you must then
-	  add it to the X font server (<command>xfs</command>) path:
-	</para>
-<screen>
-<command>chkfontpath --add /usr/share/fonts/local/</command>
-</screen>
-      </step>
-    </procedure>
-    <para>
-      Adding new fonts to the fontconfig font subsystem is more
-      straightforward; the new font file only needs to be copied into
-      the <filename>/usr/share/fonts/</filename> directory (individual
-      users can modify their personal font configuration by copying the
-      font file into the <filename>~/.fonts/</filename> directory).
-    </para>
-    <para>
-      After the new font has been copied, use
-      <command>fc-cache</command> to update the font information cache:
-    </para>
-<screen>
-<command>fc-cache <replaceable>&lt;directory&gt;</replaceable></command>
-</screen>
-    <para>
-      (Where
-      <command><replaceable>&lt;directory&gt;</replaceable></command>
-      would be either the <filename>/usr/share/fonts/</filename> or
-      <filename>~/.fonts/</filename> directories.)
-    </para>
-    <para>
-      Individual users may also install fonts graphically, by browsing
-      <command>fonts:///</command> in
-      <application>Nautilus</application>, and dragging the new font
-      files there.
-    </para>
-    <note>
-      <title>Note</title>
       <para>
-	If the font filename ends with "<filename>.gz</filename>", it
-	has been compressed with <command>gzip</command>, and must be
-	decompressed (with the <command>gunzip</command> command) before
-	the fontconfig font subsystem can use the font.
+	More information on the current status of the Xorg
+	modularization effort in &FED; is available from <ulink
+	  url='/Xorg/Modularization'>http://fedoraproject.org/wiki/Xorg/Modularization</ulink>
       </para>
-    </note>      
-    <para>
-      Due to the transition to the new font system based on
-      fontconfig/Xft, GTK+ 1.2 applications are not affected by any
-      changes made via the <guilabel>Font Preferences</guilabel> dialog.
-      For these applications, a font can be configured by adding the
-      following lines to the file <filename>~/.gtkrc.mine</filename>:
-    </para>
-<screen>    
-<computeroutput>style "user-font" {
-fontset = "<replaceable>&lt;font-specification&gt;</replaceable>"
-}
-widget_class "*" style "user-font"</computeroutput>
-</screen>
-    <para>
-      (Where
-      <command><replaceable>&lt;font-specification&gt;</replaceable></command> 
-      represents a font specification in the style used by traditional X
-      applications, such as
-      "<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>".)
-    </para>
+    </section>
+    <section id="sn-xorg-x11r7-dev">
+      <title>Xorg X11R7 Developer Notes</title>
+      <para>X11R7 RC2 is included in this release and there are a number
+	of things that software developers, and packagers in &FED;
+	repositories, need to be aware of in order to ensure that their
+	software or software packages properly compile and work with
+	X11R7. Some are simple changes, while others may be more
+	involved. Here is a summary of issues that may arise and where
+	possible, suggestions on how to fix them.
+      </para>
+      <section>
+        <title>The <filename>/usr/X11R6</filename> directory hierarchy</title>
+        <para>
+	  X11R7 installs into <filename>/usr</filename> directly now,
+	  and no longer uses the <filename>/usr/X11R6</filename>
+	  hierarchy. Applications that rely on files being present at
+	  fixed paths under <filename>/usr/X11R6</filename> at compile
+	  time or at run time, must be updated to use the system
+	  <envar>PATH</envar>, or some other mechanism, to dynamically
+	  determine where the files reside, or alternatively to hard
+	  code the new locations, possibly with fallbacks.
+	</para>
+      </section>
+      <section>
+        <title><command>Imake</command></title>
+        <para><command>Imake</command> is no longer used to build the X
+	  Window System, and as such is now officially deprecated.
+	  <command>Imake</command>, <command>xmkmf</command> and other
+	  utilities previously supplied by the X Window System, are
+	  still supplied in X11R7, however X.Org highly recommends that
+	  people migrate from Imake to using GNU autotools and
+	  <filename>pkg-config</filename>. Support for
+	  <command>imake</command> may vanish in a future X Window
+	  System release, so developers are strongly encouraged to
+	  transition away from it, and not to use it for any new
+	  software projects. 
+	</para>
+      </section>
+      <section>
+        <title>The systemwide app-defaults directory</title>
+        <para>The system app-defaults directory for X resources, is now
+	  <filename>%{_datadir}/X11/app-defaults</filename>, which
+	  expands to <filename>/usr/share/X11/app-defaults</filename> on
+	  &FC; &FCVER; and for future &RHEL; systems. </para>
+      </section>
+      <section id="sn-xorg-xft-config">
+        <title><filename>xft-config</filename> can't be found</title>
+        <para>Modular X now uses GNU autotools, and
+	  <command>pkg-config</command> for its buildsystem
+	  configuration, etc. <command>xft-config</command> has been
+	  deprecated for two to three years, and
+	  <command>pkgconfig</command> <filename>*.pc</filename> files
+	  have been provided for most of this time. Applications that
+	  previously used <command>xft-config</command> to obtain the
+	  <option>Cflags</option> or libs options for building with,
+	  must now be updated to use <command>pkg-config</command>.
+	</para>
+      </section>
+    </section>
+    <section id="sn-xorg-devel-overview">
+      <title>Xorg X11R7 Developer Overview</title>
+      <para>Here is a short list of some of the more developer/package
+	visible changes that are present in X11R7: </para>
+      <itemizedlist>
+        <listitem>
+          <para>The entire buildsystem has changed from
+	    <command>Imake</command> to the GNU autotools collection.
+	  </para>
+        </listitem>
+        <listitem>
+          <para>All of the libraries now install
+	    <command>pkgconfig</command> <filename>*.pc</filename>
+	    files, which should now always be used by software that
+	    depends on these libraries, instead of hard coding paths to
+	    them in <filename>/usr/X11R6/lib</filename> or elsewhere.
+	  </para>
+        </listitem>
+        <listitem>
+          <para>Everything is now installed directly into
+	    <filename>/usr</filename> instead of
+	    <filename>/usr/X11R6</filename>. All software that hard
+	    codes paths to anything in <filename>/usr/X11R6</filename>,
+	    must now be changed preferably to dynamically detect the
+	    proper location of the object, or to hard code the new paths
+	    that X11R7 uses by default. It is strongly advised to use
+	    autodetection methods rather than to hard code paths.
+	  </para>
+        </listitem>
+        <listitem>
+          <para>Every library has its own, private source package now,
+	    which creates a runtime binary subpackage, and a -devel
+	    subpackage.
+	  </para>
+	  <para>
+	    Any software package that previously picked up the
+	    development headers, etc. for X libraries by using
+	    <computeroutput>BuildRequires:
+	      (XFree86-devel|xorg-x11-devel)</computeroutput>, must now
+	    individually list each library dependency individually. When
+	    doing this, it is greatly preferred and strongly recommended
+	    to use <firstterm>virtual</firstterm> build dependencies instead of hard coding
+	    the library package names of the Xorg implementation.
+	  </para>
+	  <para>
+	    This means you should use: <computeroutput>BuildRequires:
+	      libXft-devel</computeroutput> instead of using:
+	    <filename>BuildRequires: xorg-x11-Xft-devel</filename>. If
+	    your software truly does depend on the X.Org X11
+	    implementation of a specific library, and there is no other
+	    clean/safe way to state the dependency, then use the
+	    <filename>xorg-x11--devel</filename> form. By sticking to
+	    the virtual provides/requires mechanism, this makes it
+	    painless if and when the libraries move to another location
+	    in the future.
+	  </para>
+        </listitem>
+      </itemizedlist>
+    </section>
   </section>
 </section>
 



From fedora-docs-commits at redhat.com  Wed Nov 23 11:26:14 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 23 Nov 2005 06:26:14 -0500
Subject: docs-common/images watermark.png,1.1,1.2 watermark.svg,1.1,1.2
Message-ID: <200511231126.jANBQECE020093@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/images
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20060

Modified Files:
	watermark.png watermark.svg 
Log Message:
Minor correction: "NOT FOR REFERENCE" instead of "Not for reference".  It
looks more imposing that way...



Index: watermark.svg
===================================================================
RCS file: /cvs/docs/docs-common/images/watermark.svg,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- watermark.svg	23 Nov 2005 06:30:23 -0000	1.1
+++ watermark.svg	23 Nov 2005 11:26:07 -0000	1.2
@@ -10,7 +10,7 @@
   <g fill="&bgColor;" font-family="Helvetica" font-size="1in" stroke="&bgColor;" stroke-width="10" text-anchor="start" transform="translate( 1, 1 )">
     <g transform="translate( 512, 384 ) rotate( -45 )">
       <text font-stretch="wider" text-anchor="middle" x="0" y="0">DRAFT</text>
-      <text fill="&fgColor;" font-size="0.6in" font-stretch="wider" stroke="rgb( 230, 200, 200 )" stroke-width="1.5" text-anchor="middle" x="0" y="1in">Not for reference.</text>
+      <text fill="&fgColor;" font-size="0.6in" font-stretch="wider" font-variant="small-caps" stroke="rgb( 230, 200, 200 )" stroke-width="1.5" text-anchor="middle" x="0" y="1in">NOT FOR REFERENCE</text>
     </g>
   </g>
 </svg>



From fedora-docs-commits at redhat.com  Wed Nov 23 23:58:32 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Wed, 23 Nov 2005 18:58:32 -0500
Subject: release-notes desktop-en.xml, 1.3, 1.4 development-tools-en.xml, 1.3,
	1.4 java-package-en.xml, 1.2, 1.3 kernel-en.xml, 1.3,
	1.4 package-movement-en.xml, 1.4, 1.5 package-notes-en.xml,
	1.5, 1.6 security-en.xml, 1.3, 1.4 splash-en.xml, 1.4,
	1.5 xorg-en.xml, 1.3, 1.4
Message-ID: <200511232358.jANNwWdO011200@cvs-int.fedora.redhat.com>

Author: elliss

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11155

Modified Files:
	desktop-en.xml development-tools-en.xml java-package-en.xml 
	kernel-en.xml package-movement-en.xml package-notes-en.xml 
	security-en.xml splash-en.xml xorg-en.xml 
Log Message:
- Replaced &FCVER; entities with &LOCALVER; to provide correct version numbers in text and headers
- Removed "Update for Fedora Core test1" notices, since it's now too late...
- Commented out Package Changes section, which is marked as lasted updated in September. See bug #173777 for argument that this should be dropped.




Index: desktop-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/desktop-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- desktop-en.xml	23 Nov 2005 05:38:24 -0000	1.3
+++ desktop-en.xml	23 Nov 2005 23:58:24 -0000	1.4
@@ -3,7 +3,7 @@
   <itemizedlist>
     <title>Notes</title>
     <listitem>
-      <para>GNOME 2.12 and KDE 3.4.2 are included in &FC; &FCVER;.
+      <para>GNOME 2.12 and KDE 3.4.2 are included in &FC; &LOCALVER;.
       </para>
     </listitem>
     <listitem>


Index: development-tools-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/development-tools-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- development-tools-en.xml	23 Nov 2005 05:38:24 -0000	1.3
+++ development-tools-en.xml	23 Nov 2005 23:58:24 -0000	1.4
@@ -16,7 +16,7 @@
   <section id="sn-java-development">
     <title>Java-like Environment</title>
     <para>A Java-like free and open source environment is available
-      within the &FC; &FCVER; release.
+      within the &FC; &LOCALVER; release.
     </para>
     <para>
       It has three components: GNU Java runtime


Index: java-package-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/java-package-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- java-package-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ java-package-en.xml	23 Nov 2005 23:58:24 -0000	1.3
@@ -1,12 +1,5 @@
 <section id="sn-java-packages">
   <title>Java Package Recommendations</title>
-  <caution>
-    <title>Information Out-of-Date</title>
-    <para>
-      The content in this section needs to be updated for &DISTRO;
-      &DISTROVER;
-    </para>
-  </caution>
   <para>
     &FC; &LOCALVER; users are advised not to use the Java RPM provided
     by Sun.  It contains <computeroutput>Provides</computeroutput> that


Index: kernel-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/kernel-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- kernel-en.xml	23 Nov 2005 05:38:24 -0000	1.3
+++ kernel-en.xml	23 Nov 2005 23:58:24 -0000	1.4
@@ -18,7 +18,7 @@
     <para>
       This distribution is based on the 2.6 series of the Linux kernel.
       &FC; may include patches for improvements, bug fixes, or
-      additional features. For this reason, the &FCl kernel may not be
+      additional features. For this reason, the &FC; kernel may not be
       line-for-line equivalent to the <firstterm>vanilla
 	kernel</firstterm> from the <ulink
 	url='http://www.kernel.org/'>http://www.kernel.org/</ulink>
@@ -63,7 +63,7 @@
       <para>
 	The default kernels in x86_64 architecture provide the SMP
 	capability. There is no seperate SMP kernel available for this
-	architecture in &FC; &FCVER;.
+	architecture in &FC; &LOCALVER;.
       </para>
     </note>
   </section>
@@ -84,7 +84,7 @@
   <section id="sn-kernel-dev">
     <title>Preparing for Kernel Development</title>
     <para>
-      &FC; &FCVER; does not include the <filename>kernel-source</filename>
+      &FC; &LOCALVER; does not include the <filename>kernel-source</filename>
       package provided by older versions. Instead, configured sources
       are available as described in <xref linkend="sn-kernel-flavors"/>.
       Users that require access to &FC; original kernel sources
@@ -248,7 +248,7 @@
   <section id="kernel-user-space-depencies">
     <title>User Space Dependencies on the Kernel</title>
     <para>
-      &PROD; &PRODVER; has support for clustered storage through the Red
+      &FC; &LOCALVER; has support for clustered storage through the Red
       Hat GFS file system. This requires a special kernel that works in
       conjunction with some user-space utilities, such as management
       daemons. Consequently, to remove such a kernel, perhaps after an


Index: package-movement-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-movement-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- package-movement-en.xml	25 Oct 2005 19:40:56 -0000	1.4
+++ package-movement-en.xml	23 Nov 2005 23:58:24 -0000	1.5
@@ -2,8 +2,8 @@
   <title>Packages Movement</title>
   <!-- 
   FIXME
-  Needs updating of entire contents for FC4.
-  -->
+  Needs updating of entire contents for FC5.
+
   <para>
     This command was used to generate the list of package changes.  The
     backslash <computeroutput>\</computeroutput> is used to artificially
@@ -932,6 +932,7 @@
     <para>[111033] ncpfs-2.2.4-8 -> [115462] ncpfs-2.2.4-9 </para>
     <para>[106079] prelink-0.3.4-3 -> [117615] prelink-0.3.6-1 </para>
     <para>[110767] netpbm-10.27-3 -> [116518] netpbm-10.29-1 </para>
+-->
     <section id="sn-packages-added">
       <title>Packages Added</title>
       <para>
@@ -1060,8 +1061,6 @@
     </para>
 -->
   </section>
-
-</section>
 <!--
 Local variables:
 mode: xml


Index: package-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- package-notes-en.xml	23 Nov 2005 06:55:57 -0000	1.5
+++ package-notes-en.xml	23 Nov 2005 23:58:24 -0000	1.6
@@ -37,13 +37,6 @@
     easier access, they are generally organized using the same groups
     used in Anaconda.
   </para>
-  <caution>
-    <title>Information Out-of-Date</title>
-    <para>
-      The content in this section needs to be updated for &DISTRO;
-      &DISTROVER;
-    </para>
-  </caution>
   <section id="sn-basic-components">
     <title>Basic Components</title>
     <para>


Index: security-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/security-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- security-en.xml	23 Nov 2005 06:55:57 -0000	1.3
+++ security-en.xml	23 Nov 2005 23:58:24 -0000	1.4
@@ -16,10 +16,8 @@
     <para>
       This section highlights various security items from &FC;.
     </para>
-    <variablelist>
-      <varlistentry>
-	<term>Buffer Overflow detection and variable reordering</term>
-	<listitem>
+      <section>
+	<title>Buffer Overflow detection and variable reordering</title>
 	  <para>For this release, all of the software in the &FC; and
 	    &FEX; software repositories is compiled using a security
 	    feature called <firstterm>fstack-protecter</firstterm>.
@@ -32,14 +30,13 @@
 	    application is started and makes it impossible to guess
 	    remotely. This is a security feature that has been
 	    backported from GCC 4.1 to the version of the GCC compiler
-	    used in &FC; &FCVER;. 
+	    used in &FC; &LOCALVER;. 
 	  </para>
 	  <para>
 	    This is in addition to using <envar>FORTIFY_SOURCE</envar>
 	    from &FC; 4 onwards.
 	  </para>
-	</listitem>
-      </varlistentry>    
+      </section>
     
     <section>
     <para>
@@ -53,21 +50,20 @@
       <filename>/etc/pki/CA/</filename>.
     </para>        
     <para>
-      Dovecot: A dovecot-openssl.cnf file is automatically installed in
-      <filename>/etc/pki/dovecot/</filename>.
+      Dovecot: A <filename>dovecot-openssl.cnf</filename> file is automatically installed in <filename>/etc/pki/dovecot/</filename>.
     </para>
   </section>
   <section id="sn-security-selinux-changes">
     <title>SELinux Changes</title>
     <para>
-      MCS SELinux is in somewhere. Major highlight.  For more
-      information, read this informative article:
+      Mult-Category Security (MCS) SELinux is included in &FC; &LOCALVER;. For more information, read this informative article:
     </para>
     <para>
       <ulink
 	url="http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/msg00001.html">http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/msg00001.html</ulink>
     </para>
   </section>
+  </section>
 </section>
 <!--
 Local variables:


Index: splash-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- splash-en.xml	23 Nov 2005 06:55:57 -0000	1.4
+++ splash-en.xml	23 Nov 2005 23:58:24 -0000	1.5
@@ -84,10 +84,10 @@
     </listitem>
   </itemizedlist>
   <section id="sn-new-in-fc">
-    <title>What's New In &FC; &FCVER;</title>
+    <title>What's New In &FC; &LOCALVER;</title>
     <itemizedlist>
       <listitem>
-        <para>Xen Virtualisation software and yum package manager are
+        <para>Xen virtualisation software and yum package manager are
 	  now well integrated within the &FED; installer. The installer
 	  interface is more streamlined.  Remote logging and improved
 	  support for tracebacks is included.


Index: xorg-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/xorg-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- xorg-en.xml	23 Nov 2005 06:55:57 -0000	1.3
+++ xorg-en.xml	23 Nov 2005 23:58:24 -0000	1.4
@@ -82,7 +82,7 @@
         <para>The system app-defaults directory for X resources, is now
 	  <filename>%{_datadir}/X11/app-defaults</filename>, which
 	  expands to <filename>/usr/share/X11/app-defaults</filename> on
-	  &FC; &FCVER; and for future &RHEL; systems. </para>
+	  &FC; &LOCALVER; and for future &RHEL; systems. </para>
       </section>
       <section id="sn-xorg-xft-config">
         <title><filename>xft-config</filename> can't be found</title>



From fedora-docs-commits at redhat.com  Thu Nov 24 01:09:32 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Wed, 23 Nov 2005 20:09:32 -0500
Subject: release-notes hardware-reqs-en.xml, 1.2, 1.3 install-notes-en.xml,
	1.4, 1.5 splash-en.xml, 1.5, 1.6 xorg-en.xml, 1.4, 1.5
Message-ID: <200511240109.jAO19WYQ014426@cvs-int.fedora.redhat.com>

Author: elliss

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14398

Modified Files:
	hardware-reqs-en.xml install-notes-en.xml splash-en.xml 
	xorg-en.xml 
Log Message:
- Updated PPC section in Hardware Requirements
- Removed additional Hardware Requirements section in PPC Installation Notes
- Set mailing list references as links in Welcome section




Index: hardware-reqs-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/hardware-reqs-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- hardware-reqs-en.xml	25 Oct 2005 09:07:12 -0000	1.2
+++ hardware-reqs-en.xml	24 Nov 2005 01:09:11 -0000	1.3
@@ -230,11 +230,8 @@
       <listitem>
 	<para>
 	  <!--<remark os="test">(ppc)</remark> --> &FC; &LOCALVER;
-	  supports only the <quote>New World</quote> generation of Apple
-	  Power Macintosh, shipped circa 1999 onwards. It also supports
-	  the 64-bit G5 processor and, POWER processors in IBM eServer
-	  pSeries. Currently 32-bit IBM RS/6000 machines are not
-	  supported.
+	  supports the <quote>New World</quote> generation of Apple
+	  Power Macintosh (shipped circa 1999 onwards), Genesi Pegasos II, and IBM 32-bit RS/6000 machines. It also supports the 64-bit G5 processor, and POWER processors in the IBM eServer pSeries.
 	</para>
       </listitem>
       <listitem>


Index: install-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- install-notes-en.xml	23 Nov 2005 05:38:24 -0000	1.4
+++ install-notes-en.xml	24 Nov 2005 01:09:11 -0000	1.5
@@ -32,35 +32,6 @@
   </note>
   <section id="sn-install-notes-ppc">
     <title>PPC Installation Notes</title>
-    <section id="sn-ppc-hardware-reqs">
-      <title>PPC Hardware Requirements</title>
-      <para>
-	This section lists the minimum PowerPC (PPC) hardware needed
-	to install &DISTRO; &DISTROVER;.
-      </para>
-      <itemizedlist>
-	<listitem>
-	  <para>Minimum: PowerPC G3 / POWER4 </para>
-	</listitem>
-	<listitem>
-	  <para>&DISTRO; &DISTROVER; supports only the ???New World???
-	    generation of <trademark class="trade">Apple</trademark>
-	    Power Macintosh, shipped circa 1999 onwards.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>&DISTRO; &DISTROVER; also supports IBM eServer pSeries, IBM
-	    RS/6000, and Genesi Pegasos II machines.</para>
-	</listitem>
-	<listitem>
-	  <para>Recommended for text-mode: 233 MHz G3 or better, 64MiB
-	    RAM.</para>
-	</listitem>
-	<listitem>
-	  <para>Recommended for graphical: 400 MHz G3 or better, 128MiB
-	    RAM.</para>
-	</listitem>
-      </itemizedlist>
       <para>
 	The DVD or first CD of the installation set of &FC; is set to be
 	bootable on supported hardware. In addition, bootable CD images
@@ -141,7 +112,6 @@
 	</varlistentry>
       </variablelist>
     </section>
-  </section>
   <section id="sn-anaconda-notes">
     <title>Anaconda Notes</title>
     


Index: splash-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- splash-en.xml	23 Nov 2005 23:58:24 -0000	1.5
+++ splash-en.xml	24 Nov 2005 01:09:11 -0000	1.6
@@ -15,7 +15,7 @@
       users.
     </para>
     <para>
-      Subscribe to the fedora-test and fedora-devel mailings lists to
+      Subscribe to the <ulink url="https://www.redhat.com/mailman/listinfo/fedora-test-list/">fedora-test</ulink> and <ulink url="https://www.redhat.com/mailman/listinfo/fedora-devel-list">fedora-devel</ulink> mailing lists to
       keep track of important changes in the current development
       versions and provide feedback to the developers. &FP; requests you
       to file bug reports and enhancements to provide a improved final
@@ -66,6 +66,11 @@
     </listitem>
     <listitem>
       <para>
+	<ulink url="http://fedoraproject.org/wiki/FAQ/">Fedora FAQ</ulink>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
 	Help and Support (<ulink
 	  url="http://fedora.redhat.com/participate/communicate/">http://fedora.redhat.com/participate/communicate/</ulink>) 
       </para>


Index: xorg-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/xorg-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- xorg-en.xml	23 Nov 2005 23:58:24 -0000	1.4
+++ xorg-en.xml	24 Nov 2005 01:09:11 -0000	1.5
@@ -1,10 +1,6 @@
 <section id="sn-xwindows">
   <title>X Window System (Graphics)</title>
   <section>
-    <title>Docs/Beats/Xorg</title>
-    <para/>
-  </section>
-  <section>
     <title>X Window System (Graphics)</title>
     <para>This section contains information related to the X Window
       System implementation provided with &FED;. 



From fedora-docs-commits at redhat.com  Thu Nov 24 22:31:28 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Thu, 24 Nov 2005 17:31:28 -0500
Subject: release-notes RELEASE-NOTES-en.xml, 1.4, 1.5 install-notes-en.xml,
	1.5, 1.6 overview-en.xml, 1.2, 1.3 project-overview-en.xml, 1.2, 1.3
Message-ID: <200511242231.jAOMVSKw020782@cvs-int.fedora.redhat.com>

Author: elliss

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20755

Modified Files:
	RELEASE-NOTES-en.xml install-notes-en.xml overview-en.xml 
	project-overview-en.xml 
Log Message:
- Removed another "Fix by test1" message
- Fixed a couple of typos




Index: RELEASE-NOTES-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- RELEASE-NOTES-en.xml	25 Oct 2005 09:07:11 -0000	1.4
+++ RELEASE-NOTES-en.xml	24 Nov 2005 22:31:21 -0000	1.5
@@ -40,7 +40,7 @@
 
  <!-- *************** Local entities *************** -->
 
- <!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-10-25-T04:20-0700)"> <!-- version of manual and date -->
+ <!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-11-24-T22:25+0000)"> <!-- version of manual and date -->
  <!ENTITY LOCALVER "5 test1">  <!-- Set value to your choice, when guide version is out -->
  <!-- of sync with FC release, use instead of FEDVER or FEDTESTVER  -->
  <!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->


Index: install-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- install-notes-en.xml	24 Nov 2005 01:09:11 -0000	1.5
+++ install-notes-en.xml	24 Nov 2005 22:31:21 -0000	1.6
@@ -15,7 +15,7 @@
       <computeroutput>File size limit exceeded</computeroutput> error.
     </para>
     <para>
-      The <command>wget</command> version 1.9.1-16 and lter,
+      The <command>wget</command> version 1.9.1-16 and later,
       <command>curl</command> and <command>ncftpget</command> file
       downloading tools do not have this limitation, and can
       successfully download files larger than 2GiB.


Index: overview-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/overview-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- overview-en.xml	25 Oct 2005 09:07:12 -0000	1.2
+++ overview-en.xml	24 Nov 2005 22:31:21 -0000	1.3
@@ -1,12 +1,5 @@
 <section id="sn-overview">
   <title>Overview of This Release</title>
-  <caution>
-    <title>Information Out-of-Date</title>
-    <para>
-      The content in this section needs to be updated for &DISTRO;
-      &DISTROVER;
-    </para>
-  </caution>
 <!--
   <para>
     The following list includes brief summaries of some of the more


Index: project-overview-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/project-overview-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- project-overview-en.xml	23 Nov 2005 05:38:24 -0000	1.2
+++ project-overview-en.xml	24 Nov 2005 22:31:21 -0000	1.3
@@ -49,7 +49,7 @@
       </listitem>
     <listitem>
       <para>
-	fedora-ambassadors-list at redehat.com &mdash; For community
+	fedora-ambassadors-list at redhat.com &mdash; For community
 	members who represent the &PROJ; in public.
       </para>
     </listitem>



From fedora-docs-commits at redhat.com  Thu Nov 24 23:12:32 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Thu, 24 Nov 2005 18:12:32 -0500
Subject: release-notes RELEASE-NOTES-en.xml, 1.5, 1.6 package-notes-en.xml,
	1.6, 1.7
Message-ID: <200511242312.jAONCWVV022608@cvs-int.fedora.redhat.com>

Author: elliss

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22587

Modified Files:
	RELEASE-NOTES-en.xml package-notes-en.xml 
Log Message:
- Removed duplicate entity declaration that caused "Games and Entertainment" ection to appear twice



Index: RELEASE-NOTES-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- RELEASE-NOTES-en.xml	24 Nov 2005 22:31:21 -0000	1.5
+++ RELEASE-NOTES-en.xml	24 Nov 2005 23:12:24 -0000	1.6
@@ -40,7 +40,7 @@
 
  <!-- *************** Local entities *************** -->
 
- <!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-11-24-T22:25+0000)"> <!-- version of manual and date -->
+ <!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-11-24-T23:10+0000)"> <!-- version of manual and date -->
  <!ENTITY LOCALVER "5 test1">  <!-- Set value to your choice, when guide version is out -->
  <!-- of sync with FC release, use instead of FEDVER or FEDTESTVER  -->
  <!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->


Index: package-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-en.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- package-notes-en.xml	23 Nov 2005 23:58:24 -0000	1.6
+++ package-notes-en.xml	24 Nov 2005 23:12:24 -0000	1.7
@@ -246,7 +246,6 @@
 <!--  no content for this release
   &DATABASE-SERVERS; -->
   &MULTIMEDIA;
-  &ENTERTAINMENT;
   &WEB-SERVERS;
   &SAMBA;
   &XORG;



From fedora-docs-commits at redhat.com  Fri Nov 25 19:22:55 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Fri, 25 Nov 2005 14:22:55 -0500
Subject: release-notes security-en.xml,1.4,1.5
Message-ID: <200511251922.jAPJMtOC027684@cvs-int.fedora.redhat.com>

Author: kwade

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27667

Modified Files:
	security-en.xml 
Log Message:
Too many nested sections, this is a place where a variablelist works really nicely.


Index: security-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/security-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- security-en.xml	23 Nov 2005 23:58:24 -0000	1.4
+++ security-en.xml	25 Nov 2005 19:22:48 -0000	1.5
@@ -16,8 +16,10 @@
     <para>
       This section highlights various security items from &FC;.
     </para>
-      <section>
-	<title>Buffer Overflow detection and variable reordering</title>
+    <variablelist>
+      <varlistentry>
+	<term>Buffer Overflow detection and variable reordering</term>
+	<listitem>
 	  <para>For this release, all of the software in the &FC; and
 	    &FEX; software repositories is compiled using a security
 	    feature called <firstterm>fstack-protecter</firstterm>.
@@ -36,34 +38,52 @@
 	    This is in addition to using <envar>FORTIFY_SOURCE</envar>
 	    from &FC; 4 onwards.
 	  </para>
-      </section>
+	</listitem>
+      </varlistentry>
     
-    <section>
-    <para>
-      Digital certificates are now centralised in directories
-      under <filename>/etc/pki/</filename>. Users performing an upgrade must
-      relocate their digital certificates.
-    </para>
-    <para>
-      OpenSSL: the <filename>/usr/share/ssl/</filename> contents have
-      moved to <filename>/etc/pki/tls/</filename> and
-      <filename>/etc/pki/CA/</filename>.
-    </para>        
-    <para>
-      Dovecot: A <filename>dovecot-openssl.cnf</filename> file is automatically installed in <filename>/etc/pki/dovecot/</filename>.
-    </para>
+      <varlistentry>
+	<term>Digital certificates</term>
+	<listitem>
+	  <para>
+	    Digital certificates are now centralised in directories
+	    under <filename>/etc/pki/</filename>. Users performing an
+	    upgrade must relocate their digital certificates.
+	  </para>
+	</listitem>
+      </varlistentry>
+      <varlistentry>
+	<term>OpenSSL</term>
+	<listitem>
+	  <para>
+	    For OpenSSL, the <filename>/usr/share/ssl/</filename>
+	    contents have moved to <filename>/etc/pki/tls/</filename>
+	    and <filename>/etc/pki/CA/</filename>.
+	  </para>        
+	</listitem>
+      </varlistentry>
+      <varlistentry>
+	<term>Dovecot</term>
+	<listitem>
+	  <para>
+	    The <filename>dovecot-openssl.cnf</filename> file is
+	    automatically installed in
+	    <filename>/etc/pki/dovecot/</filename>.
+	  </para>
+	</listitem>  
+      </varlistentry>
+    </variablelist>
   </section>
   <section id="sn-security-selinux-changes">
     <title>SELinux Changes</title>
     <para>
-      Mult-Category Security (MCS) SELinux is included in &FC; &LOCALVER;. For more information, read this informative article:
+      Mult-Category Security (MCS) SELinux is included in &FC;
+      &LOCALVER;. For more information, read this informative article:
     </para>
     <para>
       <ulink
 	url="http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/msg00001.html">http://post-office.corp.redhat.com/archives/rhselinux-project/2005-June/msg00001.html</ulink>
     </para>
   </section>
-  </section>
 </section>
 <!--
 Local variables:



From fedora-docs-commits at redhat.com  Fri Nov 25 19:25:26 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Fri, 25 Nov 2005 14:25:26 -0500
Subject: release-notes RELEASE-NOTES-en.xml,1.6,1.7
Message-ID: <200511251925.jAPJPQlH027718@cvs-int.fedora.redhat.com>

Author: kwade

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27697

Modified Files:
	RELEASE-NOTES-en.xml 
Log Message:
Making sure all my local changes are in the repo before rebuilding the website.


Index: RELEASE-NOTES-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- RELEASE-NOTES-en.xml	24 Nov 2005 23:12:24 -0000	1.6
+++ RELEASE-NOTES-en.xml	25 Nov 2005 19:25:18 -0000	1.7
@@ -55,7 +55,7 @@
 
 <article id="index" lang="en" arch="x86;x86_64;ppc" os="test;final">
   <articleinfo>
-    <title>&DISTRO; &DISTROVER; Release Notes</title>
+    <title>&DISTRO; &DISTROVER; Release Notes (latest)</title>
     <copyright>
       <year>2005</year>
       <holder>&FORMAL-RHI;</holder>



From fedora-docs-commits at redhat.com  Fri Nov 25 20:53:00 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 25 Nov 2005 15:53:00 -0500
Subject: docs-common/packaging bookinfo.xsl, NONE, 1.1 desktop.xsl, NONE,
	1.1 omf.xsl, NONE, 1.1 rpm-info.dtd, NONE, 1.1 spec.xsl, NONE, 1.1
Message-ID: <200511252053.jAPKr0oe029679@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29637/docs-common/packaging

Added Files:
	bookinfo.xsl desktop.xsl omf.xsl rpm-info.dtd spec.xsl 
Log Message:
Candidate solution to keeping all the various RPM packaging files
(the RPM spec file, the OMF file, the ".desktop" and the package's
<bookinfo> (or <articleinfo>) consistent by using a DTD-controlled metafile
from which everything else is derived.



--- NEW FILE bookinfo.xsl ---
<!-- Transform rpm-info.xml into either "bookinfo" or "articleinfo" -->
<xsl:stylesheet version="1.0" xml:space="preserve" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output encoding="UTF-8" indent="yes" method="xml" omit-xml-declaration="yes" standalone="no" version="1.0"/>

    <xsl:param name="lang" select="'en'"/>
    <xsl:param name="doctype" select="'bookinfo'"/>

    <xsl:template match="/">
        <xsl:element name="{$doctype}">
            <title>
                <xsl:call-template name="get-title"/>
            </title>
            <copyright>
                <year>
                    <xsl:value-of select="/rpm-info/copyright/year"/>
                </year>
                <xsl:for-each select="/rpm-info/copyright/holder">
                    <holder>
                        <xsl:value-of select="node()"/>
                    </holder>
                </xsl:for-each>
            </copyright>
            <authorgroup>
                <xsl:for-each select="/rpm-info/author">
                    <author>
                        <xsl:call-template name="human"/>
                    </author>
                </xsl:for-each>
                <xsl:for-each select="/rpm-info/translator">
                    <othercredit>
                        <xsl:call-template name="human"/>
                        <personalblurb>Translator</personalblurb>
                    </othercredit>
                </xsl:for-each>
                <xsl:for-each select="/rpm-info/editor">
                    <editor>
                        <xsl:call-template name="human"/>
                    </editor>
                </xsl:for-each>
            </authorgroup>
            <xsl:text disable-output-escaping="yes">&amp;LEGALNOTICE;</xsl:text>
            <revhistory>
                <xsl:for-each select="/rpm-info/changelog/revision">
                    <revision>
                        <revnumber><xsl:value-of select="@version"/></revnumber>
                        <date><xsl:value-of select="@date"/></date>
                        <authorinitials><xsl:value-of select="author/@initials"/></authorinitials>
                        <revdescription>
                            <para>
                                <xsl:value-of select="details"/>
                            </para>
                        </revdescription>
                    </revision>
                </xsl:for-each>
            </revhistory>
        </xsl:element>
    </xsl:template>

    <xsl:template name="get-title">
        <xsl:for-each select="/rpm-info/titles/translation">
            <xsl:choose>
                <xsl:when test="@lang = $lang">
                    <xsl:value-of select="title"/>
                </xsl:when>
            </xsl:choose>
        </xsl:for-each>
    </xsl:template>

    <xsl:template name="human">
        <surname><xsl:value-of select="@surname"/></surname>
        <firstname><xsl:value-of select="@firstname"/></firstname>
    </xsl:template>
</xsl:stylesheet>


--- NEW FILE desktop.xsl ---
<!-- Transform rpm-info.xml into a .desktop File -->
<xsl:stylesheet version="1.0" xml:space="preserve" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <xsl:output encoding="UTF-8" indent="no" method="text" omit-xml-declaration="no" standalone="no" version="1.0"/>

<!-- Note: do not indent this file!  Any whitespace here
     will be reproduced in the output -->

  <xsl:param name="lang" select="'en'" />
  <xsl:param name="docbase" select="'example-tutorial'" />
  <xsl:param name="release"	select="1"/>

<xsl:template match="/">
[Desktop Entry]
Encoding=UTF-8
Categories=X-Fedora-Documentation
GenericName=<xsl:value-of select="/rpm-info/titles/translation[@lang='en']/title"/>
Name=<xsl:value-of select="/rpm-info/titles/translation[@lang='en']/title"/>
Exec=gnome-help file://usr/share/doc/fedora-doc-<xsl:value-of select="$docbase"/>/en/<xsl:value-of select="$docbase"/>-en.xml
<xsl:for-each select="/rpm-info/titles/translation">
Name[<xsl:value-of select="@lang"/>]=<xsl:value-of select="title"/>
Comment[<xsl:value-of select="@lang"/>]=<xsl:value-of select="desc"/>
Exec[<xsl:value-of select="@lang"/>]=gnome-help file://usr/share/doc/fedora-doc-<xsl:value-of select="$docbase"/>/<xsl:value-of select="@lang"/>/<xsl:value-of select="$docbase"/>-<xsl:value-of select="@lang"/>.xml
</xsl:for-each>

</xsl:template>

  <xsl:template name="get-title">
    <xsl:for-each select="/rpm-info/titles/translation">
      <xsl:choose>
	<xsl:when test="@lang = $lang">
	  <xsl:value-of select="title"/>
	</xsl:when>
      </xsl:choose>
    </xsl:for-each>
  </xsl:template>

</xsl:stylesheet>


--- NEW FILE omf.xsl ---
<!-- Transform rpm-info.xml into an OMF file -->
<xsl:stylesheet version="1.0" xml:space="preserve" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <xsl:output doctype-public="-//OMF//DTD Scrollkeeper OMF Variant V1.0//EN" doctype-system="http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd" encoding="UTF-8" indent="yes" method="xml" omit-xml-declaration="no" standalone="no" version="1.0"/>

<!-- Note: do not indent this file!  Any whitespace here
     will be reproduced in the output -->

  <xsl:param name="lang" select="'en'" />
  <xsl:param name="docbase" select="'example-tutorial'" />

  <xsl:template match="/">
    <omf>
      <resource>
        <creator>
          fedora-docs-list at redhat.com (Fedora Documentation Project)
        </creator>
        <maintainer>
          fedora-docs-list at redhat.com (Fedora Documentation Project)
        </maintainer>
        <title>
          <xsl:call-template name="get-title"/>
        </title>
        <date>
          <xsl:value-of select="/rpm-info/changelog/revision[1]/@date"/>
        </date>
        <version
          identifier="{/rpm-info/changelog/revision[1]/@version}"
          date="{/rpm-info/changelog/revision[1]/@date}"
          description="{$docbase}-{/rpm-info/changelog/revision[1]/@version} ({/rpm-info/changelog/revision[1]/@date})"
        />
        <subject category="General|Linux|Distributions|Other"/>
        <description>
          <xsl:call-template name="get-title"/>
        </description>
        <type>
          <xsl:call-template name="get-title"/>
        </type>
        <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.2//EN"/>
        <identifier url="file:/usr/share/fedora/doc/fedora-doc-{$docbase}/{$lang}/{$docbase}-{$lang}.xml" />
        <language code="{$lang}"/>
        <relation seriesid="7a5d3ea2-2a1e-11da-86a3-8ea47a4bb227"/>
        <rights type="GNU FDL" license.version="1.1" />
      </resource>
    </omf>
  </xsl:template>

  <xsl:template name="get-title">
    <xsl:for-each select="/rpm-info/titles/translation">
      <xsl:choose>
        <xsl:when test="@lang = $lang">
          <xsl:value-of select="title"/>
        </xsl:when>
      </xsl:choose>
    </xsl:for-each>
  </xsl:template>

</xsl:stylesheet>


--- NEW FILE rpm-info.dtd ---
<!--
  DTD for the Fedora Docs Project RPM Information file "rpm-info.xml"
-->

<!ELEMENT rpm-info		(release,author+,translator*,editor*,
				license,copyright+,titles,changelog)	>

<!ELEMENT release		EMPTY					>
<!ATTLIST release	rel	CDATA		#REQUIRED		>

<!ELEMENT license		(rights,license.version)		>
<!ELEMENT rights		(#PCDATA)				>
<!ELEMENT license.version	(#PCDATA)				>

<!ELEMENT copyright		(year,holder+)				>
<!ELEMENT year			(#PCDATA)				>
<!ELEMENT holder		(#PCDATA)				>

<!ELEMENT titles	 	(translation+) 				>

<!ELEMENT translation		(title,desc)*				>
<!ATTLIST translation	lang 	CDATA		#REQUIRED		>

<!ELEMENT title			(#PCDATA)				>
<!ELEMENT version 		(#PCDATA)     				>
<!ELEMENT desc			(#PCDATA)				>

<!ELEMENT changelog		(revision+)				>
<!ATTLIST changelog 	order  	(newest-first)  #REQUIRED 		>

<!ELEMENT revision		(author+,editor*,details)		>
<!ATTLIST revision  	date   	CDATA   	#REQUIRED 		>
<!ATTLIST revision  	version	CDATA   	#REQUIRED 		>

<!ELEMENT author  		EMPTY					>
<!ATTLIST author	wholename CDATA   	#REQUIRED 		>
<!ATTLIST author	email     CDATA   	#REQUIRED 		>
<!ATTLIST author  	surname   CDATA   	#REQUIRED 		>
<!ATTLIST author  	firstname CDATA   	#REQUIRED 		>
<!ATTLIST author  	initials  CDATA		#REQUIRED 		>

<!ELEMENT editor  			EMPTY				>
<!ATTLIST editor	wholename CDATA   #REQUIRED 			>
<!ATTLIST editor	email     CDATA   #REQUIRED 			>
<!ATTLIST editor  	surname   CDATA   #REQUIRED 			>
<!ATTLIST editor  	firstname CDATA   #REQUIRED 			>


<!ELEMENT translator  			EMPTY				>
<!ATTLIST translator	wholename CDATA   #REQUIRED 			>
<!ATTLIST translator	email     CDATA   #REQUIRED 			>
<!ATTLIST translator	surname   CDATA   #REQUIRED 			>
<!ATTLIST translator  	firstname CDATA   #REQUIRED 			>

<!ELEMENT details		(#PCDATA)				>


--- NEW FILE spec.xsl ---
<!-- Transform rpm-info.xml into a SPEC File -->
<xsl:stylesheet version="1.0" xml:space="preserve" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <xsl:output encoding="UTF-8" indent="no" method="text" omit-xml-declaration="no" standalone="no" version="1.0"/>

<!-- Note: do not indent this file!  Any whitespace here
     will be reproduced in the output -->

  <xsl:param name="lang" select="'en'" />
  <xsl:param name="docbase" select="'example-tutorial'" />
  <xsl:param name="release"	select="1"/>

<xsl:template match="/">
# Fedora Documentation Specfile
%define	docbase	<xsl:value-of select="$docbase"/>
%define release	<xsl:value-of select="$release"/>
#
Summary:	Fedora Documentation: %{docbase}
Name:		fedora-doc-%{docbase}
Version:	<xsl:value-of select="/rpm-info/changelog/revision[1]/@version"/>
Release:	<xsl:value-of select="/rpm-info/release/@rel"/>
License:	<xsl:value-of select="/rpm-info/license/rights"/>
Url:		http://fedora.redhat.com/projects/docs
Source0:	%{docbase}-%{version}.src.tar.gz
Source1:	%{name}.desktop
<xsl:for-each select="/rpm-info/titles/translation">
Source<xsl:value-of select="position()+1" />:	%{name}-<xsl:value-of select="@lang"/>.omf</xsl:for-each>
Group:		Documentation
BuildArch:	noarch
BuildRoot:	%{_tmppath}/%{name}-%{version}-root
Requires:	scrollkeeper &gt;= 0.3.11
Requires:	fedora-doc-common
BuildRequires:	xmlto

%description
<xsl:value-of select="/rpm-info/titles/translation[@lang='en']/desc" />

<xsl:for-each select="/rpm-info/titles/translation">
%description	<xsl:value-of select="@lang"/>
<xsl:value-of select="desc"/>
</xsl:for-each>

%prep
%setup -q -n %{docbase}-${version}
	for in in $RPM_BUILD_DIR/%{docbase}-%{version}/%{docbase}*.xml
	do
		%{__sed} -i 's;../docs-common;../../docs-common;' "$i"
	done

%build
#	/bin/rm -r $RPM_BUILD_ROOT
#	/usr/bin/install -d -m 0755 $RPM_BUILD_ROOT/%{_datadir}/omf/%{name}

%clean
	/bin/rm -rf $RPM_BUILD_ROOT

<xsl:for-each select="/rpm-info/titles/translation">
%post	<xsl:value-of select="@lang"/>
	/usr/bin/scrollkeeper-update || true
%postun	<xsl:value-of select="@lang"/>
	/usr/bin/scrollkeeper-update || true
%files	<xsl:value-of select="@lang"/>
%defattr(-, root, root, -)
</xsl:for-each>
</xsl:template>

  <xsl:template name="get-title">
    <xsl:for-each select="/rpm-info/titles/translation">
      <xsl:choose>
	<xsl:when test="@lang = $lang">
	  <xsl:value-of select="title"/>
	</xsl:when>
      </xsl:choose>
    </xsl:for-each>
  </xsl:template>

</xsl:stylesheet>



From fedora-docs-commits at redhat.com  Fri Nov 25 21:02:32 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 25 Nov 2005 16:02:32 -0500
Subject: example-tutorial rpm-info.xml,NONE,1.1
Message-ID: <200511252102.jAPL2W57031384@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31329

Added Files:
	rpm-info.xml 
Log Message:
Example of an "rpm-info.xml" file.



--- NEW FILE rpm-info.xml ---
<?xml version="1.0" encoding="UTF-8"?>

<!-- Sample document description from which we build RPMs -->
<!DOCTYPE rpm-info SYSTEM "../docs-common/packaging/rpm-info.dtd">
<rpm-info>
  <release rel="1"/>
  <author email="tcf at redhat.com" firstname="Tammy" initials="TCF" surname="Fox" wholename="Tammy Fox"/>
  <editor email="stickster at gmail.com" firstname="Paul" surname="Frields" wholename="Paul W. Frields"/>
  <license>
    <rights>GNU FDL</rights>
    <license.version>1.0</license.version>
  </license>
  <copyright>
    <year>2003, 2004, 2005</year>
    <!-- <holder>&FORMAL-RHI;</holder> -->
    <holder>Tammy Fox</holder>
  </copyright>
  <titles>
    <translation lang="en">
      <title>Example Tutorial</title>
      <desc>This is quite a feat.</desc>
    </translation>
    <translation lang="de">
      <title>Beispeil Tutorial</title>
      <desc>Ist idiotien</desc>
    </translation>
  </titles>
  <changelog order="newest-first">
    <revision date="2005-09-18" version="0.13">
      <author email="stickster at gmail.com" firstname="Paul" initials="PWF" surname="Frields" wholename="Paul W. Frields"/>
      <details>Add revision history</details>
    </revision>
  </changelog>
</rpm-info>



From fedora-docs-commits at redhat.com  Fri Nov 25 21:12:20 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Fri, 25 Nov 2005 16:12:20 -0500
Subject: release-notes colophon-relnotes-it.xml, 1.1, 1.2 desktop-it.xml, 1.1,
	1.2 development-tools-it.xml, 1.1, 1.2 file-servers-it.xml,
	1.1, 1.2 hardware-reqs-it.xml, 1.2, 1.3 i18n-it.xml, 1.1,
	1.2 install-notes-it.xml, 1.2, 1.3 java-package-it.xml, 1.2,
	1.3 kernel-it.xml, 1.2, 1.3 legacy-it.xml, 1.1,
	1.2 multimedia-it.xml, 1.1, 1.2 overview-it.xml, 1.2,
	1.3 package-movement-it.xml, 1.4, 1.5 package-notes-it.xml,
	1.3, 1.4 project-overview-it.xml, 1.2,
	1.3 RELEASE-NOTES-it.xml, 1.3, 1.4 security-it.xml, 1.1,
	1.2 splash-it.xml, 1.2, 1.3 web-servers-it.xml, 1.1,
	1.2 xorg-it.xml, 1.2, 1.3
Message-ID: <200511252112.jAPLCKju031564@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31526/release-notes

Modified Files:
	colophon-relnotes-it.xml desktop-it.xml 
	development-tools-it.xml file-servers-it.xml 
	hardware-reqs-it.xml i18n-it.xml install-notes-it.xml 
	java-package-it.xml kernel-it.xml legacy-it.xml 
	multimedia-it.xml overview-it.xml package-movement-it.xml 
	package-notes-it.xml project-overview-it.xml 
	RELEASE-NOTES-it.xml security-it.xml splash-it.xml 
	web-servers-it.xml xorg-it.xml 
Log Message:
Aligned to latest release notes from Wade & Ellis


Index: colophon-relnotes-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/colophon-relnotes-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- colophon-relnotes-it.xml	22 Nov 2005 18:15:37 -0000	1.1
+++ colophon-relnotes-it.xml	25 Nov 2005 21:12:13 -0000	1.2
@@ -1,5 +1,5 @@
 <section id="sn-colophon">
-  <title>&FC; Release Notes Colophon</title>
+  <title>Colophon Note di rilascio &FC;</title>
   <note>
     <title>Colophon preliminare</title>
     <para>


Index: desktop-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/desktop-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- desktop-it.xml	4 Nov 2005 19:54:45 -0000	1.1
+++ desktop-it.xml	25 Nov 2005 21:12:13 -0000	1.2
@@ -3,70 +3,88 @@
   <itemizedlist>
     <title>Note</title>
     <listitem>
-      <para>GNOME 2.12 e KDE 3.4.2 Caratteristiche principali
+      <para>GNOME 2.12 e KDE 3.4.2 sono inclusi in &FC; &LOCALVER;.
       </para>
     </listitem>
     <listitem>
-      <para>La test release attuale ha GNOME 2.12.1, insieme ad
-	alcune anticipazioni di tecnologia del prossimo GNOME 2.14:
+      <para>Questa test release ha GNOME 2.12.1, insieme ad
+	alcune anticipazioni della tecnologia del prossimo GNOME 2.14. Riscontri
+	su questi pacchetti sno apprezzati in modo speciale.
       </para>
       <itemizedlist>
         <listitem>
-          <para>gnome-power-manager: porta l'Hardware Abstraction
-	    Layer al mondo delle batterie dei laptop e delle unit?? UPS - queste
-	    cose dovrebbero "semplicemente funzionare", con una semplice UI
-	    (naturalmente, in una test release, potrebbero non farlo)
+          <para><filename>gnome-power-manager</filename>:
+	    <application>GNOME Power Manager </application> ?? un demone
+	    di sessione per l'ambiente desktop GNOME che rende semplice
+	    amministrare l'alimentazione sul tuo sistema portatile o desktop. Si
+	    avvantaggia dell'HAL (che fornisce un hardware abstraction
+	    layer) e di DBUS (software di comunicazione inter process)
+	    scritto e mantenuto da sviluppatori &FC;.
 	  </para>
         </listitem>
         <listitem>
-          <para>gnome-screensaver: da una fresca UI agli screensavers e
-	    alla finestra di dialogo <guilabel>Lock Screen</guilabel>
+          <para><filename>gnome-screensaver</filename>: fornisce un
+	    interfaccia utente integrata agli screensavers ed alla finestra di
+	    dialogo di blocco dello schermo.
 	  </para>
         </listitem>
         <listitem>
-          <para>Ottimizzazioni della memoria nei pacchetti fontconfig e
-	    shared-mime-info (questi ora usano shared
-	    memory-mapped caches per questi dati).  Entrambe queste caches
-	    sono ancora qualcosa di sperimentale.
+          <para>Ottimizzazioni della memoria nei
+	    pacchetti <filename>fontconfig</filename> e
+	    <filename>shared-mime-info</filename>.  Questi ora
+	    usano shared memory-mapped caches per questi dati.
 	  </para>
         </listitem>
       </itemizedlist>
     </listitem>
-  <para>
-    Sono apprezzati in modo speciale i feedback di test su questi pacchetti
-    sperimentali.
-  </para>
-  <para>
-    GNOME 2.12 ha rimosso l'opzione terminale dal menu di base del desktop.
-    nautilus-open-terminal nel repositorio Fedora Extras ne fornisce un
-    sostituto avanzato. E' anche gi?? menzionato nella release notes di 
-    GNOME 2.12 ma abbiamo voluto evidenziarlo poich?? il pacchetto ?? fornito
-    con il repositorio extras.
-  </para>
-  <para>
-    Screensavers per impostazione predefinita non sono pi?? installati. Spiegheremo perch??
-    e forniremo i comandi per installarli.
-  </para>
-  <para>MCS SELinux ?? in rawhide. Caratteristiche principali
-    (<emphasis>tentativo</emphasis> - non assicuriamo la qualificazione del
-    cambiamento)
-  </para>
-  <caution>
-    <title>OpenOffice ed upgrading dalle test releases</title>
-    <para>
-      Se hai scelto di andare contro le raccomandazioni di <emphasis
-	role='strong'>non</emphasis> aggiornare da una test
-      release precedente, potrai avere un problema con <ulink
-	url='/OpenOffice'>OpenOffice</ulink> eseguendo l'upgrade.
-    </para>
-    <para>
-      Per risolverla, dovrai dare il seguente comando <emphasis
-	role='strong'>prima</emphasis> di fare l'upgrade:
-    </para>
+    <listitem>
+      <para>GNOME 2.12 ha rimosso l'opzione
+	<guimenuitem>terminal</guimenuitem> dal menu contestuale
+	del desktop. Il pacchetto
+	<filename>nautilus-open-terminal</filename> nel repositorio &FEX;
+	fornisce un sostituto avanzato per coloro che lo richiedono.
+	Puoi installarlo usando il seguente comando:
+      </para>
 <screen>
-<command>rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
+<command>yum install nautilus-open-terminal</command>
 </screen>
-  </caution>
+    </listitem>
+    <listitem>
+      <para>Solo il salvaschermo blank ?? prinstallato, fin
+      da &FC; 4.
+      </para>
+      <para>
+	Il motivo principale ?? che ?? noto che alcuni screensavers non
+	funzionano correttamente o terminano bruscamente l'interfaccia grafica.
+	Ci?? ?? particolarmente vero per alcuni di quelli animati OpenGL
+	forniti con il pacchetto
+	<filename></filename>xscreensaver-gl-extras.
+      </para>
+      <para>
+	Inoltre, il materiale contenuto negli screensavers ??
+	talvolta controverso o causa di forti reazioni.  E'
+	meglio, per l'esperienza dell'utente, non essere sorpresi dalla
+	natura degli screensavers.
+      </para>
+      <para>
+	Gli utenti che vogliono installare il pacchetto screensavers possono usare
+	il seguente comando.
+      </para>
+<screen>
+<command>yum install xscreensaver-extras xscreensaver-gl-extras</command>
+</screen>
+    </listitem>
+  </itemizedlist>
+  <note>
+    <title>L'utilit?? di configurazione del mouse ?? cambiata</title>
+    <para>
+      L'utilit?? di configurazione
+      <application>system-config-mouse</application> ?? stata scartata
+      da questa release poich?? synaptic e la configurazione del mouse a 3 bottoni
+      viene fatta automaticamente durante l'installazione. I mouse seriali sono
+      formalmente non pi?? supportati da &FC;.
+    </para>
+  </note>
 </section>
 <!--
 Local variables:


Index: development-tools-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/development-tools-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- development-tools-it.xml	4 Nov 2005 19:55:14 -0000	1.1
+++ development-tools-it.xml	25 Nov 2005 21:12:13 -0000	1.2
@@ -9,11 +9,39 @@
 
 ]>
 -->
-<!-- Content commented out, no update performed by beat writer yet.
 <section id="sn-devel">
   <title>
     Strumenti di sviluppo
   </title>
+  <section id="sn-java-development">
+    <title>Ambiente Java-like</title>
+    <para>Un ambiente libero ed open source Java-like ?? disponibile
+      in questa release di &FC; &LOCALVER;.
+    </para>
+    <para>
+      Ha tre componenti: GNU Java runtime
+      (<filename>libgcj</filename>), il compilatore Eclipse Java
+      (<command>ecj</command>), ed un gruppo di wrappers e links
+      (<filename>java-gcj-compat</filename>) che mostrano la runtime
+      ed il compiler all'utente nello stesso modo in cui vengono presentati
+      gli altri ambienti Java.
+    </para>
+    <para>
+      Diversi pacchetti software principali come Openoffice.org Base,
+      Eclipse, ed Apache Tomcat, oltre a diversi altri pacchetti software Java
+      inclusi in questa release, sono compatibili con questo
+      ambiente.
+    </para>
+    <para>
+      Per maggiori informazioni, fa riferimento alla FAQ:
+    </para>
+    <para>
+      <ulink
+	url='http://www.fedoraproject.org/wiki/JavaFAQ'>http://www.fedoraproject.org/wiki/JavaFAQ</ulink>
+    </para>
+  </section>
+
+<!-- Content commented out, no update performed by beat writer yet.
   <section id="sn-devel-gcc">
     <title>Collezione di compilatori GCC</title>
     <para>
@@ -177,6 +205,7 @@
   </section>
 </section>
 -->
+</section>
 
 <!--
 Local variables:


Index: file-servers-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/file-servers-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- file-servers-it.xml	4 Nov 2005 19:55:14 -0000	1.1
+++ file-servers-it.xml	25 Nov 2005 21:12:13 -0000	1.2
@@ -10,7 +10,8 @@
   <para>
     Questa sezione si riferisce ai servers di file e di condivisione.
     Siete pregati di fare riferimento alle sezioni &WEB-SERVERS; e &SAMBA; per
-    informazioni sul trasferimento file HTTP (Web) e sulla condivisione file Samba (Windows).
+    informazioni sul trasferimento file HTTP (Web) e sulla condivisione file 
+    Samba (Windows).
   </para>
   <section id="sn-file-servers-netatalk-suite">
     <title>Netatalk (Compatibilit?? Macintosh)</title>
@@ -23,12 +24,18 @@
       <title><filename>netatalk</filename></title>
       <para>
 	&DISTRO; &DISTROVER; include la versione 2 di Netatalk.
-	<emphasis>Aggiornare da Netatalk versione 1 a versione 2 pu??
-	  causare la perdita di dati</emphasis>.    La versione 2 di Netatalk usa
-	un differente metodo per registrare i file resource forks dalla
-	precedente versione, e pu?? richiedere una differente codifica del nome del
-	file.  Siete pregati di leggere la documentazione e pianificare la vostra migrazione
-	prima di eseguire l'aggiornamento.
+      </para>
+      <caution>
+	<title>Fa attenzione quando aggiorni le versioni di Netatalk</title>
+	<para>
+	  Aggiornando da Netatalk versione 1 alla versione 2 si corre il rischio
+	  di perdere dei dati.
+	</para>
+      </caution>
+      <para>La versione 2 di Netatalk usa un metodo differente di registrare i file
+	resource forks dalla versione precedente, e pu?? richiedere una
+	differente schema di codifica dei nomi dei file.  Leggi la documentazione e
+	pianifica la tua migrazione prima di eseguire l'aggiornamento.
       </para>
       <para>
 	Le informazioni sull'aggiornamento sono disponibili direttamente dal sito


Index: hardware-reqs-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/hardware-reqs-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- hardware-reqs-it.xml	5 Nov 2005 15:19:09 -0000	1.2
+++ hardware-reqs-it.xml	25 Nov 2005 21:12:13 -0000	1.3
@@ -231,21 +231,20 @@
 	<para>
 	  <!--<remark os="test">(ppc)</remark> --> &FC; &LOCALVER;
 	  supporta solo la generazione <quote>New World</quote> di Apple
-	  Power Macintosh, venduta dal 1999 in avanti. Supporta anche
-	  il processore 64-bit G5 ed i processori POWER negli IBM eServer
-	  pSeries. Attualmente le macchine a 32-bit IBM RS/6000 non sono
-	  supportate.
+	  Power Macintosh, (venduta dal 1999 in avanti), Genesi Pegasos II, e le macchine
+	  IBM 32-bit RS/6000. Supporta anche il processore 64-bit G5 ed i processori POWER
+	  negli IBM eServer pSeries.
 	</para>
       </listitem>
       <listitem>
 	<para>
-	  <!--<remark os="test">(x86)</remark> --> Raccommandato per
+	  <!--<remark os="test">(x86)</remark> --> Raccomandato per
 	  la modalit?? testo: 233 MHz G3 o superiore
 	</para>
       </listitem>
       <listitem>
 	<para>
-	  <!-- <remark os="test">(ppc)</remark> --> Raccommendato per
+	  <!-- <remark os="test">(ppc)</remark> --> Raccomandato per
 	  la modalit?? grafica: 400 MHz G3 o superiore
 	</para>
       </listitem>


Index: i18n-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/i18n-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- i18n-it.xml	4 Nov 2005 19:56:08 -0000	1.1
+++ i18n-it.xml	25 Nov 2005 21:12:13 -0000	1.2
@@ -1,5 +1,5 @@
 <section id="sn-i18n">
-  <title>Internationalizazione (i18n)</title>
+  <title>Internazionalizzazione (i18n)</title>
   <para>
     SCIM ha sostituito tutti gli altri metodi di input. Principali caratteristiche.
   </para>
@@ -9,99 +9,13 @@
       Questa sezione include le informazioni relative al supporto dei
       vari linguaggi in &DISTRO;.
     </para>
-    <section>
-      <title>Il sistema di input IIIMF</title>
+    <note>
+      <title>IIIMF replaced</title>
       <para>
-	IIIMF ?? l'Internet/Intranet Input Method Framework.  In &FC;
-	&LOCALVER; il pacchetto <filename>iiimf</filename> ?? aggiornato alla
-	versione 12.2.
+	SCIM ha sostituito IIIMF in questa release
+	di Fedora Core.
       </para>
-      <variablelist>
-	<varlistentry>
-	  <term>Cambiamenti di percorso dei file</term>
-	  <listitem>
-	    <para>
-	      I nomi e le locazioni di alcuni files nel pacchetto
-	      <filename>iiimf</filename> sono stati cambiati.
-	    </para>
-	    <para>
-	      Il server IIIMF ?? stato rinominato da
-	      <filename>/usr/sbin/htt</filename> a
-	      <filename>/usr/bin/iiimd</filename>, e lo XIM bridge
-	      client ?? stato rinominato da <filename>httx</filename> a
-	      <filename>iiimx</filename>. Il nome dello script
-	      <filename>init.d</filename> non ?? cambiato:
-	      ?? ancora chiamato <filename>iiim</filename>. Tutti i
-	      files di configurazione globali del sistema sono ora collocati sotto
-	      <filename>/etc/iiim/</filename>.
-	    </para>
-	    <para>
-	      Gli sviluppatori della Language Engine (LE) noteranno che i moduli LE
-	      ed i loro dati adesso risiedono sotto
-	      <filename>${libdir}/iiim/le/<filename>&lt;LE_NAME&gt;</filename>/</filename>, 
-	      mentre i dati di runtime sono immagazzinati sotto
-	      <filename>/var/lib/iiim/le/<replaceable>&lt;LE_NAME&gt;</replaceable>/</filename>.
-	    </para>
-	    <para>
-	      Per ulteriori informazioni sull'esatto percorso e cambiamento della locazione
-	      dei file, fate riferimento alle Fedora IIIMF FAQ:
-	    </para>
-	    <para>
-	      <ulink
-		url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term>Hotkeys</term>
-	  <listitem>
-	    <para>
-	      Le scorciatoie, come
-	      <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo> 
-	      usate per attivare Input Methods, sono ora configurabili con lo strumento a
-	      linea di comando <command>iiimf-le-tools</command>.
-	      Questa caratteristica ?? attualmente supportata solo dalle applicazioni
-	      GTK2.  Per le altre applicazioni che usano XIM le chiavi
-	      di scorciatoia possono essere cambiate usando una risorsa X.  Fate riferimento alle
-	      IIIMF FAQ su <ulink
-		url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink> 
-	      per ulteriori dettagli su come cambiare le chiavi di scorciatoia.
-	    </para>
-	    <para>
-	      Nota che il nome della chiave si riferisce al nome del simbolo della chiave X. Per
-	      esempio, se vuoi attivare un
-	      <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>, 
-	      devi specificare '&lt;Control&gt;at' come nome della chiave e non
-	      '&lt;Control&gt;@'.
-	    </para>
-	    <para>
-	      La configurazione per-user delle scorciatoie attualmente non funziona
-	      con &SEL; in modalit?? enforcing a causa di una mancanza della
-	      &SEL; policy.  In questo caso, le scorciatoie possono essere cambiate
-	      solo nella configurazione globale del sistema.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term>Supporto Qt</term>
-	  <listitem>
-	    <para>
-	      Un immodule Qt per <filename>iiimf</filename> ?? ora
-	      incluso.  Questo immodule funziona, ma manca di una finestra di status
-	      ed ?? considerato sperimentale.  Perci??, le impostazioni predefinite
-	      per le applicazioni Qt sono di continuare ad usare XIM per l'input IIMF.
-	    </para>
-	    <para>
-	      Se vuoi provare l'immodule in un applicazione Qt, prima
-	      installa il pacchetto <filename>iiimf-qt</filename>, avvia
-	      l'applicazione, quindi clicca il bottone-3 del mouse in un area
-	      di input e seleziona <guimenuitem>iiimqcf</guimenuitem> dal
-	      submenu <guisubmenu>Select Input Method</guisubmenu>'.
-	    </para>
-	  </listitem>
-	</varlistentry>
-      </variablelist>
-    </section>
+    </note>
   </section>
 </section>
 <!--


Index: install-notes-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- install-notes-it.xml	5 Nov 2005 15:43:27 -0000	1.2
+++ install-notes-it.xml	25 Nov 2005 21:12:13 -0000	1.3
@@ -1,5 +1,5 @@
 <section id="sn-anaconda">
-  <title>Note Relative all'installazione</title>
+  <title>Note relative all'installazione</title>
   <para>
     Questa sezione descrive le problematiche relative ad Anaconda
     (il programma di installazione di &DISTRO;) ed all'installazione di &DISTRO;
@@ -11,11 +11,12 @@
       Se intendi scaricare l'immagine ISO DVD di &DISTRO; &DISTROVER;,
       tieni a mente che non tutti gli strumenti di download file possono
       scaricare files pi?? grandi di 2GB.  Per esempio,
-      <command>wget</command> si chiuderebbe con un errore <computeroutput>File size
-	limit exceeded</computeroutput>.
+      <command>wget</command> versione precedente alla 1.9.1.16 si chiuderebbe con un errore
+      <computeroutput>File size limit exceeded</computeroutput>.
     </para>
     <para>
-      Gli strumenti <command>curl</command> e <command>ncftpget</command>
+      Gli strumenti per scaricare <command>wget</command> versione 1.9.1-16 e successivi,
+      <command>curl</command> e <command>ncftpget</command>
       non hanno questa limitazione, e possono
       scaricare con successo files pi?? grandi di 2GB.
     </para>
@@ -31,39 +32,11 @@
   </note>
   <section id="sn-install-notes-ppc">
     <title>Note di installazione PPC</title>
-    <section>
-      <title>Requisiti hardware PPC</title>
-      <para>
-	Questa sezione elenca l'hardware minimo PowerPC (PPC) necessario
-	all'installazione di &DISTRO; &DISTROVER;.
-      </para>
-      <itemizedlist>
-	<listitem>
-	  <para>Minimo: PowerPC G3 / POWER4 </para>
-	</listitem>
-	<listitem>
-	  <para>&DISTRO; &DISTROVER; supporta solo la generazione ???New World???
-	    degli Apple Power Macintosh, venduta all'incirca dal 1999 in avanti.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>&DISTRO; &DISTROVER; supporta anche gli IBM eServer pSeries, IBM
-	    RS/6000, e le macchine Genesi Pegasos II.</para>
-	</listitem>
-	<listitem>
-	  <para>Raccomandato per la modalit?? testo: 233 MHz G3 or better, 64MB
-	    RAM.</para>
-	</listitem>
-	<listitem>
-	  <para>Raccomandato per la modalit?? grafica: 400 MHz G3 or better, 128MB
-	    RAM.</para>
-	</listitem>
-      </itemizedlist>
       <para>
 	Il DVD o il primo CD del gruppo di dischi d'installazione di &FC; ?? impostato
 	per essere avviabile sull'hardware supportato. In aggiunta, immagini avviabili di CD
 	possono essere trovate nella directory <filename>images/</filename> del
-	DVD o del primo CD. Queste si comporteranno differentemente a seconda
+	DVD o del primo CD. Queste si comportano differentemente a seconda
 	dell'hardware:
       </para>
       <variablelist>
@@ -71,15 +44,14 @@
 	<varlistentry>
 	  <term>Apple Macintosh </term>
 	  <listitem>
-	    <para>Il bootloader avvier?? automaticamente
-	      l'appropriato installer a 32-bit o 64-bit.  Il supporto del power
+	    <para>Il bootloader avvier?? automaticamente l'appropriato
+	      installer a 32-bit o 64-bit.  Il supporto del power
 	      management, incluso lo sleep e l'amministrazione della retroilluminazione,
-	      ?? presente nel pacchetto <filename>apmud</filename>,
-	      in &FEX;. &FEX; per &FC; ?? per impostazione predefinita, gi?? configurato
-	      per yum. Seguendo l'installazione,
-	      <filename>apmud</filename> pu?? essere installato eseguendo il
-	      comando <command>yum install apmud</command> in un
-	      terminale.
+	      ?? presente nel pacchetto <filename>apmud</filename>, che
+	      in &FEX;. &FEX; per &FC; ?? preconfigurato per yum.
+	      Seguendo l'installazione, <filename>apmud</filename> pu?? essere
+	      installato eseguendo il comando <command>yum install
+	      apmud</command> in un terminale.
 	    </para>
 	  </listitem>
 	</varlistentry>
@@ -115,10 +87,10 @@
 </screen> 
 	    <para>
 	      Avrai anche bisogno di configurare manualmente OpenFirmware sul
-	      Pegasos per rendere il sistema &FC; installato
-	      avviabile. Per far questo, dovrai impostare le variabili ambiente
-	      <envar>boot-device</envar> e <envar>boot-file</envar>
-	      in modo appropriato.
+	      Pegasos per rendere il sistema &FC; installato avviabile. Per far
+	      questo, dovrai impostare le variabili ambiente <envar>boot-device</envar> e
+	      <envar>boot-file</envar> in modo
+	      appropriato.
 	    </para>
 	  </listitem>
 	</varlistentry>
@@ -126,12 +98,13 @@
 	  <term>Avvio via network</term>
 	  <listitem>
 	    <para>Ci sono immagini combinate contenenti il kernel d'installazione
-	      ed il ramdisk nella directory <filename>images/netboot/</filename> dell'albero
+	      ed il ramdisk nella directory
+	      <filename>images/netboot/</filename> dell'albero
 	      d'installazione. Queste sono intese per l'avvio da network con
 	      TFTP, ma possono essere usate in molti modi.
 	    </para>
 	    <para>
-	      Il comando <command>yaboot</command> supporta l'avvio tftp
+	      Il comando <command>yaboot</command> supporta l'avvio TFTP
 	      per IBM eServer pSeries ed Apple Macintosh. &FED;
 	      raccomanda di usare <command>yaboot</command> sulle immagini netboot.
 	    </para>
@@ -139,8 +112,7 @@
 	</varlistentry>
       </variablelist>
     </section>
-  </section>
-  <section>
+  <section id="sn-anaconda-notes">
     <title>Note su anaconda</title>
 
     <itemizedlist>
@@ -175,10 +147,6 @@
 	</para>
       </listitem>
       <listitem arch="x86">
-<!--	<remark os="test">%%% <ulink
-	    url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654">http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654</ulink> 
-	  %%%</remark>
--->
 	<para>
 	  <!-- <remark os="test">(x86)</remark> --> Dei Test della memoria possono essere
 	  effettuati prima di eseguire l'installazione di &DISTRO; immettendo
@@ -199,17 +167,72 @@
 	  %%%</remark>
 -->
 	<para>
-	  &DISTRO; &DISTROVER; supporta installazioni grafiche FTP ed HTTP.
-	  Comunque, a causa della necessit?? di contenere
-	  l'immagine d'installazione in RAM, solo i sistemi con pi?? di 128MB
+	  &DISTRO; &DISTROVER; supporta installazioni grafiche
+	  FTP ed HTTP. Comunque, a causa della necessit?? di contenere
+	  l'immagine d'installazione in RAM, solo i sistemi con pi?? di 128MiB
 	  di RAM (o sistemi avviati dal CD-ROM 1, che contiene l'immagine
 	  d'installazione) possono usare l'installer grafico.  I sistemi
-	  con 128MB o meno potranno continuare ad usare l'installer testuale.
+	  con 128MiB o meno potranno continuare ad usare l'installer
+	  testuale.
 	</para>
       </listitem>
     </itemizedlist>
   </section>
-  <section>
+  <section id="sn-installer-changes">
+    <title>Cambiamenti nel programma d'installazione</title>
+    <itemizedlist>
+      <listitem>
+	<para>E stato aggiunto supporto per <command>yum</command> come
+	  backend di risoluzione delle dipendenze per i pacchetti software che sono stati
+	  aggiunti.  Ci si aspetta che altri repositori siano supportati
+	  durante l'installazione in una futura release.
+	</para>
+      </listitem>
+      <listitem>
+	<para>In questa release, l'installer controlla le possibilit??
+	  dell'hardware ed installa il kernel uniprocessoro o SMP
+	  (Symmetric Multi Processor), in modo appropriato. Le precedenti
+	  versioni installavano entrambe le varianti usando poi quella appropriata
+	  come predefinita.
+	</para>
+      </listitem>
+      <listitem>
+	<para>Le impostazioni di partizionamento sono state rielaborate per essere
+	  pi?? amichevoli per l'utente.
+	</para>
+      </listitem>
+      <listitem>
+	<para>In questa release ?? supportato il logging remoto via 
+	  <command>syslog</command>.  Per abilitarlo, passa
+	  <option>syslog=host:port</option> al prompt di boot.
+	  Specificare la porta ?? opzionale.
+	</para>
+      </listitem>
+      <listitem>
+	<para>La configurazione del Firewall/SELinux ?? stata spostata nella fase finale
+	  dell'installazione chiamata
+	  <application>firstboot</application>.
+	</para>
+      </listitem>
+      <listitem>
+	<para>Il rendering delle pagine HTML durante l'installazione ?? fatto usando
+	  i widget <command>gtkhtml</command> per ottenere maggiori possibilit??.
+	</para>
+      </listitem>
+      <listitem>
+	<para>Il kickstart ?? stato riassemblato nel suo nuovo pacchetto -
+	  <filename>pykickstart</filename> - contenente parser e
+	  writers. Come risultato di questo cambiamento, la validazione e l'estensione
+	  del kickstart ?? ora pi?? facile.
+	</para>
+      </listitem>
+      <listitem>
+	<para>I mouse seriali sono formalmente non pi?? supportati
+	  ne dall'installer ne da &FC;. </para>
+      </listitem>
+    </itemizedlist>
+  </section>
+  <section id="sn-install-related-issues">
     <title>Problemi relativi all'intallazione</title>
     <itemizedlist>
       <listitem>
@@ -220,7 +243,6 @@
 	  l'installazione, ed aggiungete l'opzione "<command>nofb</command>" nella
 	  linea di comando di boot.
 	</para>
-
 	<note>
 	  <title>Nota</title>
 	  <para>


Index: java-package-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/java-package-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- java-package-it.xml	5 Nov 2005 17:47:06 -0000	1.2
+++ java-package-it.xml	25 Nov 2005 21:12:13 -0000	1.3
@@ -1,12 +1,5 @@
 <section id="sn-java-packages">
   <title>Raccomandazioni sul pacchetto Java</title>
-  <caution>
-    <title>Informazioni non aggiornate</title>
-    <para>
-      Il contenuto in questa sezione ha necessit?? di essere aggiornato per &DISTRO;
-      &DISTROVER;
-    </para>
-  </caution>
   <para>
     Gli utenti di &FC; &LOCALVER; sono avvisati di non utilizzare i pacchetti RPM Java forniti
     da Sun.  Essi contengono <computeroutput>producono</computeroutput> un


Index: kernel-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/kernel-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- kernel-it.xml	5 Nov 2005 18:08:28 -0000	1.2
+++ kernel-it.xml	25 Nov 2005 21:12:13 -0000	1.3
@@ -12,60 +12,62 @@
 ]>
 -->
 <section id="sn-kernel">
-  <title>
-    Linux Kernel
-  </title>
-  <section id="sn-kernel-lotsa">
+  <title>Linux Kernel</title>
+  <section id="sn-kernel-version">
     <title>Versione</title>
     <para>
       La distribuzione ?? basata sulla serie 2.6 del kernel di Linux. &FC; pu?? includere
       patches aggiuntive per miglioramenti, bug fixes, o caratteristiche
       aggiuntive. Per questa ragione, il kernel di &FC; potrebbe non essere
-      linea-per-linea equivalente al kernel vanilla<firstterm></firstterm> proveniente dal sito web di
-      <ulink
-  url="http://www.kernel.org"><filename>kernel.org</filename></ulink>.
+      linea-per-linea equivalente al <firstterm>vanilla
+	kernel</firstterm> proveniente dal
+      sito web di <ulink
+	url='http://www.kernel.org/'>http://www.kernel.org/</ulink>.
     </para>
     <para>
-      Potrai ottenere una lista di ciascuna di queste patches usando il seguente comando sul pacchetto di &FC;:
-    </para>
-<screen width="56">
-<command>rpm <parameter class="option">-qpl</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
+      Potrai ottenere una lista di ciascuna di queste patches usando il seguente comando
+      sul pacchetto di &FC;:</para>
+<screen>
+<command>rpm -qpl kernel-&lt;version>.src.rpm</command>
 </screen>
   </section>
   <section id="sn-kernel-flavors">
     <title>Tipi di Kernel</title>
-    <para>
-      &FC; include i seguenti kernel compilati:
-    </para>
+    <para>&FC; include i seguenti kernel compilati: </para>
     <itemizedlist>
       <listitem>
-        <para>Kernel nativo, nelle variet?? uniprocessore e
-	  <abbrev>SMP</abbrev>. I sorgenti configurati sono
-	  disponibili nel pacchetto
+        <para>Kernel nativo, nelle variet?? uniprocessore e SMP (Symmetric
+	  Multi Processor). I sorgenti configurati sono disponibili
+	  nel
+	  pacchetto
 	  <filename>kernel-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>.
         </para>
       </listitem>
       <listitem>
-        <para>
-          Kernel virtuale per l'uso con il pacchetto emulatore <application>Xen</application>.
+        <para>Kernel virtuale per l'uso con il pacchetto emulatore Xen.
 	  I sorgenti configurati sono disponibili nel pacchetto
 	  <filename>kernel-xen0-devel-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename>.
         </para>
       </listitem>
     </itemizedlist>
     <para>
-      I sorgenti per entrambe i tipi di kernel possono essere installati allo stesso momento.
+      I sorgenti per entrambe i tipi di kernel possono essere installati allo stesso tempo.
       I files sono installati nell'albero
       <filename>/usr/src/kernels/<replaceable>version</replaceable>[-xen0]-<replaceable>arch</replaceable>/</filename>.
-      Usando il comando:
-    </para>
-<screen width="56">
-<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</filename></command>
-</screen>
-    <para>
+      Usando il comando: <command>rpm -Uvh
+	kernel-devel[-xen0]-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</command> 
       appropriatamente.
     </para>
-    <tip>
+    <note> 
+      <title>Non c'?? un kernel SMP per x86_64 separato</title>
+      <para>
+	I kernels predefinit per l'architettura x86_64 fornisce la capacit??
+	SMP. Non ?? disponibile un kernel SMP separato per questa
+	architettura in &FC; &LOCALVER;.
+      </para>
+    </note>
+  </section>
+  <section>
       <title>Riguardo ai libri di testo generici sul Kernel di Linux</title>
       <para>
         Molti dei tutorial, esempi, e libri di testo sullo sviluppo del 
@@ -75,229 +77,191 @@
 	materiale dapprendimento con i pacchetti di &FC;. Installa gli
 	appropriati sorgenti del kernel, come mostrato sopra, quindi:
       </para>
-<screen width="56">
-<command>ln <parameter class="option">-s</parameter> <filename>/usr/src/kernels/kernel-<replaceable>all-the-rest</replaceable></filename> <filename>/usr/src/linux</filename></command>
+<screen>
+<command>ln -s /usr/src/kernels/kernel-<replaceable>version</replaceable>-<replaceable>arch</replaceable> /usr/src/linux</command>
 </screen>
-    </tip>
   </section>
-  <!--
-  <tip>
-    <title>Usare <command>yum</command> per rimuovere i pacchetti del Kernel
-    </title>
-    <para>
-      &FC; &LOCALVER; contiene il supporto per sistemi cluster che usano CMAN e GFS.
-      Questi kernels richiedono assistenza da alcuni pacchetti in user-space.
-      Questi pacchetti non sono rimossi quando usi <command>rpm
-      -e</command> per rimuovere le vecchie versioni dei pacchetti del kernel.
-    </para>
+  <section id="sn-kernel-exploding">
+    <title>Preparazione allo sviluppo del Kernel</title>
     <para>
-      Quando usi <command>rpm -e kernel-<replaceable>version</replaceable> </command> per rimuovere il kernel, devi anche rimuovere i pacchetti di assistenza user-space.  Potresti considerare uno strumento di risoluzione delle dipendenze come <command>yum remove kernel-<replaceable>version</replaceable> </command>.
-      Questo automaticamente rimuover?? qualsiasi pacchetto dipendente.
+      &FC; &LOCALVER; non include il pacchetto <filename>kernel-source</filename>
+      fornito nelle vecchie versioni. Invece, sono disponibili sorgenti configurati
+      come descritto in <xref linkend="sn-kernel-flavors"/>.
+      Gli utenti che hanno bisogno dei sorgenti originali del kernel di &FC;
+      possono trovarli nel pacchetto kernel <filename>.src.rpm</filename>.
     </para>
-  </tip>
-  -->
-  <section id="sn-kernel-exploding">
-    <title>
-      Preparazione allo sviluppo del Kernel
-    </title>
     <para>
-      &DISTRO; &DISTROVER; non include il pacchetto
-      <filename>kernel-source</filename> fornito nelle vecchie
-      versioni. Invece, sono disponibili sorgenti configurati come descritto
-      in <xref
-  linkend="sn-kernel-flavors"/>. Gli utenti che hanno bisogno dei sorgenti 
-      originali del kernel di &FC; possono trovarli nel pacchetto
-      <filename>kernel</filename> <filename>.src.rpm</filename>.
       Per creare un albero di sorgenti esploso da questo file, seguite i
       seguenti passi:
     </para>
-    <important>
-    <title>Queste istruzioni fanno riferimento al Kernel attuale!</title>
-      <para>
+    <tip>
+      <title>Queste istruzioni fanno riferimento al Kernel attuale!</title>
+        <para>
 	Per semplificare le seguenti direttive, assumiamo che tu voglia
 	configurare i sorgenti del kernel che combaciano con la versione del kernel
-	che hai in esecuzione. Nei prossimi passi, dovrai capire che
-	la parola
+	che hai in esecuzione. Nei prossimi passi, la parola
 	<replaceable>version</replaceable> si riferisce alla versione del kernel
-	mostrata da questo comando:
+	mostrata da questo comando:<command>uname -r</command>
       </para>
-<screen width="56">
-<command>uname <parameter class="option">-r</parameter></command>
-</screen>
-    </important>
-    <procedure id="sn-kernel-exploding-steps">
+    </tip>
+    <procedure>
       <step>
         <para>
-          Puoi ottenere il file
+          Ottieni il file
 	  <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename> 
 	  da una delle seguenti risorse:
         </para>
         <itemizedlist>
           <listitem>
-            <para>La directory <filename>SRPMS/</filename> sull'appropriato
-	      <abbrev>CD</abbrev> o immagine <filename>ISO</filename>
-	      <wordasword>SRPMS</wordasword>.
-              </para>
-          </listitem>
-          <listitem>
-            <para>Il sito FTP da dove hai scaricato il pacchetto del kernel.
+            <para>La directory SRPMS sull'appropriato SRPMS CD o immagine
+              iso.
             </para>
           </listitem>
           <listitem>
-            <para>Eseguendo il seguente comando:
+            <para>Il sito FTP da dove hai scaricato il pacchetto del kernel.
             </para>
-<!-- FIXME up2date is sorta deprecated for FC, how to do this with yum? -->
-<screen width="56">
-<command>up2date <parameter class="option">--get-source</parameter> <filename>kernel</filename></command>
-</screen>
           </listitem>
         </itemizedlist>
+        <para>
+          Installa il pacchetto eseguendo il seguente comando: o:
+	</para>
+<screen>
+<command>yum install yum-utils yumdownloader --source kernel</command>
+</screen>
       </step>
       <step>
-        <para>
-          Installa il pacchetto
+	<para>
+	  Installa il
 	  <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename> 
-	  usando il seguente comando:
-        </para>
-<screen width="56">
-<command>rpm <parameter class="option">-Uvh</parameter> <filename>kernel-<replaceable>version</replaceable>.src.rpm</filename></command>
-</screen>
-        <para>
-          Questo scriver?? i contenuti dell'<abbrev>RPM</abbrev> in
+	  usando il comando <command>rpm -Uvh
+	    kernel-<replaceable>version</replaceable>.src.rpm</command>.
+	</para>
+	<para>
+          Questo scriver?? i contenuti dell'RPM in
 	  <filename>/usr/src/redhat/SOURCES</filename> e
 	  <filename>/usr/src/redhat/SPECS</filename>.
         </para>
       </step>
       <step>
-        <para>
-          Prepara i sorgenti del kernel usando i comandi:
-        </para>
-<screen width="56">
-<command>cd <filename>/usr/src/redhat/SPECS</filename></command>
-<command>rpmbuild <parameter class="option">-bp --target $(arch)</parameter> <filename>kernel-2.6.spec</filename></command>
+        <para>Prepara i sorgenti del kernel usando i comandi:
+	</para>
+<screen>
+<command>cd /usr/src/redhat/SPECS
+rpmbuild -bp --target $(arch) kernel-2.6.spec</command>
 </screen>
         <para>
           L'albero dei sorgenti del kernel ?? locato nella directory
-	  <filename>/usr/src/redhat/BUILD/kernel-</filename><replaceable>version</replaceable>.
-	  E' pratica comune muovere le risultanti directory
+	  <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable>/</filename>.
+	  E' pratica comune spostare le risultanti directory
 	  <filename>linux-<replaceable>version</replaceable></filename>
 	  nell'albero <filename>/usr/src</filename>; anche se non ??
-	  strettamente necessario, cos?? facendo lo farai coincidere con quanto riportato nella
+	  strettamente necessario, puoi fare cos?? per coincidere con quanto riportato nella
 	  documentazione generica.
         </para>
-<screen width="56">
-<command>cd <filename>/usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
-<command>mv <filename>linux-<replaceable>version</replaceable></filename> <filename>/usr/src/</filename></command>
-<command>cd <filename>/usr/src</filename></command>
-<command>ln <parameter class="option">-s</parameter> <filename>./linux-<replaceable>version</replaceable></filename> <filename>linux</filename></command>
-<command>cd <filename>/usr/src/linux</filename></command>
+<screen>
+<command>cd /usr/src/redhat/BUILD/kernel-<replaceable>version</replaceable>
+mv linux-<replaceable>version</replaceable> /usr/src/
+cd /usr/src\
+ln -s ./linux-<replaceable>version</replaceable> linux
+cd /usr/src/linux</command>
 </screen>
       </step>
       <step>
         <para>
-          Le configurazioni per i kernel specifici distribuiti con
-	  &DISTRO; &DISTROVER; sono nella directory <filename>configs/</filename>.
-	  Per esempio, il file di configurazione i686 SMP
-	  ?? nominato
+	  Le configurazioni per i kernel specifici distribuiti in &FC;
+	  sono nella directory <filename>configs/</filename>.
+	  Per esempio, il file di configurazione i686 SMP ?? denominato
 	  <filename>configs/kernel-<replaceable>version</replaceable>-i686-smp.config</filename>. 
 	  Lancia il seguente comando per porre il file di configurazione desiderato
-	  nel posto giusto per la compilazione:
+	  nel posto giusto per la compilazione:<command>cp
+	    configs/<replaceable>desired-config-file</replaceable>
+	    .config</command>
         </para>
-<screen width="56">
-<command>cp <filename>configs/<replaceable>desired-config-file</replaceable></filename> <filename>.config</filename></command>
-</screen>
         <para>
           Puoi trovare inoltre il file <filename>.config</filename> che combacia
 	  la tua configurazione attuale del kernel nel file
-	  <filename>/lib/modules/</filename><replaceable>version</replaceable><filename>/build/.config</filename>.
+	  <filename>/lib/modules/<replaceable>version</replaceable>/build/.config</filename>
+	  .
         </para>
       </step>
       <step>
         <para>
           Ogni kernel ha un nome basato sul numero della sua versione. Questo ??
-	  il valore che mostra il comando <command>uname -r</command>.
-	  Il nome del kernel ?? definito dalle prime quattro linee del
-	  kernel <filename>Makefile</filename>. Per proteggere gli inconsapevoli,
-	  il <filename>Makefile</filename> ?? stato cambiato per generare
-	  un kernel con un nome differente da quello in esecuzione.
-	  Prima che un modulo possa essere accettato dal kernel in esecuzione,
-	  quel modulo deve essere compilato per un kernel con il nome
-	  corretto.  Per fare questo, devi editare il kernel
-	  <filename>Makefile</filename>.
-        </para>
-        <para>
-          Per esempio, se con <command>uname -r</command> restituir?? la
-	  stringa <systemitem
-	    class="osname">2.6.11-1.234_FC4</systemitem>, cambia la definizione
-	  <systemitem class="macro">EXTRAVERSION</systemitem>
-	  da questo:
-        </para>
-<screen width="60">
+	  il valore mostrato dal comando <command>uname
+	    -r</command>. Il nome del kernel ?? definito dalle prime quattro linee del
+	  kernel Makefile. Per proteggere dagli errori,
+	  il Makefile ?? stato cambiato per generare
+	  un kernel con un nome differente da quello in esecuzione. Prima che
+	  un modulo possa essere accettato dal kernel in esecuzione, quel modulo deve
+	  essere compilato per un kernel con il nome corretto.  Per fare
+	  questo, devi editare il kernel Makefile.
+        </para>
+    <para>Per esempio, se <command>uname -r</command> restituisce la stringa
+      <computeroutput>2.6.11-1.234_FC4</computeroutput>, cambia la definizione
+      <envar>EXTRAVERSION</envar> da questo:
+    </para>
+<screen>
 EXTRAVERSION = -prep
 </screen>
-        <para>
+	<para>
 	  a questo:
 	</para>
-<screen width="60">
+<screen>
 EXTRAVERSION = -1.234_FC4
 </screen>
-        <para>
-          E cos?? via, sostituite ogni cosa dall'inizio alla fine.
+	<para>Questo rappresenta ogni cosa dall'inizio alla fine nel nome
+	  del pacchetto.
         </para>
       </step>
       <step>
         <para>
           Impartite il seguente comando:
         </para>
-<screen width="56">
+<screen>
 <command>make oldconfig</command>
 </screen>
-      </step>
+	<para>Quindi potrai procedere come al solito.</para></step>
     </procedure>
-    <para>
-      Quindi potrai procedere come al solito.
-    </para>
   </section>
-  <section id="sn-kernel-3rdparty">
+  <section id="sn-kernel-modules-building">
     <title>Compilare solo i moduli del Kernel</title>
     <para>
-      <emphasis>Non</emphasis> ?? necessario un albero dei sorgenti esploso per
-      compilare un modulo del kernel, tipo il tuo driver di periferica, per il
-      kernel in uso.
-    </para>
-    <para>
-      Per esempio, per compilare il modulo <filename>foo.ko</filename>,
+      Non ?? necessario un albero dei sorgenti esploso per compilare un modulo del kernel,
+      tipo il tuo driver di periferica, per il kernel in
+      uso. Per esempio, per compilare il modulo <filename>foo.ko</filename>,
       create il seguente <filename>Makefile</filename> nella
       directory contenente il file <filename>foo.c</filename>:
     </para>
-<programlisting width="56">
+<screen>
 obj-m := foo.o
 
 KDIR  := /lib/modules/$(shell uname -r)/build
 PWD   := $(shell pwd)
 
-default:
-    $(MAKE) -C $(KDIR) M=$(PWD) modules
-</programlisting>
-      <para>
-      Impartite il comando <command>make</command> per creare
+ndefault:
+      $(MAKE) -C $(KDIR) M=$(PWD) modules
+</screen>
+    <para>Impartite il comando <command>make</command> per compilare
       il modulo <filename>foo.ko</filename>.
-    </para>
+</para>
   </section>
-  <section id="sn-kernel-coop">
+  <section id="kernel-user-space-depencies">
     <title>Dipendenze User Space sul Kernel</title>
     <para>
-      &DISTRO; aggiunge supporto per i sistemi cluster. Ci?? richiede un
-      kernel speciale che funzioni in congiunzione con alcune utilit?? 
-      user-space, tipo i demoni di amministrazione. Di conseguenza, per rimuovere
-      un simile kernel, ad esempio dopo un aggiornamento,
-      <emphasis>non puoi</emphasis> semplicemente usare il comando <command>rpm -e
+      &FC; &LOCALVER; aggiunge supporto per i sistemi di storage cluster mediante il Red
+      Hat GFS file system. Ci?? richiede un kernel speciale che funzioni
+      in congiunzione con alcune utilit?? user-space, tipo i demoni di
+      amministrazione. Di conseguenza, per rimuovere un simile kernel, ad esempio dopo un
+      aggiornamento, non puoi semplicemente usare il comando <command>rpm -e
 	kernel-<replaceable>version</replaceable></command> come
       nelle precedenti distribuzioni poich?? questi pacchetti in user space
-      dipendono dal pacchetto del kernel. Potresti elencare sia il pacchetto kernel
-      ed i suoi pacchetti user space dependenti al comando <command>rpm
-	-e</command>, oppure invece potresti usare il comando <command>yum
-	remove kernel-<replaceable>version</replaceable></command>,
+      dipendono dal pacchetto del kernel.
+    </para>
+    <para>
+      Potresti elencare sia il pacchetto kernel ed i suoi pacchetti user space
+      dependenti al comando <command>rpm -e</command>, oppure
+      invece potresti usare il comando <command>yum remove
+	kernel-<replaceable>version</replaceable></command>,
       e <command>yum</command> rimuover?? automaticamente
       i pacchetti dependenti se necessario.
     </para>


Index: legacy-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/legacy-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legacy-it.xml	4 Nov 2005 19:56:57 -0000	1.1
+++ legacy-it.xml	25 Nov 2005 21:12:13 -0000	1.2
@@ -1,3 +1,50 @@
+<section id="sn-legacy">
+    <title>Informazioni legacy</title>
+    
+  <note>
+    <title><command>Slocate</command> ?? stato sostituito da
+    <command>mlocate</command> in questa release.</title>
+    <para>
+      L'implementazione <command>/usr/bin/{locate,updatedb}</command>
+      <command>slocate</command> ?? stata sostituita da mlocate.
+    </para>
+  </note>
+    <itemizedlist>
+      <listitem>
+      <para>Il comando <command>locate</command> dovrebbe essere completamente
+      compatibile.
+      </para>
+      </listitem>
+    </itemizedlist>
+    <itemizedlist>
+      <listitem>
+      <para><filename>/etc/updatedb.conf</filename> ?? compatibile per correggere
+	i files di configurazione
+      </para>
+    </listitem>.
+    <listitem>
+      <para>Gli errori di sintassi che <command>slocate</command> non potr??
+	determinare saranno segnalati.
+      </para>
+    </listitem>
+    <listitem>
+      <para>La variabile <envar>DAILY_UPDATE</envar> non ??
+	supportata.
+      </para>
+    </listitem>
+    <listitem>
+      <para>Il comando <command>updatedb</command> non ?? compatibile, gli scripts
+	proprietari che usano <command>updatedb</command> dovranno essere
+	cambiati.
+      </para>
+      </listitem>
+    </itemizedlist>
+  <para>
+    La LinuxThreads library, che ?? stta deprecata in &FC; 4, non ?? pi??
+    disponibile in questa release. NPTL threading library ?? la libreria
+    predefinita fin da Red Hat Linux 9.
+  </para>
+</section>
 <!--
 Local variables:
 mode: xml


Index: multimedia-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/multimedia-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- multimedia-it.xml	4 Nov 2005 19:56:57 -0000	1.1
+++ multimedia-it.xml	25 Nov 2005 21:12:13 -0000	1.2
@@ -65,26 +65,22 @@
     </varlistentry>
   </variablelist>
   <section id="sn-multimedia-excluded">
-	  <title>Software multimediale escluso</title>
+    <title>Software multimediale escluso</title>
     <para>
       Diversi programmi sono esclusi da &FC; e &FEX; a cusa di problemi di
       licenza.  Queso include programmi che forniscono supporto MP3 e DVD,
-      Flash Player e Real Player.  Gli utenti che desiderano usare questi
-      programmi o formati ristretti devono acquisire pacchetti aggiuntivi
-      dai loro rispettivi repositori.  Molte delle applicazioni
-      multimediali nei repositorie Fedora supportano i plugins, cos??
-      il supporto per nuovi formati pu?? essere facilmente aggiunto o rimosso.
-      Per maggiori informazioni su questo soggetto, siete pregati di vedere:
+      Flash Player e Real Player. Per maggiori informazioni su questo soggetto,
+      riferitevi a:
     </para>
     <para>
       <ulink url='http://fedoraproject.org/wiki/ForbiddenItems'>http://fedoraproject.org/wiki/ForbiddenItems</ulink>
     </para>
   </section>
   <section id="sn-multimedia-cd-dvd-burning">
-    <title>CD e DVD Authoring e Burning</title>
+    <title>CD e DVD Authoring e masterizzazione</title>
     <para>
       Strumenti per masterizzare facilmente CDs e DVDs sono inclusi in &FC; e &FEX;.
-      Gli strumenti possono essere usati dalla console
+      Gli strumenti che possono essere usati dalla console
       includono <command>cdrecord</command>, <command>readcd</command>,
       <command>mkisofs</command>, ed altre tipiche applicazioni Linux.
       Per gli utenti GNOME, il pacchetto <filename>xcdroast</filename> da


Index: overview-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/overview-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- overview-it.xml	5 Nov 2005 12:07:20 -0000	1.2
+++ overview-it.xml	25 Nov 2005 21:12:13 -0000	1.3
@@ -1,12 +1,5 @@
 <section id="sn-overview">
   <title>Descrizione di questa release</title>
-  <caution>
-    <title>Informazioni non aggiornate</title>
-    <para>
-      Il contenuto in questa seczione deve essere aggiornato per &DISTRO;
-      &DISTROVER;
-    </para>
-  </caution>
 <!--
   <para>
     Il seguente elenco include un breve sommario di alcune dei pi??


Index: package-movement-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-movement-it.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- package-movement-it.xml	6 Nov 2005 22:32:25 -0000	1.4
+++ package-movement-it.xml	25 Nov 2005 21:12:13 -0000	1.5
@@ -2,8 +2,8 @@
   <title>Movimenti dei pacchetti</title>
   <!-- 
   FIXME
-  Necessita dell'aggiornamento dell'intero contenuto di FC4.
-  -->
+  Necessita dell'aggiornamento dell'intero contenuto di FC5.
+
   <para>
     Questo comando ?? stato usato per generare la lista dei pacchetti modificati.  Lo
     backslash <computeroutput>\</computeroutput> ?? usato per interrompere
@@ -932,6 +932,7 @@
     <para>[111033] ncpfs-2.2.4-8 -> [115462] ncpfs-2.2.4-9 </para>
     <para>[106079] prelink-0.3.4-3 -> [117615] prelink-0.3.6-1 </para>
     <para>[110767] netpbm-10.27-3 -> [116518] netpbm-10.29-1 </para>
+-->
     <section id="sn-packages-added">
       <title>Pacchetti aggiunti</title>
       <para>
@@ -1055,13 +1056,11 @@
     </para>
 <!-- FIXME
     <para>
-      Gbenson ?? daccordo nel giustificare qualsuasi inclusione di pacchetti Java in
-      FC5. Spedisci un e-mail. Questa info potrebbe essere inclusa prima del rilascio della release test1
+      Gbenson agreed to justify any inclusion of Java packages in
+      FC5. Send a mail. Should include this info before test1 release
     </para>
 -->
   </section>
-
-</section>
 <!--
 Local variables:
 mode: xml


Index: package-notes-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-it.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- package-notes-it.xml	5 Nov 2005 17:47:06 -0000	1.3
+++ package-notes-it.xml	25 Nov 2005 21:12:13 -0000	1.4
@@ -37,13 +37,6 @@
     un accesso facilitato, sono in linea generale organizzati usando gli stessi gruppi
     usati in Anaconda.
   </para>
-  <caution>
-    <title>Informazioni non aggiornate</title>
-    <para>
-      Il contenuto di questa sezione necessita di essere aggiornato per &DISTRO;
-      &DISTROVER;
-    </para>
-  </caution>
   <section id="sn-basic-components">
     <title>Componenti di base</title>
     <para>
@@ -81,21 +74,22 @@
       </para>
     </section>
     <section id="sn-audit-daemon">
-      <title>Il demone di audit <command>auditd</command> ed i files di log</title>
+      <title>Il demone di audit <command>auditd</command> ed i files
+        di log</title>
       <para>
 	Il demone audit, auditd, ?? abilitato per impostazione predefinita. Quando
-	auditd ?? in esecuzione, il kernel direziona i messagi a
-	<filename>/var/log/audit/audit.log</filename>.  La locazione di questo file ??
+	auditd ?? in esecuzione, il kernel redireziona i messagi a
+	<filename>/var/log/audit/audit.log</filename>.  La posiozione di questo file ??
 	specificata in <filename>/etc/auditd.conf</filename>.
       </para>
       <para>
-	I messaggi AVC per &SEL; sono spediti usando l'infrastruttura audit.
+	I messaggi AVC per &SEL; sono inviati usando l'infrastruttura audit.
 	Questi messaggi sono adesso in
 	<filename>/var/log/audit/audit.log</filename>.
       </para>
       <para>
-	Quando auditd non ?? in esecuzione, il kernel passa i messaggi di audit a
-	syslog.  Questi logs sono tipicamente tenuti in <filename>/var/log/messages</filename> e
+	Quando auditd non ?? in esecuzione, il kernel passa i messaggi audit a
+	syslog.  Questi logs sono tipicamente contenuti in <filename>/var/log/messages</filename> e
 	sono visibili usando <command>dmesg</command>.
       </para>
       <para>
@@ -113,6 +107,7 @@
 <command>auditctl -e 1</command>
 </screen>
     </section>
+<!--
     <section id="sn-nptl">
       <title>LinuxThreads contro NPTL</title>
       <para>
@@ -177,6 +172,7 @@
 	In generale, la conversione all'uso di NPTL non ?? stata un problema.
       </para>
     </section>
+    -->
     <section>
       <title>Abilitare il database <filename>slocate</filename></title>
       <para>
@@ -214,8 +210,9 @@
 	In pi??, OpenSSH non ?? pi?? configurato per impostazione predefinita,
 	per richiedere l'X11 forwarding quando ci si connette ai servers.
 	Per abilitare l'X11 forwarding, l'opzione <option>-X</option> o
-	<option>-Y</option> deve essere specificata, o l'opzione
-	<option>ForwardX11</option> deve essere abilitata nel file <filename>~/.ssh/config</filename>.
+	<option>-Y</option> deve essere specificate, o l'opzione
+	<option>ForwardX11</option> deve essere abilitata nel file
+	<filename>~/.ssh/config</filename>.
       </para>
       <para>
 	Il comportamento dei clients <command>ssh</command> che sono stati invocati
@@ -223,46 +220,23 @@
 	e superiori, l'X11 forwarding ?? eseguito in modo che, per impostazione predefinita,
 	le applicazioni siano eseguite come clients privi di credenziali (untrusted).
 	Precedentemente, l'X11 forwarding era effettuato in modo tale che le applicazioni
-	fossero eseguite sempre come clients verificati.
-	Alcune applicazioni potrebbero non funzionare correttamente se eseguite
-	come client non verificati.
-	Per eseguire l'X11 forwarding affinch?? le applicazioni siano eseguite come
-	clients verificati, invocate ssh con l'opzione
-	<option>-Y</option> invece che l'opzione <option>-X</option>,
+	fossero eseguite sempre come clients verificati. Alcune applicazioni potrebbero non
+	funzionare correttamente se eseguite come client non verificati. Per eseguire l'X11
+	forwarding affinch?? le applicazioni siano eseguite come clients verificati, invocate ssh con
+	l'opzione <option>-Y</option> invece che l'opzione <option>-X</option>,
 	o impostate <option>ForwardX11Trusted</option> nel file
 	<option>~/.ssh/config</option>.
       </para>
     </section>
-    <section id="sn-perl">
-      <title>I symlinks Perl Binary Compat</title>
-      <para>
-	I symlinks binary compat per <filename>perl-5.8.0</filename>,
-	<filename>perl-5.8.1</filename>, e
-	<filename>perl-5.8.2</filename> sono stati rimossi.  Se hai moduli perl
-	creati con queste vecchie versioni di perl, dovrai
-	ricompilarli usando il <filename>perl-5.8.6</filename> contenuto
-	in &FC; &LOCALVER;.
-      </para>
-    </section>
-    &SERVER-TOOLS;
+<!--    &SERVER-TOOLS; -->
     &JAVA-PACKAGE;
   </section>
   <section id="sn-packages-core">
     <title>Core</title>
     <para>
-      Questa sezione contiene le componenti pi?? elementari di &DISTRO;,
+      Questa sezione contiene i componenti pi?? elementari di &DISTRO;,
       incluso il kernel.
     </para>
-    <section>
-      <title>yum</title>
-      <para>
-	Il database sqllite ?? ora utilizzato da yum, e rende le prestazioni
-	notevolmente pi?? veloci.
-      </para>
-      <para>
-	Il repositorio Fedora Extras ?? ora abilitato per impostazione predefinita.
-      </para>
-    </section>
     &KERNEL;
     &SECURITY;
   </section>
@@ -272,7 +246,6 @@
 <!--  no content for this release
   &DATABASE-SERVERS; -->
   &MULTIMEDIA;
-  &ENTERTAINMENT;
   &WEB-SERVERS;
   &SAMBA;
   &XORG;


Index: project-overview-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/project-overview-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- project-overview-it.xml	6 Nov 2005 01:23:15 -0000	1.2
+++ project-overview-it.xml	25 Nov 2005 21:12:13 -0000	1.3
@@ -20,7 +20,8 @@
 	url="http://fedora.redhat.com/">http://fedora.redhat.com/</ulink>
     </para>
     <para>
-      In aggiunta al sito, sono disponibili le seguenti mailing lists:
+      In aggiunta al sito, sono disponibili le seguenti
+      mailing lists:
     </para>
     <itemizedlist>
       <listitem>
@@ -30,7 +31,8 @@
       </listitem>
       <listitem>
         <para>
-	  fedora-test-list at redhat.com &mdash; Per i testers delle test releases di &DISTRO;
+	  fedora-test-list at redhat.com &mdash; Per i testers delle test
+	  releases di &DISTRO;
 	</para>
       </listitem>
       <listitem>
@@ -41,33 +43,42 @@
       </listitem>
       <listitem>
         <para>
-	  fedora-docs-list at redhat.com &mdash; Per i partecipanti al Documentation Project
+	  fedora-docs-list at redhat.com &mdash; Per i partecipanti al
+	  Documentation Project
 	</para>
       </listitem>
-    </itemizedlist>
-    <para>
-      Per sottoscrivere ad una di queste liste, spedisci un email con la parola
-      "subscribe" nel soggetto a
-      <computeroutput><replaceable>&lt;listname&gt;</replaceable>-request</computeroutput>
-      (dove
-      <computeroutput><replaceable>&lt;listname&gt;</replaceable></computeroutput>
-      ?? una delle sopraelencate liste.)
-    </para>
-    <para>
-      Alternativamente, puoi sottoscriverti mediante l'interfaccia Web:
-    </para>
-    <para>
-      <ulink url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
-    </para>
+    <listitem>
+      <para>
+	fedora-ambassadors-list at redhat.com &mdash; Per i componenti
+	della comunit?? che rappresentano il &PROJ; in pubblico.
+      </para>
+    </listitem>
+  </itemizedlist>
+  <para>
+    Per sottoscrivere ad una di queste liste, spedisci un email con la parola
+    "subscribe" nel soggetto a
+    <computeroutput><replaceable>&lt;listname&gt;</replaceable>-request</computeroutput>
+    (dove
+    <computeroutput><replaceable>&lt;listname&gt;</replaceable></computeroutput>
+    ?? una delle sopraelencate liste.)
+  </para>
+  <para>
+    Alternativamente, puoi sottoscriverti mediante l'interfaccia Web:
+  </para>
+  <para>
+    <ulink url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
+  </para>
+  <!-- Aren't we quite past this?  Saving just in case we are not.
     <para>
       Se sei stato sottoscritto in passato alle rhl-list, rhl-beta-list,
       rhl-devel-list, o rhl-docs-list, le tue sottoscrizioni saranno
       mantenute.
     </para>
+  -->
     <para>
       Il &PROJ; include anche un canale IRC (Internet Relay Chat).  IRC ?? una
       forma di comunicazione real-time, basata su testo.  Con essa, puoi avere
-      conversazioni con pi?? persone contemporaneamente in un canale aqperto o
+      conversazioni con pi?? persone contemporaneamente in un canale aperto o
       chattare privatamente con qualcuno uno-a-uno.
     </para>
     <para>
@@ -91,7 +102,8 @@
     <note>
       <title>Nota</title>
       <para>
-	&RH; non ha controllo sui canali IRC di &PROJ; o i loro contenuti.
+	&RH; non ha controllo sui canali IRC di &PROJ; o i loro
+	contenuti.
       </para>
     </note>
   </section>


Index: RELEASE-NOTES-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-it.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- RELEASE-NOTES-it.xml	19 Nov 2005 21:05:38 -0000	1.3
+++ RELEASE-NOTES-it.xml	25 Nov 2005 21:12:13 -0000	1.4
@@ -34,7 +34,7 @@
 
 
 <!-- *************** COMMON FDP entities *************** -->
-<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-it.ent">
+ <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-it.ent">
  %FEDORA-ENTITIES-EN;
  <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-it.xml">
 
@@ -55,7 +55,7 @@
 
 <article id="index" lang="it" arch="x86;x86_64;ppc" os="test;final">
   <articleinfo>
-    <title>Note di rilascio per &DISTRO; &DISTROVER;</title>
+    <title>(Ultime) Note di rilascio per &DISTRO; &DISTROVER;</title>
     <copyright>
       <year>2005</year>
       <holder>&FORMAL-RHI;</holder>


Index: security-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/security-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- security-it.xml	4 Nov 2005 19:59:37 -0000	1.1
+++ security-it.xml	25 Nov 2005 21:12:13 -0000	1.2
@@ -4,35 +4,80 @@
     Questa sezione evidenzia varie questioni di sicurezza da &FC;.
   </para>
   <para>
-    <computeroutput>Pam_stack</computeroutput> ?? deprecato. Maggiori
-    dettagli sono disponibili dalla fedora-test-list (<ulink
-    url="http://www.redhat.com/mailman/listinfo/fedora-test-list">http://www.redhat.com/mailman/listinfo/fedora-test-list</ulink>
+    <computeroutput>Pam_stack</computeroutput> ?? deprecato. Linux-PAM
+    0.78 e successivi contengono la direttiva che include e rende obsoleto il
+    modulo <computeroutput>pam_stack</computeroutput>.
+    L'uso del modulo <computeroutput>pam_stack</computeroutput> ?? loggato
+    con un messaggio d'avvertimento di disapprovazione.  Potrebbe essere rimosso in una versione
+    futura.
   </para>
   <section id="sn-security-highlights">
     <title>Novit?? sulla sicurezza</title>
     <para>
       Questa sezione evidenzia varie questioni di sicurezza da &FC;.
     </para>
-    <para>
-      I certificati digitali sono ora centralizzati in directories
-      sotto <filename>/etc/pki/</filename>. Gli utenti che eseguono un aggiornamento devono
-      rilocare i propri certificati digitali.
-    </para>
-    <para>
-      OpenSSL: i contenuti di <filename>/usr/share/ssl/</filename> sono stati
-      sossi su <filename>/etc/pki/tls/</filename> e
-      <filename>/etc/pki/CA/</filename>.
-    </para>
-    <para>
-      Dovecot: Un file dovecot-openssl.cnf ?? automaticamente installato in
-      <filename>/etc/pki/dovecot/</filename>.
-    </para>
+    <variablelist>
+      <varlistentry>
+	<term>Determinazione dei buffer overflow e riordino delle variabili</term>
+	<listitem>
+	  <para>Per questa release, tutti i software nei repositori di &FC; e
+	    &FEX; sono compilati usando una caratteristica di sicurezza
+	    chiamata <firstterm>fstack-protector</firstterm>.
+	    fstack-protector pone un canary value sullo stack delle
+	    funzioni <computeroutput>key</computeroutput>.  Appena prima
+	    dell'indirizzo di restituzione ed appena prima di essere restituito da quel
+	    valore, il canary value viene verificato.  Se si verifica un buffer
+	    overflow, il canary value non combacia pi?? ed il programma
+	    abortisce. Il canary value ?? randomico ogni volta che
+	    l'applicazione ?? avviata divenendo impossibile da indovinare
+	    remotamente. Questa ?? una caratteristica di sicurezza che ?? stata
+	    riportata da GCC 4.1 alla versione del compilatore GCC
+	    usato in &FC; &LOCALVER;. 
+	  </para>
+	  <para>
+	    Questa ?? un aggiunta per utilizzare <envar>FORTIFY_SOURCE</envar>
+	    dala &FC; 4 in poi.
+	  </para>
+	</listitem>
+      </varlistentry>
+      
+      <varlistentry>
+	<term>I certificati digitali</term>
+	<listitem>
+	  <para>
+            I certificati digitali sono ora centralizzati in directories
+            sotto <filename>/etc/pki/</filename>. Gli utenti che eseguono un aggiornamento devono
+            rilocare i propri certificati digitali.
+	  </para>
+	</listitem>
+      </varlistentry>
+      <varlistentry>
+	<term>OpenSSL</term>
+	<listitem>
+	  <para>
+            Per OpenSSL i contenuti di <filename>/usr/share/ssl/</filename>
+	    sono stati spostati in <filename>/etc/pki/tls/</filename>
+	    e <filename>/etc/pki/CA/</filename>.
+	  </para>        
+	</listitem>
+      </varlistentry>
+      <varlistentry>
+	<term>Dovecot</term>
+	<listitem>
+	  <para>
+            Il file <filename>dovecot-openssl.cnf</filename> ??
+	    automaticamente installato automaticamente in
+	    <filename>/etc/pki/dovecot/</filename>.
+	  </para>
+	</listitem>  
+      </varlistentry>
+    </variablelist>
   </section>
   <section id="sn-security-selinux-changes">
     <title>Cambiamenti su SELinux</title>
     <para>
-      MCS SELinux ?? dentro. Maggiori novit??.  Per maggiori
-      informazioni, leggete questo articolo informativo:
+      Mult-Category Security (MCS) SELinux ?? incluso in &FC;
+      &LOCALVER;. Per maggiori informazioni, leggete questo articolo informativo:
     </para>
     <para>
       <ulink


Index: splash-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- splash-it.xml	6 Nov 2005 09:05:30 -0000	1.2
+++ splash-it.xml	25 Nov 2005 21:12:13 -0000	1.3
@@ -1,18 +1,33 @@
 <section id="sn-splash">
   <title>Benvenuti in &FC; &LOCALVER;</title>
-  <caution>
-    <title>Informazioni non aggiornate</title>
-    <para>
-      Il contenuto in questa sezione deve essere aggiornato per &DISTRO;
-      &DISTROVER;
-    </para>
-  </caution>
   <para>
     &FC; ?? una piattaforma basata su Linux completamente gratutita, amichevole, sicura e
-    general purpose.  &FP; ?? un progetto open source che
+    general purpose.  &FP; ?? un progetto open source che ?? utilizzabile, modificabile e distribuibile
+    liberamente da chiunque, ora e per sempre.  Il &FP; ?? un progetto open source che 
     esplora le ultime tecnologie e concetti sponsorizzato da &RH; e
     supportato dalla comunit?? &FED;.
   </para>
+  <caution>
+    <title>Questa ?? una test release, non intesa per gli utenti finali</title>
+    <para>
+      Questa ?? una test release ed ?? distribuita per gli sviluppatori e testers
+      per partecipare e fornire giudizzi. Non ?? intesa per gli
+      utenti finali.
+    </para>
+    <para>
+      Sottoscrivi le mailing lists <ulink url="https://www.redhat.com/mailman/listinfo/fedora-test-list/">fedora-test</ulink> e <ulink url="https://www.redhat.com/mailman/listinfo/fedora-devel-list">fedora-devel</ulink> per tenere traccia
+      dei cambiamenti pi?? importanti nella versione di sviluppo attuale
+      e dare il tuo giudizio agli sviluppatori. &FP; ha bisogno che tu
+      invii i rapporti d'errore e le migliorie per dare all'utente finale una migliore
+      versione definitva. Per maggiori informazioni su questo, fa riferimento al
+      seguente documento:
+    </para>
+    <para>
+      <ulink
+	url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'>http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink>. 
+      
+    </para>
+  </caution>
   <tip>
     <title>Ultime Release Notes sul Web</title>
     <para>
@@ -39,16 +54,19 @@
     Fa riferimento a queste pagine web per cercare maggiori informazioni su &FED;:
   </para>
   <itemizedlist>
-<!-- FIXME Return when the section is updated
     <listitem>
       <para>
 	<xref linkend="sn-new-in-fc"/>
       </para>
     </listitem>
--->
     <listitem>
       <para>
-	      <xref linkend="sn-intro"/> &mdash; Release notes tecniche
+	<xref linkend="sn-intro"/> &mdash; Release notes tecniche
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+	<ulink url="http://fedoraproject.org/wiki/FAQ/">Fedora FAQ</ulink>
       </para>
     </listitem>
     <listitem>
@@ -70,6 +88,67 @@
       </para>
     </listitem>
   </itemizedlist>
+  <section id="sn-new-in-fc">
+    <title>Che c'?? di nuovo in &FC; &LOCALVER;</title>
+    <itemizedlist>
+      <listitem>
+        <para>Il software di virtualizzazione Xen ed lo strumento di amministrazione dei
+	  pacchetti yum sono ora ben integrati all'interno del proramma di installazione &FED;.
+	  L'interfaccia del programma d'installazione ?? molto sequenziale.  Il login remoto ed
+	  il supporto per i tracebacks ?? incluso.
+	</para>
+      </listitem>
+      <listitem>
+        <para><application>Pup</application>, ?? un updater grafico che usa
+	  yum, e sostituisce la <application>rhn-applet</application>.
+	</para>
+      </listitem>
+      <listitem>
+        <para>Sono disponibili gli ambienti desktop GNOME 2.12 e
+	KDE 3.4.
+	</para>
+      </listitem>
+      <listitem>
+        <para>GNOME Power Manager e GNOME Screensaver sono disponibili come
+	  anteprima tecnologica in questa release.
+	</para>
+      </listitem>
+      <listitem>
+        <para>
+          OpenOffice.org 2.0 final release ?? incluso. OpenOffice.org
+	  adesso usa versioni di sistema per molte delle librerie raggiungendo
+	  maggiori prestazioni ed efficienza.
+	</para>
+      </listitem>
+      <listitem>
+        <para>Xorg X11R7 release candidate 2 ?? stato incluso in questa
+	  release.  Questa ?? la prima versione modulare, che aiuta nel fornire caratteristiche
+	  aggiuntive e risoluzione degli errori ad un passo pi?? spedito.
+	</para>
+      </listitem>
+      <listitem>
+        <para>Il Kernel 2.6.14 ?? incluso. In questa versione ?? stata abilitata la
+        sospensione software.
+	</para>
+      </listitem>
+      <listitem>
+        <para>SCIM ha sostituito IIMF in &FC; in questa release.
+	</para>
+      </listitem>
+      <listitem>
+	<para>Ci sono cambiamenti nel tema animato del cursore del mouse.
+	</para>
+      </listitem>
+      <listitem>
+        <para>&FP; adesso ha un nuovo logo.
+	</para>
+      </listitem>
+    </itemizedlist>
+    <para>I piani proposti per Fedora in questa versione sono disponibili
+      su <ulink
+	url='http://fedoraproject.org/wiki/RoadMap'>http://fedoraproject.org/wiki/RoadMap</ulink>.
+    </para>
+  </section>
 <!-- commented out until the content can be updated
   <section id="sn-new-in-fc">
     <title>New in &FC; &LOCALVER;</title>


Index: web-servers-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/web-servers-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- web-servers-it.xml	4 Nov 2005 19:59:37 -0000	1.1
+++ web-servers-it.xml	25 Nov 2005 21:12:13 -0000	1.2
@@ -6,7 +6,8 @@
   <section>
     <title><command>httpd</command></title>
     <para>
-      Il seguenti cambiamenti sono stati fatti sulla configurazione predefinita di <command></command>httpd:
+      Il seguenti cambiamenti sono stati fatti sulla configurazione predefinita di
+      <command>httpd</command>:
     </para>
     <itemizedlist>
       <listitem>


Index: xorg-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/xorg-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- xorg-it.xml	6 Nov 2005 09:46:14 -0000	1.2
+++ xorg-it.xml	25 Nov 2005 21:12:13 -0000	1.3
@@ -1,210 +1,158 @@
 <section id="sn-xwindows">
-  <title>Sistema X Window (Grafico)</title>
-  <caution>
-    <title>Informazioni non aggiornate</title>
-    <para>
-      Il contenuto di questa sezione deve essere aggiornato per &DISTRO;
-      &DISTROVER;
-    </para>
-  </caution>
-  <para>
-    Questa sezione contiene le informazioni relative all'implementazione del
-    sistema X Window fornito con &DISTRO;.
-  </para>
-  <section id="sn-xwindows-xorg">
-    <title><filename>xorg-x11</filename></title>
-    <para>
-      Gli utenti che sono nuovi all'implementazione di X.org X11 dovranno prendere nota di
-      poche differenze tra lui e l'implementazione XFree86.org X11
-      che veniva rilasciata nei precedenti sistemi operativi &RH; e &FED;. In
-      particolare, i nomi di alcuni files sono cambiati:
-    </para>
-    <para>
-      Binari X Server:
-    </para>
-    <itemizedlist>
-      <listitem>
-	<para>XFree86 X11: <filename>XFree86</filename></para>
-      </listitem>
-      <listitem>
-	<para>X.org X11: <filename>Xorg</filename></para>
-      </listitem>
-    </itemizedlist>
-    <para>
-      File di configurazione X Server:
-    </para>
-    <itemizedlist>
-      <listitem>
-	<para>XFree86 X11:
-	  <filename>/etc/X11/XF86Config</filename></para>
-      </listitem>
-      <listitem>
-	<para>X.org X11: <filename>/etc/X11/xorg.conf</filename></para>
-      </listitem>
-    </itemizedlist>
-    <para>
-      File di log X Server:
-    </para>
-    <itemizedlist>
-      <listitem>
-	<para>XFree86 X11:
-	  <filename>/var/log/XFree86.<replaceable>$DISPLAY</replaceable>.log</filename></para>
-      </listitem>
-      <listitem>
-	<para>X.org X11:
-	  <filename>/var/log/Xorg.<replaceable>$DISPLAY</replaceable>.log</filename></para>
-      </listitem>
-    </itemizedlist>
-    <para>
-      Quando configuri o risolvi le problematiche della configurazione
-      del tuo X server, sii sicuro di usare i files giusti.
-    </para>
-    <para>
-      C'?? stata un po di confusione reguardante le problematiche inerenti i font
-      sotto il sistema X Window nelle recenti versioni di &DISTRO; (e
-      versioni di &RHL; prima di lui.)  Oggi, ci sono due
-      subsistemi di font, ciascuno con caratteristiche differenti:
-    </para>
-    <itemizedlist>
-      <listitem>
-	<para>Il subsistema originale (vecchio pi?? di 15 anni) fa riferimento al
-	  <firstterm>sottosistema core X font</firstterm>.  I fonts
-	  renderizzati da questo sottosistema non sono anti-aliased, sono manipolati
-	  dall'X server, ed hanno nomi tipo:
-	  <computeroutput>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</computeroutput>
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Il nuovo subsistema di font ?? conosciuto come
-	  <firstterm>fontconfig</firstterm>, e permette alle applicazioni
-	  accesso diretto ai files dei font.  Fontconfig ?? spesso usato
-	  insieme alla libreria <filename>Xft</filename>, che permette
-	  alle applicazioni di renderizzare le fonti fontconfig sullo schermo con
-	  l'antialiasing. Fontconfig usa dei nomi pi?? amichevoli per l'uomo tipo:
-	  <computeroutput>Luxi Sans-10</computeroutput>
-	</para>
-      </listitem>
-    </itemizedlist>
-    <para>
-      Nel tempo, fontconfig e <filename>Xft</filename> sostituiranno
-      il subsistema core X font.  Attualmente, le applicazioni
-      che usano i toolkits Qt 3 o GTK 2 (che includono le applicazioni KDE e
-      GNOME) usano il subsistema di font fontconfig ed Xft;
-      quasi tutto il resto usa il core X fonts.
-    </para>
-    <para>
-      Nel futuro, &FC; supporter?? solo fontconfig/Xft al
-      posto del XFS font server come impostazione predefinita come metodo per l'accesso
-      ai font locali.
-    </para>
-    <note>
-      <title>Nota</title>
+  <title>Il sistema X Window (Grafico)</title>
+  <section>
+    <title>Il sistema X Window (Grafico)</title>
+    <para>Questa sezione contiene le informazioni relative all'implementazione del
+      sistema X Window distribuita con &FED;.
+    </para>
+    <section id="sn-xorg-x11">
+      <title>xorg-x11</title>
+      <para>X.org X11 ?? un implementazione open source del sistema
+	X Window. Fornisce quelle elementari funzionalit?? di basso livello sulle
+	quali sbandierate interfacce grafiche (GUIs) come GNOME e KDE
+	sono disegnate. </para>
+      <para>Per maggiori informazioni su Xorg fa riferimento a <ulink
+	  url='http://xorg.freedesktop.org/wiki/'>http://xorg.freedesktop.org/wiki/</ulink>
+      </para>
+      <para>Puoi usare
+	<guimenu>Applications</guimenu><guimenuitem>System
+	  Settings</guimenuitem><guimenuitem>Display</guimenuitem> o
+	eseguire <command>system-config-display</command> per configurare le
+	impostazioni. Il file di configurazione per Xorg ?? collocato in
+	<filename>/etc/X11/xorg.conf</filename>.
+      </para>
       <para>
-	Un eccezione al subsistema dei font delineato sopra ??
-	OpenOffice.org, che usa la propria tecnologia di font rendering.
+	Il modulare X.Org X11R7 RC2 ?? stato distribuito con &FED; development
+	(<firstterm>rawhide</firstterm>) il 16 November, 2005. Questa ??
+	la prima release modulare di Xorg. Fra i  vari benefici,
+	Xorg modulare da la possibilit?? agli utenti di ricevere gli aggiornamenti
+	con un passo pi?? veloce, mentre aiuta gli sviluppatori a
+	programmare e rilasciare componenti specifiche in modo pi?? rapido.
       </para>
-    </note>
-    <para>
-      I passi per aggiungere nuove fonti a &DISTRO; &DISTROVER; dipendono dal
-      subsistema che dovr?? usare le nuove fonti.  Per il subsistema core X
-      font:
-    </para>
-
-    <procedure>
-      <step>
-	<para>
-	  Crea la directory <filename>/usr/share/fonts/local/</filename>
-	  (se non esiste gi??):
-	</para>
-<screen>
-<command>mkdir /usr/share/fonts/local/</command>
-</screen>
-      </step>
-      <step>
-	<para>
-	  Copia la nuova fonte in
-	  <filename>/usr/share/fonts/local/</filename>
-	</para>
-      </step>
-      <step>
-	<para>
-	  Aggiorna le informazioni dei font eseguendo i seguenti comandi
-	  (nota che, a causa delle restrizioni sulla formattazione, i seguenti
-	  comandi potrebbero sembrare apparire su pi?? di una linea; quando li usi, ciascun
-	  comando dovr?? essere inserito su una singola linea):
-	</para>
-<screen>
-<command>ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</command>
-<command>mkfontdir /usr/share/fonts/local/</command>
-</screen>
-      </step>
-      <step>
-	<para>
-	  Se hai creato
-	  <filename>/usr/share/fonts/local/</filename>, dovrai quindi
-	  aggiungere il percorso all'X font server (<command>xfs</command>):
-	</para>
-<screen>
-<command>chkfontpath --add /usr/share/fonts/local/</command>
-</screen>
-      </step>
-    </procedure>
-    <para>
-      Aggiungere nuove fonti al subsistema fontconfig ?? pi?? semplice;
-      le nuove fonti hanno necessit?? di essere copiate nella
-      directory <filename>/usr/share/fonts/</filename> (individualmente
-      gli utenti possono modificare la loro configurazione di fornti copiandole nella
-      directory <filename>~/.fonts/</filename>).
-    </para>
-    <para>
-      Dopo che le nuove fonti sono state copiate, usa
-      <command>fc-cache</command> per aggiornare le informazioni della cache:
-    </para>
-<screen>
-<command>fc-cache <replaceable>&lt;directory&gt;</replaceable></command>
-</screen>
-    <para>
-      (Dove
-      <command><replaceable>&lt;directory&gt;</replaceable></command>
-      potr?? essere sia la directory <filename>/usr/share/fonts/</filename> che
-      <filename>~/.fonts/</filename>.)
-    </para>
-    <para>
-      Individualmente gli utenti potranno installare fonts graficamente, navigando
-      <command>fonts:///</command> in
-      <application>Nautilus</application>, e trascinando i nuovi files di font
-      qui.
-    </para>
-    <note>
-      <title>Nota</title>
       <para>
-	Se il nome del file finisce con l'estensione "<filename>.gz</filename>", ??
-	stato compresso con <command>gzip</command>, e deve essere
-	decompresso (con il comando <command>gunzip</command>) prima
-	che il subsistema fontconfig possa usare il font.
+	Maggiori informazioni sullo status attuale dello sforzo di modularizzazione
+	di Xorg in &FED; ?? disponibile su <ulink
+	  url='/Xorg/Modularization'>http://fedoraproject.org/wiki/Xorg/Modularization</ulink>
       </para>
-    </note>      
-    <para>
-      A causa della transizione al nuovo sistema di font basato su
-      fontconfig/Xft, le applicazioni GTK+ 1.2 non possono beneficiare dei
-      cambiamenti fatti mediante la finestra di dialogo <guilabel>Font Preferences</guilabel>.
-      Per queste applicazioni, un font pu?? essere configurato aggiungendo le
-      seguenti linee al file <filename>~/.gtkrc.mine</filename>:
-    </para>
-<screen>    
-<computeroutput>style "user-font" {
-fontset = "<replaceable>&lt;font-specification&gt;</replaceable>"
-}
-widget_class "*" style "user-font"</computeroutput>
-</screen>
-    <para>
-      (Dove
-      <command><replaceable>&lt;font-specification&gt;</replaceable></command> 
-      rappresenta le specifiche della fonte nello stile usato dalle applicazioni X
-      tradizionali, tipo
-      "<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>".)
-    </para>
+    </section>
+    <section id="sn-xorg-x11r7-dev">
+      <title>Note dello sviluppatore di Xorg X11R7</title>
+      <para>X11R7 RC2 ?? incluso in questa release e c'?? un numero
+	di cose di cui gli sviluppatori, e i creatori di pacchetti nei repositori &FED;,
+	devono essere informati per potersi assicurare che i loro
+	software o pacchetti software si compilino in modo appropriato e funzionino con
+	X11R7. Alcuni sono cambiamenti superficiali, mentre altri possono essere pi??
+	coinvolgenti. Qui c'?? un sommario delle cose che possono insorgere e quando
+	possibile, suggerimenti su come risolverle.
+      </para>
+      <section>
+        <title>La gerarchia della directory <filename>/usr/X11R6</filename></title>
+        <para>
+	  X11R7 si installa direttamente in <filename>/usr</filename> ora,
+	  e non usa pi?? la gerarchia <filename>/usr/X11R6</filename>.
+	  Le applicazioni che contano che i files siano presenti nel
+	  percorso fisso sotto <filename>/usr/X11R6</filename> durante la compilazione
+	  o l'esecuzione, devono essere aggiornati o usare il system
+	  <envar>PATH</envar>, o alcuni altri meccanismi, per determinare
+	  dinamicamente dove risiedono i files, o alternativamente inglobare nel codice
+	  i nuovi percorsi, con la possibilit?? di tornare indietro.
+	</para>
+      </section>
+      <section>
+        <title><command>Imake</command></title>
+        <para><command>Imake</command> non ?? pi?? utilizzato per compilare il
+	  sistema X Window, e cos?? ?? ora ufficialmente deprecato.
+	  <command>Imake</command>, <command>xmkmf</command> ed altre
+	  utilities distribuite in precedenza con il sistema X Window, sono
+	  ancora fornite con X11R7, comunque X.Org raccomanda caldamente a
+	  tutti di migrare da Imake per utilizzare GNU autotools e
+	  <filename>pkg-config</filename>. Il supporto per
+	  <command>imake</command> potrebbe scomparire in una futura versione del sistema
+	  X Window, cos?? gli sviluppatori sono fortemente incoraggiati a
+	  starne alla larga, e non usarlo per nessun nuovo
+	  progetto software. 
+	</para>
+      </section>
+      <section>
+        <title>La directory di sistema app-defaults</title>
+        <para>La directory di sistema app-defaults per le risorse X, ?? ora
+	  <filename>%{_datadir}/X11/app-defaults</filename>, che
+	  espande la <filename>/usr/share/X11/app-defaults</filename> su
+	  &FC; &LOCALVER; e per i futuri sistemi &RHEL;. </para>
+      </section>
+      <section id="sn-xorg-xft-config">
+        <title>Non si trova <filename>xft-config</filename></title>
+        <para>X modulare usa ora GNU autotools, e
+	  <command>pkg-config</command> per il suo sistema di compilazione
+	  configurazione, etc. <command>xft-config</command> ?? stato
+	  deprecato per due o tre anni, ed i files
+	  <command>pkgconfig</command> <filename>*.pc</filename> sono
+	  stati distribuiti per la maggior parte di questo tempo. Le applicazioni che
+	  precedentemente usavano <command>xft-config</command> per ottenere il
+	  <option>Cflags</option> o le opzioni di libreria per essere compilate,
+	  devono ora essere aggiornate per l'uso di <command>pkg-config</command>.
+	</para>
+      </section>
+    </section>
+    <section id="sn-xorg-devel-overview">
+      <title>Xorg X11R7 descrizione per lo sviluppatore</title>
+      <para>Qui c'?? una breve lista di alcuni dei molti cambiamenti sviluppatore/pacchetto
+	che sono presenti in X11R7: </para>
+      <itemizedlist>
+        <listitem>
+          <para>L'intero sistema di compilazione ?? cambiato da
+	    <command>Imake</command> alla collezione GNU autotools.
+	  </para>
+        </listitem>
+        <listitem>
+          <para>Tutte le librerie ora installano files
+	    <command>pkgconfig</command> <filename>*.pc</filename>,
+	    che ora dovrebbero essere sempre usati dal software che
+	    dipende da queste librerie, invece di inglobare nel codice i percorsi a
+	    queste in <filename>/usr/X11R6/lib</filename> o altrove.
+	  </para>
+        </listitem>
+        <listitem>
+          <para>Ogni cosa ?? ora installata direttamente in
+	    <filename>/usr</filename> invece di
+	    <filename>/usr/X11R6</filename>. Tutto il software i cui
+	    percorsi sono compilati all'interno del codice in <filename>/usr/X11R6</filename>,
+	    devono ora essere cambiati preferibilmente per determinare automaticamente
+	    l'appropriata posizione dell'oggetto, o inglobare nel codice i nuovi percorsi
+	    che X11R7 usa per impostazione predefinit. E' fortemente consigliato l'uso di
+	    sistemi di autodeterminazione rispetto a quelli che inglobano i percorsi nel codice.
+	  </para>
+        </listitem>
+        <listitem>
+          <para>Ogni libreria ora ha il suo pacchetto di sorgenti privato,
+	    che crea un subpacchetto binario runtime, ed un subpacchetto
+	    -devel.
+	  </para>
+	  <para>
+	    Ogni pacchetto software che in precedenza prelevava gli
+	    headers di sviluppo, etc. pe le librerie X usando
+	    <computeroutput>BuildRequires:
+	      (XFree86-devel|xorg-x11-devel)</computeroutput>, devono ora
+	    elencare individualmente la dipendenza da ciascuna libreria. Quando
+	    fano questo, ?? notevolmente preferito e fortemente raccomandato
+	    usare compilazioni di dipendenze <firstterm>virtual</firstterm> invece di
+	    includere il nome di pacchetto della libreria nell'implementazione Xorg.
+	  </para>
+	  <para>
+	    Questo vuol dire che dovresti usare: <computeroutput>BuildRequires:
+	      libXft-devel</computeroutput> invece di usare:
+	    <filename>BuildRequires: xorg-x11-Xft-devel</filename>. Se
+	    il tuo software dipende veramente dall'implementazione di una libreria
+	    specifica di X.Org X11, e non ci sono altre
+	    pulite/sicure maniere di risolvere la dipendenza, allora usate la forma
+	    <filename>xorg-x11--devel</filename>. Unirsi al
+	    meccanismo virtuale fornisce/richiede, e rende
+	    indolore se e quando in futuro la libreria verr?? spostata in un altro
+	    posto.
+	  </para>
+        </listitem>
+      </itemizedlist>
+    </section>
   </section>
 </section>
 



From fedora-docs-commits at redhat.com  Fri Nov 25 21:57:12 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 25 Nov 2005 16:57:12 -0500
Subject: docs-common/packaging spec.xsl,1.1,1.2
Message-ID: <200511252157.jAPLvC4k031678@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31658

Modified Files:
	spec.xsl 
Log Message:
Output the changelog



Index: spec.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/spec.xsl,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- spec.xsl	25 Nov 2005 20:52:52 -0000	1.1
+++ spec.xsl	25 Nov 2005 21:57:05 -0000	1.2
@@ -61,6 +61,11 @@
 %files	<xsl:value-of select="@lang"/>
 %defattr(-, root, root, -)
 </xsl:for-each>
+%changelog
+<xsl:for-each select="/rpm-info/changelog/revision">
+* <xsl:value-of select="@date"/> - <xsl:value-of select="author/@email"/> (<xsl:value-of select="author/@wholename"/>)
+- <xsl:value-of select="details"/>
+</xsl:for-each>
 </xsl:template>
 
   <xsl:template name="get-title">



From fedora-docs-commits at redhat.com  Sat Nov 26 04:35:21 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Fri, 25 Nov 2005 23:35:21 -0500
Subject: release-notes/xmlbeats - New directory
Message-ID: <200511260435.jAQ4ZLZh013516@cvs-int.fedora.redhat.com>

Author: kwade

Update of /cvs/docs/release-notes/xmlbeats
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13502/xmlbeats

Log Message:
Directory /cvs/docs/release-notes/xmlbeats added to the repository




From fedora-docs-commits at redhat.com  Sat Nov 26 04:37:28 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Fri, 25 Nov 2005 23:37:28 -0500
Subject: release-notes/xmlbeats README, NONE, 1.1 beatlist, NONE,
	1.1 xmlbeats, NONE, 1.1
Message-ID: <200511260437.jAQ4bSst013545@cvs-int.fedora.redhat.com>

Author: kwade

Update of /cvs/docs/release-notes/xmlbeats
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13527/xmlbeats

Added Files:
	README beatlist xmlbeats 
Log Message:
This script and its config file are a way of getting XML out of the Wiki; if we continue to use something like this ... well, shame on us ... meanwhile, it works well enough.  Read the README for usage tips.


--- NEW FILE README ---
Edit 'beatlist' to specify which wiki file names to convert to XML, then run './xmlbeats'.


--- NEW FILE beatlist ---
Welcome
HardwareRequirements
OverView
Installer
Kernel
Desktop
Printing
ServerTools
FileSystems
FileServers
WebServers
DevelTools
DevelTools/GCC
Security
Security/SELinux
Java
Samba
SystemDaemons
Multimedia
Entertainment
Xorg
ArchSpecific
DatabaseServers
I18n
PackageChanges
Legacy
FinalOverview
Colophon


--- NEW FILE xmlbeats ---
#!/bin/sh

WIKIURL="http://fedoraproject.org/wiki/"
CONVERTERURL="http://www.n-man.com/moin2docbook.htm"
PAGES="`cat beatlist`"

rm -rf Beats

for PAGEBASE in $PAGES; do
	PAGENAME="Docs/Beats/${PAGEBASE}"
	PAGEENCODED="`echo "$PAGENAME" | sed 's/\//%2F/g' | sed 's/:/%3A/g'`"
	PAGEOUT="Beats/`basename "$PAGENAME"`"
	mkdir -p Beats
	wget -nv "${CONVERTERURL}?submit=submit&url=${WIKIURL}${PAGEENCODED}%3Faction=raw" -O "${PAGEOUT}.xml"
done




From fedora-docs-commits at redhat.com  Sat Nov 26 14:43:16 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 26 Nov 2005 09:43:16 -0500
Subject: install-guide fedora-install-guide-en.xml,1.22,1.23
Message-ID: <200511261443.jAQEhGxM000424@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv407

Modified Files:
	fedora-install-guide-en.xml 
Log Message:
Remember to include revhistory entry


Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- fedora-install-guide-en.xml	22 Nov 2005 01:11:28 -0000	1.22
+++ fedora-install-guide-en.xml	26 Nov 2005 14:43:08 -0000	1.23
@@ -115,7 +115,16 @@
 	  </para>
 	</revdescription>
       </revision>
-
+      <revision>
+	<revnumber>1.01rc1</revnumber>
+	<date>2005-11-20</date>
+	<authorinitials>PaulWFrields</authorinitials>
+	<revdescription>
+	  <para>
+	    Reorganization of introductory material
+	  </para>
+	</revdescription>
+      </revision>
     </revhistory>
   </bookinfo>
 



From fedora-docs-commits at redhat.com  Sat Nov 26 14:45:19 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 26 Nov 2005 09:45:19 -0500
Subject: install-guide fedora-install-guide-intro-en.xml,1.17,1.18
Message-ID: <200511261445.jAQEjJZ4000454@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv437

Modified Files:
	fedora-install-guide-intro-en.xml 
Log Message:
Scootch bug reporting notice so as not to interfere with introduction


Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- fedora-install-guide-intro-en.xml	22 Nov 2005 01:11:28 -0000	1.17
+++ fedora-install-guide-intro-en.xml	26 Nov 2005 14:45:12 -0000	1.18
@@ -2,9 +2,6 @@
 <preface id="ch-intro">
   <title>Introduction</title>
 
-<!--  removed until we begin working on the FC5 version -->
-  &BUG-REPORTING;
-
   <para>
     &FC; is a complete desktop and server operating system created
     entirely with open source software.
@@ -36,6 +33,8 @@
     they exist, do not reference them. - PWF.] -->
   </para>
 
+  &BUG-REPORTING;
+
   <section id="sn-background">
     <title>Background</title>
 



From fedora-docs-commits at redhat.com  Sat Nov 26 16:59:35 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 26 Nov 2005 11:59:35 -0500
Subject: install-guide fedora-install-guide-beginninginstallation-en.xml, 1.9,
	1.10 fedora-install-guide-diskpartitioning-en.xml, 1.13,
	1.14 fedora-install-guide-en.xml, 1.23,
	1.24 fedora-install-guide-intro-en.xml, 1.18,
	1.19 fedora-install-guide-other-instmethods-en.xml, 1.14, 1.15
Message-ID: <200511261659.jAQGxZGb003918@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3895

Modified Files:
	fedora-install-guide-beginninginstallation-en.xml 
	fedora-install-guide-diskpartitioning-en.xml 
	fedora-install-guide-en.xml fedora-install-guide-intro-en.xml 
	fedora-install-guide-other-instmethods-en.xml 
Log Message:
Bump 1.0.2, hopefully adding organization improvements and a bit on /home


Index: fedora-install-guide-beginninginstallation-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-beginninginstallation-en.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fedora-install-guide-beginninginstallation-en.xml	22 Nov 2005 01:11:28 -0000	1.9
+++ fedora-install-guide-beginninginstallation-en.xml	26 Nov 2005 16:59:27 -0000	1.10
@@ -3,25 +3,23 @@
   <title>Beginning the Installation</title>
 
   <para>
-    To begin installation of &FC;, boot the computer from the boot
-    media.  The boot media provides the necessary programs and files to
-    start the installation program.  Once you start the installation
+    To begin installation of &FC;, boot the computer from the bootable
+    media.  The bootable media provides the necessary programs and files
+    to start the installation program.  Once you start the installation
     program, you may be able to install from a completely different
     piece of media.
   </para>
 
-  <important>
-    <title>Choosing a Different Installation Source</title>
-    <para>
-      To choose a different source for installation, enter
-      <userinput>linux askmethod</userinput> at the
-      <computeroutput>boot:</computeroutput> prompt.  If you boot from
-      some types of media such as USB or the network, the installation
-      program <emphasis>always</emphasis> asks you to choose the
-      installation source.
-    </para>
-  </important>
-
+  <para>
+    If you boot from the first installation disc of the &FC;
+    distribution, you may choose a different source for installation.
+    The default source is the CDs themselves.  To change this behavior,
+    enter <userinput>linux askmethod</userinput> at the
+    <computeroutput>boot:</computeroutput> prompt.  If you boot from
+    other media, the installation program <emphasis>always</emphasis>
+    asks you to choose the installation source.
+  </para>
+  
   <para>
     The <indexterm>
       <primary>BIOS (Basic Input/Output System)</primary>


Index: fedora-install-guide-diskpartitioning-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-diskpartitioning-en.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- fedora-install-guide-diskpartitioning-en.xml	9 Jun 2005 00:18:04 -0000	1.13
+++ fedora-install-guide-diskpartitioning-en.xml	26 Nov 2005 16:59:27 -0000	1.14
@@ -246,26 +246,29 @@
       <title>Partition Types</title>
 
       <para>
-      Every partition has a <indexterm>
-	<primary>partition</primary>
-	<secondary>type</secondary>
-	<seealso>file system</seealso>
-      </indexterm> <firstterm>partition type</firstterm>, to indicate the format of the <indexterm>
-	<primary>file system</primary> </indexterm> <firstterm>file system</firstterm> on that
-      partition.  The file system enables Linux to organize, search, and
-	retrieve files stored on that partition.  Use the
+	Every partition has a <indexterm>
+	  <primary>partition</primary>
+	  <secondary>type</secondary>
+	  <seealso>file system</seealso>
+	</indexterm> <firstterm>partition type</firstterm>, to indicate
+	the format of the <indexterm>
+	  <primary>file system</primary> </indexterm> <firstterm>file
+	  system</firstterm> on that partition.  The file system enables
+	Linux to organize, search, and retrieve files stored on that
+	partition.  Use the
 	<indexterm>
-	<primary><systemitem
-	    class="filesystem">ext3</systemitem></primary>
-	<see>file system</see>
-      </indexterm><indexterm>
-	<primary>file system</primary>
-	<secondary
-	  sortas="filesystem"><systemitem>ext3</systemitem></secondary>
-      </indexterm> <systemitem
-	class="filesystem"><firstterm>ext3</firstterm></systemitem> file
-	    system for data partitions, unless you have specific needs that require another
-	type of file system.
+	  <primary><systemitem
+	      class="filesystem">ext3</systemitem></primary>
+	  <see>file system</see>
+	</indexterm><indexterm>
+	  <primary>file system</primary>
+	  <secondary
+	    sortas="filesystem"><systemitem>ext3</systemitem></secondary>
+	</indexterm> <systemitem
+	  class="filesystem"><firstterm>ext3</firstterm></systemitem>
+	file system for data partitions that are not part of LVM, unless
+	you have specific needs that require another type of file
+	system.
       </para>
 
       </section> 
@@ -315,8 +318,31 @@
          </para>
       </note>
 
-   </section>
+    </section>
 
+    <section id="sn-partitioning-home">
+      <title>Creating a <filename>/home</filename> Partition</title>
+
+      <para>
+	Many users find it helpful to create a separate partition for
+	the <filename>/home</filename> directory.  With a separate
+	<filename>/home</filename> partition, you can reinstall &FC;
+	without erasing user data files.  If you expect that you or
+	other users will be creating data files, you should create a
+	<filename>/home</filename> partition.
+      </para>
+
+      <tip>
+	<title>LVM and <filename>/home</filename></title>
+	<para>
+	  If your &FC; system will host accounts for numerous users, you
+	  should create the <filename>/home</filename> partition in an
+	  LVM logical volume.  LVM provides flexibility for adding more
+	  user data storage later.
+	</para>
+      </tip>
+
+    </section>
 
   </section>
 


Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- fedora-install-guide-en.xml	26 Nov 2005 14:43:08 -0000	1.23
+++ fedora-install-guide-en.xml	26 Nov 2005 16:59:27 -0000	1.24
@@ -6,8 +6,8 @@
 
 <!ENTITY DOCNAME "fedora-install-guide">
 <!ENTITY DOCLANG "en">
-<!ENTITY DOCVERSION "1.01rc">
-<!ENTITY DOCDATE "2005-11-20">
+<!ENTITY DOCVERSION "1.0.2">
+<!ENTITY DOCDATE "2005-11-25">
 <!ENTITY BOOKID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)">
 
 <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
@@ -41,7 +41,7 @@
 
 <book id="book" lang="en">
   <bookinfo>
-    <title>&FC; &FCLOCALVER; &IG;</title>
+    <title>&FC; &FCLOCALVER; &IG; - BETA</title>
     <!-- Remove DOCLOCALVER for release -->
     <copyright>
       <year>2005</year>
@@ -116,7 +116,7 @@
 	</revdescription>
       </revision>
       <revision>
-	<revnumber>1.01rc1</revnumber>
+	<revnumber>1.0.1rc1</revnumber>
 	<date>2005-11-20</date>
 	<authorinitials>PaulWFrields</authorinitials>
 	<revdescription>
@@ -125,6 +125,17 @@
 	  </para>
 	</revdescription>
       </revision>
+      <revision>
+	<revnumber>1.0.2</revnumber>
+	<date>2005-11-25</date>
+	<authorinitials>PaulWFrields</authorinitials>
+	<revdescription>
+	  <para>
+	    Additional reorganization for clarity; information on
+	    <filename>/home</filename> partition
+	  </para>
+	</revdescription>
+      </revision>
     </revhistory>
   </bookinfo>
 


Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- fedora-install-guide-intro-en.xml	26 Nov 2005 14:45:12 -0000	1.18
+++ fedora-install-guide-intro-en.xml	26 Nov 2005 16:59:27 -0000	1.19
@@ -71,59 +71,25 @@
     <title>Before You Begin</title>
     
     <para>
-      To install &FC; from discs, you need four installation CDs, or the
-      installation DVD.  There are separate disc sets for each supported
-      <firstterm>architecture</firstterm>.  Currently, &FC; supports the
-      <firstterm>i386</firstterm>, <firstterm>ppc</firstterm>, and
-      <firstterm>x86_64</firstterm> architectures.  These architectures
-      are described below:
+      Before installing &FC; you will need access to the following
+      things:
     </para>
-
-    <variablelist>
-      <varlistentry>
-	<term>i386</term>
-	<listitem>
-	  <para>
-	    Intel x86-compatible processors, including Intel Pentium and
-	    Pentium-MMX, Pentium Pro, Pentium-II, Pentium-III, Celeron,
-	    Pentium 4, and Xeon; VIA C3/C3-m and Eden/Eden-N; and AMD
-	    Athlon, AthlonXP, Duron, AthlonMP, and Sempron
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term>ppc</term>
-	<listitem>
-	  <para>
-	    PowerPC processors, such as those found in Apple Power
-	    Macintosh, G3, G4, and G5, and IBM pSeries systems
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term>x86_64</term>
-	<listitem>
-	  <para>
-	    64-bit AMD processors such as Athlon64, Turion64, Opteron;
-	    and Intel 64-bit processors such as EM64T
-	  </para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>
-      You should also have the following documents:
-    </para>
- 
     <itemizedlist>
       <listitem>
 	<para>
-	  a current copy of the Release Notes
+	  Boot or installation media (refer to <xref
+	  linkend="sn-preparing-media"/> for more information)
+	</para>
+      </listitem>
+      <listitem>
+	<para>
+	  Information about your network configuration
 	</para>
       </listitem>
       <listitem>
 	<para>
-	  a copy of this &IG;
+	  A copy of this &IG; and the Release Notes for this version of
+	  &FC;
 	</para>
       </listitem>
     </itemizedlist>
@@ -138,8 +104,7 @@
     <para>
       The Release Notes are available on the first disc in HTML and
       plain text format.  The latest versions of this &IG; and the
-      Release Notes can always be found at <ulink
-	url="http://fedora.redhat.com/docs/">&FDPDOCS-URL;</ulink>.
+      Release Notes can always be found at &FDPDOCS-URL;.
     </para>
 
     <section id="sn-installing-network-configurations">
@@ -226,7 +191,8 @@
 	<firstterm>PXE</firstterm> (Pre-boot eXecution Environment) to
 	boot your computer.  Boot your computer using either an
 	installation DVD, the first installation CD, a boot CD, or a
-	prepared USB storage device.
+	prepared USB storage device.  Refer to <xref
+	linkend="sn-preparing-media"/> for more information.
       </para>
       
       <para>
@@ -235,11 +201,6 @@
 	device.  &FC; includes utilities that allow it to function as a
 	  PXE server for other computers.
       </para>
-
-      <para>
-	Booting your computer is explained in the next section, <xref
-	  linkend="ch-beginninginstallation"/>.
-      </para>
       
     </section>
     
@@ -338,35 +299,83 @@
     </note>
 
     <para>
+      To install &FC; from discs, you need five installation CDs, or the
+      installation DVD.  There are separate disc sets for each supported
+      <firstterm>architecture</firstterm>.  Currently, &FC; supports the
+      <firstterm>i386</firstterm>, <firstterm>ppc</firstterm>, and
+      <firstterm>x86_64</firstterm> architectures.  These architectures
+      are described below:
+    </para>
+
+    <variablelist>
+      <varlistentry>
+	<term>i386</term>
+	<listitem>
+	  <para>
+	    Intel x86-compatible processors, including Intel Pentium and
+	    Pentium-MMX, Pentium Pro, Pentium-II, Pentium-III, Celeron,
+	    Pentium 4, and Xeon; VIA C3/C3-m and Eden/Eden-N; and AMD
+	    Athlon, AthlonXP, Duron, AthlonMP, and Sempron
+	  </para>
+	</listitem>
+      </varlistentry>
+      <varlistentry>
+	<term>ppc</term>
+	<listitem>
+	  <para>
+	    PowerPC processors, such as those found in Apple Power
+	    Macintosh, G3, G4, and G5, and IBM pSeries systems
+	  </para>
+	</listitem>
+      </varlistentry>
+      <varlistentry>
+	<term>x86_64</term>
+	<listitem>
+	  <para>
+	    64-bit AMD processors such as Athlon64, Turion64, Opteron;
+	    and Intel 64-bit processors such as EM64T
+	  </para>
+	</listitem>
+      </varlistentry>
+    </variablelist>
+
+    <important>
+      <title>Architecture-Specific Distributions</title>
+      <para>
+	To install &FC; you need the boot or installation media that is
+	particular to your architecture.
+      </para>
+    </important>
+
+    <para>
       The &FC; distribution includes <firstterm>image files</firstterm>
       for boot-only CD or DVD media and USB media. These files can be
       converted into bootable media using standard Linux utilities or
       third-party programs on other operating systems.
     </para>
 
-    <note>
-      <title>CD or DVD Installation Media</title>
-      <para>
-	You may also use the first CD or DVD disc from the complete &FC;
-	distribution as boot media.  For instructions to download and
-	prepare this media, refer to <ulink
-	  url="http://fedora.redhat.com/download/"/>.  If you already
-	have the full set of &FC;, skip to <xref
-	linkend="sn-booting-from-disc"/>.
-      </para>
-    </note>
+    <para>
+      You may also use the first CD or DVD installation disc from the
+      complete &FC; distribution as boot media.  For instructions to
+      download and prepare this CD or DVD installation media, refer to
+      <ulink url="http://fedora.redhat.com/download/"/>.  If you already
+      have the full set of &FC; installation media, skip to <xref
+      linkend="sn-booting-from-disc"/>.
+    </para>
 
     <section id="sn-preparing-cd-or-dvd-media">
-      <title>Preparing CD or DVD Boot Disc</title>
+      <title>Preparing CD or DVD Media</title>
 
       <para>
 	The <filename>images/boot.iso</filename> file on the first &FC;
 	installation disc is a boot image designed for CD and DVD media.
-	This file also appears on FTP and Web sites providing &FC;.
+	This file also appears on FTP and Web sites providing &FC;.  You
+	can also find this file on mirror sites in the &FC; distribution
+	directory for your particular architecture.
       </para>
 
       <para>
-	To convert the ISO file into a physical CD, use the option in
+	To convert an ISO file into a physical CD, use the option in
 	your CD-writing program that burns a CD image file to a CD. If
 	you copy the file itself to a CD instead, the disc will not boot
 	or work correctly.  Refer to your CD writing program
@@ -438,7 +447,7 @@
 	  </para>
 
 <screen>
-<userinput>dd if=diskboot.img of=/dev/sda1</userinput>
+<userinput>dd if=diskboot.img of=/dev/sda</userinput>
 </screen>
 
 	</step>


Index: fedora-install-guide-other-instmethods-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-other-instmethods-en.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- fedora-install-guide-other-instmethods-en.xml	9 Jun 2005 00:18:55 -0000	1.14
+++ fedora-install-guide-other-instmethods-en.xml	26 Nov 2005 16:59:27 -0000	1.15
@@ -10,7 +10,7 @@
   <orderedlist>
     <listitem>
       <para>
-	You booted with PXE, or USB media.
+	You booted with PXE, USB media, or boot-only CD or DVD media.
       </para>
     </listitem>
     <listitem>
@@ -46,9 +46,10 @@
   <note>
     <title>CD/DVD Activity</title>
     <para>
-      If a &FED; disc is in your computer's CD or DVD drive, the
-      installation program loads its next stage from that disc.  The
-      installation program downloads package data from the source you
+      If the first &FC; distribution installation disc is in your
+      computer's CD or DVD drive, the installation program loads its
+      next stage from that disc.  The installation program still
+      downloads <emphasis>package data</emphasis> from the source you
       choose.
     </para>
   </note>



From fedora-docs-commits at redhat.com  Sat Nov 26 18:29:21 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 26 Nov 2005 13:29:21 -0500
Subject: docs-common/packaging spec.xsl,1.2,1.3
Message-ID: <200511261829.jAQITLbg007513@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7496

Modified Files:
	spec.xsl 
Log Message:
Just cosmetic changes


Index: spec.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/spec.xsl,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- spec.xsl	25 Nov 2005 21:57:05 -0000	1.2
+++ spec.xsl	26 Nov 2005 18:29:13 -0000	1.3
@@ -7,13 +7,11 @@
 
   <xsl:param name="lang" select="'en'" />
   <xsl:param name="docbase" select="'example-tutorial'" />
-  <xsl:param name="release"	select="1"/>
 
 <xsl:template match="/">
 # Fedora Documentation Specfile
 %define	docbase	<xsl:value-of select="$docbase"/>
-%define release	<xsl:value-of select="$release"/>
-#
+
 Summary:	Fedora Documentation: %{docbase}
 Name:		fedora-doc-%{docbase}
 Version:	<xsl:value-of select="/rpm-info/changelog/revision[1]/@version"/>
@@ -41,29 +39,32 @@
 
 %prep
 %setup -q -n %{docbase}-${version}
-	for in in $RPM_BUILD_DIR/%{docbase}-%{version}/%{docbase}*.xml
-	do
-		%{__sed} -i 's;../docs-common;../../docs-common;' "$i"
-	done
+for in in $RPM_BUILD_DIR/%{docbase}-%{version}/%{docbase}*.xml
+do
+	%{__sed} -i 's;../docs-common;../../docs-common;' "$i"
+done
 
 %build
 #	/bin/rm -r $RPM_BUILD_ROOT
 #	/usr/bin/install -d -m 0755 $RPM_BUILD_ROOT/%{_datadir}/omf/%{name}
 
 %clean
-	/bin/rm -rf $RPM_BUILD_ROOT
+/bin/rm -rf $RPM_BUILD_ROOT
 
 <xsl:for-each select="/rpm-info/titles/translation">
 %post	<xsl:value-of select="@lang"/>
-	/usr/bin/scrollkeeper-update || true
+/usr/bin/scrollkeeper-update || true
+
 %postun	<xsl:value-of select="@lang"/>
-	/usr/bin/scrollkeeper-update || true
+/usr/bin/scrollkeeper-update || true
+
 %files	<xsl:value-of select="@lang"/>
 %defattr(-, root, root, -)
 </xsl:for-each>
+
 %changelog
 <xsl:for-each select="/rpm-info/changelog/revision">
-* <xsl:value-of select="@date"/> - <xsl:value-of select="author/@email"/> (<xsl:value-of select="author/@wholename"/>)
+* <xsl:value-of select="@date"/> - <xsl:value-of select="author/@wholename"/> &lt;<xsl:value-of select="author/@email"/>&gt; - <xsl:value-of select="@version"/> 
 - <xsl:value-of select="details"/>
 </xsl:for-each>
 </xsl:template>



From fedora-docs-commits at redhat.com  Sat Nov 26 21:44:32 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sat, 26 Nov 2005 16:44:32 -0500
Subject: docs-common/packaging bookinfo.xsl, 1.1, 1.2 rpm-info.dtd, 1.1,
	1.2 spec.xsl, 1.3, 1.4
Message-ID: <200511262144.jAQLiWla013021@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12984/docs-common/packaging

Modified Files:
	bookinfo.xsl rpm-info.dtd spec.xsl 
Log Message:
Removed top-level "<release>" element.  Added "release" and "role='rpm'"
attributes to the changelog  info.  Changelog elements marked "role='rpm'" 
only appear in the RPM %changelog.



Index: bookinfo.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/bookinfo.xsl,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- bookinfo.xsl	25 Nov 2005 20:52:52 -0000	1.1
+++ bookinfo.xsl	26 Nov 2005 21:44:24 -0000	1.2
@@ -6,68 +6,68 @@
     <xsl:param name="doctype" select="'bookinfo'"/>
 
     <xsl:template match="/">
-        <xsl:element name="{$doctype}">
-            <title>
-                <xsl:call-template name="get-title"/>
-            </title>
-            <copyright>
-                <year>
-                    <xsl:value-of select="/rpm-info/copyright/year"/>
-                </year>
-                <xsl:for-each select="/rpm-info/copyright/holder">
-                    <holder>
-                        <xsl:value-of select="node()"/>
-                    </holder>
-                </xsl:for-each>
-            </copyright>
-            <authorgroup>
-                <xsl:for-each select="/rpm-info/author">
-                    <author>
-                        <xsl:call-template name="human"/>
-                    </author>
-                </xsl:for-each>
-                <xsl:for-each select="/rpm-info/translator">
-                    <othercredit>
-                        <xsl:call-template name="human"/>
-                        <personalblurb>Translator</personalblurb>
-                    </othercredit>
-                </xsl:for-each>
-                <xsl:for-each select="/rpm-info/editor">
-                    <editor>
-                        <xsl:call-template name="human"/>
-                    </editor>
-                </xsl:for-each>
-            </authorgroup>
-            <xsl:text disable-output-escaping="yes">&amp;LEGALNOTICE;</xsl:text>
-            <revhistory>
-                <xsl:for-each select="/rpm-info/changelog/revision">
-                    <revision>
-                        <revnumber><xsl:value-of select="@version"/></revnumber>
-                        <date><xsl:value-of select="@date"/></date>
-                        <authorinitials><xsl:value-of select="author/@initials"/></authorinitials>
-                        <revdescription>
-                            <para>
-                                <xsl:value-of select="details"/>
-                            </para>
-                        </revdescription>
-                    </revision>
-                </xsl:for-each>
-            </revhistory>
-        </xsl:element>
+	<xsl:element name="{$doctype}">
+	    <title>
+		<xsl:call-template name="get-title"/>
+	    </title>
+	    <copyright>
+		<year>
+		    <xsl:value-of select="/rpm-info/copyright/year"/>
+		</year>
+		<xsl:for-each select="/rpm-info/copyright/holder">
+		    <holder>
+			<xsl:value-of select="node()"/>
+		    </holder>
+		</xsl:for-each>
+	    </copyright>
+	    <authorgroup>
+		<xsl:for-each select="/rpm-info/author">
+		    <author>
+			<xsl:call-template name="human"/>
+		    </author>
+		</xsl:for-each>
+		<xsl:for-each select="/rpm-info/translator">
+		    <othercredit>
+			<xsl:call-template name="human"/>
+			<personalblurb>Translator</personalblurb>
+		    </othercredit>
+		</xsl:for-each>
+		<xsl:for-each select="/rpm-info/editor">
+		    <editor>
+			<xsl:call-template name="human"/>
+		    </editor>
+		</xsl:for-each>
+	    </authorgroup>
+	    <xsl:text disable-output-escaping="yes">&amp;LEGALNOTICE;</xsl:text>
+	    <revhistory>
+		<xsl:for-each select="/rpm-info/changelog/revision[@role != 'rpm']">
+		    <revision>
+			<revnumber><xsl:value-of select="@version"/></revnumber>
+			<date><xsl:value-of select="@date"/></date>
+			<authorinitials><xsl:value-of select="author/@initials"/></authorinitials>
+			<revdescription>
+			    <para>
+				<xsl:value-of select="details"/>
+			    </para>
+			</revdescription>
+		    </revision>
+		</xsl:for-each>
+	    </revhistory>
+	</xsl:element>
     </xsl:template>
 
     <xsl:template name="get-title">
-        <xsl:for-each select="/rpm-info/titles/translation">
-            <xsl:choose>
-                <xsl:when test="@lang = $lang">
-                    <xsl:value-of select="title"/>
-                </xsl:when>
-            </xsl:choose>
-        </xsl:for-each>
+	<xsl:for-each select="/rpm-info/titles/translation">
+	    <xsl:choose>
+		<xsl:when test="@lang = $lang">
+		    <xsl:value-of select="title"/>
+		</xsl:when>
+	    </xsl:choose>
+	</xsl:for-each>
     </xsl:template>
 
     <xsl:template name="human">
-        <surname><xsl:value-of select="@surname"/></surname>
-        <firstname><xsl:value-of select="@firstname"/></firstname>
+	<surname><xsl:value-of select="@surname"/></surname>
+	<firstname><xsl:value-of select="@firstname"/></firstname>
     </xsl:template>
 </xsl:stylesheet>


Index: rpm-info.dtd
===================================================================
RCS file: /cvs/docs/docs-common/packaging/rpm-info.dtd,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-info.dtd	25 Nov 2005 20:52:52 -0000	1.1
+++ rpm-info.dtd	26 Nov 2005 21:44:24 -0000	1.2
@@ -1,16 +1,11 @@
-<!--
-  DTD for the Fedora Docs Project RPM Information file "rpm-info.xml"
--->
-
-<!ELEMENT rpm-info		(release,author+,translator*,editor*,
-				license,copyright+,titles,changelog)	>
+<!ELEMENT rpm-info		(author+,translator*,editor*, license,copyright+,titles,changelog)	>
 
 <!ELEMENT release		EMPTY					>
 <!ATTLIST release	rel	CDATA		#REQUIRED		>
 
-<!ELEMENT license		(rights,license.version)		>
+<!ELEMENT license		(rights,version)			>
 <!ELEMENT rights		(#PCDATA)				>
-<!ELEMENT license.version	(#PCDATA)				>
+<!ELEMENT version		(#PCDATA)				>
 
 <!ELEMENT copyright		(year,holder+)				>
 <!ELEMENT year			(#PCDATA)				>
@@ -21,8 +16,7 @@
 <!ELEMENT translation		(title,desc)*				>
 <!ATTLIST translation	lang 	CDATA		#REQUIRED		>
 
-<!ELEMENT title			(#PCDATA)				>
-<!ELEMENT version 		(#PCDATA)     				>
+<!ELEMENT title			(#PCDATA) 				>
 <!ELEMENT desc			(#PCDATA)				>
 
 <!ELEMENT changelog		(revision+)				>
@@ -31,6 +25,8 @@
 <!ELEMENT revision		(author+,editor*,details)		>
 <!ATTLIST revision  	date   	CDATA   	#REQUIRED 		>
 <!ATTLIST revision  	version	CDATA   	#REQUIRED 		>
+<!ATTLIST revision	release	CDATA		#REQUIRED		>
+<!ATTLIST revision	role	(doc|rpm)	"doc"			>
 
 <!ELEMENT author  		EMPTY					>
 <!ATTLIST author	wholename CDATA   	#REQUIRED 		>


Index: spec.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/spec.xsl,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- spec.xsl	26 Nov 2005 18:29:13 -0000	1.3
+++ spec.xsl	26 Nov 2005 21:44:24 -0000	1.4
@@ -15,8 +15,8 @@
 Summary:	Fedora Documentation: %{docbase}
 Name:		fedora-doc-%{docbase}
 Version:	<xsl:value-of select="/rpm-info/changelog/revision[1]/@version"/>
-Release:	<xsl:value-of select="/rpm-info/release/@rel"/>
-License:	<xsl:value-of select="/rpm-info/license/rights"/>
+Release:	<xsl:value-of select="/rpm-info/changelog/revision[1]/@release"/>
+License:	<xsl:value-of select="/rpm-info/license/rights"/> (Version <xsl:value-of select="/rpm-info/license/version"/>)
 Url:		http://fedora.redhat.com/projects/docs
 Source0:	%{docbase}-%{version}.src.tar.gz
 Source1:	%{name}.desktop
@@ -64,7 +64,7 @@
 
 %changelog
 <xsl:for-each select="/rpm-info/changelog/revision">
-* <xsl:value-of select="@date"/> - <xsl:value-of select="author/@wholename"/> &lt;<xsl:value-of select="author/@email"/>&gt; - <xsl:value-of select="@version"/> 
+* <xsl:value-of select="@date"/> - <xsl:value-of select="author/@wholename"/> &lt;<xsl:value-of select="author/@email"/>&gt; - <xsl:value-of select="@version"/>
 - <xsl:value-of select="details"/>
 </xsl:for-each>
 </xsl:template>



From fedora-docs-commits at redhat.com  Sat Nov 26 21:44:26 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sat, 26 Nov 2005 16:44:26 -0500
Subject: example-tutorial Makefile, 1.15, 1.16 example-tutorial-en.xml, 1.15,
	1.16 rpm-info.xml, 1.1, 1.2
Message-ID: <200511262144.jAQLiuXJ013026@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12984/example-tutorial

Modified Files:
	Makefile example-tutorial-en.xml rpm-info.xml 
Log Message:
Removed top-level "<release>" element.  Added "release" and "role='rpm'"
attributes to the changelog  info.  Changelog elements marked "role='rpm'" 
only appear in the RPM %changelog.



Index: Makefile
===================================================================
RCS file: /cvs/docs/example-tutorial/Makefile,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- Makefile	11 Oct 2005 23:43:01 -0000	1.15
+++ Makefile	26 Nov 2005 21:44:18 -0000	1.16
@@ -7,12 +7,21 @@
 # Copyright 2003 Tammy Fox, Red Hat, Inc.
 # Copyright 2005 Tommy Reynolds, MegaCoder.com
 ###############################################################################
+# There is actually no "de" translation.  All the '*-de*" files are just
+# fodder to check the internationalization (i18n) workings for the FTP.
+# No discourtesey to an Germanic speaker is intended.  -- Tommy Reynolds
+###############################################################################
 #
 # Document-specific definitions.
 #
-LANGUAGES      	= en
+LANGUAGES      	= en de
 DOCBASE        	= example-tutorial
-XMLEXTRAFILES-en=
+#
+DOCTITLE-en	= Example Tutorial
+XMLEXTRAFILES-en=article-info-en.xml
+#
+DOCTITLE-de	= Beispiel Tutorial
+XMLEXTRAFILES-de=
 #
 ######################################################
 include ../docs-common/Makefile.common
@@ -27,6 +36,14 @@
 #${DOCBASE}-en/index.html::
 #	echo FINISHED AT LAST
 
+######################################################
+#
+article-info-en.xml:: rpm-info.xml
+	xsltproc -o $@ --stringparam doctype articleinfo ../docs-common/packaging/bookinfo.xsl rpm-info.xml
+
+clean::
+	${RM} bookinfo.xml
+######################################################
 
 ######################################################
 # Some packaging specific vars


Index: example-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/example-tutorial-en.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- example-tutorial-en.xml	18 Sep 2005 22:55:34 -0000	1.15
+++ example-tutorial-en.xml	26 Nov 2005 21:44:18 -0000	1.16
@@ -1,4 +1,5 @@
 <!-- $Id: -->
+
 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
  "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
 
@@ -7,70 +8,42 @@
 
 <!ENTITY BOOKID "example-tutorial-0.14 (2005-09-18)"> <!-- change version of manual and date here -->
 
+<!ENTITY  ARTICLE-INFO-EN SYSTEM "article-info-en.xml" >
+
 ]>
 
 <article id="example-tutorial" lang="en">
-  <articleinfo>
-    <title>Example Tutorial</title>
-    <copyright>
-      <year>2003, 2005</year>
-      <holder>&FORMAL-RHI;</holder>
-      <holder>Tammy Fox</holder>
-    </copyright>
-    <authorgroup>
-      <author>
-  <surname>Fox</surname>
-  <firstname>Tammy</firstname>
-      </author>
-      <editor>
-  <surname>Frields</surname>
-  <firstname>Paul</firstname>
-  <othername role="mi">W.</othername>
-      </editor>
-    </authorgroup>
-    &LEGALNOTICE;
-    <revhistory>
-      <revision>
-	<revnumber>0.13</revnumber>
-	<date>2005-09-18</date>
-	<authorinitials>PaulWFrields</authorinitials>
-	<revdescription>
-	  <para>
-	    Add revision history.
-	  </para>
-	</revdescription>
-      </revision>
-    </revhistory>
-  </articleinfo>
+
+  &ARTICLE-INFO-EN;
 
   <section id="sn-some-section">
     <title>Some Section</title>
-
     <indexterm>
       <primary>Index term</primary>
     </indexterm>
-
     <para>
-      This is an example section. You should not use sect1, sect2, etc., since
-      those tags will make sections less modular &mdash; that is, harder to
-      relocate without changing a lot of other markup.
+      This is an example section. You should not use sect1, sect2, etc.,
+      since those tags will make sections less modular &mdash; that is,
+      harder to relocate without changing a lot of other markup.
     </para>
+
     <para>
-      Keep text within the <command>title</command> tags on the same line as the
-      tags. Nesting the title on a separate line from the enclosing tags results
-      in extra spaces in HTML rendering.
+      Keep text within the <command>title</command> tags on the same
+      line as the tags. Nesting the title on a separate line from the
+      enclosing tags results in extra spaces in HTML rendering.
     </para>
 
     <warning>
       <title>Warning</title>
+
       <para>
         Example of an admonition.
       </para>
     </warning>
 
     <para>
-      This paragraph illustrates the use of command syntax to accomplish a
-      task. Note that specific filenames denoting versions should be
+      This paragraph illustrates the use of command syntax to accomplish
+      a task. Note that specific filenames denoting versions should be
       avoided. To install any RPM package, use the following syntax:
     </para>
 <screen>
@@ -78,11 +51,11 @@
 </screen>
     <para>
       Notice that the <command>screen</command> section is entirely
-      left-justified with no preceding indent. This is necessary to ensure
-      proper rendering in PDFs. Also notice that the entire
+      left-justified with no preceding indent. This is necessary to
+      ensure proper rendering in PDFs. Also notice that the entire
       <command>command</command> has been surrounded by
-      <command>userinput</command> since the user types this
-      command. Computer output would be enclosed in
+      <command>userinput</command> since the user types this command.
+      Computer output would be enclosed in
       <command>computeroutput</command> tags, as in the following
       sample.
     </para>
@@ -92,42 +65,59 @@
 </screen>
     <para>
       Lines should be broken <emphasis>exactly</emphasis> as they are
-      on-screen. Also, note that spaces inside <command>screen</command> tags
-      are automatically treated as non-breaking.
+      on-screen. Also, note that spaces inside <command>screen</command>
+      tags are automatically treated as non-breaking.
     </para>
     <tip>
       <title>Fill modes and <command>screen</command> tags</title>
       <para>
-  Using automatic or manual fill commands in Emacs/PSGML will sometimes
-  mangle <command>screen</command> sections. Use care when performing fill
-  operations, and check the results.
+        Using automatic or manual fill commands in Emacs/PSGML will
+        sometimes mangle <command>screen</command> sections. Use care
+        when performing fill operations, and check the results.
       </para>
     </tip>
   </section>
 
   <section>
     <title>Callout Example</title>
-      <programlisting id="pl-callout">
+<programlisting id="pl-callout">
 Line 1 <co id="pl-callout-L1"/>
 Line 2
 Line 3
 Line 4 <co id="pl-callout-L4"/>
       </programlisting>
-      <calloutlist>
-        <callout arearefs="pl-callout-L1">
-          <para>
-            Here is a callout.
-          </para>
-        </callout>
-        <callout arearefs="pl-callout-L4">
-          <para>
-            The second callout.
-          </para>
-        </callout>
-      </calloutlist>
+    <calloutlist>
+      <callout arearefs="pl-callout-L1">
+        <para>
+          Here is a callout.
+        </para>
+      </callout>
+      <callout arearefs="pl-callout-L4">
+        <para>
+          The second callout.
+        </para>
+      </callout>
+    </calloutlist>
+  </section>
+
+  <section>
+    <title>Deeply nested sections</title>
+    <para>Early to bed, early to rise</para>
+    <section>
+      <title>Second Level</title>
+      <para>Is the curse of the working class</para>
+      <section>
+        <title>Third Level</title>
+        <para>He who can, does</para>
+        <section>
+          <title>Fourth Level</title>
+          <para>He who cannot, manages.</para>
+        </section>
+      </section>
+    </section>
   </section>
 
-<index id="generated-index"></index>
+  <index id="generated-index"></index>
 </article>
 
 <!--


Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/rpm-info.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-info.xml	25 Nov 2005 21:01:59 -0000	1.1
+++ rpm-info.xml	26 Nov 2005 21:44:18 -0000	1.2
@@ -3,12 +3,11 @@
 <!-- Sample document description from which we build RPMs -->
 <!DOCTYPE rpm-info SYSTEM "../docs-common/packaging/rpm-info.dtd">
 <rpm-info>
-  <release rel="1"/>
   <author email="tcf at redhat.com" firstname="Tammy" initials="TCF" surname="Fox" wholename="Tammy Fox"/>
   <editor email="stickster at gmail.com" firstname="Paul" surname="Frields" wholename="Paul W. Frields"/>
   <license>
     <rights>GNU FDL</rights>
-    <license.version>1.0</license.version>
+    <version>1.0</version>
   </license>
   <copyright>
     <year>2003, 2004, 2005</year>
@@ -26,7 +25,11 @@
     </translation>
   </titles>
   <changelog order="newest-first">
-    <revision date="2005-09-18" version="0.13">
+    <revision date="Sat 26 Nov 2005" release="2" version="1.0.0" role="rpm">
+      <author email="me at home.net" firstname="Me" initials="I" surname="Myself" wholename="Me Myself"/>
+      <details>Some rpm-only changes</details>
+    </revision>
+    <revision date="2005-09-18" release="1" version="0.13">
       <author email="stickster at gmail.com" firstname="Paul" initials="PWF" surname="Frields" wholename="Paul W. Frields"/>
       <details>Add revision history</details>
     </revision>



From fedora-docs-commits at redhat.com  Sat Nov 26 21:49:19 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sat, 26 Nov 2005 16:49:19 -0500
Subject: example-tutorial Makefile,1.16,1.17
Message-ID: <200511262149.jAQLnJrs013057@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13040

Modified Files:
	Makefile 
Log Message:
Oops. Didn't mean to commit the Makefile changes just yet.  Sorry for the noise.



Index: Makefile
===================================================================
RCS file: /cvs/docs/example-tutorial/Makefile,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- Makefile	26 Nov 2005 21:44:18 -0000	1.16
+++ Makefile	26 Nov 2005 21:49:12 -0000	1.17
@@ -38,11 +38,11 @@
 
 ######################################################
 #
-article-info-en.xml:: rpm-info.xml
-	xsltproc -o $@ --stringparam doctype articleinfo ../docs-common/packaging/bookinfo.xsl rpm-info.xml
-
-clean::
-	${RM} bookinfo.xml
+#article-info-en.xml:: rpm-info.xml
+#	xsltproc -o $@ --stringparam doctype articleinfo ../docs-common/packaging/bookinfo.xsl rpm-info.xml
+#
+#clean::
+#	${RM} bookinfo.xml
 ######################################################
 
 ######################################################



From fedora-docs-commits at redhat.com  Sun Nov 27 13:12:13 2005
From: fedora-docs-commits at redhat.com (Andrew Martynov (andrmart))
Date: Sun, 27 Nov 2005 08:12:13 -0500
Subject: docs-common/common legalnotice-relnotes-ru.xml, NONE,
	1.1 legalnotice-content-ru.xml, NONE,
	1.1 legalnotice-section-ru.xml, NONE, 1.1
Message-ID: <200511271312.jARDCDjC014070@cvs-int.fedora.redhat.com>

Author: andrmart

Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14052

Added Files:
	legalnotice-relnotes-ru.xml legalnotice-content-ru.xml 
	legalnotice-section-ru.xml 
Log Message:
Necessary Russian localized files


--- NEW FILE legalnotice-relnotes-ru.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY BOILERPLATE "This header makes editing XML easier">

]>
-->

<!-- 

  Use this legalnotice for no-chunks/single-page HTML output.  It is an optional
  usage to move the bulk of the legalnotice to another location in the document.

  If you use this legalnotice, you must include a call to the
  LEGALNOTICE-SECTION entity, or include a similar <section
> in your document.
  The call to LEGALNOTICE-SECTION must happen where a <section
> is otherwise
  allowed.  One good location is immediately following an introduction.

  -->

<legalnotice id="legalnotice">
  <para
>???????? ???????????????? ?????????????????????? ?? ???????????????????????? ?? ?????????????????? ???????????????? ?????????????????? ???????????????????????? GNU (GNU Free Documentation License). ???????????????????????????? ?????????????????????? ?????????? ?????????????????? ?? ???????????? ?????????????????????? ?????????????????????? ?? <xref linkend="sn-legalnotice"/>. </para>
  <tip>
    <title
>?????????? ?????????? ?????????????????? ?? ?????????????? ?????????????????? ?? ????????</title>
    <para
>?????? ?????????????????? ?? ?????????????? ?????????? ???????? ??????????????????. ???????????????? ???????????????? <ulink url="http://fedora.redhat.com/docs/release-notes/"
>http://fedora.redhat.com/docs/release-notes/</ulink
> ?????? ?????????????????? ?????????? ?????????? ?????????????????? ?? ?????????????? &DISTRO; &DISTROVER;. </para>
  </tip>
</legalnotice>


--- NEW FILE legalnotice-content-ru.xml ---
<!-- Andrew Martynov 27-Nov-2005 
  <para>
    Permission is granted to copy, distribute, and/or modify this document under
    the terms of the GNU Free Documentation License, Version 1.2 or any later
    version published by the Free Software Foundation; with no Invariant
    Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the
    license is available at <ulink
    url="http://www.gnu.org/licenses/fdl.html">http://www.gnu.org/licenses/fdl.html</ulink>.
  </para>
-->

  <para>
    ?????????? ???? ??????????????????????, ?????????????????????????????? ??/?????? ?????????????????? ?????????? ?????????????????? ???????????????????? 
    ?? ???????????????? ?????????????????? ???????????????????????? GNU, ???????????? 1.2 ?????? ?????????? ??????????????, ???????????????? ???????????? 
    ???????????????????? ???????????????????????? ?????????????????????? (Free Software Foundation); ?????? ?????????????????? ????????????????, 
    ???????????????? ???????????? ?????? ?????????? ????????????. ?????????? ???????? ???????????????? ?????????? ???????????????? ???? ???????????? <ulink
    url="http://www.gnu.org/licenses/fdl.html">http://www.gnu.org/licenses/fdl.html</ulink>. 
  </para>

<!-- Andrew Martynov 27-Nov-2005
  <para>
    This document may be copied and distributed in any medium, either
    commercially or noncommercially, provided that the GNU Free Documentation
    License (FDL), the copyright notices, and the license notice saying the GNU
    FDL applies to the document are reproduced in all copies, and that you add
    no other conditions whatsoever to those of the GNU FDL.
  </para>
-->

  <para>
    ???????????????? ?????????? ???????? ???????????????????? ?????? ?????????????????????????? ???? ?????????? ????????????????, 
    ?? ???????????????????????? ?????? ???????????????????????????? ??????????, ?? ????????????, ???????? GNU-???????????????? 
    ?????????????????? ???????????????????????? (FDL), ?????????????? ?? ???????????????????????????????? ?? ?????????????????? ?? ????????????????, ?? ?????????????? 
    ?????????????????? ???? ?????????????????????????? GNU FDL ?????????????????????????? ?? ?????????? ??????????????????, ?????????????????? ???? ???????? ????????????, 
    ?? ???? ???? ???????????????? ???????????? ??????????????, ???????????? ???????????????????????? ?? GNU FDL.
  </para>

<!-- Andrew Martynov 27-Nov-2005
  <para>
    Garrett LeSage created the admonition graphics (note, tip, important,
    caution, and warning).
    Tommy Reynolds <email>Tommy.Reynolds at MegaCoder.com</email> created the callout graphics.
    They all may be freely redistributed with documentation
    produced for the &PROJECT;.
    </para>
-->

  <para>
    ??????????????, ???????????????????????? ???????????????? (??????????????????, ??????????????????, ??????????, ???????????????? ?? 
    ????????????????????????????), ???????????? ???????????? ?????????? (Garrett LeSage) . ?????????? ???????????????????? ???????????????? ??? 
    ?????????? ?????????????????? (Tommy Reynolds) <email>Tommy.Reynolds at MegaCoder.com</email>. 
    ?????? ?????? ?????????? ???????????????? ???????????????????????????????? ?? ?????????????? ????????????????????????, ?????????????????????? ?????? ?????????????? &PROJECT;.
    </para>

  <para>
    &BOOKID;
  </para>

<!-- Andrew Martynov 27-Nov-2005
  <para>
    &RH; and the &RH; "Shadow Man" logo are registered trademarks of
    &FORMAL-RHI; in the United States and other countries.
  </para>
-->

  <para>
    &RH; ?? ?????????????? &RH; "Shadow Man" ???????????????? ?????????????????????????????????????? ?????????????????? ?????????????? 
    ???????????????? &FORMAL-RHI; ?? ?????????????????????? ???????????? ?? ???????????? ??????????????.
  </para>

<!-- Changing to match RHEL usage, changes are drawn directly from existing -->
<!-- lawyer-approved changes within the RHEL legalnotice:
  <para>
    &RH;, &RH; Network, the &RH; "Shadow Man" logo, RPM, Maximum RPM, the RPM logo, Linux
    Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts,
    Rawhide and all &RH;-based trademarks and logos are trademarks or registered
    trademarks of &FORMAL-RHI; in the United States and other countries.
  </para>

  <para>
    Linux is a registered trademark of Linus Torvalds.
  </para>

  <para>
    Motif and UNIX are registered trademarks of The Open Group.
  </para>

  <para>
    Intel and Pentium are registered trademarks of Intel Corporation. Itanium
    and Celeron are trademarks of Intel Corporation.
  </para>

  <para>
    AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of Advanced Micro
    Devices, Inc.
  </para>

  <para>
    Windows is a registered trademark of Microsoft Corporation.
  </para>

  <para>
    SSH and Secure Shell are trademarks of SSH Communications Security, Inc.
  </para>

  <para>
    FireWire is a trademark of Apple Computer Corporation.
  </para>
-->

<!-- Andrew Martynov 27-Nov-2005
  <para>
    All other trademarks and copyrights referred to are the property of their
    respective owners.
  </para>
-->

  <para>
    ?????? ???????????? ???????????????????????? ???????????????? ?????????? ?? ?????????? ?????????????????????? ???????????????? 
    ???????????????????????????? ???? ????????????????????.
  </para>


--- NEW FILE legalnotice-section-ru.xml ---
<!-- 

  Use this legalnotice for no-chunks/single-page HTML output.  It is an optional
  usage to move the bulk of the legalnotice to another location in the document.

  If you use this legalnotice, you must include a call to the
  LEGALNOTICE-NOCHUNKS or LEGALNOTICE-RELNOTES.  This gets the legal material in
  the proper <legalnotice /> container.SECTION entity, or include a similar <section> in your document.
  The call to LEGALNOTICE-SECTION must happen where a <section> is otherwise
  allowed.  One good location is immediately following an introduction.

  -->
  <section id="sn-legalnotice">
    <title>?????????????????????? ??????????????????????</title>
    &LEGALNOTICE-CONTENT;
  </section>



From fedora-docs-commits at redhat.com  Sun Nov 27 13:19:32 2005
From: fedora-docs-commits at redhat.com (Andrew Martynov (andrmart))
Date: Sun, 27 Nov 2005 08:19:32 -0500
Subject: release-notes desktop-ru.xml, 1.1, 1.2 development-tools-ru.xml, 1.1,
	1.2 i18n-ru.xml, 1.1, 1.2 install-notes-ru.xml, 1.1,
	1.2 legacy-ru.xml, 1.1, 1.2 package-movement-ru.xml, 1.1,
	1.2 splash-ru.xml, 1.1, 1.2
Message-ID: <200511271319.jARDJWoc014104@cvs-int.fedora.redhat.com>

Author: andrmart

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14080

Modified Files:
	desktop-ru.xml development-tools-ru.xml i18n-ru.xml 
	install-notes-ru.xml legacy-ru.xml package-movement-ru.xml 
	splash-ru.xml 
Log Message:
Updated translation ofter FC5 test1


Index: desktop-ru.xml
===================================================================
RCS file: /cvs/docs/release-notes/desktop-ru.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- desktop-ru.xml	10 Nov 2005 21:21:08 -0000	1.1
+++ desktop-ru.xml	27 Nov 2005 13:19:24 -0000	1.2
@@ -1,92 +1,76 @@
 <section id="sn-desktop">
   <title
->Desktop</title>
+>?????????????? ????????</title>
   <itemizedlist>
     <title
->Notes</title>
+>??????????????????</title>
     <listitem>
       <para
->GNOME 2.12 and KDE 3.4.2 Major highlight
-      </para>
+>GNOME 2.12 and KDE 3.4.2 are included in &FC; &LOCALVER;. </para>
     </listitem>
     <listitem>
       <para
->The current test release has GNOME 2.12.1, together with
-	some previews of technology from the forthcoming GNOME 2.14:
-      </para>
+>This test release has GNOME 2.12.1, together with some previews of technology from the forthcoming GNOME 2.14. Feedback on these packages is especially appreciated. </para>
       <itemizedlist>
         <listitem>
           <para
->gnome-power-manager: brings the Hardware Abstraction
-	    Layer to the world of laptop batteries and UPS units - these
-	    things should "Just Work", with a simple UI  (naturally, in
-	    a test release, they might not)
-	  </para>
+><filename
+>gnome-power-manager</filename
+>: <application
+>GNOME Power Manager </application
+> is a session daemon for the GNOME desktop environment that makes it easy to manage power on your laptop or desktop system. It takes advantage of HAL (which provides a hardware abstraction layer) and DBUS (Inter Process Communication software) written and maintained by &FC; developers. </para>
         </listitem>
         <listitem>
           <para
->gnome-screensaver: giving a fresh UI to screensavers and
-	    the <guilabel
->Lock Screen</guilabel
-> dialog
-	  </para>
+><filename
+>gnome-screensaver</filename
+>: Provides a integrated user interface to screensavers and the lock screen dialog. </para>
         </listitem>
         <listitem>
           <para
->Memory optimizations in the fontconfig and
-	    shared-mime-info packages (these now use shared
-	    memory-mapped caches for this data).  Both of these caches
-	    are still somewhat experimental.
-	  </para>
+>Memory optimizations in the <filename
+>fontconfig</filename
+> and <filename
+>shared-mime-info</filename
+> packages. These now use shared memory-mapped caches for this data. </para>
         </listitem>
       </itemizedlist>
     </listitem>
-  <para>
-    Test feedback on these experimental packages is especially
-    appreciated.
-  </para>
-  <para>
-    GNOME 2.12 has removed the terminal option from the desktop root
-    menu. nautilus-open-terminal in Fedora Extras repository provides a
-    enhanced replacement. It is also mentioned in the GNOME 2.12 release
-    notes itself but we might highlight it since the package is provided
-    with the extras repository.
-  </para>
-  <para>
-    Screensavers not installed by default anymore. Should explain why
-    and provide commands to install them.
-  </para>
-  <para
->MCS SELinux is in rawhide. Major highlight
-    (<emphasis
->tentative</emphasis
-> - not sure about classification of
-    this change)
-  </para>
-  <caution>
-    <title
->OpenOffice and upgrading from test releases</title>
-    <para>
-      If you choose to go counter to the recommendation to <emphasis
-	role='strong'
->not</emphasis
-> upgrade from a previous test
-      release, you may encounter a problem with <ulink
-	url='/OpenOffice'
->OpenOffice</ulink
-> following the upgrade.
-    </para>
-    <para>
-      To resolve this, you must do the following command <emphasis
-	role='strong'
->before</emphasis
-> doing the upgrade:
-    </para>
+    <listitem>
+      <para
+>GNOME 2.12 has removed the <guimenuitem
+>terminal</guimenuitem
+> option from the desktop context menu. The package <filename
+>nautilus-open-terminal</filename
+> in &FEX; repository provides an enhanced replacement for those who require it. You can install it using the following command: </para>
 <screen
->
-<command>rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap</command>
+><command>yum install nautilus-open-terminal</command>
 </screen>
-  </caution>
+    </listitem>
+    <listitem>
+      <para
+>Only the blank screensavers is installed by default, since &FC; 4. </para>
+      <para
+>The primary issue is that some screensavers are known to not work correctly or abruptly terminate the graphical interface. This is particularly true for some of the OpenGL animated ones provided within <filename
+></filename
+>xscreensaver-gl-extras package. </para>
+      <para
+>In addition, the material content of the screensavers is sometimes controversial or causes strong reactions. It is better, for the user experience, to not be surprised by the nature of the screensavers. </para>
+      <para
+>Users who want the screensavers package can install it using the following command. </para>
+<screen
+><command>yum install xscreensaver-extras xscreensaver-gl-extras</command>
+</screen>
+    </listitem>
+  </itemizedlist>
+  <note>
+    <title
+>???????????????? ?????????????? ?????????????????? ????????</title>
+    <para
+>The configuration utility <application
+>system-config-mouse</application
+> has been dropped from this release since synaptic and 3 button mouse configuration is being done automatically during installation. Serial mice are not formally supported in &FC; anymore. </para>
+  </note>
 </section>
 <!--
 Local variables:


Index: development-tools-ru.xml
===================================================================
RCS file: /cvs/docs/release-notes/development-tools-ru.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- development-tools-ru.xml	10 Nov 2005 21:21:08 -0000	1.1
+++ development-tools-ru.xml	27 Nov 2005 13:19:24 -0000	1.2
@@ -9,11 +9,34 @@
 
 ]>
 -->
-<!-- Content commented out, no update performed by beat writer yet.
 <section id="sn-devel">
-  <title>
-    Development Tools
-  </title>
+  <title
+>???????????????? ???????????????????? </title>
+  <section id="sn-java-development">
+    <title
+>Java-???????????????? ??????????????????</title>
+    <para
+>Java-???????????????? ?????????????????? ?????????????????? ?? ???????????????? ???????????????? ?????????? ???????????????????????? ?? &FC; &LOCALVER;. </para>
+    <para
+>?????? ?????????????? ???? ???????? ??????????????????: ?????????? ???????????????????? GNU Java runtime (<filename
+>libgcj</filename
+>), ???????????????????? Eclipse Java (<command
+>ecj</command
+>), ?? ?????????? ???????????????? ?? ????????????  (<filename
+>java-gcj-compat</filename
+>), ?????????????? ?????????????????????????? ???????????????????????? ?????????? ???????????????????? ?? ????????????????????, ???????????????????? ???????????? Java ????????????????????. </para>
+    <para
+>???????????????? ?????????????????????? ????????????, ?????????? ?????? Openoffice.org Base, Eclipse ?? Apache Tomcat, ?????? ?? ?????????????????? ???????????? Java ???????????? ?? ?????????????? ?????????? ??????????????, ???????????????????? ?? ???????????? ????????????????????. </para>
+    <para
+>???? ???????????????????????????? ?????????????????????? ???????????????????? ?? ?????????? ???????????????????? ???????????????? (FAQ): </para>
+    <para>
+      <ulink
+	url='http://www.fedoraproject.org/wiki/JavaFAQ'
+>http://www.fedoraproject.org/wiki/JavaFAQ</ulink>
+    </para>
+  </section>
+
+<!-- Content commented out, no update performed by beat writer yet.
   <section id="sn-devel-gcc">
     <title
 >GCC Compiler Collection</title>
@@ -246,8 +269,9 @@
       </listitem>
     </itemizedlist>
   </section>
-</section>
 -->
+</section>
+
 
 <!--
 Local variables:


Index: i18n-ru.xml
===================================================================
RCS file: /cvs/docs/release-notes/i18n-ru.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- i18n-ru.xml	10 Nov 2005 21:21:08 -0000	1.1
+++ i18n-ru.xml	27 Nov 2005 13:19:24 -0000	1.2
@@ -2,110 +2,18 @@
   <title
 >?????????????????????????????????????? (i18n)</title>
   <para
->SCIM has replaced all the other input methods. Major highlight. </para>
+>SCIM ?????????????? ?????? ???????????? ???????????? ??????????. ???????????????? ??????????????. </para>
   <section>
     <title
 >???????????????? ??????????????????</title>
     <para
 >?? ???????? ???????????? ???????????????? ???????????????????? ???? ?????????????????? ?? ?????????????? &DISTRO; ?????????????????? ????????????. </para>
-    <section>
+    <note>
       <title
->?????????????? ?????????? IIIMF</title>
+>IIIMF ??????????????</title>
       <para
->IIIMF is the Internet/Intranet Input Method Framework. In &FC; &LOCALVER; the <filename
->iiimf</filename
-> package is updated to version 12.2. </para>
-      <variablelist>
-	<varlistentry>
-	  <term
->File Path Changes</term>
-	  <listitem>
-	    <para
->The names and locations of some files in the <filename
->iiimf</filename
-> packages have changed. </para>
-	    <para
->The IIIMF server has been renamed from <filename
->/usr/sbin/htt</filename
-> to <filename
->/usr/bin/iiimd</filename
->, and the XIM bridge client renamed from <filename
->httx</filename
-> to <filename
->iiimx</filename
->. The <filename
->init.d</filename
-> script name has not changed: it is still called <filename
->iiim</filename
->. All the global system configuration files are now located under <filename
->/etc/iiim/</filename
->. </para>
-	    <para
->Language Engine (LE) developers should note that LE modules and their data now live under <filename
->${libdir}/iiim/le/<filename
->&lt;LE_NAME&gt;</filename
->/</filename
->, while runtime data is stored under <filename
->/var/lib/iiim/le/<replaceable
->&lt;LE_NAME&gt;</replaceable
->/</filename
->. </para>
-	    <para
->For more information on the exact path and file location changes, please refer to Fedora IIIMF FAQ: </para>
-	    <para
-><ulink url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html"
->http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink
->. </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term
->Hotkeys</term>
-	  <listitem>
-	    <para
->Trigger keys, such as <keycombo
-><keycap
->Ctrl</keycap
-><keycap
->Space</keycap
-></keycombo
-> used to activate Input Methods, are now configurable with the command-line tool <command
->iiimf-le-tools</command
->. This feature is only supported by GTK2 applications currently. For other applications using XIM the trigger key can be changed using an X resource. Refer to the IIIMF FAQ at <ulink url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html"
->http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink
-> for more details on how to change trigger hotkeys. </para>
-	    <para
->Note that the keyname refers to the X key symbol name. For example, if you want to activate with <keycombo
-><keycap
->Ctrl</keycap
-><keycap
->@</keycap
-></keycombo
->, you need to specify '&lt;Control&gt;at' as the keyname not '&lt;Control&gt;@'. </para>
-	    <para
->The per-user configuration of hotkeys does not work currently with &SEL; in enforcing mode due to lack of &SEL; policy. In this case, the hotkey can only be changed in the system-wide configuration. </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term
->Qt Support</term>
-	  <listitem>
-	    <para
->A Qt immodule for <filename
->iiimf</filename
-> is now included. This immodule works but lacks a status window and is considered experimental. Therefore, the default for Qt applications is to continue using XIM for IIMF input. </para>
-	    <para
->If you wish to try the immodule in a Qt application, first install the <filename
->iiimf-qt</filename
-> package, start the application, then click mouse button-3 in an input area and select <guimenuitem
->iiimqcf</guimenuitem
-> from the <guisubmenu
->Select Input Method</guisubmenu
->' submenu. </para>
-	  </listitem>
-	</varlistentry>
-      </variablelist>
-    </section>
+>SCIM ?????????????? IIIMF ?? ?????????????? ?????????? ?????????????? Fedora Core. </para>
+    </note>
   </section>
 </section>
 <!--


Index: install-notes-ru.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-ru.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- install-notes-ru.xml	10 Nov 2005 21:21:08 -0000	1.1
+++ install-notes-ru.xml	27 Nov 2005 13:19:24 -0000	1.2
@@ -9,13 +9,15 @@
     <para
 >???????? ???? ???????????????? ?????????????????? DVD ISO-?????????? &DISTRO; &DISTROVER;, ?????????????? ?? ??????, ?????? ???? ?????? ?????????????????? ???????????????? ???????????? ?????????? ???????????????? ?? ?????????????? ???????????????? ???????????? ?????? 2 ????????????. ????????????????, <command
 >wget</command
-> ?????????????????? ???????? ???????????? ?? ?????????????? <computeroutput
+> ???????????? ???? 1.9.1.16 ?????????????????? ???????? ???????????? ?? ?????????????? <computeroutput
 >File size limit exceeded</computeroutput
 >. </para>
     <para
 >?????????????????? ?????? ???????????????? ???????????? <command
+>wget</command
+> ???????????? 1.9.1-16 ?? ????????????, <command
 >curl</command
->?? <command
+> ?? <command
 >ncftpget</command
 > ???? ?????????? ???????????? ?????????????????????? ?? ?????????? ?????????????? ?????????????????? ??????????, ?????????????? 2 ??????????. </para>
     <para
@@ -29,33 +31,6 @@
   <section id="sn-install-notes-ppc">
     <title
 >?????????????????? ???? ?????????????????? ???? ?????????????????? PPC</title>
-    <section>
-      <title
->???????????????????? ?? ???????????????????????? PPC</title>
-      <para
->?? ???????? ?????????????? ???????????????????????? ?????????????????????? ???????????????????? ?? ???????????????????????? PowerPC (PPC), ???????????????????? ?????? ?????????????????? &DISTRO; &DISTROVER;. </para>
-      <itemizedlist>
-	<listitem>
-	  <para
->??????????????: PowerPC G3 / POWER4 </para>
-	</listitem>
-	<listitem>
-	  <para
->&DISTRO; &DISTROVER; ???????????????????????? ???????????? ?????????????????? "New World" ?????????????????????? Apple Power Macintosh, ?????????????????????? ?? 1999 ??. </para>
-	</listitem>
-	<listitem>
-	  <para
->&DISTRO; &DISTROVER; ?????????? ???????????????????????? IBM eServer pSeries, IBM RS/6000 ?? ???????????? Genesi Pegasos II.</para>
-	</listitem>
-	<listitem>
-	  <para
->?????????????????????????? ?????? ???????????????????? ????????????: ?????????????????? G3 ???????????????? 233 ?????? ?????? ??????????, 64 ?????????? ??????.</para>
-	</listitem>
-	<listitem>
-	  <para
->?????????????????????????? ?????? ??????????????: ?????????????????? G3 ???????????????? 400 ?????? ?????? ??????????, 128?????????? ??????.</para>
-	</listitem>
-      </itemizedlist>
       <para
 >DVD ?????? ???????????? CD ?????????????????????????? ???????????? &FC; ???????????? ?????????????????????? ???? ???????????????????????????? ????????????????????????. ?????????? ??????????, ???????????? ?????????????????????? ??????????????-???????????? ?????????? ?????????? ???? DVD ?????? ???????????? CD ?? ???????????????? <filename
 >images/</filename
@@ -68,13 +43,13 @@
 >Apple Macintosh </term>
 	  <listitem>
 	    <para
->The bootloader should automatically boot the appropriate 32-bit or 64-bit installer. Power management support, including sleep and backlight level management, is present in the <filename
+>?????????????????? ?????????????????????????? ???????????????? ?????????????????????????????? 32-?? ?????? 64-?????????????????? ???????????? ?????????????????? ??????????????????. ?????????????????? ???????????????????? ????????????????, ?????????????? ???????????????????? "???????????? ??????????????" ?? ?????????????? ??????????????????, ???????????????????????? ?? ???????????? <filename
 >apmud</filename
-> package, which is in &FEX;. &FEX; for &FC; is configured by default for yum. Following installation, <filename
+> ???? ?????????????? &FEX;. ???? ??????????????????, ?? yum ?????????????????????? &FEX; ???????????????? ?????? &FC;. ?????????? ?????????????????? ?????????? <filename
 >apmud</filename
-> can be installed by running the command <command
+> ?????????? ???????? ???????????????????? ???????????????? <command
 >yum install apmud</command
-> in a terminal. </para>
+> ?? ???????? ??????????????????. </para>
 	  </listitem>
 	</varlistentry>
 	<varlistentry>
@@ -82,22 +57,22 @@
 >64-bit IBM eServer pSeries (POWER4/POWER5)</term>
 	  <listitem>
 	    <para
->After using OpenFirmware to boot the CD, the bootloader (<command
+>?????????? ???????????????????????????? OpenFirmware ?????? ???????????????? ?? CD, ?????????????????? (<command
 >yaboot</command
->) should automatically boot the 64-bit installer. </para>
+>) ?????????????????????????? ???????????????? 64-???????????? ?????????????????? ??????????????????. </para>
 	  </listitem
 >        
 	</varlistentry>
 	<varlistentry>
 	  <term
->32-bit CHRP (IBM RS/6000 and others)</term>
+>32-bit CHRP (IBM RS/6000 ?? ????????????)</term>
 	  <listitem>
 	    <para
->After using OpenFirmware to boot the CD, select the <filename
+>?????????? ???????????????????????????? OpenFirmware ?????? ???????????????? ?? CD, ???????????????? ?????????????????????? ?????????? <filename
 >linux32</filename
-> boot image at the <prompt
+> ?? ?????????????????????? <prompt
 >boot:</prompt
-> prompt to start the 32-bit installer. Otherwise, the 64-bit installer is started, which does not work.</para>
+> ?????? ?????????????? 32-???????????? ?????????????????? ??????????????????. ?????????? ?????????? ???????????????? 64-???????????? ????????????, ?????????????? ???? ?????????? ????????????????.</para>
 	  </listitem>
 	</varlistentry>
 	<varlistentry>
@@ -105,17 +80,19 @@
 >Genesi Pegasos II</term>
 	  <listitem>
 	    <para
->As of &DISTRO; &DISTROVER;, firmware with full support for ISO9660 file systems is not yet released for the Pegasos. However, the network boot image can be used. At the OpenFirmware prompt, enter the command: </para>
+>?????? &DISTRO; &DISTROVER; ???????????????????????????? ?? ???????????? ???????????????????? ???????????????? ?????????????? ISO9660 ?????? ?????? ???? ???????????????????????? ?????? Pegasos. ?????? ???? ??????????, ?????????? ???????????????????????????? ?????????????? ?????????????????????? ??????????????. ?????? ??????????, ?? ?????????????????????? OpenFirmware ?????????????? ??????????????: </para>
 <screen
-><command>boot cd: /images/netboot/ppc32.img</command> 
+><command
+>boot cd: /images/netboot/ppc32.img</command
+> 
 </screen
 >          
 	    <para
->You will also need to configure OpenFirmware on the Pegasos manually to make the installed &FC; system bootable. To do this, you need to set the <envar
+>?????? ?????? ???? ?????????????????????? ?????????????? ?????????????????? OpenFirmware ???? ???????????? Pegasos ?????? ???????????????? ?????????????????????????? ?????????????? &FC;. ?????? ?????????? ?????? ?????????????????????? ???????????????????? ???????????????????? ?????????? <envar
 >boot-device</envar
-> and <envar
+> ?? <envar
 >boot-file</envar
-> environment variables appropriately. </para>
+> ???????????????????????????? ??????????????. </para>
 	  </listitem
 >        
 	</varlistentry>
@@ -124,17 +101,18 @@
 >???????????????? ???? ????????</term>
 	  <listitem>
 	    <para
->?? ???????????????? images/netboot/ ???????????? ?????????????????? ?????????????? ???????????? ?????????????????????????? ???????? ?? ramdisk. ?????? ?????????????????????????? ?????? ???????????????? ???? ???????? ?? ???????????????????????????? TFTP, ???? ?????????? ???????????????????????????? ?? ?????????? ??????????????????. </para>
+>?? ???????????????? <filename
+>images/netboot/</filename
+> ???????????? ?????????????????? ?????????????? ???????????? ?????????????????????????? ???????? ?? ramdisk. ?????? ?????????????????????????? ?????? ???????????????? ???? ???????? ?? ???????????????????????????? TFTP, ???? ?????????? ???????????????????????????? ?? ?????????? ??????????????????. </para>
 	    <para
->The command <command
+>?????????????? <command
 >yaboot</command
-> supports tftp booting for IBM eServer pSeries and Apple Macintosh. &FED; recommends using yaboot over the netboot images. </para>
+> ???????????????????????? ???????????????? ???? TFTP ???? ???????????????? IBM eServer pSeries ?? Apple Macintosh. &FED; ?????????????????????? ???????????????????????? yaboot ???????????? ?????????????? ?????????????????????? ??????????????. </para>
 	</listitem>
 	</varlistentry>
       </variablelist>
     </section>
-  </section>
-  <section>
+  <section id="sn-anaconda-notes">
     <title
 >?????????????????? ???? Anaconda</title>
     
@@ -161,13 +139,6 @@
 >. ?????? ?????????? ?????????????????? ?????????? ?? ???????????????? ?????? ???????????????????????? ???? ???????????????? ISO-??????????????. </para>
       </listitem>
       <listitem arch="x86">
-<!--	<remark os="test"
->%%% <ulink
-	    url="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654"
->http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137654</ulink
-> 
-	  %%%</remark>
--->
 	<para
 >?????????? ?????????? ???????????????????? &DISTRO; ?????????? ???????? ?????????????????? ???????????????? ????????????, ?????? ?????????? ?????????????? <command
 >memtest86</command
@@ -192,7 +163,57 @@
       </listitem>
     </itemizedlist>
   </section>
-  <section>
+  <section id="sn-installer-changes">
+    <title
+>?????????????????? ?? ?????????????????? ??????????????????</title>
+    <itemizedlist>
+      <listitem>
+	<para
+>???????????????? ?????????????????? <command
+>yum</command
+>, ?????? ?????????????????? ?????????????????????? ?????????????????????? ?????? ?????????????????????? ?????????????????????? ??????????????. ?????????????????? ???????????????????????????? ???????????????????????? ?? ???????????????? ?????????????????? ?????????? ???????? ?????????????????? ?? ?????????????? ??????????????. </para>
+      </listitem>
+      <listitem>
+	<para
+>?? ???????? ?????????????? ?????????????????? ?????????????????? ?????????????????? ?????????????????????????? ???????????????????????? ?? ??????????????????????????????, ??????????????????????????, ????????- ?????? ?????????????????????????????????? (SMP, Symmetric Multi Processor) ????????. ?? ???????????????????? ???????????????? ?????????????????????????????? ?????? ???????????????? ?? ?????????????????????????????? ???? ?????? ???????????????????? ???? ??????????????????. </para>
+      </listitem>
+      <listitem>
+	<para
+>?????????????????? ?????????????????? ?????????? ???????? ???????????????????????? ?????? ???????????????? ????????????????. </para>
+      </listitem>
+      <listitem>
+	<para
+>?? ???????? ?????????????? ???????????????????????????? ?????????????? ???????????????????????????? ?????????? <command
+>syslog</command
+>. ?????? ?????? ???????????????????????????? ?????????????? <option
+>syslog=host:port</option
+> ?? ?????????????????????? boot ????????????????????. ?????????????????? ???????? ???? ??????????????????????. </para>
+      </listitem>
+      <listitem>
+	<para
+>?????????????????? ??????????????????????/SELinux ???????????????????? ?? ?????????????????? ?????????? ??????????????????, ???????????????????? <application
+>firstboot</application
+>. </para>
+      </listitem>
+      <listitem>
+	<para
+>?????????????????????? HTML ?????????????? ?? ???????????????? ?????????????????? ???????????? ?????????????????????? ?????? ???????????? ???????????????? <command
+>gtkhtml</command
+> ?????? ???????????? ??????????????????????????. </para>
+      </listitem>
+      <listitem>
+	<para
+>???????????????? Kickstart ?????? ?????????????????????? ?? ???????????? ?? ?????????????????? ?????????? - <filename
+>pykickstart</filename
+>, ???????????????????? ?????????????????? ?????????????? ?? ???????????? ????????????. ?? ???????????????????? ?????????? ??????????????????, ???????????????? ???????????????????????? ?? ???????????????????? ?????????????????? kickstart ?????????????????????? ????????????????. </para>
+      </listitem>
+      <listitem>
+	<para
+>???????? ?? ???????????????????????????????? ???????????????????? ?????????????????? ?????????? ???? ???????????????????????????? ?? ?????????????????? ?????????????????? ?? ?? &FC;. </para>
+      </listitem>
+    </itemizedlist>
+  </section>
+  <section id="sn-install-related-issues">
     <title
 >??????????????, ???????????????????? ??????????????????</title>
     <itemizedlist>
@@ -201,7 +222,6 @@
 >?? ?????????????????? ???????????????????? ?????????????????????????? (???????????????? ?????? ???????????????? LCD-????????????????) ?????? ?????????????? ?????????????????? ?????????????????? &DISTRO; ???? ???????????? ?????????????????????? ?? ????????????????????. ???????????????????? ???????????? ????, ???????????????????????? ?????????????????? ?? ?????????????? ?? ?????????????????? ???????????? ???????????????????? ???????????????? "<command
 >nofb</command
 >". </para>
-
 	<note>
 	  <title
 >??????????????????</title>
@@ -218,8 +238,12 @@
 >VAIO</trademark
 > ?????????? ???????????????????? ????????????????. ?? ???????? ?????????????? ?????????????????????????? ?????????????????? ?? ???????????????? ?? ?????????????????? ???????????? ???????????????????? ?????????????????? ????????????????: </para>
 <screen
-><!-- <remark os="test">(x86)</remark> -->
-<command>pci=off ide1=0x180,0x386</command>
+><!-- <remark os="test"
+>(x86)</remark
+> -->
+<command
+>pci=off ide1=0x180,0x386</command
+>
 </screen>
 	<para
 >???????? ???????????????? ???????????????? ?????????????????? ??????????????????; ?????? ????????????????????, ???? ?????????????????? ????-???? ?????????? ??????????????????, ?????????? ?????????????????? ?????? ???????????? ?????????????? &DISTRO;. </para>


Index: legacy-ru.xml
===================================================================
RCS file: /cvs/docs/release-notes/legacy-ru.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legacy-ru.xml	10 Nov 2005 21:21:08 -0000	1.1
+++ legacy-ru.xml	27 Nov 2005 13:19:24 -0000	1.2
@@ -1,3 +1,60 @@
+<section id="sn-legacy">
+    <title
+>???????????????????? ???? ???????????????????? ??????????????????????</title>
+    
+  <note>
+    <title
+>?????????? <command
+>Slocate</command
+> ?????? ?????????????? ?? ???????? ?????????????? ???? <command
+>mlocate</command
+>.</title>
+    <para
+>???????????????????? ???????????? <command
+>/usr/bin/{locate,updatedb}</command
+> ???????????? <command
+>slocate</command
+> ???????? ???????????????? ???? mlocate. </para>
+  </note>
+    <itemizedlist>
+      <listitem>
+      <para
+>?????????????? <command
+>locate</command
+> ???????????? ???????????????? ?????????????????? ??????????????????????. </para>
+      </listitem>
+    </itemizedlist>
+    <itemizedlist>
+      <listitem>
+      <para
+>???????? <filename
+>/etc/updatedb.conf</filename
+> ?????????????????? ?????? ???????????????????? ?????????????????????? ???????????? </para>
+</listitem
+>. <listitem
+> <para
+>???????????? ???????????????????? ???????????????????????????? ????????????, ?????????????????? ???? ???????????????????? <command
+>slocate</command
+>. </para>
+    </listitem>
+    <listitem>
+      <para
+>???????????????????? <envar
+>DAILY_UPDATE</envar
+> ?????????? ???? ????????????????????????????. </para>
+    </listitem>
+    <listitem>
+      <para
+>?????????????? <command
+>updatedb</command
+> ???? ???????????????????? ?? ????????????????????, ???????????????? ????????????????????????, ???????????????????????? ?????????????? <command
+>updatedb</command
+>, ???????????????? ?????????????????? ??????????????????????. </para>
+      </listitem>
+    </itemizedlist>
+  <para
+>???????????????????? LinuxThreads, ???????????????????? ?? ?????????????? ?????????????? &FC; 4, ?????????? ???? ????????????????. ???????????????????? NPTL ???????????????? ???????????????? ?????????????????????? ?????????????? ?????????????? ?? Red Hat Linux 9. </para>
+</section>
 <!--
 Local variables:
 mode: xml


Index: package-movement-ru.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-movement-ru.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- package-movement-ru.xml	10 Nov 2005 21:21:08 -0000	1.1
+++ package-movement-ru.xml	27 Nov 2005 13:19:24 -0000	1.2
@@ -0,0 +1,1760 @@
+<section id="sn-package-movement">
+  <title
+>?????????????????????? ??????????????</title>
+  <!-- 
+  FIXME
+  Needs updating of entire contents for FC5.
+
+  <para>
+    This command was used to generate the list of package changes.  The
+    backslash <computeroutput
+>\</computeroutput
+> is used to artificially
+    break the line for printing purposes.:
+  </para>
+<screen
+>
+<command>treediff.py dist-fc4 dist-rawhide > /tmp/diff \
+sed -e 's,^,* ,g' -e 's,$,\n,g' /tmp/diff > diffwiki</command>
+</screen>
+  <section>
+    <title
+>Package Changes</title>
+    <para
+>As of 21st September 2005 </para>
+    <para
+>[106429] MAKEDEV-3.19-1 -> [115423] MAKEDEV-3.19-4 </para>
+    <para
+>[111566] <ulink
+	url='/ImageMagick'
+>ImageMagick</ulink
+>-6.2.2.0-2 -> [112246]
+      <ulink url='/ImageMagick'
+>ImageMagick</ulink
+>-6.2.2.0-4 </para>
+    <para
+>[105261] newt-0.51.6-7 -> [117695] newt-0.51.6-8 </para>
+    <para
+>[106878] am-utils-6.0.9-12 -> [117066] am-utils-6.1.1-2
+    </para>
+    <para
+>[108819] amanda-2.4.5-2 -> [115871] amanda-2.4.5-3 </para>
+    <para
+>[112105] anaconda-10.2.1.5-2 -> [118390]
+      anaconda-10.3.0.24-1 </para>
+    <para
+>[105300] aspell-0.50.5-6 -> [114172] aspell-0.60.3-2 </para>
+    <para
+>[108035] aspell-ca-0.50-2 -> [114184] aspell-ca-0.50-4
+    </para>
+    <para
+>[108036] aspell-cs-0.51-2 -> [114270] aspell-cs-0.51-3
+    </para>
+    <para
+>[108038] aspell-da-0.50-11 -> [114276] aspell-da-0.50-12
+    </para>
+    <para
+>[106443] libsoup-2.2.3-2 -> [116988] libsoup-2.2.6.1-1
+    </para>
+    <para
+>[108042] aspell-es-0.50-11 -> [117058] aspell-es-0.50-13
+    </para>
+    <para
+>[108044] aspell-fr-0.50-8 -> [114285] aspell-fr-0.50-9
+    </para>
+    <para
+>[108051] aspell-it-0.53-2 -> [114362] aspell-it-0.53-3
+    </para>
+    <para
+>[108055] aspell-nl-0.50-6 -> [114363] aspell-nl-0.50-7
+    </para>
+    <para
+>[108058] aspell-no-0.50.1-8 -> [114366] aspell-no-0.50.1-9
+    </para>
+    <para
+>[108060] aspell-pl-0.51-3 -> [118018] aspell-pl-0.51-5
+    </para>
+    <para
+>[108061] aspell-sv-0.50-7 -> [114371] aspell-sv-0.50-8
+    </para>
+    <para
+>[107959] at-3.1.8-77_FC4 -> [112026] at-3.1.8-78 </para>
+    <para
+>[108132] gtkhtml3-3.6.2-1 -> [117587] gtkhtml3-3.8.0-1
+    </para>
+    <para
+>[108304] ntp-4.2.0.a.20040617-8 -> [117060]
+      ntp-4.2.0.a.20050816-1 </para>
+    <para
+>[108909] autofs-4.1.4-5 -> [112718] autofs-4.1.4-9 </para>
+    <para
+>[102923] automake-1.9.5-1 -> [114414] automake-1.9.6-1
+    </para>
+    <para
+>[108562] autorun-3.16-1 -> [118091] autorun-3.17-1 </para>
+    <para
+>[105321] awesfx-0.5.0d-2 -> [113536] awesfx-0.5.0d-3 </para>
+    <para
+>[105808] nut-2.0.1-1 -> [114509] nut-2.0.2-1 </para>
+    <para
+>[110344] bash-3.0-31 -> [118423] bash-3.0-34 </para>
+    <para
+>[110908] bind-9.3.1-4 -> [116915] bind-9.3.1-11 </para>
+    <para
+>[111486] binutils-2.15.94.0.2.2-2 -> [116754]
+      binutils-2.16.91.0.2-4 </para>
+    <para
+>[105319] bootparamd-0.17-22.devel -> [116780]
+      bootparamd-0.17-23.devel </para>
+    <para
+>[106988] bug-buddy-2.10.0-1 -> [117633] bug-buddy-2.12.0-1
+    </para>
+    <para
+>[111028] bzip2-1.0.2-16 -> [117182] bzip2-1.0.3-1 </para>
+    <para
+>[106470] pax-3.0-11 -> [116422] pax-3.4-1 </para>
+    <para
+>[109185] <ulink url='/SysVinit'
+>SysVinit</ulink
+>-2.85-39 ->
+      [113360] <ulink url='/SysVinit'
+>SysVinit</ulink
+>-2.85-40 </para>
+    <para
+>[111393] control-center-2.10.1-6 -> [118105]
+      control-center-2.12.0-2 </para>
+    <para
+>[111120] openldap-2.2.23-5 -> [111936] openldap-2.2.26-1
+    </para>
+    <para
+>[110745] cpio-2.6-7 -> [113389] cpio-2.6-8 </para>
+    <para
+>[106419] cracklib-2.8.2-1 -> [111862] cracklib-2.8.3-1
+    </para>
+    <para
+>[104496] bluez-hcidump-1.18-1 -> [115995]
+      bluez-hcidump-1.24-1 </para>
+    <para
+>[104877] ctags-5.5.4-3 -> [115419] ctags-5.5.4-4 </para>
+    <para
+>[108614] cvs-1.11.19-8 -> [116935] cvs-1.11.19-10 </para>
+    <para
+>[108252] cyrus-sasl-2.1.20-5 -> [117833] cyrus-sasl-2.1.21-5
+    </para>
+    <para
+>[109650] pam-0.79-8 -> [118330] pam-0.80-8 </para>
+    <para
+>[109663] dhcp-3.0.2-12 -> [117972] dhcp-3.0.3-6 </para>
+    <para
+>[110743] apr-0.9.6-3 -> [118164] apr-0.9.6-6 </para>
+    <para
+>[110347] e2fsprogs-1.37-4 -> [117739] e2fsprogs-1.38-1
+    </para>
+    <para
+>[104668] diffstat-1.38-2 -> [116208] diffstat-1.38-4 </para>
+    <para
+>[107298] doxygen-1.4.2-1 -> [118248] doxygen-1.4.4-2 </para>
+    <para
+>[110505] dump-0.4b40-2 -> [113542] dump-0.4b40-4 </para>
+    <para
+>[110508] eject-2.0.13-15 -> [117061] eject-2.1.2-1 </para>
+    <para
+>[110262] parted-1.6.22-2 -> [117238] parted-1.6.24-1 </para>
+    <para
+>[110911] emacs-21.4-5 -> [114092] emacs-21.4-7 </para>
+    <para
+>[111808] esound-0.2.35-5 -> [114327] esound-0.2.36-1 </para>
+    <para
+>[105304] passwd-0.69-2 -> [112701] passwd-0.70-1 </para>
+    <para
+>[106286] fetchmail-6.2.5-7 -> [114678] fetchmail-6.2.5.2-1
+    </para>
+    <para
+>[109759] patch-2.5.4-24 -> [117794] patch-2.5.4-29 </para>
+    <para
+>[111272] filesystem-2.3.4-1 -> [116817] filesystem-2.3.5-1
+    </para>
+    <para
+>[106330] findutils-4.2.20-1 -> [117490] findutils-4.2.25-2
+    </para>
+    <para
+>[105012] finger-0.17-28 -> [113967] finger-0.17-29 </para>
+    <para
+>[105097] freetype-2.1.9-2 -> [116586] freetype-2.1.9-4
+    </para>
+    <para
+>[111401] ftp-0.17-26 -> [117241] ftp-0.17-29 </para>
+    <para
+>[104499] gawk-3.1.4-5 -> [118359] gawk-3.1.5-2 </para>
+    <para
+>[111099] gcc-4.0.0-8 -> [118294] gcc-4.0.1-14 </para>
+    <para
+>[108458] gd-2.0.33-2 -> [117628] gd-2.0.33-3 </para>
+    <para
+>[109684] gdb-6.3.0.0-1.21 -> [117661] gdb-6.3.0.0-1.65
+    </para>
+    <para
+>[106626] gettext-0.14.3-1 -> [116274] gettext-0.14.5-1
+    </para>
+    <para
+>[111402] gdm-2.6.0.8-16 -> [117776] gdm-2.8.0.4-1 </para>
+    <para
+>[108333] gedit-2.10.2-3 -> [117719] gedit-2.12.0-1 </para>
+    <para
+>[110935] perl-5.8.6-15 -> [117489] perl-5.8.7-0.3.fc5
+    </para>
+    <para
+>[107237] gok-1.0.3-1 -> [116496] gok-1.0.5-4 </para>
+    <para
+>[110356] php-5.0.4-10 -> [118097] php-5.0.5-3 </para>
+    <para
+>[110581] gimp-2.2.7-4 -> [116538] gimp-2.2.8-3 </para>
+    <para
+>[111654] gnome-applets-2.10.1-9 -> [117721]
+      gnome-applets-2.12.0-1 </para>
+    <para
+>[111691] glibc-2.3.5-10 -> [117966] glibc-2.3.90-12 </para>
+    <para
+>[111104] gnome-games-2.10.0-5 -> [117724]
+      gnome-games-2.12.0-1 </para>
+    <para
+>[111214] gnome-media-2.10.2-4 -> [117726]
+      gnome-media-2.12.0-1 </para>
+    <para
+>[106508] kdeadmin-3.4.0-1 -> [118336] kdeadmin-3.4.2-2
+    </para>
+    <para
+>[110919] gnome-utils-2.10.0-3 -> [117738]
+      gnome-utils-2.12.0-1 </para>
+    <para
+>[110246] gnupg-1.4.1-3 -> [116120] gnupg-1.4.2-3 </para>
+    <para
+>[104528] gnuplot-4.0.0-7 -> [117403] gnuplot-4.0.0-8 </para>
+    <para
+>[104506] gperf-3.0.1-6 -> [115552] gperf-3.0.1-7 </para>
+    <para
+>[104548] grep-2.5.1-48 -> [113236] grep-2.5.1-50 </para>
+    <para
+>[108057] xinitrc-4.0.18-1 -> [111974] xinitrc-4.0.19-1
+    </para>
+    <para
+>[104544] guile-1.6.7-2 -> [117402] guile-1.6.7-4 </para>
+    <para
+>[104475] hdparm-5.9-1 -> [112183] hdparm-6.1-1 </para>
+    <para
+>[111501] initscripts-8.11.1-1 -> [117977] initscripts-8.14-1
+    </para>
+    <para
+>[107880] inn-2.4.2-3 -> [115559] inn-2.4.2-4 </para>
+    <para
+>[106114] iproute-2.6.11-1 -> [118247] iproute-2.6.14-3
+    </para>
+    <para
+>[106499] iptables-1.3.0-2 -> [114287] iptables-1.3.2-1
+    </para>
+    <para
+>[107881] iputils-20020927-22 -> [117698] iputils-20020927-26
+    </para>
+    <para
+>[111656] isdn4k-utils-3.2-28 -> [115009] isdn4k-utils-3.2-32
+    </para>
+    <para
+>[105032] joe-3.1-8 -> [112056] joe-3.3-1 </para>
+    <para
+>[108237] kdebase-3.4.0-5 -> [118422] kdebase-3.4.2-5 </para>
+    <para
+>[106532] kdegames-3.4.0-1 -> [116019] kdegames-3.4.2-1
+    </para>
+    <para
+>[107198] kdegraphics-3.4.0-2 -> [117508] kdegraphics-3.4.2-3
+    </para>
+    <para
+>[104526] openobex-1.0.1-3 -> [111937] openobex-1.0.1-4
+    </para>
+    <para
+>[107226] kdemultimedia-3.4.0-2 -> [115553]
+      kdemultimedia-3.4.2-1 </para>
+    <para
+>[106551] kdeutils-3.4.0-1 -> [117699] kdeutils-3.4.2-2
+    </para>
+    <para
+>[105322] minicom-2.00.0-21 -> [114175] minicom-2.1-1 </para>
+    <para
+>[112015] kernel-2.6.11-1.1369_FC4 -> [118394]
+      kernel-2.6.13-1.1565_FC5 </para>
+    <para
+>[108707] libbtctl-0.4.1-7 -> [114382] libbtctl-0.4.1-8
+    </para>
+    <para
+>[107067] krb5-1.4-3 -> [118053] krb5-1.4.2-4 </para>
+    <para
+>[106252] krbafs-1.2.2-7 -> [115422] krbafs-1.2.2-8 </para>
+    <para
+>[111032] kudzu-1.1.116.2-2 -> [118290] kudzu-1.2.7-1 </para>
+    <para
+>[105596] lam-7.1.1-3 -> [115564] lam-7.1.1-7.FC5 </para>
+    <para
+>[105047] less-382-7 -> [117533] less-382-8 </para>
+    <para
+>[104599] libieee1284-0.2.9-2 -> [114409] libieee1284-0.2.9-3
+    </para>
+    <para
+>[106523] libtermcap-2.0.8-41 -> [115467] libtermcap-2.0.8-42
+    </para>
+    <para
+>[110440] libtiff-3.7.1-6 -> [113273] libtiff-3.7.2-1 </para>
+    <para
+>[109070] libtool-1.5.16.multilib2-1 -> [118098]
+      libtool-1.5.20-3 </para>
+    <para
+>[104597] lm_sensors-2.8.8-5 -> [117365] lm_sensors-2.9.1-4
+    </para>
+    <para
+>[105199] lockdev-1.0.1-7 -> [118409] lockdev-1.0.1-9 </para>
+    <para
+>[107338] logrotate-3.7.1-10 -> [117629] logrotate-3.7.2-3
+    </para>
+    <para
+>[110353] lsof-4.74-7 -> [118297] lsof-4.76-1 </para>
+    <para
+>[108835] dovecot-0.99.14-4.fc4 -> [114740]
+      dovecot-0.99.14-6.fc5 </para>
+    <para
+>[106781] make-3.80-7 -> [116850] make-3.80-8 </para>
+    <para
+>[104365] distcache-1.4.5-7 -> [115345] distcache-1.4.5-11
+    </para>
+    <para
+>[107530] man-pages-1.67-7 -> [118017] man-pages-2.07-5
+    </para>
+    <para
+>[93204] man-pages-cs-0.16-4 -> [115882] man-pages-cs-0.16-5
+    </para>
+    <para
+>[93194] man-pages-de-0.4-9 -> [115873] man-pages-de-0.4-10
+    </para>
+    <para
+>[108613] man-pages-ja-20050415-1 -> [116660]
+      man-pages-ja-20050815-1 </para>
+    <para
+>[110081] mx4j-2.1.0-1jpp_7fc -> [114677] mx4j-3.0.1-1jpp_5fc
+    </para>
+    <para
+>[109945] mc-4.6.1a-0.9 -> [118021] mc-4.6.1a-0.15 </para>
+    <para
+>[101562] desktop-file-utils-0.10-1 -> [117302]
+      desktop-file-utils-0.10-3 </para>
+    <para
+>[111217] redhat-artwork-0.122-10 -> [116975]
+      redhat-artwork-0.128-1 </para>
+    <para
+>[104435] mikmod-3.1.6-34 -> [112072] mikmod-3.1.6-35 </para>
+    <para
+>[110923] mkinitrd-4.2.15-1 -> [116471] mkinitrd-4.2.21-1
+    </para>
+    <para
+>[110244] gimp-print-4.2.7-7 -> [116481] gimp-print-4.2.7-12
+    </para>
+    <para
+>[111409] rhpl-0.167-1 -> [118384] rhpl-0.174-1 </para>
+    <para
+>[108728] glade2-2.10.0-1 -> [116544] glade2-2.10.0-2 </para>
+    <para
+>[107181] pyxf86config-0.3.19-4 -> [114209]
+      pyxf86config-0.3.19-6 </para>
+    <para
+>[105582] arptables_jf-0.0.8-4 -> [116740]
+      arptables_jf-0.0.8-6 </para>
+    <para
+>[108583] fontconfig-2.2.3-13 -> [114861] fontconfig-2.3.2-1
+    </para>
+    <para
+>[108241] oprofile-0.8.2-4 -> [114916] oprofile-0.9.1-2
+    </para>
+    <para
+>[104605] mtr-0.69-3 -> [117503] mtr-0.69-4 </para>
+    <para
+>[105384] mutt-1.4.2.1-2 -> [117134] mutt-1.4.2.1-3 </para>
+    <para
+>[106486] kdeedu-3.4.0-1 -> [118428] kdeedu-3.4.2-3 </para>
+    <para
+>[111281] httpd-2.0.54-10 -> [115215] httpd-2.0.54-12 </para>
+    <para
+>[109664] libwpd-0.8.1-1 -> [117298] libwpd-0.8.3-1 </para>
+    <para
+>[109161] ncurses-5.4-17 -> [115668] ncurses-5.4-18 </para>
+    <para
+>[109016] net-tools-1.60-52 -> [115663] net-tools-1.60-56
+    </para>
+    <para
+>[106997] rdesktop-1.4.0-2 -> [113322] rdesktop-1.4.1-1.fc5
+    </para>
+    <para
+>[106852] redhat-rpm-config-8.0.34-1 -> [116588]
+      redhat-rpm-config-8.0.39-1 </para>
+    <para
+>[104517] compat-slang-1.4.5-10 -> [115421]
+      compat-slang-1.4.5-11 </para>
+    <para
+>[111646] nfs-utils-1.0.7-8 -> [117732] nfs-utils-1.0.7-16
+    </para>
+    <para
+>[104611] rarpd-ss981107-20 -> [114929] rarpd-ss981107-22
+    </para>
+    <para
+>[111216] nss_ldap-234-4 -> [117936] nss_ldap-241-1 </para>
+    <para
+>[101793] squirrelmail-1.4.4-2 -> [117917]
+      squirrelmail-1.4.6-0.cvs20050812.2.fc5 </para>
+    <para
+>- perl-Filter-1.30-7 </para>
+    <para
+>- perl-Filter-Simple-0.79-5 </para>
+    <para
+>[111400] libxslt-1.1.14-2 -> [117480] libxslt-1.1.15-1
+    </para>
+    <para
+>[111035] pam_krb5-2.1.7-3 -> [115747] pam_krb5-2.1.8-2
+    </para>
+    <para
+>[106493] file-roller-2.10.0-1 -> [117656]
+      file-roller-2.12.0-1 </para>
+    <para
+>[106353] pyOpenSSL-0.6-1.p24.4 -> [117052]
+      pyOpenSSL-0.6-1.p24.6 </para>
+    <para
+>[104627] rdist-6.1.5-40 -> [111944] rdist-6.1.5-41 </para>
+    <para
+>[110926] spamassassin-3.0.3-4.fc4 -> [118074]
+      spamassassin-3.1.0-1.fc5 </para>
+    <para
+>[105950] pilot-link-0.12.0-0.pre2.0 -> [117233]
+      pilot-link-0.12.0-0.pre4.5 </para>
+    <para
+>[106474] star-1.5a54-2 -> [117115] star-1.5a65-1 </para>
+    <para
+>[111515] net-snmp-5.2.1-12 -> [118322] net-snmp-5.2.1.2-3
+    </para>
+    <para
+>[96116] ppp-2.4.2-7 -> [115416] ppp-2.4.3-3 </para>
+    <para
+>[110366] vlock-1.3-19 -> [115661] vlock-1.3-20 </para>
+    <para
+>[110359] procps-3.2.5-6 -> [117548] procps-3.2.5-7 </para>
+    <para
+>[105210] psmisc-21.5-4 -> [117707] psmisc-21.6-1 </para>
+    <para
+>[105614] pvm-3.4.5-3_FC4 -> [111812] pvm-3.4.5-5 </para>
+    <para
+>[105105] bogl-0.1.18-7 -> [118318] bogl-0.1.18-10 </para>
+    <para
+>[108185] gnopernicus-0.10.6-1 -> [117638]
+      gnopernicus-0.11.6-1 </para>
+    <para
+>[110883] qt-3.3.4-14 -> [118419] qt-3.3.5-2 </para>
+    <para
+>[104494] ksh-20050202-1 -> [111912] ksh-20050202-3 </para>
+    <para
+>[108083] quota-3.12-6 -> [116742] quota-3.12-7 </para>
+    <para
+>[101735] gnome-speech-0.3.6-1 -> [115904]
+      gnome-speech-0.3.7-1 </para>
+    <para
+>[111387] openoffice.org-1.9.104-2 -> [118196]
+      openoffice.org-1.9.130-1.2.fc5 </para>
+    <para
+>[105350] rp-pppoe-3.5-27 -> [116414] rp-pppoe-3.5-30 </para>
+    <para
+>[111410] rpm-4.4.1-21 -> [117156] rpm-4.4.2-4 </para>
+    <para
+>[110925] rsync-2.6.4-3 -> [115264] rsync-2.6.6-2 </para>
+    <para
+>[104630] rusers-0.17-43 -> [117620] rusers-0.17-45 </para>
+    <para
+>[109533] samba-3.0.14a-2 -> [117971] samba-3.0.20-2 </para>
+    <para
+>- sash-3.7-6 </para>
+    <para
+>[110268] sendmail-8.13.4-2 -> [118253] sendmail-8.13.5-1
+    </para>
+    <para
+>[111123] setup-2.5.44-1 -> [117568] setup-2.5.47-1.1 </para>
+    <para
+>[111408] shadow-utils-4.0.7-9 -> [117343]
+      shadow-utils-4.0.12-2 </para>
+    <para
+>[106465] slang-1.4.9-17 -> [117492] slang-1.4.9-19 </para>
+    <para
+>[108441] slocate-2.7-22 -> [118067] slocate-2.7-27 </para>
+    <para
+>[105316] slrn-0.9.8.1-4 -> [114996] slrn-0.9.8.1-5 </para>
+    <para
+>[110665] squid-2.5.STABLE9-7 -> [117506]
+      squid-2.5.STABLE10-4 </para>
+    <para
+>[106754] strace-4.5.11-1 -> [115667] strace-4.5.13-1 </para>
+    <para
+>[108145] sudo-1.6.8p8-1 -> [118285] sudo-1.6.8p9-4 </para>
+    <para
+>[93654] switchdesk-4.0.6-3 -> [114432] switchdesk-4.0.7-1
+    </para>
+    <para
+>[111041] sysklogd-1.4.1-30 -> [117045] sysklogd-1.4.1-33
+    </para>
+    <para
+>[112528] syslinux-3.08-2 -> [117044] syslinux-3.10-2 </para>
+    <para
+>[110362] sysreport-1.4.1-2 -> [112702] sysreport-1.4.1-4
+    </para>
+    <para
+>[105297] sysstat-5.0.5-9.fc -> [116738] sysstat-5.0.5-11.fc
+    </para>
+    <para
+>[108370] tar-1.15.1-5 -> [117554] tar-1.15.1-10 </para>
+    <para
+>[109655] tcpdump-3.8.2-12 -> [116178] tcpdump-3.9.3-3
+    </para>
+    <para
+>[106994] tcsh-6.14-1 -> [115897] tcsh-6.14-5 </para>
+    <para
+>[106284] termcap-5.4-4 -> [118201] termcap-5.4-7 </para>
+    <para
+>[110274] tetex-3.0-4 -> [116781] tetex-3.0-6 </para>
+    <para
+>[106019] texinfo-4.8-4 -> [112242] texinfo-4.8-6 </para>
+    <para
+>[109641] jwhois-3.2.2-14 -> [115889] jwhois-3.2.3-2 </para>
+    <para
+>[110348] elfutils-0.108-1 -> [117517] elfutils-0.115-1
+    </para>
+    <para
+>[105286] expect-5.43.0-1 -> [111871] expect-5.43.0-2 </para>
+    <para
+>[105014] traceroute-1.4a12-26 -> [116290]
+      traceroute-1.4a12-27 </para>
+    <para
+>[108240] subversion-1.1.4-3 -> [117737] subversion-1.2.3-3
+    </para>
+    <para
+>- schedutils-1.4.0-4 </para>
+    <para
+>[106314] umb-scheme-3.2-38 -> [117616] umb-scheme-3.2-39
+    </para>
+    <para
+>[104847] units-1.80-12 -> [114388] units-1.85-1 </para>
+    <para
+>[107560] quagga-0.98.3-2 -> [117222] quagga-0.98.5-2 </para>
+    <para
+>[105298] unzip-5.51-10 -> [115669] unzip-5.51-12 </para>
+    <para
+>[109681] util-linux-2.12p-9.3 -> [117509]
+      util-linux-2.13-0.3.pre2 </para>
+    <para
+>[108550] uucp-1.07-9 -> [114161] uucp-1.07-11 </para>
+    <para
+>[109140] vim-6.3.071-3 -> [117700] vim-6.3.086-5 </para>
+    <para
+>[108347] vixie-cron-4.1-33 -> [113831] vixie-cron-4.1-36.FC5
+    </para>
+    <para
+>[106439] gtksourceview-1.2.0-1 -> [117747]
+      gtksourceview-1.4.1-1 </para>
+    <para
+>[109142] vnc-4.1.1-10 -> [117547] vnc-4.1.1-17 </para>
+    <para
+>- w3c-libwww-5.4.0-13 </para>
+    <para
+>[104493] wget-1.9.1-22 -> [117731] wget-1.10.1-7 </para>
+    <para
+>[100923] wireless-tools-28-0.pre4.3 -> [117952]
+      wireless-tools-28-0.pre9.5 </para>
+    <para
+>[104447] neon-0.24.7-6 -> [118267] neon-0.24.7-7 </para>
+    <para
+>[108529] desktop-printing-0.18-10 -> [116635]
+      desktop-printing-0.19-2 </para>
+    <para
+>[109757] libselinux-1.23.10-2 -> [118218] libselinux-1.26-6
+    </para>
+    <para
+>[110975] xfig-3.2.4-11 -> [114406] xfig-3.2.4-13 </para>
+    <para
+>[106604] ttmkfdir-3.0.9-16 -> [115679] ttmkfdir-3.0.9-17
+    </para>
+    <para
+>[106293] ckermit-8.0.211-1 -> [117400] ckermit-8.0.211-3
+    </para>
+    <para
+>[111493] coreutils-5.2.1-48 -> [117826] coreutils-5.2.1-55
+    </para>
+    <para
+>[109668] gstreamer-0.8.10-1 -> [117857] gstreamer-0.8.11-1
+    </para>
+    <para
+>[110247] gstreamer-plugins-0.8.8-6 -> [117858]
+      gstreamer-plugins-0.8.11-1 </para>
+    <para
+>[108260] gnome-icon-theme-2.10.1-4 -> [117725]
+      gnome-icon-theme-2.12.0-1 </para>
+    <para
+>[111290] xpdf-3.00-19 -> [116734] xpdf-3.01-1 </para>
+    <para
+>[104699] xsane-0.95-3 -> [112799] xsane-0.95-4 </para>
+    <para
+>[110438] xscreensaver-4.21-4 -> [118219]
+      xscreensaver-4.22-16 </para>
+    <para
+>[106575] nautilus-cd-burner-2.10.0-2 -> [117669]
+      nautilus-cd-burner-2.12.0-1 </para>
+    <para
+>- hpoj-0.91-13 </para>
+    <para
+>[108081] ypserv-2.13-6 -> [114545] ypserv-2.13-7 </para>
+    <para
+>[108065] zlib-1.2.2.2-3 -> [117021] zlib-1.2.3-1 </para>
+    <para
+>[110759] gthumb-2.6.5-1 -> [117742] gthumb-2.6.7-1 </para>
+    <para
+>[110698] alsa-utils-1.0.9rc2-2 -> [116939]
+      alsa-utils-1.0.9rf-5 </para>
+    <para
+>[111418] libgnomeprint22-2.10.3-1 -> [117675]
+      libgnomeprint22-2.12.0-1 </para>
+    <para
+>[106542] libgnomeprintui22-2.10.1-1 -> [117676]
+      libgnomeprintui22-2.12.0-1 </para>
+    <para
+>[106076] rhythmbox-0.8.8-2 -> [117443]
+      rhythmbox-0.9.0.cvs20050902-1 </para>
+    <para
+>[104518] libgsf-1.11.1-2 -> [118324] libgsf-1.12.3-1 </para>
+    <para
+>[104645] libmng-1.0.9-1 -> [112902] libmng-1.0.9-2 </para>
+    <para
+>[104492] bluez-libs-2.15-1 -> [117512] bluez-libs-2.20-1
+    </para>
+    <para
+>[109626] bluez-utils-2.15-7 -> [117513] bluez-utils-2.20-1
+    </para>
+    <para
+>[109284] gnome-themes-2.10.1-2 -> [117637]
+      gnome-themes-2.12.0-1 </para>
+    <para
+>[106333] lv-4.51-5 -> [113778] lv-4.51-6 </para>
+    <para
+>[106337] nkf-2.04-5 -> [113596] nkf-2.05-1 </para>
+    <para
+>- nvi-m17n-1.79-20040401.23 </para>
+    <para
+>[108025] ruby-1.8.2-7 -> [118404] ruby-1.8.3-1 </para>
+    <para
+>[109083] stunnel-4.08-2 -> [113854] stunnel-4.11-1 </para>
+    <para
+>[108440] 4Suite-1.0-8.b1 -> [112368] 4Suite-1.0-9.b1 </para>
+    <para
+>[106235] nss_db-2.2-31 -> [117271] nss_db-2.2-33 </para>
+    <para
+>[111212] eclipse-3.1.0_fc-0.M6.22 -> [115167]
+      eclipse-3.1.0_fc-12 </para>
+    <para
+>[111394] dbus-0.33-3 -> [117773] dbus-0.50-1 </para>
+    <para
+>[106803] a2ps-4.13b-46 -> [111842] a2ps-4.13b-47 </para>
+    <para
+>[109643] libuser-0.53.7-1 -> [117997] libuser-0.54-1 </para>
+    <para
+>[109886] gtk-doc-1.3-2 -> [113533] gtk-doc-1.4-1 </para>
+    <para
+>[109144] perl-DBD-MySQL-2.9007-1 -> [117217]
+      perl-DBD-MySQL-3.0002-1 </para>
+    <para
+>[111122] perl-DBD-Pg-1.41-2 -> [113244] perl-DBD-Pg-1.43-1
+    </para>
+    <para
+>[105244] kdbg-1.2.10-2 -> [114272] kdbg-2.0.0-1 </para>
+    <para
+>[106810] kdepim-3.4.0-4 -> [117234] kdepim-3.4.2-3 </para>
+    <para
+>[106772] xdelta-1.1.3-16 -> [117821] xdelta-1.1.3-17 </para>
+    <para
+>[107253] pkgconfig-0.15.0-6 -> [116158] pkgconfig-0.18.1-4
+    </para>
+    <para
+>[108628] kdesdk-3.4.0-3 -> [116008] kdesdk-3.4.2-1 </para>
+    <para
+>[106503] kde-i18n-3.4.0-1 -> [116284] kde-i18n-3.4.2-1
+    </para>
+    <para
+>[111302] hotplug-2004_09_23-7 -> [118092]
+      hotplug-2004_09_23-10 </para>
+    <para
+>[112023] fedora-release-4-2 -> [113067]
+      fedora-release-4-rawhide </para>
+    <para
+>[108436] xterm-200-6 -> [118082] xterm-200-9 </para>
+    <para
+>[106145] ppc64-utils-0.7-9 -> [118408] ppc64-utils-0.7-11
+    </para>
+    <para
+>[104559] htdig-3.2.0b6-5 -> [117484] htdig-3.2.0b6-6 </para>
+    <para
+>- libgal2-2.4.2-4 </para>
+    <para
+>[110442] gaim-1.3.0-1.fc4 -> [118167] gaim-1.5.0-5.fc5
+    </para>
+    <para
+>[108062] aspell-en-0.51-12 -> [114279] aspell-en-6.0-1
+    </para>
+    <para
+>[108357] freeradius-1.0.2-2 -> [114495] freeradius-1.0.4-2
+    </para>
+    <para
+>[110988] devhelp-0.10-1 -> [116721] devhelp-0.10-5 </para>
+    <para
+>[106525] kdebindings-3.4.0-1 -> [116107] kdebindings-3.4.2-1
+    </para>
+    <para
+>[110439] nautilus-2.10.0-4 -> [117668] nautilus-2.12.0-1
+    </para>
+    <para
+>[111391] boost-1.32.0-6 -> [116965] boost-1.33.0-3 </para>
+    <para
+>[104523] nano-1.3.5-0.20050302 -> [117495] nano-1.3.8-1
+    </para>
+    <para
+>[110577] epiphany-1.6.1-3 -> [117510] epiphany-1.8.0-1
+    </para>
+    <para
+>[111496] yum-2.3.2-7 -> [118230] yum-2.4.0-3 </para>
+    <para
+>[104625] GConf-1.0.9-16 -> [115534] GConf-1.0.9-17 </para>
+    <para
+>[105438] g-wrap-1.3.4-8 -> [113627] g-wrap-1.3.4-9 </para>
+    <para
+>[105029] pcre-5.0-4 -> [117019] pcre-6.3-1 </para>
+    <para
+>[103293] pychecker-0.8.14-3 -> [117907] pychecker-0.8.16-1
+    </para>
+    <para
+>[107295] gnome-bluetooth-0.5.1-12 -> [116637]
+      gnome-bluetooth-0.5.1-14 </para>
+    <para
+>[110227] setarch-1.7-3 -> [113328] setarch-1.8-1 </para>
+    <para
+>[107662] kdeaddons-3.4.0-2 -> [116097] kdeaddons-3.4.2-1
+    </para>
+    <para
+>[105264] MyODBC-2.50.39-24 -> [116340] MyODBC-2.50.39-25
+    </para>
+    <para
+>[108719] nmap-3.81-3 -> [118008] nmap-3.93-1 </para>
+    <para
+>[107878] glib2-2.6.4-1 -> [116932] glib2-2.8.1-1 </para>
+    <para
+>[106280] m2crypto-0.13-2 -> [117174] m2crypto-0.15-1 </para>
+    <para
+>[105135] pango-1.8.1-2 -> [116700] pango-1.10.0-1 </para>
+    <para
+>[106004] atk-1.9.1-1 -> [117631] atk-1.10.3-1 </para>
+    <para
+>[110350] gtk2-2.6.7-4 -> [117200] gtk2-2.8.3-1 </para>
+    <para
+>[110963] logwatch-6.0.1-2 -> [118256] logwatch-6.1.2-4
+    </para>
+    <para
+>[107440] libxml2-2.6.19-1 -> [117989] libxml2-2.6.22-1
+    </para>
+    <para
+>[107238] gnome-mag-0.12.0-2 -> [116495] gnome-mag-0.12.1-2
+    </para>
+    <para
+>[109656] tzdata-2005i-2 -> [117537] tzdata-2005m-2 </para>
+    <para
+>[105136] ddd-3.3.10-2 -> [112263] ddd-3.3.11-1 </para>
+    <para
+>[111516] ethereal-0.10.11-2 -> [118418] ethereal-0.10.12-7
+    </para>
+    <para
+>[105946] mrtg-2.11.1-3 -> [117906] mrtg-2.12.2-2 </para>
+    <para
+>[109779] curl-7.13.1-3 -> [112559] curl-7.14.0-1 </para>
+    <para
+>[110585] mozilla-1.7.8-2 -> [118143] mozilla-1.7.11-5
+    </para>
+    <para
+>[104474] cdrdao-1.1.9-9 -> [114286] cdrdao-1.2.0-1 </para>
+    <para
+>[111152] policycoreutils-1.23.10-2 -> [118399]
+      policycoreutils-1.27.1-1 </para>
+    <para
+>[108677] selinux-doc-1.19.5-1 -> [118233] selinux-doc-1.22-1
+    </para>
+    <para
+>[108338] checkpolicy-1.23.1-1 -> [118421]
+      checkpolicy-1.27.2-1 </para>
+    <para
+>[107547] sound-juicer-2.10.1-1 -> [116671]
+      sound-juicer-2.11.91-1 </para>
+    <para
+>[104852] mod_auth_mysql-2.6.1-4 -> [112597]
+      mod_auth_mysql-2.9.0-1 </para>
+    <para
+>[106515] kdeartwork-3.4.0-1 -> [116101] kdeartwork-3.4.2-1
+    </para>
+    <para
+>[111390] setools-2.1.0-5 -> [118333] setools-2.1.2-1 </para>
+    <para
+>[111060] grub-0.95-13 -> [114871] grub-0.95-15 </para>
+    <para
+>[110652] openssh-4.0p1-3 -> [117588] openssh-4.2p1-1 </para>
+    <para
+>[108233] gnucash-1.8.11-3 -> [117839] gnucash-1.8.11-4
+    </para>
+    <para
+>[108697] MySQL-python-1.2.0-1 -> [115666]
+      MySQL-python-1.2.0-2 </para>
+    <para
+>[106774] PyQt-3.14.1-1 ->
+      [117928] PyQt-3.15-1 </para>
+    <para
+>[106773] sip-4.2.1-1 -> [117925] sip-4.3.1-1 </para>
+    <para
+>[109146] jpilot-0.99.8-0.pre8.4 -> [116645]
+      jpilot-0.99.8-0.pre10.2 </para>
+    <para
+>[108932] lftp-3.1.3-1 -> [117026] lftp-3.3.0-1 </para>
+    <para
+>[107870] cdrtools-2.01.1-9 -> [117294] cdrtools-2.01.1-10
+    </para>
+    <para
+>- apel-10.6-6 </para>
+    <para
+>[107986] mysql-4.1.11-2 -> [116941] mysql-4.1.12-3 </para>
+    <para
+>[108427] tmpwatch-2.9.3-1 -> [112807] tmpwatch-2.9.4-1
+    </para>
+    <para
+>[107682] kdenetwork-3.4.0-3 -> [116293] kdenetwork-3.4.2-1
+    </para>
+    <para
+>[111395] fedora-logos-1.1.31-1 -> [117762]
+      fedora-logos-1.1.31-2 </para>
+    <para
+>[100527] junit-3.8.1-3jpp_4fc -> [112932]
+      junit-3.8.1-3jpp_5fc </para>
+    <para
+>[105492] xmlsec1-1.2.7-4 -> [118326] xmlsec1-1.2.9-1 </para>
+    <para
+>[104606] openCryptoki-2.1.5-9 -> [117535]
+      openCryptoki-2.1.5-10 </para>
+    <para
+>[110363] system-config-bind-4.0.0-16_FC4 -> [116458]
+      system-config-bind-4.0.0-30_FC5 </para>
+    <para
+>[110056] system-config-date-1.7.18-1 -> [115786]
+      system-config-date-1.7.99.0-1 </para>
+    <para
+>[109174] system-config-keyboard-1.2.6-2 -> [118188]
+      system-config-keyboard-1.2.6-3 </para>
+    <para
+>[109127] system-config-kickstart-2.5.22-2 -> [118045]
+      system-config-kickstart-2.5.24-1 </para>
+    <para
+>- system-config-mouse-1.2.11-1 </para>
+    <para
+>[108705] system-config-netboot-0.1.14-1 -> [116895]
+      system-config-netboot-0.1.30-1_FC5 </para>
+    <para
+>[110270] system-config-nfs-1.3.10-1 -> [113615]
+      system-config-nfs-1.3.11-1 </para>
+    <para
+>[110775] system-config-printer-0.6.131-1 -> [117714]
+      system-config-printer-0.6.142-1 </para>
+    <para
+>[110889] system-config-securitylevel-1.5.8-1 -> [116959]
+      system-config-securitylevel-1.6.4-1 </para>
+    <para
+>[110271] system-config-services-0.8.25-1 -> [116537]
+      system-config-services-0.8.26-1 </para>
+    <para
+>[111388] system-config-soundcard-1.2.11-5 -> [116656]
+      system-config-soundcard-1.2.12-5 </para>
+    <para
+>[111429] system-config-display-1.0.29-1 -> [117812]
+      system-config-display-1.0.31-1 </para>
+    <para
+>[111664] alsa-lib-1.0.9rc4-2 -> [114503] alsa-lib-1.0.9rf-3
+    </para>
+    <para
+>[105652] tcl-8.4.9-3 -> [113371] tcl-8.4.11-1 </para>
+    <para
+>[105658] tk-8.4.9-3 -> [113372] tk-8.4.11-1 </para>
+    <para
+>[109302] lvm2-2.01.08-2.1 -> [118142] lvm2-2.01.14-2 </para>
+    <para
+>[110929] device-mapper-1.01.02-1.0 -> [115634]
+      device-mapper-1.01.04-1.0 </para>
+    <para
+>[108262] libgnomecups-0.2.0-2 -> [117671]
+      libgnomecups-0.2.1-1 </para>
+    <para
+>[109132] tvtime-0.9.15-7 -> [117915] tvtime-1.0.1-1 </para>
+    <para
+>- hpijs-1.7.1-3 </para>
+    <para
+>[111138] shared-mime-info-0.16-3 -> [112690]
+      shared-mime-info-0.16-4 </para>
+    <para
+>[110914] evolution-data-server-1.2.2-3 -> [118144]
+      evolution-data-server-1.4.0-2 </para>
+    <para
+>[106495] gnome-keyring-0.4.2-1 -> [117659]
+      gnome-keyring-0.4.4-1 </para>
+    <para
+>[111218] udev-058-1 -> [118405] udev-069-4 </para>
+    <para
+>- pcmcia-cs-3.2.8-4.12 </para>
+    <para
+>- iiimf-le-xcin-0.1.10-1 </para>
+    <para
+>[109118] gnome-netstatus-2.10.0-4 -> [116639]
+      gnome-netstatus-2.11.90-2 </para>
+    <para
+>[110265] perl-XML-NamespaceSupport-1.08-7 ->
+      [117865] perl-XML-NamespaceSupport-1.09-1 </para>
+    <para
+>[107102] memtest86+-1.55.1-1 -> [113262] memtest86+-1.60-1
+    </para>
+    <para
+>[100526] antlr-2.7.4-2jpp_1fc -> [112867]
+      antlr-2.7.4-2jpp_2fc </para>
+    <para
+>[111283] jakarta-commons-beanutils-1.7.0-1jpp_4fc ->
+      [114381] jakarta-commons-beanutils-1.7.0-2jpp_2fc </para>
+    <para
+>[111285] jakarta-commons-collections-3.1-1jpp_4fc ->
+      [114380] jakarta-commons-collections-3.1-2jpp_2fc </para>
+    <para
+>[101451] jakarta-commons-dbcp-1.2.1-3jpp_1fc -> [112880]
+      jakarta-commons-dbcp-1.2.1-3jpp_2fc </para>
+    <para
+>[111286] jakarta-commons-digester-1.6-2jpp_4fc -> [114394]
+      jakarta-commons-digester-1.6-2jpp_6fc </para>
+    <para
+>[111288] jakarta-commons-logging-1.0.4-2jpp_4fc -> [114180]
+      jakarta-commons-logging-1.0.4-2jpp_6fc </para>
+    <para
+>[111289] jakarta-commons-modeler-1.1-3jpp_4fc -> [114487]
+      jakarta-commons-modeler-1.1-4jpp_2fc </para>
+    <para
+>[101447] jakarta-commons-pool-1.2-2jpp_1fc -> [112885]
+      jakarta-commons-pool-1.2-2jpp_2fc </para>
+    <para
+>[101435] jakarta-commons-validator-1.1.3-1jpp_1fc ->
+      [112887] jakarta-commons-validator-1.1.3-1jpp_2fc </para>
+    <para
+>[100530] jdepend-2.6-2jpp_3fc -> [112928]
+      jdepend-2.6-2jpp_4fc </para>
+    <para
+>[111423] log4j-1.2.8-7jpp_4fc -> [112933]
+      log4j-1.2.8-7jpp_5fc </para>
+    <para
+>[96312] oro-2.0.8-1jpp_2fc -> [113162] oro-2.0.8-1jpp_3fc
+    </para>
+    <para
+>[109898] regexp-1.3-1jpp_5fc -> [114182] regexp-1.3-2jpp_3fc
+    </para>
+    <para
+>[100606] xalan-j2-2.6.0-2jpp_1fc -> [114410]
+      xalan-j2-2.6.0-3jpp_3fc </para>
+    <para
+>[109899] xerces-j2-2.6.2-4jpp_5fc -> [114312]
+      xerces-j2-2.6.2-5jpp_2fc </para>
+    <para
+>[109900] xml-commons-1.0-0.b2.6jpp_12fc -> [114196]
+      xml-commons-1.0-0.b2.7jpp_3fc </para>
+    <para
+>[96303] xml-commons-resolver-1.1-1jpp_4fc -> [113163]
+      xml-commons-resolver-1.1-1jpp_5fc </para>
+    <para
+>[101437] jakarta-commons-lang-2.0-2jpp_1fc -> [112883]
+      jakarta-commons-lang-2.0-2jpp_2fc </para>
+    <para
+>[96300] java_cup-0.10-0.k.1jpp_2fc -> [114395]
+      java_cup-0.10-0.k.1jpp_5fc </para>
+    <para
+>[100540] avalon-logkit-1.2-2jpp_4fc -> [113428]
+      avalon-logkit-1.2-3jpp_1fc </para>
+    <para
+>[101462] cryptix-3.2.0-4jpp_1fc -> [112869]
+      cryptix-3.2.0-4jpp_2fc </para>
+    <para
+>[101463] cryptix-asn1-20011119-4jpp_1fc -> [112873]
+      cryptix-asn1-20011119-4jpp_2fc </para>
+    <para
+>[101464] gnu.getopt-1.0.9-4jpp_1fc -> [112875]
+      gnu.getopt-1.0.9-4jpp_2fc </para>
+    <para
+>[110589] xorg-x11-6.8.2-31 -> [115364] xorg-x11-6.8.2-45
+    </para>
+    <para
+>[108218] aspell-is-0.51.1-1 -> [114361] aspell-is-0.51.1-2
+    </para>
+    <para
+>[106231] pyparted-1.6.9-3 -> [117327] pyparted-1.6.9-4
+    </para>
+    <para
+>[110354] mod_auth_kerb-5.0-6 -> [118413] mod_auth_kerb-5.0-7
+    </para>
+    <para
+>[106186] iprutils-2.0.13.7-2 -> [115548] iprutils-2.0.15.3-1
+    </para>
+    <para
+>[110365] tomcat5-5.0.30-5jpp_6fc -> [118323]
+      tomcat5-5.0.30-8jpp_3fc </para>
+    <para
+>[110776] xchat-2.4.3-3 -> [118268] xchat-2.4.5-1 </para>
+    <para
+>[111287] jakarta-commons-el-1.0-2jpp_3fc -> [114396]
+      jakarta-commons-el-1.0-4jpp_2fc </para>
+    <para
+>- GFS-6.1-0.pre22.6 </para>
+    <para
+>[107882] k3b-0.11.23-3 -> [114095] k3b-0.12.2-1 </para>
+    <para
+>[111251] hal-0.5.2-2 -> [117285] hal-0.5.4-3 </para>
+    <para
+>[107343] gnome-volume-manager-1.3.1-1 -> [117761]
+      gnome-volume-manager-1.5.1-1 </para>
+    <para
+>[106242] pam_passwdqc-0.7.6-1 -> [118214]
+      pam_passwdqc-1.0.2-1 </para>
+    <para
+>[106603] libidn-0.5.15-1 -> [118283] libidn-0.5.19-1 </para>
+    <para
+>[110913] evolution-connector-2.2.2-5 -> [118165]
+      evolution-connector-2.4.0-2 </para>
+    <para
+>[111158] selinux-policy-targeted-1.23.16-6 -> [118397]
+      selinux-policy-targeted-1.27.1-4 </para>
+    <para
+>[111157] selinux-policy-strict-1.23.16-6 -> [118396]
+      selinux-policy-strict-1.27.1-4 </para>
+    <para
+>- ecj-3.1-0.M4.9 </para>
+    <para
+>[104920] diskdumputils-1.0.1-6 -> [116910]
+      diskdumputils-1.1.9-2 </para>
+    <para
+>[108918] module-init-tools-3.1-3 -> [117811]
+      module-init-tools-3.2-0.pre7.3 </para>
+    <para
+>[104418] numactl-0.6.4-1.18 -> [113672] numactl-0.6.4-1.23
+    </para>
+    <para
+>[104522] libwmf-0.2.8.3-8 -> [115159] libwmf-0.2.8.4-1
+    </para>
+    <para
+>[107934] authd-1.4.3-4.devel -> [113028] authd-1.4.3-5.devel
+    </para>
+    <para
+>[112018] gamin-0.1.0-1.1 -> [118342] gamin-0.1.6-2 </para>
+    <para
+>[111127] vino-2.10.0-4 -> [117670] vino-2.12.0-1 </para>
+    <para
+>[109620] HelixPlayer-1.0.4-4 -> [116508]
+      HelixPlayer-1.0.5-2 </para>
+    <para
+>[110936] totem-1.0.2-1 -> [116504] totem-1.1.4-1 </para>
+    <para
+>- gnbd-kernel-2.6.11.2-20050420.133124.FC4.35 </para>
+    <para
+>[108039] aspell-de-0.50-10 -> [114277] aspell-de-0.50-11
+    </para>
+    <para
+>[109112] eclipse-changelog-2.0.1_fc-21 -> [114192]
+      eclipse-changelog-2.0.1_fc-22 </para>
+    <para
+>[111405] eclipse-cdt-3.0.0_fc-0.M6.7 -> [116981]
+      eclipse-cdt-3.0.0_fc-1 </para>
+    <para
+>- iiimf-le-chinput-0.3-19 </para>
+    <para
+>[106138] synaptics-0.14.0-2 -> [115769] synaptics-0.14.3-3
+    </para>
+    <para
+>[110766] libsepol-1.5.9-2 -> [118331] libsepol-1.9.4-1
+    </para>
+    <para
+>[108031] aspell-af-0.50-2 -> [114179] aspell-af-0.50-4
+    </para>
+    <para
+>[103800] aspell-bg-0.50-9 -> [114176] aspell-bg-0.50-11
+    </para>
+    <para
+>[108032] aspell-br-0.50-2 -> [114181] aspell-br-0.50-4
+    </para>
+    <para
+>[108037] aspell-cy-0.50-2 -> [114274] aspell-cy-0.50-4
+    </para>
+    <para
+>[108040] aspell-el-0.50-2 -> [114278] aspell-el-0.50-4
+    </para>
+    <para
+>[108043] aspell-fo-0.51-2 -> [114281] aspell-fo-0.51-4
+    </para>
+    <para
+>[108045] aspell-ga-0.50-2 -> [114288] aspell-ga-0.50-4
+    </para>
+    <para
+>[108047] aspell-gd-0.50-2 -> [114357] aspell-gd-0.50-4
+    </para>
+    <para
+>[108048] aspell-gl-0.50-2 -> [114358] aspell-gl-0.50-4
+    </para>
+    <para
+>[108049] aspell-hr-0.51-2 -> [114359] aspell-hr-0.51-4
+    </para>
+    <para
+>[108050] aspell-id-0.50.1-2 -> [114360] aspell-id-0.50.1-4
+    </para>
+    <para
+>[105301] busybox-1.00-4 -> [111857] busybox-1.00-5 </para>
+    <para
+>[104570] sysfsutils-1.2.0-4 -> [113812] sysfsutils-1.3.0-1
+    </para>
+    <para
+>- rgmanager-1.9.31-3 </para>
+    <para
+>[109173] openswan-2.3.1-2 -> [118022] openswan-2.4.0-1
+    </para>
+    <para
+>[110687] NetworkManager-0.4-15.cvs20050404
+      -> [118005] NetworkManager-0.4.1-2.cvs20050912
+    </para>
+    <para
+>[112106] java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh ->
+      [118416] java-1.4.2-gcj-compat-1.4.2.0-40jpp_51rh </para>
+    <para
+>[106674] gnome-keyring-manager-0.0.4-3 -> [117662]
+      gnome-keyring-manager-2.12.0-1 </para>
+    <para
+>[105646] evolution-webcal-2.2.0-1 -> [118166]
+      evolution-webcal-2.4.0.1-2 </para>
+    <para
+>[106722] krb5-auth-dialog-0.2-5 -> [116572]
+      krb5-auth-dialog-0.2-6 </para>
+    <para
+>[107396] dhcpv6-0.10-13 -> [116466] dhcpv6-0.10-14 </para>
+    <para
+>[106006] dasher-3.2.15-1 -> [117634] dasher-3.2.18-1 </para>
+    <para
+>[111497] firefox-1.0.4-4 -> [118182] firefox-1.5-0.5.0.beta1
+    </para>
+    <para
+>[110588] thunderbird-1.0.2-6 -> [116773] thunderbird-1.0.6-5
+    </para>
+    <para
+>- valgrind-callgrind-0.9.11-1 </para>
+    <para
+>[106256] pam_ccreds-1-6 -> [112255] pam_ccreds-1-7 </para>
+    <para
+>[100966] createrepo-0.4.2-2 -> [114098] createrepo-0.4.3-1
+    </para>
+    <para
+>[111205] audit-0.8.2-1 -> [116925] audit-1.0.3-1 </para>
+    <para
+>[109751] kdewebdev-3.4.0-3 -> [116306] kdewebdev-3.4.2-1
+    </para>
+    <para
+>[98989] slib-3a1-2 -> [117769] slib-3a1-5 </para>
+    <para
+>[105026] webalizer-2.01_10-28 -> [118412]
+      webalizer-2.01_10-29 </para>
+    <para
+>[108536] ipv6calc-0.48-5 -> [118194] ipv6calc-0.50-1 </para>
+    <para
+>[100524] classpathx-mail-1.0-3jpp_1fc -> [111780]
+      classpathx-mail-1.0-4jpp_2fc </para>
+    <para
+>[111648] gnu-crypto-2.0.1-1jpp_5fc -> [114171]
+      gnu-crypto-2.0.1-1jpp_7fc </para>
+    <para
+>[107249] OpenIPMI-1.4.11-5 -> [117704] OpenIPMI-1.4.14-9
+    </para>
+    <para
+>[100864] zsh-4.2.1-2 -> [113141] zsh-4.2.5-1 </para>
+    <para
+>[104688] sane-backends-1.0.15-9 -> [116782]
+      sane-backends-1.0.16-1 </para>
+    <para
+>- lvm2-cluster-2.01.09-3.0 </para>
+    <para
+>- struts11-1.1-1jpp_7fc </para>
+    <para
+>[107376] gkrellm-2.2.4-4 -> [117540] gkrellm-2.2.7-3 </para>
+    <para
+>[108839] cpufreq-utils-0.2-1.1.14 -> [115418]
+      cpufreq-utils-0.3-1.1.16 </para>
+    <para
+>[108362] dmidecode-2.6-1.14 -> [117909] dmidecode-2.7-1.15
+    </para>
+    <para
+>[109300] hardlink-1.0-1.13 -> [117099] hardlink-1.0-1.14
+    </para>
+    <para
+>[111037] readahead-1.1-1.14 -> [115793] readahead-1.1-1.17
+    </para>
+    <para
+>[104427] smartmontools-5.33-1.5 -> [115762]
+      smartmontools-5.33-1.7 </para>
+    <para
+>[108364] x86info-1.13-1.10 -> [117440] x86info-1.15-1.13
+    </para>
+    <para
+>- python-twisted-1.3.0-4 </para>
+    <para
+>[111505] evince-0.3.1-1 -> [118030] evince-0.4.0-2 </para>
+    <para
+>[109178] gnome-doc-utils-0.2.0-2 -> [117722]
+      gnome-doc-utils-0.4.0-1 </para>
+    <para
+>[108845] gnome-menus-2.10.1-3 -> [117531]
+      gnome-menus-2.12.0-1 </para>
+    <para
+>[107103] gnome-python2-extras-2.10.0-2.1 -> [116816]
+      gnome-python2-extras-2.11.4-9 </para>
+    <para
+>[109933] gjdoc-0.7.4-5 -> [114163] gjdoc-0.7.5-4 </para>
+    <para
+>[109753] kdelibs-3.4.0-6 -> [115465] kdelibs-3.4.2-1 </para>
+    <para
+>[106258] kdeaccessibility-3.4.0-1 -> [116016]
+      kdeaccessibility-3.4.2-1 </para>
+    <para
+>[108603] fonts-korean-1.0.11-4 -> [116512]
+      fonts-korean-1.0.11-6 </para>
+    <para
+>[108601] fonts-japanese-0.20050222-3 -> [116488]
+      fonts-japanese-0.20050222-7 </para>
+    <para
+>[108604] fonts-chinese-2.15-2 -> [117399]
+      fonts-chinese-3.00.pre2-1 </para>
+    <para
+>[111507] poppler-0.3.2-1 -> [117476] poppler-0.4.2-1 </para>
+    <para
+>[111030] eclipse-bugzilla-0.1.0_fc-16 -> [114650]
+      eclipse-bugzilla-0.1.1_fc-5 </para>
+    <para
+>[109095] eclipse-pydev-0.9.3_fc-7 -> [115587]
+      eclipse-pydev-0.9.3_fc-11 </para>
+    <para
+>[108005] sqlite-3.1.2-3 -> [117898] sqlite-3.2.5-1 </para>
+    <para
+>[105636] python-urlgrabber-2.9.6-1 -> [118139]
+      python-urlgrabber-2.9.6-3 </para>
+    <para
+>[107161] cryptsetup-luks-1.0-1 -> [116857]
+      cryptsetup-luks-1.0.1-2 </para>
+    <para
+>[108817] jsch-0.1.18-1jpp_1fc -> [114185]
+      jsch-0.1.18-1jpp_2fc </para>
+    <para
+>[109747] latex2html-2002.2.1-3 -> [112874]
+      latex2html-2002.2.1-4 </para>
+    <para
+>[110960] openssl-0.9.7f-7 -> [116949] openssl-0.9.7f-9
+    </para>
+    <para
+>- iiimf-12.2-4 </para>
+    <para
+>[108246] kdevelop-3.2.0-2 -> [116301] kdevelop-3.2.2-1
+    </para>
+    <para
+>- Canna-3.7p3-13 </para>
+    <para
+>- VFlib2-2.25.6-28 </para>
+    <para
+>[108287] perl-Archive-Zip-1.14-1 -> [117218]
+      perl-Archive-Zip-1.16-1 </para>
+    <para
+>[108275] pm-utils-0.01-1 -> [116385] pm-utils-0.04-1 </para>
+    <para
+>[109632] foomatic-3.0.2-19 -> [118014] foomatic-3.0.2-28
+    </para>
+    <para
+>[108982] perl-DateManip-5.42a-4 -> [117863]
+      perl-DateManip-5.44-1 </para>
+    <para
+>- perl-libxml-enno-1.02-31 </para>
+    <para
+>[104653] s390utils-1.3.2-4 -> [112864] s390utils-1.3.2-5
+    </para>
+    <para
+>[107373] m4-1.4.3-1 -> [118239] m4-1.4.3-2 </para>
+    <para
+>[110355] ORBit2-2.12.1-3 -> [117666] ORBit2-2.12.4-1 </para>
+    <para
+>[110242] GConf2-2.10.0-4 -> [117717] GConf2-2.12.0-1 </para>
+    <para
+>[106017] libgnomecanvas-2.10.0-1 -> [117642]
+      libgnomecanvas-2.12.0-1 </para>
+    <para
+>[102603] libbonobo-2.8.1-1 -> [117820] libbonobo-2.10.1-2
+    </para>
+    <para
+>[109591] gnome-vfs2-2.10.0-5 -> [117664] gnome-vfs2-2.12.0-1
+    </para>
+    <para
+>[109285] libgnome-2.10.0-3 -> [117751] libgnome-2.12.0-1
+    </para>
+    <para
+>[109171] libbonoboui-2.8.1-4 -> [117749]
+      libbonoboui-2.10.1-1 </para>
+    <para
+>[104650] librsvg2-2.9.5-2 -> [117304] librsvg2-2.11.1-1
+    </para>
+    <para
+>[107485] eel2-2.10.0-2 -> [117651] eel2-2.12.0-1 </para>
+    <para
+>[106316] tn5250-0.16.5-5 -> [113112] tn5250-0.16.5-6 </para>
+    <para
+>[106143] yaboot-1.3.12-9 -> [118141] yaboot-1.3.13-0.16
+    </para>
+    <para
+>[107969] libgnomeui-2.10.0-1 -> [117980] libgnomeui-2.12.0-2
+    </para>
+    <para
+>[104629] libglade2-2.5.1-2 -> [116545] libglade2-2.5.1-3
+    </para>
+    <para
+>[105166] libIDL-0.8.5-2 -> [117667] libIDL-0.8.6-1 </para>
+    <para
+>[110521] usermode-1.80-1 -> [116503] usermode-1.81-1 </para>
+    <para
+>[102961] docbook-style-xsl-1.68.1-1 -> [116354]
+      docbook-style-xsl-1.69.1-1 </para>
+    <para
+>[104584] intltool-0.33-2 -> [115810] intltool-0.34.1-1
+    </para>
+    <para
+>[110237] evolution-2.2.2-5 -> [118148] evolution-2.4.0-2
+    </para>
+    <para
+>[104652] xmltex-20020625-5 -> [118338] xmltex-20020625-6
+    </para>
+    <para
+>[105333] pygtk2-2.6.0-2 -> [117772] pygtk2-2.8.0-1 </para>
+    <para
+>[105908] gnome-python2-2.10.0-1 -> [116511]
+      gnome-python2-2.11.3-2 </para>
+    <para
+>[104649] libpng10-1.0.18-2 -> [115463] libpng10-1.0.18-3
+    </para>
+    <para
+>[96234] aspell-pt-0.50-9 -> [114369] aspell-pt-0.50-10
+    </para>
+    <para
+>[106303] stardict-2.4.4-3 -> [118242] stardict-2.4.5-1
+    </para>
+    <para
+>[108452] glibc-kernheaders-2.4-9.1.94 -> [111898]
+      glibc-kernheaders-2.4-9.1.95 </para>
+    <para
+>[105250] wordtrans-1.1pre13-10 -> [115775]
+      wordtrans-1.1pre13-11 </para>
+    <para
+>[104417] microcode_ctl-1.11-1.21 -> [118068]
+      microcode_ctl-1.12-1.23 </para>
+    <para
+>[109638] gnome-pilot-2.0.13-2 -> [116547]
+      gnome-pilot-2.0.13-7.fc5 </para>
+    <para
+>[106005] at-spi-1.6.3-1 -> [117632] at-spi-1.6.6-1 </para>
+    <para
+>[110915] gail-1.8.3-2 -> [117635] gail-1.8.5-1 </para>
+    <para
+>[106768] vsftpd-2.0.3-1 -> [117823] vsftpd-2.0.3-10 </para>
+    <para
+>[108150] authconfig-4.6.12-1 -> [117485] authconfig-5.0.1-1
+    </para>
+    <para
+>[104665] linuxdoc-tools-0.9.21-5 -> [113333]
+      linuxdoc-tools-0.9.21-6 </para>
+    <para
+>[111809] gphoto2-2.1.5-10 -> [115052] gphoto2-2.1.6-2
+    </para>
+    <para
+>[104555] xmlto-0.0.18-6 -> [116003] xmlto-0.0.18-9 </para>
+    <para
+>- perl-Time-HiRes-1.65-1 </para>
+    <para
+>[108948] db4-4.3.27-3 -> [118387] db4-4.3.28-2 </para>
+    <para
+>[107533] openmotif-2.2.3-10 -> [117413] openmotif-2.2.3-11
+    </para>
+    <para
+>[101890] docbook-dtds-1.0-26 -> [111825] docbook-dtds-1.0-27
+    </para>
+    <para
+>[111495] firstboot-1.3.42-1 -> [118187] firstboot-1.3.47-2
+    </para>
+    <para
+>[107310] cups-1.1.23-15 -> [117439] cups-1.1.23-17 </para>
+    <para
+>[108639] postfix-2.2.2-2 -> [117702] postfix-2.2.5-1 </para>
+    <para
+>[110444] booty-0.53-1 -> [118032] booty-0.57-1 </para>
+    <para
+>[106326] cdicconf-0.2-11 -> [113538] cdicconf-0.2-12 </para>
+    <para
+>[110352] libwnck-2.10.0-3 -> [117752] libwnck-2.12.0-1
+    </para>
+    <para
+>[110575] crypto-utils-2.2-5 -> [111863] crypto-utils-2.2-6
+    </para>
+    <para
+>[107303] perl-Compress-Zlib-1.34-2 -> [117468]
+      perl-Compress-Zlib-1.37-1.fc5 </para>
+    <para
+>[109590] libgtop2-2.10.1-1 -> [117665] libgtop2-2.12.0-1
+    </para>
+    <para
+>[110990] yelp-2.10.0-1 -> [117757] yelp-2.12.0-1 </para>
+    <para
+>[110693] hwdata-0.158-1 -> [117804] hwdata-0.169-1 </para>
+    <para
+>[106407] rhnlib-1.8-6.p24.1 -> [116200] rhnlib-1.8-6.p24.11
+    </para>
+    <para
+>[106361] arts-1.4.0-1 -> [115461] arts-1.4.2-1 </para>
+    <para
+>[107873] dia-0.94-11 -> [116485] dia-0.94-13 </para>
+    <para
+>[106665] gnome-system-monitor-2.10.0-2 -> [117663]
+      gnome-system-monitor-2.12.0-1 </para>
+    <para
+>[106473] pwlib-1.8.4-1 -> [117530] pwlib-1.8.7-1 </para>
+    <para
+>[106475] openh323-1.15.3-1 -> [117538] openh323-1.15.6-1
+    </para>
+    <para
+>[106477] gnomemeeting-1.2.1-1 -> [118169]
+      gnomemeeting-1.2.2-2 </para>
+    <para
+>[93048] fonts-KOI8-R-1.0-7 -> [113604] fonts-KOI8-R-1.0-8
+    </para>
+    <para
+>[104596] patchutils-0.2.30-4 -> [114399] patchutils-0.2.31-2
+    </para>
+    <para
+>[107936] man-1.5p-4 -> [111925] man-1.5p-6 </para>
+    <para
+>[110750] elinks-0.10.3-3 -> [112404] elinks-0.10.3-3.1
+    </para>
+    <para
+>[107263] netatalk-2.0.2-3 -> [114554] netatalk-2.0.3-2
+    </para>
+    <para
+>[107736] netdump-0.7.7-6 -> [115481] netdump-0.7.10-4
+    </para>
+    <para
+>[111279] ant-1.6.2-3jpp_8fc -> [115662] ant-1.6.2-3jpp_14fc
+    </para>
+    <para
+>[109158] openmotif21-2.1.30-14 -> [116779]
+      openmotif21-2.1.30-17.1 </para>
+    <para
+>[109640] gnutls-1.0.25-1 -> [115978] gnutls-1.2.6-1 </para>
+    <para
+>[104487] privoxy-3.0.3-7 -> [117709] privoxy-3.0.3-9 </para>
+    <para
+>[107117] eog-2.10.0-1 -> [117654] eog-2.12.0-1 </para>
+    <para
+>[109172] gconf-editor-2.10.0-5 -> [117718]
+      gconf-editor-2.12.0-1 </para>
+    <para
+>[111105] gtk2-engines-2.6.3-2 -> [117640]
+      gtk2-engines-2.6.5-1 </para>
+    <para
+>[111267] gnome-desktop-2.10.0-5 -> [117723]
+      gnome-desktop-2.12.0-1 </para>
+    <para
+>[110510] gnome-panel-2.10.1-10 -> [118149]
+      gnome-panel-2.12.0-2 </para>
+    <para
+>[108570] gnome-session-2.10.0-2 -> [117729]
+      gnome-session-2.12.0-1 </para>
+    <para
+>[109748] gnome-terminal-2.10.0-2 -> [117730]
+      gnome-terminal-2.12.0-1 </para>
+    <para
+>[107500] metacity-2.10.0-1 -> [117759] metacity-2.12.0-1
+    </para>
+    <para
+>[107193] valgrind-2.4.0-2 -> [117903] valgrind-3.0.1-1
+    </para>
+    <para
+>[111389] vte-0.11.13-2.fc4 -> [117756] vte-0.11.15-1.fc5
+    </para>
+    <para
+>[105809] ghostscript-7.07-40 -> [116480]
+      ghostscript-8.15-0.rc4.3 </para>
+    <para
+>[108033] file-4.13-4 -> [118257] file-4.15-3 </para>
+    <para
+>[108940] mgetty-1.1.33-1 -> [115032] mgetty-1.1.33-3_FC5
+    </para>
+    <para
+>[111301] xen-2-20050522 -> [118168] xen-3.0-0.20050912.fc5.1
+    </para>
+    <para
+>[106289] libraw1394-1.1.0-3 -> [114765]
+      libraw1394-1.2.0-1.fc5 </para>
+    <para
+>[108526] mod_perl-2.0.0-0.rc5.3 -> [112776]
+      mod_perl-2.0.1-1.fc5 </para>
+    <para
+>[103976] radvd-0.7.3-1_FC4 -> [114404] radvd-0.8-2.FC5
+    </para>
+    <para
+>[111033] ncpfs-2.2.4-8 -> [115462] ncpfs-2.2.4-9 </para>
+    <para
+>[106079] prelink-0.3.4-3 -> [117615] prelink-0.3.6-1 </para>
+    <para
+>[110767] netpbm-10.27-3 -> [116518] netpbm-10.29-1 </para>
+-->
+    <section id="sn-packages-added">
+      <title
+>?????????????????????? ????????????</title>
+      <para
+>?????????????????? ???????????? ???????? ?????????????????? ?? &FC; ?? ???????? ???????????????????? ?? ??????????????. </para>
+      <para
+>scim-anthy-0.6.1-1.fc5 </para>
+      <para
+>struts-1.2.4-2jpp_3fc </para>
+      <para
+>jonas-4.3.3-1jpp_10fc </para>
+      <para
+>nspr-4.6-4 </para>
+      <para
+>scim-1.4.2-3 </para>
+      <para
+>anthy-6829-3 </para>
+      <para
+>system-config-cluster-0.9.69-1.0 </para>
+      <para
+>axis-1.2.1-1jpp_1fc </para>
+      <para
+>bsf-2.3.0-6jpp_2fc </para>
+      <para
+>bsh-1.3.0-5jpp_1fc </para>
+      <para
+>concurrent-1.3.2-2jpp_1fc </para>
+      <para
+>dtdparser-1.21-2jpp_1fc </para>
+      <para
+>jakarta-commons-discovery-0.3-1jpp_1fc </para>
+      <para
+>jdom-1.0-1jpp_2fc </para>
+      <para
+>wsdl4j-1.5.1-1jpp_1fc </para>
+      <para
+>javacc-3.2-1jpp_3fc </para>
+      <para
+>jakarta-commons-httpclient-3.0-0.rc2.0jpp_1fc </para>
+      <para
+>castor-0.9.5-1jpp_1fc </para>
+      <para
+>adaptx-0.9.6-1jpp_1fc </para>
+      <para
+>amtu-1.0.2-1 </para>
+      <para
+>xdoclet-1.2.2-2jpp_1fc </para>
+      <para
+>xjavadoc-1.1-1jpp_1fc </para>
+      <para
+>jgroups-2.2.6-1jpp_1fc </para>
+      <para
+>hsqldb-1.80.1-1jpp_1fc </para>
+      <para
+>jonathan-core-4.1-1jpp_4fc </para>
+      <para
+>jonathan-jeremie-4.2-1jpp_4fc </para>
+      <para
+>jrefactory-2.8.9-3jpp_1fc </para>
+      <para
+>mockobjects-0.09-12jpp_2fc </para>
+      <para
+>monolog-1.8.6-1jpp_5fc </para>
+      <para
+>oldkilim-1.1.3-2jpp_3fc </para>
+      <para
+>p6spy-1.3-2jpp_3fc </para>
+      <para
+>fractal-2.2-2jpp_1fc </para>
+      <para
+>velocity-1.4-3jpp_1fc </para>
+      <para
+>werken.xpath-0.9.4-0.beta.9jpp_1fc </para>
+      <para
+>gnu.regexp-1.1.4-7jpp_1fc </para>
+      <para
+>nanoxml-2.2.3-3jpp_3fc </para>
+      <para
+>asm-1.5.3-1jpp_1fc </para>
+      <para
+>cairo-1.0.0-1 </para>
+      <para
+>objectweb-anttask-1.2-1jpp_1fc </para>
+      <para
+>objectweb-deploysched-0.2-1jpp_1fc </para>
+      <para
+>carol-1.8.9.3-1jpp_5fc </para>
+      <para
+>jacorb-2.2-3jpp_3fc </para>
+      <para
+>jakarta-commons-cli-1.0-6jpp_1fc </para>
+      <para
+>tanukiwrapper-3.1.1-4jpp_3fc </para>
+      <para
+>tog-pegasus-2.4.1-4.FC5 </para>
+      <para
+>joram-4.1.5-1jpp_5fc </para>
+      <para
+>jotm-2.0.5-1jpp_3fc </para>
+      <para
+>lucene-1.4.3-1jpp_1fc </para>
+      <para
+>geronimo-specs-1.0-0.M2.2jpp_4fc </para>
+      <para
+>jakarta-commons-codec-1.3-2jpp_1fc </para>
+      <para
+>howl-logger-0.1.8-1jpp_3fc </para>
+      <para
+>dhcdbd-1.8-1 </para>
+      <para
+>aspell-ru-0.99f7-2 </para>
+      <para
+>hplip-0.9.5-3 </para>
+      <para
+>gpart-0.1h-1 </para>
+      <para
+>iso-codes-0.47-1 </para>
+      <para
+>gif89encoder-0.90-0.b.1jpp_1fc </para>
+      <para
+>jonathan-rmi-3.1-5 </para>
+      <para
+>pup-0.0.2-1 </para>
+      <para
+>jorm-2.4.3-1jpp_2fc </para>
+      <para
+>jorm-rdb-adapter-2.6-1jpp_1fc </para>
+      <para
+>medor-1.4.4-1jpp_1fc </para>
+      <para
+>medor-expression-1.4.2-1jpp_1fc </para>
+      <para
+>perseus-cache-1.3.4-1jpp_1fc </para>
+      <para
+>perseus-concurrency-1.4-1jpp_1fc </para>
+      <para
+>perseus-dependency-1.4-1jpp_1fc </para>
+      <para
+>perseus-distribution-1.3.2-1jpp_1fc </para>
+      <para
+>perseus-fos-1.3.1-1jpp_1fc </para>
+      <para
+>perseus-persistence-1.3.4-1jpp_1fc </para>
+      <para
+>perseus-pool-1.3.3-1jpp_1fc </para>
+      <para
+>systemtap-0.4.1-2 </para>
+      <para
+>pcmciautils-007-1 </para>
+      <para
+>scim-tables-0.5.3-4 </para>
+      <para
+>libsemanage-1.3.2-1 </para>
+      <para
+>scim-hangul-0.2.0-5.fc5 </para>
+      <para
+>scim-pinyin-0.5.91-1 </para>
+      <para
+>scim-chewing-0.2.1-1 </para>
+      <para
+>scim-qtimm-0.9.4-1 </para>
+      <para
+>libchewing-0.2.7-1 </para>
+      <para
+>kasumi-0.9-3.fc5 </para>
+      <para
+>kexec-tools-1.101-2 </para>
+      <para
+>libsetrans-0.1.7-1 </para>
+      <para
+>icu-3.4-4 </para>
+      <para
+>libiec61883-1.0.0-8.fc5 </para>
+    </section>
+    <section>
+      <title
+>?????????????????? ????????????</title>
+      <para
+>?????????????????? ???????????? ???????? ??????????????: </para>
+      <para
+>ccs-0.25-0.17 </para>
+      <para
+>cman-1.0-0.pre33.15 </para>
+      <para
+>cman-kernel-2.6.11.5-20050601.152643.FC4.2 </para>
+      <para
+>dlm-1.0-0.pre21.10 </para>
+      <para
+>dlm-kernel-2.6.11.5-20050601.152643.FC4.2 </para>
+      <para
+>fence-1.27-16 </para>
+      <para
+>GFS-kernel-2.6.11.8-20050601.152643.FC4.2 </para>
+      <para
+>gnbd-1.0-0.pre14.6 </para>
+      <para
+>gulm-1.0-0.pre30.1 </para>
+      <para
+>iddev-1.9-21 </para>
+      <para
+>magma-1.0-0.pre21.7 </para>
+      <para
+>magma-plugins-1.0-0.pre18.3 </para>
+    </section>
+  </section>
+  <section>
+    <title
+>Notes</title>
+    <para>
+      <application
+>system-config-mouse</application
+> configuration
+      utility has been dropped in this release because synaptic and 3
+      button mouse configuration is being done automatically and serial
+      mice are not supported.
+    </para>
+    <para>
+      Screensavers not installed by default anymore?  Explain
+      why and provide commands to install them.
+    </para>
+<!-- FIXME
+    <para>
+      Gbenson agreed to justify any inclusion of Java packages in
+      FC5. Send a mail. Should include this info before test1 release 
+    </para>
+-->
+  </section>
+<!--
+Local variables:
+mode: xml
+sgml-parent-document:("RELEASE-NOTES-en.xml" "article" "section")
+fill-column: 72
+End:
+-->


Index: splash-ru.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-ru.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- splash-ru.xml	10 Nov 2005 21:21:08 -0000	1.1
+++ splash-ru.xml	27 Nov 2005 13:19:24 -0000	1.2
@@ -1,14 +1,24 @@
 <section id="sn-splash">
   <title
 >?????????? ???????????????????? ?? &FC; &LOCALVER;</title>
+  <para
+>&FC; &mdash; ?????????????????? ????????????????????, ?????????????????????????? ???????????????????????? ?? ???????????????????? ?????????????????????????? ??????????????????, ???????????????????? ???? Linux, ?????????????????? ?????? ???????? ?????? ??????????????????????????, ?????? ?????????????????? ?? ??????????????????????????????, ???????????? ?? ????????????????. ???????????? &FP; &mdash; ???????????? ?? ???????????????? ??????????, ???????????????????????? &RH; ?? ???????????????????????????? ?????????????????????? &FED;, ?? ???????????? ???????????????? ???????????????????? ?????????? ?????????????????? ???????????????????? ?? ??????????????????. </para>
   <caution>
     <title
->???????????????????? ????????????????</title>
+>?????? ???????????????? ????????????. ???? ???? ???????????????????????? ?????? ?????????????????????????? ?????????????????? ????????????????????????????</title>
+    <para
+>???????? ???????????????? ???????????? ???????????????????????? ?????? ?????????????????????????? ?? ?????????????????????????? ?????? ???????????????? ?? ???????????????? ?????????????? ?? ??????????????????????????????????. ???? ???? ???????????????????????? ?????? ?????????????? ??????????????????????????. </para>
+    <para
+>?????????????????????? ???? ???????????? ???????????????? <ulink url="https://www.redhat.com/mailman/listinfo/fedora-test-list/"
+>fedora-test</ulink
+> ?? <ulink url="https://www.redhat.com/mailman/listinfo/fedora-devel-list"
+>fedora-devel</ulink
+> ?????? ???????????????????????? ???????????????? ???????????? ?????????????????? ?? ?????????????? ?????????????????????????????? ???????????? ?? ?????????????? ?????????? ??????????????????????????. ?????????????? &FP; ?????????????????? ???????? ???????????? ???? ?????????????? ?? ???????????????????? ?????? ???????????????????? ?????????????????? ?????????????? ?????? ?????????????? ??????????????????????????. ???????????????????????????? ???????????????????? ???? ???????????? ?????????? ?? ?????????????????? ??????????????????: </para>
     <para
->???????????????????? ?????????????? ?????????????? ?????????????? ?????????????????????????? ?? &DISTRO; &DISTROVER; </para>
+><ulink url="http://fedoraproject.org/wiki/BugsAndFeatureRequests"
+>http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink
+>. </para>
   </caution>
-  <para
->&FC; &mdash; ?????????????????? ????????????????????, ?????????????????????????? ???????????????????????? ?? ???????????????????? ?????????????????????????? ??????????????????, ???????????????????? ???? Linux. ???????????? &FP; &mdash; ???????????? ?? ???????????????? ??????????, ???????????????????????? &RH; ?? ???????????????????????????? ?????????????????????? &FED;, ?? ???????????? ???????????????? ???????????????????? ?????????? ?????????????????? ???????????????????? ?? ??????????????????. </para>
   <tip>
     <title
 >?????????? ?????????? ?????????????????? ?? ?????????????? ?????????????????? ?? ????????</title>
@@ -39,18 +49,22 @@
   <para
 >?????????? ???????????????? ???????????????????????????? ???????????????????? ?? &FED;, ???????????????????? ?? ?????????????????? Web-??????????????????: </para>
   <itemizedlist>
-<!-- FIXME Return when the section is updated
     <listitem>
       <para>
 	<xref linkend="sn-new-in-fc"/>
       </para>
     </listitem>
--->
     <listitem>
       <para
 ><xref linkend="sn-intro"/> &mdash; ?????????????????????? ?????????????????? ?? ???????????? </para>
     </listitem>
     <listitem>
+      <para>
+	<ulink url="http://fedoraproject.org/wiki/FAQ/"
+>?????????? ???????????????????? ?????????????? Fedora FAQ</ulink>
+      </para>
+    </listitem>
+    <listitem>
       <para
 >?????????????? ?? ?????????????????? (<ulink url="http://fedora.redhat.com/participate/communicate/"
 >http://fedora.redhat.com/participate/communicate/</ulink
@@ -69,6 +83,60 @@
 >) </para>
     </listitem>
   </itemizedlist>
+  <section id="sn-new-in-fc">
+    <title
+>?????? ???????????? ?? &FC; &LOCALVER;</title>
+    <itemizedlist>
+      <listitem>
+        <para
+>???? ?????????????????????????? Xen ?? ???????????????? ?????????????? yum ?????????????????????????? ?? ?????????????????? ?????????????????? &FED;. ?????????????????? ?????????????????????? ???????? ?????????? ??????????. ?????? ???? ???????????????? ?????????????????? ?????? ???????????????? ???????????????????????????? ?? ?????????????? ???????????????? ?????????? ?????????????????? ???? ??????????????. </para>
+      </listitem>
+      <listitem>
+        <para
+><application
+>Pup</application
+>, ?????????????????????? ?????????????????? ???????????????????? ?????????? yum ???????????????? <application
+>rhn-applet</application
+>. </para>
+      </listitem>
+      <listitem>
+        <para
+>?????????????????????? ?????????????????? GNOME 2.12 ?? KDE 3.4. </para>
+      </listitem>
+      <listitem>
+        <para
+>GNOME Power Manager ?? GNOME Screensaver ???????????????????????? ?? ???????? ?????????????? ?????? "technology preview". </para>
+      </listitem>
+      <listitem>
+        <para
+>?????????????? ?? ???????????? ?????????????????????????? ???????????? OpenOffice.org 2.0. OpenOffice.org ???????????? ???????????????????? ?????????????????? ???????????? ???????????? ?????????????????? ?????? ???????????????????? ???????????????????????????????????? ?? ??????????????????????????. </para>
+      </listitem>
+      <listitem>
+        <para
+>?????????????? ?? ???????????? Xorg X11R7 release candidate 2. ?????? ???????????? ?????????????????? ????????????, ???????????????????? ?????????????????? ?????????? ?????????????????????? ?? ???????????????????? ???????????? ?? ?????????? ?????????????? ??????????????????. </para>
+      </listitem>
+      <listitem>
+        <para
+>???????????????? ?? ???????????? ???????? Kernel 2.6.14. ?? ???????? ?????????????? ?????????????????????????? ?????????????? ?????????????????????? ???????????????????????? ???????????? (software suspend). </para>
+      </listitem>
+      <listitem>
+        <para
+>?? ???????? ?????????????? SCIM ?????????????? IIMF ?? ?????????????? &FC;. </para>
+      </listitem>
+      <listitem>
+	<para
+>???????????????? ???????? ?????????????????????????? ???????????????? ????????. </para>
+      </listitem>
+      <listitem>
+        <para
+>?????????? ?????????????? &FP;. </para>
+      </listitem>
+    </itemizedlist>
+    <para
+>???????????????????????????? ???????? ?????? Fedora ???????? ???????????? ?????????? ?????????? ???? ???????????????? <ulink url="http://fedoraproject.org/wiki/RoadMap"
+>http://fedoraproject.org/wiki/RoadMap</ulink
+>. </para>
+  </section>
 <!-- commented out until the content can be updated
   <section id="sn-new-in-fc">
     <title



From fedora-docs-commits at redhat.com  Sun Nov 27 13:55:38 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 27 Nov 2005 08:55:38 -0500
Subject: example-tutorial example-tutorial-en.xml,1.16,1.17
Message-ID: <200511271355.jARDtc9h014175@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14158

Modified Files:
	example-tutorial-en.xml 
Log Message:
Added procedure test


Index: example-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/example-tutorial-en.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- example-tutorial-en.xml	26 Nov 2005 21:44:18 -0000	1.16
+++ example-tutorial-en.xml	27 Nov 2005 13:55:30 -0000	1.17
@@ -6,7 +6,11 @@
  <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
 %FEDORA-ENTITIES-EN;
 
-<!ENTITY BOOKID "example-tutorial-0.14 (2005-09-18)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKNAME "example-tutorial">
+<!ENTITY BOOKVERSION "0.14"> <!-- change version here -->
+<!ENTITY BOOKDATE "2005-09-18"> <!-- change revision date here -->
+<!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)">
+<!ENTITY BUG-NUM "000000"> <!-- use this only while in draft stage -->
 
 <!ENTITY  ARTICLE-INFO-EN SYSTEM "article-info-en.xml" >
 
@@ -117,6 +121,23 @@
     </section>
   </section>
 
+  <section id="sn-procedure-test">
+    <title>Procedure Test</title>
+
+    <procedure>
+      <step>
+	<para>First step</para>
+      </step>
+      <step>
+	<para>Second step</para>
+      </step>
+      <step>
+	<para>Third step</para>
+      </step>
+    </procedure>
+
+  </section>
+
   <index id="generated-index"></index>
 </article>
 



From fedora-docs-commits at redhat.com  Sun Nov 27 15:40:46 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 27 Nov 2005 10:40:46 -0500
Subject: mirror-tutorial mirror-tutorial-en.xml,1.19,1.20
Message-ID: <200511271540.jARFek9R018383@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18366

Modified Files:
	mirror-tutorial-en.xml 
Log Message:
Minor command fix


Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- mirror-tutorial-en.xml	17 Nov 2005 12:43:56 -0000	1.19
+++ mirror-tutorial-en.xml	27 Nov 2005 15:40:38 -0000	1.20
@@ -6,8 +6,8 @@
 %FEDORA-ENTITIES-EN;
 
 <!ENTITY BOOKNAME "mirror-tutorial">
-<!ENTITY BOOKVERSION "0.37">
-<!ENTITY BOOKDATE "2005-11-17">
+<!ENTITY BOOKVERSION "0.37.1">
+<!ENTITY BOOKDATE "2005-11-27">
 <!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)"> <!-- change version of manual and date here -->
 
 <!ENTITY BUG-NUM "130125">
@@ -213,6 +213,16 @@
 	  </para>
 	</revdescription>
       </revision>
+      <revision>
+	<revnumber>0.37.1</revnumber>
+	<date>2005-11-25</date>
+	<authorinitials>PaulWFrields</authorinitials>
+	<revdescription>
+	  <para>
+	    Minor revision fixing service reload command.
+	  </para>
+	</revdescription>
+      </revision>
     </revhistory>
   </articleinfo>
 
@@ -1155,7 +1165,7 @@
       </para>
 
 <screen>
-<userinput>/sbin/service httpd reload</userinput>
+<userinput>su -c '/sbin/service httpd reload'</userinput>
 </screen>
 
       <para>



From fedora-docs-commits at redhat.com  Sun Nov 27 15:42:09 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sun, 27 Nov 2005 10:42:09 -0500
Subject: example-tutorial Makefile,1.17,1.18
Message-ID: <200511271542.jARFg9VH018433@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18396

Modified Files:
	Makefile 
Log Message:
Another decruftication of that accidental check-in the other day.  Sorry.



Index: Makefile
===================================================================
RCS file: /cvs/docs/example-tutorial/Makefile,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- Makefile	26 Nov 2005 21:49:12 -0000	1.17
+++ Makefile	27 Nov 2005 15:42:01 -0000	1.18
@@ -18,7 +18,7 @@
 DOCBASE        	= example-tutorial
 #
 DOCTITLE-en	= Example Tutorial
-XMLEXTRAFILES-en=article-info-en.xml
+XMLEXTRAFILES-en=
 #
 DOCTITLE-de	= Beispiel Tutorial
 XMLEXTRAFILES-de=



From fedora-docs-commits at redhat.com  Sun Nov 27 16:53:38 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Sun, 27 Nov 2005 11:53:38 -0500
Subject: release-notes install-notes-en.xml,1.6,1.7
Message-ID: <200511271653.jARGrcOB020422@cvs-int.fedora.redhat.com>

Author: kwade

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20405

Modified Files:
	install-notes-en.xml 
Log Message:
Fixing tag usage and extraneous quotemarks used to denote meaning.


Index: install-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-en.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- install-notes-en.xml	24 Nov 2005 22:31:21 -0000	1.6
+++ install-notes-en.xml	27 Nov 2005 16:53:30 -0000	1.7
@@ -240,7 +240,7 @@
 	  Certain hardware configurations (particularly those with
 	  LCD displays) may experience problems while starting the
 	  &DISTRO; installation program.  In these instances, restart
-	  the installation, and add the "<command>nofb</command>" option
+	  the installation, and add the <option>nofb</option> option
 	  to the boot command line.
 	</para>
 	<note>



From fedora-docs-commits at redhat.com  Sun Nov 27 17:13:33 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 27 Nov 2005 12:13:33 -0500
Subject: mirror-tutorial mirror-tutorial-en.xml,1.20,1.21
Message-ID: <200511271713.jARHDXHw022111@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22094

Modified Files:
	mirror-tutorial-en.xml 
Log Message:
Remove BETA notice


Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- mirror-tutorial-en.xml	27 Nov 2005 15:40:38 -0000	1.20
+++ mirror-tutorial-en.xml	27 Nov 2005 17:13:26 -0000	1.21
@@ -16,7 +16,7 @@
 
 <article id="mirror-tutorial" lang="en">
   <articleinfo>
-    <title>Mirror Tutorial - <emphasis>BETA</emphasis></title>
+    <title>Mirror Tutorial</title>
     <copyright>
       <year>2004</year>
       <year>2005</year>



From fedora-docs-commits at redhat.com  Sun Nov 27 17:57:30 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 27 Nov 2005 12:57:30 -0500
Subject: example-tutorial example-tutorial-de.xml, NONE, 1.1 Makefile, 1.18,
	1.19 rpm-info.xml, 1.2, 1.3 example-tutorial-it.xml, 1.1, NONE
Message-ID: <200511271757.jARHvU7f022601@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22579

Modified Files:
	Makefile rpm-info.xml 
Added Files:
	example-tutorial-de.xml 
Removed Files:
	example-tutorial-it.xml 
Log Message:
Ignore some of the makefile cruft at the bottom... in transition, obviously.
Also, moved "it" i18n stuff to "de" to match what's in Makefile and rpm-info.xml file.



--- NEW FILE example-tutorial-de.xml ---
<!-- $Id: -->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;

<!ENTITY BOOKNAME "example-tutorial">
<!ENTITY BOOKVERSION "0.14"> <!-- change version here -->
<!ENTITY BOOKDATE "2005-09-18"> <!-- change revision date here -->
<!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)">
<!ENTITY BUG-NUM "000000"> <!-- use this only while in draft stage -->

]>

<!-- This file is just a copy of the English version, only here for testing -->
<!-- Makefile locale capabilities.  Nobody really needs to translate this -->
<!-- yet. -->


<article id="example-tutorial" lang="it">
  <articleinfo>
    <title>Example Tutorial</title>
    <copyright>
      <year>2003, 2005</year>
      <holder>&FORMAL-RHI;</holder>
      <holder>Tammy Fox</holder>
    </copyright>
    <authorgroup>
      <author>
  <surname>Fox</surname>
  <firstname>Tammy</firstname>
      </author>
      <editor>
  <surname>Frields</surname>
  <firstname>Paul</firstname>
  <othername role="mi">W.</othername>
      </editor>
    </authorgroup>
    &LEGALNOTICE;
    <revhistory>
      <revision>
	<revnumber>0.13</revnumber>
	<date>2005-09-18</date>
	<authorinitials>PaulWFrields</authorinitials>
	<revdescription>
	  <para>
	    Add revision history.
	  </para>
	</revdescription>
      </revision>
    </revhistory>
  </articleinfo>

  <section id="sn-some-section">
    <title>Some Section</title>

    <indexterm>
      <primary>Index term</primary>
    </indexterm>

    <para>
      This is an example section. You should not use sect1, sect2, etc., since
      those tags will make sections less modular &mdash; that is, harder to
      relocate without changing a lot of other markup.
    </para>
    <para>
      Keep text within the <command>title</command> tags on the same line as the
      tags. Nesting the title on a separate line from the enclosing tags results
      in extra spaces in HTML rendering.
    </para>

    <warning>
      <title>Warning</title>
      <para>
        Example of an admonition.
      </para>
    </warning>

    <para>
      This paragraph illustrates the use of command syntax to accomplish a
      task. Note that specific filenames denoting versions should be
      avoided. To install any RPM package, use the following syntax:
    </para>
<screen>
<userinput><command>rpm -ivh <replaceable>pkgname</replaceable>-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</command></userinput>
</screen>
    <para>
      Notice that the <command>screen</command> section is entirely
      left-justified with no preceding indent. This is necessary to ensure
      proper rendering in PDFs. Also notice that the entire
      <command>command</command> has been surrounded by
      <command>userinput</command> since the user types this
      command. Computer output would be enclosed in
      <command>computeroutput</command> tags, as in the following
      sample.
    </para>
<screen>
<userinput><command>grep snmptrap /etc/services</command></userinput>
<computeroutput>snmptrap        162/udp         snmp-trap       # Traps for SNMP</computeroutput>
</screen>
    <para>
      Lines should be broken <emphasis>exactly</emphasis> as they are
      on-screen. Also, note that spaces inside <command>screen</command> tags
      are automatically treated as non-breaking.
    </para>
    <tip>
      <title>Fill modes and <command>screen</command> tags</title>
      <para>
  Using automatic or manual fill commands in Emacs/PSGML will sometimes
  mangle <command>screen</command> sections. Use care when performing fill
  operations, and check the results.
      </para>
    </tip>
  </section>

  <section>
    <title>Callout Example</title>
      <programlisting id="pl-callout">
Line 1 <co id="pl-callout-L1"/>
Line 2
Line 3
Line 4 <co id="pl-callout-L4"/>
      </programlisting>
      <calloutlist>
        <callout arearefs="pl-callout-L1">
          <para>
            Here is a callout.
          </para>
        </callout>
        <callout arearefs="pl-callout-L4">
          <para>
            The second callout.
          </para>
        </callout>
      </calloutlist>
  </section>

<index id="generated-index"></index>
</article>

<!--
Local variables:
mode: xml
End:
-->


Index: Makefile
===================================================================
RCS file: /cvs/docs/example-tutorial/Makefile,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- Makefile	27 Nov 2005 15:42:01 -0000	1.18
+++ Makefile	27 Nov 2005 17:57:23 -0000	1.19
@@ -9,7 +9,7 @@
 ###############################################################################
 # There is actually no "de" translation.  All the '*-de*" files are just
 # fodder to check the internationalization (i18n) workings for the FTP.
-# No discourtesey to an Germanic speaker is intended.  -- Tommy Reynolds
+# No discourtesy to any German speaker is intended.  -- Tommy Reynolds
 ###############################################################################
 #
 # Document-specific definitions.
@@ -21,7 +21,7 @@
 XMLEXTRAFILES-en=
 #
 DOCTITLE-de	= Beispiel Tutorial
-XMLEXTRAFILES-de=
+XMLEXTRAFILES-de= 
 #
 ######################################################
 include ../docs-common/Makefile.common
@@ -38,8 +38,10 @@
 
 ######################################################
 #
+# Note xmlformat eliminates need to munge pretty XSL
+#
 #article-info-en.xml:: rpm-info.xml
-#	xsltproc -o $@ --stringparam doctype articleinfo ../docs-common/packaging/bookinfo.xsl rpm-info.xml
+#	xsltproc --stringparam doctype articleinfo ../docs-common/packaging/bookinfo.xsl rpm-info.xml | ../docs-common/bin/xmlformat -f ../docs-common/bin/xmlformat-fdp.conf > $@
 #
 #clean::
 #	${RM} bookinfo.xml
@@ -47,42 +49,53 @@
 
 ######################################################
 # Some packaging specific vars
-VERSION=$(shell grep BOOKID $(DOCBASE)-en.xml | sed 's/<!ENTITY BOOKID "[^0-9\.]\+//' | sed 's/ .\+//')
-DATE=${shell grep BOOKID $(DOCBASE)-en.xml | sed 's/.\+(//' | sed 's/).\+//' }
+
+# These are obviated by new standard
+#VERSION=$(shell grep BOOKID $(DOCBASE)-en.xml | sed 's/<!ENTITY BOOKID "[^0-9\.]\+//' | sed 's/ .\+//')
+DATE=$(shell grep BOOKID $(DOCBASE)-en.xml | sed 's/.\+(//' | sed 's/).\+//')
+VERSION=$(shell grep " BOOKVERSION" $(DOCBASE)-en.xml | sed 's/.\+"\([0-9\.]\+\)".\+/\1/' )
 NOW=$(shell date +"%a %b %e %Y")
 SPECIN=../docs-common/packaging/fedora-doc.spec.in.common
 OMFIN=../docs-common/packaging/fedora-doc.omf.in.common
 DESKTOPIN=../docs-common/packaging/fedora-doc.desktop.in.common
-DOCSPEC=$(PWD)/SPECS/$(DOCBASE).spec
-DOCOMF=$(PWD)/SOURCES/fedora-doc-$(DOCBASE)-C.omf
-DOCDESKTOP=$(PWD)/SOURCES/fedora-doc-$(DOCBASE).desktop
-DOCSRCTAR=$(PWD)/SOURCES/$(DOCBASE)-$(VERSION).src.tar.gz
+DOCSPEC=$(PWD)/$(DOCBASE).spec.in
+DOCOMF=$(PWD)/fedora-doc-$(DOCBASE)-C.omf
+DOCDESKTOP=$(PWD)/fedora-doc-$(DOCBASE).desktop
+DOCSRCTAR=$(PWD)/$(DOCBASE)-$(VERSION).src.tar.gz
 TITLE=$(shell ../docs-common/packaging/titlegrab.py $(DOCBASE)-en.xml | sed 's/^ \+//')
 ######################################################
 # Some RPM flags...
 ######################################################
-RPMFLAGS=--define "docbase $(DOCBASE)" --define "version $(VERSION)" --define "_topdir $(PWD)"
+RPMFLAGS=--define "docbase $(DOCBASE)" --define "version $(VERSION)" --define "lang $(1)" --define "_topdir $(PWD)" --define "_rpmfilename %%{NAME}-$(1)-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm" --define "_sourcedir $(PWD)" --define "_rpmdir $(PWD)" --define "_specdir $(PWD)"
 ######################################################
 
-
-clean::
-	rm -rf fedora-doc-$(DOCBASE)*.rpm
-
-
-rpm: clean
-#
-# Make RPM-compliant tarball of source XML and other stuff
+$(DOCBASE)-$(VERSION).src.tar.gz::  tarball
 	mkdir $(DOCBASE)-$(VERSION)
-	find . -maxdepth 1 -type f ! \( -name '*~' -o -name 'Makefile*' \) \
+	find . -maxdepth 1 -type f ! \( -name '*~' -o -name 'Makefile*' \
+		-o -name '$(DOCBASE)*.tar.gz' \) \
 		| cpio -pamdv $(DOCBASE)-$(VERSION)
 	find . -maxdepth 1 -type d ! \( -name '$(DOCBASE)-$(VERSION)' \
 		-o -name 'CVS' -o -name '*~' -o -name '$(DOCBASE)*' \) \
 		| cpio -pamdv $(DOCBASE)-$(VERSION)
-#
-# Make RPM build tree; don't rely on local user's setup
-	mkdir -p {BUILD,RPMS/noarch,SOURCES,SPECS,SRPMS}
-	tar -zcvf $(DOCSRCTAR) $(DOCBASE)-$(VERSION)
+	( cd $(DOCBASE)-$(VERSION) ; tar xzf ../$(DOCBASE)-$(VERSION).tar.gz )
+	pwd
+	tar -zcvf $(DOCBASE)-$(VERSION).src.tar.gz $(DOCBASE)-$(VERSION)/
 	rm -rf $(DOCBASE)-$(VERSION)/
+
+
+#$(DOCBASE)-$(1)-clean::
+clean::
+	${RM} -rf fedora-doc-$(DOCBASE)*.rpm
+	${RM} -rf $(DOCBASE)-$(VERSION)*.src.tar.gz
+	${RM} -rf BUILD/ $(DOCBASE)-$(VERSION)/
+	${RM} -f *omf *desktop *spec.in
+
+
+define rpm_template
+rpm-$(1)::  clean $(DOCBASE)-$(VERSION).src.tar.gz
+# depend on source tarball and lang-specific HTML tarball
+# Make RPM build tree; don't rely on local user's setup
+	mkdir -p BUILD
 #
 # Make rpmlint happy with a changelog entry
 # FIXME: Maybe more magic would make this stickier; pity
@@ -105,8 +118,16 @@
 #
 # Do the build...
 #
-	rpmbuild -bb $(RPMFLAGS) $(DOCSPEC)
-	mv RPMS/noarch/*.rpm .
+	rpmbuild -bb $(RPMFLAGS) \
+		$(DOCSPEC)
 	rpmbuild --clean --rmsource $(RPMFLAGS) $(DOCSPEC)
-	rm -rf {BUILD,RPMS,SOURCES,SPECS,SRPMS}
-	rm -rf $(DOCBASE)-$(VERSION)
+#	rm -rf {BUILD,RPMS,SOURCES,SPECS,SRPMS}
+#	rm -rf $(DOCBASE)-$(VERSION)
+endef
+
+rpm::	$(foreach LANG,$(LANGUAGES),rpm-$(LANG))
+
+$(foreach LANG,${LANGUAGES},$(eval $(call rpm_template,${LANG})))
+
+showvars::
+	@echo "VERSION=$(VERSION)"


Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/rpm-info.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-info.xml	26 Nov 2005 21:44:18 -0000	1.2
+++ rpm-info.xml	27 Nov 2005 17:57:23 -0000	1.3
@@ -3,8 +3,19 @@
 <!-- Sample document description from which we build RPMs -->
 <!DOCTYPE rpm-info SYSTEM "../docs-common/packaging/rpm-info.dtd">
 <rpm-info>
-  <author email="tcf at redhat.com" firstname="Tammy" initials="TCF" surname="Fox" wholename="Tammy Fox"/>
-  <editor email="stickster at gmail.com" firstname="Paul" surname="Frields" wholename="Paul W. Frields"/>
+  <author>
+    <wholename>Tammy Fox</wholename>
+    <email>tcf at redhat.com</email>
+    <surname>Fox</surname>
+    <firstname>Tammy</firstname>
+    <initials>TCF</initials>
+  </author>
+  <editor>
+    <wholename>Paul W. Frields</wholename>
+    <email>stickster at gmail.com</email>
+    <surname>Frields</surname>
+    <firstname>Paul</firstname>
+  </editor>
   <license>
     <rights>GNU FDL</rights>
     <version>1.0</version>
@@ -17,21 +28,27 @@
   <titles>
     <translation lang="en">
       <title>Example Tutorial</title>
-      <desc>This is quite a feat.</desc>
+      <desc>An example tutorial for use with the Fedora Documentation Project.</desc>
     </translation>
     <translation lang="de">
-      <title>Beispeil Tutorial</title>
-      <desc>Ist idiotien</desc>
+      <title>Beispieltutorial</title>
+      <desc>Ein Beispieltutorial f??r Gebrauch mit dem Unterlagenprojekt Fedora.</desc>
     </translation>
   </titles>
   <changelog order="newest-first">
-    <revision date="Sat 26 Nov 2005" release="2" version="1.0.0" role="rpm">
-      <author email="me at home.net" firstname="Me" initials="I" surname="Myself" wholename="Me Myself"/>
+    <pkgrevision>
+      <date>Sat 26 Nov 2005</date>
+      <pkgversion>1.0.0</pkgversion>
+      <pkgrelease>2</pkgrelease>
+      <wholename>Paul W. Frields</wholename>
+      <email>stickster at gmail.com</email>
       <details>Some rpm-only changes</details>
-    </revision>
-    <revision date="2005-09-18" release="1" version="0.13">
-      <author email="stickster at gmail.com" firstname="Paul" initials="PWF" surname="Frields" wholename="Paul W. Frields"/>
+    </pkgrevision>
+    <docrevision>
+      <date>2005-09-18</date>
+      <docversion>0.13</docversion>
+      <initials>PWF</initials>
       <details>Add revision history</details>
-    </revision>
+    </docrevision>
   </changelog>
 </rpm-info>


--- example-tutorial-it.xml DELETED ---



From fedora-docs-commits at redhat.com  Sun Nov 27 17:58:32 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 27 Nov 2005 12:58:32 -0500
Subject: docs-common/packaging rpm-info.dtd,1.2,1.3
Message-ID: <200511271758.jARHwWwv022642@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22621

Modified Files:
	rpm-info.dtd 
Log Message:
Updated DTD to hopefully simplify life a little, or maybe just for fun


Index: rpm-info.dtd
===================================================================
RCS file: /cvs/docs/docs-common/packaging/rpm-info.dtd,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-info.dtd	26 Nov 2005 21:44:24 -0000	1.2
+++ rpm-info.dtd	27 Nov 2005 17:58:25 -0000	1.3
@@ -19,33 +19,28 @@
 <!ELEMENT title			(#PCDATA) 				>
 <!ELEMENT desc			(#PCDATA)				>
 
-<!ELEMENT changelog		(revision+)				>
+<!ELEMENT changelog		((docrevision|pkgrevision)+)		>
 <!ATTLIST changelog 	order  	(newest-first)  #REQUIRED 		>
 
-<!ELEMENT revision		(author+,editor*,details)		>
-<!ATTLIST revision  	date   	CDATA   	#REQUIRED 		>
-<!ATTLIST revision  	version	CDATA   	#REQUIRED 		>
-<!ATTLIST revision	release	CDATA		#REQUIRED		>
-<!ATTLIST revision	role	(doc|rpm)	"doc"			>
-
-<!ELEMENT author  		EMPTY					>
-<!ATTLIST author	wholename CDATA   	#REQUIRED 		>
-<!ATTLIST author	email     CDATA   	#REQUIRED 		>
-<!ATTLIST author  	surname   CDATA   	#REQUIRED 		>
-<!ATTLIST author  	firstname CDATA   	#REQUIRED 		>
-<!ATTLIST author  	initials  CDATA		#REQUIRED 		>
-
-<!ELEMENT editor  			EMPTY				>
-<!ATTLIST editor	wholename CDATA   #REQUIRED 			>
-<!ATTLIST editor	email     CDATA   #REQUIRED 			>
-<!ATTLIST editor  	surname   CDATA   #REQUIRED 			>
-<!ATTLIST editor  	firstname CDATA   #REQUIRED 			>
-
-
-<!ELEMENT translator  			EMPTY				>
-<!ATTLIST translator	wholename CDATA   #REQUIRED 			>
-<!ATTLIST translator	email     CDATA   #REQUIRED 			>
-<!ATTLIST translator	surname   CDATA   #REQUIRED 			>
-<!ATTLIST translator  	firstname CDATA   #REQUIRED 			>
+<!ELEMENT docrevision		(date,docversion,initials,details+)     >
+<!ELEMENT docversion            (#PCDATA)                               >
+
+<!ELEMENT pkgrevision           (date,pkgversion,pkgrelease,wholename,email,details+) >
+<!-- pkgversion will often key off docversion, but not necessarily -->
+<!ELEMENT pkgversion            (#PCDATA)                               >
+<!ELEMENT pkgrelease            (#PCDATA)                               >
+
+<!-- used in both docrevision and pkgrevision elements -->
+<!ELEMENT date                  (#PCDATA)                               >
+<!ELEMENT details               (#PCDATA)                               >
+
+<!ELEMENT author  		(wholename,email,surname,firstname,initials) >
+<!ELEMENT editor                (wholename,email,surname,firstname) >
+<!ELEMENT translator            (wholename,email,surname,firstname) >
+
+<!ELEMENT wholename             (#PCDATA)                               >
+<!ELEMENT email                 (#PCDATA)                               >
+<!ELEMENT surname               (#PCDATA)                               >
+<!ELEMENT firstname             (#PCDATA)                               >
+<!ELEMENT initials              (#PCDATA)                               >
 
-<!ELEMENT details		(#PCDATA)				>



From fedora-docs-commits at redhat.com  Sun Nov 27 19:28:23 2005
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sun, 27 Nov 2005 14:28:23 -0500
Subject: release-notes install-notes-it.xml,1.3,1.4
Message-ID: <200511271928.jARJSNj8026118@cvs-int.fedora.redhat.com>

Author: tombo

Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26101/release-notes

Modified Files:
	install-notes-it.xml 
Log Message:
Fixing tag usage and extraneous quotemarks used to denote meaning.


Index: install-notes-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-it.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- install-notes-it.xml	25 Nov 2005 21:12:13 -0000	1.3
+++ install-notes-it.xml	27 Nov 2005 19:28:15 -0000	1.4
@@ -240,7 +240,7 @@
 	  Certe configurazioni hardware (in particolare quelle con
 	  gli schermi LCD) potrebbero dare problemi durante l'avvio del
 	  programma d'installazione di &DISTRO;.  In queste circostanze, ricominciate
-	  l'installazione, ed aggiungete l'opzione "<command>nofb</command>" nella
+	  l'installazione, ed aggiungete l'opzione <option>nofb</option> nella
 	  linea di comando di boot.
 	</para>
 	<note>



From fedora-docs-commits at redhat.com  Sun Nov 27 23:28:05 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 27 Nov 2005 18:28:05 -0500
Subject: docs-common/packaging rpm-info.dtd,1.3,1.4
Message-ID: <200511272328.jARNS5XE001041@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1009/docs-common/packaging

Modified Files:
	rpm-info.dtd 
Log Message:
Experiment over, reverted rpm-info tests


Index: rpm-info.dtd
===================================================================
RCS file: /cvs/docs/docs-common/packaging/rpm-info.dtd,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-info.dtd	27 Nov 2005 17:58:25 -0000	1.3
+++ rpm-info.dtd	27 Nov 2005 23:27:58 -0000	1.4
@@ -19,28 +19,33 @@
 <!ELEMENT title			(#PCDATA) 				>
 <!ELEMENT desc			(#PCDATA)				>
 
-<!ELEMENT changelog		((docrevision|pkgrevision)+)		>
+<!ELEMENT changelog		(revision+)				>
 <!ATTLIST changelog 	order  	(newest-first)  #REQUIRED 		>
 
-<!ELEMENT docrevision		(date,docversion,initials,details+)     >
-<!ELEMENT docversion            (#PCDATA)                               >
-
-<!ELEMENT pkgrevision           (date,pkgversion,pkgrelease,wholename,email,details+) >
-<!-- pkgversion will often key off docversion, but not necessarily -->
-<!ELEMENT pkgversion            (#PCDATA)                               >
-<!ELEMENT pkgrelease            (#PCDATA)                               >
-
-<!-- used in both docrevision and pkgrevision elements -->
-<!ELEMENT date                  (#PCDATA)                               >
-<!ELEMENT details               (#PCDATA)                               >
-
-<!ELEMENT author  		(wholename,email,surname,firstname,initials) >
-<!ELEMENT editor                (wholename,email,surname,firstname) >
-<!ELEMENT translator            (wholename,email,surname,firstname) >
-
-<!ELEMENT wholename             (#PCDATA)                               >
-<!ELEMENT email                 (#PCDATA)                               >
-<!ELEMENT surname               (#PCDATA)                               >
-<!ELEMENT firstname             (#PCDATA)                               >
-<!ELEMENT initials              (#PCDATA)                               >
+<!ELEMENT revision		(author+,editor*,details)		>
+<!ATTLIST revision  	date   	CDATA   	#REQUIRED 		>
+<!ATTLIST revision  	version	CDATA   	#REQUIRED 		>
+<!ATTLIST revision	release	CDATA		#REQUIRED		>
+<!ATTLIST revision	role	(doc|rpm)	"doc"			>
+
+<!ELEMENT author  		EMPTY					>
+<!ATTLIST author	wholename CDATA   	#REQUIRED 		>
+<!ATTLIST author	email     CDATA   	#REQUIRED 		>
+<!ATTLIST author  	surname   CDATA   	#REQUIRED 		>
+<!ATTLIST author  	firstname CDATA   	#REQUIRED 		>
+<!ATTLIST author  	initials  CDATA		#REQUIRED 		>
+
+<!ELEMENT editor  			EMPTY				>
+<!ATTLIST editor	wholename CDATA   #REQUIRED 			>
+<!ATTLIST editor	email     CDATA   #REQUIRED 			>
+<!ATTLIST editor  	surname   CDATA   #REQUIRED 			>
+<!ATTLIST editor  	firstname CDATA   #REQUIRED 			>
+
+
+<!ELEMENT translator  			EMPTY				>
+<!ATTLIST translator	wholename CDATA   #REQUIRED 			>
+<!ATTLIST translator	email     CDATA   #REQUIRED 			>
+<!ATTLIST translator	surname   CDATA   #REQUIRED 			>
+<!ATTLIST translator  	firstname CDATA   #REQUIRED 			>
 
+<!ELEMENT details		(#PCDATA)				>



From fedora-docs-commits at redhat.com  Sun Nov 27 23:28:00 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 27 Nov 2005 18:28:00 -0500
Subject: example-tutorial rpm-info.xml,1.3,1.4
Message-ID: <200511272328.jARNSUGf001044@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1009/example-tutorial

Modified Files:
	rpm-info.xml 
Log Message:
Experiment over, reverted rpm-info tests


Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/rpm-info.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-info.xml	27 Nov 2005 17:57:23 -0000	1.3
+++ rpm-info.xml	27 Nov 2005 23:27:52 -0000	1.4
@@ -3,19 +3,8 @@
 <!-- Sample document description from which we build RPMs -->
 <!DOCTYPE rpm-info SYSTEM "../docs-common/packaging/rpm-info.dtd">
 <rpm-info>
-  <author>
-    <wholename>Tammy Fox</wholename>
-    <email>tcf at redhat.com</email>
-    <surname>Fox</surname>
-    <firstname>Tammy</firstname>
-    <initials>TCF</initials>
-  </author>
-  <editor>
-    <wholename>Paul W. Frields</wholename>
-    <email>stickster at gmail.com</email>
-    <surname>Frields</surname>
-    <firstname>Paul</firstname>
-  </editor>
+  <author email="tcf at redhat.com" firstname="Tammy" initials="TCF" surname="Fox" wholename="Tammy Fox"/>
+  <editor email="stickster at gmail.com" firstname="Paul" surname="Frields" wholename="Paul W. Frields"/>
   <license>
     <rights>GNU FDL</rights>
     <version>1.0</version>
@@ -28,27 +17,21 @@
   <titles>
     <translation lang="en">
       <title>Example Tutorial</title>
-      <desc>An example tutorial for use with the Fedora Documentation Project.</desc>
+      <desc>This is quite a feat.</desc>
     </translation>
     <translation lang="de">
-      <title>Beispieltutorial</title>
-      <desc>Ein Beispieltutorial f??r Gebrauch mit dem Unterlagenprojekt Fedora.</desc>
+      <title>Beispeil Tutorial</title>
+      <desc>Ist idiotien</desc>
     </translation>
   </titles>
   <changelog order="newest-first">
-    <pkgrevision>
-      <date>Sat 26 Nov 2005</date>
-      <pkgversion>1.0.0</pkgversion>
-      <pkgrelease>2</pkgrelease>
-      <wholename>Paul W. Frields</wholename>
-      <email>stickster at gmail.com</email>
+    <revision date="Sat 26 Nov 2005" release="2" version="1.0.0" role="rpm">
+      <author email="me at home.net" firstname="Me" initials="I" surname="Myself" wholename="Me Myself"/>
       <details>Some rpm-only changes</details>
-    </pkgrevision>
-    <docrevision>
-      <date>2005-09-18</date>
-      <docversion>0.13</docversion>
-      <initials>PWF</initials>
+    </revision>
+    <revision date="2005-09-18" release="1" version="0.13">
+      <author email="stickster at gmail.com" firstname="Paul" initials="PWF" surname="Frields" wholename="Paul W. Frields"/>
       <details>Add revision history</details>
-    </docrevision>
+    </revision>
   </changelog>
 </rpm-info>



From fedora-docs-commits at redhat.com  Mon Nov 28 01:36:22 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sun, 27 Nov 2005 20:36:22 -0500
Subject: example-tutorial example-tutorial-de.xml,1.1,1.2
Message-ID: <200511280136.jAS1aM5l004761@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4744

Modified Files:
	example-tutorial-de.xml 
Log Message:
Mark this "*-de.xml" with an "de" language, not with "it" lang.



Index: example-tutorial-de.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/example-tutorial-de.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- example-tutorial-de.xml	27 Nov 2005 17:57:23 -0000	1.1
+++ example-tutorial-de.xml	28 Nov 2005 01:36:14 -0000	1.2
@@ -18,7 +18,7 @@
 <!-- yet. -->
 
 
-<article id="example-tutorial" lang="it">
+<article id="example-tutorial" lang="de">
   <articleinfo>
     <title>Example Tutorial</title>
     <copyright>



From fedora-docs-commits at redhat.com  Mon Nov 28 22:49:54 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 28 Nov 2005 17:49:54 -0500
Subject: docs-common/packaging desktop.xsl,1.1,1.2
Message-ID: <200511282249.jASMnsYV014336@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14319

Modified Files:
	desktop.xsl 
Log Message:
Put some good advice to use; we'll figure out a khelpcenter version as we go


Index: desktop.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/desktop.xsl,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- desktop.xsl	25 Nov 2005 20:52:52 -0000	1.1
+++ desktop.xsl	28 Nov 2005 22:49:46 -0000	1.2
@@ -19,7 +19,11 @@
 <xsl:for-each select="/rpm-info/titles/translation">
 Name[<xsl:value-of select="@lang"/>]=<xsl:value-of select="title"/>
 Comment[<xsl:value-of select="@lang"/>]=<xsl:value-of select="desc"/>
-Exec[<xsl:value-of select="@lang"/>]=gnome-help file://usr/share/doc/fedora-doc-<xsl:value-of select="$docbase"/>/<xsl:value-of select="@lang"/>/<xsl:value-of select="$docbase"/>-<xsl:value-of select="@lang"/>.xml
+Exec[<xsl:value-of select="@lang"/>]=gnome-help
+      file://usr/share/doc/fedora-doc-<xsl:value-of
+	select="$docbase"/>/<xsl:value-of select="@lang"/>/<xsl:value-of
+	select="$docbase"/>-<xsl:value-of select="@lang"/>.xml
+OnlyShownIn=GNOME;
 </xsl:for-each>
 
 </xsl:template>



From fedora-docs-commits at redhat.com  Tue Nov 29 03:00:08 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 28 Nov 2005 22:00:08 -0500
Subject: yum-software-management yum-software-management-en.xml,1.49,1.50
Message-ID: <200511290300.jAT308Gn021226@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21199

Modified Files:
	yum-software-management-en.xml 
Log Message:
Changed &FED; entity to &FC; where a version is used, since FC itself is the only thing which can carry a version number.


Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- yum-software-management-en.xml	15 Nov 2005 00:13:03 -0000	1.49
+++ yum-software-management-en.xml	29 Nov 2005 02:59:54 -0000	1.50
@@ -4,10 +4,13 @@
 <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
 %FEDORA-ENTITIES-EN;
 
-<!ENTITY BOOKID "yum-software-management-1.0.4 (2005-11-15)"> <!-- change version of manual and date here -->
+<!ENTITY DOCNAME "yum-software-management">
+<!ENTITY DOCVERSION "1.0.5">
+<!ENTITY DOCDATE "2005-11-28">
+<!ENTITY DOCID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)">
+<!-- this will soon vanish -->
+<!ENTITY BOOKID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)">
 
-<!-- Bugzilla bug number for the draft notice -->
-<!ENTITY BUG-NUM "155190">
 <!ENTITY FCLOCALVER "4">
 
 ]>
@@ -108,6 +111,16 @@
           </para>
         </revdescription>
       </revision>
+      <revision>
+	<revnumber>1.0.5</revnumber>
+	<date>2005-11-28</date>
+	<authorinitials>PaulWFrields</authorinitials>
+	<revdescription>
+	  <para>
+	    Fixed some uses of "&FED;" to read "&FC;" where appropriate.
+	  </para>
+	</revdescription>
+      </revision>
     </revhistory>
   </articleinfo>
 
@@ -149,14 +162,14 @@
       </para>
 
       <note>
-        <title>Previous Versions of &FED;</title>
+        <title>Previous Versions of &FC;</title>
 
         <para>
           This document describes the configuration of
-          <command>yum</command> on &FED; &FCLOCALVER; systems. You must
+          <command>yum</command> on &FC; &FCLOCALVER; systems. You must
           perform the additional step noted in
           <xref linkend="sn-authorizing-package-sources" /> to enable
-          <command>yum</command> on &FED; 3.
+          <command>yum</command> on &FC; 3.
         </para>
       </note>
 
@@ -331,7 +344,7 @@
 
       <para>
         A network of servers provide several repositories for each
-        version of &FED;. The package management utilities in &FC; are
+        version of &FC;. The package management utilities in &FC; are
         already configured to use three of these repositories:
       </para>
 
@@ -371,11 +384,11 @@
       </variablelist>
 
       <note>
-        <title>Previous Versions of &FED;</title>
+        <title>Previous Versions of &FC;</title>
 
         <para>
-          &FED; &FCLOCALVER; automatically supports the three
-          repositories listed above. You must manually configure &FED; 3
+          &FC; &FCLOCALVER; automatically supports the three
+          repositories listed above. You must manually configure &FC; 3
           systems to use &FEX;, as noted in
           <xref linkend="sn-using-repositories"/>.
         </para>
@@ -1250,11 +1263,11 @@
       <title>&FEX; Repositories for Previous Versions of &FC;</title>
 
       <para>
-        You must manually configure &FED; 3 systems to use &FEX;, using
+        You must manually configure &FC; 3 systems to use &FEX;, using
         the instructions at
         <ulink
 	  url="http://fedora.redhat.com/projects/extras/"/>. For
-        additional packages for &FED; 1 and &FED; 2, refer to
+        additional packages for &FC; 1 and &FC; 2, refer to
         <ulink
 	  url="http://www.fedora.us/"/>.
       </para>
@@ -1317,9 +1330,9 @@
         <title>Repositories and <application>up2date</application> Channels</title>
 
         <para>
-          Starting with &FED; 4, <command>yum</command> repositories are
+          Starting with &FC; 4, <command>yum</command> repositories are
           automatically used as <application>up2date</application>
-          channels. On &FED; 3 and earlier systems, you must manually
+          channels. On &FC; 3 and earlier systems, you must manually
           configure <application>up2date</application> to use these
           channels. To do so, edit the
           <filename>/etc/sysconfig/rhn/sources</filename> file.
@@ -1364,11 +1377,11 @@
       </para>
 
       <important>
-        <title>Importing the &FED; Key on &FED; 3</title>
+        <title>Importing the &FED; Key on &FC; 3</title>
 
         <para>
           To add the &FED; public key to the <command>rpm</command>
-          keyring on &FED; 3 systems, run the command <command>su -c
+          keyring on &FC; 3 systems, run the command <command>su -c
           'rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora'</command>.
         </para>
       </important>
@@ -1426,8 +1439,8 @@
         <para>
           The data format for repository indexes changed with version
           2.1 of <command>yum</command>. This was the version supplied
-          with &FED; 3. Repository providers should specify the versions
-          of &FED; that they support. To confirm that an unlabeled
+          with &FC; 3. Repository providers should specify the versions
+          of &FC; that they support. To confirm that an unlabeled
           repository is compatible with current versions of
           <command>yum</command>, check that it has a sub-directory
           called <filename>repodata/</filename>.



From fedora-docs-commits at redhat.com  Tue Nov 29 15:52:57 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 29 Nov 2005 10:52:57 -0500
Subject: docs-common Makefile.common,1.13,1.14
Message-ID: <200511291552.jATFqv61014046@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14011

Modified Files:
	Makefile.common 
Log Message:
Corrected bug #174469 - Typo prevents over-ride of the ${XSLHTMLNOCHUNKS}
value.



Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- Makefile.common	15 Nov 2005 23:10:46 -0000	1.13
+++ Makefile.common	29 Nov 2005 15:52:49 -0000	1.14
@@ -40,7 +40,7 @@
 ifeq	(${XSLHTML},)
 XSLHTML        	= ${FDPDIR}/docs-common/xsl/main-html.xsl
 endif
-ifeq	(${XSHTMLNOCHUNKS},)
+ifeq	(${XSLHTMLNOCHUNKS},)
 XSLHTMLNOCHUNKS	= ${FDPDIR}/docs-common/xsl/main-html-nochunks.xsl
 endif
 #########################################################################



From fedora-docs-commits at redhat.com  Tue Nov 29 17:41:22 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 29 Nov 2005 12:41:22 -0500
Subject: docs-common/packaging desktop.xsl,1.2,1.3
Message-ID: <200511291741.jATHfMub019921@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/packaging
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19904

Modified Files:
	desktop.xsl 
Log Message:
Oops, didn't watch fill... fixed


Index: desktop.xsl
===================================================================
RCS file: /cvs/docs/docs-common/packaging/desktop.xsl,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- desktop.xsl	28 Nov 2005 22:49:46 -0000	1.2
+++ desktop.xsl	29 Nov 2005 17:41:14 -0000	1.3
@@ -19,10 +19,7 @@
 <xsl:for-each select="/rpm-info/titles/translation">
 Name[<xsl:value-of select="@lang"/>]=<xsl:value-of select="title"/>
 Comment[<xsl:value-of select="@lang"/>]=<xsl:value-of select="desc"/>
-Exec[<xsl:value-of select="@lang"/>]=gnome-help
-      file://usr/share/doc/fedora-doc-<xsl:value-of
-	select="$docbase"/>/<xsl:value-of select="@lang"/>/<xsl:value-of
-	select="$docbase"/>-<xsl:value-of select="@lang"/>.xml
+Exec[<xsl:value-of select="@lang"/>]=gnome-help file://usr/share/doc/fedora-doc-<xsl:value-of select="$docbase"/>/<xsl:value-of select="@lang"/>/<xsl:value-of select="$docbase"/>-<xsl:value-of select="@lang"/>.xml
 OnlyShownIn=GNOME;
 </xsl:for-each>
 



From fedora-docs-commits at redhat.com  Tue Nov 29 21:24:01 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 29 Nov 2005 16:24:01 -0500
Subject: docs-common/bin bulkbuild,1.2,1.3
Message-ID: <200511292124.jATLO12C028162@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28145

Modified Files:
	bulkbuild 
Log Message:
Remove interaction


Index: bulkbuild
===================================================================
RCS file: /cvs/docs/docs-common/bin/bulkbuild,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- bulkbuild	16 Nov 2005 02:02:10 -0000	1.2
+++ bulkbuild	29 Nov 2005 21:23:54 -0000	1.3
@@ -14,6 +14,7 @@
 HTMLDIR="${HOME}/fdpdocs-html"
 # Do this anonymously for now
 ANONCVS=":pserver:anonymous at cvs.fedora.redhat.com:2401/cvs/docs"
+#INTERACT=no #default
 
 mkdir "${FDPDIR}" || ( echo "Could not mkdir ${FDPDIR}" ; exit 254 )
 mkdir "${HTMLDIR}" || ( echo "Could not mkdir ${FDPDIR}" ; exit 254 )
@@ -39,14 +40,16 @@
     
 
 popd >/dev/null
-echo -n "OK to remove temp dir ${FDPDIR} [y/n]? "
-read -sn1 REPLY
-case $REPLY in
-    y|Y )
-	rm -rf "${FDPDIR}"
-	echo
-	;;
-    * )
-	echo "... not removed."
-	;;
-esac
+if [ ! -z "$INTERACT" ]; then
+    echo -n "OK to remove temp dir ${FDPDIR} [y/n]? "
+    read -sn1 REPLY
+    case $REPLY in
+	y|Y )
+	    rm -rf "${FDPDIR}"
+	    echo
+	    ;;
+	* )
+	    echo "... not removed."
+	    ;;
+    esac
+fi



From fedora-docs-commits at redhat.com  Tue Nov 29 21:42:41 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 29 Nov 2005 16:42:41 -0500
Subject: docs-common/bin use-prod-css,NONE,1.1
Message-ID: <200511292142.jATLgftt028294@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28240/bin

Added Files:
	use-prod-css 
Log Message:
Change default to the HTML "fedora-draft.css" stylesheet to reinforce
that the rendering here is not meant to be the final production rendering.
Provided the "bin/use-prod-css" to locally change HTML files to minic
production-quality rendering.  NOTE: draft watermarking does NOT PRINT 
unless the browser preferences enable background image printing.



--- NEW FILE use-prod-css ---
#!/bin/bash
########################################################################
# Tommy.Reynolds <Tommy.Reynolds at MegaCoder.com>
# International copyright secured (C) 2005, All rights reserved.
# This software is licensed under the GPL.
########################################################################
# Do surgery on the *.html files to reference the production CSS stylesheet
#
# Use like this:
#
#	use-prod-css /path/to/docdir
#
########################################################################
USAGE="usage: $(basename $0) /path/to/docdir"
SILENT=yes
while getopts v c
do
	case "${c}" in
	v )	SILENT="";;
	* )	echo "${USAGE}" >&2; exit 1;;
	esac
done
shift $(expr ${OPTIND} - 1)
if [ $# -gt 1 ]; then
	echo "${USAGE}" >&2
	exit 1
fi
find ${1:-.} -iname '*.html' -print					|
while read f; do
	[ "${SILENT}" ] || echo ${f}
	sed 's/href="fedora-draft.css"/href="fedora.css"/' ${f} >${f}.tmp
	mv ${f}.tmp ${f}
done



From fedora-docs-commits at redhat.com  Tue Nov 29 21:42:46 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 29 Nov 2005 16:42:46 -0500
Subject: docs-common/xsl html-common-relnotes.xsl, 1.1, 1.2 html-common.xsl,
	1.9, 1.10
Message-ID: <200511292142.jATLgkPT028308@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common/xsl
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28240/xsl

Modified Files:
	html-common-relnotes.xsl html-common.xsl 
Log Message:
Change default to the HTML "fedora-draft.css" stylesheet to reinforce
that the rendering here is not meant to be the final production rendering.
Provided the "bin/use-prod-css" to locally change HTML files to minic
production-quality rendering.  NOTE: draft watermarking does NOT PRINT 
unless the browser preferences enable background image printing.



Index: html-common-relnotes.xsl
===================================================================
RCS file: /cvs/docs/docs-common/xsl/html-common-relnotes.xsl,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- html-common-relnotes.xsl	2 Jun 2005 18:23:47 -0000	1.1
+++ html-common-relnotes.xsl	29 Nov 2005 21:42:39 -0000	1.2
@@ -30,7 +30,7 @@
 <xsl:param name="generate.legalnotice.link" select="1"></xsl:param>
 -->
 
-<xsl:param name="html.stylesheet" select="'fedora.css'"></xsl:param>
+<xsl:param name="html.stylesheet" select="'fedora-draft.css'"></xsl:param>
 <xsl:param name="html.stylesheet.type">text/css</xsl:param>
 
 <xsl:param name="html.cleanup" select="1"></xsl:param>


Index: html-common.xsl
===================================================================
RCS file: /cvs/docs/docs-common/xsl/html-common.xsl,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- html-common.xsl	29 Jun 2005 14:32:49 -0000	1.9
+++ html-common.xsl	29 Nov 2005 21:42:39 -0000	1.10
@@ -25,7 +25,7 @@
 
 <xsl:output method="html" indent="no"/>
 
-<xsl:param name="html.stylesheet" select="'fedora.css'"></xsl:param>
+<xsl:param name="html.stylesheet" select="'fedora-draft.css'"></xsl:param>
 <xsl:param name="html.stylesheet.type">text/css</xsl:param>
 
 <xsl:param name="html.cleanup" select="1"></xsl:param>



From fedora-docs-commits at redhat.com  Tue Nov 29 21:42:35 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 29 Nov 2005 16:42:35 -0500
Subject: docs-common Makefile.common,1.14,1.15
Message-ID: <200511292143.jATLh5ND028315@cvs-int.fedora.redhat.com>

Author: jtr

Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28240

Modified Files:
	Makefile.common 
Log Message:
Change default to the HTML "fedora-draft.css" stylesheet to reinforce
that the rendering here is not meant to be the final production rendering.
Provided the "bin/use-prod-css" to locally change HTML files to minic
production-quality rendering.  NOTE: draft watermarking does NOT PRINT 
unless the browser preferences enable background image printing.



Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- Makefile.common	29 Nov 2005 15:52:49 -0000	1.14
+++ Makefile.common	29 Nov 2005 21:42:28 -0000	1.15
@@ -64,7 +64,8 @@
 #  LANG=en.UTF-8 ${XMLTO} html -x $(XSLHTML) -o mydoc-en mydoc-en.xml
 #  mkdir -p mydoc-en/stylesheet-images
 #  cp ${FDPDIR}/docs-common/stylesheet-images/*.png mydoc-en/stylesheet-images/
-#  cp ${FDPDIR}/docs-common/css/fedora.css mydoc-en/
+#  cp ${FDPDIR}/docs-common/css/fedora*.css mydoc-en/
+#  cp ${FDPDIR}/docs-common/images/watermark.png mydoc-en/
 #  mkdir -p mydoc-en/figs
 #  cp -p figs/*-${LANG}.* mydoc-en/figs
 # but we do avoid copying EPS files since they are nonsense to the HTML world.
@@ -76,7 +77,8 @@
 	LANG=$(1).UTF-8 ${XMLTO} html -x $(XSLHTML) -o $(DOCBASE)-$(1) $(DOCBASE)-$(1).xml
 	mkdir -p $(DOCBASE)-$(1)/stylesheet-images/
 	cp ${FDPDIR}/docs-common/stylesheet-images/*.png $(DOCBASE)-$(1)/stylesheet-images
-	cp ${FDPDIR}/docs-common/css/fedora.css $$(DOCBASE)-$(1)/
+	cp ${FDPDIR}/docs-common/css/fedora*.css $$(DOCBASE)-$(1)/
+	cp ${FDPDIR}/docs-common/images/watermark.png $${DOCBASE}-$(1)/
 	[ ! -d figs ] || (						\
 		mkdir -p ${DOCBASE}-$(1)/figs;				\
 		find figs -type f -iname '*.*' -print		|	\
@@ -97,7 +99,8 @@
 	${XMLTO} html-nochunks -x $(XSLHTMLNOCHUNKS) $(DOCBASE)-$(1).xml
 	mkdir -p stylesheet-images/
 	cp ${FDPDIR}/docs-common/stylesheet-images/*.png stylesheet-images/
-	cp ${FDPDIR}/docs-common/css/fedora.css .
+	cp ${FDPDIR}/docs-common/css/fedora*.css .
+	cp ${FDPDIR}/docs-common/images/watermark.png .
 endef
 #
 html-nochunks::	$(foreach LANG,${LANGUAGES},$(DOCBASE)-$(LANG).html)
@@ -133,9 +136,10 @@
 define	CLEAN_template
 ${DOCBASE}-$(1)-clean::
 	${RM} -r ${DOCBASE}-$(1)
-	${RM} -r ${DOCBASE}-$(1).html stylesheet-images fedora.css
+	${RM} -r ${DOCBASE}-$(1).html stylesheet-images
 	${RM} -r ${DOCBASE}-$(1).pdf
 	${RM} -r ${DOCBASE}-$(1).tar.gz
+	${RM} fedora*.css watermark.png
 endef
 #
 distclean clean:: $(foreach LANG,${LANGUAGES},${DOCBASE}-${LANG}-clean)



From fedora-docs-commits at redhat.com  Wed Nov 30 12:56:37 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Wed, 30 Nov 2005 07:56:37 -0500
Subject: docs-common/bin bulkbuild,1.3,1.4
Message-ID: <200511301256.jAUCubh9023521@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23504

Modified Files:
	bulkbuild 
Log Message:
Update bulkbuild for more flexibility


Index: bulkbuild
===================================================================
RCS file: /cvs/docs/docs-common/bin/bulkbuild,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- bulkbuild	29 Nov 2005 21:23:54 -0000	1.3
+++ bulkbuild	30 Nov 2005 12:56:30 -0000	1.4
@@ -1,7 +1,9 @@
 #!/bin/bash
 #
+# Written by stickster :)
+#
 # Pull all active FDP docs from CVS, build and install HTML in
-# folder $HOME/fdpdocs-html.
+# TARGETDIR folder.
 #
 # This script is not designed to be run inside a local CVS repository;
 # it is only stored here for convenience and upkeep.  It may be used
@@ -9,47 +11,158 @@
 # hand, it may be vaporized.
 #
 
+MYSELF="$(basename "$0")"
 NOW="$(date +%Y%m%d%H%M%S)"
-FDPDIR="${HOME}/fdpdocs-cvs${NOW}"
-HTMLDIR="${HOME}/fdpdocs-html"
-# Do this anonymously for now
-ANONCVS=":pserver:anonymous at cvs.fedora.redhat.com:2401/cvs/docs"
-#INTERACT=no #default
 
+print_usage() {
+    echo "$MYSELF: Usage: $MYSELF [options...]"
+    echo "   -m WORKDIR   : set home directory, default $HOME"
+    echo "   -f FDPDIR    : set d/l dir for CVS, default $FDPDIR"
+    echo "   -D TARGETDIR : set target dir for built files, default $TARGETDIR"
+    echo "   -a ANONCVS   : set CVS repo location (cvs -d), default $ANONCVS"
+    echo "   -r REV       : checkout REV from CVS (global), default $REV"
+    echo "   -Q           : make CVS checkout less quiet"
+    echo "   -c           : build chunked HTML"
+    echo "   -n           : build HTML nochunks"
+    echo "   -p           : build PDF (not working currently)"
+    echo "   -t           : build tarball"
+    echo "   -h           : print usage (this message)"
+}
+
+
+set_vars() {
+    [ -z "$WORKDIR" ] && WORKDIR="${HOME}"
+    [ -z "$FDPDIR" ] && FDPDIR="${WORKDIR}/fdpdocs-cvs${NOW}"
+    [ -z "$TARGETDIR" ] && TARGETDIR="/var/www/webtest/docs"
+    # Do this anonymously for now
+    [ -z "$ANONCVS" ] && ANONCVS=":pserver:anonymous at cvs.fedora.redhat.com:/cvs/docs"
+    [ -z "$REV" ] && REV="HEAD"
+    [ -z "$REDIR" ] && REDIR="/dev/null"
+    [ -z "$QUIET" ] && QUIET="-Q"
+}
+
+
+# just to make sure defaults are read
+unset FDPDIR HTMLDIR ANONCVS TAG CHUNKS NOCHUNKS PDF TARBALL VERBOSE
+BUILDS=0
+
+while getopts "m:f:D:a:r:Qcnpthv" OPT; do
+    case $OPT in
+	m )
+	    WORKDIR="$OPTARG"
+	    ;;
+	f )
+	    FDPDIR="$OPTARG"
+	    ;;
+	D )
+	    TARGETDIR="$OPTARG"
+	    ;;
+	a )
+	    ANONCVS="$OPTARG"
+	    ;;
+	r )
+	    REV="$OPTARG"
+	    ;;
+	Q )
+	    QUIET="-q"
+	    ;;
+	c )
+	    CHUNKS="yes"
+	    BUILDS=$(($BUILDS+1))
+	    ;;
+	n )
+	    NOCHUNKS="yes"
+	    BUILDS=$(($BUILDS+1))
+	    ;;
+	p )
+	    PDF="yes"  # But PDF doesn't work yet, don't do this!
+	    BUILDS=$(($BUILDS+1))
+	    ;;
+	t )
+	    TARBALL="yes"
+	    BUILDS=$(($BUILDS+1))
+	    ;;
+	h )
+	    set_vars
+	    print_usage
+	    exit 0
+	    ;;
+	v )
+	    REDIR="/dev/stdout"
+	    ;;
+	* )
+	    echo "$MYSELF: invalid option: $OPT"
+	    print_usage
+	    exit 10
+	    ;;
+    esac
+done
+shift $(($OPTIND - 1))
+
+
+if [ $BUILDS -lt 1 ]; then
+    echo "$MYSELF: nothing to do, try selecting one of [-c|-n|-p|-t]"
+    exit 20
+fi
+
+
+set_vars
 mkdir "${FDPDIR}" || ( echo "Could not mkdir ${FDPDIR}" ; exit 254 )
-mkdir "${HTMLDIR}" || ( echo "Could not mkdir ${FDPDIR}" ; exit 254 )
+mkdir -p "${TARGETDIR}" || ( echo "Could not mkdir ${FDPDIR}" ; exit 254 )
 pushd "${FDPDIR}" >/dev/null || ( echo "Could not pushd ${FDPDIR}" ; exit 253 )
 
-cvs -d $ANONCVS login
-cvs -qz3 -d $ANONCVS co docs-common
+
+echo "Checking out docs-common from Fedora Docs CVS"
+#cvs -d $ANONCVS login
+cvs "$QUIET" -z3 -d $ANONCVS co docs-common
+
 
 for DOC in `cat docs-common/bin/active`; do
-    cvs -qz3 -d $ANONCVS co $DOC
+    DONE=""
+    echo "Checking out module $DOC from Fedora Docs CVS"
+    cvs "$QUIET" -z3 -d $ANONCVS co $DOC 2>&1 > $REDIR
     pushd "$DOC" >/dev/null || (echo "Couldn't cd to $DOCDIR" ; exit 252 )
     make showvars > tmpvars
     . tmpvars
     rm -f tmpvars
-    make html
-    for LANG in $LANGUAGES ; do
-	DESTDIR="${HTMLDIR}/${DOCBASE}/${LANG}"
-	mkdir -p "${DESTDIR}"
-	cp -a "${DOCBASE}-${LANG}"/* "${DESTDIR}"
-    done
+    if [ "$CHUNKS" = "yes" ]; then
+	echo "Making chunked HTML for ${DOCBASE}"
+	make html 2>&1 > $REDIR || ( echo "$MYSELF: CHUNKS failed" ;\
+	    exit 251 )
+	for LANG in $LANGUAGES ; do
+	    DESTDIR="${TARGETDIR}/${DOCBASE}/${LANG}"
+	    [ ! -d "$DESTDIR" ] && mkdir -p $DESTDIR
+	    cp -r "${DOCBASE}-${LANG}/"* "${DESTDIR}"
+	done
+    fi
+    if [ "$NOCHUNKS" = "yes" ]; then
+	echo "Making nochunks HTML for ${DOCBASE}"
+	mak html-nochunks 2>&1 > $REDIR || ( echo "$MYSELF: NOCHUNKS failed" ;\
+	    exit 251 )
+	for LANG in $LANGUAGES ; do
+	    DESTDIR="${TARGETDIR}/${DOCBASE}/" # add $LANG if desired
+	    [ ! -d "$DESTDIR" ] && mkdir -p $DESTDIR
+	    cp -r "${DOCBASE}-${LANG}.html" "${DESTDIR}"
+	done
+    fi
+    if [ "$TARBALL" = "yes" ]; then
+	echo "Making tarball for ${DOCBASE}"
+	make tarball 2>&1 > $REDIR || ( echo "$MYSELF: TARBALL failed" ;\
+	    exit 251 )
+	for LANG in $LANGUAGES ; do
+	    DESTDIR="${TARGETDIR}/${DOCBASE}/" # add $LANG if desired
+	    [ ! -d "$DESTDIR" ] && mkdir -p $DESTDIR
+	    cp -r "${DOCBASE}-${LANG}.tar.gz" "${DESTDIR}"
+	done
+    fi
+
     popd >/dev/null
+    
 done
     
 
 popd >/dev/null
-if [ ! -z "$INTERACT" ]; then
-    echo -n "OK to remove temp dir ${FDPDIR} [y/n]? "
-    read -sn1 REPLY
-    case $REPLY in
-	y|Y )
-	    rm -rf "${FDPDIR}"
-	    echo
-	    ;;
-	* )
-	    echo "... not removed."
-	    ;;
-    esac
-fi
+[ "$FDPDIR" != "/" ] && [ "$FDPDIR" != "$HOME" ] && rm -rf "${FDPDIR}"
+exit 0
+
+



From fedora-docs-commits at redhat.com  Wed Nov 30 12:57:32 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Wed, 30 Nov 2005 07:57:32 -0500
Subject: docs-common/bin xmlformat-fdp.conf,1.7,1.8
Message-ID: <200511301257.jAUCvWa5023551@cvs-int.fedora.redhat.com>

Author: pfrields

Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23529

Modified Files:
	xmlformat-fdp.conf 
Log Message:
Add some nicety for OMF files


Index: xmlformat-fdp.conf
===================================================================
RCS file: /cvs/docs/docs-common/bin/xmlformat-fdp.conf,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- xmlformat-fdp.conf	9 Nov 2005 23:42:29 -0000	1.7
+++ xmlformat-fdp.conf	30 Nov 2005 12:57:25 -0000	1.8
@@ -35,6 +35,7 @@
 revnumber date authorinitials
   entry-break = 0
   exit-break = 0
+  normalize = yes
 
 revremark
   normalize = yes
@@ -100,3 +101,10 @@
 ulink xref
   format = inline
 
+# Cover OMF files
+creator description format identifier language maintainer omf relation rights subject type version
+  format = block
+  normalize = yes
+  entry-break = 1
+  exit-break = 1
+