Variety is the spice of life. I’ve used Slackware, Arch, Gentoo, Fedora, Nix, been on Debian the last few years. Been looking at setting up my own UBlue image. I really like the immutable thing. Do whatever makes you happy…
Variety is the spice of life. I’ve used Slackware, Arch, Gentoo, Fedora, Nix, been on Debian the last few years. Been looking at setting up my own UBlue image. I really like the immutable thing. Do whatever makes you happy…
~/.projects
I have a 650m from 2013 (almost 10 years) and there are zero working drivers aside from noveau ones.
Thanks, I had no idea this existed.
software level architecture that can be used on various different CPU architectures providing maximum flexibility.
I’ve only done a little bare metal programming, but I really don’t see how this is possible. Everything I’ve used is so vastly different, I think it would be impossible to create something like that, and have it work well.
Could it be that it just introduces additional attack vectors?
Do you have any high quality resources on testing you would mind sharing? I’m mostly a self taught programmer who loves TDD, because I’m shit at writing code.
UBlue is a tool the fedora team created to build immutable distros in a container. This is a list of official distros created by it. If you’ve seen Bazzite it was also created with UBlue.
Immutable distro just means the root filesystem is mounted read-only. So when you do updates, they create another image of your filesystem with the updates applied. Then you have to boot into the new filesystem. This is called an atomic upgrade. So if something is broken, you reload your last image and everything is fine.