diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2022-03-17 19:46:28 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2022-03-18 06:59:44 +0100 |
commit | a55e318a865afebcd9ca91039ed256ce4e907f81 (patch) | |
tree | b07b4d25ff149f236acfe09ad7b03aa17298702d /README.initrd | |
parent | ae74897d321c65aca844b23e4ae780fdd915185f (diff) | |
download | current-a55e318a865afebcd9ca91039ed256ce4e907f81.tar.gz current-a55e318a865afebcd9ca91039ed256ce4e907f81.tar.xz |
Thu Mar 17 19:46:28 UTC 202220220317194628
Have a great day, everyone! Off to enjoy a couple Guinness. :-)
a/kernel-generic-5.16.15-x86_64-1.txz: Upgraded.
a/kernel-huge-5.16.15-x86_64-1.txz: Upgraded.
a/kernel-modules-5.16.15-x86_64-1.txz: Upgraded.
a/openssl-solibs-1.1.1n-x86_64-1.txz: Upgraded.
d/kernel-headers-5.16.15-x86-1.txz: Upgraded.
d/meson-0.61.3-x86_64-1.txz: Upgraded.
k/kernel-source-5.16.15-noarch-1.txz: Upgraded.
kde/kstars-3.5.8-x86_64-1.txz: Upgraded.
l/nodejs-16.14.1-x86_64-1.txz: Upgraded.
n/bind-9.18.1-x86_64-1.txz: Upgraded.
This update fixes bugs and the following security issues:
An assertion could occur in resume_dslookup() if the fetch had been shut
down earlier.
Lookups involving a DNAME could trigger an INSIST when "synth-from-dnssec"
was enabled.
A synchronous call to closehandle_cb() caused isc__nm_process_sock_buffer()
to be called recursively, which in turn left TCP connections hanging in the
CLOSE_WAIT state blocking indefinitely when out-of-order processing was
disabled.
The rules for acceptance of records into the cache have been tightened to
prevent the possibility of poisoning if forwarders send records outside
the configured bailiwick.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0667
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0635
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0396
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-25220
(* Security fix *)
n/bluez-5.64-x86_64-1.txz: Upgraded.
n/mobile-broadband-provider-info-20220316-x86_64-1.txz: Upgraded.
n/openssl-1.1.1n-x86_64-1.txz: Upgraded.
This update fixes a high severity security issue:
The BN_mod_sqrt() function, which computes a modular square root, contains
a bug that can cause it to loop forever for non-prime moduli.
For more information, see:
https://www.openssl.org/news/secadv/20220315.txt
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0778
(* Security fix *)
n/openvpn-2.5.6-x86_64-1.txz: Upgraded.
x/ibus-1.5.26-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.initrd | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd index 3ddcb076f..6baaff0f0 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Sat Mar 12 20:40:47 UTC 2022 +Thu Mar 17 19:26:17 UTC 2022 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.16.14 Linux kernel using the packages +upgrading to the generic 5.16.15 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.16.14-x86_64-1.txz - installpkg kernel-modules-5.16.14-x86_64-1.txz + installpkg kernel-generic-5.16.15-x86_64-1.txz + installpkg kernel-modules-5.16.15-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-28.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.16.14 -m ext4 + mkinitrd -c -k 5.16.15 -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.16.14 +Here's another example: Build an initrd image using Linux 5.16.15 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.16.14 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.16.15 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |