diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2018-10-10 23:09:36 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2018-10-11 09:00:31 +0200 |
commit | 7716b728c18deb9a2c780e148050e3683d4d93c1 (patch) | |
tree | 0ed1643262bc41121f3fd1a27da70106a8e9f937 /README.initrd | |
parent | 7a2f2302165a37a7a57a4765375e33881a3697b0 (diff) | |
download | current-7716b728c18deb9a2c780e148050e3683d4d93c1.tar.gz current-7716b728c18deb9a2c780e148050e3683d4d93c1.tar.xz |
Wed Oct 10 23:09:36 UTC 201820181010230936
a/kernel-firmware-20181008_c6b6265-noarch-1.txz: Upgraded.
a/kernel-generic-4.14.75-x86_64-1.txz: Upgraded.
a/kernel-huge-4.14.75-x86_64-1.txz: Upgraded.
a/kernel-modules-4.14.75-x86_64-1.txz: Upgraded.
d/git-2.19.1-x86_64-1.txz: Upgraded.
Submodules' "URL"s come from the untrusted .gitmodules file, but we
blindly gave it to "git clone" to clone submodules when "git clone
--recurse-submodules" was used to clone a project that has such a
submodule. The code has been hardened to reject such malformed URLs
(e.g. one that begins with a dash). Credit for finding and fixing this
vulnerability goes to joernchen and Jeff King, respectively.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17456
(* Security fix *)
d/kernel-headers-4.14.75-x86-1.txz: Upgraded.
d/make-4.2.1-x86_64-4.txz: Rebuilt.
Use a non-blocking read with pselect to avoid hangs.
Thanks to Linux.tar.gz and David Spencer.
d/subversion-1.10.3-x86_64-1.txz: Upgraded.
k/kernel-source-4.14.75-noarch-1.txz: Upgraded.
Config changes since 4.14.74:
FB_HYPERV n -> m
Thanks to walecha.
l/librsvg-2.44.7-x86_64-1.txz: Upgraded.
l/python-pillow-5.3.0-x86_64-1.txz: Upgraded.
n/nghttp2-1.34.0-x86_64-1.txz: Upgraded.
x/libSM-1.2.3-x86_64-1.txz: Upgraded.
x/libX11-1.6.7-x86_64-1.txz: Upgraded.
x/libdrm-2.4.95-x86_64-1.txz: Upgraded.
x/libxcb-1.13.1-x86_64-1.txz: Upgraded.
x/vulkan-sdk-1.1.85.0-x86_64-1.txz: Upgraded.
Thanks to dugan.
xap/gnuplot-5.2.5-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 | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd index 6c703f6da..3b6762b5e 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Thu Oct 4 19:34:15 UTC 2018 +Wed Oct 10 22:11:34 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.14.74 Linux kernel using the packages +upgrading to the generic 4.14.75 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.14.74-x86_64-1.txz - installpkg kernel-modules-4.14.74-x86_64-1.txz + installpkg kernel-generic-4.14.75-x86_64-1.txz + installpkg kernel-modules-4.14.75-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.14.74 -m ext4 + mkinitrd -c -k 4.14.75 -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.14.74 +Here's another example: Build an initrd image using Linux 4.14.75 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 4.14.74 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 4.14.75 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |