ACM/3S-Image: Scripts to generate a domain-specific Debian image. - Codeberg.org

Archive: %: Merged with
https://codeberg.org/ACM/Domain_Specific_Utility_Environment
/ System Setup Scripts (for Debian)
 Minimal script to create a minimal Debian system with stable/LTS versions
of software and new hardware support.
 As opposed to newer methods of automating the process, shell scripting was
chosen for the reasons of portability and that it can be run from an installer.
POSIX shells also have standardized programs included that significantly
simplify the process.
 The script is meant to be somewhat general purpose; it can be used on many
different types of systems, including virtual machines, servers, desktops, and
handhelds.
 Meant to run either during the installation or after, this configurable
script automatically installs numerous base packages, drivers, and other
components for convenience; the script will set a number of reasonable defaults
as well.
 In comparison to other scripts and distributions, this project leaves the
presentation and general behavior of the system untouched; instead, defaults
are mostly used with minor tweaks to simplify use and offer increased platform
support by installing drivers and firmware from both Debian and outside sources
to maximize compatibility with new and old hardware. Hardware incompatibilities
are counted as bugs for this project. If a piece of hardware is not functioning
as expected after this installer, a request may be opened for PBSI to install
the required programs automatically. Continuing, it is a goal of this project to
make newer systems have the ability to run this soft-distribution of Debian,
since it has all the added benefits of the minimal and tailorable system without
going to hard-distributions that remove portability and make major alterations
to the base system.
 Adding on, there are more than just compatibility scripts provided by this
project; in fact, most of the scripts are likely for various changes and
additions that simplify use or make actions that would be taken by the
administrator anyway. All of these changes are modular and optional.
 See documentation for more details on use.
// Installation
 Post-Install script.
	1.) Place the repository contents in the desired directory.
	2.) Edit the "src/conf-install" file to set the specified parameters.
	3.) Run the "install.sh" file to initiate the installation.
// Scope
 1.) In order to maintain portability between shells, the script only employs
the use of "if" and basic POSIX programs located in the system's path
directories; comments are placed on separate lines.
 2.) To ensure hardware compatiblity, the script installs numerous packages
containing drivers and firmware. As well as this, it pulls remote packages to
obtain the newest firmware, drivers, and kernel.
 3.) To setup a reliable installation, the script only installs components
and configurations that are stable, as in experiencing little change; simple, as
in easy to use and unobtrusive; and minimal, as in having a small footprint or
small effect on the system; such as basic packages for managing the OS or
environment.
 4.) For configuration, the script has a configuration file to permit easy
modification to its behavior.
 5.) In use, the resulting system should have no annoyances, such as random
pop-ups; everything should have as few steps as possible. A wide variety of
scripts are placed on the system to automate certain processes as the system is
used.
 6.) To maintain simplicity, the implementation is limited to the script; this
script can be embedded in an ISO image file, or can be run post-install. Limiting
the scope is a catalyst for efficient production, since the effort is placed
entirely on the core component without the overhead of designing an entire
environment, such as Debian, which was targeted for its versatility and minimal
footprint.
 See the documentation for more information on the scripts configurations,
post-installation behavior, and installed programs.
+/