Improve UX and documentation of services

[andrewdavidwong]

Qubes OS version:

R4.0

Affected component(s) or functionality:

sys-firewall and qubes-firewall service

---

Steps to reproduce the behavior:

Check the services of sys-firewall and see that qubes-firewall is not enabled.

Despite this, sys-firewall still seems to work correctly as a FirewallVM.

Expected or desired behavior:

Either qubes-firewall is enabled in sys-firewall, or the documentation about qubes-firewall is updated to explain why it is not needed, or qubes-firewall is deprecated.

Actual behavior:

sys-firewall still seems to work correctly as a FirewallVM even without qubes-firewall being enabled.

General notes:

---

I have consulted the following relevant documentation:

http://dev.qubes-os.org/projects/core-admin-client/en/latest/manpages/qvm-features.html
http://dev.qubes-os.org/projects/core-admin-client/en/latest/manpages/qvm-service.html
https://dev.qubes-os.org/projects/core-admin-client/en/latest/manpages/qvm-prefs.html
https://dev.qubes-os.org/projects/core-admin-client/en/latest/manpages/qvm-create.html
https://www.qubes-os.org/doc/config-files/
https://www.qubes-os.org/doc/firewall/

I am aware of the following related, non-duplicate issues:

[marmarek]

Works as intended - service not listed means "use default value".
This is also included in qvm-service manual you linked:

Reset service to its default state (remove from the list). Default state means “lets VM choose” and can depend on VM type (NetVM, AppVM etc).

Although indeed could be better exposed.

[andrewdavidwong]

Ok, Thanks. Filing as a UX issue.