Boot options

Agama Live ISO behavior can be altered using the kernel command line at boot time. For those architectures that support Grub, you need to modify the agama-installer entry adding the boot options at the end of the linux line.

inst.auto: tells the installer to use the profile in the given URL to start an unattended installation. Check the URLs section to learn more about which URLs Agama supports.
```
inst.auto=http://mydomain.org/tumbleweed.jsonnet
```
inst.auto_insecure: ignores SSL/TLS problems like a self-signed certificate when downloading the profile.
inst.copy_network: whether the NetworkManager persistent system connections should be copied to the target system at the end of the installation or not. The copy is enabled by default.
```
inst.copy_network=0
```
inst.dud: applies a Driver Update (DUD) to the installation environment. A DUD can be used to patch or extend the installer. Supported formats include RPM packages and special DUD archives created with mkdud.

You can specify this parameter multiple times; each entry is processed independently. For more details on supported URL formats, see the URLs section.
```
inst.dud=https://download.opensuse.org/some-project/some.rpm
inst.dud=label://UPDATES/package.rpm
```
Beware that this option does not perform any dependency checks or signature validation on the provided update.
inst.dud_insecure: ignores SSL/TLS problems like a self-signed certificate when downloading the DUD image from an HTTPS server

Security
Disabling SSL/TLS checks is a security risk! An attacker could easily tamper the downloaded DUD image and could inject a malicious code into the system or install vulnerable packages!
inst.dud_packages.gpg: this allows ignoring the package GPG signature problems with the inst.dud_packages.gpg=0 option when installing the packages to the target system.

Applies only to the DUD packages, the GPG problems for the other packages are still detected and reported.

Security
Installing unknown packages is a security risk! Malicious code might be easily installed in your system!
inst.self_update=0: Since SLES16.0/QU0 disable the installer self-update. See more details and the other self-update related boot options (inst.self_update_ssl=0, inst.self_update_unsigned_repo=1, inst.self_update_import_key=1 and inst.self_update_gpg=0) in the Self-update guide.
inst.info: points to info file that contains additional Agama settings. It is useful when you want to provide more options for Agama and typing them during boot is not possible.
```
inst.info=ftp://myserver/devel.info
```
note
Supports only parameters specified on this section. Kernel parameters are ignored.
inst.register_url: sets the URL of the RMT or SCC proxy server to register the product with.
```
inst.register_url=http://rmt.example.net
```
inst.install_url: overrides the default installation_url set in the product files here by passing the inst.install_url parameter as a boot option in the bootloader. This is particularly useful for any pre-production testing in openQA.
```
inst.install_url=https://myrepo,https://myrepo2
```
warning
Setting this variable will impact all products.
inst.finish: allows to change the behavior of Agama when the installation finishes.
- stop: do nothing (default for the interactive installation). Agama web user interface shows a button to reboot the system and gives you a chance to download the logs.
- reboot: reboots the system (default for the unattended installation).
- halt: halts the system.
- poweroff: powers the system off.
```
inst.finish=poweroff
```
inst.solver_testcase=1: Since 16.1 Always save a solver test case. By default the solver testcase is saved only on failure, this option forces saving the solver testcase also on success. This is useful for debugging package dependency problems. The solver testcase is saved to /run/agama/testcase directory and is included in the logs created by the agama logs store command.

If the ZYPP_FULLLOG=1 boot option is set then the solver testcase is automatically created by libzypp in the /var/log/YaST2/autoTestcase directory and the inst.solver_testcase option is ignored.
inst.install: on unattended mode, Agama automatically starts the installation after reading the profile. However, if you set inst.install to 0, Agama stops after reading the configuration, giving the user a chance to review the installation options before proceeding.
fips: this is a standard Linux kernel parameter. When set to 1, the installer starts in FIPS-enabled mode. Additionally, Agama will use this as a trigger to propose the installed system to be FIPS-compliant.
```
fips=1
```
live.password and live.password_hash: sets the root password of the live system. live.password accepts a plain text password, while live.password_hash is expected to receive a hashed password, which is more secure. The disadvantage of a hashed password is that it is quite long and is not easy to type it into the boot prompt manually. It makes sense in environments where you can prepare the boot parameters in advance like in PXE boot or some virtual machines.
```
live.password=nots3cr3t
```
inst.script: specify the URL of an installation script that will run during boot. This script could do some preparation work or even tweak the installation workflow using Agama's command-line interface. The inst.auto option, if given, will be processed after this script runs.
inst.script_insecure: ignores SSL/TLS problems like a self-signed certificate when downloading the installation script.
live.password_dialog: start an interactive dialog during the boot process. This uses a nice dialog for entering and confirming the password. However, in some situations the full screen dialog might not be displayed correctly or some messages might be displayed over it. In that case you might use the Ctrl+L key shortcut to refresh the screen. If it still does not work then try using the other option below.
```
live.password_dialog
live.password_dialog=1
```
live.password_systemd: asks for a password using a simple prompt. This is similar to the option above, but the advantage is that this solution does not use a full screen dialog but a single line prompt so it should work better in special environments like a serial console.
```
live.password_systemd
live.password_systemd=1
```
inst.listen_on: Since 16.1 By default the Agama installer can be accessed using all network interfaces present in the machine. But for increased security it is possible to limit access only to particular network interfaces or it is possible to completely disable remote access.
- inst.listen_on=localhost - listen only on loop back (localhost) device. This disables remote access, the Agama installer can be accessed only locally.
- inst.listen_on=<ip> - listen on the specified IP address. Both IPv4 and IPv6 addresses are supported. It is possible to use multiple IP addresses separated by comma. Addresses not matching any network interface in the system are ignored.
- inst.listen_on=<interface> - listen on the specified network interface. Multiple interfaces can be separated by comma, not found interfaces are ignored. Example: inst.listen_on=eth2
- inst.listen_on=all - listen on all network interfaces (allow local and remote access). This is the default behavior, added just for completeness.
The Agama installer can be always accessed locally, even in cases when specifying an IP address or an network interface.

Note: For disabling other network services (like SSH) use the standard systemd.mask boot option, see more details below.
proxy: sets up a network proxy. The supported proxy URL format is protocol://[user[:password]@]host[:port].
```
proxy=http://192.168.122.1:3128
```
systemd.unit: standard way to change target for systemd boot. It is useful for head-less mode when graphical interface neither browser needs to be started locally.
```
systemd.unit=multi-user.target
```
systemd.mask: standard way to disable a systemd unit during boot. Can be used to disable some default services started in the Live ISO. For example if you want to disable the SSH server use this boot option:
```
systemd.mask=sshd.service
```