Ryan Hughes 3a91cf780c orchestrator: install Limine ourselves; stop creating arch-limine entries to delete later
archinstall's add_bootloader creates EFI/arch-limine/{BOOTX64.EFI, BOOTIA32.EFI}, writes a limine.conf with an Arch Linux entry, and registers an efibootmgr label "Arch Linux Limine Bootloader" — only for limine-snapper.sh to delete it all and rebuild with Omarchy branding via limine-mkinitcpio-hook.

Replace the add_bootloader call with _install_limine_omarchy, which does the same work archinstall's _add_limine_bootloader does (UEFI EFI binary copy + efibootmgr register, or BIOS limine-bios.sys + limine bios-install) but with Omarchy-owned paths and labels from the start:

  - EFI subdir:    EFI/limine          (not EFI/arch-limine)

  - efibootmgr:    label "Limine"      (not "Arch Linux Limine Bootloader")

  - loader path:   \EFI\limine\BOOTX64.EFI

Compute the kernel cmdline directly from disk_config instead of harvesting it from a file archinstall wrote (whose path keeps drifting across versions). Then write /etc/default/limine and /etc/kernel/cmdline, and stage /boot/limine.conf from our styling template — limine-mkinitcpio-hook will add the actual boot entries when it deploys.

Adds limine + efibootmgr to EARLY_PACKAGES (archinstall used to pacstrap these as a side effect of add_bootloader).

Does not modify limine-snapper.sh — its cleanup code will simply no-op because there are no arch-limine paths or "Arch Linux Limine Bootloader" entries to find. That code can be pruned in a follow-up.
2026-05-21 21:57:50 -04:00
2025-11-26 01:29:16 -05:00
2026-04-30 13:51:08 +02:00
2025-08-15 09:38:30 +02:00
2025-07-27 15:21:01 +02:00
2026-04-16 16:10:50 +02:00

Omarchy ISO

The Omarchy ISO streamlines the installation of Omarchy. It includes the Omarchy Configurator as a front-end to archinstall and automatically launches the Omarchy Installer after base arch has been setup.

Downloading the latest ISO

See the ISO link on omarchy.org.

Creating the ISO

Run ./bin/omarchy-iso-make and the output goes into ./release. You can build from your local $OMARCHY_PATH for testing by using --local-source or from a checkout of the dev branch (instead of master) by using --dev.

Environment Variables

You can customize the repositories used during the build process by passing in variables:

  • OMARCHY_INSTALLER_REPO - GitHub repository for the installer (default: basecamp/omarchy)
  • OMARCHY_INSTALLER_REF - Git ref (branch/tag) for the installer (default: master)

Example usage:

OMARCHY_INSTALLER_REPO="myuser/omarchy-fork" OMARCHY_INSTALLER_REF="some-feature" ./bin/omarchy-iso-make

Testing the ISO

Run ./bin/omarchy-iso-boot [release/omarchy.iso].

Signing the ISO

Run ./bin/omarchy-iso-sign [gpg-user] [release/omarchy.iso].

Uploading the ISO

Run ./bin/omarchy-iso-upload [release/omarchy.iso]. This requires you've configured rclone (use rclone config).

Full release of the ISO

Run ./bin/omarchy-iso-release VERSION to create, test, sign, and upload the ISO in one flow. Add --rc to release an RC build instead.

S
Description
Omarchy ISO with the Chinese installer. Fork of omacom/omarchy-iso.
Readme MIT
2 MiB
0 Stars 1 Watchers 0 Forks
Languages
Shell 61%
Python 39%