Wed Dec 15 04:34:02 UTC 202120211215043402

a/dialog-1.3_20211214-x86_64-1.txz:  Upgraded.
a/kernel-generic-5.15.8-x86_64-1.txz:  Upgraded.
a/kernel-huge-5.15.8-x86_64-1.txz:  Upgraded.
a/kernel-modules-5.15.8-x86_64-1.txz:  Upgraded.
a/sysvinit-3.01-x86_64-1.txz:  Upgraded.
d/kernel-headers-5.15.8-x86-1.txz:  Upgraded.
d/patchelf-0.14.3-x86_64-1.txz:  Upgraded.
k/kernel-source-5.15.8-noarch-1.txz:  Upgraded.
l/oniguruma-6.9.7.1-x86_64-1.txz:  Upgraded.
l/pipewire-0.3.41-x86_64-1.txz:  Upgraded.
x/libinput-1.19.3-x86_64-1.txz:  Upgraded.
x/xorg-server-1.20.13-x86_64-2.txz:  Rebuilt.
  Fixes for multiple input validation failures in X server extensions:
  render: Fix out of bounds access in SProcRenderCompositeGlyphs()
  xfixes: Fix out of bounds access in *ProcXFixesCreatePointerBarrier()
  Xext: Fix out of bounds access in SProcScreenSaverSuspend()
  record: Fix out of bounds access in SwapCreateRegister()
  For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4008
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4009
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4010
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4011
  (* Security fix *)
x/xorg-server-xephyr-1.20.13-x86_64-2.txz:  Rebuilt.
x/xorg-server-xnest-1.20.13-x86_64-2.txz:  Rebuilt.
x/xorg-server-xvfb-1.20.13-x86_64-2.txz:  Rebuilt.
x/xorg-server-xwayland-21.1.4-x86_64-1.txz:  Upgraded.
  Fixes for multiple input validation failures in X server extensions:
  render: Fix out of bounds access in SProcRenderCompositeGlyphs()
  xfixes: Fix out of bounds access in *ProcXFixesCreatePointerBarrier()
  Xext: Fix out of bounds access in SProcScreenSaverSuspend()
  record: Fix out of bounds access in SwapCreateRegister()
  For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4008
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4009
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4010
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4011
  (* Security fix *)
xap/xsnow-3.4.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 a62c82132..3d76297d8 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Wed Dec  8 20:31:03 UTC 2021
+Wed Dec 15 04:21:13 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.15.7 Linux kernel using the packages
+upgrading to the generic 5.15.8 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.15.7-x86_64-1.txz
-  installpkg kernel-modules-5.15.7-x86_64-1.txz
+  installpkg kernel-generic-5.15.8-x86_64-1.txz
+  installpkg kernel-modules-5.15.8-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.15.7 -m ext4
+  mkinitrd -c -k 5.15.8 -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.15.7
+Here's another example: Build an initrd image using Linux 5.15.8
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 5.15.7 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 5.15.8 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?