diff options
| author | Patrick J Volkerding <volkerdi@slackware.com> | 2019-06-18 21:46:31 +0000 |
|---|---|---|
| committer | Eric Hameleers <alien@slackware.com> | 2019-06-19 08:59:48 +0200 |
| commit | eae1dffeec2f8950e5437a3e1c2476fb55183796 (patch) | |
| tree | 0695addb09a2d19246ce4c13ca1aa859ea6bb6b8 /README.initrd | |
| parent | 59d1b9557c6ead2ecf81afed31d24b4ddf184a10 (diff) | |
| download | current-eae1dffeec2f8950e5437a3e1c2476fb55183796.tar.gz | |
Tue Jun 18 21:46:31 UTC 201920190618214631
a/kernel-firmware-20190618_acb56f2-noarch-1.txz: Upgraded.
a/kernel-generic-4.19.52-x86_64-1.txz: Upgraded.
a/kernel-huge-4.19.52-x86_64-1.txz: Upgraded.
a/kernel-modules-4.19.52-x86_64-1.txz: Upgraded.
ap/mariadb-10.3.16-x86_64-1.txz: Upgraded.
ap/nano-4.3-x86_64-1.txz: Upgraded.
d/kernel-headers-4.19.52-x86-1.txz: Upgraded.
d/llvm-8.0.0-x86_64-3.txz: Rebuilt.
Added lld-8.0.0. Thanks to TheRealGrogan.
d/meson-0.51.0-x86_64-1.txz: Upgraded.
d/vala-0.44.5-x86_64-1.txz: Upgraded.
k/kernel-source-4.19.52-noarch-1.txz: Upgraded.
This update fixes "SACK Panic", a remote denial-of-service issue.
For more information, see:
https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-001.md
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11477
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11478
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11479
(* Security fix *)
l/SDL2-2.0.9-x86_64-4.txz: Rebuilt.
Include libSDL2_test.a and libSDL2main.a. Thanks to dugan.
l/gtk+3-3.24.9-x86_64-1.txz: Upgraded.
n/ca-certificates-20190617-noarch-1.txz: Upgraded.
x/encodings-1.0.5-noarch-1.txz: Upgraded.
x/libX11-1.6.8-x86_64-1.txz: Upgraded.
xap/mozilla-firefox-60.7.1esr-x86_64-1.txz: Upgraded.
This release contains a security fix and improvements. The patched flaw is
considered critical, and could be used to run attacker code and install
software, requiring no user interaction beyond normal browsing.
For more information, see:
https://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html
https://www.mozilla.org/en-US/security/advisories/mfsa2019-18/
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11707
(* Security fix *)
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 51a49bbc..b80c189d 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Sun Jun 16 03:06:25 UTC 2019 +Tue Jun 18 16:45:53 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.51 Linux kernel using the packages +upgrading to the generic 4.19.52 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.51-x86_64-1.txz - installpkg kernel-modules-4.19.51-x86_64-1.txz + installpkg kernel-generic-4.19.52-x86_64-1.txz + installpkg kernel-modules-4.19.52-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.51 -m ext4 + mkinitrd -c -k 4.19.52 -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.51 +Here's another example: Build an initrd image using Linux 4.19.52 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 4.19.51 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 4.19.52 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |