path: root/README.initrd
diff options
author Patrick J Volkerding <>2020-06-10 23:15:33 +0000
committer Eric Hameleers <>2020-06-11 08:59:54 +0200
commit129db239a3b2dccf962f18fe360d07e7279a4146 (patch)
treebed9d14bb8b149a3f4c32dc6e36392d34a758871 /README.initrd
parentb6970e29920f34f56b6bc1026001657790e11702 (diff)
Wed Jun 10 23:15:33 UTC 202020200610231533
a/kernel-generic-5.4.46-x86_64-1.txz: Upgraded. a/kernel-huge-5.4.46-x86_64-1.txz: Upgraded. a/kernel-modules-5.4.46-x86_64-1.txz: Upgraded. d/kernel-headers-5.4.46-x86-1.txz: Upgraded. k/kernel-source-5.4.46-noarch-1.txz: Upgraded. l/QScintilla-2.11.5-x86_64-1.txz: Upgraded. isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. usb-and-pxe-installers/usbboot.img: Rebuilt.
Diffstat (limited to 'README.initrd')
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd
index 1f6db457..24aa7bd0 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding,
-Sun Jun 7 23:16:58 UTC 2020
+Wed Jun 10 22:48:00 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.45 Linux kernel using the packages
+upgrading to the generic 5.4.46 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.45-x86_64-1.txz
- installpkg kernel-modules-5.4.45-x86_64-1.txz
+ installpkg kernel-generic-5.4.46-x86_64-1.txz
+ installpkg kernel-modules-5.4.46-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.45 -m ext4
+ mkinitrd -c -k 5.4.46 -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.45
+Here's another example: Build an initrd image using Linux 5.4.46
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.4.45 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.4.46 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?