From d9f16c58d5d4ac0333335c8c6112629a4f520a05 Mon Sep 17 00:00:00 2001 From: Patrick J Volkerding Date: Wed, 18 Jul 2018 22:41:16 +0000 Subject: Wed Jul 18 22:41:16 UTC 2018 n/httpd-2.4.34-x86_64-1.txz: Upgraded. This update fixes two denial of service issues: mod_md: DoS via Coredumps on specially crafted requests mod_http2: DoS for HTTP/2 connections by specially crafted requests For more information, see: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8011 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1333 (* Security fix *) --- README.initrd | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'README.initrd') diff --git a/README.initrd b/README.initrd index b6ed715e7..eecad9bbc 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Thu Jul 12 01:21:42 UTC 2018 +Wed Jul 18 06:53:04 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,16 +33,16 @@ 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.55 Linux kernel using the packages +upgrading to the generic 4.14.56 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.55-x86_64-1.txz - installpkg kernel-modules-4.14.55-x86_64-1.txz - installpkg mkinitrd-1.4.11-x86_64-7.txz + installpkg kernel-generic-4.14.56-x86_64-1.txz + installpkg kernel-modules-4.14.56-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.14.55 -m ext4 + mkinitrd -c -k 4.14.56 -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.55 +Here's another example: Build an initrd image using Linux 4.14.56 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 4.14.55 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 4.14.56 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? -- cgit v1.2.3-79-gdb01