diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2019-09-16 21:01:05 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2019-09-17 08:59:47 +0200 |
commit | 6d3daa25f6bab4720130798050ca40c9d31cd7b1 (patch) | |
tree | cb0d136d1d962d77e9c907450d6d1272ff4dd523 /README.initrd | |
parent | 975ec5de232ae505fc2082132eeeffbde12f93b7 (diff) | |
download | current-6d3daa25f6bab4720130798050ca40c9d31cd7b1.tar.gz |
Mon Sep 16 21:01:05 UTC 201920190916210105
a/kernel-generic-4.19.73-x86_64-1.txz: Upgraded.
a/kernel-huge-4.19.73-x86_64-1.txz: Upgraded.
a/kernel-modules-4.19.73-x86_64-1.txz: Upgraded.
d/kernel-headers-4.19.73-x86-1.txz: Upgraded.
k/kernel-source-4.19.73-noarch-1.txz: Upgraded.
l/expat-2.2.8-x86_64-1.txz: Upgraded.
Fix heap overflow triggered by XML_GetCurrentLineNumber (or
XML_GetCurrentColumnNumber), and deny internal entities closing the doctype.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15903
(* Security fix *)
x/libwacom-1.1-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 81f85012..dbc6ce21 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Tue Sep 10 21:02:23 UTC 2019 +Mon Sep 16 20:36:09 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 4.19.72 Linux kernel using the packages +upgrading to the generic 4.19.73 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.72-x86_64-1.txz - installpkg kernel-modules-4.19.72-x86_64-1.txz - installpkg mkinitrd-1.4.11-x86_64-12.txz + installpkg kernel-generic-4.19.73-x86_64-1.txz + installpkg kernel-modules-4.19.73-x86_64-1.txz + installpkg mkinitrd-1.4.11-x86_64-13.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.72 -m ext4 + mkinitrd -c -k 4.19.73 -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.72 +Here's another example: Build an initrd image using Linux 4.19.73 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 4.19.72 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 4.19.73 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |