summaryrefslogtreecommitdiff
path: root/README.initrd
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2021-03-26 03:07:35 +0000
committerEric Hameleers <alien@slackware.com>2021-03-26 08:59:54 +0100
commitef8da054874c083955348ec5ecfeb571c9a81b7e (patch)
tree9c008c5d9849025d9fa9d400e220d9a9a7b64b6b /README.initrd
parent74147bf26e89436f62ddf9e4390aba27fa6c4581 (diff)
downloadcurrent-ef8da054874c083955348ec5ecfeb571c9a81b7e.tar.gz
Fri Mar 26 03:07:35 UTC 202120210326030735
a/btrfs-progs-5.11.1-x86_64-1.txz: Upgraded. a/dialog-1.3_20210324-x86_64-1.txz: Upgraded. a/kernel-generic-5.10.26-x86_64-1.txz: Upgraded. a/kernel-huge-5.10.26-x86_64-1.txz: Upgraded. a/kernel-modules-5.10.26-x86_64-1.txz: Upgraded. a/openssl-solibs-1.1.1k-x86_64-1.txz: Upgraded. d/kernel-headers-5.10.26-x86-1.txz: Upgraded. d/rust-1.51.0-x86_64-1.txz: Upgraded. e/emacs-27.2-x86_64-1.txz: Upgraded. k/kernel-source-5.10.26-noarch-1.txz: Upgraded. -ADI_AXI_ADC m AD9467 m -> n FONT_TER16x32 n -> y n/openssl-1.1.1k-x86_64-1.txz: Upgraded. This update fixes security issues: Fixed a problem with verifying a certificate chain when using the X509_V_FLAG_X509_STRICT flag. Fixed an issue where an OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. For more information, see: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3450 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3449 (* Security fix *) n/samba-4.14.2-x86_64-1.txz: Upgraded. This is a security release in order to address the following defects: Heap corruption via crafted DN strings. Out of bounds read in AD DC LDAP server. For more information, see: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27840 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20277 (* Security fix *) x/mesa-21.0.1-x86_64-1.txz: Upgraded. isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. testing/packages/linux-5.11.x/kernel-generic-5.11.10-x86_64-1.txz: Upgraded. testing/packages/linux-5.11.x/kernel-headers-5.11.10-x86-1.txz: Upgraded. testing/packages/linux-5.11.x/kernel-huge-5.11.10-x86_64-1.txz: Upgraded. testing/packages/linux-5.11.x/kernel-modules-5.11.10-x86_64-1.txz: Upgraded. testing/packages/linux-5.11.x/kernel-source-5.11.10-noarch-1.txz: 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 fcfa128f..4b541574 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Sat Mar 20 19:23:52 UTC 2021
+Fri Mar 26 01:42:41 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.25 Linux kernel using the packages
+upgrading to the generic 5.10.26 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.25-x86_64-1.txz
- installpkg kernel-modules-5.10.25-x86_64-1.txz
+ installpkg kernel-generic-5.10.26-x86_64-1.txz
+ installpkg kernel-modules-5.10.26-x86_64-1.txz
installpkg mkinitrd-1.4.11-x86_64-19.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.25 -m ext4
+ mkinitrd -c -k 5.10.26 -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.25
+Here's another example: Build an initrd image using Linux 5.10.26
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.10.25 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.10.26 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?