Sat Sep 15 21:19:23 UTC 201820180915211923

a/kernel-firmware-20180913_44d4fca-noarch-1.txz:  Upgraded.
a/kernel-generic-4.14.70-x86_64-1.txz:  Upgraded.
a/kernel-huge-4.14.70-x86_64-1.txz:  Upgraded.
a/kernel-modules-4.14.70-x86_64-1.txz:  Upgraded.
ap/hplip-3.18.7-x86_64-4.txz:  Rebuilt.
  Applied fixed patch - this has a better chance of working now. I've checked
  and hpcups no longer links to libImageProcessor. Which, by the way, the
  previous build dumped onto my main system (not even in "make install"),
  but not into the package itself. I no longer own an HP printer and will
  never buy another one, so if there are any remaining problems please report.
  Thanks to Matteo Bernardini.
d/kernel-headers-4.14.70-x86-1.txz:  Upgraded.
k/kernel-source-4.14.70-noarch-1.txz:  Upgraded.
  Config changes since 4.14.69:
   CLEANCACHE n -> y
   CMA n -> y
   MEMORY_FAILURE n -> y
   NUMA n -> y
   X86_CHECK_BIOS_CORRUPTION n -> y
   Z3FOLD m -> y
   ZBUD m -> y
   ZSMALLOC m -> y
  +ACPI_APEI_MEMORY_FAILURE y
  +ACPI_NUMA y
  +AMD_NUMA y
  +CMA_AREAS 7
  +CMA_DEBUG n
  +CMA_DEBUGFS n
  +DMA_CMA n
  +HWPOISON_INJECT m
  +NEED_MULTIPLE_NODES y
  +NODES_SHIFT 6
  +NODES_SPAN_OTHER_NODES y
  +NUMA_BALANCING n
  +NUMA_EMU n
  +RAS_CEC n
  +USE_PERCPU_NUMA_NODE_ID y
  +X86_64_ACPI_NUMA y
  +X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK n
n/NetworkManager-1.14.0-x86_64-1.txz:  Upgraded.
  Added new options:  --enable-json-validation --enable-ovs
xap/network-manager-applet-1.8.18-x86_64-1.txz:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
pasture/php-5.6.38-x86_64-1.txz:  Upgraded.
  One security bug has been fixed in this release:
  Apache2: XSS due to the header Transfer-Encoding: chunked
  For more information, see:
    https://php.net/ChangeLog-5.php#5.6.38
  (* Security fix *)
usb-and-pxe-installers/usbboot.img:  Rebuilt.

1 files changed, 7 insertions, 7 deletions

diff --git a/README.initrd b/README.initrd
index a71db4a31..d8386d2e8 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Mon Sep 10 20:25:15 UTC 2018
+Sat Sep 15 20:46:22 UTC 2018
 
 This document describes how to create and install an initrd, which may be 
 required to use the 4.x kernel. Also see "man mkinitrd".
@@ -33,15 +33,15 @@ flexible to ship a generic kernel and a set of kernel modules for it.
 
 The easiest way to make the initrd is to use the mkinitrd script included 
 in Slackware's mkinitrd package. We'll walk through the process of 
-upgrading to the generic 4.14.69 Linux kernel using the packages
+upgrading to the generic 4.14.70 Linux kernel using the packages
 found in Slackware's slackware/a/ directory.
 
 First, make sure the kernel, kernel modules, and mkinitrd package are 
 installed (the current version numbers might be a little different, so 
 this is just an example):
 
-  installpkg kernel-generic-4.14.69-x86_64-1.txz
-  installpkg kernel-modules-4.14.69-x86_64-1.txz
+  installpkg kernel-generic-4.14.70-x86_64-1.txz
+  installpkg kernel-modules-4.14.70-x86_64-1.txz
   installpkg mkinitrd-1.4.11-x86_64-8.txz
 
 Change into the /boot directory:
@@ -52,7 +52,7 @@ Now you'll want to run "mkinitrd". I'm using ext4 for my root filesystem,
 and since the disk controller requires no special support the ext4 module
 will be the only one I need to load:
 
-  mkinitrd -c -k 4.14.69 -m ext4
+  mkinitrd -c -k 4.14.70 -m ext4
 
 This should do two things. First, it will create a directory
 /boot/initrd-tree containing the initrd's filesystem. Then it will
@@ -61,10 +61,10 @@ you could make some additional changes in /boot/initrd-tree/ and
 then run mkinitrd again without options to rebuild the image. That's
 optional, though, and only advanced users will need to think about that.
 
-Here's another example: Build an initrd image using Linux 4.14.69
+Here's another example: Build an initrd image using Linux 4.14.70
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 4.14.69 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 4.14.70 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?