diff options
| author | Patrick J Volkerding <volkerdi@slackware.com> | 2021-09-22 18:45:12 +0000 |
|---|---|---|
| committer | Eric Hameleers <alien@slackware.com> | 2021-09-23 08:59:56 +0200 |
| commit | d8d00b30a4af22a58f96432bb28400146d76c0f3 (patch) | |
| tree | 4203a527b458ec3696d2e10ca2bfc5356e128768 /README.initrd | |
| parent | 1466aa1f79ae537f4244351e1340e537fc571d31 (diff) | |
| download | current-d8d00b30a4af22a58f96432bb28400146d76c0f3.tar.gz | |
Wed Sep 22 18:45:12 UTC 202120210922184512
a/kernel-generic-5.14.7-x86_64-1.txz: Upgraded.
a/kernel-huge-5.14.7-x86_64-1.txz: Upgraded.
a/kernel-modules-5.14.7-x86_64-1.txz: Upgraded.
ap/sudo-1.9.8p2-x86_64-1.txz: Upgraded.
d/kernel-headers-5.14.7-x86-1.txz: Upgraded.
d/python-setuptools-58.1.0-x86_64-1.txz: Upgraded.
k/kernel-source-5.14.7-noarch-1.txz: Upgraded.
l/neon-0.32.1-x86_64-1.txz: Upgraded.
n/ca-certificates-20210922-noarch-1.txz: Upgraded.
n/curl-7.79.1-x86_64-1.txz: Upgraded.
n/nghttp2-1.45.1-x86_64-1.txz: Upgraded.
x/xterm-369-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 038078dd..699ba71a 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Sat Sep 18 23:59:47 UTC 2021 +Wed Sep 22 18:35:16 UTC 2021 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.14.6 Linux kernel using the packages +upgrading to the generic 5.14.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-5.14.6-x86_64-1.txz - installpkg kernel-modules-5.14.6-x86_64-1.txz + installpkg kernel-generic-5.14.7-x86_64-1.txz + installpkg kernel-modules-5.14.7-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-25.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.14.6 -m ext4 + mkinitrd -c -k 5.14.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 5.14.6 +Here's another example: Build an initrd image using Linux 5.14.7 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.14.6 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.14.7 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |