diff options
Diffstat (limited to 'README.initrd')
| -rw-r--r-- | README.initrd | 62 |
1 files changed, 31 insertions, 31 deletions
diff --git a/README.initrd b/README.initrd index 84057a3ef..74418f7da 100644 --- a/README.initrd +++ b/README.initrd @@ -1,85 +1,85 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Fri Jun 24 13:32:40 CDT 2016 +Fri May 25 23:01:32 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". +required to use the 4.x kernel. Also see "man mkinitrd". -1. What is an initrd? -2. Why to I need an initrd? -3. How do I build the initrd? -4. Now that I've built an initrd, how do I use it? +1. What is an initrd? +2. Why to I need an initrd? +3. How do I build the initrd? +4. Now that I've built an initrd, how do I use it? -1. What is an initrd? +1. What is an initrd? -Initrd stands for "initial ramdisk". An initial ramdisk is a very small +Initrd stands for "initial ramdisk". An initial ramdisk is a very small Linux filesystem that is loaded into RAM and mounted as the kernel boots, and before the main root filesystem is mounted. -2. Why do I need an initrd? +2. Why do I need an initrd? The usual reason to use an initrd is because you need to load kernel -modules before mounting the root partition. Usually these modules are +modules before mounting the root partition. Usually these modules are required to support the filesystem used by the root partition (ext3, ext4, btrfs, xfs), or perhaps the controller that the hard drive is attached -to (SCSI, RAID, etc). Essentially, there are so many different options +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 +many different kernels to try to cover everyone's needs. It's a lot more flexible to ship a generic kernel and a set of kernel modules for it. -3. How do I build the initrd? +3. How do I build the initrd? 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.4.14 Linux kernel using the packages +in Slackware's mkinitrd package. We'll walk through the process of +upgrading to the generic 4.14.44 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.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 + installpkg kernel-generic-4.14.44-x86_64-1.txz + installpkg kernel-modules-4.14.44-x86_64-1.txz + installpkg mkinitrd-1.4.11-x86_64-6.txz Change into the /boot directory: cd /boot -Now you'll want to run "mkinitrd". I'm using ext4 for my root filesystem, +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.4.14 -m ext4 + mkinitrd -c -k 4.14.44 -m ext4 -This should do two things. First, it will create a directory -/boot/initrd-tree containing the initrd's filesystem. Then it will -create an initrd (/boot/initrd.gz) from this tree. If you wanted to, +This should do two things. First, it will create a directory +/boot/initrd-tree containing the initrd's filesystem. Then it will +create an initrd (/boot/initrd.gz) from this tree. If you wanted to, you could make some additional changes in /boot/initrd-tree/ and -then run mkinitrd again without options to rebuild the image. That's +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.4.14 +Here's another example: Build an initrd image using Linux 4.14.44 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 4.4.14 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 4.14.44 -m ext4 -f ext4 -r /dev/sdb3 -4. Now that I've built an initrd, how do I use it? +4. Now that I've built an initrd, how do I use it? Now that you've got an initrd (/boot/initrd.gz), you'll want to load -it along with the kernel at boot time. If you use LILO for your boot +it along with the kernel at boot time. If you use LILO for your boot loader you'll need to edit /etc/lilo.conf and add a line to load the -initrd. Here's an example section of lilo.conf showing how this is +initrd. Here's an example section of lilo.conf showing how this is done: # Linux bootable partition config begins -image = /boot/vmlinuz-generic-4.4.14 +image = /boot/vmlinuz-generic initrd = /boot/initrd.gz root = /dev/sda6 - label = Lnx4414 + label = Slackware read-only # Linux bootable partition config ends |