summaryrefslogtreecommitdiff
path: root/README.initrd
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2020-06-03 20:21:52 +0000
committerEric Hameleers <alien@slackware.com>2020-06-04 08:59:54 +0200
commit51dac8e0d6d3193cb63563eb91a2cd6c8084e20d (patch)
treedff63b2d50f9c7f7545d0a893fd358db164038d3 /README.initrd
parent611a2c13b5943177c809540ee05d83bf10ae940a (diff)
downloadcurrent-51dac8e0d6d3193cb63563eb91a2cd6c8084e20d.tar.gz
Wed Jun 3 20:21:52 UTC 202020200603202152
a/dbus-1.12.18-x86_64-1.txz: Upgraded. a/kernel-generic-5.4.44-x86_64-1.txz: Upgraded. a/kernel-huge-5.4.44-x86_64-1.txz: Upgraded. a/kernel-modules-5.4.44-x86_64-1.txz: Upgraded. d/bison-3.6.3-x86_64-1.txz: Upgraded. d/kernel-headers-5.4.44-x86-1.txz: Upgraded. d/subversion-1.14.0-x86_64-1.txz: Upgraded. k/kernel-source-5.4.44-noarch-1.txz: Upgraded. l/harfbuzz-2.6.7-x86_64-1.txz: Upgraded. l/libcap-2.36-x86_64-1.txz: Upgraded. l/librsvg-2.48.6-x86_64-1.txz: Upgraded. n/gnutls-3.6.14-x86_64-1.txz: Upgraded. Fixed insecure session ticket key construction, since 3.6.4. The TLS server would not bind the session ticket encryption key with a value supplied by the application until the initial key rotation, allowing attacker to bypass authentication in TLS 1.3 and recover previous conversations in TLS 1.2. [GNUTLS-SA-2020-06-03, CVSS: high] (* Security fix *) n/iproute2-5.7.0-x86_64-1.txz: Upgraded. n/iptables-1.8.5-x86_64-1.txz: Upgraded. xap/audacious-4.0.4-x86_64-1.txz: Upgraded. xap/audacious-plugins-4.0.4-x86_64-1.txz: Upgraded. extra/pure-alsa-system/audacious-plugins-4.0.4-x86_64-1_alsa.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 9be7c462..57eb8892 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Thu May 28 18:00:07 UTC 2020
+Wed Jun 3 20:12:34 UTC 2020
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 5.4.43 Linux kernel using the packages
+upgrading to the generic 5.4.44 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-5.4.43-x86_64-1.txz
- installpkg kernel-modules-5.4.43-x86_64-1.txz
+ installpkg kernel-generic-5.4.44-x86_64-1.txz
+ installpkg kernel-modules-5.4.44-x86_64-1.txz
installpkg mkinitrd-1.4.11-x86_64-15.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 5.4.43 -m ext4
+ mkinitrd -c -k 5.4.44 -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 5.4.43
+Here's another example: Build an initrd image using Linux 5.4.44
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.4.43 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.4.44 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?