diff options
| author | Patrick J Volkerding <volkerdi@slackware.com> | 2020-04-17 21:38:36 +0000 |
|---|---|---|
| committer | Eric Hameleers <alien@slackware.com> | 2020-04-18 08:59:53 +0200 |
| commit | c55b2370e968607051b83e94539833260bd4e084 (patch) | |
| tree | d5a5c3a3e84feab3d89bc091b341a6e6f5efe43c /README.initrd | |
| parent | 3021bc8054ca3531d5e7f2d0692b99cd16167930 (diff) | |
| download | current-c55b2370e968607051b83e94539833260bd4e084.tar.gz | |
Fri Apr 17 21:38:36 UTC 202020200417213836
a/kernel-firmware-20200417_6314fa0-noarch-1.txz: Upgraded.
a/kernel-generic-5.4.33-x86_64-1.txz: Upgraded.
a/kernel-huge-5.4.33-x86_64-1.txz: Upgraded.
a/kernel-modules-5.4.33-x86_64-1.txz: Upgraded.
d/kernel-headers-5.4.33-x86-1.txz: Upgraded.
k/kernel-source-5.4.33-noarch-1.txz: Upgraded.
l/adwaita-icon-theme-3.36.1-noarch-1.txz: Upgraded.
l/libuv-1.36.0-x86_64-2.txz: Rebuilt.
Revert commits that cause BIND to crash. Thanks to Markus Wiesner.
l/wavpack-5.3.0-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 48209b37..9b1d8568 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Mon Apr 13 21:54:36 UTC 2020 +Fri Apr 17 21:14:20 UTC 2020 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.4.32 Linux kernel using the packages +upgrading to the generic 5.4.33 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.4.32-x86_64-1.txz - installpkg kernel-modules-5.4.32-x86_64-1.txz + installpkg kernel-generic-5.4.33-x86_64-1.txz + installpkg kernel-modules-5.4.33-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-14.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.4.32 -m ext4 + mkinitrd -c -k 5.4.33 -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.4.32 +Here's another example: Build an initrd image using Linux 5.4.33 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.4.32 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.4.33 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |