Slackware 14.0slackware-14.0

Wed Sep 26 01:10:42 UTC 2012
Slackware 14.0 x86_64 stable is released!

We're perfectionists here at Slackware, so this release has been a long
time a-brewing.  But we think you'll agree that it was worth the wait.
Slackware 14.0 combines modern components, ease of use, and flexible
configuration... our "KISS" philosophy demands it.

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.

Thanks to everyone who helped make this happen.  The Slackware team, the
upstream developers, and (of course) the awesome Slackware user
community.

Have fun!  :-)

1 files changed, 14 insertions, 14 deletions

diff --git a/source/a/mkinitrd/README.initrd b/source/a/mkinitrd/README.initrd
index ca95c332..c10bb630 100644
--- a/source/a/mkinitrd/README.initrd
+++ b/source/a/mkinitrd/README.initrd
@@ -1,10 +1,10 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Thu Apr  7 06:02:26 CDT 2011
+@DATE@
 
 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 some features of the kernel.  Also see "man mkinitrd".
 
 1.  What is an initrd?
 2.  Why to I need an initrd?
@@ -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 2.6.37.6 Linux kernel using the packages
+upgrading to the generic @KERNEL_VERSION@ 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 mkinitrd-1.1.0-i486-1.tgz
+  installpkg kernel-generic-@KERNEL_VERSION@-@ARCH@-@BUILD@.tgz
+  installpkg kernel-modules-@KERNEL_VERSION@-@ARCH@-@BUILD@.tgz
+  installpkg mkinitrd-@MKINITRD_VERSION@-@ARCH@-@BUILD@.tgz
 
 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 mkinitrd should figure out any other modules
+it requires, I shouldn't need to specify any others:
 
-  mkinitrd -c -k 2.6.37.6 -m reiserfs
+  mkinitrd -c -k @KERNEL_VERSION@ -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 2.6.37.6
+Here's another example:  Build an initrd image using Linux @KERNEL_VERSION@
 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 @KERNEL_VERSION@ -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-@KERNEL_VERSION@
   initrd = /boot/initrd.gz
   root = /dev/sda6
-  label = Lnx26376
+  label = @LILO_KERNEL_NAME@
   read-only
 # Linux bootable partition config ends