summaryrefslogtreecommitdiff
path: root/README.initrd
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2020-01-04 22:21:30 +0000
committerEric Hameleers <alien@slackware.com>2020-01-05 08:59:50 +0100
commit4f5eb0f5505bf4c6361e2b2ebea465b559006a7e (patch)
tree4546c7c6e62cfa608f5ddcd8c19fdb39cc85ebfb /README.initrd
parent1448fe3879c97183a67f452d2d54ffdbabd510dc (diff)
downloadcurrent-4f5eb0f5505bf4c6361e2b2ebea465b559006a7e.tar.gz
Sat Jan 4 22:21:30 UTC 202020200104222130
a/hwdata-0.331-noarch-1.txz: Upgraded. a/kernel-generic-5.4.8-x86_64-1.txz: Upgraded. a/kernel-huge-5.4.8-x86_64-1.txz: Upgraded. a/kernel-modules-5.4.8-x86_64-1.txz: Upgraded. ap/cups-filters-1.26.1-x86_64-1.txz: Upgraded. d/help2man-1.47.12-x86_64-1.txz: Upgraded. d/kernel-headers-5.4.8-x86-1.txz: Upgraded. k/kernel-source-5.4.8-noarch-1.txz: Upgraded. l/glib-networking-2.62.3-x86_64-1.txz: Upgraded. l/python-distro-1.4.0-x86_64-1.txz: Added. This is needed by hplip since Python 3.8 has removed the platform.linux_distribution function. 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 3a57b756..1664115c 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Tue Dec 31 22:26:12 UTC 2019
+Sat Jan 4 21:55:51 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.7 Linux kernel using the packages
+upgrading to the generic 5.4.8 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.7-x86_64-1.txz
- installpkg kernel-modules-5.4.7-x86_64-1.txz
+ installpkg kernel-generic-5.4.8-x86_64-1.txz
+ installpkg kernel-modules-5.4.8-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.7 -m ext4
+ mkinitrd -c -k 5.4.8 -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.7
+Here's another example: Build an initrd image using Linux 5.4.8
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.4.7 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.4.8 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?