+++ /dev/null
-#
-# ~/.bash_profile
-#
-[[ -f ~/.bashrc ]] && . ~/.bashrc
-[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx
+++ /dev/null
-# lxpanel <profile> config file. Manually editing is not recommended.
-# Use preference dialog in lxpanel to adjust config when you can.
-
-Global {
- edge=bottom
- allign=left
- margin=0
- widthtype=percent
- width=100
- height=26
- transparent=0
- tintcolor=#000000
- alpha=0
- setdocktype=1
- setpartialstrut=1
- usefontcolor=1
- fontcolor=#ffffff
- usefontsize=0
- fontsize=10
- background=0
- backgroundfile=/usr/share/lxpanel/images/background.png
-}
-Plugin {
- type=menu
- Config {
- image=/usr/share/lxpanel/images/my-computer.png
- system {
- }
- separator {
- }
- item {
- command=run
- }
- separator {
- }
- item {
- image=gnome-logout
- command=logout
- }
- }
-}
-Plugin {
- type=taskbar
- expand=1
- Config {
- tooltips=1
- IconsOnly=0
- AcceptSkipPager=1
- ShowIconified=1
- ShowMapped=1
- ShowAllDesks=0
- UseMouseWheel=1
- UseUrgencyHint=1
- FlatButton=0
- MaxTaskWidth=150
- spacing=1
- }
-}
+++ /dev/null
-lxpanel &
-sudo calamares &
\ No newline at end of file
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-
-<openbox_menu xmlns="http://openbox.org/3.4/menu">
-
-<menu id="root-menu" label="Openbox 3">
- <item label="Chromium">
- <action name="Execute">
- <command>chromium</command>
- <startupnotify>
- <enabled>yes</enabled>
- </startupnotify>
- </action>
- </item>
- <item label="PCMan File Manager">
- <action name="Execute">
- <command>pcmanfm</command>
- <startupnotify>
- <enabled>yes</enabled>
- </startupnotify>
- </action>
- </item>
- <item label="LXTerminal">
- <action name="Execute">
- <command>lxterminal</command>
- <startupnotify>
- <enabled>yes</enabled>
- </startupnotify>
- </action>
- </item>
- <item label="ARandR">
- <action name="Execute">
- <command>arandr</command>
- <startupnotify>
- <enabled>yes</enabled>
- </startupnotify>
- </action>
- </item>
- <item label="Reconfigure Openbox">
- <action name="Reconfigure" />
- </item>
- <item label="Log Out">
- <action name="Exit">
- <prompt>yes</prompt>
- </action>
- </item>
-</menu>
-
-</openbox_menu>
+++ /dev/null
-export ZIPINFOOPT=-OCP932
-export UNZIPOPT=-OCP932
-exec openbox-session
\ No newline at end of file
+++ /dev/null
-# Product branding information. This influences some global
-# user-visible aspects of Calamares, such as the product
-# name, window behavior, and the slideshow during installation.
-#
-# Additional styling can be done using the stylesheet.qss
-# file, also in the branding directory.
----
-componentName: alter
-
-# This selects between different welcome texts. When false, uses
-# the traditional "Welcome to the %1 installer.", and when true,
-# uses "Welcome to the Calamares installer for %1." This allows
-# to distinguish this installer from other installers for the
-# same distribution.
-welcomeStyleCalamares: false
-
-# Should the welcome image (productWelcome, below) be scaled
-# up beyond its natural size? If false, the image does not grow
-# with the window but remains the same size throughout (this
-# may have surprising effects on HiDPI monitors).
-welcomeExpandingLogo: true
-
-# Size and expansion policy for Calamares.
-# - "normal" or unset, expand as needed, use *windowSize*
-# - "fullscreen", start as large as possible, ignore *windowSize*
-# - "noexpand", don't expand automatically, use *windowSize*
-windowExpanding: fullscreen
-
-# Size of Calamares window, expressed as w,h. Both w and h
-# may be either pixels (suffix px) or font-units (suffix em).
-# e.g. "800px,600px"
-# "60em,480px"
-# This setting is ignored if "fullscreen" is selected for
-# *windowExpanding*, above. If not set, use constants defined
-# in CalamaresUtilsGui, 800x520.
-windowSize: 800px,520px
-
-# Placement of Calamares window. Either "center" or "free".
-# Whether "center" actually works does depend on the window
-# manager in use (and only makes sense if you're not using
-# *windowExpanding* set to "fullscreen").
-windowPlacement: center
-
-# These are strings shown to the user in the user interface.
-# There is no provision for translating them -- since they
-# are names, the string is included as-is.
-#
-# The four Url strings are the Urls used by the buttons in
-# the welcome screen, and are not shown to the user. Clicking
-# on the "Support" button, for instance, opens the link supportUrl.
-# If a Url is empty, the corresponding button is not shown.
-#
-# bootloaderEntryName is how this installation / distro is named
-# in the boot loader (e.g. in the GRUB menu).
-#
-# These strings support substitution from /etc/os-release
-# if KDE Frameworks 5.58 are available at build-time. When
-# enabled, @{var-name} is replaced by the equivalent value
-# from os-release. All the supported var-names are in all-caps,
-# and are listed on the FreeDesktop.org site,
-# https://www.freedesktop.org/software/systemd/man/os-release.html
-# Note that ANSI_COLOR and CPE_NAME don't make sense here, and
-# are not supported (the rest are). Remember to quote the string
-# if it contains substitutions, or you'll get YAML exceptions.
-#
-# The *Url* entries are used on the welcome page, and they
-# are visible as buttons there if the corresponding *show* keys
-# are set to "true" (they can also be overridden).
-strings:
- productName: Alter Linux
- shortProductName: Alter Linux
- version:
- shortVersion:
- versionedName: Alter Linux
- shortVersionedName: Alter Linux
- bootloaderEntryName: Alter Linux
- productUrl: https://alterlinux.com
- supportUrl: https://github.com/SereneTeam/alterlinux/issues
- knownIssuesUrl: https://alterlinux.com
- releaseNotesUrl: https://github.com/SereneTeam/alterlinux/releases
-
-# These images are loaded from the branding module directory.
-#
-# productIcon is used as the window icon, and will (usually) be used
-# by the window manager to represent the application. This image
-# should be square, and may be displayed by the window manager
-# as small as 16x16 (but possibly larger).
-# productLogo is used as the logo at the top of the left-hand column
-# which shows the steps to be taken. The image should be square,
-# and is displayed at 80x80 pixels (also on HiDPI).
-# productWelcome is shown on the welcome page of the application in
-# the middle of the window, below the welcome text. It can be
-# any size and proportion, and will be scaled to fit inside
-# the window. Use `welcomeExpandingLogo` to make it non-scaled.
-# Recommended size is 320x150.
-#
-# These filenames can also use substitutions from os-release (see above).
-images:
- productIcon: "logo-16.png"
- productLogo: "logo-128.png"
- productWelcome: "languages.png"
-
-# The slideshow is displayed during execution steps (e.g. when the
-# installer is actually writing to disk and doing other slow things).
-slideshow: "show.qml"
-# There are two available APIs for the slideshow:
-# - 1 (the default) loads the entire slideshow when the installation-
-# slideshow page is shown and starts the QML then. The QML
-# is never stopped (after installation is done, times etc.
-# continue to fire).
-# - 2 loads the slideshow on startup and calls onActivate() and
-# onLeave() in the root object. After the installation is done,
-# the show is stopped (first by calling onLeave(), then destroying
-# the QML components).
-slideshowAPI: 2
-
-
-# Colors for text and background components.
-#
-# - sidebarBackground is the background of the sidebar
-# - sidebarText is the (foreground) text color
-# - sidebarTextHighlight sets the background of the selected (current) step.
-# Optional, and defaults to the application palette.
-# - sidebarSelect is the text color of the selected step.
-#
-# These colors can **also** be set through the stylesheet, if the
-# branding component also ships a stylesheet.qss. Then they are
-# the corresponding CSS attributes of #sidebarApp.
-style:
-# sidebarBackground: "#EFEFEF"
- sidebarBackground: "#FFFFFF"
- sidebarText: "#000000"
- sidebarTextSelect: "#1565C0"
- sidebarTextHighlight: "#EFEFEF"
+++ /dev/null
-/* === This file is part of Calamares - <http://github.com/calamares> ===
- *
- * Copyright 2015, Teo Mrnjavac <teo@kde.org>
- *
- * Calamares is free software: you can redistribute it and/or modify
- * it under the terms of the GNU General Public License as published by
- * the Free Software Foundation, either version 3 of the License, or
- * (at your option) any later version.
- *
- * Calamares is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with Calamares. If not, see <http://www.gnu.org/licenses/>.
- */
-
-/*
- * Slides images dimensions are 800x440px.
- */
-
-import QtQuick 2.0;
-import calamares.slideshow 1.0;
-
-Presentation
-{
- id: presentation
-
- Timer {
- interval: 20000
- running: false
- repeat: false
- onTriggered: presentation.goToNextSlide()
- }
-
- Slide {
-
- Image {
- id: background1
- source: "slide.png"
- width: 800; height: 440
- fillMode: Image.PreserveAspectFit
- anchors.centerIn: parent
- }
- Text {
- anchors.horizontalCenter: background1.horizontalCenter
- anchors.top: background1.bottom
- text: ""
- wrapMode: Text.WordWrap
- width: 800
- horizontalAlignment: Text.Center
- }
- }
-}
+++ /dev/null
-#!/usr/bin/env bash
-
-function remove () {
- local list
- local file
- list=($(echo "$@"))
- for file in "${list[@]}"; do
- if [[ -f ${file} ]]; then
- rm -f "${file}"
- elif [[ -d ${file} ]]; then
- rm -rf "${file}"
- fi
- done
-}
-
-while getopts 'u:' arg; do
- case "${arg}" in
- u) user="${OPTARG}";;
- esac
-done
-
-remove /etc/skel/*
-remove /home/${user}/Desktop/calamares.desktop
-remove /home/${user}/.config
-remove /usr/share/calamares
-remove /etc/systemd/system/getty@tty1.service.d/autologin.conf
-remove /root/.automated_script.sh
-remove /etc/mkinitcpio-archiso.conf
-remove /etc/initcpio
-remove /usr/share/calamares/
-
-<<DISABLED
-if [[ -f /home/${user}/.config/user-dirs.dirs ]]; then
- HOME="/home/${user}"
- source ${HOME}/.config/user-dirs.dirs
-
- # Add pictures to bookmark
- echo -n "file://" >> ${HOME}/.config/gtk-3.0/bookmarks
- echo -n "${XDG_PICTURES_DIR}" >> ${HOME}/.config/gtk-3.0/bookmarks
- echo -ne "\n" >> ${HOME}/.config/gtk-3.0/bookmarks
-
- # Add videos to bookmark
- echo -n "file://" >> ${HOME}/.config/gtk-3.0/bookmarks
- echo -n "${XDG_VIDEOS_DIR}" >> ${HOME}/.config/gtk-3.0/bookmarks
- echo -ne "\n" >> ${HOME}/.config/gtk-3.0/bookmarks
-
- # Add music to bookmark
- echo -n "file://" >> ${HOME}/.config/gtk-3.0/bookmarks
- echo -n "${XDG_VIDEOS_DIR}" >> ${HOME}/.config/gtk-3.0/bookmarks
- echo -ne "\n" >> ${HOME}/.config/gtk-3.0/bookmarks
-
- # Add downloads to bookmark
- echo -n "file://" >> ${HOME}/.config/gtk-3.0/bookmarks
- echo -n "${XDG_DOWNLOAD_DIR}" >> ${HOME}/.config/gtk-3.0/bookmarks
- echo -ne "\n" >> ${HOME}/.config/gtk-3.0/bookmarks
-
- # Add documents to bookmark
- echo -n "file://" >> ${HOME}/.config/gtk-3.0/bookmarks
- echo -n "${XDG_DOCUMENTS_DIR}" >> ${HOME}/.config/gtk-3.0/bookmarks
- echo -ne "\n" >> ${HOME}/.config/gtk-3.0/bookmarks
-fi
-DISABLED
\ No newline at end of file
+++ /dev/null
----
-#
-# 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
-# - apk = Alpine Linux package manager
-# - dummy - Dummy manager, only logs
-#
-backend: pacman
-
-#
-# Often package installation needs an internet connection.
-# Since you may allow system installation without a connection
-# and want to offer OPTIONAL package installation, it's
-# possible to have no internet, yet have this packages module
-# enabled in settings.
-#
-# You can skip the whole module when there is no internet
-# by setting "skip_if_no_internet" to true.
-#
-# You can run a package-manager specific update procedure
-# before installing packages (for instance, to update the
-# list of packages and dependencies); this is done only if there
-# is an internet connection.
-#
-# Set "update_db" to 'true' for refreshing the database on the
-# target system. On target installations, which got installed by
-# unsquashing, a full system update may be needed. Otherwise
-# post-installing additional packages may result in conflicts.
-# Therefore set also "update_system" to 'true'.
-#
-skip_if_no_internet: false
-update_db: true
-update_system: true
-
-#
-# 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.
-# Such a job would populate a list of dictionaries in the global
-# storage called "packageOperations" and that list is processed
-# after the static list in the job configuration (i.e. the list
-# that is in this configuration file).
-#
-# Allowed package operations are:
-# - *install*, *try_install*: will call the package manager to
-# install one or more packages. The install target will
-# abort the whole installation if package-installation
-# fails, while try_install carries on. Packages may be
-# listed as (localized) names, or as (localized) package-data.
-# See below for the description of the format.
-# - *localInstall*: this is used to call the package manager
-# to install a package from a path-to-a-package. This is
-# useful if you have a static package archive on the install media.
-# The *pacman* package manager is the only one to specially support
-# this operation (all others treat this the same as *install*).
-# - *remove*, *try_remove*: will call the package manager to
-# remove one or more packages. The remove target will
-# abort the whole installation if package-removal fails,
-# while try_remove carries on. Packages may be listed as
-# (localized) names.
-# One additional key is recognized, to help netinstall out:
-# - *source*: ignored, does get logged
-# Any other key is ignored, and logged as a warning.
-#
-# There are two formats for naming packages: as a name or as package-data,
-# which is an object notation providing package-name, as well as pre- and
-# post-install scripts.
-#
-# Here are both formats, for installing vi. The first one just names the
-# package for vi (using the naming of the installed package manager), while
-# the second contains three data-items; the pre-script is run before invoking
-# the package manager, and the post-script runs once it is done.
-#
-# - install
-# - vi
-# - package: vi
-# pre-script: touch /tmp/installing-vi
-# post-script: rm -f /tmp/installing-vi
-#
-# The pre- and post-scripts are optional, but you cannot leave both out
-# if you do use the *package* key: using "package: vi" with neither script
-# option will trick Calamares into trying to install a package named
-# "package: vi", which is unlikely to work.
-#
-# The pre- and post-scripts are **not** executed by a shell unless you
-# explicitly invoke `/bin/sh` in them. The command-lines are passed
-# to exec(), which does not understand shell syntax. In other words:
-#
-# pre-script: ls | wc -l
-#
-# Will fail, because `|` is passed as a command-line argument to ls,
-# as are `wc`, and `-l`. No shell pipeline is set up, and ls is likely
-# to complain. Invoke the shell explicitly:
-#
-# pre-script: /bin/sh -c \"ls | wc -l\"
-#
-# The above note on shell-expansion applies to versions up-to-and-including
-# Calamares 3.2.12, but will change in future.
-#
-# Any package name may be localized; this is used to install localization
-# packages for software based on the selected system locale. By including
-# the string `LOCALE` in the package name, the following happens:
-#
-# - if the system locale is English (any variety), then the package is not
-# installed at all,
-# - otherwise `$LOCALE` or `${LOCALE}` is replaced by the 'lower-cased' BCP47
-# name of the 'language' part of the selected system locale (not the
-# country/region/dialect part), e.g. selecting "nl_BE" will use "nl"
-# here.
-#
-# Take care that just plain `LOCALE` will not be replaced, so `foo-LOCALE` will
-# be left unchanged, while `foo-$LOCALE` will be changed. However, `foo-LOCALE`
-# **will** be removed from the list of packages (i.e. not installed), if
-# English is selected. If a non-English locale is selected, then `foo-LOCALE`
-# will be installed, unchanged (no language-name-substitution occurs).
-#
-# The following installs localizations for vi, if they are relevant; if
-# there is no localization, installation continues normally.
-#
-# - install
-# - vi-$LOCALE
-# - package: vi-${LOCALE}
-# pre-script: touch /tmp/installing-vi
-# post-script: rm -f /tmp/installing-vi
-#
-# When installing packages, Calamares will invoke the package manager
-# with a list of package names if it can; package-data prevents this because
-# of the scripts that need to run. In other words, this:
-#
-# - install:
-# - vi
-# - binutils
-# - package: wget
-# pre-script: touch /tmp/installing-wget
-#
-# This will invoke the package manager three times, once for each package,
-# because not all of them are simple package names. You can speed up the
-# process if you have only a few pre-scripts, by using multiple install targets:
-#
-# - install:
-# - vi
-# - binutils
-# - install:
-# - package: wget
-# pre-script: touch /tmp/installing-wget
-#
-# This will call the package manager once with the package-names "vi" and
-# "binutils", and then a second time for "wget". When installing large numbers
-# of packages, this can lead to a considerable time savings.
-#
-
-operations:
- - remove:
- - alterlinux-calamares
- - alterlinux-keyring
- - alterlinux-mirrorlist
- - aptpac
- - arandr
- - arch-install-scripts
- - arj
- - b43-fwcutter
- - bash-completion
- - binutils
- - btrfs-progs
- - bzip2
- - chromium
- - clonezilla
- - cpio
- - crda
- - cups
- - cups-pdf
- - darkhttpd
- - ddrescue
- - dhclient
- - dhcpcd
- - dialog
- - dmraid
- - dnsmasq
- - dnsutils
- - dosfstools
- - eg-installer
- - ethtool
- - exfat-utils
- - f2fs-tools
- - fsarchiver
- - gnu-netcat
- - gpm
- - gptfdisk
- - grub
- - gzip
- - hdparm
- - ipw2100-fw
- - ipw2200-fw
- - irssi
- - iwd
- - jfsutils
- - lha
- - libpwquality
- - linux-atm
- - linux-firmware
- - lrzip
- - lsscsi
- - lvm2
- - lxpanel
- - lxterminal
- - lz4
- - lzip
- - lzop
- - man-db
- - man-pages
- - mc
- - mdadm
- - mtools
- - nano
- - ndisc6
- - netctl
- - network-manager-applet
- - networkmanager
- - nfs-utils
- - nilfs-utils
- - noto-fonts
- - noto-fonts-cjk
- - noto-fonts-emoji
- - ntfs-3g
- - ntp
- - openbox
- - openconnect
- - openssh
- - openvpn
- - os-prober
- - p7zip
- - partclone
- - parted
- - partimage
- - pcmanfm
- - ppp
- - pptpclient
- - refind-efi
- - reiserfsprogs
- - rp-pppoe
- - rsync
- - sdparm
- - sg3_utils
- - smartmontools
- - tar
- - tcpdump
- - testdisk
- - tlp
- - unarj
- - unrar
- - unzip-iconv
- - usb_modeswitch
- - usbutils
- - vim
- - vpnc
- - wget
- - wireless-regdb
- - wireless_tools
- - wpa_supplicant
- - wvdial
- - xdg-user-dirs
- - xfsprogs
- - xl2tpd
- - xorg-server
- - xorg-xinit
- - xz
- - yay-bin
- - zip
- - zstd
- - install:
- - base
- - base-devel
\ No newline at end of file
+++ /dev/null
-# 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:
-# - modules in $LIBDIR/calamares/modules, with
-# - settings in SHARE/calamares/modules or /etc/calamares/modules.
-# In debug-mode (e.g. calamares -d) "local" also adds some paths
-# that make sense from inside the build-directory, so that you
-# can build-and-run with the latest modules immediately.
-#
-# Strings other than "local" are taken as paths and interpreted
-# relative to wherever Calamares is started. It is therefore **strongly**
-# recommended to use only absolute paths here. This is mostly useful
-# if your distro has forks of standard Calamares modules, but also
-# uses some form of upstream packaging which might overwrite those
-# forked modules -- then you can keep modules somewhere outside of
-# the "regular" module tree.
-#
-#
-# 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 module name, an instance
-# 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. In the *sequence*
-# section below, use instance-keys to name instances (instead of just
-# a module name, for modules which have only a single instance).
-#
-# Every module implicitly has an instance with the instance name equal
-# to its module name, e.g. "welcome@welcome". In the *sequence* section,
-# mentioning a module without a full instance key (e.g. "welcome")
-# means that implicit module.
-#
-# An instance must specify its configuration file (e.g. `webview-home.conf`).
-# The implicit instances all have configuration files named `<module>.conf`.
-# This (implict) way matches the source examples, where the welcome
-# module contains an example `welcome.conf`.
-#
-# For more information on running module instances, run Calamares in debug
-# mode and check the Modules page in the Debug information interface.
-#
-# A module that is often used with instances is shellprocess, which will
-# run shell commands specified in the configuration file. By configuring
-# more than one instance of the module, multiple shell sessions can be run
-# during install.
-#
-# 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.
-#
-# YAML: list of lists of strings.
-sequence:
-- show:
- - welcome
- - locale
- - keyboard
- - partition
- - users
- - summary
-- exec:
- - partition
- - mount
- - unpackfs
- - machineid
- - fstab
- - locale
- - keyboard
- - localecfg
- - shellprocess
- - luksopenswaphookcfg
- - luksbootkeyfile
- - initcpiocfg
- - initcpio
- - removeuser
- - users
- - networkcfg
- - hwclock
- - packages
- - services
- - 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: alter
-
-# 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, but Calamares will complain if
-# this is not explicitly set.
-#
-# YAML: boolean.
-prompt-install: false
-
-# If this is set to true, Calamares will execute all target environment
-# commands in the current environment, without chroot. This setting 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. (e.g. partitioning seems like a bad idea, since that is expected to
-# have been done already)
-#
-# Default is false (for a normal installer), but Calamares will complain if
-# this is not explicitly set.
-#
-# YAML: boolean.
-dont-chroot: false
-
-# If this is set to true, Calamares refers to itself as a "setup program"
-# rather than an "installer". Defaults to the value of dont-chroot, but
-# Calamares will complain if this is not explicitly set.
-# oem-setup: true
-
-# If this is set to true, the "Cancel" button will be disabled entirely.
-# The button is also hidden from view.
-#
-# This can be useful if when e.g. Calamares is used as a post-install
-# configuration tool and you require the user to go through all the
-# configuration steps.
-#
-# Default is false, but Calamares will complain if this is not explicitly set.
-#
-# YAML: boolean.
-disable-cancel: false
-
-# If this is set to true, the "Cancel" button will be disabled once
-# you start the 'Installation', meaning there won't be a way to cancel
-# the Installation until it has finished or installation has failed.
-#
-# Default is false, but Calamares will complain if this is not explicitly set.
-#
-# YAML: boolean.
-disable-cancel-during-exec: false
+++ /dev/null
-AlterLinux with a minimal GUI.You can install a minimal CLI ArchLinux with Calamares."
\ No newline at end of file
+++ /dev/null
-#
-# Alter Linux package list
-#
-# Yamada Hayao
-# Twitter: @Hayao0819
-# Email : hayao@fascone.net
-#
-# (c) 2019-2020 Fascode Network.
-#
-# Disk management
-
-
-clonezilla
-ddrescue
-dmraid
-fsarchiver
-gptfdisk
-hdparm
-lvm2
-mdadm
-partclone
-parted
-partimage
-sdparm
-smartmontools
-testdisk
\ No newline at end of file
+++ /dev/null
-#
-# Alter Linux package list
-#
-# Yamada Hayao
-# Twitter: @Hayao0819
-# Email : hayao@fascone.net
-#
-# (c) 2019-2020 Fascode Network.
-#
-# Internet
-
-
-#-- chat --#
-irssi
-
-
-#-- connection --#
-dhclient
-dhcpcd
-dnsutils
-ndisc6
-netctl
-networkmanager
-network-manager-applet
-ppp
-pptpclient
-rp-pppoe
-wvdial
-
-
-#-- client --#
-# lftp
-ntp
-openssh
-wget
-
-
-#-- server --#
-darkhttpd
-dnsmasq
-
-
-#-- web browser --#
-chromium
-# elinks
-
-
-#-- wireless --#
-crda
-iwd
-wireless-regdb
-wireless_tools
-wpa_supplicant
-
-
-#-- vpn --#
-openconnect
-openvpn
-vpnc
-xl2tpd
-
-
-#-- other tools --#
-ethtool
-gnu-netcat
-# nmap
-rsync
-tcpdump
\ No newline at end of file
+++ /dev/null
-#
-# Alter Linux package list
-#
-# Yamada Hayao
-# Twitter: @Hayao0819
-# Email : hayao@fascone.net
-#
-# (c) 2019-2020 Fascode Network.
-#
-# OpenBox
-
-
-#-- File manager --#
-pcmanfm
-
-
-#-- openbox --#
-openbox
-lxpanel
-
-
-#-- Terminal --#
-lxterminal
-
-
-#-- Settings --#
-arandr
-
-
-#-- xorg --#
-gpm
-xorg-server
-xorg-xinit
\ No newline at end of file
+++ /dev/null
-#
-# Alter Linux package list
-#
-# Yamada Hayao
-# Twitter: @Hayao0819
-# Email : hayao@fascone.net
-#
-# (c) 2019-2020 Fascode Network.
-#
-
-
-#-- boot manager --#
-grub
-os-prober
-refind-efi
-
-
-#-- documents --#
-man-db
-man-pages
-
-
-#-- linux --#
-linux-atm
-linux-firmware
-
-
-#-- GVFS --#
-#gvfs
-#gvfs-smb
-# Need this?
-
-
-#-- text editor --#
-nano
-vim
\ No newline at end of file
--- | ---
xfce | This is the default channel that uses Xfce4 for the desktop environment and adds various software.
plasma | This is an edition with Plasma and Qt apps. Currently in development and not stable.
-arch | It has only a minimal GUI and installer, and after installation it has a minimal ArchLinux. This is an ArchLinux installer.
#### About the kernel
--- | ---
xfce | デスクトップ環境にXfce4を使用し、様々なソフトウェアを追加したデフォルトのチャンネルです。
plasma | PlasmaとQtアプリを搭載したエディションです。 現在開発中で、安定していません。
-arch | 最小限のGUIとインストーラーのみを搭載し、インストール後は最小限のArchLinuxになります。つまりこれはArchLinuxのインストーラーです。
#### カーネルについて
OSDN Git Service
