Wed Aug 17 20:41:53 UTC 202220220817204153

a/aaa_glibc-solibs-2.36-x86_64-2.txz:  Rebuilt.
a/kernel-generic-5.19.2-x86_64-1.txz:  Upgraded.
a/kernel-huge-5.19.2-x86_64-1.txz:  Upgraded.
a/kernel-modules-5.19.2-x86_64-1.txz:  Upgraded.
ap/vim-9.0.0223-x86_64-1.txz:  Upgraded.
  Fix use after free, out-of-bounds read, and heap based buffer overflow.
  Thanks to marav for the heads-up.
  For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2816
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2817
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2819
  (* Security fix *)
d/kernel-headers-5.19.2-x86-1.txz:  Upgraded.
k/kernel-source-5.19.2-noarch-1.txz:  Upgraded.
l/glibc-2.36-x86_64-2.txz:  Rebuilt.
  Rebuilt with a patch from Arch to reenable DT_HASH in shared objects since
  the change broke Steam games that use EPIC's EAC. I'm not exactly 100% on
  board with this approach, but since DT_GNU_HASH remains and is still used,
  I guess I'll go along with it for now. Hopefully EAC will be patched and we
  can back this out.
  Thanks to Swaggajackin for the notice and for providing links to the glibc
  bug discussion as well as the patch.
  If anything else needs a rebuild after this, let me know in the LQ thread.
l/glibc-i18n-2.36-x86_64-2.txz:  Rebuilt.
l/glibc-profile-2.36-x86_64-2.txz:  Rebuilt.
xap/vim-gvim-9.0.0223-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 0b2ca7e3c..e285d679f 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Fri Aug 12 01:20:17 UTC 2022
+Wed Aug 17 20:21:25 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.18.17 Linux kernel using the packages
+upgrading to the generic 5.19.2 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.18.17-x86_64-1.txz
-  installpkg kernel-modules-5.18.17-x86_64-1.txz
+  installpkg kernel-generic-5.19.2-x86_64-1.txz
+  installpkg kernel-modules-5.19.2-x86_64-1.txz
   installpkg mkinitrd-1.4.11-x86_64-30.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.18.17 -m ext4
+  mkinitrd -c -k 5.19.2 -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.18.17
+Here's another example: Build an initrd image using Linux 5.19.2
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 5.18.17 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 5.19.2 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?