Tue May 14 19:07:51 UTC 202420240514190751

a/kernel-firmware-20240510_b9d2bf2-noarch-1.txz:  Upgraded.
a/kernel-generic-6.9.0-x86_64-1.txz:  Upgraded.
a/kernel-huge-6.9.0-x86_64-1.txz:  Upgraded.
a/kernel-modules-6.9.0-x86_64-1.txz:  Upgraded.
d/gcc-14.1.0-x86_64-1.txz:  Upgraded.
d/gcc-g++-14.1.0-x86_64-1.txz:  Upgraded.
d/gcc-gdc-14.1.0-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
d/gcc-gfortran-14.1.0-x86_64-1.txz:  Upgraded.
d/gcc-gm2-14.1.0-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
d/gcc-gnat-14.1.0-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
d/gcc-go-14.1.0-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
d/gcc-objc-14.1.0-x86_64-1.txz:  Upgraded.
d/kernel-headers-6.9.0-x86-1.txz:  Upgraded.
d/libgccjit-14.1.0-x86_64-1.txz:  Upgraded.
d/libtool-2.4.7-x86_64-7.txz:  Rebuilt.
  Recompiled to update embedded GCC version number.
k/kernel-source-6.9.0-noarch-1.txz:  Upgraded.
l/harfbuzz-8.5.0-x86_64-1.txz:  Upgraded.
l/mozjs115-115.11.0esr-x86_64-1.txz:  Upgraded.
xap/mozilla-firefox-126.0-x86_64-1.txz:  Upgraded.
  This update contains security fixes and improvements.
  For more information, see:
    https://www.mozilla.org/en-US/firefox/126.0/releasenotes/
    https://www.mozilla.org/security/advisories/mfsa2024-21/
    https://www.cve.org/CVERecord?id=CVE-2024-4764
    https://www.cve.org/CVERecord?id=CVE-2024-4367
    https://www.cve.org/CVERecord?id=CVE-2024-4765
    https://www.cve.org/CVERecord?id=CVE-2024-4766
    https://www.cve.org/CVERecord?id=CVE-2024-4767
    https://www.cve.org/CVERecord?id=CVE-2024-4768
    https://www.cve.org/CVERecord?id=CVE-2024-4769
    https://www.cve.org/CVERecord?id=CVE-2024-4770
    https://www.cve.org/CVERecord?id=CVE-2024-4771
    https://www.cve.org/CVERecord?id=CVE-2024-4772
    https://www.cve.org/CVERecord?id=CVE-2024-4773
    https://www.cve.org/CVERecord?id=CVE-2024-4774
    https://www.cve.org/CVERecord?id=CVE-2024-4775
    https://www.cve.org/CVERecord?id=CVE-2024-4776
    https://www.cve.org/CVERecord?id=CVE-2024-4777
    https://www.cve.org/CVERecord?id=CVE-2024-4778
  (* Security fix *)
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 b95b61b80..67c4ca969 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Thu May  2 22:24:31 UTC 2024
+Tue May 14 18:09:39 UTC 2024
 
 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 6.6.30 Linux kernel using the packages
+upgrading to the generic 6.9 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-6.6.30-x86_64-1.txz
-  installpkg kernel-modules-6.6.30-x86_64-1.txz
+  installpkg kernel-generic-6.9.0-x86_64-1.txz
+  installpkg kernel-modules-6.9.0-x86_64-1.txz
   installpkg mkinitrd-1.4.11-x86_64-34.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 6.6.30 -m ext4
+  mkinitrd -c -k 6.9 -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 6.6.30
+Here's another example: Build an initrd image using Linux 6.9
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 6.6.30 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 6.9 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?