How SLICK Linux OS (Simple LInux Customizer Kit) slickA07_amd64 is COMPLETELY self-rebuildable           20261022 GLF
----------------------------------------------------------------------------------------------------------------------

This specific demonstration remix of Debian MATE Linux OS uses an extremely self-referential trick to make it completely self-rebuildable.  That is, if you boot this OS, from either a DVD+R or from a USB stick using a PC running an x86_64 (amd64) processor, you will have all the necessary software tools to have a useful working live boot operating system (which does not require the computer to even HAVE an installed hard drive, let alone alter it).  Because that OS also includes all the necessary tools to download, install, and rebuild an entirely new copy of iteself with updated and upgraded package components, it is self-rebuildable.

The requirements to perform this self-rebuild of SLICK are modest:

  A 64-bit (AMD64 or x86_64) PC with at least 2Gb RAM, preferably 4Gb or more
  Access to the internet, preferably using an Ethernet cable, but most WiFi is supported
  An external USB-pluggable work drive, preferably SSD for speed, with at 64 Gb or more free space
  
By following a defined set of procedures using the Debian-supported "live-build" system, one may create an ISO image of a live bootable DVD or USB flash operating system.  By default, this live build system can boot using ONLY the available RAM as a pseudo-hard drive, and does not require permanent installation.  This is ideal for casual testing or for "Vegas Rules" day-to-day activity (what happens in Vegas stays in Vegas).

Debian itself releases similar official live boot OS images which contain much of the same basic content, but which have NOT been specifically curated to perform the specific rebuilding process supported by SLICK and other GLF OS variants.  The official Debian releases are produced using essentially the same build process, but contain only those packages which the Debian maintainers choose to release into that image.  The advantage of using a live-build remix is that the user may add and subtract application packages and/or other local files which fill out a truly customized OS specific to that user's needs.  This rebuild process runs a set of highly engineered scripts to download all the necessary binary packages fom Debian repositories within a sandboxed (chroot) environment, building an entirely new version, perhaps even with a newer update of the Linux kernel, into a bootable ISO image file.

GLF (Gary L. Flispart) has performed such builds for many years across several biennial releases of Debian, and of Linux Mint before that.  From experience and much trial and error, GLF has established a set of practices which extend somtimes quite far from the original scripted nature of the live-build system, but still fully valid and supported by it.  These extensions allow forcing the behavior of the initial user's view of the OS, and what files are found in the home folder at boot.  Some of these changes are ideosyncratic to GLF, but any may be changed by rebuilding using an edited configuration fileset.

The live-build system is intended to be run from a set of configuration files and folders which by design may be created by careful and repeated application of the live-config application form command-line scripts.  The highly structured filesets, once constructed, are then used to drive the live build process.  There are several places within this configuration fileset where a user may impose changes to the base files set by live config scripts.  Some files are simply edited with a text editor, other changes involve placement of certain files in specific places.  The entire configuration fileset may be preserved across builds by compressing into a *.tar.gz archive.  When the archive is unpacked, it can be then used as the base for a new rebuild.  Usually certain key files and values should be edited to rename the remix to distinguish it from older versions, then the new configuration is recompressed for reuse on the next rebuild.
  
The SLICK OS remix is intended to be a fully rebuildable, somewhat minimalist demonstration variant which is small enough to fit on a bootable DVD.  This is a tight fit in recent years. The core OS now barely fits into the 4.7Gb limit for standard DVD-R+ images.  SLICK has been carefully pared down to just fit.  The advantage for DVD distribution is that it is unquestionably read-only, so new users can trust it has not been altered.  It is however slow to use, and many newer systems no longer have built-in DVD readers.  The ISO images work well on most modern 64-bit PCs, and can be booted either in legacy (BIOS) or EFI mode.  USUALLY Secure Boot is supported, but that may depend on the specific computer's settings and history of security certificates (an issue arose in 2026 where Microsoft changed certificates and expired older ones, which MIGHT be a problem for specific users).
  
In general, the compressed configuration filesets necessary to rebuild a specific OS remix are stored on other media, and must be acquired or reconstructed from scratch by a prospective user.  SLICK is special in that a trick of file placement in the configuration files was implemented.  There was just enough room left within the available 4.7Gb limit for DVD images to fit a copy of the configuration fileset itself.  That makes the SLICK OS recursively self-referential.  The configuration fileset includes its own configuration inside in a location intended to be available to the OS user from inside the OS itself.

That trick makes SLICK truly self-rebuildable, since all you need to rebuild is included within the OS boot session itself.  In a booted session, the user can navigate to /run/live/medium to see the raw DVD contents.  Within that folder, under the "boot" folder should also be a *.tar.gz file which includes the configuration for the rebuild of itself.  Unpack that to a EXT4 format (Linux filesystem) work drive and you can proceed to rebuild an updated copy of SLICK. 


Recompressing an edited SLICK configuration set
------------------------------------------------

NOTE that the configuration fileset itself (slickA07_amd64.tar.gz) is compressed WITHOUT the extra copy within config/includes.binary/boot.  SLICK is the only GLF-supported OS variant small enough to have room to hold its own configuration. Most variants have quite large configuration sets, because they hold local versions of files and applications to install into the live filesystem.  SLICK is just small enough to fit the configuration into the ISO. 

   FIRST,    unpack the configuration fileset to the work drive, making a folder "slickA07_amd64".  
   SECOND,   change the name of that folder to reflect the change in version number (e.g. slickA07_amd64 to
             slickA08_amd64). 
   THIRD,    edit any changes, especially config/binary and /config/common (change version name of variant from 
             slickA07 to something else), and config/includes/binary/isolinux (change the splash screen to reflect 
             version number A07 to something else).  
   FOURTH,   recompress the whole folder using "compressdir" script (the GUI app Engrampa is OK to extract, 
             but compressing the folder with it might mess up certain symlinks).  

             Example:  go to parent folder of "slickA08_amd64" in terminal and execute:

                compressdir slickA08_amd64

   FINALLY,  assuming that the folder "slick08_amd64" still exists as the new configuration top level folder, 
             COPY the new file "slickA08_amd64.tar.gz" to the subfolder config/includes.binary/boot.  When that 
             top level configuration set is now used, the contents of "boot" will be preserved in the ISO image, 
             and therefore the USB or DVD medium, so SLICK will hold its own configuration and be self-rebuildable
             (look under /run/live/medium/boot).
             
For all other custom edits of configuration fileset for other OS variants, skip the final step with the extra copy 
of the compressed configuration set.  Otherwise the confguration sets will be quite a lot larger than needed.  Some OS variants already take up as much as 70 Gb of temporary space on the work drive while rebuilding.
 
