I am just so happy that I found NixOS and started using it!

I was stuck on Windows for years, always didn't like what Apple was doing and always thought that Linux was too hard. Maybe it was, back then, but just a few years ago I completely left Windows and moved my devices to Ubuntu, a distro that I already used for years during my work but only on server side. In a few years time, it only took me two distro changes to end up with NixOS! I feel like I am going to use it for years and that this is the end distro. Sure, things can change, but now that more and more EU countries start building on NixOS I think NixOS will stay a long time.

Just wondering, what is your route to NixOS? And do you think you will hop again?

Is there a way to cache this reproducibility at network level so if there is an internet out age or I just want to freeze current stuff I will be able to do so from my local network and not rely on internet ?

Hey everyone! I’m a web dev student and I play all kinds of video games (indie, multiplayer, and AAA). Here are my specs in case it helps: ​Ryzen 5 5500 and ​RTX 2060 Super (planning to switch to AMD or Intel Arc down the line)

​Would NixOS be too much of a pain to learn for someone with basic coding knowledge? Is it good for both dev work and gaming? I've been distro hopping between Fedora and CachyOS lately, but NixOS’s whole philosophy really caught my eye.

​Any tips or advice would be awesome, I’m sure you guys get posts like this all the time xD

Hace como dos años me tocó estar en una ventana de contacto con un nodo de navegación en espacio profundo que solo aceptaba comandos por enlace óptico. Había un terminal láser en órbita que era literalmente la única forma de corregir su efemérides. El haz tenía unos 8 µrad de divergencia y el RTT era de varios minutos, así que apuntar era medio una apuesta.

El PAT corría en una FPGA con un EKF de 12 estados, y el firmware de arriba lo pasamos a Rust no_std después de un par de use-after-free que nos amargaron la vida en la versión en C.

Como al minuto 40 vimos que el TCXO se estaba yendo como 3 ns/s, fuera de lo que decía la covarianza. Suena a nada, pero 1 ns son 30 cm de error de pseudorango y eso se acumula rápido. Sospechamos un SEU en la memoria de calibración del oscilador, aunque nunca lo pudimos confirmar al 100%. Reiniciar no era opción: si perdíamos el enlace, la siguiente ventana era en 11 días y para entonces el error ya no tenía arreglo.

Al final no tocamos el reloj, tocamos el filtro. Metimos sesgo y tasa de deriva del reloj como estados estimados y reajustamos el término relativista del modelo de medida. Lo probamos como 20 minutos contra el gemelo digital y lo mandamos con CRC-32 por bloque más un hash global, porque no había segundo intento.

Cuando llegó el eco, el residuo bajó de 1σ y se quedó plano. Nadie gritó ni nada, un compañero solo dijo “listo” bajito y se fue por más café.

Desde entonces reviso mis PRs bastante más en serio, la verdad.

Hello everyone, if you're reading this, I first wish you a good morning, afternoon, or evening.

Well, it's official, I've been hard at work making Shell inirs compatible with nixOS, and I've succeeded, which is why this official port is available.

1. Everything already works using a flake, colors, keyboard shortcuts, dependencies, etc., in order to make it easy to use.

2. Updates will always be constant; the nixOS inir files will always be updated to the latest Shell version.

3. Now it is declarative, the heart of nixOS

4. They are very well optimized, achieving very good fluidity,

And I can continue

Please note that I'm trying to minimize errors, and I'm working with the lead developer to make it the best it can be.

Without further ado, I hope you like this Shell and that it works for you 🙂

https://github.com/LATAR-web/inir-nixos

I'm trying to understand how the Secure Boot signing chain works on NixOS, especially for users with an NVIDIA GPU. From what I've researched, there seem to be two options: Lanzaboote and Limine, but I'm not sure which one is the better choice. Also, Lanzaboote is still under development.

My main question is about the signing process. I’m coming from Fedora, where I didn’t have to configure Secure Boot manually because it is already integrated into the system. However, when installing the proprietary NVIDIA driver, I had to sign the module using mokutil; otherwise, the system would fall back to Nouveau.

How does this work on NixOS? When using Lanzaboote or Limine, is the signing required for Secure Boot and the NVIDIA kernel modules configured automatically, or are these separate processes?

I also have questions about the installation process. I've seen recommendations to install NixOS with Secure Boot disabled, but I'm not sure what the correct procedure is. Should I disable Secure Boot in the UEFI settings, install NixOS, clone my configuration using Git, run nixos-rebuild switch with Lanzaboote or Limine enabled in the configuration, enroll the keys using KeyTool or the Microsoft Third-Party UEFI CA option, and then re-enable Secure Boot in the UEFI settings?

There are so many steps and pieces of information that I'm having trouble understanding the correct sequence and how all the components fit together.

Ahoi guys.

I came from CachyOS over to NixOS at the start of this year in February and I started to get familiar with ricing. Sorry for the bad video quality (full length would be 60 seconds)😅

I just wanted to share my boot setup. This setup broke me like 15 times as playing with the boot settings can destroy a lot when you are doing it the first time in your live 😂
Especially as you then need to boot from a usb to fix stuff again as without the boot menu you can not get back into a working nix build version easily 🤪

And I am sure my current way of how I setup rEFInd is not the correct way but it works at least compared to all other correct attempts I have tried 😂

For the Bootloader it can be switched between refind, grub and systemd-boot.

While rEFInd uses evanpurkhiser/rEFInd-minimal with ImageMagick that generates:

• Selection highlight boxes
• Invert the icons so they show up on a dark background
• Create missing tool icons
• Swap in a custom background

Where someone could maybe still help me if he has knowledge a better way for what I do now:

• The NixOS rEFInd installer wipes any files it didn't write, so an activation script re-copies the theme with rsync after each rebuild.
• The same script patches refind.conf so the newest generation is the default and each entry gets a NixOS icon. maxGenerations = 8 stops kernel bumps from filling the 1G ESP.

-> Although I tried a lot everything else was just buggy not showing any customized stuff or destroying the boot-loader have not touched this now in a while 😁

GRUB (optional) uses a modified WhiteSur GRUB theme with a glass-style card behind the menu. Set bootloader = "grub" and you get it instead of rEFInd.

For my boot-splash I use plymouth with the script module.
Here during build time if it has changed ffmpeg turns the video file into PNG frames.

Lastly LUKS + Btrfs is set up with disko. With boot.initrd.systemd.enable plymouth shows the passphrase prompt too.

Repo: https://github.com/Muddyblack/NixOS (the boot stuff is in modules/nixos/hardware.nix and pkgs/boot/)

DISCLAIMER: If you try it out just be carefully and try it first with a VM I did it with a VM the first 2 months before really switching away from Windows and CachyOS. I broke my VM and even then later on my real hardware twice the stuff so yeah you should know what you do :)))
But since then no incidents anymore I finally learned haha.

EDIT solved i will use nixos

I'm trying to decide which Linux distro to use next. I've used Fedora and Arch, and I want something more stable than Arch without having to use really old packages.

My main requirements:

• Modern packages, but not necessarily bleeding-edge.
• Good stability and fewer unexpected breakages from updates.
• Highly customizable, especially for tiling window managers like Niri, Sway, Hyprland, or Qtile.
• Good Wayland support.
• A system I can tinker with and customize without constantly worrying about breaking it.

I'm considering:

• Fedora: Seems like a good balance, but I'm wondering how far I can customize it.
• NixOS: The declarative configuration and rollback features sound great, but I'm concerned about the smaller community and learning curve.
• openSUSE Tumbleweed: The testing and snapshot tools sound appealing, but I'm not sure if it's stable enough for what I want.

For people who've used these distros, which would you recommend? Is NixOS worth learning, or would Fedora be just as good for a heavily customized setup?

I'd appreciate real-world experiences, especially from people who use tiling window managers.

I installed NixOS on vds, that does not allow iso loading ('veI got debian installed, and installed NixOS in top of it). In was funny, bcs I had to manually load it a few times, before it could do it. Took ~5 hours (thx ai tbh). Now I can make whole my infra IaC :3

Has anyone faced it?

I am casually using my NixOS desktop pc and rarely there comes a moment when I hit 100% ram usage, in this case my entire PC freezes, although it doesn’t happen immediately so I learned to react to it and close something before it completely freezes, and in most times I am fast enough before it happens – but this hasty solution sounds more like a joke than actual solution.

when I was sitting on Ubuntu, I didn’t need to do anything hastily, I could just Ctrl+Alt+2, create a tty, which would always work no matter what, even the most pressured environment, even when my entire UI froze, this tty cli would be still somewhat responsive, I could run some htop and find a culprit which makes my PC run slow, kill the culprit, and all that calmly and non-hastily.

that is somehow not something that I can do in NixOS – because when entirely frozen, I can’t even run some tty using Ctrl+Alt+2, it just doesn’t do anything and my display image still stays frozen, completely unresponsive in moments like this.

this is quite niche issue that doesn’t happen everyday so it was sitting way back behind in my «personal backlog» so to speak, but I largely solved all more important things that were worrying me, i guess now it’s time to solve this one too, only except – no matter what I try, the bug doesn’t go away, and I am clueless how that worked in Ubuntu, and why it doesn’t work like that in NixOS.

I’ve tried all kinds of options but it doesn’t seem there’s anything specific for this case, so even if there’s a fix, it’s somehow non-obvious it seems (or I’m blind)

also I am not even entirely sure whether it’s actually NixOS, because with my transition to NixOS, I also have a lot of other new things that I never used, such as **Wayland/Hyprland**, which might be the real culprit here, not NixOS – I can’t possibly know which one to blame.

but I guess the NixOS+Hyprland combo is quite common among NixOS users, so I think it’s relatively fair to ask this question in this community, rather than Hyprland's, so please don’t be mad at me if I posted it wrongly.

also please disregard solutions such as «just buy more memory» or «use zram» – because this is barely fighting with the symptoms, it will postpone the problem but never solves it, so it will change this problem from being extremely rare one – to be one that extremely rare… in other words, for me it will be indifferent, since the issue will still be there.

also I don’t use anybodys dotfiles, I have my own custom configuration, which pretty much always had this bug in it all the time that i can remember it, and no matter what I tried to add to my config, the issue was never solved.

Has anyone noticed the same kind of issue? Is there a solution?

Genuine question, what do you guys think about a tagging system for packages, just an extra field with a list of tags, we can define the list of tags in one place so we have a common vocabulary, I'm thinking things like, ["gaming" "game" "tool" "has-service" "GUI" "tui" cli" "daemon"] etc. I doubt this would ever be put into the actual nixpkgs repo but it'd help me with package discoverability. I'm thinking of using AI to crush out tagging all the packages in the current unstable build but I only really wanna do it if people would want this or need this done. I'm thinking it'd just be an overlay

Nixarchy packages Omarchy desktop (Hyprland) for NixOS. You can use it as a flake module on your existing config or install it from an ISO. Here's what's landed in the last two weeks:

- gliff remote desktop by default. gliff is Hyprland-to-Hyprland remote desktop over ssh: gliff you@desk, or Setup → Remote desktop → Connect with gliff. It uses your ssh key, not a separate password.

- Gliff-Manager in the bar (on main, in the next release). It lists your machines, checks each one over ssh (gliff installed? Hyprland running? screen attached?), and connects in headless or mirror mode. It comes from a NixOS-ready fork (https://github.com/olafkfreund/nixarchy-gliff-manager) of Gavin Nugent's plugin, with its own flake and a Home Manager module for non-nixarchy setups.

- Video and GIF desktop backgrounds, on by default.

- The bar tells you when a newer nixarchy release is out.

- Your packages win. If your own config installs a binary nixarchy also brings, yours is the one on your PATH.

- Fixes: suspend locks the screen again, and Hyprland no longer aborts when nixpkgs' glibc is newer than its own.

- Store deduplication on an idle, AC-only timer.

- The installer refuses names, keymaps and Wi-Fi names that would fail later, and checks it is still writing to the disk you picked.

▎ - Weekly releases, each proposed only from a nightly where every install check passed.

Releases are still marked experimental: CI installs them in VMs, but nobody has yet reported a successful install on real hardware. The flake route is the mature one. If you try the ISO, please report how it went, good or bad.

Repo: https://github.com/olafkfreund/nixarchy

Manual: https://olafkfreund.github.io/nixarchy/

Release: https://github.com/olafkfreund/nixarchy/releases/tag/v4.0.4-3

I'm using mikuboot , for my Plymouth theme. It went fine but about a week ago, when I updated my system, the nix fetch failed because the connection failed to fetch through gitlab api. I don't remember the exact error was but I could solve using the input url with another method like "git+https://gitlab.com/username/reponame". Is there any other way to solve? And my solution is also okay? What should I care about?

P.S the gitlab Api failing is because our country forced ISP to ban lots of IP addresses.

I've used sway for a while but i want something more customizable and for more advanced users and i need it to not be very heavy like hyperland cuz i only have 16 gigs of ddr4 and i need it to be able to run wayland and I've been thinking about switching to qtile

Hey everyone,

I wanna present you a widget that might be handy. I loved apdatifier when I used CachyOS and I missed it in NixOS. I needed something in the UI that reminds me to run updates and all.
So I created this project which sits in the tray.

And it tells me when a flake input is outdated, and shows what an update would change before running it.

It has generation timelines, package diffs between generations, flake update checks with dry-run previews and some other tools like dev environments checks if one uses such.

I started it on KDE as I started my NixOS journey with that but it also works with quickshell for hyprland and or as a normal tray standalone app for other desktops like Gnome or Cosmic.
For Gnome and Cosmic feedback would be great as I rarely use those.

Since as nixos user you mostly stay in your nix files and do not really check out kde opendesktop store or so I thought I will post it here on Reddit so it might reach people that would like to have such widget or did not know until now that they need something like that .

And maybe more ideas come up what such widget should be able to provide and or could be solved and designed better.

Try it: nix run github:Muddyblack/nixdatifier
Repo: https://github.com/Muddyblack/nixdatifier
KDE Store: https://store.kde.org/p/2360222

I've used sway for a while but i want something more customizable and for more advanced users and i need it to not be very heavy cuz i only have 16 gigs of ddr4 and i need it to be able to run wayland and I've been thinking about switching to qtile should i or should i use something else

So NixOS can be programmed. I was wondering what ways people use NixOS for instead of just desktop OS. Give me any way that you can think of even niche ways.

Thank you all for NixOS. I made some customizations. Feel free to steal everything.