There is definitely this for activities, so I’d be surprised if there isn’t for virtual desktops given how much more popular/supported they are
I’m a software dev in the UK who’s into sci-fi, fantasy, videogames and music.
Big on doctor who, star trek, discworld, final fantasy, dream theater, and people’s right to be themselves.
@beforan@mastodonapp.uk
@beforan@metapixl.com
There is definitely this for activities, so I’d be surprised if there isn’t for virtual desktops given how much more popular/supported they are
This reminds me of my practice French oral exam at school, so not a typo but still:
As part of the conversation my teacher asked what sort of things I liked to read, and I decided to talk about a then popular technology magazine called T3.
“T trois” sounds rather like “Tais toi” (shut up), and she was a bit taken aback!
Thankfully though we learned not to use that in the real exam.
I don’t know tons of the detail but I understand the principle. The immutable part of the system is really just an applied oci container image for any ublue based distro.
Certain mount points are writable and persisted (e.g.
/home
), but otherwise you can just reimage the entire system with any compatible (ublue based) image. Then each image is built by layering changes using ostree. So that’s how you get the different distros.Silverblue is ublue with gnome, kinoite is ublue with KDE, Bazzite layers steam, proprietary Nvidia drivers and other stuff mainly gaming related, etc.
System updates (which tend to be regular) are just applying an updated image, so actually updating is effectively the same as rebasing.
You can also yourself add ostree layers on top of the base image, and if you rebase to a different one your layers get reapplied on top.