From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>,
Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: Spectrum OS management daemon?
Date: Thu, 21 Aug 2025 12:32:24 +0200 [thread overview]
Message-ID: <87y0rdt16v.fsf@alyssa.is> (raw)
In-Reply-To: <157e2b88-c292-419a-b5cd-0735d1f78a59@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2025-08-21 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 7:15 Spectrum OS management daemon? Demi Marie Obenour
2025-08-21 10:32 ` Alyssa Ross [this message]
2025-08-22 4:41 ` Demi Marie Obenour
2025-08-22 13:52 ` Alyssa Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y0rdt16v.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).