X-Git-Url: https://code.delx.au/refind/blobdiff_plain/d6882a1cf9f487600ccb2b57ba880b5f91ff0c10..b1ba9f9e7edcf78bb9bfeb5451bff0ecf1752f90:/docs/refind/linux.html diff --git a/docs/refind/linux.html b/docs/refind/linux.html index a28b7ed..a58502c 100644 --- a/docs/refind/linux.html +++ b/docs/refind/linux.html @@ -15,10 +15,10 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com

Originally written: 3/19/2012; last Web page update: -8/25/2013, referencing rEFInd 0.7.4

+12/8/2014, referencing rEFInd 0.8.4

-

I'm a technical writer and consultant specializing in Linux technologies. This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!

+

This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!

@@ -166,7 +166,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com

Using a Traditional Linux Boot Loader

-

I consider ELILO, GRUB Legacy, and GRUB 2 to be traditional Linux boot loaders. These programs all exist independent of the Linux kernel, but they can load a kernel and hand off control to it. All three programs have their own configuration files that reside in the same directory as the boot loader itself (or optionally elsewhere, in the case of GRUB 2).

+

I consider ELILO, GRUB Legacy, GRUB 2, and SYSLINUX to be traditional Linux boot loaders. These programs all exist independent of the Linux kernel, but they can load a kernel and hand off control to it. All four programs have their own configuration files that reside in the same directory as the boot loader itself (or optionally elsewhere, in the case of GRUB 2).

Ordinarily, rEFInd will detect these traditional boot loaders and provide main menu entries for them. If the boot loader exists in a directory with a name that matches a Linux distribution's icon filename, you'll automatically get a distribution-specific icon to refer to the boot loader.

@@ -190,8 +190,8 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com

  • Copy the relevant driver file for your filesystem and architecture to the drivers or drivers_arch - subdirectory of the rEFInd installation directory on the ESP. You may - need to create this subdirectory, too.
    • + subdirectory of the rEFInd installation directory on the EFI System + Partition (ESP). You may need to create this subdirectory, too.
  • Create a refind_linux.conf file in your /boot directory. The mkrlconf.sh script that comes with rEFInd @@ -337,7 +337,9 @@ on BIOS. The most reliable solution under BIOS is to chainload one boot loader to another. The same solution is possible under EFI, but rEFInd offers another possibility.

    -

    rEFInd 0.2.1 and later supports semi-automatic Linux EFI stub loader detection. This feature works as part of the standard boot loader scan operation, but it extends it as follows:

    +

    rEFInd supports semi-automatic Linux EFI stub loader detection. This +feature works as part of the standard boot loader scan operation, but it +extends it as follows:

      @@ -353,6 +355,17 @@ offers another possibility.

      rEFInd won't scan for kernels that lack .efi filename extensions. +
    1. If a file's name ends in .efi.signed, any other file with an + otherwise-identical name that lacks this extension is excluded. + This peculiar rule exists because Ubuntu has begun delivering two + copies of every kernel, one with and one without this extension. The + one with the extension is signed with a Secure Boot key; the one + without it is not so signed. Thus, if both files are present, the one + without the key won't boot on a computer with Secure Boot active, and + either will boot if Secure Boot is inactive. Thus, rEFInd excludes the + redundant (unsigned) file in order to help keep the list of boot + options manageable.
      2. +

      A kernel whose filename lacks a version string matches an initial RAM disk that also lacks a version string in its filename. Note that you can reliably use only one kernel and initial RAM disk per directory that lack version numbers in their filenames.

    2. rEFInd looks for an initial RAM disk in the same directory as the @@ -368,11 +381,8 @@ offers another possibility.

      initial RAM disk is identified, rEFInd passes a suitable initrd= option to the kernel when it boots.
      3. -

      rEFInd 0.2.1 and 0.2.2 used a filename of linux.conf to hold Linux kernel options; however, the Linux kernel developers plan to use this name themselves, so I've switched to refind_linux.conf as of rEFInd 0.2.3. Through version 0.4.2, rEFInd still supported the linux.conf filename as a backup to refind_linux.conf, but as of version 0.4.3, linux.conf no longer works, so you should rename rEFInd's linux.conf file to refind_linux.conf if you're upgrading.

      -
    3. rEFInd looks for a file called refind_linux.conf in the same - directory as the kernel file. This file is a practical requirement for - booting from an auto-detected kernel. It consists of a series of lines, + directory as the kernel file. It consists of a series of lines, each of which consists of a label followed by a series of kernel options. The first line sets default options, and subsequent lines set options that are accessible from the main menu tag's submenu screen. If @@ -477,7 +487,7 @@ total 17943
      -

      copyright © 2012 by Roderick W. Smith

      +

      copyright © 2012–2014 by Roderick W. Smith

      This document is licensed under the terms of the GNU Free Documentation License (FDL), version 1.3.