summaryrefslogtreecommitdiff
path: root/README.initrd
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2019-10-29 20:09:01 +0000
committerEric Hameleers <alien@slackware.com>2019-10-30 08:59:50 +0100
commit50041dbf9ae0b1b0cfed11f7864ea0df61a96855 (patch)
treee712bb08285908f576592bad167c222c4023a90c /README.initrd
parent02056549bf9950d4e854dad95426ff1ad42fefc7 (diff)
downloadcurrent-50041dbf9ae0b1b0cfed11f7864ea0df61a96855.tar.gz
Tue Oct 29 20:09:01 UTC 201920191029200901
a/aaa_elflibs-15.0-x86_64-14.txz: Rebuilt. Upgraded: libglib-2.0.so.0.6200.2, libgmodule-2.0.so.0.6200.2, libgobject-2.0.so.0.6200.2, libgthread-2.0.so.0.6200.2. Added: libgomp.so.1.0.0. a/kernel-firmware-20191029_4065643-noarch-1.txz: Upgraded. a/kernel-generic-4.19.81-x86_64-1.txz: Upgraded. a/kernel-huge-4.19.81-x86_64-1.txz: Upgraded. a/kernel-modules-4.19.81-x86_64-1.txz: Upgraded. ap/sudo-1.8.29-x86_64-1.txz: Upgraded. d/kernel-headers-4.19.81-x86-1.txz: Upgraded. d/python-setuptools-41.6.0-x86_64-1.txz: Upgraded. k/kernel-source-4.19.81-noarch-1.txz: Upgraded. l/harfbuzz-2.6.3-x86_64-1.txz: Upgraded. n/samba-4.11.2-x86_64-1.txz: Upgraded. This update fixes bugs and these security issues: Client code can return filenames containing path separators. Samba AD DC check password script does not receive the full password. User with "get changes" permission can crash AD DC LDAP server via dirsync. For more information, see: https://www.samba.org/samba/security/CVE-2019-10218.html https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10218 https://www.samba.org/samba/security/CVE-2019-14833.html https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14833 https://www.samba.org/samba/security/CVE-2019-14847.html https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14847 (* Security fix *) x/libglvnd-1.2.0-x86_64-4.txz: Rebuilt. Applied upstream patches to fix EGL/eglplatform.h. x/xorg-server-1.20.5-x86_64-3.txz: Rebuilt. #define EGL_NO_X11 to fix glamor build against libglvnd-1.2.0. x/xorg-server-xephyr-1.20.5-x86_64-3.txz: Rebuilt. x/xorg-server-xnest-1.20.5-x86_64-3.txz: Rebuilt. x/xorg-server-xvfb-1.20.5-x86_64-3.txz: Rebuilt. 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 97039e34..ec08b075 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Fri Oct 18 00:21:04 UTC 2019
+Tue Oct 29 19:28:52 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.80 Linux kernel using the packages
+upgrading to the generic 4.19.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-4.19.80-x86_64-1.txz
- installpkg kernel-modules-4.19.80-x86_64-1.txz
+ installpkg kernel-generic-4.19.81-x86_64-1.txz
+ installpkg kernel-modules-4.19.81-x86_64-1.txz
installpkg mkinitrd-1.4.11-x86_64-13.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.80 -m ext4
+ mkinitrd -c -k 4.19.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 4.19.80
+Here's another example: Build an initrd image using Linux 4.19.81
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 4.19.80 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 4.19.81 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?