release-notes RELEASE-NOTES-en.xml, 1.3, 1.4 hardware-reqs-en.xml, 1.1, 1.2 install-notes-en.xml, 1.2, 1.3 multimedia-en.xml, 1.2, 1.3 overview-en.xml, 1.1, 1.2 package-movement-en.xml, 1.2, 1.3 package-notes-en.xml, 1.2, 1.3 splash-en.xml, 1.2, 1.3

Tue Oct 25 09:07:27 UTC 2005

Author: kwade

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

Modified Files:
	RELEASE-NOTES-en.xml hardware-reqs-en.xml install-notes-en.xml 
	multimedia-en.xml overview-en.xml package-movement-en.xml 
	package-notes-en.xml splash-en.xml 
Log Message:
Cleanup before tagging for trans.


Index: RELEASE-NOTES-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4

--- RELEASE-NOTES-en.xml	25 Oct 2005 08:34:00 -0000	1.3
+++ RELEASE-NOTES-en.xml	25 Oct 2005 09:07:11 -0000	1.4
@@ -40,7 +40,7 @@
 
  <!-- *************** Local entities *************** -->
 
- <!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-07-26-T16:20-0700)"> <!-- version of manual and date -->
+ <!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-10-25-T04:20-0700)"> <!-- version of manual and date -->
  <!ENTITY LOCALVER "5 test1">  <!-- Set value to your choice, when guide version is out -->
  <!-- of sync with FC release, use instead of FEDVER or FEDTESTVER  -->
  <!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
@@ -48,9 +48,9 @@
  <!ENTITY DISTRO "&FC;"> <!-- The software's name -->
  <!ENTITY DISTROVER "&LOCALVER;"> <!-- The software's version -->
  <!ENTITY BUG-NUM "151189"> <!-- Tracker bug number --> 
- <!ENTITY BUG-URL "https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?assigned_to=relnotes%40fedoraproject.org&blocked=151189&bug_file_loc=http%3A%2F%2Ffedoraproject.org%2Fwiki%2FDocsProject%2FReleaseNotes%2FProcess&bug_severity=normal&bug_status=NEW&cc=kwade%40redhat.com&comment=Description%20of%20problem%2C%20bug%2C%20incorrect%20information%2C%20or%20enhancement%20request%3A%0D%0A%0D%0A%0D%0AVersion%20of%20release%20notes%20this%20bug%20refers%20to%3A%0D%0A%0D%0AFedora%20Core%204%20final%20release&component=fedora-docs&contenttypeentry=&contenttypemethod=list&contenttypeselection=text%2Fplain&data=&dependson=&descript!
 ion=&estimated_time=0.0&estimated_time_presets=0.0&ext_bz_bug_id=&ext_bz_id=0&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Linux&priority=normal&product=Fedora%20Core&rep_platform=All&short_desc=Describe%20problem%2C%20fix%2C%20or%20request%20for%20release%20notes&version=devel&GoAheadAndLogIn=Login">
+ <!ENTITY BUG-URL "https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Documentation&op_sys=Linux&target_milestone=---&bug_status=NEW&version=devel&component=release-notes&rep_platform=All&priority=normal&bug_severity=normal&assigned_to=relnotes%40fedoraproject.org&cc=&estimated_time_presets=0.0&estimated_time=0.0&bug_file_loc=http%3A%2F%2F&short_desc=summarize%20bug%20or%20enhancement%20here&comment=Description%20of%20problem%3A%0D%0A%0D%0A%0D%0AVersion-Release%20number%20of%20selected%20component%20%28if%20applicable%29%3A%0D%0A%0D%0A%0D%0AHow%20reproducible%3A%0D%0A%0D%0A%0D%0ASteps%20to%20Reproduce&p!
 ercnt;3A%0D%0A1.%0D%0A2.%0D%0A3.%0D%0A%20%20%0D%0AActual%20results%3A%0D%0A%0D%0A%0D%0AExpected%20results%3A%0D%0A%0D%0A%0D%0AAdditional%20info%3A&status_whiteboard=&keywords=&issuetrackers=&dependson=&blocked=151189%2C%20168083&ext_bz_id=0&ext_bz_bug_id=&data=&description=&contenttypemethod=list&contenttypeselection=text%2Fplain&contenttypeentry=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug">
 <!-- Pre-filled bz -->
-<!ENTITY TINY-BUG-URL "http://tinyurl.com/al5g4">
+<!ENTITY TINY-BUG-URL "http://tinyurl.com/byvk2">
 ]>
 
 <article id="index" lang="en" arch="x86;x86_64;ppc" os="test;final">


Index: hardware-reqs-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/hardware-reqs-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hardware-reqs-en.xml	25 Oct 2005 02:48:50 -0000	1.1
+++ hardware-reqs-en.xml	25 Oct 2005 09:07:12 -0000	1.2
@@ -230,14 +230,11 @@
       <listitem>
 	<para>
 	  <!--<remark os="test">(ppc)</remark> --> &FC; &LOCALVER;
-	  supports only the <quote>New World</quote> generation of
-	  <trademark class="registered">Apple</trademark> Power
-	  Macintosh, shipped circa 1999 onwards. It also supports the
-	  64-bit G5 processor and, POWER processors in <trademark
-	    class="registered">IBM</trademark>
-	  <trademark>eServer</trademark> <trademark>pSeries</trademark>.
-	  Currently 32-bit <trademark class="registered">IBM</trademark>
-	  <trademark>RS/6000</trademark> machines are not supported.
+	  supports only the <quote>New World</quote> generation of Apple
+	  Power Macintosh, shipped circa 1999 onwards. It also supports
+	  the 64-bit G5 processor and, POWER processors in IBM eServer
+	  pSeries. Currently 32-bit IBM RS/6000 machines are not
+	  supported.
 	</para>
       </listitem>
       <listitem>


Index: install-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/install-notes-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- install-notes-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ install-notes-en.xml	25 Oct 2005 09:07:12 -0000	1.3
@@ -59,88 +59,90 @@
 	    RAM.</para>
 	</listitem>
       </itemizedlist>
-    </section>
-    <para>
-      The DVD or first CD of the installation set of &FC; is set to be
-      bootable on supported hardware. In addition, bootable CD images
-      can be found in the <filename>images/</filename> directory of the
-      DVD or first CD. These will behave differently according to the
-      hardware:
-    </para>
-    <variablelist>
-      <title>Boot Image Behavior by Hardware</title>
+      <para>
+	The DVD or first CD of the installation set of &FC; is set to be
+	bootable on supported hardware. In addition, bootable CD images
+	can be found in the <filename>images/</filename> directory of
+	the DVD or first CD. These will behave differently according to
+	the hardware:
+      </para>
+      <variablelist>
+	<title>Boot Image Behavior by Hardware</title>
 	<varlistentry>
 	  <term>Apple Macintosh </term>
-	<listitem>
-	  <para>The bootloader should automatically boot the appropriate
-	    32-bit or 64-bit installer.  Power management support,
-	    including sleep and backlight level management, is present
-	    in the <filename>apmud</filename> package, which is in &FEX;.
-	    &FEX; for &FC; is configured by default for yum. Following
-	    installation, <filename>apmud</filename> can be installed by
-	    running the command <command>yum install apmud</command>
-	    in a terminal.
-	  </para>
-	</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>
+	  <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>Network booting</term>
-	<listitem>
-	  <para>There are combined images containing the installer
-	    kernel and ramdisk in the images/netboot/ directory of the
-	    install tree. These are intended for network booting with
-	    TFTP, but can be used in many ways.
-	  </para>
-	  <para>
-	    The command <command>yaboot</command> supports tftp
-	    booting for IBM eServer pSeries and Apple Macintosh.
-	    &FED; recommends using yaboot over the netboot images.
-	  </para>
+	    <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>Network booting</term>
+	  <listitem>
+	    <para>There are combined images containing the installer
+	      kernel and ramdisk in the images/netboot/ directory of the
+	      install tree. These are intended for network booting with
+	      TFTP, but can be used in many ways.
+	    </para>
+	    <para>
+	      The command <command>yaboot</command> supports tftp
+	      booting for IBM eServer pSeries and Apple Macintosh. &FED;
+	      recommends using yaboot over the netboot images.
+	    </para>
 	</listitem>
-      </varlistentry>
-    </variablelist>
+	</varlistentry>
+      </variablelist>
+    </section>
   </section>
   <section>
     <title>Anaconda Notes</title>
-
+    
     <itemizedlist>
       <listitem>
 	<para>


Index: multimedia-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/multimedia-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- multimedia-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ multimedia-en.xml	25 Oct 2005 09:07:12 -0000	1.3
@@ -59,7 +59,7 @@
 	  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-exluded"/>.
+	    linkend="sn-multimedia-excluded"/>.
 	</para>
       </listitem>
     </varlistentry>


Index: overview-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/overview-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- overview-en.xml	25 Oct 2005 02:48:50 -0000	1.1
+++ overview-en.xml	25 Oct 2005 09:07:12 -0000	1.2
@@ -1,5 +1,13 @@
 <section id="sn-overview">
   <title>Overview of This Release</title>
+  <caution>
+    <title>Information Out-of-Date</title>
+    <para>
+      The content in this section needs to be updated for &DISTRO;
+      &DISTROVER;
+    </para>
+  </caution>
+<!--
   <para>
     The following list includes brief summaries of some of the more
     significant aspects of &DISTRO; &DISTROVER;:
@@ -69,10 +77,6 @@
 	  </para>
 	</listitem>
 	<listitem>
-<!--	  <remark os="test">%%% <ulink
-	      url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136251">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136251</ulink> 
-	    %%%</remark>-->
-
 	  <para>
 	    &SEL; — This release includes coverage for 80 new
 	    daemons by the targeted policy.  There are changes to the
@@ -543,42 +547,6 @@
       </itemizedlist>
     </listitem>
   </itemizedlist>
- <!--
-  <note>
-    <remark os="test">%%% <ulink
-	url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136774">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136774</ulink> 
-      %%%</remark>
-    <title>Note</title>
-    <para>
-      VMware WS 4.5.2 is known to work on &DISTRO; &DISTROVER; after
-      the following workarounds are used:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>You must upgrade the kernel modules and configuration
-	  using the unofficial <filename>vmware-any-any-*</filename>
-	  toolkit available from:</para>
-
-	<remark os="test">%%% <ulink
-	    url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137378">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137378</ulink> 
-	  %%%</remark>
-
-	<para><ulink
-	    url="http://platan.vc.cvut.cz/ftp/pub/vmware/">http://platan.vc.cvut.cz/ftp/pub/vmware/</ulink></para>
-
-      </listitem>
-
-      <listitem>
-	<para>After <filename>vmware-config.pl</filename> is run and the
-	  VMware modules are loaded, the following command creates the
-	  <filename>/sys/class/*</filename> nodes needed for
-	  udev:</para>
-
-	<para><command>cp -rp /dev/vm*
-	    /etc/udev/devices/</command></para>
-      </listitem>
-    </itemizedlist>
-  </note>
 -->
 </section>
 <!--


Index: package-movement-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-movement-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- package-movement-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ package-movement-en.xml	25 Oct 2005 09:07:12 -0000	1.3
@@ -1044,18 +1044,14 @@
   <section>
     <title>Notes</title>
     <para>
-      system-config-mouse configuration utility has been dropped in this
-      release because synaptic and 3 button mouse configuration is being
-      done automatically and serial mice are not supported (<emphasis
-	role='strong'>copied to <ulink
-	  url='/Docs/Beats/Desktop'>Docs/Beats/Desktop</ulink>
-      </emphasis> - OK?) 
+      <application>system-config-mouse</application> configuration
+      utility has been dropped in this release because synaptic and 3
+      button mouse configuration is being done automatically and serial
+      mice are not supported.
     </para>
     <para>
       Screensavers not installed by default anymore?  Explain
-      why and provide commands to install them (<emphasis
-	role='strong'>copied to <ulink
-	  url='/Docs/Beats/Desktop'>Docs/Beats/Desktop</ulink>
+      why and provide commands to install them.
       </emphasis>)
     </para>
 <!-- FIXME


Index: package-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- package-notes-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ package-notes-en.xml	25 Oct 2005 09:07:12 -0000	1.3
@@ -36,8 +36,14 @@
     have undergone significant changes for &DISTRO; &DISTROVER;.  For
     easier access, they are generally organized using the same groups
     used in Anaconda.
-  </para>
-
+  </para
+  <caution>
+    <title>Information Out-of-Date</title>
+    <para>
+      The content in this section needs to be updated for &DISTRO;
+      &DISTROVER;
+    </para>
+  </caution>
   <section id="sn-basic-components">
     <title>Basic Components</title>
     <para>


Index: splash-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- splash-en.xml	25 Oct 2005 08:34:00 -0000	1.2
+++ splash-en.xml	25 Oct 2005 09:07:12 -0000	1.3
@@ -39,11 +39,13 @@
     Refer to these webpages to find out more information about &FED;:
   </para>
   <itemizedlist>
+<!-- FIXME Return when the section is updated
     <listitem>
       <para>
 	<xref linkend="sn-new-in-fc"/>
       </para>
     </listitem>
+-->
     <listitem>
       <para>
 	<xref linkend="sn-intro"/> — Technical release notes


