diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2021-01-06 22:59:38 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2021-01-07 08:59:48 +0100 |
commit | ba4a3a137963e8f2dd63d2c594cbbfd099a2bc47 (patch) | |
tree | abc50bfa097ac5e7989881d214de7834d08624be /README.initrd | |
parent | 8b1588afc8929eda7491496bfac0b004a1d88efc (diff) | |
download | current-ba4a3a137963e8f2dd63d2c594cbbfd099a2bc47.tar.gz |
Wed Jan 6 22:59:38 UTC 202120210106225938
a/kernel-generic-5.10.5-x86_64-1.txz: Upgraded.
a/kernel-huge-5.10.5-x86_64-1.txz: Upgraded.
a/kernel-modules-5.10.5-x86_64-1.txz: Upgraded.
d/kernel-headers-5.10.5-x86-1.txz: Upgraded.
d/meson-0.56.1-x86_64-1.txz: Upgraded.
k/kernel-source-5.10.5-noarch-1.txz: Upgraded.
We'll turn off the silent stream feature as there's a known deadlock bug that
remains in 5.10.5. Perhaps we'll restore it once that's patched... but we
made it this far without the feature so I'll probably wait for a case to be
made for it. Thanks to Petri Kaukasoina.
Also build the intelfb module. This doesn't have anything to do with the
lockups occurring on Intel systems, but we might as well provide the module.
It remains blacklisted by default.
FB_INTEL n -> m
SND_HDA_INTEL_HDMI_SILENT_STREAM y -> n
+FB_INTEL_DEBUG n
+FB_INTEL_I2C y
l/imagemagick-7.0.10_56-x86_64-1.txz: Upgraded.
x/ibus-table-1.12.3-x86_64-1.txz: Upgraded.
xap/mozilla-firefox-78.6.1esr-x86_64-1.txz: Upgraded.
This release contains a security fix:
A malicious peer could have modified a COOKIE-ECHO chunk in a SCTP packet
in a way that potentially resulted in a use-after-free. We presume that with
enough effort it could have been exploited to run arbitrary code.
For more information, see:
https://www.mozilla.org/en-US/firefox/78.6.1/releasenotes/
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16044
(* Security fix *)
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 151618e4..c512e135 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Wed Dec 30 20:12:29 UTC 2020 +Wed Jan 6 22:37:31 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,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.10.4 Linux kernel using the packages +upgrading to the generic 5.10.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.10.4-x86_64-1.txz - installpkg kernel-modules-5.10.4-x86_64-1.txz + installpkg kernel-generic-5.10.5-x86_64-1.txz + installpkg kernel-modules-5.10.5-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-16.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.4 -m ext4 + mkinitrd -c -k 5.10.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.10.4 +Here's another example: Build an initrd image using Linux 5.10.5 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.10.4 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.10.5 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |