Skip to main content

🌍 The Universal Strategy

The Universal Strategy is the philosophical and technical framework guiding the development of oa-tools. The core principle is simple: a remastered Linux system (an "egg") must be able to hatch on any hardware and in any environment, regardless of the "mother" distribution it was generated on.

This strategy turns remastering from a mere carbon copy into the creation of agnostic, resilient, ready-to-use systems.

1. The Pillars of Resilience​

1.1 Hybrid, monolithic boot (the "hermaphrodite" egg)​

Bootloader compatibility is challenge number one. To guarantee maximum interoperability without the bureaucratic complications of digital signatures, we adopt a policy of Universal Pragmatism:

  • Full equipment: every egg ships the binaries for both Legacy BIOS (grub-pc-bin) and UEFI (grub-efi-amd64-bin, efibootmgr).
  • Monolithic choice: we use the Debian-derived grub-monolithic-efi: a single pre-compiled binary with all the necessary modules, guaranteeing stability and fast loading.
  • Beyond Secure Boot: we consciously renounce the Secure Boot signing chain in favor of kernel and module customization freedom (essential for systems with ZFS or custom drivers). Compatibility is guaranteed on every machine once Secure Boot is disabled in the firmware.
  • Independence from the generator: if you hatch an image on a modern UEFI laptop, the resulting egg will still boot on an old BIOS PC from 2010. The system carries the "genes" for every possible firmware.

1.2 Universal autologin and access​

Instead of fighting each distro's specific PAM configuration, we use a structured bypass (e.g. LightDM or session scripts) guaranteeing automatic access to the live session, so the user always lands on the desktop without friction.

1.3 The "Secret Agent" (desktop independence)​

The system must not fear the Desktop Environment. Through automated background scripts, it recognizes the environment (XFCE, GNOME, KDE, …) and dynamically authorizes the .desktop launchers (such as the installer). This eliminates the file manager security warnings and guarantees a smooth UX everywhere.

1.4 Responsive design ("premium" UI)​

The installation interface adapts dynamically. Thanks to mathematical containers in the Calamares QML, images and text scale perfectly, avoiding empty borders or clipped text on monitors with different resolutions.

2. The Template Architecture​

The universal strategy is made possible by a templating system (Go text/template) living in brain.d:

A. base.yaml.tmpl (the declarative DNA)​

The source of truth. Here we define the abstract characteristics of the system:

  • The remastering plan: the full sequence of steps, written once for all distributions.
  • Global branding: the ISO name (VOL_ID), theme colors and support URLs, defined in a single centralized place.
  • Total abstraction: no distro-specific if/else clauses. When it reaches a critical point, it simply invokes a hook (e.g. distro_initramfs_cmd, distro_hook_squashfs, distro_hook_install_logic).

B. Distro modules (modules/<distro>.bash.tmpl)​

These are the "impedance adapters" — currently alpine, arch, debian, fedora, manjaro, opensuse. They translate the universal hooks into the local dialects:

  • Initramfs handling: the differences between mkinitcpio (Arch), dracut (Fedora), initramfs-tools (Debian) and so on.
  • Structural quirks: local oddities, such as building the Arch-specific boot hierarchy (arch/x86_64/airootfs.sfs) from the standard filesystem generated by the engine.

C. index.yaml (the matchmaker)​

Maps each distribution ID (and its ID_LIKE relatives) to the right profile, so that derivatives like Pop!_OS, Kali or Nobara automatically inherit the correct module.

3. Scalability and Future​

Thanks to this architecture, oa-tools is not tied to the present. The Universal Strategy makes it possible to:

  • Support new distros: adding a distribution only requires writing a new modules/<distro>.bash.tmpl, without touching the Go core.
  • Explore hardware: the separation between logic and implementation opens the way to different architectures (such as the arm64 and RISC-V ports), where the binaries change but the hatching strategy stays the same.

In short: the Universal Strategy turns the fragmentation of the Linux world into a competitive advantage, creating a remastering standard that is, by definition, universal.