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

Andrew Martynov (andrmart) fedora-docs-commits at redhat.com
Thu Nov 10 21:21:16 UTC 2005


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:
-->




More information about the docs-commits mailing list