Add a note about using a kernel base+patch.

chapter01/changelog.xml

@@ -40,6 +40,17 @@
     appropriate for the entry or if needed the entire day's listitem.
     -->
 
+    <listitem>
+      <para>2025-09-03</para>
+      <itemizedlist>
+        <listitem>
+          <para>[bdubbs] - Add a description on how to use a kernel base+patch
+          in Chapter 3.  Fixes
+          <ulink url='&lfs-ticket-root;5785'>#5785</ulink>.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
     <listitem>
       <para>2025-09-01</para>
       <itemizedlist>

chapter03/packages.xml

@@ -3,6 +3,7 @@
   "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
   <!ENTITY % general-entities SYSTEM "../general.ent">
   %general-entities;
+  <!ENTITY kernel-directory "https://www.kernel.org/pub/linux/kernel/v6.x">
 ]>
 
 <sect1 id="ch-materials-packages">
@@ -466,15 +467,43 @@
 
         <note>
           <para>The Linux kernel is updated quite frequently, many times due to
-          discoveries of security vulnerabilities.  The latest available
-          <!--&linux-major-version;.&linux-minor-version;.x--> stable kernel
-          version <!--should--> may be
-          used, unless the errata page says otherwise.</para>
+          discoveries of security vulnerabilities.  The latest available stable
+          kernel version may be used, unless the errata page says
+          otherwise.</para>
 
           <para>For users with limited speed or expensive bandwidth who wish to
           update the Linux kernel, a baseline version of the package and
           patches can be downloaded separately.  This may save some time or
-          cost for a subsequent patch level upgrade within a minor release.
+          cost for a subsequent patch level upgrade within a minor
+          release.</para>
+
+          <para>
+            As an example, for linux-&linux-version;, the following could be downloaded:
+
+            <itemizedlist spacing="compact">
+              <listitem>
+                <para>
+                  <ulink url='&kernel-directory;/linux-&linux-majmin-version;.tar.xz'/>
+                </para>
+              </listitem>
+              <listitem>
+                <para>
+                  <ulink url='&kernel-directory;/patch-&linux-version;.xz'/>
+                </para>
+              </listitem>
+            </itemizedlist>
+
+            Then in <xref linkend='ch-tools-linux-headers'/> and 
+            <xref linkend='ch-bootable-kernel'/> unpack the kernel, change
+            to the package directory and then apply the patch with 
+            <userinput>xzcat ../patch-&linux-version;.xz | patch -Np1</userinput>.
+          </para>
+
+          <para>
+            At this point, if a newer point version of the kernel is needed, then
+            only the newer patch is needed. However, if a new minor version is 
+            desired, then both full minor version and any desired patch will both
+            need to be downloaded.
           </para>
         </note>
       </listitem>

packages.ent

@@ -398,7 +398,7 @@
 <!ENTITY libffi-fin-sbu "1.7 SBU">
 
 <!ENTITY libpipeline-version "1.5.8">
-<!ENTITY libpipeline-size "1046 KB">
+<!ENTITY libpipeline-size "1,046 KB">
 <!ENTITY libpipeline-url "&savannah;/releases/libpipeline/libpipeline-&libpipeline-version;.tar.gz">
 <!ENTITY libpipeline-md5 "17ac6969b2015386bcb5d278a08a40b5">
 <!ENTITY libpipeline-home "https://libpipeline.nongnu.org/">
@@ -423,6 +423,7 @@
 
 <!ENTITY linux-major-version "6">
 <!ENTITY linux-minor-version "16">
+<!ENTITY linux-majmin-version "&linux-major-version;.&linux-minor-version;">
 <!ENTITY linux-patch-version "1">
 <!--<!ENTITY linux-version "&linux-major-version;.&linux-minor-version;">-->
 <!ENTITY linux-version "&linux-major-version;.&linux-minor-version;.&linux-patch-version;">