fedora-docs-l10n/fedora-install-guide/f35/pages/advanced/Boot_Options — English @ Fedora Weblate: [option]#inst.repo=#

Zen

	English	Actions
	Boot Options
	The [application]Anaconda installer includes a range of boot options for administrators, which modify the default behavior of the installation program by enabling or disabling certain functions. To use one or more boot options, you either have to boot from installation media and append these options at the boot menu (see xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]), or you must add them into your PXE server configuration file if you are booting from a network (see xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server]).
	You can use multiple options at the same time; in that case, separate them by a single space.
	There are two basic types of options described in this chapter:
	Options presented as ending with an "`equals`" sign (`=`) require a value to be specified - they cannot be used on their own. For example, the [option]#inst.vncpassword=# option must also contain a value (in this case, a password). The correct form is therefore [option]#inst.vncpassword=pass:attributes[{blank}]_password_pass:attributes[{blank}]#. On its own, without a password specified, the option is invalid.
	Options presented without the "`pass:attributes[{blank}]`=`pass:attributes[{blank}]`" sign do not accept any values or parameters. For example, the [option]#rd.live.check# option forces [application]Anaconda to verify the installation media before starting the installation; if this option is present, the check will be performed, and if it is not present, the check will be skipped.
	In addition to the options described in this chapter, the boot prompt also accepts [application]dracut kernel options. A list of these options is available as the `dracut.cmdline(7)` man page.
	Boot options specific to the installation program always start with `inst.` in this guide. This prefix was optional in previous releases, but starting with Fedora 34, the installer will ignore options that do not use it (for example, `stage2=` instead of `inst.stage2=`).
	Configuring the Installation System at the Boot Menu
	The exact way to specify custom boot options is differs based on your system's architecture, firmware and the method you use to boot the installation. If you are booting from local media, you can specify options in the boot menu, before you begin the installation; if you are booting from a network using a PXE server, you must add boot options into the boot loader configuration file before you boot the installation system. For specific instructions, see xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu] if you are booting from local media, and xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server] if you are booting from a server.
	Available Boot Options
	The following options are available in {PRODUCT}:
	Specifying the Installation Source
	[option]#inst.repo=#
	Specifies the installation source - that is, a location where the installation program can find the images and packages it requires. For example:
	[option]#inst.repo=cdrom#
	The source must be either:
	an installable tree, which is a directory structure containing the installation program's images, packages and repodata as well as a valid `.treeinfo` file
	a DVD (a physical disk present in the system's DVD drive)
	an ISO image of the full {PRODUCT} installation DVD, placed on a hard drive or a network location accessible from the installation system
	This option allows for the configuration of different installation methods using different formats. The syntax is described in the table below.
	Installation Sources
	\|Installation source\|Option format \|Any CD/DVD drive\|[option]#inst.repo=cdrom# \|Specific CD/DVD drive\|[option]#inst.repo=cdrom:pass:attributes[{blank}]_device_pass:attributes[{blank}]# \|Hard Drive\|[option]#inst.repo=hd:pass:attributes[{blank}]_device_:/pass:attributes[{blank}]_path_pass:attributes[{blank}]# \|HTTP Server\|[option]#inst.repo=http://pass:attributes[{blank}]_host_pass:attributes[{blank}]/pass:attributes[{blank}]_path_pass:attributes[{blank}]# \|HTTPS Server\|[option]#inst.repo=https://pass:attributes[{blank}]_host_pass:attributes[{blank}]/pass:attributes[{blank}]_path_pass:attributes[{blank}]# \|FTP Server\|[option]#inst.repo=ftp://pass:attributes[{blank}]_username_:pass:attributes[{blank}]_password_pass:attributes[{blank}]@pass:attributes[{blank}]_host_pass:attributes[{blank}]/pass:attributes[{blank}]_path_pass:attributes[{blank}]# \|NFS Server\|[option]#inst.repo=nfs:[pass:attributes[{blank}]_options_:]pass:attributes[{blank}]_server_:/pass:attributes[{blank}]_path_pass:attributes[{blank}]# footnote:[This option uses NFS protocol version 3 by default. To use a different version, add [option]#+nfsvers=pass:attributes[{blank}]_X_pass:attributes[{blank}]# to _options_.]
	Disk device names may be specified using the following formats:
	Kernel device name, for example `/dev/sda1` or `sdb2`
	File system label, for example `LABEL=Flash` or `LABEL=RHEL7`
	File system UUID, for example `UUID=8176c7bf-04ff-403a-a832-9557f94e61db`
	Non-alphanumeric characters must be represented as `\xpass:attributes[{blank}]_NN_pass:attributes[{blank}]`, where _NN_ is the hexadecimal representation of the character. For example, `\x20` is a white space (“ ”).
	[option]#inst.stage2=#

Loading…

No matching activity found.

Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Unchanged translation: Korean, Chinese (Simplified), Indonesian, Portuguese (Brazil), Turkish, Spanish, French

Reset

Glossary

English	English
No related strings found in the glossary.

String information

Source string description

type: Labeled list

Flags

no-wrap, read-only

Source string location

./pages/advanced/Boot_Options.adoc:39

String age

2 years ago

Last updated

10 months ago

Source string age