... | ... | @@ -54,9 +54,42 @@ It just needs a bit more cleanup and refactor. |
|
|
|
|
|
See bug report (wherever it is). Almost certainly just bug
|
|
|
|
|
|
# Future work
|
|
|
# Future work
|
|
|
|
|
|
The units provided now are very barebones aimed at just working with the current system.
|
|
|
Next we can add in some namespaces to provide some security on features that don't need it, OOM hints, as well as potentially hard CPU/memory limits and weights.
|
|
|
|
|
|
|
|
|
If you have ideas and suggestions please let me know. |
|
|
\ No newline at end of file |
|
|
If you have ideas and suggestions please let me know.
|
|
|
|
|
|
# Internals / Adding services
|
|
|
|
|
|
Startup can be summarised as being:
|
|
|
|
|
|
plasma-core.target
|
|
|
plasma-workspace@.target
|
|
|
graphical-session.target
|
|
|
|
|
|
plasma-workspace@ is the target explicitly activated.
|
|
|
|
|
|
## X11 and wayland
|
|
|
|
|
|
plasma-workspace@ is a template file that ends with x11 or wayland. That will then require the correct kwin_
|
|
|
startup order can be different between the two.
|
|
|
|
|
|
## Wants & Order
|
|
|
Note that in systemd dependencies (wants/wantedby) counter-intuitively do not determine order.
|
|
|
|
|
|
plasma-workspace wants graphical-session, meaning it will make it something started by it, but it also explicitly comes before graphical-session.
|
|
|
|
|
|
The order of events is:
|
|
|
plasma-core does anything that adjusts environment variables
|
|
|
plasma-workspace@ starts all runtime services
|
|
|
graphical-session is at a point where everything including runtime services are up
|
|
|
|
|
|
## Adding a new service
|
|
|
|
|
|
If something is /required/ by a working session place it in the WantedBy of plasma-core or plasma-workspace.
|
|
|
|
|
|
If something is optional add an [Install] section into that specific service file and make it into graphical-session.target.wants upstream documentation on this is the best.
|
|
|
|