Wed Jul 10 23:56:13 UTC 201920190710235613

a/glibc-zoneinfo-2019b-noarch-1.txz:  Upgraded.
a/kernel-generic-4.19.58-x86_64-1.txz:  Upgraded.
a/kernel-huge-4.19.58-x86_64-1.txz:  Upgraded.
a/kernel-modules-4.19.58-x86_64-1.txz:  Upgraded.
d/Cython-0.29.12-x86_64-1.txz:  Upgraded.
d/kernel-headers-4.19.58-x86-1.txz:  Upgraded.
d/mercurial-5.0.2-x86_64-1.txz:  Upgraded.
d/python3-3.7.4-x86_64-1.txz:  Upgraded.
k/kernel-source-4.19.58-noarch-1.txz:  Upgraded.
l/glib2-2.60.5-x86_64-1.txz:  Upgraded.
n/gnupg2-2.2.17-x86_64-1.txz:  Upgraded.
n/iproute2-5.2.0-x86_64-1.txz:  Upgraded.
n/samba-4.10.6-x86_64-1.txz:  Upgraded.
x/libva-utils-2.5.0-x86_64-1.txz:  Upgraded.
x/mesa-19.1.2-x86_64-1.txz:  Upgraded.
xap/mozilla-firefox-68.0esr-x86_64-1.txz:  Upgraded.
  This release contains security fixes and improvements. Some of the patched
  flaws are considered critical, and could be used to run attacker code and
  install software, requiring no user interaction beyond normal browsing.
  For more information, see:
    https://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html
    https://www.mozilla.org/en-US/security/advisories/mfsa2019-22/
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9811
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11711
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11712
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11713
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11729
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11715
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11717
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11719
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11730
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11709
  (* Security fix *)
xap/mozilla-thunderbird-60.8.0-x86_64-1.txz:  Upgraded.
  This is a bugfix release.
  For more information, see:
    https://www.mozilla.org/en-US/thunderbird/60.8.0/releasenotes/
xfce/garcon-0.6.3-x86_64-2.txz:  Rebuilt.
  Patched crash bug.
  Installed gtk-doc HTML docs.
  Thanks to Robby Workman.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
testing/packages/blueman-2.1.1-x86_64-1.txz:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.

1 files changed, 7 insertions, 7 deletions

diff --git a/README.initrd b/README.initrd
index fbfdd6a43..18281e6fe 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Wed Jul  3 20:35:45 UTC 2019
+Wed Jul 10 19:33:37 UTC 2019
 
 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 4.19.57 Linux kernel using the packages
+upgrading to the generic 4.19.58 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-4.19.57-x86_64-1.txz
-  installpkg kernel-modules-4.19.57-x86_64-1.txz
+  installpkg kernel-generic-4.19.58-x86_64-1.txz
+  installpkg kernel-modules-4.19.58-x86_64-1.txz
   installpkg mkinitrd-1.4.11-x86_64-12.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 4.19.57 -m ext4
+  mkinitrd -c -k 4.19.58 -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 4.19.57
+Here's another example: Build an initrd image using Linux 4.19.58
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 4.19.57 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 4.19.58 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?