diff options
| author | Patrick J Volkerding <volkerdi@slackware.com> | 2018-10-20 19:41:13 +0000 |
|---|---|---|
| committer | Eric Hameleers <alien@slackware.com> | 2018-10-21 09:00:29 +0200 |
| commit | e942aa8f7c69e5fa07c32af30ee0903b464087dc (patch) | |
| tree | 383f7df3657158f187e1e1c3806f630bc4e5edd8 /README.initrd | |
| parent | fcbdf0b9ccb30d2f290ae4fa408d342e285becde (diff) | |
| download | current-e942aa8f7c69e5fa07c32af30ee0903b464087dc.tar.gz | |
Sat Oct 20 19:41:13 UTC 201820181020194113
a/kernel-generic-4.14.78-x86_64-1.txz: Upgraded.
a/kernel-huge-4.14.78-x86_64-1.txz: Upgraded.
a/kernel-modules-4.14.78-x86_64-1.txz: Upgraded.
d/Cython-0.29-x86_64-1.txz: Upgraded.
d/kernel-headers-4.14.78-x86-1.txz: Upgraded.
d/meson-0.48.1-x86_64-1.txz: Upgraded.
k/kernel-source-4.14.78-noarch-1.txz: Upgraded.
l/cairo-1.16.0-x86_64-1.txz: Upgraded.
l/python-certifi-2018.10.15-x86_64-1.txz: Upgraded.
l/python-requests-2.20.0-x86_64-1.txz: Upgraded.
l/python-urllib3-1.24-x86_64-1.txz: Upgraded.
x/libwacom-0.31-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 4a915022..4ca133d8 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Fri Oct 19 02:57:34 UTC 2018 +Sat Oct 20 19:21:00 UTC 2018 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 4.14.77 Linux kernel using the packages +upgrading to the generic 4.14.78 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-4.14.77-x86_64-1.txz - installpkg kernel-modules-4.14.77-x86_64-1.txz + installpkg kernel-generic-4.14.78-x86_64-1.txz + installpkg kernel-modules-4.14.78-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-8.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 4.14.77 -m ext4 + mkinitrd -c -k 4.14.78 -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 4.14.77 +Here's another example: Build an initrd image using Linux 4.14.78 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 4.14.77 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 4.14.78 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |