Wed Nov 28 07:25:32 UTC 201820181128072532

a/elilo-3.16-x86_64-9.txz:  Rebuilt.
  eliloconfig: don't assume that mount output lists the / partition first.
a/f2fs-tools-1.12.0-x86_64-1.txz:  Added.
a/kernel-generic-4.19.5-x86_64-1.txz:  Upgraded.
a/kernel-huge-4.19.5-x86_64-1.txz:  Upgraded.
 CRYPTO_CRC32 m -> y
 F2FS_FS m -> y
a/kernel-modules-4.19.5-x86_64-1.txz:  Upgraded.
a/sysvinit-scripts-2.1-noarch-22.txz:  Rebuilt.
  rc.S: if we're using F2FS for the root filesystem, don't try to check it as
  fsck.f2fs throws an error on trying to check a read-only filesystem.
d/clisp-2.49_20181112_df3b9f6fd-x86_64-1.txz:  Upgraded.
d/kernel-headers-4.19.5-x86-1.txz:  Upgraded.
k/kernel-source-4.19.5-noarch-1.txz:  Upgraded.
l/graphite2-1.3.12-x86_64-1.txz:  Added.
  Required by harfbuzz in order to use it as a system library for TeXlive.
l/harfbuzz-2.1.3-x86_64-1.txz:  Upgraded.
  Requires graphite2-1.3.12.
t/texlive-2018.180822-x86_64-4.txz:  Rebuilt.
  Use system harfbuzz, not the bundled version.
isolinux/initrd.img:  Rebuilt.
  Activate LVM volumes at boot, not only when setup is run.
  Make /etc/mtab a symlink to /proc/mounts on the installer.
  On a freshly installed system, make /etc/mtab a symlink to /proc/mounts.
  Include f2fs-tools on the installer.
  Support installing on F2FS partitions.
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 237dd4a59..bb0f75b80 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Fri Nov 23 22:11:18 UTC 2018
+Wed Nov 28 01:30:16 UTC 2018
 
 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.4 Linux kernel using the packages
+upgrading to the generic 4.19.5 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.4-x86_64-1.txz
-  installpkg kernel-modules-4.19.4-x86_64-1.txz
+  installpkg kernel-generic-4.19.5-x86_64-1.txz
+  installpkg kernel-modules-4.19.5-x86_64-1.txz
   installpkg mkinitrd-1.4.11-x86_64-8.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.4 -m ext4
+  mkinitrd -c -k 4.19.5 -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.4
+Here's another example: Build an initrd image using Linux 4.19.5
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 4.19.4 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 4.19.5 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?