summaryrefslogtreecommitdiffstats
path: root/README.initrd
diff options
context:
space:
mode:
author Patrick J Volkerding <volkerdi@slackware.com>2019-07-22 03:05:48 +0000
committer Eric Hameleers <alien@slackware.com>2019-07-22 08:59:46 +0200
commit9f4ecf6a5f87f2f8eb2401c45d1dff7ca806bba5 (patch)
tree4b600cf3316a8824740c8b9c7532c0f99b83a8ea /README.initrd
parent445d52ff429e65a921df7dd9b85e8e2153558fb6 (diff)
downloadcurrent-9f4ecf6a5f87f2f8eb2401c45d1dff7ca806bba5.tar.gz
current-9f4ecf6a5f87f2f8eb2401c45d1dff7ca806bba5.tar.xz
Mon Jul 22 03:05:48 UTC 201920190722030548
l/SDL2_mixer-2.0.4-x86_64-2.txz: Rebuilt. Recompiled with --enable-music-mp3-mad-gpl. Thanks to pomf.
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 4ae24c443..573b0921a 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Sun Jul 14 22:37:57 UTC 2019
+Sun Jul 21 19:43:08 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,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 4.19.59 Linux kernel using the packages
+upgrading to the generic 4.19.60 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-4.19.59-x86_64-1.txz
- installpkg kernel-modules-4.19.59-x86_64-1.txz
+ installpkg kernel-generic-4.19.60-x86_64-1.txz
+ installpkg kernel-modules-4.19.60-x86_64-1.txz
installpkg mkinitrd-1.4.11-x86_64-12.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 4.19.59 -m ext4
+ mkinitrd -c -k 4.19.60 -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 4.19.59
+Here's another example: Build an initrd image using Linux 4.19.60
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 4.19.59 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 4.19.60 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?