summaryrefslogtreecommitdiff
path: root/README.initrd
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2020-05-07 01:30:11 +0000
committerEric Hameleers <alien@slackware.com>2020-05-07 08:59:50 +0200
commit7f9672ea573b02b2665782f9760d8c38b83c46e9 (patch)
treeab9abfdb667ae37a5cc06c91e2185a4dafc36da2 /README.initrd
parent33be03fb136ca11ba09834a19984c9f956049b6d (diff)
downloadcurrent-7f9672ea573b02b2665782f9760d8c38b83c46e9.tar.gz
Thu May 7 01:30:11 UTC 202020200507013011
a/kernel-generic-5.4.39-x86_64-1.txz: Upgraded. a/kernel-huge-5.4.39-x86_64-1.txz: Upgraded. a/kernel-modules-5.4.39-x86_64-1.txz: Upgraded. d/kernel-headers-5.4.39-x86-1.txz: Upgraded. k/kernel-source-5.4.39-noarch-1.txz: Upgraded. HUGETLBFS n -> y JUMP_LABEL n -> y +CGROUP_HUGETLB n +HUGETLB_PAGE y +STATIC_KEYS_SELFTEST n Thanks to camerabambai. l/libspectre-0.2.9-x86_64-1.txz: Upgraded. l/pygobject3-3.36.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 46ea4ef8..528202c1 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Sun May 3 06:27:35 UTC 2020
+Thu May 7 01:09:38 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.38 Linux kernel using the packages
+upgrading to the generic 5.4.39 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.38-x86_64-1.txz
- installpkg kernel-modules-5.4.38-x86_64-1.txz
+ installpkg kernel-generic-5.4.39-x86_64-1.txz
+ installpkg kernel-modules-5.4.39-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.38 -m ext4
+ mkinitrd -c -k 5.4.39 -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.38
+Here's another example: Build an initrd image using Linux 5.4.39
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.4.38 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.4.39 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?