summaryrefslogtreecommitdiffstats
path: root/README.initrd
diff options
context:
space:
mode:
author Patrick J Volkerding <volkerdi@slackware.com>2023-01-19 00:40:12 +0000
committer Eric Hameleers <alien@slackware.com>2023-01-19 02:39:15 +0100
commitf493ddecac957a63e0ffb71febc2fcf454113aa3 (patch)
tree7592c61718b9b1f2d0249fe76bb829815b272b3e /README.initrd
parent9cc1c3b3609f9dadfb87ca32723780a5ba6870dc (diff)
downloadcurrent-f493ddecac957a63e0ffb71febc2fcf454113aa3.tar.gz
current-f493ddecac957a63e0ffb71febc2fcf454113aa3.tar.xz
Thu Jan 19 00:40:12 UTC 202320230119004012
a/kernel-firmware-20230117_7e4f0ed-noarch-1.txz: Upgraded. a/kernel-generic-6.1.7-x86_64-1.txz: Upgraded. a/kernel-huge-6.1.7-x86_64-1.txz: Upgraded. a/kernel-modules-6.1.7-x86_64-1.txz: Upgraded. a/pkgtools-15.1-noarch-3.txz: Rebuilt. installpkg: allow xz to use all the available CPU threads. makepkg: by default, allow xz to determine how many threads to use. However, on 32-bit platforms default to 2 threads since we were using this before. If allowed to decide, xz seems to only want to use a single thread on 32-bit. ap/nano-7.2-x86_64-1.txz: Upgraded. ap/sudo-1.9.12p2-x86_64-1.txz: Upgraded. This update fixes a flaw in sudo's -e option (aka sudoedit) that could allow a malicious user with sudoedit privileges to edit arbitrary files. For more information, see: https://www.cve.org/CVERecord?id=CVE-2023-22809 (* Security fix *) d/kernel-headers-6.1.7-x86-1.txz: Upgraded. k/kernel-source-6.1.7-noarch-1.txz: Upgraded. kde/plasma-wayland-protocols-1.10-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 dc902c17f..07d2938be 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Sun Jan 15 00:50:17 UTC 2023
+Thu Jan 19 00:28:59 UTC 2023
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 6.1.6 Linux kernel using the packages
+upgrading to the generic 6.1.7 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-6.1.6-x86_64-1.txz
- installpkg kernel-modules-6.1.6-x86_64-1.txz
+ installpkg kernel-generic-6.1.7-x86_64-1.txz
+ installpkg kernel-modules-6.1.7-x86_64-1.txz
installpkg mkinitrd-1.4.11-x86_64-30.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 6.1.6 -m ext4
+ mkinitrd -c -k 6.1.7 -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 6.1.6
+Here's another example: Build an initrd image using Linux 6.1.7
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 6.1.6 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 6.1.7 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?