Thu Oct 28 01:11:07 UTC 202120211028011107

a/kernel-generic-5.14.15-x86_64-1.txz:  Upgraded.
a/kernel-huge-5.14.15-x86_64-1.txz:  Upgraded.
a/kernel-modules-5.14.15-x86_64-1.txz:  Upgraded.
d/cmake-3.21.4-x86_64-1.txz:  Upgraded.
d/kernel-headers-5.14.15-x86-1.txz:  Upgraded.
k/kernel-source-5.14.15-noarch-1.txz:  Upgraded.
  We're going to go ahead and take both of those changes that were considered
  in /testing. GazL almost had me talked out of the autogroup change, but it's
  easy to disable if traditional "nice" behavior is important to someone.
  -DRM_I810 n
  -INLINE_READ_UNLOCK y
  -INLINE_READ_UNLOCK_IRQ y
  -INLINE_SPIN_UNLOCK_IRQ y
  -INLINE_WRITE_UNLOCK y
  -INLINE_WRITE_UNLOCK_IRQ y
   PREEMPT n -> y
   PREEMPT_VOLUNTARY y -> n
   SCHED_AUTOGROUP n -> y
  +CEC_GPIO n
  +DEBUG_PREEMPT y
  +PREEMPTION y
  +PREEMPT_COUNT y
  +PREEMPT_DYNAMIC y
  +PREEMPT_RCU y
  +PREEMPT_TRACER n
  +RCU_BOOST n
  +TASKS_RCU y
  +UNINLINE_SPIN_UNLOCK y
kde/plasma-desktop-5.23.2.1-x86_64-1.txz:  Upgraded.
l/imagemagick-7.1.0_12-x86_64-1.txz:  Upgraded.
l/librsvg-2.52.3-x86_64-1.txz:  Upgraded.
n/bind-9.16.22-x86_64-1.txz:  Upgraded.
  This update fixes bugs and the following security issue:
  The "lame-ttl" option is now forcibly set to 0. This effectively disables
  the lame server cache, as it could previously be abused by an attacker to
  significantly degrade resolver performance.
  For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-25219
  (* Security fix *)
n/c-ares-1.18.1-x86_64-1.txz:  Upgraded.
n/samba-4.15.1-x86_64-1.txz:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.

1 files changed, 7 insertions, 7 deletions

diff --git a/README.initrd b/README.initrd
index e6dc3a9b..0f961db6 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Wed Oct 20 19:11:11 UTC 2021
+Wed Oct 27 18:28:34 UTC 2021
 
 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 5.14.14 Linux kernel using the packages
+upgrading to the generic 5.14.15 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-5.14.14-x86_64-1.txz
-  installpkg kernel-modules-5.14.14-x86_64-1.txz
+  installpkg kernel-generic-5.14.15-x86_64-1.txz
+  installpkg kernel-modules-5.14.15-x86_64-1.txz
   installpkg mkinitrd-1.4.11-x86_64-26.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 5.14.14 -m ext4
+  mkinitrd -c -k 5.14.15 -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 5.14.14
+Here's another example: Build an initrd image using Linux 5.14.15
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 5.14.14 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 5.14.15 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?