diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2020-03-13 20:15:29 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2020-03-14 08:59:50 +0100 |
commit | 99054d5dbe96b4947262b6b28946c6b11c949e2b (patch) | |
tree | a90dcd314a0d0a94977ddc915689526caeefeb64 /README.initrd | |
parent | 2c7220ae76c6e36f190d5a0591e8412c4b965c34 (diff) | |
download | current-99054d5dbe96b4947262b6b28946c6b11c949e2b.tar.gz |
Fri Mar 13 20:15:29 UTC 202020200313201529
a/cryptsetup-2.3.1-x86_64-1.txz: Upgraded.
a/kernel-firmware-20200309_3b3dd5a-noarch-1.txz: Upgraded.
a/kernel-generic-5.4.25-x86_64-1.txz: Upgraded.
a/kernel-huge-5.4.25-x86_64-1.txz: Upgraded.
a/kernel-modules-5.4.25-x86_64-1.txz: Upgraded.
ap/ghostscript-9.51-x86_64-1.txz: Upgraded.
d/gcc-9.3.0-x86_64-1.txz: Upgraded.
d/gcc-brig-9.3.0-x86_64-1.txz: Upgraded.
d/gcc-g++-9.3.0-x86_64-1.txz: Upgraded.
d/gcc-gdc-9.3.0-x86_64-1.txz: Upgraded.
d/gcc-gfortran-9.3.0-x86_64-1.txz: Upgraded.
d/gcc-gnat-9.3.0-x86_64-1.txz: Upgraded.
d/gcc-go-9.3.0-x86_64-1.txz: Upgraded.
d/gcc-objc-9.3.0-x86_64-1.txz: Upgraded.
d/kernel-headers-5.4.25-x86-1.txz: Upgraded.
d/libtool-2.4.6-x86_64-13.txz: Rebuilt.
Recompiled to update embedded GCC version number.
d/rust-1.42.0-x86_64-1.txz: Upgraded.
d/scons-3.1.2-x86_64-2.txz: Rebuilt.
Drop python2 support and switch to python3.
k/kernel-source-5.4.25-noarch-1.txz: Upgraded.
GCC_VERSION 90200 -> 90300
l/libuv-1.35.0-x86_64-1.txz: Upgraded.
n/NetworkManager-1.22.10-x86_64-1.txz: Upgraded.
n/postfix-3.4.10-x86_64-1.txz: Upgraded.
xap/blueman-2.1.2-x86_64-2.txz: Rebuilt.
This needed a rebuild for glib2-2.64.1. Thanks to Lockywolf.
xap/mozilla-thunderbird-68.6.0-x86_64-1.txz: Upgraded.
This release contains security fixes and improvements.
For more information, see:
https://www.mozilla.org/en-US/thunderbird/68.6.0/releasenotes/
https://www.mozilla.org/en-US/security/advisories/mfsa2020-10/
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6805
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6806
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6807
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6811
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20503
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6812
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6814
(* 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 5f078031..10cb971b 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Fri Mar 6 02:12:38 UTC 2020 +Fri Mar 13 19:43:19 UTC 2020 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 5.4.24 Linux kernel using the packages +upgrading to the generic 5.4.25 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-5.4.24-x86_64-1.txz - installpkg kernel-modules-5.4.24-x86_64-1.txz + installpkg kernel-generic-5.4.25-x86_64-1.txz + installpkg kernel-modules-5.4.25-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-14.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 5.4.24 -m ext4 + mkinitrd -c -k 5.4.25 -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 5.4.24 +Here's another example: Build an initrd image using Linux 5.4.25 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.4.24 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.4.25 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |