summaryrefslogtreecommitdiffstats
path: root/README.initrd
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--README.initrd16
1 files changed, 8 insertions, 8 deletions
diff --git a/README.initrd b/README.initrd
index 0163fe3a9..9360c8ada 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Fri Dec 13 18:46:06 UTC 2019
+Wed Dec 18 20:04:42 UTC 2019
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,16 +33,16 @@ 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.3 Linux kernel using the packages
+upgrading to the generic 5.4.5 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.3-x86_64-1.txz
- installpkg kernel-modules-5.4.3-x86_64-1.txz
- installpkg mkinitrd-1.4.11-x86_64-13.txz
+ installpkg kernel-generic-5.4.5-x86_64-1.txz
+ installpkg kernel-modules-5.4.5-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.3 -m ext4
+ mkinitrd -c -k 5.4.5 -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.3
+Here's another example: Build an initrd image using Linux 5.4.5
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.4.3 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.4.5 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?