diff options
| author |   Patrick J Volkerding <volkerdi@slackware.com> | 2022-07-24 22:00:30 +0000 |
|---|---|---|
| committer |   Eric Hameleers <alien@slackware.com> | 2022-07-25 07:00:13 +0200 |
| commit | a2e14bcd878ba924f378d9f62c2ab83245313717 (patch) | |
| tree | 3c1958f6766755eec8ed2ce3e90777378e9174f6 /README.initrd | |
| parent | b805df1ad4897b02d6f18a982a6e3fd48ce6eb9f (diff) | |
| download | current-a2e14bcd878ba924f378d9f62c2ab83245313717.tar.gz current-a2e14bcd878ba924f378d9f62c2ab83245313717.tar.xz | |
Sun Jul 24 22:00:30 UTC 202220220724220030
a/kernel-generic-5.18.14-x86_64-1.txz: Upgraded.
a/kernel-huge-5.18.14-x86_64-1.txz: Upgraded.
a/kernel-modules-5.18.14-x86_64-1.txz: Upgraded.
d/kernel-headers-5.18.14-x86-1.txz: Upgraded.
d/parallel-20220722-noarch-1.txz: Upgraded.
k/kernel-source-5.18.14-noarch-1.txz: Upgraded.
+CC_HAS_RETURN_THUNK y
+CPU_IBPB_ENTRY y
+CPU_IBRS_ENTRY y
+CPU_UNRET_ENTRY y
+RETHUNK y
+SPECULATION_MITIGATIONS y
isolinux/initrd.img: Rebuilt.
kernels/*: Upgraded.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Diffstat (limited to 'README.initrd')
| -rw-r--r-- | README.initrd | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd index e317e3a00..b07a54f1a 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Fri Jul 22 18:22:32 UTC 2022 +Sun Jul 24 21:49:02 UTC 2022 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.18.13 Linux kernel using the packages +upgrading to the generic 5.18.14 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.18.13-x86_64-1.txz - installpkg kernel-modules-5.18.13-x86_64-1.txz + installpkg kernel-generic-5.18.14-x86_64-1.txz + installpkg kernel-modules-5.18.14-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 5.18.13 -m ext4 + mkinitrd -c -k 5.18.14 -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.18.13 +Here's another example: Build an initrd image using Linux 5.18.14 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.18.13 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.18.14 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |