From: Alyssa Ross <hi@alyssa.is>
To: Geblaat <geblaat@riseup.net>
Cc: discuss@spectrum-os.org
Subject: Re: PlagueOS
Date: Tue, 15 Mar 2022 21:10:44 +0000 [thread overview]
Message-ID: <20220315211044.owok7z2esxk7weyv@eve> (raw)
In-Reply-To: <725dae3fb6c253624b5aea184923c5f1@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 2505 bytes --]
On Tue, Mar 15, 2022 at 12:23:13PM -0700, Geblaat wrote:
> On the mailing list, I saw an article about FlexOS, which has some
> similar goals, though it seems to be in very early stages. I thought
> PlagueOS might be of interest to people here as well. Like Spectrum, it
> has better hardware compatibility and performance compared to Qubes OS.
> They use Void OS as hypervisor(looks like standard KVM compared to a
> more secure Rust alternative) and a lot of hardening. It already has an
> ISO image available and a graphical desktop environment, so it can
> already be used by people with not much technical skills.
That's very interesting, thank you for sharing.
I took a look at their documentation. I also had a quick go at running
it in a VM but couldn't get it to boot. It looks like it's a hardened
Linux distro, with some out of the box support for running applications
in virt-manager VMs. I'm very curious about how those VMs are
integrated with the system, and whether there's any tooling for making
it easier to create/manage VMs on top of the standard virt-manager
stuff — it was difficult for me to tell just going by the information on
their GitLab site.
I've seen a few other projects now that bundle virt-manager or
crosvm and try to make it a bit easier to use, at varying stages of
development[1][2]. The main difference between these projects and
Spectrum is that Spectrum is aiming for a higher level of integration
than just using the standard virtualization programs can provide. I want
it to be difficult to tell that the application you're using is even
running in a VM. I want it not to be necessary to configure and manage
VMs just to run applications. But that's not something that existing
Linux virtualization stuff is quite up to (Qubes is closer than anything
else), so I'm working on that virtualization technology to try to push
it forward to that end. In my mind, that's what separates Spectrum from
lots of the other efforts I've seen. (If any of those projects *are*
doing development work on virtualization software that I've missed, I'd
be very happy to be corrected and to learn about it!)
[1]: https://github.com/jollheef/appvm
[2]: https://blog.openw3b.org/crosvm-for-os-and-app-virtualization-on-linux/
P.S. Looks like the reason PlagueOS wouldn't boot is that its initramfs
is looking for /dev/disk/by-label/PLAGUE_LIVE, but the actual path
is /dev/disk/by-label/plague_live (lowercase).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-15 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164737130657.1627.12904004323655713683@atuin.qyliss.net>
2022-03-15 19:23 ` PlagueOS Geblaat
2022-03-15 21:10 ` Alyssa Ross [this message]
2022-03-23 9:25 ` PlagueOS Geblaat
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=20220315211044.owok7z2esxk7weyv@eve \
--to=hi@alyssa.is \
--cc=discuss@spectrum-os.org \
--cc=geblaat@riseup.net \
/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.
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).