1 files changed, 14 insertions, 14 deletions
diff --git a/README_CRYPT.TXT b/README_CRYPT.TXT
index d2b980297..0ea11b89a 100644
--- a/README_CRYPT.TXT
+++ b/README_CRYPT.TXT
@@ -307,10 +307,10 @@ needed to unlock the root filesystem, so that the kernel can start the init
 program.  In the example command line below which creates the 'initrd.gz'
 image I assume that the root filesystem is 'ext3', we used the mapped device
 'cryptroot' for the root filesystem on the real partition '/dev/sdx1',
-and are running the Slackware 13.37 default SMP kernel '2.6.37.6-smp'
+and are running the Slackware 14.0 default SMP kernel '3.2.29-smp'
 and we did not use Logical Volumes (more about that in the next section):
 
-  # mkinitrd -c -k 2.6.37.6-smp -m ext3 -f ext3 -r cryptroot -C /dev/sdx1
+  # mkinitrd -c -k 3.2.29-smp -m ext3 -f ext3 -r cryptroot -C /dev/sdx1
 
 * The resulting initrd image will be written to the file '/boot/initrd.gz'
 by default.  We still need to tell lilo about this initrd. Open the
@@ -318,7 +318,7 @@ configuration file '/etc/lilo.conf' in an editor such as vi or pico -
 it should already have been generated by the 'liloconfig' part of setup.
 Look for the "Linux bootable partition config" and add a line for the initrd.
 We also need to change the kernel file to a generic kernel, because lilo
-is unable to combine the 'huge' kernels in Slackware 13.37 with an initrd
+is unable to combine the 'huge' kernels in Slackware 14.0 with an initrd
 image - it will complain about "The initial RAM disk is too big to fit
 between the kernel and the 15M-16M memory hole" if you try with a 'huge'
 kernel.  We can live with that, since the 'huge' kernels are not meant
@@ -326,7 +326,7 @@ for day-to-day use anyway.  They are meant to install Slackware on a wide
 range of computers and that is why they are 'huge'.  The linux part of
 '/etc/lilo.conf' should end up looking somewhat like this:
 
-image = /boot/vmlinuz-generic-smp-2.6.37.6-smp
+image = /boot/vmlinuz-generic-smp-3.2.29-smp
   initrd = /boot/initrd.gz
   root = /dev/mapper/cryptroot
   label = linux
@@ -367,7 +367,7 @@ One, you will need to enter a passphrase for every partition you have encrypted
 (except for the swap which Slackware encrypts with a random passphrase
 on every boot).  Two, the method used for encrypting the swap partition
 prohibits the use of the swap as a hibernation partition.  And since the
-initrd of Slackware 13.37 supports hibernation, it would be a shame not to be
+initrd of Slackware 14.0 supports hibernation, it would be a shame not to be
 able to use this feature on your laptop (which, because of it's portability,
 is the primary target for full disk encryption anyway).
 
@@ -490,10 +490,10 @@ stage of booting the kernel.  The initial ramdisk (initrd) contains a small
 filesystem with the tools needed to unlock the root filesystem, so that
 the kernel can start the init program.  In the example command line below
 which creates the 'initrd.gz' image I assume that you formatted the root
-filesystem as 'ext3', and will be running the Slackware 13.37 default SMP
-kernel '2.6.37.6-smp' :
+filesystem as 'ext3', and will be running the Slackware 14.0 default SMP
+kernel '3.2.29-smp' :
 
-  # mkinitrd -c -k 2.6.37.6-smp -m ext3 -f ext3 -r /dev/cryptvg/root -C /dev/sdx2 -L
+  # mkinitrd -c -k 3.2.29-smp -m ext3 -f ext3 -r /dev/cryptvg/root -C /dev/sdx2 -L
 
 NOTE: if you use a non-US keyboard and need to enter a passphrase during boot,
       this may be problematic if the keyboard mapping is US while Slackware
@@ -509,7 +509,7 @@ configuration file '/etc/lilo.conf' in an editor such as vi or pico -
 it should already have been generated by the 'liloconfig' part of setup.
 Look for the "Linux bootable partition config" and add a line for the initrd.
 We also need to change the kernel file to a generic kernel, because lilo
-is unable to combine the 'huge' kernels in Slackware 13.37 with an initrd
+is unable to combine the 'huge' kernels in Slackware 14.0 with an initrd
 image - it will complain about "The initial RAM disk is too big to fit
 between the kernel and the 15M-16M memory hole" if you try a 'huge'
 kernel.  We can live with that, since the 'huge' kernels are not meant
@@ -517,7 +517,7 @@ for day-to-day use anyway.  They are meant to install Slackware on a wide
 range of computers and that is why they are 'huge'.  The linux part of
 '/etc/lilo.conf' should end up looking somewhat like this:
 
-image = /boot/vmlinuz-generic-smp-2.6.37.6-smp
+image = /boot/vmlinuz-generic-smp-3.2.29-smp
   initrd = /boot/initrd.gz
   root = /dev/cryptvg/root
   label = linux
@@ -562,7 +562,7 @@ system, it will be used and you won't have to type a passphrase.
 requires you to use the "-K" parameter to mkinitrd to specify the USB stick's
 FAT-label or UUID, as well as the full path to the keyfile.  An example:
 
-  # mkinitrd -c -k 2.6.37.6-smp -m ext3 -f ext3 -r /dev/cryptvg/root -C /dev/sdx2 -L -K LABEL=TRAVELSTICK:/keys/alien.luks
+  # mkinitrd -c -k 3.2.29-smp -m ext3 -f ext3 -r /dev/cryptvg/root -C /dev/sdx2 -L -K LABEL=TRAVELSTICK:/keys/alien.luks
 
     The mkinitrd of Slackware 13.1 introduced this support for USB sticks as
 unlocking mechanism.  Alternatively, after the root filesystem is unlocked
@@ -621,7 +621,7 @@ support for this keyboard to your initrd.
 A mkinitrd helper script
 ------------------------
 
-    The mkinitrd package in Slackware 13.37 ships with a script called
+    The mkinitrd package in Slackware 14.0 ships with a script called
 'mkinitrd_command_generator.sh'.  If you run this script, it will analyze
 your Slackware configuration and make a smart suggestion about the 'mkinitrd'
 command you have to type in order to create an initrd.gz with all the bells
@@ -636,7 +636,7 @@ by yourself:
 It should emit a string like this (your system will probably give different
 parameter values):
 
-mkinitrd -c -k 2.6.37.6-smp -m ext3 -f ext3 -r /dev/cryptvg/root -C /dev/sdx2 -L
+mkinitrd -c -k 3.2.29-smp -m ext3 -f ext3 -r /dev/cryptvg/root -C /dev/sdx2 -L
 
 You can copy and paste this output to your command prompt, and add any other
 parameters you need such as "-h" to indicate a hibernation partition or
@@ -651,7 +651,7 @@ Good luck with your fresh Slackware installion on encrypted partition(s)!
 
 ==============================================================================
 Author:
-  Eric Hameleers <alien@slackware.com> 08-apr-2011
+  Eric Hameleers <alien@slackware.com> 18-sep-2012
 URLs:
   http://www.slackware.com/~alien/dokuwiki/doku.php?id=slackware:setup