You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

86 lines
2.7 KiB
Plaintext

# Configuration file for Calamares
# Syntax is YAML 1.2
---
# Modules can be job modules (with different interfaces) and QtWidgets view modules.
# They could all be placed in a number of different paths.
# "modules-search" is a list of strings, each of these can either be a full path to a
# directory or the keyword "local".
# "local" means LIBDIR/calamares/modules with settings in SHARE/calamares/modules or
# /etc/calamares/modules.
modules-search: [ local ]
# We define the module names in the order they should show up (QtWidget view modules,
# with one or more pages) OR be executed if enqueued (all other modules).
# Pages can also enqueue jobs for delayed execution in the order specified for the
# install phase, so a viewmodule name can appear in more than one phase.
# Phase 1 - prepare.
# View modules are shown as UI pages, jobs from job modules are executed immediately in
# the background.
# Jobs should be executed sparingly (if at all) in this phase.
prepare:
- welcome
- license
- locale
- keyboard
- partition
- users
- webview
- summary
# Phase 2 - install.
# View modules are not shown. Only the view modules shown in the previous phase are
# allowed, their names should be added here as placeholders to specify the order in
# which view module jobs should be enqueued. Job modules are also allowed.
install:
#- dummyprocess
#- dummypython
- partition
- mount
- unpackfs
- machineid
- fstab
- locale
- keyboard
- localecfg
- initcpiocfg
- initcpio
- users
- displaymanager
- networkcfg
- hwclock
- services
#- dracut
#- initramfs
- grubcfg
- bootloader
- umount
# Phase 3 - postinstall.
# View modules are shown as UI pages, jobs from job modules are executed immediately in
# the background.
# Jobs should be executed sparingly (if at all) in this phase.
postinstall:
- finished
# A branding component is a directory, either in SHARE/calamares/branding or in
# /etc/calamares/branding (the latter takes precedence). The directory must contain a
# YAML file branding.desc which may reference additional resources (such as images or QML)
# as paths relative to the current directory.
# Only the name of the branding component (directory) should be specified here, Calamares
# then takes care of finding it and loading the contents.
10 years ago
branding: default
# If this is set to true, Calamares will show an "are you sure?" prompt right before the
# install phase, i.e. at the point of no return. If it's false, no prompt is shown.
# Default is false.
prompt-install: false
# If this is set to true, all target environment calls will be executed on the current
# (host) system rather than on the target (chrooted) system.
# Only set this to true in exceptional circumstances, if you are not using Calamares as
# a system installer.
# Default is false.
dont-chroot: false