diff options
| author |   Patrick J Volkerding <volkerdi@slackware.com> | 2023-07-05 21:02:14 +0000 |
|---|---|---|
| committer |   Eric Hameleers <alien@slackware.com> | 2023-07-05 23:35:07 +0200 |
| commit | 3c177122b7f7e4145b048cc16a7980d8b7e50452 (patch) | |
| tree | 8278455845d068d52f4b89d01bf0934fd6925073 /README.initrd | |
| parent | d877915983f4d4d711abde89feb431691d43f5b2 (diff) | |
| download | current-3c177122b7f7e4145b048cc16a7980d8b7e50452.tar.gz current-3c177122b7f7e4145b048cc16a7980d8b7e50452.tar.xz | |
Wed Jul 5 21:02:14 UTC 202320230705210214
a/kernel-generic-6.1.38-x86_64-1.txz: Upgraded.
a/kernel-huge-6.1.38-x86_64-1.txz: Upgraded.
a/kernel-modules-6.1.38-x86_64-1.txz: Upgraded.
a/upower-1.90.1-x86_64-1.txz: Upgraded.
a/util-linux-2.39.1-x86_64-3.txz: Rebuilt.
Use --disable-libmount-mountfd-support for now to avoid breaking overlayfs.
d/kernel-headers-6.1.38-x86-1.txz: Upgraded.
k/kernel-source-6.1.38-noarch-1.txz: Upgraded.
l/nodejs-20.4.0-x86_64-1.txz: Upgraded.
n/samba-4.18.4-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.initrd | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd index 7a5faec80..a41fdfd5f 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Sat Jul 1 19:11:53 UTC 2023 +Wed Jul 5 20:48:22 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.37 Linux kernel using the packages +upgrading to the generic 6.1.38 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.37-x86_64-1.txz - installpkg kernel-modules-6.1.37-x86_64-1.txz + installpkg kernel-generic-6.1.38-x86_64-1.txz + installpkg kernel-modules-6.1.38-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-32.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.37 -m ext4 + mkinitrd -c -k 6.1.38 -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.37 +Here's another example: Build an initrd image using Linux 6.1.38 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 6.1.37 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 6.1.38 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |