Demi Marie Obenour <demiobenour@gmail.com> writes:
I'm wondering if Spectrum OS should have a management daemon that is responsible for a few tasks:
I'm not saying never, but I am keen to try to avoid it, and if it has to happen, to limit its scope as much as possible. My concern is that "management daemon" would end up becoming the daemon equivalent of a god object — once there's state maintained within a daemon, it's always easier to add more stuff to that daemon than it is to implement things separately and expose that state, even if those things have no business being part of that daemon. With no monolothic daemon, we don't have that tendency towards consolidation, and can instead having single purpose components that can be understood in isolation.
- Starting VMs when requested by the UI. - Notifying the user of various situations that require their attention, such if a VM crashes. - Suspending VMs before the host suspends, and resuming them after the host resumes. I believe Qubes OS didn't do this initially, but that led to problems so they do do this now. - Acting on devices being plugged and unplugged from system VM.
With proposals like this, it's important to communicate why it might be an improvement over the current situation. All of these things are things we easily could do without needing a monolithic daemon.