]> code.delx.au - refind/blob - refind.conf-sample
Merge branch 'master' of git://git.code.sf.net/p/refind/code
[refind] / refind.conf-sample
1 #
2 # refind.conf
3 # Configuration file for the rEFInd boot menu
4 #
5
6 # Timeout in seconds for the main menu screen. Setting the timeout to 0
7 # disables automatic booting (i.e., no timeout).
8 #
9 timeout 20
10
11 # Hide user interface elements for personal preference or to increase
12 # security:
13 # banner - the rEFInd title banner
14 # label - boot option text label in the menu
15 # singleuser - remove the submenu options to boot Mac OS X in single-user
16 # or verbose modes; affects ONLY MacOS X
17 # hwtest - the submenu option to run Apple's hardware test
18 # arrows - scroll arrows on the OS selection tag line
19 # hints - brief command summary in the menu
20 # editor - the options editor (+, F2, or Insert on boot options menu)
21 # all - all of the above
22 # Default is none of these (all elements active)
23 #
24 #hideui singleuser
25 #hideui all
26
27 # Set the name of a subdirectory in which icons are stored. Icons must
28 # have the same names they have in the standard directory. The directory
29 # name is specified relative to the main rEFInd binary's directory. If
30 # an icon can't be found in the specified directory, an attempt is made
31 # to load it from the default directory; thus, you can replace just some
32 # icons in your own directory and rely on the default for others.
33 # Default is "icons".
34 #
35 #icons_dir myicons
36
37 # Use a custom title banner instead of the rEFInd icon and name. The file
38 # path is relative to the directory where refind.efi is located. The color
39 # in the top left corner of the image is used as the background color
40 # for the menu screens. Currently uncompressed BMP images with color
41 # depths of 24, 8, 4 or 1 bits are supported.
42 #
43 #banner hostname.bmp
44
45 # Custom images for the selection background. There is a big one (144 x 144)
46 # for the OS icons, and a small one (64 x 64) for the function icons in the
47 # second row. If only a small image is given, that one is also used for
48 # the big icons by stretching it in the middle. If only a big one is given,
49 # the built-in default will be used for the small icons.
50 #
51 # Like the banner option above, these options take a filename of an
52 # uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits.
53 #
54 #selection_big selection-big.bmp
55 #selection_small selection-small.bmp
56
57 # Use text mode only. When enabled, this option forces rEFInd into text mode.
58 # Passing this option a "0" value causes graphics mode to be used. Pasing
59 # it no value or any non-0 value causes text mode to be used.
60 # Default is to use graphics mode.
61 #
62 #textonly
63
64 # Set the EFI text mode to be used for textual displays. This option
65 # takes a single digit that refers to a mode number. The default is 0
66 # (80x25), 1 is sometimes 80x50, and higher numbers are system-specific
67 # modes. If you specify an invalid mode, rEFInd pauses during boot to
68 # inform you of valid modes.
69 # CAUTION: On VirtualBox, and perhaps on some real computers, specifying
70 # a text mode and uncommenting the "textonly" option while NOT specifying
71 # a resolution can result in an unusable display in the booted OS.
72 # Default is 0
73 #
74 #textmode 2
75
76 # Set the screen's video resolution. Pass this option either:
77 # * two values, corresponding to the X and Y resolutions
78 # * one value, corresponding to a GOP (UEFI) video mode
79 # Note that not all resolutions are supported. On UEFI systems, passing
80 # an incorrect value results in a message being shown on the screen to
81 # that effect, along with a list of supported modes. On EFI 1.x systems
82 # (e.g., Macintoshes), setting an incorrect mode silently fails. On both
83 # types of systems, setting an incorrect resolution results in the default
84 # resolution being used. A resolution of 1024x768 usually works, but higher
85 # values often don't.
86 # Default is "0 0" (use the system default resolution, usually 800x600).
87 #
88 #resolution 1024 768
89 #resolution 3
90
91 # Launch specified OSes in graphics mode. By default, rEFInd switches
92 # to text mode and displays basic pre-launch information when launching
93 # all OSes except OS X. Using graphics mode can produce a more seamless
94 # transition, but displays no information, which can make matters
95 # difficult if you must debug a problem. Also, on at least one known
96 # computer, using graphics mode prevents a crash when using the Linux
97 # kernel's EFI stub loader. You can specify an empty list to boot all
98 # OSes in text mode.
99 # Valid options:
100 # osx - Mac OS X
101 # linux - A Linux kernel with EFI stub loader
102 # elilo - The ELILO boot loader
103 # grub - The GRUB (Legacy or 2) boot loader
104 # windows - Microsoft Windows
105 # Default value: osx
106 #
107 #use_graphics_for osx,linux
108
109 # Which non-bootloader tools to show on the tools line, and in what
110 # order to display them:
111 # shell - the EFI shell (requires external program; see rEFInd
112 # documentation for details)
113 # gptsync - the (dangerous) gptsync.efi utility (requires external
114 # program; see rEFInd documentation for details)
115 # apple_recovery - boots the Apple Recovery HD partition, if present
116 # mok_tool - makes available the Machine Owner Key (MOK) maintenance
117 # tool, MokManager.efi, used on Secure Boot systems
118 # about - an "about this program" option
119 # exit - a tag to exit from rEFInd
120 # shutdown - shuts down the computer (a bug causes this to reboot
121 # EFI systems)
122 # reboot - a tag to reboot the computer
123 # Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
124 #
125 #showtools shell, mok_tool, about, reboot, exit
126
127 # Directories in which to search for EFI drivers. These drivers can
128 # provide filesystem support, give access to hard disks on plug-in
129 # controllers, etc. In most cases none are needed, but if you add
130 # EFI drivers and you want rEFInd to automatically load them, you
131 # should specify one or more paths here. rEFInd always scans the
132 # "drivers" and "drivers_{arch}" subdirectories of its own installation
133 # directory (where "{arch}" is your architecture code); this option
134 # specifies ADDITIONAL directories to scan.
135 # Default is to scan no additional directories for EFI drivers
136 #
137 #scan_driver_dirs EFI/tools/drivers,drivers
138
139 # Which types of boot loaders to search, and in what order to display them:
140 # internal - internal EFI disk-based boot loaders
141 # external - external EFI disk-based boot loaders
142 # optical - EFI optical discs (CD, DVD, etc.)
143 # hdbios - BIOS disk-based boot loaders
144 # biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
145 # cd - BIOS optical-disc boot loaders
146 # manual - use stanzas later in this configuration file
147 # Note that the legacy BIOS options require firmware support, which is
148 # not present on all computers.
149 # On UEFI PCs, default is internal,external,optical,manual
150 # On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
151 #
152 #scanfor internal,external,optical,manual
153
154 # Delay for the specified number of seconds before scanning disks.
155 # This can help some users who find that some of their disks
156 # (usually external or optical discs) aren't detected initially,
157 # but are detected after pressing Esc.
158 # The default is 0.
159 #
160 #scan_delay 5
161
162 # When scanning volumes for EFI boot loaders, rEFInd always looks for
163 # Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
164 # and scans the root directory and every subdirectory of the /EFI directory
165 # for additional boot loaders, but it doesn't recurse into these directories.
166 # The also_scan_dirs token adds more directories to the scan list.
167 # Directories are specified relative to the volume's root directory. This
168 # option applies to ALL the volumes that rEFInd scans. If a specified
169 # directory doesn't exist, it's ignored (no error condition results).
170 # The default is to scan the "boot" directory in addition to various
171 # hard-coded directories.
172 #
173 #also_scan_dirs boot,EFI/linux/kernels
174
175 # Partitions to omit from scans. You must specify a volume by its
176 # label, which you can obtain in an EFI shell by typing "vol", from
177 # Linux by typing "blkid /dev/{devicename}", or by examining the
178 # disk's label in various OSes' file browsers.
179 # The default is an empty list (all volumes are scanned).
180 #
181 #dont_scan_volumes
182
183 # Directories that should NOT be scanned for boot loaders. By default,
184 # rEFInd doesn't scan its own directory or the EFI/tools directory.
185 # You can "blacklist" additional directories with this option, which
186 # takes a list of directory names as options. You might do this to
187 # keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
188 # another boot loader or to exclude a directory that holds drivers
189 # or non-bootloader utilities provided by a hardware manufacturer. If
190 # a directory is listed both here and in also_scan_dirs, dont_scan_dirs
191 # takes precedence. Note that this blacklist applies to ALL the
192 # filesystems that rEFInd scans, not just the ESP.
193 #
194 #dont_scan_dirs EFI/boot,EFI/Dell
195
196 # Files that should NOT be included as EFI boot loaders (on the
197 # first line of the display). If you're using a boot loader that
198 # relies on support programs or drivers that are installed alongside
199 # the main binary or if you want to "blacklist" certain loaders by
200 # name rather than location, use this option. Note that this will
201 # NOT prevent certain binaries from showing up in the second-row
202 # set of tools. Most notably, MokManager.efi is in this blacklist,
203 # but will show up as a tool if present in certain directories. You
204 # can control the tools row with the showtools token.
205 # The default is shim.efi,MokManager.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi
206 #
207 #dont_scan_files shim.efi,MokManager.efi
208
209 # Scan for Linux kernels that lack a ".efi" filename extension. This is
210 # useful for better integration with Linux distributions that provide
211 # kernels with EFI stub loaders but that don't give those kernels filenames
212 # that end in ".efi", particularly if the kernels are stored on a
213 # filesystem that the EFI can read. When uncommented, this option causes
214 # all files in scanned directories with names that begin with "vmlinuz"
215 # or "bzImage" to be included as loaders, even if they lack ".efi"
216 # extensions. The drawback to this option is that it can pick up kernels
217 # that lack EFI stub loader support and other files. Most notably, if you
218 # want to give a kernel a custom icon by placing an icon with the kernel's
219 # filename but a ".icns" extension in the same directory as the kernel, this
220 # option will cause the icon file to show up as a non-functional loader tag.
221 # Passing this option a "0" value causes kernels without ".efi" extensions
222 # to NOT be scanned; passing it alone or with any other value causes all
223 # kernels to be scanned.
224 # Default is to NOT scan for kernels without ".efi" extensions.
225 #
226 scan_all_linux_kernels
227
228 # Set the maximum number of tags that can be displayed on the screen at
229 # any time. If more loaders are discovered than this value, rEFInd shows
230 # a subset in a scrolling list. If this value is set too high for the
231 # screen to handle, it's reduced to the value that the screen can manage.
232 # If this value is set to 0 (the default), it's adjusted to the number
233 # that the screen can handle.
234 #
235 #max_tags 0
236
237 # Set the default menu selection. The available arguments match the
238 # keyboard accelerators available within rEFInd. You may select the
239 # default loader using:
240 # - A digit between 1 and 9, in which case the Nth loader in the menu
241 # will be the default.
242 # - Any substring that corresponds to a portion of the loader's title
243 # (usually the OS's name or boot loader's path).
244 #
245 #default_selection 1
246
247 # Include a secondary configuration file within this one. This secondary
248 # file is loaded as if its options appeared at the point of the "include"
249 # token itself, so if you want to override a setting in the main file,
250 # the secondary file must be referenced AFTER the setting you want to
251 # override. Note that the secondary file may NOT load a tertiary file.
252 #
253 #include manual.conf
254
255 # Sample manual configuration stanzas. Each begins with the "menuentry"
256 # keyword followed by a name that's to appear in the menu (use quotes
257 # if you want the name to contain a space) and an open curly brace
258 # ("{"). Each entry ends with a close curly brace ("}"). Common
259 # keywords within each stanza include:
260 #
261 # volume - identifies the filesystem from which subsequent files
262 # are loaded. You can specify the volume by label or by
263 # a number followed by a colon (as in "0:" for the first
264 # filesystem or "1:" for the second).
265 # loader - identifies the boot loader file
266 # initrd - Specifies an initial RAM disk file
267 # icon - specifies a custom boot loader icon
268 # ostype - OS type code to determine boot options available by
269 # pressing Insert. Valid values are "MacOS", "Linux",
270 # "Windows", and "XOM". Case-sensitive.
271 # graphics - set to "on" to enable graphics-mode boot (useful
272 # mainly for MacOS) or "off" for text-mode boot.
273 # Default is auto-detected from loader filename.
274 # options - sets options to be passed to the boot loader; use
275 # quotes if more than one option should be passed or
276 # if any options use characters that might be changed
277 # by rEFInd parsing procedures (=, /, #, or tab).
278 # disabled - use alone or set to "yes" to disable this entry.
279 #
280 # Note that you can use either DOS/Windows/EFI-style backslashes (\)
281 # or Unix-style forward slashes (/) as directory separators. Either
282 # way, all file references are on the ESP from which rEFInd was
283 # launched.
284 # Use of quotes around parameters causes them to be interpreted as
285 # one keyword, and for parsing of special characters (spaces, =, /,
286 # and #) to be disabled. This is useful mainly with the "options"
287 # keyword. Use of quotes around parameters that specify filenames is
288 # permissible, but you must then use backslashes instead of slashes,
289 # except when you must pass a forward slash to the loader, as when
290 # passing a root= option to a Linux kernel.
291
292 # Below are several sample boot stanzas. All are disabled by default.
293 # Find one similar to what you need, copy it, remove the "disabled" line,
294 # and adjust the entries to suit your needs.
295
296 # A sample entry for a Linux 3.3 kernel with its new EFI boot stub
297 # support on a filesystem called "KERNELS". This entry includes
298 # Linux-specific boot options and specification of an initial RAM disk.
299 # Note uses of Linux-style forward slashes, even in the initrd
300 # specification. Also note that a leading slash is optional in file
301 # specifications.
302 menuentry Linux {
303 icon EFI/refind/icons/os_linux.icns
304 volume KERNELS
305 loader bzImage-3.3.0-rc7
306 initrd initrd-3.3.0.img
307 options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
308 disabled
309 }
310
311 # A sample entry for loading Ubuntu using its standard name for
312 # its GRUB 2 boot loader. Note uses of Linux-style forward slashes
313 menuentry Ubuntu {
314 loader /EFI/ubuntu/grubx64.efi
315 icon /EFI/refined/icons/os_linux.icns
316 disabled
317 }
318
319 # A minimal ELILO entry, which probably offers nothing that
320 # auto-detection can't accomplish.
321 menuentry "ELILO" {
322 loader \EFI\elilo\elilo.efi
323 disabled
324 }
325
326 # Like the ELILO entry, this one offers nothing that auto-detection
327 # can't do; but you might use it if you want to disable auto-detection
328 # but still boot Windows....
329 menuentry "Windows 7" {
330 loader \EFI\Microsoft\Boot\bootmgfw.efi
331 disabled
332 }
333
334 # EFI shells are programs just like boot loaders, and can be
335 # launched in the same way. You can pass a shell the name of a
336 # script that it's to run on the "options" line. The script
337 # could initialize hardware and then launch an OS, or it could
338 # do something entirely different.
339 menuentry "Windows via shell script" {
340 icon \EFI\refind\icons\os_win.icns
341 loader \EFI\tools\shell.efi
342 options "fs0:\EFI\tools\launch_windows.nsh"
343 disabled
344 }
345
346 # Mac OS is normally detected and run automatically; however,
347 # if you want to do something unusual, a manual boot stanza may
348 # be the way to do it. This one does nothing very unusual, but
349 # it may serve as a starting point. Note that you'll almost
350 # certainly need to change the "volume" line for this example
351 # to work.
352 menuentry "My Mac OS X" {
353 icon \EFI\refind\icons\os_mac.icns
354 volume "OS X boot"
355 loader \System\Library\CoreServices\boot.efi
356 disabled
357 }