diff options
Diffstat (limited to 'README.initrd')
| -rw-r--r-- | README.initrd | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/README.initrd b/README.initrd index 872f41860..84057a3ef 100644 --- a/README.initrd +++ b/README.initrd @@ -1,10 +1,10 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Wed Oct 23 16:30:13 CDT 2013 +Fri Jun 24 13:32:40 CDT 2016 This document describes how to create and install an initrd, which may be -required to use the 3.x kernel. Also see "man mkinitrd". +required to use the 4.x kernel. Also see "man mkinitrd". 1. What is an initrd? 2. Why to I need an initrd? @@ -23,7 +23,7 @@ and before the main root filesystem is mounted. 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, -reiserfs, xfs), or perhaps the controller that the hard drive is attached +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 @@ -33,26 +33,26 @@ 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 3.10.17 Linux kernel using the packages +upgrading to the generic 4.4.14 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-3.10.17-x86_64-3.txz - installpkg kernel-modules-3.10.17-x86_64-3.txz - installpkg mkinitrd-1.4.8-x86_64-1.txz + installpkg kernel-generic-4.4.14-x86_64-1.txz + installpkg kernel-modules-4.4.14-x86_64-1.txz + installpkg mkinitrd-1.4.8-x86_64-8.txz Change into the /boot directory: cd /boot -Now you'll want to run "mkinitrd". I'm using reiserfs for my root -filesystem, and since it's an IDE system the reiserfs module will be -the only one I need to load: +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 3.10.17 -m reiserfs + mkinitrd -c -k 4.4.14 -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 3.10.17 +Here's another example: Build an initrd image using Linux 4.4.14 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 3.10.17 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 4.4.14 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? @@ -76,10 +76,10 @@ initrd. Here's an example section of lilo.conf showing how this is done: # Linux bootable partition config begins -image = /boot/vmlinuz-generic-3.10.17 +image = /boot/vmlinuz-generic-4.4.14 initrd = /boot/initrd.gz root = /dev/sda6 - label = Lnx31017 + label = Lnx4414 read-only # Linux bootable partition config ends |