diff options
Diffstat (limited to 'README.initrd')
| -rw-r--r-- | README.initrd | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/README.initrd b/README.initrd index ca95c332..698f4226 100644 --- a/README.initrd +++ b/README.initrd @@ -1,10 +1,10 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Thu Apr 7 06:02:26 CDT 2011 +Mon Sep 17 13:39:27 CDT 2012 This document describes how to create and install an initrd, which may be -required to use the 2.6 kernel. Also see "man mkinitrd". +required to use the 3.2 kernel. Also see "man mkinitrd". 1. What is an initrd? 2. Why to I need an initrd? @@ -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 2.6.37.6 Linux kernel using the packages +upgrading to the generic 3.2.29 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-2.6.37.6-i686-1.tgz - installpkg kernel-modules-2.6.37.6-i686-1.tgz + installpkg kernel-generic-3.2.29-i686-1.tgz + installpkg kernel-modules-3.2.29-i686-1.tgz installpkg mkinitrd-1.1.0-i486-1.tgz Change into the /boot directory: @@ -52,7 +52,7 @@ 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: - mkinitrd -c -k 2.6.37.6 -m reiserfs + mkinitrd -c -k 3.2.29 -m reiserfs 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 2.6.37.6 +Here's another example: Build an initrd image using Linux 3.2.29 kernel modules for a system with an ext3 root partition on /dev/sdb3: - mkinitrd -c -k 2.6.37.6 -m ext3 -f ext3 -r /dev/sdb3 + mkinitrd -c -k 3.2.29 -m ext3 -f ext3 -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-2.6.37.6 +image = /boot/vmlinuz-generic-3.2.29 initrd = /boot/initrd.gz root = /dev/sda6 - label = Lnx26376 + label = Lnx3229 read-only # Linux bootable partition config ends |