Installation without `suid` for `hikari` is now the new default

`seatd` and similar mechanisms are present on all relevant platforms.

Makefile

@@ -114,10 +114,10 @@ CFLAGS += -DHAVE_SCREENCOPY=1
 CFLAGS += -DHAVE_LAYERSHELL=1
 .endif
 
-.ifdef WITHOUT_SUID
-PERMS = 555
-.else
+.ifdef WITH_SUID
 PERMS = 4555
+.else
+PERMS = 555
 .endif
 
 .ifdef WITH_VIRTUAL_INPUT

README.md

@@ -199,16 +199,13 @@ number that will be spliced into the manpage. The distribution tarball of
 `hikari` comes with a precompiled manpage removing the need for a `pandoc`
 installation.
 
-#### Installing without SUID
+#### Installing with SUID
 
-`hikari` requires root privileges during startup on BSD systems to initialize
-the `wlroots` backend, those are dropped as soon as possible. If you don't
-happen to need this you can prevent installation from setting this bit by
-issuing `WITHOUT_SUID`. (SUID is still set for `hikari-unlocker` to allow
-communication with PAM, which is required for password authentication)
+If `hikari` should require root privileges for startup, state `WITH_SUID=YES`
+during installation.
 
 ```
-make WITHOUT_SUID=YES install
+make WITH_SUID=YES install
 ```
 
 #### Building a DEBUG build

UPDATING.md

@@ -1,5 +1,10 @@
 ## 2.0.0
 
+### 20201210
+
+* `suid` for `hikari` is no longer the default. We rely on `seatd` or similar
+  mechanisms.
+
 ### 20200509
 
 * f4c376ec920298361ccb3beb6031eef5c5dd7c39 adds the `ui` section to the