summaryrefslogtreecommitdiffstats
path: root/README.initrd
diff options
context:
space:
mode:
author Patrick J Volkerding <volkerdi@slackware.com>2021-01-12 22:20:40 +0000
committer Eric Hameleers <alien@slackware.com>2021-01-13 08:59:49 +0100
commit4e75b0d129720e16c3e34ab1edce6a9597e34b10 (patch)
tree4a0d49c8de52c17458d563f9dce0510976cfe3a4 /README.initrd
parent33dd836e5141064180d377f39344090735772cde (diff)
downloadcurrent-4e75b0d129720e16c3e34ab1edce6a9597e34b10.tar.gz
current-4e75b0d129720e16c3e34ab1edce6a9597e34b10.tar.xz
Tue Jan 12 22:20:40 UTC 202120210112222040
a/kernel-generic-5.10.7-x86_64-1.txz: Upgraded. a/kernel-huge-5.10.7-x86_64-1.txz: Upgraded. a/kernel-modules-5.10.7-x86_64-1.txz: Upgraded. a/libblockdev-2.25-x86_64-1.txz: Upgraded. ap/sudo-1.9.5p1-x86_64-1.txz: Upgraded. Fixed a regression introduced in sudo 1.9.5 where the editor run by sudoedit was set-user-ID root unless SELinux RBAC was in use. The editor is now run with the user's real and effective user-IDs. d/autoconf-2.69-noarch-2.txz: Rebuilt. We're seeing failures using autoconf-2.70 with some packages that use autoreconf. It looks like most distributions have not moved on to autoconf-2.70, and probably we shouldn't either until the next release cycle. Thanks to nobodino. d/kernel-headers-5.10.7-x86-1.txz: Upgraded. e/emacs-27.1-x86_64-2.txz: Rebuilt. Increase SYSTEM_PURESIZE_EXTRA to 100000 to avoid overflows. Nobody should be too concerned about adding 97K to emacs' memory footprint given the amount of memory available on modern machines. Thanks to Jefferson for the bug report. k/kernel-source-5.10.7-noarch-1.txz: Upgraded. l/libclc-11.0.1-x86_64-1.txz: Upgraded. Thanks to USUARIONUEVO. l/python-pygments-2.7.4-x86_64-1.txz: Upgraded. n/gnupg2-2.2.27-x86_64-1.txz: Upgraded. n/socat-1.7.4.1-x86_64-1.txz: Upgraded. x/libdrm-2.4.104-x86_64-1.txz: Upgraded. x/libevdev-1.10.1-x86_64-1.txz: Upgraded. x/vulkan-sdk-1.2.141.0-x86_64-2.txz: Rebuilt. Install additional Vulkan-ValidationLayers-sdk header files. Thanks to walecha. xap/mozilla-thunderbird-78.6.1-x86_64-1.txz: Upgraded. This release contains security fixes and improvements. For more information, see: https://www.mozilla.org/en-US/thunderbird/78.6.1/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2021-02/ 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.initrd14
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd
index d0c7d97c2..be298563d 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Sat Jan 9 20:36:18 UTC 2021
+Tue Jan 12 22:09:57 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.6 Linux kernel using the packages
+upgrading to the generic 5.10.7 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.6-x86_64-1.txz
- installpkg kernel-modules-5.10.6-x86_64-1.txz
+ installpkg kernel-generic-5.10.7-x86_64-1.txz
+ installpkg kernel-modules-5.10.7-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.6 -m ext4
+ mkinitrd -c -k 5.10.7 -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.6
+Here's another example: Build an initrd image using Linux 5.10.7
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.10.6 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.10.7 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?