OPINIONATED Preset user configurations in GLF Linux live boot OS 20250607 GLF ------------------------------------------------------------------------------------ By policy official Debian OS releases do not set ANY custom user configurations. All packages include a standard set of default assumptions and if any configurations are set before first use they are the same for all users, as they might be set in a postinstall script as the package is installed. Upon first run of thet application, if user confogurration is needed, it will be done at that time, perhaps with a query of the user's preferences. GLF has an OPINION about such things. The interactions among various applications is sometimes a delicate balance of settings which a user might need to discover and set only after much experience and experiment. The default installation state of Debian packages gives maximum flexibility, but many common issues or even severe problems may be settled by adjustying a few package specific configurations. The repository packages are intended to be a pristine source of carefully vetted software, free of external tampering and tested exhaustively. In general, unless one is attempting to perform duties of a Debian maintainer, one does not tamper with the package files (*.deb) themselves on a global or community level, though in isolated cases one may alter or create a local binary package file to install software needed in the remix but not otherwise available from Debian. Such changes would affect any user of the package at first (and/or later) use. They however do not set the bulk of user preferences or systemwide usability settings which aplly to the user's specific locally installed system. The Debian approach to user preferences is easily applied to installed systems -- those in which an actual installtion of the OS to hard drive is performed. The user of such an installation is free to set any and all prefernces and the settings will persist accordingly across boots. However, the specific GLF-gemerated OS remixes are intended by design to work upon live boot as fully working systems, which might never be permanently installed. The user preferences do not persist across live boot sessions, UNLESS a specific provision is made for a "persistence" partition in which the user may store configurations and generated data across boot sessions. Though that mode is supported by all the GLF-generated remix OS images, it is not routinely used. Specifically, the live boot sessions are usually intended to be complete workable environments in which all changes are temporary and any accumulated problems disapear after reboot ("Vegas rules" -- whatever happens in Vegas, stays in Vegas). To address configuration issues, and also to install a broad variety of user data into the live boot OS which is immediately available to the user at every boot, GLF has implemented a variety of workarounds to the "Debian Way". These remixes are intended to be standalone useful envionments to solve certain problems, and possibly to encapsulate entire libraries of historically construucted data or program source code within a sufficiently capable environment in which top run it, demonstrate it, document it, and even modify it. To that end, GLF has found several techniques essential and applies them to all live-build configuration filesets. These filesets embody instances of complete specifications for the "sudo lb build" command to rebuild a Debian Linux remix ISO image into a specific variant OS, complete with embedded preferences and user data. it is the OPINION of GLF that it is essential to support preloading non-official software and forcing presets to user configurations to make a viable total working OS for everyday use, especially if that system will only be used from a live boot USB or DVD medium. The technoques employed by GLF to make this work have been developed over many years of experience adjusting the live-build configurations for personally developed OS images. The following attempts to document the major methods used to customize a Debian live build OS for user preferences, and explain why certain OPINIONATED choices have been made. Methods used to insert arbitrary content into the OS image and filesystem --------------------------------------------------------------------------- The base live-build configuration necessary to generate a valid Debian OS live boot ISO image does not require ANY prestored configuration files. The live-build system was designed for Debian to set up the core required confoguration structures by execution of a small series of "live-config" command lines in a script. That works for a base system which only applies those system attributes which the Debian live project has anticipated to be relevant to the official live OS builds distributed by Debian. These basic builds allow for much overall variation, allowing many different flovors of OS such as Cinnamon, MATE, KDE, or XFCE. The primary specifications which set up the official builds can be created entirely by executing a sequence of "live-config" commands with appropriate arguments. The filestructure which will be built into a selected folder will contain the essential elements, especially a tree of subfolders under a top level "config" folder. If all one wanted to do was esswentially replicate an official Debian Live release image, one could do so by putting together such a script, running it, then performing a "sudo lb build" from the top folder containing the "config" subfolder. However, the live-build system allows for considerable expansion of the content which can be installed into the ultimate ISO image. There are many subfolders created under "config", many of which are empty by default. If a user inserts content into some of these empty folders, that content will influence the resulting built OS image. The rules are documented but sometimes not in great detail and errors are usually fatal to a build. The build process folows a predictable sequence of scripts installed by the "live-build" package. Any problems with the configuration tend to simply break and abort execution. However, when a tested and correct configuration fileset is applied, the build usually succeeds in producing a live bootable ISO image of the specified Debian based OS. The build process usuially takes from 1 to 3 hours, depending on computer speed, working disk speed, and broadband internet speed, as well as the size and complexity of the configuration fileset. Package lists -------------- The primary supported method of acquiring software for Debian systems is the "apt" package manager. If the only source of software in the buiult image comes from the Debian repositories managed by apt, then all required recursive dependencies and potential conflicts between packages are taken care of at installtion time automatically. The live-build system incrporates a simple "package list" which specifies package names, in plaintext one line per package, which are intended to be installed on top of whatever the predesigned default packages might be assumed in the base build pattern. This is the easisest way for a user to add applications and programming support libraries and tools to the environment built into the ISO image. All specified binary packages are installed from the Debian repository in their current executable state at time of build. Therefore all fresh builds are inherently currently updated for all software versions. The user modifiable package list may be found as "config/package-lists/desktop.chroot" in the configuration fileset. Insertion of arbitrary software annd data outside of the package manager system -------------------------------------------------------------------------------- The Derbian software repository is vast, with thousands of available application and toolset packages available for installation by simply specifying their names. Even that abundance, however, might not meet a user's needs. Especially for programmers who wish to use alternate specialty tools, or even include their own locally compiled products into the running OS, there must be a way to get additional content into the built filesystem so that those extra applications or that special data is available during the booted live session. here's where the going gets complicated and off the prescribed Debian "rails". The Debian user's home folder is not actually stored directly in the live build configuration. The user's actual user name is specified in the live-build configuration (GLF alweys uses "user"). The home folder and its contents are generated on the fly with each boot, fresh and (usually for Debian official builds) fairly empty. GLF intentionally uses a facility to embed data into that startup home folder using the "/etc/skel" mechanism. Whatever data is found under the "/etc/skel" folder when the machine is booted is copied into the newly created user home folder before the first login session starts. The live-build system allows a configurtation to force data into the ISO image's generated filesystem by placing it into an OPTIONAL subfolder "config/includes.chroot" (this folder has changed in Debian 13 trixie to "config/includes.chroot_after_packages"). Any data, applications, confogurations, etc. under this subfolder are copied into any and all matching subfolders under the booted root filesystem. The "/etc/skel" folder os merely one such example -- any other folders may be specified, such as "/usr/local/bin" or "/usr/share/applications". Any such folder and data is directly built into the ISO image. They take up space in the image, but appear to the system at boot as any other files within the fiilesystem which may have been built by Debian design. The "/etc/skel" folder is justy another such built-in folder, but it is special in that its data is COPIED into the user's home folder at boot time. Live boot OS sessions do not (unless a user wishes) require the existence or alteration on any way of an installed hard drive. The entore live session runs entirrely from the compressed read-only data in the USB or DVD boot medium, within a RAMDISK facility which shares all available RAM between application RAM use and "pseudo hard drive" functions. The RAMDISK implements an overlay filesystem which is treated as read-write, even though the initial data is immutable and comes from a read-only boot medium. If any changes or user data modifies a "file" within this structure, it affects the RAM available and in use. Application code does not itself change during use, only its stored data. As a practical matter, most of the files built into the ISO image do not consume RAM in use. Only when new data is generated does the RAMDISK consume RAM to hold the changes. Therein lies the "rub" with data in "/etc/skel". Any data copied to the user home folder at boot time will also consume RAM, therefore shrinking the apparent available RAM for either "fake disk" or for applications.