Welcome to Eric Hameleers (Alien BOB)'s Wiki pages.

If you want to support my work, please consider a small donation:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

slackware:setup [2008/01/23 13:21]
alien Fixed the errata... nothing showed up after 1st item
slackware:setup [2009/01/28 19:34] (current)
alien Add explicit error message
Line 29: Line 29:
 and it will be assumed that the BIOS supports memory moves above 16M. and it will be assumed that the BIOS supports memory moves above 16M.
 </code> As far as I know there is no remedy against this message - you need to shrink your kernel until there is room for the initrd image. A Slackware //'generic'// kernel is small enough. The recommendation for //'huge'// kernels is that they are not meant for daily use anyway. Either you compile your own custom kernel, or use one of the generic kernels with an initrd. </code> As far as I know there is no remedy against this message - you need to shrink your kernel until there is room for the initrd image. A Slackware //'generic'// kernel is small enough. The recommendation for //'huge'// kernels is that they are not meant for daily use anyway. Either you compile your own custom kernel, or use one of the generic kernels with an initrd.
 +
  
 ===== Errata ===== ===== Errata =====
Line 37: Line 38:
  
   * First issue: \\ When you finish the installation and the README prompts you to __''perform a chroot into the new   * First issue: \\ When you finish the installation and the README prompts you to __''perform a chroot into the new
-installation''__, there is one command missing. As a result, there will not be a ''/dev/mapper/cryptroot'' available inside the //chroot// and therefore the attempt to install LILO will fail.\\ Please change the list of commands that goes like <code>+installation''__, there is one command missing. As a result, there will not be a ''/dev/mapper/cryptroot'' available inside the //chroot// and therefore the attempt to install LILO will fail with the error <code>¬†
 +Fatal: Illegal 'root' specification: /dev/mapper/cryptroot¬†
 +</code> Please change the list of commands that goes like <code>
 mount -o bind /proc /mnt/proc mount -o bind /proc /mnt/proc
 mount -o bind /sys /mnt/sys mount -o bind /sys /mnt/sys
Line 53: Line 56:
 </code> which will add the required files intto the installed system so that lilo will install successfully. I have had reports from several people who experienced the above error, and I have seen it happen myself too, for reasons unclear to me. </code> which will add the required files intto the installed system so that lilo will install successfully. I have had reports from several people who experienced the above error, and I have seen it happen myself too, for reasons unclear to me.
  
-  * Second:\\ When the README mentions __''Change the boot device to name of the small unencrypted partition you've created and which is mounted under /boot''__ it must be clear that this action should __not__ be taken when you install LILO to the MBR. The example in the README is meant for a Slackware setup where there is another OS bootloader (such as MS Windows) already installed in the MBR, and your Slackware installation is a secondary install for which LILO needs to install itself into the root sector of a partition instead.+  * Second:\\ The README_CRYPT.TXT mentions __''Change the boot device to name of the small unencrypted partition you've created and which is mounted under /boot''__ it should be clear that this advice should __not__ be taken when you configured LILO to be installed in the MBR.\\ The example shown in README_CRYPT.TXT is for a Slackware setup when there is another OS bootloader (such as MS Windows) already installed in the MBR, and your encrypted Slackware installation is a secondary install for which LILO needs to be installed into the root sector of a partition instead.\\ If you are installing Slackware as the first and only Operating System on the computer, please configure ''/etc/lilo.conf'' so that LILO installs into the MBR. You still need that small unencrypted partition for ''/boot'' of  course... LILO can only load the kernel and initrd if they are found on an unencrypted medium.
  
   * Third:\\ When you run the ''lilo'' command and you are using LVM and/or LUKS-encrypted partitions, lilo will show the following warning message (or something very similar): <code>   * Third:\\ When you run the ''lilo'' command and you are using LVM and/or LUKS-encrypted partitions, lilo will show the following warning message (or something very similar): <code>

Personal Tools
sponsoring