summaryrefslogtreecommitdiff
path: root/README.initrd
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2020-04-24 18:54:41 +0000
committerEric Hameleers <alien@slackware.com>2020-04-25 08:59:53 +0200
commitfc0b7eb5cb49c356c545c934504f9e6b6fe37bc6 (patch)
tree8242f15a26950f9f8a98c35d0cc6a758ac5b30e5 /README.initrd
parentbf29f9a870281df42f1c50664c2cabd208d753d0 (diff)
downloadcurrent-fc0b7eb5cb49c356c545c934504f9e6b6fe37bc6.tar.gz
Fri Apr 24 18:54:41 UTC 202020200424185441
a/bash-5.0.017-x86_64-1.txz: Upgraded. a/kernel-generic-5.4.35-x86_64-1.txz: Upgraded. a/kernel-huge-5.4.35-x86_64-1.txz: Upgraded. a/kernel-modules-5.4.35-x86_64-1.txz: Upgraded. a/mcelog-169-x86_64-1.txz: Upgraded. ap/nvme-cli-1.11.1-x86_64-1.txz: Upgraded. ap/powertop-2.12-x86_64-1.txz: Upgraded. ap/tmux-3.1-x86_64-1.txz: Upgraded. d/kernel-headers-5.4.35-x86-1.txz: Upgraded. d/parallel-20200422-noarch-1.txz: Upgraded. d/rust-1.43.0-x86_64-1.txz: Upgraded. d/vala-0.48.5-x86_64-1.txz: Upgraded. k/kernel-source-5.4.35-noarch-1.txz: Upgraded. l/gmm-5.4-noarch-1.txz: Upgraded. l/librsvg-2.48.4-x86_64-1.txz: Upgraded. l/sip-4.19.22-x86_64-1.txz: Upgraded. n/dhcpcd-8.1.9-x86_64-1.txz: Upgraded. x/mesa-20.0.5-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 854bfa4d..6e4219d3 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Wed Apr 22 01:07:25 UTC 2020
+Fri Apr 24 06:20:32 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.34 Linux kernel using the packages
+upgrading to the generic 5.4.35 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.34-x86_64-1.txz
- installpkg kernel-modules-5.4.34-x86_64-1.txz
+ installpkg kernel-generic-5.4.35-x86_64-1.txz
+ installpkg kernel-modules-5.4.35-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.34 -m ext4
+ mkinitrd -c -k 5.4.35 -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.34
+Here's another example: Build an initrd image using Linux 5.4.35
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.4.34 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.4.35 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?