Anaconda uses kickstart to automate installation and as a data store for the user interface. Skip to content Android Windows Linux Apple. Home » Linux. Related posts: Where is the kickstart file on Linux? How do I create a kickstart in Linux? What does anaconda do in Linux? What is Anaconda Linux? How do I know if Anaconda is installed on Linux?
Does Anaconda work on Linux? The anaconda file you see is the file that is automatically created from the installation steps prompts you answered when you installed the existing operating system.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta.
Now live: A fully responsive profile. Related 3. Hot Network Questions. Valid values include sssd and winbind.
Not all realms support all values. By default, the client software is chosen automatically. Possible values include active-directory or freeipa. Valid values include samba and adcli. By default, the membership software is chosen automatically. Reboot after the installation is successfully completed no arguments.
Normally, Kickstart displays a message and waits for the user to press a key before rebooting. The reboot option is equivalent to the shutdown -r command. For other completion methods, see the halt , poweroff , and shutdown Kickstart options. The halt option is the default completion method if no other methods are explicitly specified in the Kickstart file.
Use of the reboot option might result in an endless installation loop, depending on the installation media and method. Due to the complexities involved with booting systems using kexec , it cannot be explicitly tested and guaranteed to function in every situation.
When kexec is used, device registers which would normally be cleared during a full system reboot might stay filled with data, which could potentially create issues for some device drivers. Configures additional yum repositories that can be used as sources for package installation. You can add multiple repo lines. This option is required. If a repository has a name which conflicts with another previously added repository, it is ignored.
Because the installation program uses a list of preset repositories, this means that you cannot add repositories with the same names as the preset ones. The variables that can be used in yum repo config files are not supported here. This option cannot be used together with the --mirrorlist option in the same repository definition.
The variables that can be used in yum repository configuration files are not supported here. This option cannot be used together with the --baseurl option in the same repository definition.
Without using this option, a repository configured in a Kickstart file will only be available during the installation process, not on the installed system. If multiple repositories provide the same packages, this number is used to prioritize which repository will be used before another. Repositories with a lower cost take priority over repositories with higher cost. This is useful if multiple repositories provide the same package and you want to make sure it comes from a particular repository.
This is useful if multiple repositories provide the same package and you want to make sure it comes from this repository. This setting does not affect any other repositories, nor how the install. It tells the compose tools to not look at the package group information when mirroring trees so as to avoid mirroring large amounts of unnecessary data.
Repositories used for installation must be stable. The installation can fail if a repository is modified before the installation concludes. This gives you a chance to repair the system in case of any problems. By default, the installation program finds your system and mount it in read-write mode, telling you where it has performed this mount. You can optionally select to not mount anything the --nomount option or mount in read-only mode the --romount option.
Only one of these two options can be used. Automatically creates partitions required by your hardware platform. In contrast with autopart , this command only creates platform-specific partitions and leaves the rest of the drive empty, allowing you to create a custom layout. This option is mutually exclusive with --plaintext. To create an encrypted password, you can use python :. This option is mutually exclusive with --iscrypted. This means that the root user will not be able to log in from the console.
This option will also disable the Root Password screens in both the graphical and text-based manual installation. Sets the state of SELinux on the installed system. The default SELinux policy is enforcing. Modifies the default set of services that will run under the default systemd target.
The list of disabled services is processed before the list of enabled services. Therefore, if a service appears on both lists, it will be enabled. Do not include spaces in the list of services. If you do, Kickstart will enable or disable only the services up to the first space. To disable all four services, this entry should include no spaces:. Shut down the system after the installation has successfully completed. During a Kickstart installation, if no completion method is specified, the halt command is used.
The shutdown Kickstart option is equivalent to the shutdown command. For other completion methods, see the halt , poweroff , and reboot Kickstart options. If you install a display manager among your package selection options, this package creates an X configuration, and the installed system defaults to graphical. The effect of the skipx option is overridden. Using the snapshot command, you can create LVM thin volume snapshots during the installation process.
This enables you to back up a logical volume before or after the installation. To create multiple snapshots, add the snaphost Kickstart command multiple times. This name must be unique within the volume group.
During the installation, you can interact with the installation program and monitor its progress over an SSH connection. Use the sshpw command to create temporary accounts through which to log on.
Each instance of the command creates a separate account that exists only in the installation environment. These accounts are not transferred to the installed system. This means that the user will not be able to log in from the console. By default, the ssh server is not started during the installation. To make ssh available during the installation, boot the system with the kernel boot option inst. See Console, Environment and Display Options for details.
If you want to disable root ssh access, while allowing another user ssh access, use the following:. Perform the Kickstart installation in text mode. Kickstart installations are performed in graphical mode by default. Starting with CentOS 7. In previous releases, the names were validated against pytz. Note that the graphical and text mode interfaces still use the more restricted pytz.
Tells the installation program to suppress the Unsupported Hardware Detected alert. If this command is not included and unsupported hardware is detected, the installation stalls at this alert. This is a string of various system-specific fields separated by a comma. See the passwd 5 man page for more details. The groups must exist before the user account is created. See the group command. This option will also disable the Create User screens in both the graphical and text-based manual installation.
If not provided, the account will be locked by default. If not provided, the system default is used. If not provided, this defaults to the next available non-system UID. If not provided, this defaults to the next available non-system group ID. Consider using the --uid and --gid options to set IDs of regular users and their default groups at range starting at instead of That is because the range reserved for system users and groups, 0 - , might increase in the future and thus overlap with IDs of regular users.
Files and directories are created with various permissions, dictated by the application used to create the file or directory. For example, the mkdir command creates directories with all permissions enabled. However, applications are prevented from granting certain permissions to newly created files, as specified by the user file-creation mask setting.
The user file-creation mask can be controlled with the umask command. If unset, it defaults to This means that by default when an application creates a file, it is prevented from granting write permission to users other than the owner of the file. However, this can be overridden by other settings or scripts. Allows the graphical installation to be viewed remotely through VNC. This method is usually preferred over text mode, as there are some size and language limitations in text installations.
With no additional options, this command starts a VNC server on the installation system with no password and displays the details required to connect to it. If not provided, Anaconda uses the VNC default port of This is optional, but recommended. For a detailed partitioning example including volgroup , see Advanced Partitioning Example.
If you use this option, do not specify a partition. The default value is 4 MiB , and the minimum value is 1 MiB. Applicable only to newly created volume groups. Create the partition first, then create the logical volume group, and then create the logical volume.
Configures the X Window System. If you install the X Window System with a Kickstart file that does not include the xconfig command, you must provide the X configuration manually during installation. Do not use this command in a Kickstart file that does not install the X Window System. It is currently not possible to specify KDE as your default desktop environment using this option.
This is a known issue. The zerombr initializes any invalid partition tables that are found on disks and destroys all of the contents of disks with invalid partition tables. Define a Fibre channel device. This option only applies on IBM System z.
All of the options described below must be specified. Takes the form of a digit number, preceded by 0x. You can specify packages by environment , group , or by their package names. Several environments and groups that contain related packages are defined. Each entry has an ID, user visibility value, name, description, and package list.
If the group is selected for installation, the packages marked mandatory in the package list are always installed, the packages marked default are installed if they are not specifically excluded elsewhere, and the packages marked optional must be specifically included elsewhere even when the group is selected.
If you are not sure what packages should be installed, select the Minimal Install environment. Minimal install provides only the packages which are essential for running CentOS 7.
This will substantially reduce the chance of the system being affected by a vulnerability. If necessary, additional packages can be added later after the installation. To install a bit package on a bit system, append the package name with the bit architecture for which the package was built; for example, glibc. The --multilib option also must be specified in the Kickstart file; see the available options below.
Initial Setup does not run after a system is installed from a Kickstart file unless a desktop environment and the X Window System were included in the installation and graphical login was enabled.
This means that by default, no users except for root are created. You can either create a user with the user option in the Kickstart file before installing additional systems from it see Kickstart Commands and Options for details or log into the installed system with a virtual console as root and add users with the useradd command.
This command installs all packages which are part of the Infrastracture Server environment. Only a single environment can be specified in the Kickstart file. This group contains all packages which are known to cause file conflicts, and is intended to be excluded. Specify individual packages by name, one entry to a line. Use a leading dash - to specify packages or groups to exclude from the installation. Some options work for the entire package selection, others are used with only specific groups.
To use an option, append it to the start of the package selection section. Install the default set of packages. This corresponds to the package set which would be installed if no other selections were made in the Package Selection screen during an interactive installation.
Do not install any documentation contained within packages. Ignore any packages, groups and environments missing in the installation source, instead of halting the installation to ask if the installation should be aborted or continued.
Specify a list of languages to install. Note that this is different from package group level selections. This option does not describe which package groups should be installed; instead, it sets RPM macros controlling which translation files from individual packages should be installed.
Configure the installed system for multilib packages, to allow installing bit packages on a bit system, and install packages specified in this section as such.
However, with the --multilib option, you can automatically install the bit AMD and the i Intel system packages available, if any.
Packages which are only being installed as dependencies without being specified in the Kickstart file are only installed in architecture versions in which they are needed, even if they are available for more architectures. This option only works during the installation.
Already installed systems are not configured for multilib packages installation using the dnf command. Disables installation of the Core package group which is otherwise always installed by default.
Disabling the Core package group with --nocore should be only used for creating lightweight containers; installing a desktop or server system will result in an unusable system. Using - Core to exclude packages in the Core package group does not work. The only way to exclude the Core package group is with the --nocore option. The Core package group is defined as a minimal set of packages needed for installing a working system.
It is not related in any way to core packages as defined in the Package Manifest and Scope of Coverage Details. Sets the number of times Yum will attempt to download packages retries. The default value is This option only applies during the installation, and will not affect Yum configuration on the installed system.
Sets the Yum timeout in seconds. The options in this list only apply to a single package group. Note that some package groups, such as Scientific Support , do not have any mandatory or default packages specified - only optional packages.
In this case the --optional option must always be used, otherwise no packages from this group will be installed. It is also possible to run scripts, using interpreters available in the installation environment.
However, the name service has not been configured at this point, so only IP addresses work, not URLs. The pre-installation script section of Kickstart cannot manage multiple install trees or source media. This information must be included for each created Kickstart file, as the pre-installation script occurs during the second stage of the installation process.
Unlike the post-installation script, the pre-installation script is not run in the chroot environment. The following options can be used to change the behavior of pre-installation scripts. Allows you to specify a different scripting language, such as Python. Display an error and halt the installation if the script fails.
The error message will direct you to where the cause of the failure is logged. This script determines the number of hard drives in the system and writes a text file with a different partitioning scheme depending on whether it has one or two drives. Instead of having a set of partitioning commands in the Kickstart file, include the following line:. This section controls the behavior of the user interface of the installation system.
See Kickstart Commands and Options for more details. You have the option of adding commands to run on the system once the installation is complete, but before the system is rebooted for the first time. This section is useful for functions such as installing additional software or configuring an additional name server. The post-install script is run in a chroot environment, therefore, performing tasks such as copying scripts or RPM packages from the installation media do not work by default.
You can change this behavior using the --nochroot option as described below. Because post-install script runs in a chroot environment, most systemctl commands will refuse to perform any action. You can access the network, but you cannot resolve IP addresses. The following options can be used to change the behavior of post-installation scripts. Note that the path of the log file must take into account whether or not you use the --nochroot option. For example, without --nochroot :.
Note that NFS file locking is not supported while in Kickstart mode, therefore the -o nolock option is required. Kickstart installations can contain custom scripts which are run when the installer encounters a fatal error - for example, an error in a package that has been requested for installation, failure to start VNC when specified, or an error when scanning storage devices. Installation cannot continue after such an error has occured. Kickstart installations support add-ons.
These add-ons can expand the basic Kickstart and Anaconda functionality in many ways. For example, if you want to use the Kdump add-on, which is distributed with Anaconda by default, use the following commands:. The following is an integrated example showing the clearpart , zerombr , part , raid , volgroup , and logvol Kickstart options in action:. First, the clearpart command is used on drives hda and hdc to wipe them. The zerombr command initializes unused partition tables. Then, the two drives are partitioned to prepare them for RAID configuration.
Each drive is divided into five partitions, and each drive is partitioned into an identical layout. The fifth, largest pair of partitions is named pv. Finally, the last set of commands first creates a volume group named sysvg on the pv. The following is an example showing how to prompt the user for input, and then read that input and save it as a variable, using bash:.
Due to the way Kickstart operates, the script must switch to a new virtual terminal before reading input from the user. The following is an example Kickstart file which demonstrates how to install and enable a service, in this case the Random Number Generator RNG daemon, which supplies entropy to the system kernel:. The rng-tools package, which contains the RNG daemon, is then designated for installation.
0コメント