From aafeea9fc46e31851c058896f86d9d5c88881dd8 Mon Sep 17 00:00:00 2001 From: Patrick J Volkerding Date: Mon, 13 Apr 2020 22:16:49 +0000 Subject: Mon Apr 13 22:16:49 UTC 2020 a/kernel-firmware-20200413_64dba0f-noarch-1.txz: Upgraded. a/kernel-generic-5.4.32-x86_64-1.txz: Upgraded. a/kernel-huge-5.4.32-x86_64-1.txz: Upgraded. a/kernel-modules-5.4.32-x86_64-1.txz: Upgraded. d/doxygen-1.8.18-x86_64-1.txz: Upgraded. d/kernel-headers-5.4.32-x86-1.txz: Upgraded. k/kernel-source-5.4.32-noarch-1.txz: Upgraded. n/dhcpcd-8.1.8-x86_64-1.txz: Upgraded. x/libvdpau-1.4-x86_64-1.txz: Upgraded. isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. usb-and-pxe-installers/usbboot.img: Rebuilt. --- README.initrd | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'README.initrd') diff --git a/README.initrd b/README.initrd index 9590e49d7..48209b378 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Thu Apr 9 00:31:08 UTC 2020 +Mon Apr 13 21:54:36 UTC 2020 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.4.31 Linux kernel using the packages +upgrading to the generic 5.4.32 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.4.31-x86_64-1.txz - installpkg kernel-modules-5.4.31-x86_64-1.txz + installpkg kernel-generic-5.4.32-x86_64-1.txz + installpkg kernel-modules-5.4.32-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-14.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.4.31 -m ext4 + mkinitrd -c -k 5.4.32 -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.4.31 +Here's another example: Build an initrd image using Linux 5.4.32 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.4.31 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.4.32 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? -- cgit v1.2.3