You are not logged in.
Suppose, for example, that I want to configure Systemd's behavior on pressing the machine's power key for all personal Archlinux machines (two laptops in my case).
Creating a file like this in /etc/systemd/logind.conf.d is enough to configure Systemd:
[Login]
HandlePowerKey=suspend
To make this scale across separate machines, I could create a package that would contain this configuration file in /etc/systemd/logind.conf.d, and other ones, too.
This approach has a fatal flaw, though: suppose I want to change my xinit configuration or my vim configuration, so I'm modifying /etc/X11/xinit/xserverrc or /etc/vimrc; I can't do this with a package because the files are already owned by existing packages (xorg-xinit or vim-runtime, in this example).
Any ideas?
Offline
Those are user specific configs anyway and if you want to supply the user w/ a default config on user creation, that's for /etc/skel - or a very popular fashion is to abuse github for that and manage your user configs ("dotfiles") through git.
Offline
Ansible.
Mod note: not Arch discussion, moving to System Administration
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
I'd say system files with "system config packages" and/or config management tools like Ansible, Salt, ….
User configuration with Git or any other VCS (see "dotfiles" in the Arch Wiki or anywhere else online).
Xinit and Vim configuration (and other similar things) are user config, and ideally you don't touch system files for that.
Last edited by ayekat (2022-04-29 10:38:15)
Offline
The relevant wiki links are
Offline