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.
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision |
| slackware:setup [2008/01/23 13:21] – Fixed the errata... nothing showed up after 1st item alien | slackware:setup [2008/02/14 17:49] – Changes in LILO explanation alien |
|---|
| 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 ===== |
| </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> |
