Tue Jun 12 05:02:45 UTC 201820180612050245

a/kernel-firmware-20180606_d114732-noarch-1.txz:  Upgraded.
a/kernel-generic-4.14.49-x86_64-1.txz:  Upgraded.
a/kernel-huge-4.14.49-x86_64-1.txz:  Upgraded.
a/kernel-modules-4.14.49-x86_64-1.txz:  Upgraded.
a/libcgroup-0.41-x86_64-4.txz:  Rebuilt.
  Apply all post 0.41 patches from git, including one for an infinite loop
  bug that causes 100% CPU usage on one core. Thanks to chris.willing.
a/pkgtools-15.0-noarch-17.txz:  Rebuilt.
  installpkg: Use terse mode if TERSE=0 is set in the environment (this already
  works for removepkg and upgradepkg). This allows using terse mode in other
  tools that use the pkgtools (such as slackpkg with: TERSE=0 slackpkg).
  Thanks to Xsane.
ap/hplip-3.18.6-x86_64-1.txz:  Upgraded.
d/kernel-headers-4.14.49-x86-1.txz:  Upgraded.
k/kernel-source-4.14.49-noarch-1.txz:  Upgraded.
   GPIO_AMDPT n -> m (thanks to walecha)
   NFSD_V3_ACL n -> y (thanks to Jonathan Woithe)
   NFS_V3_ACL n -> y (thanks to Jonathan Woithe)
   NFS_V4_2 n -> y
  +NFSD_V2_ACL y
  +NFS_ACL_SUPPORT y
  +NFS_V4_SECURITY_LABEL y
l/LibRaw-0.18.12-x86_64-1.txz:  Upgraded.
  This update fixes bugs and security issues, including:
  parse_qt: possible integer overflow
  reject broken/crafted NOKIARAW files
  recover read position if TIFF/EXIF tag is too long
  possible infinite loop in parse_minolta()
  possible stack overrun in X3F parser
  out of bounds read in X3F parser
  For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13735
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14265
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10528
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10529
  (* Security fix *)
l/dconf-0.26.1-x86_64-3.txz:  Rebuilt.
  Eliminate install script noise.
l/dconf-editor-3.26.2-x86_64-3.txz:  Rebuilt.
  Eliminate install script noise.
n/iproute2-4.17.0-x86_64-1.txz:  Upgraded.
x/wqy-zenhei-font-ttf-0.8.38_1-noarch-7.txz:  Rebuilt.
  Try to avoid overriding other font choices unless lang = zh-cn or zh-sg.
x/xkbcomp-1.4.2-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 2a2a2bb5..829b93cf 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Wed Jun  6 20:17:46 UTC 2018
+Tue Jun 12 04:26:32 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.14.48 Linux kernel using the packages
+upgrading to the generic 4.14.49 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.14.48-x86_64-1.txz
-  installpkg kernel-modules-4.14.48-x86_64-1.txz
+  installpkg kernel-generic-4.14.49-x86_64-1.txz
+  installpkg kernel-modules-4.14.49-x86_64-1.txz
   installpkg mkinitrd-1.4.11-x86_64-7.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.14.48 -m ext4
+  mkinitrd -c -k 4.14.49 -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.14.48
+Here's another example: Build an initrd image using Linux 4.14.49
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 4.14.48 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 4.14.49 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?