summaryrefslogtreecommitdiff
path: root/README.initrd
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2021-04-29 01:37:15 +0000
committerEric Hameleers <alien@slackware.com>2021-04-29 09:00:04 +0200
commit3c2034f8a207f61aa2ea7c0a48adad6919a64643 (patch)
tree6030976b791612cd12fe048f8c74c121cf307ace /README.initrd
parentabdca401c7c45e652987c030a41f12408b916eee (diff)
downloadcurrent-3c2034f8a207f61aa2ea7c0a48adad6919a64643.tar.gz
Thu Apr 29 01:37:15 UTC 202120210429013715
n/bind-9.16.15-x86_64-1.txz: Upgraded. This update fixes bugs and the following security issues: A specially crafted GSS-TSIG query could cause a buffer overflow in the ISC implementation of SPNEGO. named crashed when a DNAME record placed in the ANSWER section during DNAME chasing turned out to be the final answer to a client query. Insufficient IXFR checks could result in named serving a zone without an SOA record at the apex, leading to a RUNTIME_CHECK assertion failure when the zone was subsequently refreshed. This has been fixed by adding an owner name check for all SOA records which are included in a zone transfer. For more information, see: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-25216 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-25215 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-25214 (* Security fix *)
Diffstat (limited to 'README.initrd')
-rw-r--r--README.initrd16
1 files changed, 8 insertions, 8 deletions
diff --git a/README.initrd b/README.initrd
index a936d85d..404074c6 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Wed Apr 21 19:30:00 UTC 2021
+Wed Apr 28 18:30:50 UTC 2021
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 5.10.32 Linux kernel using the packages
+upgrading to the generic 5.10.33 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.10.32-x86_64-1.txz
- installpkg kernel-modules-5.10.32-x86_64-1.txz
- installpkg mkinitrd-1.4.11-x86_64-23.txz
+ installpkg kernel-generic-5.10.33-x86_64-1.txz
+ installpkg kernel-modules-5.10.33-x86_64-1.txz
+ installpkg mkinitrd-1.4.11-x86_64-24.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.10.32 -m ext4
+ mkinitrd -c -k 5.10.33 -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.10.32
+Here's another example: Build an initrd image using Linux 5.10.33
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.10.32 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.10.33 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?