summaryrefslogtreecommitdiff
path: root/README.initrd
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2019-01-23 04:39:04 +0000
committerEric Hameleers <alien@slackware.com>2019-01-23 17:59:47 +0100
commitf4a16dfaa3822cd84790612cfb5f6794e7397ea1 (patch)
tree61a5be5a608a9549f8e0e4f7ae99c0d98ed1bed3 /README.initrd
parent238f2af030367ddd0d0a014e19be72c45483e153 (diff)
downloadcurrent-f4a16dfaa3822cd84790612cfb5f6794e7397ea1.tar.gz
Wed Jan 23 04:39:04 UTC 201920190123043904
a/kernel-generic-4.19.17-x86_64-1.txz: Upgraded. a/kernel-huge-4.19.17-x86_64-1.txz: Upgraded. a/kernel-modules-4.19.17-x86_64-1.txz: Upgraded. d/kernel-headers-4.19.17-x86-1.txz: Upgraded. d/scons-3.0.4-x86_64-1.txz: Upgraded. d/vala-0.42.5-x86_64-1.txz: Upgraded. k/kernel-source-4.19.17-noarch-1.txz: Upgraded. n/httpd-2.4.38-x86_64-1.txz: Upgraded. This release contains security fixes and improvements. mod_session: mod_session_cookie does not respect expiry time allowing sessions to be reused. [Hank Ibell] mod_http2: fixes a DoS attack vector. By sending slow request bodies to resources not consuming them, httpd cleanup code occupies a server thread unnecessarily. This was changed to an immediate stream reset which discards all stream state and incoming data. [Stefan Eissing] mod_ssl: Fix infinite loop triggered by a client-initiated renegotiation in TLSv1.2 (or earlier) with OpenSSL 1.1.1 and later. PR 63052. [Joe Orton] For more information, see: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17199 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17189 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0190 (* Security fix *) x/libdrm-2.4.97-x86_64-1.txz: Upgraded. isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. usb-and-pxe-installers/usbboot.img: Rebuilt.
Diffstat (limited to 'README.initrd')
-rw-r--r--README.initrd14
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd
index 088fdbd1..b26c8803 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Thu Jan 17 04:12:59 UTC 2019
+Wed Jan 23 01:55:38 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.16 Linux kernel using the packages
+upgrading to the generic 4.19.17 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.16-x86_64-1.txz
- installpkg kernel-modules-4.19.16-x86_64-1.txz
+ installpkg kernel-generic-4.19.17-x86_64-1.txz
+ installpkg kernel-modules-4.19.17-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.16 -m ext4
+ mkinitrd -c -k 4.19.17 -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.16
+Here's another example: Build an initrd image using Linux 4.19.17
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 4.19.16 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 4.19.17 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?