Thu May 25 00:24:33 UTC 202320230525002433

a/elilo-3.16-x86_64-16.txz:  Rebuilt.
  eliloconfig: don't mess with mounting efivarfs. This should be handled by
  rc.S, or by whatever the admin put in /etc/fstab.
a/kernel-firmware-20230523_1ba3519-noarch-1.txz:  Upgraded.
a/kernel-generic-6.1.30-x86_64-1.txz:  Upgraded.
a/kernel-huge-6.1.30-x86_64-1.txz:  Upgraded.
a/kernel-modules-6.1.30-x86_64-1.txz:  Upgraded.
a/sysvinit-scripts-15.1-noarch-5.txz:  Rebuilt.
  rc.S: mount efivarfs rw, may be overridden in /etc/default/efivarfs.
ap/sc-im-0.8.3-x86_64-1.txz:  Upgraded.
d/kernel-headers-6.1.30-x86-1.txz:  Upgraded.
d/parallel-20230522-noarch-1.txz:  Upgraded.
k/kernel-source-6.1.30-noarch-1.txz:  Upgraded.
l/enchant-2.4.0-x86_64-1.txz:  Upgraded.
l/glib2-2.76.3-x86_64-1.txz:  Upgraded.
l/gtk+3-3.24.38-x86_64-1.txz:  Upgraded.
l/qt5-5.15.9_20230523_245f369c-x86_64-1.txz:  Upgraded.
  This update fixes a security issue.
  Qt-based clients may mismatch HSTS headers (Strict-Transport-Security),
  which would prevent the client from switching to a secure HTTPS
  connection as requested by a server.
  For more information, see:
    https://www.cve.org/CVERecord?id=CVE-2023-32762
  (* Security fix *)
n/curl-8.1.1-x86_64-1.txz:  Upgraded.
  This is a bugfix release.
t/texlive-2023.230322-x86_64-3.txz:  Rebuilt.
  This update patches a security issue:
  LuaTeX before 1.17.0 allows execution of arbitrary shell commands when
  compiling a TeX file obtained from an untrusted source. This occurs
  because luatex-core.lua lets the original io.popen be accessed. This also
  affects TeX Live before 2023 r66984 and MiKTeX before 23.5.
  Thanks to Johannes Schoepfer.
  For more information, see:
    https://www.cve.org/CVERecord?id=CVE-2023-32700
  (* Security fix *)
xap/mozilla-firefox-113.0.2-x86_64-1.txz:  Upgraded.
  This is a bugfix release.
  For more information, see:
    https://www.mozilla.org/en-US/firefox/113.0.2/releasenotes/
xfce/libxfce4ui-4.18.4-x86_64-1.txz:  Upgraded.
xfce/xfce4-panel-4.18.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 330619dff..73c02b4f9 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Wed May 17 20:24:47 UTC 2023
+Thu May 25 00:09:28 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.29 Linux kernel using the packages
+upgrading to the generic 6.1.30 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.29-x86_64-1.txz
-  installpkg kernel-modules-6.1.29-x86_64-1.txz
+  installpkg kernel-generic-6.1.30-x86_64-1.txz
+  installpkg kernel-modules-6.1.30-x86_64-1.txz
   installpkg mkinitrd-1.4.11-x86_64-32.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.29 -m ext4
+  mkinitrd -c -k 6.1.30 -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.29
+Here's another example: Build an initrd image using Linux 6.1.30
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 6.1.29 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 6.1.30 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?