Updated Running Sway without systemd (markdown)

Scott Anderson 2020-04-29 09:03:57 +00:00
parent 750e11be1e
commit 02a9f0c3a4

@ -32,31 +32,6 @@ chmod +s /usr/bin/sway
Sway will fork into a minimal slave process to keep these privileges, while dropping its own. As with any program, using setuid has serious security implications.
# Direct via capabilities
_Note: Attempting to run sway this way without this being configured correctly will probably leave your computer in an unresponsive state, requiring a reboot_
_Note: Sway won't drop capabilities, use setuid instead._
In order to use this, wlroots must be compiled with `libcap` support:
```
meson build -Dbuildtype=debugoptimized -Dlibcap=enabled
ninja -C build
sudo ninja -C build install
```
In order to run, sway needs permissions to open `/dev/dri/card*` and `/dev/input/event*`.
Add the user you will be running sway as into the `video` and `input` groups.
Sway also requires the `CAP_SYS_ADMIN` capability in order to take control of your GPU correctly.
You must add this capability to the sway executable:
```
setcap cap_sys_admin=eip /usr/bin/sway
```
_Note: `CAP_SYS_ADMIN` is a very serious capability to give a process, and can be considered as powerful as root itself. See [here](https://lwn.net/Articles/486306/) for some more background._
# Tips and Tricks
## Archlinux without systemd/elogind