summaryrefslogtreecommitdiffstats
path: root/README.initrd
diff options
context:
space:
mode:
author Patrick J Volkerding <volkerdi@slackware.com>2019-07-03 21:02:58 +0000
committer Eric Hameleers <alien@slackware.com>2019-07-04 08:59:47 +0200
commitdb3b9f73c4d039d80bd94aca9c0724804ef203ef (patch)
tree34a73f8cc0573657253d283185189fb6326c7521 /README.initrd
parented5de188b1ed607733e4e70b83631161dc845789 (diff)
downloadcurrent-db3b9f73c4d039d80bd94aca9c0724804ef203ef.tar.gz
current-db3b9f73c4d039d80bd94aca9c0724804ef203ef.tar.xz
Wed Jul 3 21:02:58 UTC 201920190703210258
a/kernel-generic-4.19.57-x86_64-1.txz: Upgraded. a/kernel-huge-4.19.57-x86_64-1.txz: Upgraded. a/kernel-modules-4.19.57-x86_64-1.txz: Upgraded. d/kernel-headers-4.19.57-x86-1.txz: Upgraded. k/kernel-source-4.19.57-noarch-1.txz: Upgraded. l/Mako-1.0.13-x86_64-1.txz: Upgraded. l/SDL2_image-2.0.5-x86_64-1.txz: Upgraded. n/postfix-3.4.6-x86_64-1.txz: Upgraded. xap/blueman-2.0.8-x86_64-2.txz: Rebuilt. Reverted to blueman-2.0.8 as I'm also seeing connection issues here with the newer version. xap/xscreensaver-5.43-x86_64-1.txz: Upgraded. isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. testing/packages/blueman-2.1-x86_64-1.txz: Upgraded. This doesn't seem to be working properly. Any patches are welcome. 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 724b6ad4b..fbfdd6a43 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Wed Jun 26 04:46:32 UTC 2019
+Wed Jul 3 20:35:45 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.56 Linux kernel using the packages
+upgrading to the generic 4.19.57 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.56-x86_64-1.txz
- installpkg kernel-modules-4.19.56-x86_64-1.txz
+ installpkg kernel-generic-4.19.57-x86_64-1.txz
+ installpkg kernel-modules-4.19.57-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.56 -m ext4
+ mkinitrd -c -k 4.19.57 -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.56
+Here's another example: Build an initrd image using Linux 4.19.57
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 4.19.56 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 4.19.57 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?