Welcome to the new location of Alien's Wiki, sharing a single dokuwiki install with the SlackDocs Wiki.
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
slackware:setup [2007/06/14 21:16] – created. alien | slackware:setup [2008/01/23 13:21] – Fixed the errata... nothing showed up after 1st item alien | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Install to Logical Volumes (LVM) ===== | ===== Install to Logical Volumes (LVM) ===== | ||
+ | |||
+ | FIXME | ||
===== Encrypted partitions ===== | ===== 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: | ||
+ | Multiple devices driver support (RAID and LVM) ---> | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | CONFIG_BLK_DEV_DM=y | ||
+ | CONFIG_DM_CRYPT=y | ||
+ | </ | ||
+ | |||
+ | ===== Using an initrd with a big kernel ===== | ||
+ | |||
+ | When you use an initrd file for your box(a requirement for installing Slackware to LVM or LUKS partitions) you will notice that there is a maximum to the size of the kernel you use with it. | ||
+ | If the kernel grows to big (like with the //' | ||
+ | Warning: The initial RAM disk is too big to fit between the kernel and the 15M-16M memory hole. | ||
+ | It will be loaded in the highest memory as though the configuration file specified " | ||
+ | and it will be assumed that the BIOS supports memory moves above 16M. | ||
+ | </ | ||
+ | |||
+ | ===== Errata ===== | ||
+ | |||
+ | **__README_CRYPT.TXT__** | ||
+ | |||
+ | I'd like to correct two things omitted in the [[http:// | ||
+ | |||
+ | * First issue: \\ When you finish the installation and the README prompts you to __'' | ||
+ | installation'' | ||
+ | mount -o bind /proc /mnt/proc | ||
+ | mount -o bind /sys /mnt/sys | ||
+ | chroot /mnt | ||
+ | </ | ||
+ | mount -o bind /proc /mnt/proc | ||
+ | mount -o bind /sys /mnt/sys | ||
+ | mount -o bind /dev /mnt/dev | ||
+ | chroot /mnt | ||
+ | </ | ||
+ | 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 | ||
+ | </ | ||
+ | cp -a /dev/mapper /mnt/dev/ | ||
+ | </ | ||
+ | |||
+ | * Second:\\ When the README mentions __'' | ||
+ | |||
+ | * Third:\\ When you run the '' | ||
+ | Warning: "/ | ||
+ | Name change: '/ | ||
+ | Warning: Name change: ... etc. | ||
+ | </ | ||
+ | |||
+ | I hope this clarifies the issues some people reported to me after Slackware 12.0 was released. | ||
+ | -- Eric // |