Wed May 22 23:30:54 UTC 201920190522233054

a/kernel-generic-4.19.45-x86_64-1.txz:  Upgraded.
a/kernel-huge-4.19.45-x86_64-1.txz:  Upgraded.
a/kernel-modules-4.19.45-x86_64-1.txz:  Upgraded.
ap/texinfo-6.6-x86_64-2.txz:  Rebuilt.
  Recompiled against perl-5.30.0.
ap/vim-8.1.1365-x86_64-1.txz:  Upgraded.
  Compiled against perl-5.30.0.
d/bison-3.4.1-x86_64-1.txz:  Upgraded.
d/kernel-headers-4.19.45-x86-1.txz:  Upgraded.
d/parallel-20190522-noarch-1.txz:  Upgraded.
d/perl-5.30.0-x86_64-1.txz:  Upgraded.
  Module upgraded: Net-SSLeay-1.88
d/strace-5.1-x86_64-1.txz:  Upgraded.
k/kernel-source-4.19.45-noarch-1.txz:  Upgraded.
kde/perlkde-4.14.3-x86_64-8.txz:  Rebuilt.
  Recompiled against perl-5.30.0.
kde/perlqt-4.14.3-x86_64-9.txz:  Rebuilt.
  Recompiled against perl-5.30.0.
l/glib2-2.60.3-x86_64-1.txz:  Upgraded.
n/curl-7.65.0-x86_64-1.txz:  Upgraded.
  This release fixes the following security issues:
  Integer overflows in curl_url_set
  tftp: use the current blksize for recvfrom()
  For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5435
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5436
  (* Security fix *)
n/epic5-2.1.1-x86_64-2.txz:  Rebuilt.
  Recompiled against perl-5.30.0.
n/irssi-1.2.0-x86_64-2.txz:  Rebuilt.
  Recompiled against perl-5.30.0.
n/net-snmp-5.8-x86_64-5.txz:  Rebuilt.
  Recompiled against perl-5.30.0.
n/ntp-4.2.8p13-x86_64-2.txz:  Rebuilt.
  Recompiled against perl-5.30.0.
n/samba-4.10.4-x86_64-1.txz:  Upgraded.
x/mesa-19.0.5-x86_64-1.txz:  Upgraded.
xap/hexchat-2.14.2-x86_64-4.txz:  Rebuilt.
  Recompiled against perl-5.30.0.
xap/rxvt-unicode-9.22-x86_64-7.txz:  Rebuilt.
  Recompiled against perl-5.30.0.
xap/vim-gvim-8.1.1365-x86_64-1.txz:  Upgraded.
  Compiled against perl-5.30.0.
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 73e8fabf5..2fbb8634d 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Fri May 17 02:28:34 UTC 2019
+Wed May 22 22:59:48 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.44 Linux kernel using the packages
+upgrading to the generic 4.19.45 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.44-x86_64-1.txz
-  installpkg kernel-modules-4.19.44-x86_64-1.txz
+  installpkg kernel-generic-4.19.45-x86_64-1.txz
+  installpkg kernel-modules-4.19.45-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.44 -m ext4
+  mkinitrd -c -k 4.19.45 -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.44
+Here's another example: Build an initrd image using Linux 4.19.45
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 4.19.44 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 4.19.45 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?