mirror of
git://slackware.nl/current.git
synced 2025-01-03 23:03:22 +01:00
3e486d66d2
Hey folks! Sorry about the delay in getting this batch out but I had other
distractions going on here last week that prevented getting this one wrapped
up. Anyway, probably the highlight of this update set is that we've decided
to abandon the 5.10 LTS kernel in favor of following the latest one. We've
never really had a policy that required LTS in a stable release although that
is how it has been done for years, but based on comments from the Slackware
community it seems like 5.10 LTS isn't getting a lot of love and lacks
hardware support that people need now. Conversely, the reports on 5.12 have
been almost entirely positive, so we're going to provide what we think is the
best available kernel. It's unlikely that we'll see another LTS prior to
release, so the plan for maintenance is to keep following the latest kernels
as needed for security purposes. If that means we have to jump to a new branch
while supporting the stable release, we'll start the kernel out in testing
first until we've had some feedback that it's safe to move it to the patches
directory. Sooner or later we will end up on an LTS kernel again, and at that
point we'll just roll with that one. Feel free to comment (or complain) about
this plan on LQ... I'll be curious to see what people think. Anyway, enjoy!
a/hwdata-0.348-noarch-1.txz: Upgraded.
a/kernel-generic-5.12.9-x86_64-1.txz: Upgraded.
a/kernel-huge-5.12.9-x86_64-1.txz: Upgraded.
a/kernel-modules-5.12.9-x86_64-1.txz: Upgraded.
ap/ispell-3.4.04-x86_64-1.txz: Upgraded.
ap/mpg123-1.28.0-x86_64-1.txz: Upgraded.
ap/slackpkg-15.0.5-noarch-1.txz: Upgraded.
Add "--" option to "command cd" in bash completion file. (akinomyoga)
shell-completions/slackpkg.bash: add "show-changelog".
Import bash-completion file from upstream project.
Added the new-config actions for specific files. (Piter PUNK)
Harden slackpkg with respect to obtaining GPG key. (CRTS)
d/clisp-2.50_20191103_c26de7873-x86_64-5.txz: Rebuilt.
Upgraded to libffcall-2.3.
d/git-2.32.0-x86_64-1.txz: Upgraded.
d/kernel-headers-5.12.9-x86-1.txz: Upgraded.
d/poke-1.3-x86_64-1.txz: Upgraded.
d/vala-0.52.4-x86_64-1.txz: Upgraded.
k/kernel-source-5.12.9-noarch-1.txz: Upgraded.
kde/calligra-3.2.1-x86_64-9.txz: Rebuilt.
Recompiled against poppler-21.06.1.
kde/cantor-21.04.1-x86_64-2.txz: Rebuilt.
Recompiled against poppler-21.06.1.
kde/digikam-7.2.0-x86_64-3.txz: Rebuilt.
Recompiled against imagemagick-7.0.11_14.
kde/kfilemetadata-5.82.0-x86_64-2.txz: Rebuilt.
Recompiled against poppler-21.06.1.
kde/kile-2.9.93-x86_64-9.txz: Rebuilt.
Recompiled against poppler-21.06.1.
kde/kitinerary-21.04.1-x86_64-2.txz: Rebuilt.
Recompiled against poppler-21.06.1.
kde/krita-4.4.3-x86_64-5.txz: Rebuilt.
Recompiled against poppler-21.06.1.
kde/okular-21.04.1-x86_64-2.txz: Rebuilt.
Recompiled against poppler-21.06.1.
l/alsa-lib-1.2.5-x86_64-2.txz: Rebuilt.
Account for unexpected packing of the conf file tarballs. We'll see if this
is enough to make things work well again.
l/at-spi2-core-2.40.2-x86_64-1.txz: Upgraded.
l/dvdauthor-0.7.2-x86_64-5.txz: Rebuilt.
Recompiled against imagemagick-7.0.11_14.
l/libogg-1.3.5-x86_64-1.txz: Upgraded.
l/librsvg-2.50.7-x86_64-1.txz: Upgraded.
l/pipewire-0.3.29-x86_64-1.txz: Upgraded.
l/polkit-0.119-x86_64-1.txz: Upgraded.
This update includes a mitigation for local privilege escalation using
polkit_system_bus_name_get_creds_sync().
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3560
(* Security fix *)
l/poppler-21.06.1-x86_64-1.txz: Upgraded.
Shared library .so-version bump.
l/pycairo-1.20.1-x86_64-1.txz: Upgraded.
l/qca-2.3.3-x86_64-1.txz: Upgraded.
l/vte-0.64.2-x86_64-1.txz: Upgraded.
n/epic5-2.1.5-x86_64-1.txz: Upgraded.
n/httpd-2.4.48-x86_64-1.txz: Upgraded.
This release contains security fixes and improvements.
mod_http2: Fix a potential NULL pointer dereference.
Unexpected <Location> section matching with 'MergeSlashes OFF'.
mod_auth_digest: possible stack overflow by one nul byte while validating
the Digest nonce.
mod_session: Fix possible crash due to NULL pointer dereference, which
could be used to cause a Denial of Service with a malicious backend
server and SessionHeader.
mod_session: Fix possible crash due to NULL pointer dereference, which
could be used to cause a Denial of Service.
mod_proxy_http: Fix possible crash due to NULL pointer dereference, which
could be used to cause a Denial of Service.
mod_proxy_wstunnel, mod_proxy_http: Handle Upgradable protocols end-to-end
negotiation.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-31618
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-30641
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35452
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-26691
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-26690
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13950
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17567
(* Security fix *)
n/libmbim-1.24.8-x86_64-1.txz: Upgraded.
n/libqmi-1.28.6-x86_64-1.txz: Upgraded.
n/nettle-3.7.3-x86_64-1.txz: Upgraded.
n/openldap-2.4.59-x86_64-1.txz: Upgraded.
n/p11-kit-0.24.0-x86_64-1.txz: Upgraded.
n/php-7.4.20-x86_64-1.txz: Upgraded.
n/vsftpd-3.0.4-x86_64-1.txz: Upgraded.
n/whois-5.5.10-x86_64-1.txz: Upgraded.
x/libX11-1.7.2-x86_64-1.txz: Upgraded.
This is a bug fix release, correcting a regression introduced by and
improving the checks from the fix for CVE-2021-31535.
x/libinput-1.18.0-x86_64-1.txz: Upgraded.
x/mesa-21.1.2-x86_64-1.txz: Upgraded.
xap/blueman-2.2.1-x86_64-1.txz: Upgraded.
xap/gnuplot-5.4.2-x86_64-1.txz: Upgraded.
xap/mozilla-thunderbird-78.11.0-x86_64-1.txz: Upgraded.
This release contains security fixes and improvements.
For more information, see:
https://www.mozilla.org/en-US/thunderbird/78.11.0/releasenotes/
https://www.mozilla.org/en-US/security/advisories/mfsa2021-26/
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29964
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29967
(* Security fix *)
xap/pidgin-2.14.5-x86_64-1.txz: Upgraded.
xap/xine-lib-1.2.11-x86_64-6.txz: Rebuilt.
Recompiled against poppler-21.06.1.
extra/bash-completion/bash-completion-2.11-noarch-2.txz: Rebuilt.
Removed the slackpkg completion file.
extra/php8/php8-8.0.7-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
kernels/*: Upgraded.
usb-and-pxe-installers/usbboot.img: Rebuilt.
99 lines
3.5 KiB
Text
99 lines
3.5 KiB
Text
|
|
Slackware initrd mini HOWTO
|
|
by Patrick Volkerding, volkerdi@slackware.com
|
|
Mon Jun 7 05:03:59 UTC 2021
|
|
|
|
This document describes how to create and install an initrd, which may be
|
|
required to use the 4.x kernel. Also see "man mkinitrd".
|
|
|
|
1. What is an initrd?
|
|
2. Why to I need an initrd?
|
|
3. How do I build the initrd?
|
|
4. Now that I've built an initrd, how do I use it?
|
|
|
|
|
|
1. What is an initrd?
|
|
|
|
Initrd stands for "initial ramdisk". An initial ramdisk is a very small
|
|
Linux filesystem that is loaded into RAM and mounted as the kernel boots,
|
|
and before the main root filesystem is mounted.
|
|
|
|
2. Why do I need an initrd?
|
|
|
|
The usual reason to use an initrd is because you need to load kernel
|
|
modules before mounting the root partition. Usually these modules are
|
|
required to support the filesystem used by the root partition (ext3, ext4,
|
|
btrfs, xfs), or perhaps the controller that the hard drive is attached
|
|
to (SCSI, RAID, etc). Essentially, there are so many different options
|
|
available in modern Linux kernels that it isn't practical to try to ship
|
|
many different kernels to try to cover everyone's needs. It's a lot more
|
|
flexible to ship a generic kernel and a set of kernel modules for it.
|
|
|
|
3. How do I build the initrd?
|
|
|
|
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.12.9 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.12.9-x86_64-1.txz
|
|
installpkg kernel-modules-5.12.9-x86_64-1.txz
|
|
installpkg mkinitrd-1.4.11-x86_64-24.txz
|
|
|
|
Change into the /boot directory:
|
|
|
|
cd /boot
|
|
|
|
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.12.9 -m ext4
|
|
|
|
This should do two things. First, it will create a directory
|
|
/boot/initrd-tree containing the initrd's filesystem. Then it will
|
|
create an initrd (/boot/initrd.gz) from this tree. If you wanted to,
|
|
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.12.9
|
|
kernel modules for a system with an ext4 root partition on /dev/sdb3:
|
|
|
|
mkinitrd -c -k 5.12.9 -m ext4 -f ext4 -r /dev/sdb3
|
|
|
|
|
|
4. Now that I've built an initrd, how do I use it?
|
|
|
|
Now that you've got an initrd (/boot/initrd.gz), you'll want to load
|
|
it along with the kernel at boot time. If you use LILO for your boot
|
|
loader you'll need to edit /etc/lilo.conf and add a line to load the
|
|
initrd. Here's an example section of lilo.conf showing how this is
|
|
done:
|
|
|
|
# Linux bootable partition config begins
|
|
image = /boot/vmlinuz-generic
|
|
initrd = /boot/initrd.gz
|
|
root = /dev/sda6
|
|
label = Slackware
|
|
read-only
|
|
# Linux bootable partition config ends
|
|
|
|
The initrd is loaded by the "initrd = /boot/initrd.gz" line.
|
|
Just add the line right below the line for the kernel image you use.
|
|
Save the file, and then run LILO again ('lilo' at the command line).
|
|
You'll need to run lilo every time you edit lilo.conf or rebuild the
|
|
initrd.
|
|
|
|
Other bootloaders such as syslinux also support the use of an initrd.
|
|
See the documentation for those programs for details on using an
|
|
initrd with them.
|
|
|
|
|
|
---------
|
|
|
|
Have fun!
|