diff options
| author | Patrick J Volkerding <volkerdi@slackware.com> | 2020-02-01 22:45:14 +0000 |
|---|---|---|
| committer | Eric Hameleers <alien@slackware.com> | 2020-02-02 08:59:50 +0100 |
| commit | 60e10a77d877df3139154896131eb50e5f6b1a61 (patch) | |
| tree | ec2c4a4a19682b885af55eaca176de2b9c94b392 /README.initrd | |
| parent | 4e955dc4b6fff43956d47c0286bb698e03f14b11 (diff) | |
| download | current-60e10a77d877df3139154896131eb50e5f6b1a61.tar.gz | |
Sat Feb 1 22:45:14 UTC 202020200201224514
a/inotify-tools-3.20.2.1-x86_64-1.txz: Upgraded.
a/kernel-generic-5.4.17-x86_64-1.txz: Upgraded.
a/kernel-huge-5.4.17-x86_64-1.txz: Upgraded.
a/kernel-modules-5.4.17-x86_64-1.txz: Upgraded.
d/kernel-headers-5.4.17-x86-1.txz: Upgraded.
k/kernel-source-5.4.17-noarch-1.txz: Upgraded.
l/sip-4.19.21-x86_64-1.txz: Upgraded.
x/xkeyboard-config-2.29-noarch-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 4386e4ed..098765ab 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Thu Jan 30 02:08:35 UTC 2020 +Sat Feb 1 21:59:45 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.16 Linux kernel using the packages +upgrading to the generic 5.4.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.4.16-x86_64-1.txz - installpkg kernel-modules-5.4.16-x86_64-1.txz + installpkg kernel-generic-5.4.17-x86_64-1.txz + installpkg kernel-modules-5.4.17-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.16 -m ext4 + mkinitrd -c -k 5.4.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.4.16 +Here's another example: Build an initrd image using Linux 5.4.17 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.4.16 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.4.17 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |