| Configuration Options | |||
|---|---|---|---|
| Configuration Directive | CLI Option | ||
| Possible Values | Default | Context | |
| Description | |||
answer_yes
|
-y, --yes
| ||
| 0, 1 | 0 | global, model | |
| Answer yes to all questions. This enables you to run an automated, unattended compose. | |||
clean_up
|
--clean-up
| ||
| 0, 1, 2 | 1 | global, model | |
| Should Revisor not clean up at all (0), clean up it's temporary build data (1), or everything (2). Note that everything includes the yum cache. | |||
copy_dir
|
--copy-dir
| ||
[dir]
| False | global, model | |
A directory tree to copy onto the media created. In the case of installation media, the contents of the directory specified are copied onto cdrom:/files/. In the case of live media, the contents of the directory specified are copied onto the root filesystem of the live system. See also Section 6.3, “HOWTO: Include folders and files on the Media”.
| |||
copy_local
|
--copy-local
| ||
| False | global, model | ||
Tell Revisor to copy files, even when they are local. This applies to relative corner-cases where the repositories or the destination_directory is mounted over NFS, and some actions cannot be performed.
| |||
debuglevel
|
-d, --debug
| ||
| 0 - 9 | 0 | global, model | |
| The level of debugging. 0 is the lowest debug level, whereas 9 is the highest. Revisor turns up the volume quickly. The logfile on debug level 9 may very easily become 20-30MB. | |||
destination_directory
|
--destination-directory
| ||
/srv/revisor/
|
[path]
| global, model | |
| The destination directory for the product. Revisor creates a sub-directory with the name of the model used, and places the product in that directory. | |||
getsource
|
--source
| ||
| False | global, model | ||
| Whether to obtain the source along with the binary RPMs used. This is False by default, and therefor the source is not included by default. Note that if you are distributing your product to third parties, you need to be able to provide the sources along with the binary product. | |||
include_bootiso
|
| ||
| 0, 1 | 0 | global, model | |
Whether to include the relatively large boot.iso on the optical installation media created. Setting this to 0 will still include boot.iso in the installation tree created (if configured with media_installation_tree[a])
| |||
kickstart_default
|
--kickstart-default
| ||
| 0, 1 | 0 | global, model | |
| Whether to set the isolinux.cfg entry that makes the installer use the kickstart included on the media, as a default. | |||
kickstart_exact
|
--kickstart-exact
| ||
| 0, 1 | 0 | global, model | |
Tells Revisor to ignore @core and @base groups (like with %packages --nobase) and only add what is in the package manifest.
| |||
kickstart_exact_nevra
|
--kickstart-exact-nevra
| ||
| 0, 1 | 0 | global, model | |
| Tells Revisor to only add what is in the package manifest. In addition, if the transaction changes (because of dependency resolving, for example), Revisor will stop composing. | |||
kickstart_file
|
--kickstart
| ||
[file]
| 0 | global, model | |
| What kickstart file to use. When in CLI mode, this is a mandatory setting. | |||
kickstart_include
|
--kickstart-include
| ||
| 0, 1 | 0 | global, model | |
Whether to include the kickstart on the media so that the installer may find it as cdrom:/ks.cfg.
| |||
kickstart_repos
|
--kickstart-repos
| ||
| 0, 1 | 0 | global, model | |
Whether to use the repo directives in the kickstart provided to Revisor. Useful in cases where the repo directive in the kickstart file provided points to an arbitrary repository such as a repository mirrored by Cobbler, since there is no default URI location for those repositories -and Cobbler refers to them in the kickstart (template) using $yum_repo_stanza
| |||
kickstart_save
|
--kickstart-save
| ||
| 0, 1 | 0 | global, model | |
| Where to save the resulting kickstart. In GUI mode, when changes to the package set can be applied, saves those changes out into a new kickstart file. | |||
media_installation_bluray_duallayer
|
--install-bluray-dl
| ||
| 0, 1 | 0 | global, model | |
| Whether to create Bluray Duallayer installation media (47GiB). | |||
media_installation_bluray
|
--install-bluray
| ||
| 0, 1 | 0 | global, model | |
| Whether to create Bluray installation media (23GiB). | |||
media_installation_bluray_duallayer
|
--install-bluray-dl
| ||
| 0, 1 | 0 | global, model | |
| Whether to create Bluray Duallayer installation media (47GiB). | |||
media_installation_cd
|
--install-cd
| ||
| 0, 1 | 0 | global, model | |
| Whether to create CD installation media (685MiB). | |||
media_installation_dvd
|
--install-dvd
| ||
| 0, 1 | 0 | global, model | |
| Whether to create DVD installation media (4.3GiB). | |||
media_installation_dvd_duallayer
|
--install-dvd-dl
| ||
| 0, 1 | 0 | global, model | |
| Whether to create DVD Duallayer installation media (8.0GiB). | |||
media_installation_tree
|
--install-tree
| ||
| 0, 1 | 0 | global, model | |
| Whether to create a an installation tree[b] (for publication over HTTP or FTP, or through Cobbler). No size limit. | |||
media_installation_unified
|
--install-unified
| ||
| 0, 1 | 0 | global, model | |
| Whether to create a unified ISO, installation media (no size limit). | |||
media_live_optical
|
--live-optical
| ||
| 0, 1 | 0 | global, model | |
| Whether to create Optical Live media (size unknown). | |||
model
|
--model
| ||
[model]
| global | ||
| The model to use. | |||
report_sizes
|
--report_sizes
| ||
| 0, 1 | 0 | global, model | |
| Report the sizes of RPM packages used. Lists the biggest packages in the transaction | |||
mode_respin
|
--respin
| ||
| False | global, model | ||
| Whether Revisor should operate in respin mode. See also Section 8.4, “Respin Mode” | |||
working_directory
|
-d, --debug
| ||
| 0 - 9 | 0 | global, model | |
| The level of debugging. 0 is the lowest debug level, whereas 9 is the highest. Revisor turns up the volume quickly. The logfile on debug level 9 may very easily become 20-30MB. | |||
[a] Note that the installation tree is always created. See Chapter 8, Compose Process Details for more details. [b] Note that the installation tree is always created. See Chapter 8, Compose Process Details for more details. | |||