summaryrefslogtreecommitdiffstats
path: root/README.initrd
diff options
context:
space:
mode:
author Patrick J Volkerding <volkerdi@slackware.com>2020-05-15 07:28:15 +0000
committer Eric Hameleers <alien@slackware.com>2020-05-15 17:59:53 +0200
commiteba2e5b781702a60ac9f9613c9b8456c1594215c (patch)
treee413ac11d0b244de7238614f3f0fc5e391ca4998 /README.initrd
parent5864796142dd047453e8517d6ff9ce9ad66ebdc4 (diff)
downloadcurrent-eba2e5b781702a60ac9f9613c9b8456c1594215c.tar.gz
current-eba2e5b781702a60ac9f9613c9b8456c1594215c.tar.xz
Fri May 15 07:28:15 UTC 202020200515072815
Hey folks, just a heads-up that PAM is about to be merged into the main tree. We can't have it blocking other upgrades any longer. The config files could be improved (adding support for pam_krb5 and pam_ldap, for example), but they'll do for now. Have a good weekend, and enjoy these updates! :-) a/aaa_elflibs-15.0-x86_64-23.txz: Rebuilt. Upgraded: libcap.so.2.34, libelf-0.179.so, liblzma.so.5.2.5, libglib-2.0.so.0.6400.2, libgmodule-2.0.so.0.6400.2, libgobject-2.0.so.0.6400.2, libgthread-2.0.so.0.6400.2, liblber-2.4.so.2.10.13, libldap-2.4.so.2.10.13, libpcre2-8.so.0.10.0. Added temporarily in preparation for upgrading icu4c: libicudata.so.65.1, libicui18n.so.65.1, libicuio.so.65.1, libicutest.so.65.1, libicutu.so.65.1, libicuuc.so.65.1. a/etc-15.0-x86_64-11.txz: Rebuilt. /etc/passwd: Added ldap (UID 330). /etc/group: Added ldap (GID 330). a/kernel-generic-5.4.41-x86_64-1.txz: Upgraded. a/kernel-huge-5.4.41-x86_64-1.txz: Upgraded. a/kernel-modules-5.4.41-x86_64-1.txz: Upgraded. a/pkgtools-15.0-noarch-33.txz: Rebuilt. setup.services: added support for rc.openldap and rc.openvpn. ap/hplip-3.20.5-x86_64-1.txz: Upgraded. d/kernel-headers-5.4.41-x86-1.txz: Upgraded. d/python-setuptools-46.3.0-x86_64-1.txz: Upgraded. d/python3-3.8.3-x86_64-1.txz: Upgraded. k/kernel-source-5.4.41-noarch-1.txz: Upgraded. n/openldap-2.4.50-x86_64-1.txz: Added. This is a complete OpenLDAP package with both client and server support. Thanks to Giuseppe Di Terlizzi for help with the server parts. n/openldap-client-2.4.50-x86_64-1.txz: Removed. x/mesa-20.0.7-x86_64-1.txz: Upgraded. isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. testing/packages/PAM/hplip-3.20.5-x86_64-1_pam.txz: 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 a265790d..73c2d86d 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
-Sun May 10 23:05:53 UTC 2020
+Fri May 15 07:03:45 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.40 Linux kernel using the packages
+upgrading to the generic 5.4.41 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.40-x86_64-1.txz
- installpkg kernel-modules-5.4.40-x86_64-1.txz
+ installpkg kernel-generic-5.4.41-x86_64-1.txz
+ installpkg kernel-modules-5.4.41-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.40 -m ext4
+ mkinitrd -c -k 5.4.41 -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.40
+Here's another example: Build an initrd image using Linux 5.4.41
kernel modules for a system with an ext4 root partition on /dev/sdb3:
- mkinitrd -c -k 5.4.40 -m ext4 -f ext4 -r /dev/sdb3
+ mkinitrd -c -k 5.4.41 -m ext4 -f ext4 -r /dev/sdb3
4. Now that I've built an initrd, how do I use it?