From 27a992f52591e89cd95ec0515dea6755aae83227 Mon Sep 17 00:00:00 2001 From: Patrick J Volkerding Date: Sat, 5 Sep 2020 19:27:47 +0000 Subject: Sat Sep 5 19:27:47 UTC 2020 a/kernel-generic-5.4.63-x86_64-1.txz: Upgraded. a/kernel-huge-5.4.63-x86_64-1.txz: Upgraded. a/kernel-modules-5.4.63-x86_64-1.txz: Upgraded. a/xfsprogs-5.8.0-x86_64-1.txz: Upgraded. d/kernel-headers-5.4.63-x86-1.txz: Upgraded. d/python-setuptools-50.3.0-x86_64-1.txz: Upgraded. d/vala-0.48.10-x86_64-1.txz: Upgraded. k/kernel-source-5.4.63-noarch-1.txz: Upgraded. l/at-spi2-core-2.36.1-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 23811726..a54dc827 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Thu Sep 3 19:42:49 UTC 2020 +Sat Sep 5 19:17:39 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.62 Linux kernel using the packages +upgrading to the generic 5.4.63 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.62-x86_64-1.txz - installpkg kernel-modules-5.4.62-x86_64-1.txz + installpkg kernel-generic-5.4.63-x86_64-1.txz + installpkg kernel-modules-5.4.63-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-15.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.62 -m ext4 + mkinitrd -c -k 5.4.63 -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.62 +Here's another example: Build an initrd image using Linux 5.4.63 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.4.62 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.4.63 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? -- cgit v1.2.3