summaryrefslogtreecommitdiff
path: root/README.initrd
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2019-05-17 05:06:06 +0000
committerEric Hameleers <alien@slackware.com>2019-05-17 11:59:47 +0200
commit38b94979d84c5cfc091fd2290c450d05adccb185 (patch)
treee4484b6e5ef11228c1b8776c108e3ff24c8c5f12 /README.initrd
parentd42cbc1006c76db6eb2abf7a54f2ef548ca3886f (diff)
downloadcurrent-38b94979d84c5cfc091fd2290c450d05adccb185.tar.gz
Fri May 17 05:06:06 UTC 201920190517050606
a/kernel-generic-4.19.44-x86_64-1.txz: Upgraded. a/kernel-huge-4.19.44-x86_64-1.txz: Upgraded. a/kernel-modules-4.19.44-x86_64-1.txz: Upgraded. ap/cups-filters-1.23.0-x86_64-1.txz: Upgraded. d/kernel-headers-4.19.44-x86-1.txz: Upgraded. k/kernel-source-4.19.44-noarch-1.txz: Upgraded. l/libsoup-2.66.2-x86_64-1.txz: Upgraded. n/bind-9.14.2-x86_64-1.txz: Upgraded. n/stunnel-5.54-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 8fa1e92f..73e8fabf 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Thu May 16 04:30:32 UTC 2019
+Fri May 17 02:28:34 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.43 Linux kernel using the packages
+upgrading to the generic 4.19.44 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.43-x86_64-1.txz
- installpkg kernel-modules-4.19.43-x86_64-1.txz
+ installpkg kernel-generic-4.19.44-x86_64-1.txz
+ installpkg kernel-modules-4.19.44-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.43 -m ext4
+ mkinitrd -c -k 4.19.44 -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.43
+Here's another example: Build an initrd image using Linux 4.19.44
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 4.19.43 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 4.19.44 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?