From 2315da16b798197c06be56305dfdbff4ff7321b8 Mon Sep 17 00:00:00 2001 From: V3n3RiX Date: Sun, 6 Nov 2016 11:36:56 +0000 Subject: calamares config && runtime done --- .../files/modules/bootloader.conf | 26 +++++ .../files/modules/displaymanager.conf | 16 +++ .../files/modules/keyboard.conf | 8 ++ .../files/modules/packages.conf | 40 +++++++ .../files/modules/unpackfs.conf | 5 + .../files/modules/users.conf | 22 ++++ .../files/modules/welcome.conf | 18 ++++ .../calamares-config-redcore/files/settings.conf | 117 +++++++++++++++++++++ 8 files changed, 252 insertions(+) create mode 100644 app-misc/calamares-config-redcore/files/modules/bootloader.conf create mode 100644 app-misc/calamares-config-redcore/files/modules/displaymanager.conf create mode 100644 app-misc/calamares-config-redcore/files/modules/keyboard.conf create mode 100644 app-misc/calamares-config-redcore/files/modules/packages.conf create mode 100644 app-misc/calamares-config-redcore/files/modules/unpackfs.conf create mode 100644 app-misc/calamares-config-redcore/files/modules/users.conf create mode 100644 app-misc/calamares-config-redcore/files/modules/welcome.conf create mode 100644 app-misc/calamares-config-redcore/files/settings.conf (limited to 'app-misc/calamares-config-redcore/files') diff --git a/app-misc/calamares-config-redcore/files/modules/bootloader.conf b/app-misc/calamares-config-redcore/files/modules/bootloader.conf new file mode 100644 index 00000000..62493e2e --- /dev/null +++ b/app-misc/calamares-config-redcore/files/modules/bootloader.conf @@ -0,0 +1,26 @@ +--- +# Define which bootloader you want to use for EFI installations +# Possible options are 'grub' and 'systemd-boot'. +efiBootLoader: "grub" + +# systemd-boot configuration files settings, set kernel and initramfs file names +# and amount of time before default selection boots +kernel: "/boot/kernel-genkernel-x86_64-4.8.5-redcore" +img: "/boot/initramfs-genkernel-x86_64-4.8.5-redcore" +timeout: "10" +# Optionally set the menu entry name and kernel name to use in systemd-boot. +# If not specified here, these settings will be taken from branding.desc. +# bootloaderEntryName: "Generic GNU/Linux" +# kernelLine: ", with Stable-Kernel" +# fallbackKernelLine: ", with Stable-Kernel (fallback initramfs)" + +# GRUB 2 binary names and boot directory +# Some distributions (e.g. Fedora) use grub2-* (resp. /boot/grub2/) names. +grubInstall: "grub2-install" +grubMkconfig: "grub2-mkconfig" +grubCfg: "/boot/grub/grub.cfg" +# Optionally set the --bootloader-id to use for EFI. If not set, this defaults +# to the bootloaderEntryName from branding.desc with problematic characters +# replaced. If an efiBootloaderId is specified here, it is taken to already be a +# valid directory name, so no such postprocessing is done in this case. +# efiBootloaderId: "dirname" diff --git a/app-misc/calamares-config-redcore/files/modules/displaymanager.conf b/app-misc/calamares-config-redcore/files/modules/displaymanager.conf new file mode 100644 index 00000000..2e764a9b --- /dev/null +++ b/app-misc/calamares-config-redcore/files/modules/displaymanager.conf @@ -0,0 +1,16 @@ +--- +#The DM module attempts to set up all the DMs found in this list, in that precise order. +#It also sets up autologin, if the feature is enabled in globalstorage. +#The displaymanagers list can also be set in globalstorage, and in that case it overrides anything set up here. +displaymanagers: + - lightdm + +#Enable the following settings to force a desktop environment in your displaymanager configuration file: +#defaultDesktopEnvironment: +# executable: "startkde" +# desktopFile: "plasma" + +#If true, try to ensure that the user, group, /var directory etc. for the +#display manager are set up correctly. This is normally done by the distribution +#packages, and best left to them. Therefore, it is disabled by default. +basicSetup: false diff --git a/app-misc/calamares-config-redcore/files/modules/keyboard.conf b/app-misc/calamares-config-redcore/files/modules/keyboard.conf new file mode 100644 index 00000000..ff60ed60 --- /dev/null +++ b/app-misc/calamares-config-redcore/files/modules/keyboard.conf @@ -0,0 +1,8 @@ +--- +# The name of the file to write X11 keyboard settings to +# The default value is the name used by upstream systemd-localed. +# Relative paths are assumed to be relative to /etc/X11/xorg.conf.d +xOrgConfFileName: "/usr/share/X11/xorg.conf.d/00-keyboard.conf" +# The path to search for keymaps converted from X11 to kbd format +# Leave this empty if the setting does not make sense on your distribution. +convertedKeymapPath: "/usr/share/keymaps/" diff --git a/app-misc/calamares-config-redcore/files/modules/packages.conf b/app-misc/calamares-config-redcore/files/modules/packages.conf new file mode 100644 index 00000000..8d45706b --- /dev/null +++ b/app-misc/calamares-config-redcore/files/modules/packages.conf @@ -0,0 +1,40 @@ +--- +# +# Which package manager to use, options are: +# - packagekit - PackageKit CLI tool +# - zypp - Zypp RPM frontend +# - yum - Yum RPM frontend +# - dnf - DNF, the new RPM frontend +# - urpmi - Mandriva package manager +# - apt - APT frontend for DEB and RPM +# - pacman - Pacman +# - portage - Gentoo package manager +# - entropy - Sabayon package manager +# +backend: portage +# +# List of maps with package operations such as install or remove. +# Distro developers can provide a list of packages to remove +# from the installed system (for instance packages meant only +# for the live system). +# +# A job implementing a distro specific logic to determine other +# packages that need to be installed or removed can run before +# this one. Distro developers may want to install locale packages +# or remove drivers not needed on the installed system. +# This job will populate a list of dictionaries in the global +# storage called "packageOperations" and it is processed +# after the static list in the job configuration. +# +operations: + - remove: + - app-admin/calamares + - app-misc/calamares-config-redcore + - app-misc/calamares-runtime + - app-misc/redcore-live + - x11-themes/redcore-artwork-calamares +# - install: +# - pkg1 +# - pkg2 +# - localInstall: +# - /path/to/pkg1 diff --git a/app-misc/calamares-config-redcore/files/modules/unpackfs.conf b/app-misc/calamares-config-redcore/files/modules/unpackfs.conf new file mode 100644 index 00000000..91eca93e --- /dev/null +++ b/app-misc/calamares-config-redcore/files/modules/unpackfs.conf @@ -0,0 +1,5 @@ +--- +unpack: + - source: "/dev/mapper/live-base" + sourcefs: "ext4" + destination: "" diff --git a/app-misc/calamares-config-redcore/files/modules/users.conf b/app-misc/calamares-config-redcore/files/modules/users.conf new file mode 100644 index 00000000..183c3f9d --- /dev/null +++ b/app-misc/calamares-config-redcore/files/modules/users.conf @@ -0,0 +1,22 @@ +--- +userGroup: users +defaultGroups: + - lp + - video + - tape + - uucp + - disk + - wheel + - audio + - cdrom + - cdrw + - usb + - plugdev + - portage + - messagebus + - vboxguest + - vboxsf +autologinGroup: autologin +doAutologin: false +setRootPassword: true +doReusePassword: false \ No newline at end of file diff --git a/app-misc/calamares-config-redcore/files/modules/welcome.conf b/app-misc/calamares-config-redcore/files/modules/welcome.conf new file mode 100644 index 00000000..7e4f3404 --- /dev/null +++ b/app-misc/calamares-config-redcore/files/modules/welcome.conf @@ -0,0 +1,18 @@ +--- +showSupportUrl: true +showKnownIssuesUrl: true +showReleaseNotesUrl: true + +requirements: + requiredStorage: 10.0 + requiredRam: 1.0 + check: + - storage + - ram + - power + - internet + - root + required: + - storage + - ram + - root diff --git a/app-misc/calamares-config-redcore/files/settings.conf b/app-misc/calamares-config-redcore/files/settings.conf new file mode 100644 index 00000000..91f9fe80 --- /dev/null +++ b/app-misc/calamares-config-redcore/files/settings.conf @@ -0,0 +1,117 @@ +# 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. +# YAML: list of strings. +modules-search: [ local ] + +# Instances section. This section is optional, and it defines custom instances for +# modules of any kind. An instance entry has an instance name, a module name, and +# a configuration file name. +# The primary goal of this mechanism is to allow loading multiple instances of the +# same module, with different configuration. If you don't need this, the instances +# section can safely be left empty. +# Module name plus instance name makes an instance key, e.g. "webview@owncloud", +# where "webview" is the module name (for the webview viewmodule) and "owncloud" +# is the instance name, which loads a configuration file named "owncloud.conf" from +# any of the configuration file paths, including the webview module directory. +# This instance key can then be referenced in the sequence section. +# For all modules without a custom instance specification, a default instance is +# generated automatically by Calamares. Therefore a statement such as "webview" in +# the sequence section automatically implies an instance key of "webview@webview" +# even without explicitly defining this instance, and the configuration file for +# this default instance "@" is always assumed to be +# ".conf". +# For more information on running module instances, run Calamares in debug mode +# and check the Modules page in the Debug information interface. +# YAML: list of maps of string:string key-value pairs. + +#instances: +#- id: owncloud +# module: webview +# config: owncloud.conf + +# Sequence section. This section describes the sequence of modules, both +# viewmodules and jobmodules, as they should appear and/or run. +# A jobmodule instance key (or name) can only appear in an exec phase, whereas +# a viewmodule instance key (or name) can appear in both exec and show phases. +# There is no limit to the number of show or exec phases. However, the same module +# instance key should not appear more than once per phase, and deployers should +# take notice that the global storage structure is persistent throughout the +# application lifetime, possibly influencing behavior across phases. +# A show phase defines a sequence of viewmodules (and therefore pages). These +# viewmodules can offer up jobs for the execution queue. +# An exec phase displays a progress page (with brandable slideshow). This progress +# page iterates over the modules listed in the *immediately preceding* show phase, +# and enqueues their jobs, as well as any other jobs from jobmodules, in the order +# defined in the current exec phase. +# It then executes the job queue and clears it. If a viewmodule offers up a job +# for execution, but the module name (or instance key) isn't listed in the +# immediately following exec phase, this job will not be executed. +# WARNING: when upgrading from Calamares 1.1, this section requires manual +# intervention. There are no fixed prepare/install/postinstall phases any more, +# and all limitations on the number of phases, number of pages, and number of +# instances are lifted. +# YAML: list of lists of strings. +sequence: +- show: + - welcome + - locale + - keyboard + - partition + - users + - summary +- exec: + - partition + - mount + - unpackfs + - machineid + - fstab + - locale + - keyboard + - localecfg + - luksbootkeyfile + - dracutlukscfg + - users + - displaymanager + - hwclock + - dracut + - packages + - grubcfg + - bootloader + - umount +- show: + - 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) as +# paths relative to the current directory. +# A branding component can also ship a QML slideshow for execution pages, along with +# translation files. +# Only the name of the branding component (directory) should be specified here, Calamares +# then takes care of finding it and loading the contents. +# YAML: string. +branding: redcore_branding + +# If this is set to true, Calamares will show an "Are you sure?" prompt right before +# each execution phase, i.e. at points of no return. If this is set to false, no prompt +# is shown. +# Default is false. +# YAML: boolean. +prompt-install: true + +# If this is set to true, Calamares will execute all target environment commands in the +# current environment, without chroot. This setting is considered experimental, and it +# should only be used when setting up Calamares as a post-install configuration tool, as +# opposed to a full operating system installer. +# Some official Calamares modules are not expected to function with this setting. +# Packagers beware, here be dragons. +# Default is false. +# YAML: boolean. +dont-chroot: false -- cgit v1.2.3