diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2022-04-27 21:43:51 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2022-04-28 08:59:37 +0200 |
commit | 2ab30d1fd90998cdb2715bec99430671123c3ece (patch) | |
tree | a328234d670d7f3771dda79b370354b4344986f3 /README.initrd | |
parent | ee861a17268a54a17b3b321d9a1ff82ed547e606 (diff) | |
download | current-2ab30d1fd90998cdb2715bec99430671123c3ece.tar.gz current-2ab30d1fd90998cdb2715bec99430671123c3ece.tar.xz |
Wed Apr 27 21:43:51 UTC 202220220427214351
a/kernel-generic-5.17.5-x86_64-1.txz: Upgraded.
a/kernel-huge-5.17.5-x86_64-1.txz: Upgraded.
a/kernel-modules-5.17.5-x86_64-1.txz: Upgraded.
a/sysvinit-3.04-x86_64-1.txz: Upgraded.
ap/sqlite-3.38.3-x86_64-1.txz: Upgraded.
d/gcc-11.3.0-x86_64-1.txz: Upgraded.
d/gcc-brig-11.3.0-x86_64-1.txz: Upgraded.
d/gcc-g++-11.3.0-x86_64-1.txz: Upgraded.
d/gcc-gdc-11.3.0-x86_64-1.txz: Upgraded.
d/gcc-gfortran-11.3.0-x86_64-1.txz: Upgraded.
d/gcc-gnat-11.3.0-x86_64-1.txz: Upgraded.
d/gcc-go-11.3.0-x86_64-1.txz: Upgraded.
d/gcc-objc-11.3.0-x86_64-1.txz: Upgraded.
d/kernel-headers-5.17.5-x86-1.txz: Upgraded.
d/libtool-2.4.7-x86_64-1.txz: Upgraded.
This also updates the embedded GCC version number.
k/kernel-source-5.17.5-noarch-1.txz: Upgraded.
CC_VERSION_TEXT "gcc (GCC) 11.2.0" -> "gcc (GCC) 11.3.0"
GCC_VERSION 110200 -> 110300
+CC_HAS_SLS y
+SLS y
kde/krita-5.0.6-x86_64-1.txz: Upgraded.
l/netpbm-10.98.02-x86_64-1.txz: Upgraded.
l/nodejs-16.15.0-x86_64-1.txz: Upgraded.
n/curl-7.83.0-x86_64-1.txz: Upgraded.
This update fixes security issues:
OAUTH2 bearer bypass in connection re-use.
Credential leak on redirect.
Bad local IPv6 connection reuse.
Auth/cookie leak on redirect.
For more information, see:
https://curl.se/docs/CVE-2022-22576.html
https://curl.se/docs/CVE-2022-27774.html
https://curl.se/docs/CVE-2022-27775.html
https://curl.se/docs/CVE-2022-27776.html
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22576
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27774
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27775
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27776
(* Security fix *)
n/fetchmail-6.4.30-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 | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/README.initrd b/README.initrd index 70f534532..a674296a5 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Thu Apr 21 18:54:07 UTC 2022 +Wed Apr 27 21:31:04 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,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.17.4 Linux kernel using the packages +upgrading to the generic 5.17.5 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.17.4-x86_64-1.txz - installpkg kernel-modules-5.17.4-x86_64-1.txz - installpkg mkinitrd-1.4.11-x86_64-28.txz + installpkg kernel-generic-5.17.5-x86_64-1.txz + installpkg kernel-modules-5.17.5-x86_64-1.txz + installpkg mkinitrd-1.4.11-x86_64-29.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.17.4 -m ext4 + mkinitrd -c -k 5.17.5 -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.17.4 +Here's another example: Build an initrd image using Linux 5.17.5 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.17.4 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.17.5 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |