0a2590256e
- Kernel snapshot, patch and guard now match the running 7.2.10-fiw-nyx-v1.2. - Overlay install replaces the tree instead of merging, so removed ebuilds cannot linger next to a newer Manifest; the old tree is restored on failure. - Limine refresh removes ESP kernel folders the managed menu no longer lists. - ESP discovery checks fstab FAT mounts, triggers x-systemd.automount and ignores the autofs placeholder.
89 lines
4.5 KiB
Markdown
89 lines
4.5 KiB
Markdown
# Optional bootloader deployment
|
|
|
|
`keep` is the default. Limine and GRUB have separate package choices; kernel
|
|
selection remains independent. Selecting a loader does not itself deploy it.
|
|
Use the final preview's **b** action or include it in **r** full restore.
|
|
|
|
## Preview and apply
|
|
|
|
```sh
|
|
./install --selection local/selection.json --boot-plan
|
|
sudo ./install --selection local/selection.json --deploy-bootloader
|
|
# Specify a mounted ESP when automatic discovery does not find yours:
|
|
sudo ./install --selection local/selection.json --deploy-bootloader --esp /boot/efi
|
|
```
|
|
|
|
Discovery checks `/efi`, `/boot/efi`, `/boot` and FAT mount points from
|
|
`/etc/fstab` for the GPT ESP type and FAT filesystem. An `x-systemd.automount`
|
|
ESP is mounted by accessing it first. The plan shows the selected partition, root
|
|
filesystem, kernel arguments, installed kernel/initramfs candidates and
|
|
proposed loader config or commands. UUIDs are derived on the target and kept
|
|
in its local state; they are not shipped in the repo.
|
|
|
|
Firmware registration has three choices:
|
|
|
|
| Choice | Effect |
|
|
|---|---|
|
|
| keep | Leave current firmware entries and BootOrder unchanged |
|
|
| add | Create an entry without adding it to BootOrder |
|
|
| default | Register the selected loader first in BootOrder |
|
|
|
|
The final deployment confirmation follows the target and firmware preview.
|
|
Existing matching firmware entries are reused when their partition and EFI
|
|
path match. Other entries are retained. No reboot is performed.
|
|
|
|
## Limine
|
|
|
|
The loader goes to `EFI/Fiw-Gentoo/BOOTX64.EFI`, with `limine.conf` beside it.
|
|
Versioned kernels and initramfs files are copied below that directory so
|
|
Limine can read them from the ESP. Custom Fiw/Cachy kernels appear first,
|
|
followed by generic kernels, including an installed binary fallback.
|
|
|
|
A marked block contains the generated Gentoo entries. Entries outside that
|
|
block are preserved. Locally edited managed entries receive a `.new` proposal
|
|
instead of being overwritten. ESP free space is checked before copying kernel
|
|
artifacts. Once the managed menu is current, kernel folders it no longer lists
|
|
are removed from the ESP; folders with other files are left alone. The protocol and paths follow the upstream
|
|
[Limine configuration reference](https://github.com/limine-bootloader/limine/blob/v12.x/CONFIG.md).
|
|
|
|
## GRUB
|
|
|
|
`grub-install` uses `--target=x86_64-efi`, a dedicated `Fiw-Gentoo` EFI ID,
|
|
`/boot/fiw-gentoo` as its boot directory and `--no-nvram`. Firmware changes are
|
|
handled separately by the selected registration choice.
|
|
|
|
The generated menu lives in `/boot/fiw-gentoo/grub/grub.cfg`. A temporary output
|
|
is generated before replacing it. If the previous menu was edited locally,
|
|
the new menu becomes a `.new` proposal. Existing `/etc/default/grub` settings
|
|
are used by `grub-mkconfig`.
|
|
|
|
Explicit deployment asks before replacing a conflicting GRUB menu or Limine
|
|
managed block, with a backup. Keeping it writes a proposal and leaves firmware
|
|
registration and order unchanged. Automatic kernel refreshes preserve edits
|
|
without prompting; review their proposals before using the new entries.
|
|
|
|
## Kernel updates and backups
|
|
|
|
Deployment installs a standalone refresh helper at
|
|
`/usr/local/libexec/fiw-dots-boot`, a systemd kernel-install hook and a
|
|
traditional Gentoo installkernel post-install hook. The active installkernel
|
|
configuration uses the compat layout and Dracut. Missing initramfs files are
|
|
generated when needed. Each refresh verifies the ESP is still mounted and
|
|
updates only the selected loader's managed menu.
|
|
|
|
The systemd remove hook excludes the removed kernel from its generated menu.
|
|
The legacy post-install hook refreshes after additions. Deployment saves
|
|
local boot state under `/etc/fiw-gentoo-dots/boot.json`; backup files and reports
|
|
live under `/var/lib/Fiw-Gentoo-Dots`. No existing disk partition is formatted.
|
|
|
|
Automatic deployment currently supports amd64 UEFI, GPT ESPs, plain ext4/Btrfs
|
|
roots and unsigned boot. Encrypted, UKI-only, BIOS and signing workflows can
|
|
keep their existing loader. Secure Boot being active stops unsigned deployment
|
|
before changes. Automatic GRUB and Limine deployment and booting were checked
|
|
in Gentoo QEMU/KVM with ext4 and a Btrfs `@` root. The custom Ryzen kernel and
|
|
binary fallback booted, and addition/removal hooks and preservation of edited
|
|
menus were checked. Physical firmware and unsupported storage layouts still
|
|
need their own setup.
|
|
|
|
`optional/fiw-cachy-patch` refreshes the custom kernel patch; it does not select
|
|
a bootloader. See the [helper list](scripts.md) before using it.
|