summaryrefslogtreecommitdiffstats
path: root/README.initrd
diff options
context:
space:
mode:
author Patrick J Volkerding <volkerdi@slackware.com>2020-12-03 23:52:38 +0000
committer Eric Hameleers <alien@slackware.com>2020-12-04 08:59:50 +0100
commit3f5ef65db85ac03e7cd56925ae276e9317ec01e5 (patch)
tree98a382f5c2abe8c54548fe8f5a5efc2b682993c0 /README.initrd
parentca24bdf2171b8756a322c99932f890bd69bcd86c (diff)
downloadcurrent-3f5ef65db85ac03e7cd56925ae276e9317ec01e5.tar.gz
current-3f5ef65db85ac03e7cd56925ae276e9317ec01e5.tar.xz
Thu Dec 3 23:52:38 UTC 202020201203235238
a/kernel-generic-5.4.81-x86_64-1.txz: Upgraded. a/kernel-huge-5.4.81-x86_64-1.txz: Upgraded. a/kernel-modules-5.4.81-x86_64-1.txz: Upgraded. ap/cups-filters-1.28.6-x86_64-1.txz: Upgraded. ap/nano-5.4-x86_64-1.txz: Upgraded. d/binutils-2.35.1-x86_64-1.txz: Upgraded. d/gcc-10.2.0-x86_64-2.txz: Rebuilt. These are the same GCC packages that were previously in /testing. d/gcc-brig-10.2.0-x86_64-2.txz: Rebuilt. d/gcc-g++-10.2.0-x86_64-2.txz: Rebuilt. d/gcc-gdc-10.2.0-x86_64-2.txz: Rebuilt. Shared library .so-version bump. d/gcc-gfortran-10.2.0-x86_64-2.txz: Rebuilt. d/gcc-gnat-10.2.0-x86_64-2.txz: Rebuilt. d/gcc-go-10.2.0-x86_64-2.txz: Rebuilt. Shared library .so-version bump. d/gcc-objc-10.2.0-x86_64-2.txz: Rebuilt. d/kernel-headers-5.4.81-x86-1.txz: Upgraded. d/libtool-2.4.6-x86_64-14.txz: Rebuilt. Recompiled to update embedded GCC version number. d/mercurial-5.6.1-x86_64-1.txz: Upgraded. d/oprofile-1.4.0-x86_64-2.txz: Rebuilt. d/python-pip-20.3.1-x86_64-1.txz: Upgraded. k/kernel-source-5.4.81-noarch-1.txz: Upgraded. GCC_VERSION 90300 -> 100200 l/PyQt5-5.15.2-x86_64-1.txz: Upgraded. l/glibmm-2.64.5-x86_64-1.txz: Upgraded. x/mesa-20.3.0-x86_64-1.txz: Upgraded. xap/geeqie-1.6-x86_64-1.txz: Upgraded. xap/mozilla-thunderbird-78.5.1-x86_64-1.txz: Upgraded. This release contains security fixes and improvements. For more information, see: https://www.mozilla.org/en-US/thunderbird/78.5.1/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2020-53/ https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26970 (* Security fix *) isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. usb-and-pxe-installers/usbboot.img: Rebuilt.
Diffstat (limited to 'README.initrd')
-rw-r--r--README.initrd14
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd
index 03df12a7c..420228434 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Wed Nov 25 01:01:47 UTC 2020
+Thu Dec 3 23:39:05 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.80 Linux kernel using the packages
+upgrading to the generic 5.4.81 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.80-x86_64-1.txz
- installpkg kernel-modules-5.4.80-x86_64-1.txz
+ installpkg kernel-generic-5.4.81-x86_64-1.txz
+ installpkg kernel-modules-5.4.81-x86_64-1.txz
installpkg mkinitrd-1.4.11-x86_64-15.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.80 -m ext4
+ mkinitrd -c -k 5.4.81 -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.80
+Here's another example: Build an initrd image using Linux 5.4.81
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.4.80 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.4.81 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?