| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
Wayland requires polkit for access to logind, the tty and the DRI
device.
|
| |
|
|
|
| |
Previously, cage would log to the TTY it was running on top of, so log
messages were basically lost.
|
| | |
|
| |
|
|
|
|
|
| |
Before whenever environment variables changed, pam files had to be
rebuild.
This is expensive since each file needs its own sandbox set up.
|
| |
|
|
| |
I cannot currently maintain this, as I don't have access to the hardware
running it anymore.
|
| |
|
|
|
|
| |
Without this, you don’t get any of the sessionVariables in the cage
application. Things like XDG_DATA_DIRS, XCURSOR_PATH, etc. are
missing.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since systemd 243, docs were already steering users towards using
`journal`:
https://github.com/systemd/systemd/commit/eedaf7f322a850c5d9f49346d43420423fc6f593
systemd 246 will go one step further, it shows warnings for these units
during bootup, and will [automatically convert these occurences to
`journal`](https://github.com/systemd/systemd/commit/f3dc6af20f410702beb8e45ddf77e92289fc90c7):
> [ 6.955976] systemd[1]: /nix/store/hwyfgbwg804vmr92fxc1vkmqfq2k9s17-unit-display-manager.service/display-manager.service:27: Standard output type syslog is obsolete, automatically updating to journal. Please update│······················
your unit file, and consider removing the setting altogether.
So there's no point of keeping `syslog` here, and it's probably a better
idea to just not set it, due to:
> This setting defaults to the value set with DefaultStandardOutput= in
> systemd-system.conf(5), which defaults to journal.
|
| |
|
|
|
| |
It doesn't belong into [Service]:
> Unknown key name 'ConditionPathExists' in section 'Service', ignoring.
|
|
|
Add a cage module to nixos. This can be used to make kiosk-style
systems that boot directly to a single application. The user (demo by
default) is automatically logged in by this service and the
program (xterm by default) is automatically started.
This is useful for some embedded, single-user systems where we want
automatic booting. To keep the system secure, the user should have
limited privileges.
Based on the service provided in the Cage wiki here:
https://github.com/Hjdskes/cage/wiki/Starting-Cage-on-boot-with-systemd
Co-Authored-By: Florian Klink <flokli@flokli.de>
|