Welcome to the new location of Alien's Wiki, sharing a single dokuwiki install with the SlackDocs Wiki.

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

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

no way to compare when less than two revisions

Differences

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


Previous revision
Next revision
—slackware:setup [2008/01/23 12:43] – Tips on custom kernel compilation for LUKS alien
Line 1: Line 1:
 +====== The Slackware installer ======
  
 +
 +===== Install to Logical Volumes (LVM) =====
 +
 +FIXME
 +
 +
 +===== Encrypted partitions =====
 +
 +FIXME
 +
 +Installation to encrypted partitions works well with the stock Slackware kernels.\\ 
 +If you want to compile your own custom kernel to work with LUKS encrypted partitions you need to enable at least the following two options in your kernel configuration: <code>
 +Multiple devices driver support (RAID and LVM) --->
 + <*> Device mapper support
 + <*> Crypt target support
 +</code> This is equivalent to the following options in your ''.config'' file: <code>
 +CONFIG_BLK_DEV_DM=y
 +CONFIG_DM_CRYPT=y
 +</code> Do not compile these as module! They are required in your kernel.
 +
 +===== Errata =====
 +
 +**__README_CRYPT.TXT__**
 +
 +I'd like to correct two things omitted in the [[http://slackware.osuosl.org/slackware-12.0/README_CRYPT.TXT|README_CRYPT.TXT]] file for Slackware 12.0. They relate to setting up an //encrypted root// partition in Slackware.\\ 
 +
 +  * 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>
 +mount -o bind /proc /mnt/proc
 +mount -o bind /sys /mnt/sys
 +chroot /mnt
 +</code> to  <code>
 +mount -o bind /proc /mnt/proc
 +mount -o bind /sys /mnt/sys
 +mount -o bind /dev /mnt/dev
 +chroot /mnt
 +</code> and then proceed with the remainder of the README.\\ __IF__ for whatever reason you get something like this error after running "''mount -o bind /dev/mnt/dev''": <code>
 +mount: wrong fs type, bad option, bad superblock on /dev, missing codepage or other error
 +       In some cases useful info is found in syslog - try dmesg | tail
 +</code> then please run this command instead: <code>
 +cp -a /dev/mapper /mnt/dev/
 +</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.
 +
 +I hope this clarifies the issues some people reported to me after Slackware 12.0 was released.
 +
 +-- Eric //03-july-2007//

Trace:

The Slackware installer ()
SlackDocs