aarch64 support in #SpectrumOS is now at parity with x86_64 support! It uses systemd-stub's new .dtbauto mechanism so the generic image can automatically (try to) load the right device tree for the device it's running on.
aarch64 support in #SpectrumOS is now at parity with x86_64 support! It uses systemd-stub's new .dtbauto mechanism so the generic image can automatically (try to) load the right device tree for the device it's running on.
Looked a bit into how Flatpak works. It looks like shouldn't be too difficult to figure out which paths from the OSTree repo should be passed through, so I think getting Flatpaks working in #SpectrumOS won't be quite as difficult as I thought :3
It's up! https://spectrum-os.org/doc/using-spectrum/running-vms.html#transient-vms-for-appimages
Ended up chasing one regression after another trying to do a final Nixpkgs upgrade, so took a lot longer than I expected.
Ask me about it at NixCon ^^
Coming soon to #SpectrumOS — double click an AppImage, and it runs in a temporary VM, with no other setup required.
Just need to tidy up the commits a bit…
bcachefs debugging stream! :O I keep finding packages that fail their tests on bcachefs. Maybe we can figure out what's wrong and fix something?
bcachefs debugging stream :O
Spectrum development stream!
Spectrum's File Chooser portal implementation relies on VSOCK support in D-Bus, which today I'm going to start trying to upstream!
Upstreaming D-Bus VSOCK support
Spectrum development stream!
Spectrum's File Chooser portal implementation relies on VSOCK support in D-Bus, which today I'm going to start trying to upstream!
Upstreaming D-Bus VSOCK support
One big annoyance with developing #SpectrumOS is that Linux doesn't support nested virtualisation on aarch64 (and most aarch64 hardware also lacks support), so to test Spectrum I either have to boot it directly on hardware, or get the in-development patches for the kernel and QEMU working to run it in a VM on compatible hardware.
FINALLY, the first successful full build of #SpectrumOS on aarch64!!
What took so long? Mostly that aarch64+musl seems not to be a well-tested combination, so we had to come up with lots of fixes for that.
I'm starting a stream! Going to see how much further I can get implementing our portal implementation on the Spectrum host.
Implementing the File Chooser portal for Spectrum VMs
Starting in a few minutes, I'll be carrying on with tidying up the portals implementation, and installing it on the Spectrum host system.
Implementing the File Chooser portal for Spectrum VMs
Stream time! This is going to be a quite laid back one where I bisect why a Nixpkgs update has introduced some weird behavior to the portal implementation.
@aral Please find me a technology big tech is involved with that we are not funding actual alternatives to. Any form of proprietary lock-in is something we target to remove, anything that invades privacy needs to be stopped/mitigated (think #NoScript, #JShelter, #Offen.dev, #Goatcounter, #TrackingTheTrackers, #Searx, #Qubes, #SpectrumOS, etc). That is our contribution. Obviously, the trillion dollar surveillance economy needs to be curbed by harsh regulation, but this is not within our remit...
This stuff is exactly the reason I didn't start building #SpectrumOS on top of an existing distro (even NixOS). Nobody is doing things the right way, and it's a lot easier to get right if you're designing that way from the start. Writing it all up like Lennart has done here is a really good first step, and I hope it helps distros overcome the stagnation they've been in.