💿 SlashOS Live

The actual build system and process I use to make SlashOS.

Based on the archiso releng profile (the same one used for official Arch ISOs), but with my own twists.

Setup | How It Works | Workflow | GitHub Actions | Customization

This is the source and process that bakes the SlashOS ISO from scratch.

🚀 What is this?

• The real SlashOS build system. This is what actually produces the ISO I use and ship.
• Uses archiso, for easy customization and building.
• Releng profile base, with my own packages, configs, and tweaks.

📂 What's Inside

• slashoslive/ — Main build root * airootfs/ — Your live system's root (/etc customizations) * packages.x86_64 — List of packages to include to the ISO * profiledef.sh — Main archiso profile config * efiboot/, grub/, syslinux/ — Bootloader configs * pacman.conf — Custom package repo config (also in airootfs/etc/pacman.conf) * Systemctl services to enable on boot for SlashOS experience

🛠️ Setup

1. Clone this repo
2. Install archiso (sudo pacman -S archiso)
3. Build your ISO: sh cd slashoslive sudo mkarchiso -v -r -w work -o out slashoslive
4. Find your ISO in out/

🧠 How It Works

Custom configs and carefully chosen packages work together with automatic systemctl services to deliver the full SlashOS experience.

🔄 Workflow

1. Edit: Change files in airootfs/, update packages.x86_64, or tweak boot configs.
2. Build: Run mkarchiso as above.
3. Test: Boot the ISO in a VM or on real hardware.
4. Iterate: Repeat until perfect.

🚀 GitHub Actions

This repository includes automated workflows to build the SlashOS ISO using GitHub Actions:

• Build ISO: Automatically builds the ISO monthly on the 1st of each month, or can be triggered manually via the "Actions" tab in GitHub. Creates a full release.
• Build ISO Preview: Automatically builds the ISO daily, or can be triggered manually. Creates a prerelease for testing latest changes.
• Both workflows use an Arch Linux container to run mkarchiso, ensuring a clean and reproducible build environment.
• Upon successful build, they create a new GitHub release (or prerelease) with the ISO file attached, tagged with the version extracted from the ISO name.

This ensures the latest version of SlashOS is always available as a release, without any costs, with daily previews for ongoing development.

🤝 Contributing

If you spot something weird or have a question, feel free to open an issue, or even a PR if you have improvements!

---

Just THE build system for SlashOS. Nothing more, nothing less.