SteamOS Manager is a system daemon that aims to abstract Steam's interactions with the operating system.
Find a file
2024-05-15 23:35:01 +00:00
data data: Split user and system data files into respective directories, add user D-Bus unit 2024-05-06 13:26:40 -07:00
src steamosctl: Give human-readable results for property names 2024-05-13 18:55:38 -07:00
.gitignore Merge steamos-workerd in 2024-03-22 19:31:38 -07:00
.gitlab-ci.yml Move CI to isolated runner(s) 2024-05-07 13:42:15 +01:00
Cargo.lock Cargo.toml: zbus 4.2.1 is out, fixes needed issue 2024-05-14 18:09:54 -07:00
Cargo.toml Cargo.toml: Tag 24.5.1 2024-05-14 18:10:17 -07:00
com.steampowered.SteamOSManager1.xml process: Improve signal handling, don't wait for process in exit_code 2024-05-08 16:39:14 -07:00
HACKING.md Use more standard filenames 2024-03-22 19:26:26 -07:00
LICENSE Add support to get/set WiFi back-end 2024-04-04 18:08:21 -07:00
README.md Update the README file with how things have changed lately. 2024-05-15 08:30:09 -06:00

This is the SteamOS Manager.

It is a small daemon that's sole purpose is to give Steam something with a DBus api that runs as root and can do things to the system without having to have hard coded paths and DBus apis in the Steam client itself.

It is a mostly thin wrapper around other scripts and DBus apis that provides feedback for each DBus method it implements.

How it works:

The SteamOS Manager runs as root and exposes a DBus api on the system bus. Another instance runs as deck user and exposes a DBus api on the session bus with a few extra methods. These methods run directly in the user daemon as deck user. All other apis forward to the root daemon via it's DBus api.

To add a new method:

To add a new method that doesn't require root privileges add it to the user daemon's DBus api directly.

To add a new method that does require root privileges add it to the root daemon's DBus api and it will be exposed automatically in the user daemon.