Thu Sep 1 03:08:39 UTC 202220220901030839

a/aaa_glibc-solibs-2.36-x86_64-3.txz:  Rebuilt.
a/kernel-generic-5.19.6-x86_64-1.txz:  Upgraded.
a/kernel-huge-5.19.6-x86_64-1.txz:  Upgraded.
a/kernel-modules-5.19.6-x86_64-1.txz:  Upgraded.
d/git-2.37.3-x86_64-1.txz:  Upgraded.
d/kernel-headers-5.19.6-x86-1.txz:  Upgraded.
d/ninja-1.11.1-x86_64-1.txz:  Upgraded.
k/kernel-source-5.19.6-noarch-1.txz:  Upgraded.
kde/krename-5.0.2-x86_64-1.txz:  Upgraded.
l/glibc-2.36-x86_64-3.txz:  Rebuilt.
  Applied all post-release patches from the 2.36 branch.
  This fixes a security issue introduced in glibc-2.36: When the syslog
  function is passed a crafted input string larger than 1024 bytes, it
  reads uninitialized memory from the heap and prints it to the target log
  file, potentially revealing a portion of the contents of the heap.
  Thanks to marav.
  The patches also help with several packages failing to build from source.
  Thanks to nobodino.
l/glibc-i18n-2.36-x86_64-3.txz:  Rebuilt.
l/glibc-profile-2.36-x86_64-3.txz:  Rebuilt.
l/libssh-0.10.1-x86_64-1.txz:  Upgraded.
n/curl-7.85.0-x86_64-1.txz:  Upgraded.
  This update fixes a security issue:
  control code in cookie denial of service.
  For more information, see:
    https://curl.se/docs/CVE-2022-35252.html
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35252
  (* Security fix *)
x/fcitx5-gtk-5.0.18-x86_64-1.txz:  Upgraded.
x/fcitx5-qt-5.0.15-x86_64-1.txz:  Upgraded.
x/ico-1.0.6-x86_64-1.txz:  Upgraded.
x/libdrm-2.4.113-x86_64-1.txz:  Upgraded.
x/libfontenc-1.1.6-x86_64-1.txz:  Upgraded.
x/oclock-1.0.5-x86_64-1.txz:  Upgraded.
x/showfont-1.0.6-x86_64-1.txz:  Upgraded.
x/xmh-1.0.4-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 318cbaca2..c6a35de19 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Mon Aug 29 18:58:06 UTC 2022
+Thu Sep  1 02:56:11 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.19.5 Linux kernel using the packages
+upgrading to the generic 5.19.6 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.19.5-x86_64-1.txz
-  installpkg kernel-modules-5.19.5-x86_64-1.txz
+  installpkg kernel-generic-5.19.6-x86_64-1.txz
+  installpkg kernel-modules-5.19.6-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.19.5 -m ext4
+  mkinitrd -c -k 5.19.6 -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.19.5
+Here's another example: Build an initrd image using Linux 5.19.6
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 5.19.5 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 5.19.6 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?