Hi there, According to https://www.qubes-os.org/doc/qubes-service/ VMs need a qubes-specific configuration to support the usage of the VM settings "Services" tab. I assume there is a good reason for implementing it this way, so I would like to know what this reason is. My approach would be to use qubesrc to run the services (even if they might be disabled in the template). This way it would be much more intuitive for users to understand. I myself had to spend quite some time to figure out why a service that I added to the "Services" settings tab did not run, because from the (lack of) description in the GUI I expected an equivalent to "service %name% start" being executed in the vm (for example by qubesrc)
If there is no good reason (which I doubt) I would create a feature request for changing it. if there is s good reason I would create a request for improving the GUI in a manner that allows users to correctly understand what they can configure in this tab. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c83f3501-a439-15ad-8939-4ffe21ae3e70%40web.de.
