summaryrefslogtreecommitdiffstats
path: root/README.initrd
diff options
context:
space:
mode:
author Patrick J Volkerding <volkerdi@slackware.com>2023-02-01 22:27:31 +0000
committer Eric Hameleers <alien@slackware.com>2023-02-02 00:40:26 +0100
commita130ab0fdf8914fd1036e10345f118c3838a0472 (patch)
tree98f8804aba77b4f3f1255f638c513104327eab44 /README.initrd
parent45d1307faeb72d3fefce6446c314c4b0d0d3a98a (diff)
downloadcurrent-a130ab0fdf8914fd1036e10345f118c3838a0472.tar.gz
current-a130ab0fdf8914fd1036e10345f118c3838a0472.tar.xz
Wed Feb 1 22:27:31 UTC 202320230201222731
a/kernel-firmware-20230125_5c11a37-noarch-1.txz: Upgraded. a/kernel-generic-6.1.9-x86_64-1.txz: Upgraded. a/kernel-huge-6.1.9-x86_64-1.txz: Upgraded. a/kernel-modules-6.1.9-x86_64-1.txz: Upgraded. d/kernel-headers-6.1.9-x86-1.txz: Upgraded. k/kernel-source-6.1.9-noarch-1.txz: Upgraded. l/apr-1.7.2-x86_64-1.txz: Upgraded. This update fixes security issues: Integer Overflow or Wraparound vulnerability in apr_encode functions of Apache Portable Runtime (APR) allows an attacker to write beyond bounds of a buffer. (CVE-2022-24963) Restore fix for out-of-bounds array dereference in apr_time_exp*() functions. (This issue was addressed as CVE-2017-12613 in APR 1.6.3 and later 1.6.x releases, but was missing in 1.7.0.) (CVE-2021-35940) For more information, see: https://www.cve.org/CVERecord?id=CVE-2022-24963 https://www.cve.org/CVERecord?id=CVE-2021-35940 https://www.cve.org/CVERecord?id=CVE-2017-12613 (* Security fix *) l/apr-util-1.6.3-x86_64-1.txz: Upgraded. This update fixes a security issue: Integer Overflow or Wraparound vulnerability in apr_base64 functions of Apache Portable Runtime Utility (APR-util) allows an attacker to write beyond bounds of a buffer. (CVE-2022-25147) For more information, see: https://www.cve.org/CVERecord?id=CVE-2022-25147 (* Security fix *) l/libhandy-1.8.1-x86_64-1.txz: Upgraded. l/libjpeg-turbo-2.1.5-x86_64-1.txz: Upgraded. xap/mozilla-thunderbird-102.7.1-x86_64-1.txz: Upgraded. This release contains security fixes and improvements. For more information, see: https://www.mozilla.org/en-US/thunderbird/102.7.1/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2023-04/ https://www.cve.org/CVERecord?id=CVE-2023-0430 (* Security fix *) 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 73b64d156..0182cb6bf 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Tue Jan 24 20:16:35 UTC 2023
+Wed Feb 1 22:16:07 UTC 2023
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 6.1.8 Linux kernel using the packages
+upgrading to the generic 6.1.9 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-6.1.8-x86_64-1.txz
- installpkg kernel-modules-6.1.8-x86_64-1.txz
+ installpkg kernel-generic-6.1.9-x86_64-1.txz
+ installpkg kernel-modules-6.1.9-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 6.1.8 -m ext4
+ mkinitrd -c -k 6.1.9 -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 6.1.8
+Here's another example: Build an initrd image using Linux 6.1.9
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 6.1.8 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 6.1.9 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?