summaryrefslogtreecommitdiffstats
path: root/README.initrd
diff options
context:
space:
mode:
author Patrick J Volkerding <volkerdi@slackware.com>2020-07-01 19:15:58 +0000
committer Eric Hameleers <alien@slackware.com>2020-07-02 08:59:52 +0200
commitd2a3990477a6cf0d8fbcf333bb6041ddaf30db3d (patch)
treeacac534c9e44da85c463084a35938261c5317e80 /README.initrd
parentdba2771e932227541afc45ae9b231c132c349508 (diff)
downloadcurrent-d2a3990477a6cf0d8fbcf333bb6041ddaf30db3d.tar.gz
current-d2a3990477a6cf0d8fbcf333bb6041ddaf30db3d.tar.xz
Wed Jul 1 19:15:58 UTC 202020200701191558
a/kernel-generic-5.4.50-x86_64-1.txz: Upgraded. a/kernel-huge-5.4.50-x86_64-1.txz: Upgraded. a/kernel-modules-5.4.50-x86_64-1.txz: Upgraded. d/kernel-headers-5.4.50-x86-1.txz: Upgraded. k/kernel-source-5.4.50-noarch-1.txz: Upgraded. l/netpbm-10.91.00-x86_64-1.txz: Upgraded. l/python-pillow-7.2.0-x86_64-1.txz: Upgraded. n/curl-7.71.1-x86_64-1.txz: Upgraded. 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 7f32ea46..45bac3a9 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Thu Jun 25 18:02:37 UTC 2020
+Wed Jul 1 19:01:18 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.49 Linux kernel using the packages
+upgrading to the generic 5.4.50 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.49-x86_64-1.txz
- installpkg kernel-modules-5.4.49-x86_64-1.txz
+ installpkg kernel-generic-5.4.50-x86_64-1.txz
+ installpkg kernel-modules-5.4.50-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.49 -m ext4
+ mkinitrd -c -k 5.4.50 -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.49
+Here's another example: Build an initrd image using Linux 5.4.50
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.4.49 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.4.50 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?