summaryrefslogtreecommitdiff
path: root/README.initrd
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2019-05-16 04:55:49 +0000
committerEric Hameleers <alien@slackware.com>2019-05-16 17:59:33 +0200
commitd42cbc1006c76db6eb2abf7a54f2ef548ca3886f (patch)
treea25b0532e60ce0fd071e224616e33b70f951762b /README.initrd
parentd42614785a6e27f06dfa601f5a07fa28a5c23b16 (diff)
downloadcurrent-d42cbc1006c76db6eb2abf7a54f2ef548ca3886f.tar.gz
Thu May 16 04:55:49 UTC 201920190516045549
a/kernel-firmware-20190514_711d329-noarch-1.txz: Upgraded. a/kernel-generic-4.19.43-x86_64-1.txz: Upgraded. a/kernel-huge-4.19.43-x86_64-1.txz: Upgraded. a/kernel-modules-4.19.43-x86_64-1.txz: Upgraded. ap/hplip-3.19.5-x86_64-1.txz: Upgraded. ap/mariadb-10.3.15-x86_64-1.txz: Upgraded. This update fixes denial-of-service security issues. For more information, see: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2614 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2627 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2628 (* Security fix *) d/cmake-3.14.4-x86_64-1.txz: Upgraded. d/gcc-9.1.0-x86_64-5.txz: Rebuilt. Rebuilt with --enable-clocale=gnu. This is recommended by Linux From Scratch, and while it doesn't seem to fix the issue with kernel compiles failing with some locales, it probably doesn't hurt. d/gcc-brig-9.1.0-x86_64-5.txz: Rebuilt. d/gcc-g++-9.1.0-x86_64-5.txz: Rebuilt. Applied patch: PR libstdc++/90397 fix std::variant friend declaration This fixes problems compiling programs that use std::variant with clang. Thanks to orbea. d/gcc-gdc-9.1.0-x86_64-5.txz: Rebuilt. d/gcc-gfortran-9.1.0-x86_64-5.txz: Rebuilt. d/gcc-gnat-9.1.0-x86_64-5.txz: Rebuilt. d/gcc-go-9.1.0-x86_64-5.txz: Rebuilt. d/gcc-objc-9.1.0-x86_64-5.txz: Rebuilt. d/kernel-headers-4.19.43-x86-1.txz: Upgraded. d/rust-1.34.2-x86_64-1.txz: Upgraded. k/kernel-source-4.19.43-noarch-1.txz: Upgraded. l/librsvg-2.44.14-x86_64-1.txz: Upgraded. n/samba-4.10.3-x86_64-1.txz: Upgraded. This is a security release in order to address the following defect: The checksum validation in the S4U2Self handler in the embedded Heimdal KDC did not first confirm that the checksum was keyed, allowing replacement of the requested target (client) principal. For more information, see: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16860 (* Security fix *) x/xterm-345-x86_64-1.txz: Upgraded. xap/rdesktop-1.8.5-x86_64-1.txz: Upgraded. This update fixes security issues: Add bounds checking to protocol handling in order to fix many security problems when communicating with a malicious server. (* Security fix *) 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 c5e7201e..8fa1e92f 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Fri May 10 23:50:27 UTC 2019
+Thu May 16 04:30:32 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,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.42 Linux kernel using the packages
+upgrading to the generic 4.19.43 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.42-x86_64-1.txz
- installpkg kernel-modules-4.19.42-x86_64-1.txz
+ installpkg kernel-generic-4.19.43-x86_64-1.txz
+ installpkg kernel-modules-4.19.43-x86_64-1.txz
installpkg mkinitrd-1.4.11-x86_64-12.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.42 -m ext4
+ mkinitrd -c -k 4.19.43 -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.42
+Here's another example: Build an initrd image using Linux 4.19.43
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 4.19.42 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 4.19.43 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?