Greetd: Difference between revisions
(suggest D-Bus session) |
(finish sentence) |
||
| Line 11: | Line 11: | ||
{{cmd|# apk add {{pkg|greetd}} <greeter>}} | {{cmd|# apk add {{pkg|greetd}} <greeter>}} | ||
You need to [[#Configuration|configure]] greetd before | You need to [[#Configuration|configure]] greetd before you can start it. | ||
Enable and start greetd: | Enable and start greetd: | ||
{{cmd|# rc-update add greetd | {{cmd|<nowiki># rc-update add greetd | ||
# rc-service greetd start</nowiki>}} | |||
== Configuration == | == Configuration == | ||
Revision as of 14:24, 29 February 2024
greetd is a minimal and flexible login manager daemon that makes no assumptions about what you want to launch.
This article focuses on alpine specific instructions. It is recommended to read the greetd wiki first.
Installation
greetd needs to be combined with a greeter. You can find a list of available greeters here: greetd-*. Install the main package and the greeter you selected:
# apk add greetd <greeter>
You need to configure greetd before you can start it.
Enable and start greetd:
# rc-update add greetd # rc-service greetd start
Configuration
Some graphical greeters (like gtkgreet) require seatd or elogind. Add rc_need=seatd or rc_need=elogind to /etc/conf.d/greetd.
For text based greeters you want to make sure that vt is set to 7 in /etc/greetd/config.toml. (This will be the default in alpine 3.20)
You might want to start a D-Bus session when the greetd session is started.