summaryrefslogtreecommitdiffstats
path: root/README.initrd
diff options
context:
space:
mode:
author Patrick J Volkerding <volkerdi@slackware.com>2022-09-20 22:50:28 +0000
committer Eric Hameleers <alien@slackware.com>2022-09-21 07:00:16 +0200
commitbae5a7d8587d3c1c7fd0ca466a80bb744833c012 (patch)
tree56df345f19d265415a60ae05c2457258f8896e9c /README.initrd
parent7de9181e0d4848ae4bb93be7cf8f21660a4e8752 (diff)
downloadcurrent-bae5a7d8587d3c1c7fd0ca466a80bb744833c012.tar.gz
current-bae5a7d8587d3c1c7fd0ca466a80bb744833c012.tar.xz
Tue Sep 20 22:50:28 UTC 202220220920225028
a/kernel-generic-5.19.10-x86_64-1.txz: Upgraded. a/kernel-huge-5.19.10-x86_64-1.txz: Upgraded. a/kernel-modules-5.19.10-x86_64-1.txz: Upgraded. d/kernel-headers-5.19.10-x86-1.txz: Upgraded. k/kernel-source-5.19.10-noarch-1.txz: Upgraded. l/expat-2.4.9-x86_64-1.txz: Upgraded. This update fixes a security issue: Heap use-after-free vulnerability in function doContent. Expected impact is denial of service or potentially arbitrary code execution. For more information, see: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40674 (* Security fix *) l/libffi-3.4.3-x86_64-1.txz: Upgraded. xap/mozilla-firefox-105.0-x86_64-1.txz: Upgraded. This update contains security fixes and improvements. For more information, see: https://www.mozilla.org/en-US/firefox/105.0/releasenotes/ https://www.mozilla.org/security/advisories/mfsa2022-40/ https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40959 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40960 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40958 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40961 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40956 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40957 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40962 (* Security fix *) xap/mozilla-thunderbird-102.3.0-x86_64-1.txz: Upgraded. This is a bugfix release. For more information, see: https://www.mozilla.org/en-US/thunderbird/102.3.0/releasenotes/ isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. usb-and-pxe-installers/usbboot.img: Rebuilt.
Diffstat (limited to 'README.initrd')
-rw-r--r--README.initrd14
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd
index 8b739c9ec..fa16d3f68 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Thu Sep 15 20:01:45 UTC 2022
+Tue Sep 20 22:40:08 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.19.9 Linux kernel using the packages
+upgrading to the generic 5.19.10 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.19.9-x86_64-1.txz
- installpkg kernel-modules-5.19.9-x86_64-1.txz
+ installpkg kernel-generic-5.19.10-x86_64-1.txz
+ installpkg kernel-modules-5.19.10-x86_64-1.txz
installpkg mkinitrd-1.4.11-x86_64-30.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.19.9 -m ext4
+ mkinitrd -c -k 5.19.10 -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.19.9
+Here's another example: Build an initrd image using Linux 5.19.10
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.19.9 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.19.10 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?