About
Why this shape
- Chimera Linux’s own userland is BSD (
chimerautils), on top of the Linux kernel — the “hybrid” is real, not just a name. dinithandles init, with per-package<pkg>-dinitsubpackages (greetd-dinit,udiskie-dinit,networkmanager-dinit, …). Not every service self-enables on install —dbusandeloginddo,polkit,networkmanager,seatd,rtkitandsyslog-ngdon’t, soh77-installerenables the ones actually present right after install.- Waybar, not yambar — ported from an already-working sway config after yambar showed real bugs on actual hardware (a hardcoded battery name, unreliable refresh, the wireless module going blank).
- No greeter, by design: a plain
gettyprompt into a shell that execs Sway via.profile, matching Void’s and Chimera’s own convention.anon/chimeraandroot/chimeraare Chimera’s own shipped defaults, left untouched.
Layout
vendor/chimera-live/ vendored fork of chimera-linux/chimera-live
(mklive.sh), patched with a "sway" case
vendor/chimera-install-scripts/ vendored, patched chimera-installer:
Groups + Services checklists, Partition +
Filesystems, Network (nmtui) and Keymap
pkg/h77-dots/ general app dotfiles (/etc/skel)
pkg/h77-sway-dots/ sway/waybar/swaylock/swaync dotfiles
pkg/h77-installer/ thin wrapper around the patched installer
pkg/h77-install-scripts/ cports package for the patched installer
iso/mklive-d77.sh builds the "sway" live ISO variant
container/ Containerfile(s) for both build stages
Build
Two containers, in order: cbuild builds pkg/h77-* into real .apk
files (it refuses to run as root); the ISO container then consumes those
and runs mklive.sh (needs root, for mount(8)).
./build.sh # both containers, in order -> iso/*.iso
Or, on a Chimera/hybrid-d77 host already, skip the containers and run
iso/mklive-d77.sh directly once cbuild-out/hybrid/ is populated —
either build the packages yourself via cbuild, or fetch CI’s
already-built ones with iso/fetch-pkgs.sh.
See the project’s own README for the full, step-by-step build instructions.