Wed Aug 30 21:58:04 UTC 202320230830215804

a/dcron-4.5-x86_64-13.txz:  Rebuilt.
  rc.crond: ensure world-writable permissions on /run/cron, needed for
  crontab -e with some editors. Thanks to lostintime.
a/kernel-firmware-20230830_5ebb591-noarch-1.txz:  Upgraded.
a/kernel-generic-6.1.50-x86_64-1.txz:  Upgraded.
a/kernel-huge-6.1.50-x86_64-1.txz:  Upgraded.
a/kernel-modules-6.1.50-x86_64-1.txz:  Upgraded.
d/ccache-4.8.3-x86_64-1.txz:  Upgraded.
d/clinfo-3.0.23.01.25-x86_64-1.txz:  Added.
  Thanks to Heinz Wiesinger.
d/kernel-headers-6.1.50-x86-1.txz:  Upgraded.
d/vala-0.56.13-x86_64-1.txz:  Upgraded.
k/kernel-source-6.1.50-noarch-1.txz:  Upgraded.
l/libnl3-3.8.0-x86_64-1.txz:  Upgraded.
l/mozjs102-102.15.0esr-x86_64-1.txz:  Upgraded.
x/mesa-23.1.6-x86_64-1.txz:  Upgraded.
  It appears that mesa-23.2.0 was pulled and replaced with mesa-23.2.0-rc2
  sometime after we upgraded to it. I've tested this version and it does not
  suffer from the "radeon: failed testing IB on GFX ring" bug that was
  happening with mesa-23.1.3, so let's use it for now.
xap/mozilla-firefox-115.2.0esr-x86_64-1.txz:  Upgraded.
  This update contains security fixes and improvements.
  For more information, see:
    https://www.mozilla.org/en-US/firefox/115.2.0/releasenotes/
    https://www.mozilla.org/security/advisories/mfsa2023-36/
    https://www.cve.org/CVERecord?id=CVE-2023-4573
    https://www.cve.org/CVERecord?id=CVE-2023-4574
    https://www.cve.org/CVERecord?id=CVE-2023-4575
    https://www.cve.org/CVERecord?id=CVE-2023-4576
    https://www.cve.org/CVERecord?id=CVE-2023-4577
    https://www.cve.org/CVERecord?id=CVE-2023-4051
    https://www.cve.org/CVERecord?id=CVE-2023-4578
    https://www.cve.org/CVERecord?id=CVE-2023-4053
    https://www.cve.org/CVERecord?id=CVE-2023-4580
    https://www.cve.org/CVERecord?id=CVE-2023-4581
    https://www.cve.org/CVERecord?id=CVE-2023-4582
    https://www.cve.org/CVERecord?id=CVE-2023-4583
    https://www.cve.org/CVERecord?id=CVE-2023-4584
    https://www.cve.org/CVERecord?id=CVE-2023-4585
  (* Security fix *)
xap/mozilla-thunderbird-115.2.0-x86_64-1.txz:  Upgraded.
  This release contains security fixes and improvements.
  For more information, see:
    https://www.mozilla.org/en-US/thunderbird/115.2.0/releasenotes/
  (* 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 beab59e02..b1eb050f5 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Mon Aug 28 00:25:53 UTC 2023
+Wed Aug 30 20:01:11 UTC 2023
 
 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.1.49 Linux kernel using the packages
+upgrading to the generic 6.1.50 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.1.49-x86_64-1.txz
-  installpkg kernel-modules-6.1.49-x86_64-1.txz
+  installpkg kernel-generic-6.1.50-x86_64-1.txz
+  installpkg kernel-modules-6.1.50-x86_64-1.txz
   installpkg mkinitrd-1.4.11-x86_64-33.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.1.49 -m ext4
+  mkinitrd -c -k 6.1.50 -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.1.49
+Here's another example: Build an initrd image using Linux 6.1.50
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 6.1.49 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 6.1.50 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?