release-notes/FC4 kernel.xml,1.2,1.3 package-notes.xml,1.10,1.11

Karsten Wade (kwade) fedora-docs-commits at redhat.com
Mon May 30 18:16:24 UTC 2005 

Author: kwade

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

Modified Files:
	kernel.xml package-notes.xml 
Log Message:
A tip from bz#158394, misc. other fixes.


Index: kernel.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/kernel.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- kernel.xml	28 May 2005 16:10:31 -0000	1.2
+++ kernel.xml	30 May 2005 18:16:22 -0000	1.3
@@ -1,3 +1,157 @@
+<section id="sn-kernel">
+  <title><filename>kernel</filename></title>
+  <!-- still don't entirely grok the use of these sections, leaving them -->
+<!-- for now commented out but available.
+            <remark os="test">%%% <ulink
+                url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135269">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135269</ulink>
+                %%%</remark>
+-->
+  <tip>
+    <title>Using <command>yum</command> to Uninstall Kernel
+    Packages</title>
+    <para>
+      &FC; &LOCALVER; contains support for clustering systems using CMAN
+      and GFS. These kernels require assistance from some user-space
+      packages.  These packages are not removed when using <command>rpm
+      -e</command> to uninstall older versions of the kernel packages.
+    </para>
+    <para>
+      When using <command>rpm -e
+	kernel-<replaceable><version></replaceable></command> to
+      uninstall the kernel, you must also remove the assisting
+      user-space packages.  You may wish to consider a dependecy
+      resolving tool such as <command>yum remove
+	kernel-<replaceable><version></replaceable></command>.
+      This automatically removes any dependant packages.
+    </para>
+  </tip>
+  <para>
+    In order to eliminate the redundancy inherent in providing a
+    separate package for the kernel source code when that source code
+    already exists in the kernel's <filename>.src.rpm</filename> file,
+    &DISTRO; &DISTROVER; no longer includes the
+    <filename>kernel-source</filename> package.  Users that require
+    access to the kernel sources can find them in the
+    <filename>kernel</filename> <filename>.src.rpm</filename> file. To
+    create an exploded source tree from this file, perform the following
+    steps (note that
+    <filename><replaceable><version></replaceable></filename>
+    refers to the version specification for your currently-running
+    kernel):
+  </para>
+  <procedure>
+    <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
+	    "SRPMS" CD iso image
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    The FTP site where you got the kernel package
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    By running the following command:
+	  </para>
+	  <para>
+	    <command>up2date --get-source kernel</command>
+	  </para>
+	</listitem>
+      </itemizedlist>
+    </step>
+    <step>
+      <para>
+	Install
+	<filename>kernel-<replaceable><version></replaceable>.src.rpm</filename> 
+	(given the default RPM configuration, the files this package
+	contains will be written to
+	<filename>/usr/src/redhat/</filename>)
+      </para>
+    </step>
+    <step>
+      <para>
+	Change directory to <filename>/usr/src/redhat/SPECS/</filename>,
+	and issue the following command:
+      </para>
+      <para>
+	<command>rpmbuild -bp
+	  --target=<replaceable><arch></replaceable>
+	  kernel.spec</command>
+      </para>
+      <para>
+	(Where
+	<command><replaceable><arch></replaceable></command> is
+	the desired target architecture.)
+      </para>
+      <para>
+	On a default RPM configuration, the kernel tree will be located
+	in <filename>/usr/src/redhat/BUILD/</filename>.
+      </para>
+    </step>
+    <step>
+      <para>
+	In the resulting tree, 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>
+      <para>
+	<command>cp <replaceable><desired-file></replaceable>
+	  ./.config</command>
+      </para>
+    </step>
+    <step>
+      <para>
+	Issue the following command:
+      </para>
+      <para>
+	<command>make oldconfig</command>
+      </para>
+    </step>
+  </procedure>
+  <para>
+    You can then proceed as usual.
+  </para>
+  <tip>
+    <title>Source not required to build kernel modules</title>
+    <para>
+      An exploded source tree is <emphasis>not</emphasis> required to
+      build kernel modules against the currently in-use kernel.
+    </para>
+    <para>
+      For example, to build the <filename>foo.ko</filename> module,
+      create the following file (named <filename>Makefile</filename>) in
+      the directory containing the <filename>foo.c</filename> file:
+    </para>
+<screen>
+<computeroutput>
+obj-m    := foo.o
+
+KDIR    := /lib/modules/$(shell uname -r)/build
+PWD    := $(shell pwd)
+
+default:
+    $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
+</computeroutput>
+</screen>
+    <para>
+      Issue the <command>make</command> command to build the
+      <filename>foo.ko</filename> module.
+    </para>
+  </tip>
+</section>
 <!--
 Local variables:
 mode: xml


Index: package-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/package-notes.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- package-notes.xml	30 May 2005 17:40:09 -0000	1.10
+++ package-notes.xml	30 May 2005 18:16:22 -0000	1.11
@@ -240,7 +240,7 @@
 
     </section>
 -->
-  <section>
+  <section id="sn-packages-core">
     <title>Core</title>
     <para>
       This section contains the most elemental components of &DISTRO;,
@@ -255,7 +255,9 @@
       <para>
 	The Fedora Extras repository is now enabled by default.
       </para>
-</section>
+    </section>
+    &KERNEL;
+  </section>
 <!--
       <section>
         <title><filename>e2fsprogs</filename></title>
@@ -370,143 +372,6 @@
           moved into the new directory.</para>
       </section>
   -->
-      <section>
-        <title><filename>kernel</filename></title>
-<!-- still don't entirely grok the use of these sections, leaving them -->
-<!-- for now commented out but available.
-            <remark os="test">%%% <ulink
-                url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135269">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135269</ulink>
-                %%%</remark>
--->
-    <para>
-      In order to eliminate the redundancy inherent in providing a
-      separate package for the kernel source code when that source code
-      already exists in the kernel's <filename>.src.rpm</filename> file,
-      &DISTRO; &DISTROVER; no longer includes the
-      <filename>kernel-source</filename> package.  Users that require
-      access to the kernel sources can find them in the
-      <filename>kernel</filename> <filename>.src.rpm</filename> file. To
-      create an exploded source tree from this file, perform the
-      following steps (note that
-      <filename><replaceable><version></replaceable></filename>
-      refers to the version specification for your currently-running
-      kernel):
-    </para>
-    <orderedlist>
-      <listitem>
-	<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 "SRPMS" CD iso image
-	    </para>
-	  </listitem>
-	  <listitem>
-	    <para>
-	      The FTP site where you got the kernel package
-	    </para>
-	  </listitem>
-	  <listitem>
-	    <para>
-	      By running the following command:
-	    </para>
-	    <para>
-	      <command>up2date --get-source kernel</command>
-	    </para>
-	  </listitem>
-	</itemizedlist>
-      </listitem>
-      <listitem>
-	<para>
-	  Install
-	  <filename>kernel-<replaceable><version></replaceable>.src.rpm</filename> 
-	  (given the default RPM configuration, the files this package
-	  contains will be written to
-	  <filename>/usr/src/redhat/</filename>)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Change directory to
-	  <filename>/usr/src/redhat/SPECS/</filename>, and issue the
-	  following command:
-	</para>
-	<para>
-	  <command>rpmbuild -bp
-	    --target=<replaceable><arch></replaceable>
-	    kernel.spec</command>
-	</para>
-	<para>
-	  (Where
-	  <command><replaceable><arch></replaceable></command> is
-	  the desired target architecture.)
-	</para>
-	<para>
-	  On a default RPM configuration, the kernel tree will be
-	  located in <filename>/usr/src/redhat/BUILD/</filename>.
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  In the resulting tree, 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>
-	<para>
-	  <command>cp <replaceable><desired-file></replaceable>
-	    ./.config</command>
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Issue the following command:
-	</para>
-	<para>
-	  <command>make oldconfig</command>
-	</para>
-      </listitem>
-    </orderedlist>
-    <para>
-      You can then proceed as usual.
-    </para>
-    <tip>
-      <title>Source not required to build kernel modules</title>
-      <para>
-	An exploded source tree is <emphasis>not</emphasis> required to
-	build kernel modules against the currently in-use kernel.
-      </para>
-      <para>
-	For example, to build the <filename>foo.ko</filename> module,
-	create the following file (named <filename>Makefile</filename>)
-	in the directory containing the <filename>foo.c</filename> file:
-      </para>
-<screen>
-<computeroutput>
-obj-m    := foo.o
-
-KDIR    := /lib/modules/$(shell uname -r)/build
-PWD    := $(shell pwd)
-
-default:
-    $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
-</computeroutput>
-</screen>
-      <para>
-	Issue the <command>make</command> command to build the
-	<filename>foo.ko</filename> module.
-      </para>
-    </tip>
-  </section>
-</section>
 <!--
     <section os="bogus">
       <title>DNS Name Server</title>
@@ -648,7 +513,7 @@
       <para>*** Enter group description here ***</para>
 
     </section>
--->
+  -->
   <section>
     <title>Language Support</title>
     <para>

More information about the Fedora-docs-commits mailing list