Thu Apr 2 06:07:52 UTC 202020200402060752

a/hwdata-0.334-noarch-1.txz:  Upgraded.
a/kernel-generic-5.4.29-x86_64-1.txz:  Upgraded.
a/kernel-huge-5.4.29-x86_64-1.txz:  Upgraded.
a/kernel-modules-5.4.29-x86_64-1.txz:  Upgraded.
a/pkgtools-15.0-noarch-32.txz:  Rebuilt.
  installpkg: handle the uninstall script packaged as /install/douninst.sh.
  removepkg: add --skip-douninst option to skip running the uninstall script.
    Save removed douninst.sh in /var/log/pkgtools/removed_uninstall_scripts.
ap/groff-1.22.4-x86_64-2.txz:  Rebuilt.
  Fixed docdir. Thanks to Xsane.
d/gcc-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-brig-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-g++-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-gdc-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-gfortran-9.3.0-x86_64-2.txz:  Rebuilt.
  Patched a compiler bug concerning assumed-shape vs. deferred-shape arrays.
  Thanks to Lockywolf.
d/gcc-gnat-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-go-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-objc-9.3.0-x86_64-2.txz:  Rebuilt.
d/kernel-headers-5.4.29-x86-1.txz:  Upgraded.
d/ruby-2.7.1-x86_64-1.txz:  Upgraded.
  This update fixes security issues:
  Unsafe Object Creation Vulnerability in JSON (Additional fix).
  Heap exposure vulnerability in the socket library.
  For more information, see:
    https://www.ruby-lang.org/en/news/2020/03/19/json-dos-cve-2020-10663/
    https://www.ruby-lang.org/en/news/2020/03/31/heap-exposure-in-socket-cve-2020-10933/
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10663
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10933
  (* Security fix *)
k/kernel-source-5.4.29-noarch-1.txz:  Upgraded.
l/graphite2-1.3.14-x86_64-1.txz:  Upgraded.
l/librsvg-2.48.2-x86_64-1.txz:  Upgraded.
l/utf8proc-2.5.0-x86_64-1.txz:  Upgraded.
x/libva-2.7.0-x86_64-1.txz:  Upgraded.
x/libva-utils-2.7.1-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 b770697d7..be683bbe1 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Wed Mar 25 22:26:01 UTC 2020
+Thu Apr  2 00:07:41 UTC 2020
 
 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.4.28 Linux kernel using the packages
+upgrading to the generic 5.4.29 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.4.28-x86_64-1.txz
-  installpkg kernel-modules-5.4.28-x86_64-1.txz
+  installpkg kernel-generic-5.4.29-x86_64-1.txz
+  installpkg kernel-modules-5.4.29-x86_64-1.txz
   installpkg mkinitrd-1.4.11-x86_64-14.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.4.28 -m ext4
+  mkinitrd -c -k 5.4.29 -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.4.28
+Here's another example: Build an initrd image using Linux 5.4.29
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 5.4.28 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 5.4.29 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?