diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2020-03-22 01:55:55 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2020-03-22 08:59:48 +0100 |
commit | 16310a19148f787e420b0281f288ba8b9dc5cd4d (patch) | |
tree | 7825df453b507506f9aa012ad68a9f222c3cc97b /README.initrd | |
parent | 4e5b493e88d62f5ba0a4a4b54fdbdbdbea69d6b2 (diff) | |
download | current-16310a19148f787e420b0281f288ba8b9dc5cd4d.tar.gz |
Sun Mar 22 01:55:55 UTC 202020200322015555
a/kernel-generic-5.4.27-x86_64-1.txz: Upgraded.
a/kernel-huge-5.4.27-x86_64-1.txz: Upgraded.
a/kernel-modules-5.4.27-x86_64-1.txz: Upgraded.
a/tcsh-6.22.02-x86_64-3.txz: Rebuilt.
Actually apply the shell history patch this time. Thanks to jmccue.
ap/cups-filters-1.27.3-x86_64-1.txz: Upgraded.
d/automake-1.16.2-noarch-1.txz: Upgraded.
d/kernel-headers-5.4.27-x86-1.txz: Upgraded.
d/parallel-20200322-noarch-1.txz: Upgraded.
k/kernel-source-5.4.27-noarch-1.txz: Upgraded.
l/gmime-3.2.7-x86_64-1.txz: Upgraded.
l/pangomm-2.42.1-x86_64-1.txz: Upgraded.
n/gnupg2-2.2.20-x86_64-1.txz: Upgraded.
xap/xaos-3.7-x86_64-1.txz: Upgraded.
xap/xscreensaver-5.44-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
kernels/*: Upgraded.
testing/packages/PAM/xscreensaver-5.44-x86_64-1_pam.txz: 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 10cb971b..fe526548 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Fri Mar 13 19:43:19 UTC 2020 +Sun Mar 22 00:45:37 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.25 Linux kernel using the packages +upgrading to the generic 5.4.27 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.25-x86_64-1.txz - installpkg kernel-modules-5.4.25-x86_64-1.txz + installpkg kernel-generic-5.4.27-x86_64-1.txz + installpkg kernel-modules-5.4.27-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.25 -m ext4 + mkinitrd -c -k 5.4.27 -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.25 +Here's another example: Build an initrd image using Linux 5.4.27 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.4.25 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.4.27 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |