release-notes/en Desktop.xml, 1.4, 1.5 I18n.xml, 1.3, 1.4 Kernel.xml, 1.4, 1.5 Networking.xml, 1.3, 1.4

[Karsten Wade (kwade)]

Author: kwade

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

Modified Files:
	Desktop.xml I18n.xml Kernel.xml Networking.xml 
Log Message:
This should be clean of all <screen> block ugliness.


Index: Desktop.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Desktop.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Desktop.xml	28 Feb 2006 20:04:04 -0000	1.4
+++ Desktop.xml	28 Feb 2006 20:18:27 -0000	1.5
@@ -35,7 +35,7 @@
         <para> Starting with GNOME 2.12, the terminal option has been removed from the desktop context menu. The <code>nautilus-open-terminal</code> package in Fedora Extras provides a enhanced replacement for those who require it. You can install it with the following command. </para>
         <itemizedlist>
           <listitem>
-            <screen>yum install nautilus-open-terminal</screen>
+            <screen>su -c 'yum install nautilus-open-terminal'</screen>
           </listitem>
         </itemizedlist>
       </listitem>
@@ -43,7 +43,7 @@
         <para> In Fedora Core 5, only a small assortment of screensavers is installed by default.  Some users find certain screensavers unpleasant, and other screensavers may abruptly terminate the graphical interface.  This tends to happen more often with OpenGL animated screensavers provided within the <code>xscreensaver-gl-extras</code> package, when used with poorly-supported video hardware.  To install these extra screensavers, run the following command: </para>
         <itemizedlist>
           <listitem>
-            <screen>yum install xscreensaver-extras xscreensaver-gl-extras</screen>
+            <screen>su -c 'yum install xscreensaver-extras xscreensaver-gl-extras'</screen>
           </listitem>
         </itemizedlist>
       </listitem>


Index: I18n.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/I18n.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- I18n.xml	28 Feb 2006 19:04:19 -0000	1.3
+++ I18n.xml	28 Feb 2006 20:18:27 -0000	1.4
@@ -37,7 +37,10 @@
         <para>If your desktop is not running in an Asian locale, to activate it in your user account, run these commands, then logout and login again to your desktop. </para>
         <itemizedlist>
           <listitem>
-            <screen>mkdir ~/.xinput.d ln -s /etc/X11/xinit/xinput.d/scim ~/.xinput.d/default</screen>
+            <screen>
+mkdir ~/.xinput.d 
+ln -s /etc/X11/xinit/xinput.d/scim ~/.xinput.d/default
+	    </screen>
           </listitem>
         </itemizedlist>
       </section>
@@ -60,7 +63,18 @@
       <title>Fonts</title>
       <para>Support is now available for synthetic emboldening of fonts that do not have a bold face. </para>
       <para>New fonts for Chinese have been added: AR PL ShanHeiSun Uni (<code>uming.ttf</code>) and AR PL ZenKai Uni (<code>ukai.ttf</code>).  The default font is AR PL ShanHeiSun Uni, which contains embedded bitmaps. If you prefer outline glyphs you can put the following section in your <code>~/.font.conf</code> file: </para>
-      <screen><fontconfig><match target="font"><test name="family" compare="eq"><string>AR PL ShanHeiSun Uni</string></test><edit name="embeddedbitmap" mode="assign"><bool>false</bool></edit></match></fontconfig></screen>
+      <screen>
+<fontconfig>
+  <match target="font">
+    <test name="family" compare="eq">
+      <string>AR PL ShanHeiSun Uni</string>
+    </test>
+    <edit name="embeddedbitmap" mode="assign">
+      <bool>false</bool>
+    </edit>
+  </match>
+</fontconfig>	
+      </screen>
       <para>
       </para>
     </section>


Index: Kernel.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Kernel.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Kernel.xml	28 Feb 2006 20:04:04 -0000	1.4
+++ Kernel.xml	28 Feb 2006 20:18:27 -0000	1.5
@@ -98,7 +98,10 @@
           <para>Prepare a RPM package building environment in your home directory.  Run the following commands: </para>
           <itemizedlist>
             <listitem>
-              <screen>su -c 'yum install fedora-rpmdevtools'fedora-buildrpmtree</screen>
+              <screen>
+su -c 'yum install fedora-rpmdevtools'
+fedora-buildrpmtree
+	      </screen>
               <para>Enter the <code>root</code> password when prompted. </para>
             </listitem>
           </itemizedlist>
@@ -116,7 +119,10 @@
               <para> by running the following command:  </para>
               <itemizedlist>
                 <listitem>
-                  <screen>su -c 'yum install yum-utils'su -c 'yumdownloader --source kernel'</screen>
+                  <screen>
+su -c 'yum install yum-utils'
+su -c 'yumdownloader --source kernel'
+		  </screen>
                 </listitem>
               </itemizedlist>
               <para>Enter the <code>root</code> password when prompted. </para>
@@ -138,7 +144,10 @@
           <para>Prepare the kernel sources using the commands: </para>
 	      <itemizedlist>
 		<listitem>
-              <screen>cd ~/rpmbuild/SPECSrpmbuild -bp --target $(uname -m) kernel-2.6.spec</screen>
+              <screen>
+cd ~/rpmbuild/SPECS
+rpmbuild -bp --target $(uname -m) kernel-2.6.spec
+		  </screen>
               <para>The kernel source tree is located in the <code>${HOME}/rpmbuild/BUILD/kernel-<version>/</code> directory. </para>
             </listitem>
           </itemizedlist>
@@ -180,7 +189,15 @@
       <para>An exploded source tree is not required to build a kernel module, such as your own device driver, against the currently in-use kernel. For example, to build the <code>foo.ko</code> module, create the following <code>Makefile</code> in the directory containing the <code>foo.c</code> file: </para>
       <itemizedlist>
         <listitem>
-          <screen>obj-m := foo.oKDIR  := /lib/modules/$(shell uname -r)/buildPWD   := $(shell pwd)default:$(MAKE) -C $(KDIR) M=$(PWD) modules</screen>
+          <screen>
+obj-m := foo.o
+
+KDIR  := /lib/modules/$(shell uname -r)/build
+PWD   := $(shell pwd)
+
+default:
+    $(MAKE) -C $(KDIR) M=$(PWD) modules
+	  </screen>
         </listitem>
       </itemizedlist>
       <para>Issue the <code>make</code> command to build the <code>foo.ko</code> module. </para>


Index: Networking.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Networking.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Networking.xml	28 Feb 2006 19:44:07 -0000	1.3
+++ Networking.xml	28 Feb 2006 20:18:27 -0000	1.4
@@ -83,8 +83,18 @@
       <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 <code>iproute2</code> tool now issues a warning if no prefix length is provided, to warn about possible unintended deletions: </para>
       <itemizedlist>
         <listitem>
-          <screen>ip addr list dev eth0 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000inet 10.0.0.3/24 scope global eth0</screen>
-          <screen>su -c 'ip addr del 10.0.0.3 dev eth0' Warning: Executing wildcard deletion to stay compatible with oldscripts. Explicitly specify the prefix length (10.0.0.3/32) toavoid this warning. This special behaviour is likely to disappearin further releases, fix your scripts!</screen>
+          <screen>
+ip addr list dev eth0 
+4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
+    inet 10.0.0.3/24 scope global eth0
+	  </screen>
+          <screen>
+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>
         </listitem>
       </itemizedlist>
       <para>The correct method of deleting the address and thus avoiding the warning is: </para>