summaryrefslogtreecommitdiff
path: root/README.initrd
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2018-11-14 00:00:07 +0000
committerEric Hameleers <alien@slackware.com>2018-11-14 08:59:46 +0100
commite10adef4c2a06f02cd4970f0f6459c27e840f772 (patch)
treea8686f5f485fe72c2cac0bec34516a183e6c6043 /README.initrd
parent2520b90f18ab408818b967f77ef38c1be85de634 (diff)
downloadcurrent-e10adef4c2a06f02cd4970f0f6459c27e840f772.tar.gz
Wed Nov 14 00:00:07 UTC 201820181114000007
a/aaa_terminfo-6.1_20181110-x86_64-1.txz: Upgraded. a/kernel-generic-4.19.2-x86_64-1.txz: Upgraded. a/kernel-huge-4.19.2-x86_64-1.txz: Upgraded. a/kernel-modules-4.19.2-x86_64-1.txz: Upgraded. ap/vim-8.1.0526-x86_64-1.txz: Upgraded. Don't package .desktop files for the base vim package. Move the terminal-based vim.desktop (menu clutter) into the docs directory. d/kernel-headers-4.19.2-x86-1.txz: Upgraded. k/kernel-source-4.19.2-noarch-1.txz: Upgraded. l/librsvg-2.44.9-x86_64-1.txz: Upgraded. l/ncurses-6.1_20181110-x86_64-1.txz: Upgraded. The new kernel fixes the artifact on the virtual console, so the original linux terminal definition has been restored. xap/vim-gvim-8.1.0526-x86_64-1.txz: Upgraded. Let vim install its own icon and gvim.desktop files. Thanks to drumz. Don't include the terminal-based vim.desktop file. isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. usb-and-pxe-installers/usbboot.img: Rebuilt.
Diffstat (limited to 'README.initrd')
-rw-r--r--README.initrd14
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd
index f7d2ac12..8d7b02b7 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Sun Nov 4 19:17:58 UTC 2018
+Tue Nov 13 22:36:16 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.19.1 Linux kernel using the packages
+upgrading to the generic 4.19.2 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.19.1-x86_64-1.txz
- installpkg kernel-modules-4.19.1-x86_64-1.txz
+ installpkg kernel-generic-4.19.2-x86_64-1.txz
+ installpkg kernel-modules-4.19.2-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.19.1 -m ext4
+ mkinitrd -c -k 4.19.2 -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.19.1
+Here's another example: Build an initrd image using Linux 4.19.2
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 4.19.1 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 4.19.2 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?