diff options
| author | Patrick J Volkerding <volkerdi@slackware.com> | 2010-05-19 08:58:23 +0000 |
|---|---|---|
| committer | Eric Hameleers <alien@slackware.com> | 2018-05-31 22:43:05 +0200 |
| commit | b76270bf9e6dd375e495fec92140a79a79415d27 (patch) | |
| tree | 3dbed78b2279bf9f14207a16dc634b90995cbd40 /source/a/mkinitrd/README.initrd | |
| parent | 5a12e7c134274dba706667107d10d231517d3e05 (diff) | |
| download | current-b76270bf9e6dd375e495fec92140a79a79415d27.tar.gz | |
Slackware 13.1slackware-13.1
Wed May 19 08:58:23 UTC 2010
Slackware 13.1 x86_64 stable is released!
Lots of thanks are due -- see the RELEASE_NOTES and the rest of the
ChangeLog for credits. The ISOs are on their way to replication,
a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD.
We are taking pre-orders now at store.slackware.com, and offering
a discount if you sign up for a subscription. Consider picking up
a copy to help support the project. Thanks again to the Slackware
community for testing, contributing, and generally holding us to a
high level of quality. :-)
Enjoy!
Diffstat (limited to 'source/a/mkinitrd/README.initrd')
| -rw-r--r-- | source/a/mkinitrd/README.initrd | 17 |
1 files changed, 8 insertions, 9 deletions
diff --git a/source/a/mkinitrd/README.initrd b/source/a/mkinitrd/README.initrd index f027fa27..86d77539 100644 --- a/source/a/mkinitrd/README.initrd +++ b/source/a/mkinitrd/README.initrd @@ -22,7 +22,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, +required to support the filesystem used by the root partition (ext3, ext4, reiserfs, 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 @@ -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.29.5 -m reiserfs + mkinitrd -c -k 2.6.32.3 -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,11 +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.29.5 -kernel modules for a system with an ext3 root partition on /dev/hdb3. -Note that you need the mbcache, jbd, and ext3 modules to use ext3: +Here's another example: Build an initrd image using Linux 2.6.32.3 +kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 2.6.29.5 -m mbcache:jbd:ext3 -f ext3 -r /dev/hdb3 + mkinitrd -c -k 2.6.32.3 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? @@ -77,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.29.5 +image = /boot/vmlinuz-generic-2.6.32.3 initrd = /boot/initrd.gz - root = /dev/hda6 - label = Lnx26295 + root = /dev/sdb3 + label = Lnx26323 read-only # Linux bootable partition config ends |