diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2018-06-18 06:19:23 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2018-06-18 10:35:08 +0200 |
commit | 04696baa146387e730d10a1e0b0a540989eea8e6 (patch) | |
tree | 642d09926a46b27d6a853e1f761398bb013746f9 /README.initrd | |
parent | 3a51ffacffe54c13e2e8f54390a730971cd9383b (diff) | |
download | current-04696baa146387e730d10a1e0b0a540989eea8e6.tar.gz current-04696baa146387e730d10a1e0b0a540989eea8e6.tar.xz |
Mon Jun 18 06:19:23 UTC 201820180618061923
a/aaa_elflibs-15.0-x86_64-1.txz: Upgraded.
Upgraded to libelf-0.171.so, added libgdbm.so.6.0.0.
a/etc-15.0-x86_64-6.txz: Rebuilt.
Add $(uname -m) information to /etc/issue.new.
Don't include /tmp directories - these are handled by aaa_base.
a/kernel-generic-4.14.50-x86_64-1.txz: Upgraded.
a/kernel-huge-4.14.50-x86_64-1.txz: Upgraded.
a/kernel-modules-4.14.50-x86_64-1.txz: Upgraded.
ap/man-db-2.8.3-x86_64-3.txz: Rebuilt.
Recompiled against gdbm-1.15.
ap/zsh-5.5.1-x86_64-2.txz: Rebuilt.
Recompiled against gdbm-1.15.
d/clisp-2.49_20180423_d1310adc5-x86_64-1.txz: Upgraded.
Compiled against gdbm-1.15.
d/kernel-headers-4.14.50-x86-1.txz: Upgraded.
d/perl-5.26.2-x86_64-5.txz: Rebuilt.
Recompiled against gdbm-1.15.
d/python-2.7.15-x86_64-3.txz: Rebuilt.
Recompiled against gdbm-1.15.
d/python3-3.6.5-x86_64-4.txz: Rebuilt.
Recompiled against gdbm-1.15.
d/ruby-2.5.1-x86_64-4.txz: Rebuilt.
Recompiled against gdbm-1.15.
k/kernel-source-4.14.50-noarch-1.txz: Upgraded.
kde/kdelibs-4.14.38-x86_64-3.txz: Rebuilt.
Patched to build with OpenSSL-1.1.x. Thanks to nobodino.
l/gdbm-1.15-x86_64-1.txz: Upgraded.
Shared library .so-version bump.
n/cyrus-sasl-2.1.27_rc8-x86_64-1.txz: Upgraded.
Compiled against gdbm-1.15.
n/mutt-1.10.0-x86_64-2.txz: Rebuilt.
Recompiled against gdbm-1.15.
n/php-7.2.6-x86_64-2.txz: Rebuilt.
Recompiled against gdbm-1.15.
n/yptools-2.14-x86_64-11.txz: Rebuilt.
Recompiled against gdbm-1.15.
xap/gnuchess-6.2.5-x86_64-3.txz: Rebuilt.
Recompiled against gdbm-1.15.
isolinux/initrd.img: Rebuilt.
Copy libefiboot to the installer (needed by efibootmgr).
Compress the kernel modules with xz.
Compress the initrd image with xz.
kernels/*: Upgraded.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Copy libefiboot to the installer (needed by efibootmgr).
Compress the kernel modules with xz.
Compress the initrd image with xz.
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 829b93cf0..44ee54ccb 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Tue Jun 12 04:26:32 UTC 2018 +Mon Jun 18 05:56:33 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.49 Linux kernel using the packages +upgrading to the generic 4.14.50 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.49-x86_64-1.txz - installpkg kernel-modules-4.14.49-x86_64-1.txz + installpkg kernel-generic-4.14.50-x86_64-1.txz + installpkg kernel-modules-4.14.50-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-7.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.49 -m ext4 + mkinitrd -c -k 4.14.50 -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.49 +Here's another example: Build an initrd image using Linux 4.14.50 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 4.14.49 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 4.14.50 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |