silverblue-nix VS nix

On silverblue, you just follow this guide and it uses a systemd service that uses the command chattr to make / immutable (temporary) but not the reclusive directories (that means only / not the contents inside the directories) by doing chattr -i / creates /nix and /var/lib/nix mkdir /nix mkdir /var/lib/nix then it bind mounts it mount --bind /var/lib/nix /nix then it uses chattr again to make / immutable again chattr +i / . The problem with microos is that the chattr command can't change atributes on the / directory. But is there like a way to have a /nix subvolume like how there is writable /var and /home subvolumes? Like how can you make it not part of the immutable part. you can go into the transactional update shell and type mkdir /nix and /nix is there but is not writable. Is there a way to make a subvolume and mount it as /nix and have it readable and writable?

agreed with that I only install drivers, distrobox, and qemu/virt manager on the immutable part and everything else is done with either flatpak, containers, or nix (it works on silverblue quite well. there is a guide for it)

fedora silverblue is good if you want a reliable system. you can also get traditional package management by using containers from distrobox or toolbox or you can use nix on silverblue

I find it quite useful for silverblue. I can install packages user wide or system wide without the need to layer packages. It gives me a mutable eviroment while keeping the core system safe. Proot isn't available for fedora but it is available with nix so I can have proot system wide with nix which is not possible with podman. Applications with nix start way faster than starting a podman container. It is quite useful. only downside is that you need to set SELinux to permissive (which really isn't an issue for me) there is a guide for installing nix on silverblue too.

Installing nix, you would have to disable selinux and if you use silverblue, you have to do these extra steps. it would be nice if all you got to do is type sudo dnf install nix (or sudo rpm-ostree install nix if you are on silverblue) and it would automaticly add selinux policies and automaticly have the .desktop files in ~/.nix-profile/share/applications or ~/nix/var/nix/profiles/default/share/applications for system wide automaticly show up in the DE launcher and also have sudo work with nix better. it should also work for workstation and silverblue too.

maybe install it on toolbox, distrobox, or even nix if you want to install something that isn't a flatpak. nix is good for installing other terminals, shells, and fetch programs so I don't need to layer. it also supports user wide and system wide packages. only downside is that you need to disable selinux.

you should give nix on silverbluea try

here is a guide to install it on silverblue https://gitlab.com/ahayzen/silverblue-nix

the nice thing is you can install nix package manager on other distros. it is very useful to use different shells and using neofetch without layering on silverblue. there is a guide for it

Never mind traditional package managers... you plug it in right, you can run Nix on Silverblue!

https://gitlab.com/ahayzen/silverblue-nix

NixOS people will prefer NixOS, but Silverblue seems like a nice complement to Nix if you need an FHS base system and want to retain some Nix-ish features like rollbacks and atomic upgrades.

> https://github.com/NixOS/nix/pull/9911#issuecomment-19252073...

As we covered in my last post, NixOS is a amazing Linux distribution for creating stable and declared environments. Now while this is amazing for a desktop setup, it is also perfect for a home-server or home-lab.

(Nix itself is slowly chugging along with Windows via MinGW - https://discourse.nixos.org/t/nix-on-windows/1113/108 and https://github.com/NixOS/nix/issues/1320 , for example.)

Nix is a cross-platform package manager. It uses the nix programming language. Nix and NixOs are often used in the same context, but while the first is a package manager, the latter is a linux distribution based on nix.

Today I want to talk to you about Nixos. What is it? Nixos is a declarative and reproducible OS, partly taking the words used on their own page. What does that mean?

Software developers often want to customize:

1. their home environments: for packages (some reach for brew on MacOS) and configurations (dotfiles, and some reach for stow).

2. their development shells: for build dependencies (compilers, SDKs, libraries), tools (LSP, linters, formatters, debuggers), and services (runtime, database). Some reach for devcontainers here.

3. or even their operating systems: for development, for CI, for deployment, or for personal use.

Nix provision all of the above in the same language, with Nixpkgs, NixOS, home-manager, and devShells such as https://devenv.sh/. What's more, Nix is (https://nixos.org/):

- reproducible: what works on your dev machine also works in CI in prod,

- declarative: you version control and review your configurations and infrastructure as code, at a reasonable level of abstraction,

- reliable: all changes are atomic with easy roll back.

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

- it reduces bloat, because you can generate an environment or OS image with only the software needed to run a specific program or service

My guess is that a big efficiency gain would come from the second point, because you don't waste CPU on code that you don't use.

Does this make sense? Has anyone explored this?

[0]: https://nixos.org

1) Setting up the development environment - I currently use devcontainers for most things, but may also dig into nix -> isolated, portable, repeatable development environment 2) Exploring Echo - understand routing, requests, response, etc. 3) Incorporate Templ - integration with Echo, template composition, etc. 4) Integrating TailwindCSS - config for use with Echo/Templ, development cycle, deployment, etc. 5) Add in HTMX - endpoints, template structure, concepts, etc. 6) hyperscript for interactivity - client side interactivity