diff options
| author |   Patrick J Volkerding <volkerdi@slackware.com> | 2022-06-01 00:49:45 +0000 |
|---|---|---|
| committer |   Eric Hameleers <alien@slackware.com> | 2022-06-01 07:00:07 +0200 |
| commit | f7ccccdcba28b2e09d0c9731e7761990f1bf6a8e (patch) | |
| tree | 5b2ff96559ffaeacd4cde9a51c061f99d0165331 /README.initrd | |
| parent | de42b727197149058ceade000c902b6fc65836fd (diff) | |
| download | current-f7ccccdcba28b2e09d0c9731e7761990f1bf6a8e.tar.gz current-f7ccccdcba28b2e09d0c9731e7761990f1bf6a8e.tar.xz | |
Wed Jun 1 00:49:45 UTC 202220220601004945
a/dialog-1.3_20220526-x86_64-1.txz: Upgraded.
a/kernel-generic-5.17.12-x86_64-1.txz: Upgraded.
a/kernel-huge-5.17.12-x86_64-1.txz: Upgraded.
a/kernel-modules-5.17.12-x86_64-1.txz: Upgraded.
ap/sysstat-12.6.0-x86_64-1.txz: Upgraded.
d/kernel-headers-5.17.12-x86-1.txz: Upgraded.
k/kernel-source-5.17.12-noarch-1.txz: Upgraded.
l/libtiff-4.4.0-x86_64-1.txz: Upgraded.
n/gnutls-3.7.6-x86_64-1.txz: Upgraded.
n/links-2.27-x86_64-1.txz: Upgraded.
xap/mozilla-firefox-101.0-x86_64-1.txz: Upgraded.
This update contains security fixes and improvements.
For more information, see:
https://www.mozilla.org/en-US/firefox/101.0/releasenotes/
https://www.mozilla.org/security/advisories/mfsa2022-20/
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31736
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31737
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31738
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31739
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31740
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31741
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31742
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31743
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31744
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31745
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1919
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31747
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31748
(* Security fix *)
extra/rust-for-mozilla/rust-1.59.0-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 b0f38e4a4..72e08f8e8 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Wed May 25 19:35:06 UTC 2022 +Tue May 31 19:19:11 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.17.11 Linux kernel using the packages +upgrading to the generic 5.17.12 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.11-x86_64-1.txz - installpkg kernel-modules-5.17.11-x86_64-1.txz + installpkg kernel-generic-5.17.12-x86_64-1.txz + installpkg kernel-modules-5.17.12-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.11 -m ext4 + mkinitrd -c -k 5.17.12 -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.11 +Here's another example: Build an initrd image using Linux 5.17.12 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.17.11 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.17.12 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |