diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2022-10-24 18:57:53 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2022-10-25 07:00:17 +0200 |
commit | 1214d3810791ea9561cb7816e030604bf67baed5 (patch) | |
tree | e8fdf7d9f8bacb77eff3f47e22dfea15b93d672d /README.initrd | |
parent | af2cb09097c3e167bbd06fbe18d0df9489f36f82 (diff) | |
download | current-1214d3810791ea9561cb7816e030604bf67baed5.tar.gz current-1214d3810791ea9561cb7816e030604bf67baed5.tar.xz |
Mon Oct 24 18:57:53 UTC 202220221024185753
a/kernel-firmware-20221017_48407ff-noarch-1.txz: Upgraded.
a/kernel-generic-5.19.17-x86_64-1.txz: Upgraded.
a/kernel-huge-5.19.17-x86_64-1.txz: Upgraded.
a/kernel-modules-5.19.17-x86_64-1.txz: Upgraded.
ap/sudo-1.9.12-x86_64-1.txz: Upgraded.
d/ccache-4.7.1-x86_64-1.txz: Upgraded.
d/kernel-headers-5.19.17-x86-1.txz: Upgraded.
k/kernel-source-5.19.17-noarch-1.txz: Upgraded.
l/libffi-3.4.4-x86_64-1.txz: Upgraded.
l/libidn2-2.3.4-x86_64-1.txz: Upgraded.
x/xterm-375-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 c5fec2abc..7c1306c81 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Sat Oct 15 20:17:47 UTC 2022 +Mon Oct 24 18:47:20 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.19.16 Linux kernel using the packages +upgrading to the generic 5.19.17 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.19.16-x86_64-1.txz - installpkg kernel-modules-5.19.16-x86_64-1.txz + installpkg kernel-generic-5.19.17-x86_64-1.txz + installpkg kernel-modules-5.19.17-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.19.16 -m ext4 + mkinitrd -c -k 5.19.17 -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.19.16 +Here's another example: Build an initrd image using Linux 5.19.17 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.19.16 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.19.17 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |