Sun Jan 16 21:33:27 UTC 202220220116213327

a/aaa_libraries-15.0-x86_64-14.txz:  Rebuilt.
  Upgraded: libexpat.so.1.8.3.
a/kernel-generic-5.15.15-x86_64-1.txz:  Upgraded.
a/kernel-huge-5.15.15-x86_64-1.txz:  Upgraded.
a/kernel-modules-5.15.15-x86_64-1.txz:  Upgraded.
ap/cups-filters-1.28.11-x86_64-1.txz:  Upgraded.
ap/ksh93-1.0_20220114_e569f23e-x86_64-1.txz:  Upgraded.
ap/vim-8.2.4115-x86_64-1.txz:  Upgraded.
d/gdb-11.2-x86_64-1.txz:  Upgraded.
d/kernel-headers-5.15.15-x86-1.txz:  Upgraded.
k/kernel-source-5.15.15-noarch-1.txz:  Upgraded.
kde/kwayland-server-5.23.5-x86_64-2.txz:  Rebuilt.
  Applied upstream patch:
  [PATCH] Store surface object in tablet cursor using QPointer.
  Thanks to ZhaoLin1457.
l/expat-2.4.3-x86_64-1.txz:  Upgraded.
  Fix issues with left shifts by >=29 places resulting in:
    a) realloc acting as free
    b) realloc allocating too few bytes
    c) undefined behavior
  Fix integer overflow on variable m_groupSize in function doProlog leading
  to realloc acting as free. Impact is denial of service or other undefined
  behavior.
  Prevent integer overflows near memory allocation at multiple places.
  For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45960
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46143
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22822
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22823
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22824
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22825
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22826
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22827
  (* Security fix *)
l/libunwind-1.6.2-x86_64-1.txz:  Upgraded.
x/xterm-370-x86_64-3.txz:  Rebuilt.
  Ship a sample XTerm.linux.console app-defaults file. Thanks to GazL.
xap/vim-gvim-8.2.4115-x86_64-1.txz:  Upgraded.
xap/xsnow-3.4.3-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 408533da3..6f81ae9cb 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Wed Jan 12 21:38:19 UTC 2022
+Sun Jan 16 21:23:01 UTC 2022
 
 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.14 Linux kernel using the packages
+upgrading to the generic 5.15.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.15.14-x86_64-1.txz
-  installpkg kernel-modules-5.15.14-x86_64-1.txz
+  installpkg kernel-generic-5.15.15-x86_64-1.txz
+  installpkg kernel-modules-5.15.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.15.14 -m ext4
+  mkinitrd -c -k 5.15.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.15.14
+Here's another example: Build an initrd image using Linux 5.15.15
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 5.15.14 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 5.15.15 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?