Slackware 14.1slackware-14.1

Mon Nov  4 17:08:47 UTC 2013
Slackware 14.1 x86_64 stable is released!

It's been another interesting release cycle here at Slackware bringing
new features like support for UEFI machines, updated compilers and
development tools, the switch from MySQL to MariaDB, and many more
improvements throughout the system.  Thanks to the team, the upstream
developers, the dedicated Slackware community, and everyone else who
pitched in to help make this release a reality.

The ISOs are off to be replicated, a 6 CD-ROM 32-bit set and a
dual-sided
32-bit/64-bit x86/x86_64 DVD.  Please consider supporting the Slackware
project by picking up a copy from store.slackware.com.  We're taking
pre-orders now, and offer a discount if you sign up for a subscription.

Have fun!  :-)

1 files changed, 13 insertions, 13 deletions

diff --git a/README.initrd b/README.initrd
index 698f42266..872f41860 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,10 +1,10 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Mon Sep 17 13:39:27 CDT 2012
+Wed Oct 23 16:30:13 CDT 2013
 
 This document describes how to create and install an initrd, which may be 
-required to use the 3.2 kernel.  Also see "man mkinitrd".
+required to use the 3.x kernel.  Also see "man mkinitrd".
 
 1.  What is an initrd?
 2.  Why to I need an 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 
@@ -33,16 +33,16 @@ 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.2.29 Linux kernel using the packages
+upgrading to the generic 3.10.17 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.2.29-i686-1.tgz
-  installpkg kernel-modules-3.2.29-i686-1.tgz
-  installpkg mkinitrd-1.1.0-i486-1.tgz
+  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
 
 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 3.2.29 -m reiserfs
+  mkinitrd -c -k 3.10.17 -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 3.2.29
-kernel modules for a system with an ext3 root partition on /dev/sdb3:
+Here's another example:  Build an initrd image using Linux 3.10.17
+kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 3.2.29 -m ext3 -f ext3 -r /dev/sdb3
+  mkinitrd -c -k 3.10.17 -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.2.29
+image = /boot/vmlinuz-generic-3.10.17
   initrd = /boot/initrd.gz
   root = /dev/sda6
-  label = Lnx3229
+  label = Lnx31017
   read-only
 # Linux bootable partition config ends