summaryrefslogtreecommitdiffstats
path: root/init-systemd (follow)
Commit message (Collapse)AuthorAgeLines
* init-systemd: Bring in line with 23.0 hardened/systemd profilesWolfgang Müller2024-03-23-4/+0
| | | | | With the upstream addition of hardened/systemd profiles, we no longer have to set these settings manually.
* init-systemd: Enable 'kernel-install' for systemdWolfgang Müller2023-12-01-1/+1
|
* init-systemd: Enable boot USE flagWolfgang Müller2023-11-01-1/+1
| | | | | We use systemd-boot and bootctl on at least one machine with the init-systemd profile, so enable it here.
* init-systemd: Mask the 'split-usr' USE flagWolfgang Müller2023-06-11-0/+1
|
* init-systemd: Disable fido2Wolfgang Müller2023-05-02-1/+1
| | | | | | | Because of [1] this will now pull in cryptsetup. Since there's no point in having fido2 enabled without it for now, we can simply disable it. [1] https://bugs.gentoo.org/902831
* init-systemd: Enable tpm and fido2 USE flags for sys-apps/systemdWolfgang Müller2022-11-08-1/+1
| | | | | We have at least one machine with both a TPM chip and a FIDO2 device. It shouldn't hurt enabling this for every systemd-based system we have.
* init-systemd: Remove 'cryptsetup' and 'fido2' USE flagsWolfgang Müller2022-04-28-1/+1
| | | | | These are not needed in the general case and should instead be enabled in a host-specific profile.
* Rename group-systemd to init-systemdWolfgang Müller2022-04-28-0/+34
This more clearly describes what this profile does.