Look up what?
Yes GNU Guix is a linux distro.
The package manager for Guix (also called guix) is also a portable package manager which works on any linux distro, similar to flatpak, nix, homebrew, etc.
Guix's claim to fame is that it is a functional distro/package manager, meaning that all changes are atomic, so installing/upgrading/deleting packages never leaves your system in a broken state.
Not only that, but if you make some change to your system and it breaks for normal reasons (e.g. newest software version has a bug), you can roll back to your previous system state with all your previous packages and their versions, and this roll-back operation is also atomic.
Guix the distro not only let's you do package management this way, but also let's you do declarative system configuration. This means rather than manually rummaging around /etc changing files and hoping nothing breaks, there's simply a single config file which declares all of your system configuration. From your kernel to users, partitions, system services, and just about anything else, all the configuration is declaratively done in one place with one language (Guile Scheme). Any changes you make to your system this way are also of course atomic and can be rolled back.
It even comes with a built in system called guix home which lets you bring that same level of declarative, atomic configuration to your user's home environment, letting you manage user level packages, dotfiles, env variables, and more with a single home configuration file.
There are other goodies too, such as the ability to spawn one-off shell environments with the guix shell command, dropping you in a shell with all the packages and env variables you declare, keeping your regular user environment clean (very nice for development).
There's even more, but at this point if you're still interested just head over to the site and the docs.
codeberg
it’s like github but non-corporate free software
it’s very polished and featurful
it’s built upon/by the same devs as forgejo, which is open tech to self host your own git server (with federation potentially coming), so supporting one supports the other
If I understand you correctly, this is trivial in emacs:
(defun insert-text ()
(interactive)
(insert "your text here"))
(global-set-key your-keybind-here #'insert-text)
You could make it a format string if it relies on data specific to some file or parameter. You could also make the keybind local to certain modes/files rather than a global keybind if you don't want to pollute your keybind space.
emacs org-mode
Yeah rollbacks are probably the best part of immutable OS's, but of almost equal importance is reproducible system configuration, which imo only Nix and Guix do well. Neither snapshots nor Silverblue really manage that yet.
edit: I do feel norawibb's point, the slippery mutability of Void is something I am a lot less comfortable with than I used to be. Apparently Guix has spoiled me.
There are two different immutable OS models hot on the table in the linux space I see: The Nix[^1] way and the Silverblue[^2] way.
Both have immutable filesystems which deviate from the FHS, provide atomic updates, and support the creation of more-or-less isolated environments at the user level. But the way the two models implement these features is very different.
The Nix way takes inspiration from the world of functional programming, while the Silverblue way takes inspiration from the containerized, cloud native technologies which are used so widely in the industry.
I believe the idea that these two approaches share is the future of linux on both the server and the desktop, and it is only a matter of time before some (if not all) of these advantages become mainstream. However, I am uncertain of which approach is superior.
I have personal experience with Guix and enjoyed it greatly and even recommend others try it or Nix out for themselves, but there are some complexity issues. It is not clear to me whether these issues are growing pains, or symptoms of a fundamentally overcomplicated system to solve a seemingly simpler problem.
The Silverblue way I have no experience with, but seems like a more grounded approach to tackling the specific problems laid out. The big area where Silverblue seems to lack in comparison to Nix/Guix is declarative, reproducible system configuration. With Nix/Guix you can just throw your system config file up in a repo, and anybody else can pull it down and install that system bit-for-bit, including future you! With home manager this extends to a large extent to user configuration as well. Of course with Silverblue you can create images, but that is less straightforward and powerful (at least for now).
What are ya'll's thoughts on immutable OS's?
[^1]: The only other example I am aware of is Guix, which imo is the superior implementation, but it is newer and less popular. [^2]: Others include openSUSE's MircoOS/Aeon and Vanilla OS.
This is patently false. Most alternatives to GNU software are permissively licensed (MIT, BSD, Apache, etc.). Just look at musl, clang, bzip2, and the various “new” userland replacements like ripgrep, neovim, bat, exa, dust, etc. The one notable exception is busybox which is GPL 2.
I don’t know why this trend exists, but I am constantly disappointed that talented young open source devs choose to sacrifice software freedom just because it will make their software easier to integrate in proprietary contexts. This strikes me as pure vanity or greed on the devs part so that their software is more popular and maybe even monetizable.
I hope that trend halts, but time will tell.
what would you be stealing?
Lisp
It solves so many problems new languages have been invented to try and solve, while being simultaneously simpler than most