diff options
| author | Craig Jennings <c@cjennings.net> | 2026-07-20 23:30:56 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-07-20 23:30:56 -0500 |
| commit | e0d22bd8250d27438c9cd4c6a0c7f9e1abddff46 (patch) | |
| tree | 27beb4c951923591441277e1ae5fe5a4bce4193d /working/clock-display-references | |
| parent | cfcac2e06d43e6e757b1be9d6449891332848bce (diff) | |
| download | archsetup-e0d22bd8250d27438c9cd4c6a0c7f9e1abddff46.tar.gz archsetup-e0d22bd8250d27438c9cd4c6a0c7f9e1abddff46.zip | |
fix(installer): rebuild initramfs after the nvme MODULES edit
The nvme early-load edit landed in mkinitcpio.conf, but the only nearby mkinitcpio -P ran behind an is-not-zfs-root gate. On ZFS-root machines (all of mine) the hardening was never compiled into the initramfs, which is exactly the case the early load exists for. The extracted ensure_nvme_early_module now rebuilds whenever it changed the file, and skips the rebuild on an unchanged conf so a resume stays idempotent.
The already-present check also grepped the whole file for "nvme", so a comment or nvme_tcp anywhere skipped the edit. It now checks for the nvme word on the MODULES line only.
Diffstat (limited to 'working/clock-display-references')
0 files changed, 0 insertions, 0 deletions