Explain why archinstall's zram-generator.conf gets dropped
omarchy-settings now ships the tuning as a vendor drop-in that outranks the main config file, so setup_swap's /etc copy decides nothing and is removed only to keep /etc free for the local admin. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LjeyQZsNBxqyYy9z8KaKm7
This commit is contained in:
1 parent
529001d566
commit
436f37f926
1 file changed
+5
-6
@@ -570,12 +570,11 @@ DEFERRED_BOOT_HOOKS = (
|
|||||||
def _drop_archinstall_zram_conf(ctx: InstallContext) -> None:
|
def _drop_archinstall_zram_conf(ctx: InstallContext) -> None:
|
||||||
"""Remove the zram-generator.conf archinstall's setup_swap writes directly.
|
"""Remove the zram-generator.conf archinstall's setup_swap writes directly.
|
||||||
|
|
||||||
omarchy-settings now ships its own /etc/systemd/zram-generator.conf as a
|
omarchy-settings ships the tuning as a vendor drop-in at
|
||||||
packaged file. setup_swap writes a generic config to that same path before
|
/usr/lib/systemd/zram-generator.conf.d/90-omarchy.conf, which outranks the
|
||||||
we pacstrap omarchy-settings, so pacman aborts the transaction with a file
|
main config file. setup_swap's generic /etc copy decides nothing and only
|
||||||
conflict ("zram-generator.conf exists in filesystem"). Delete archinstall's
|
implies /etc is where zram gets configured, so drop it — we still want the
|
||||||
copy here — we still want the zram-generator package and service that
|
zram-generator package and service that setup_swap installs.
|
||||||
setup_swap installs, but omarchy-settings' config is the one to keep.
|
|
||||||
"""
|
"""
|
||||||
zram_conf = ctx.target / "etc" / "systemd" / "zram-generator.conf"
|
zram_conf = ctx.target / "etc" / "systemd" / "zram-generator.conf"
|
||||||
zram_conf.unlink(missing_ok=True)
|
zram_conf.unlink(missing_ok=True)
|
||||||
|
|||||||
Reference in new issue
Block a user