This enables systemd-oomd by default and provides some default
configuration for system.slice and for all slices that run under user.
This default slice config is inspired by what Fedora ships,
which seems like a sensible default for us to start with. Units/slices
within these two top-ish level slices can set their own limits and
actions if they want.
The package name was missing the -systemd suffix, causing it to conflict
with the real polkit-kde-agent-1 package.
[ci:skip-build]: already built successfully in CI
pam_dump_runtime_dir isn't needed with systemd. if a user install this
module, this might break with logind integration..
[ci:skip-build]: already built successfully in CI
There are some notable changes:
- systemd-journal-upload is now available, but not tested
- pam files now live under `/usr/lib/pam.d`. users can easily override
configuration by putting files under /etc/pam.d with the same name.
- journalctl should now work for `wheel` groups without privilege
esclation to root. ACLs' for /var/log/journal should hopefully be
set correctly now.
- /bin/udevadm /sbin/{init,udevd} are now provided by the APKBUILD itself
- The split-usr backport lives now in the downstream release.
The current -systemd subpackage isn't getting installed due to the
invalid install_if statement. As abuild's fork in pmOS for systemd
specifies a default_systemd() and systemd() function, overriding it
here isn't needed.
The -systemd subpackage contains configuration for gnome-session in
systemd mode.
- By placing a file into systemd/user/gnome-session@phosh.target.d,
we generate a valid gnome-session@phosh.target.
- The first invokation of gnome-session by phosh-session includes
the arg `--session phosh`. When gnome-session sees a running
systemd user manager via dbus, it will signal to systemd to start
`gnome-session@phosh.target`.
As we switched to tinydm/autologin for phosh on systemd-edge, this
will only work when autologin also tries to load pam_systemd.so.
[ci:skip-build]: already built successfully in CI
kded currently doesn't start with the session, but when I rename the systemd unit file to plasma-kded6.service, it starts automatically.
[ci:skip-build]: already built successfully in CI
I evaluated using systemd/zram-generator but decided against it for the following reasons:
1) it was more difficult to configure using the existing deviceinfo var
we have for zram_pct, this meant that we would ultimately couldn't have
a consistent way to configure zram stuff for all supported init systems
2) it's a Rust app, and was failing to build in CI for armv7, riscv64,
and armhf with some weird qemu crashes, failed tests, etc
3) zram-init Just Works, upstream ships a unit file for it so they
support running under systemd already
[ci:skip-build]: already built successfully in CI
Also add config to rmtfs so systemd starts stuff in the correct order.
I added the msm-modem unit here instead of in pmaports/modem/msm-modem
because systemd-services handles creating boilerplate install scripts
automatically.
fixes#3451
[ci:skip-build]: already built successfully in CI
- hexagonrpcd-adsp-rootpd should only be started if valid config exists
for it, e.g. provided by device pkgs
- For devices with a CDSP: only the -adsp-rootpd and -sdsp services should
be started.
- For devices with only an ADSP: only -adsp-rootpd and -adsp-sensorspd
should be started.
This also stops the hexagonrpcd-adsp-sensorspd on suspend, attempting
to work around some issue wrt sargo that is implemented in openrc (see
fe00027849)
[ci:skip-build]: build tested locally since alsa-ucm conflicts prevent
build testing in CI
Matching the openRC ones. Also make use of the hexagonrpcd_fw_dir env var
and reuse the correcponding conf files, making it easier to support
both init systems.
