diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2019-12-18 20:32:12 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2019-12-19 08:59:49 +0100 |
commit | 4d0d6dac995cb4d7fc582aeae703e81a5cb54efa (patch) | |
tree | 0e773ad2e2097ae8533b2777d45b008305b43164 /README.initrd | |
parent | f36e13b41f026660b357f6885075eb31ae8f2ae1 (diff) | |
download | current-4d0d6dac995cb4d7fc582aeae703e81a5cb54efa.tar.gz |
Wed Dec 18 20:32:12 UTC 201920191218203212
a/kernel-firmware-20191218_c4586ff-noarch-1.txz: Upgraded.
a/kernel-generic-5.4.5-x86_64-1.txz: Upgraded.
a/kernel-huge-5.4.5-x86_64-1.txz: Upgraded.
a/kernel-modules-5.4.5-x86_64-1.txz: Upgraded.
ap/vim-8.2.0019-x86_64-1.txz: Upgraded.
d/kernel-headers-5.4.5-x86-1.txz: Upgraded.
d/scons-3.1.2-x86_64-1.txz: Upgraded.
k/kernel-source-5.4.5-noarch-1.txz: Upgraded.
x/mesa-19.3.1-x86_64-1.txz: Upgraded.
xap/vim-gvim-8.2.0019-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 | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/README.initrd b/README.initrd index 0163fe3a..9360c8ad 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Fri Dec 13 18:46:06 UTC 2019 +Wed Dec 18 20:04:42 UTC 2019 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,16 +33,16 @@ 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.3 Linux kernel using the packages +upgrading to the generic 5.4.5 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.3-x86_64-1.txz - installpkg kernel-modules-5.4.3-x86_64-1.txz - installpkg mkinitrd-1.4.11-x86_64-13.txz + installpkg kernel-generic-5.4.5-x86_64-1.txz + installpkg kernel-modules-5.4.5-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.3 -m ext4 + mkinitrd -c -k 5.4.5 -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.3 +Here's another example: Build an initrd image using Linux 5.4.5 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.4.3 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.4.5 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |