I have to say traditional LTS distros. After doing big manual server upgrades for some decade, no more LTS expiration dread!
Next to go will be my arch desktop as I find #nixos fits my desktop and server needs way better.
A disclaimer would be that NixOS is non standard. Documentation is lacking and knowledge of the Nix language is required for advanced configuration.
A new module is available: 'programs.smug'. Session manager and task runner for tmux written in Go. See https://github.com/ivaaaan/smug for more information.
#NixOS #Nix #HomeManager
Ok #linux and #nixos peeps, I have a puzzle.
I want this systemd service to run ONLY WHEN a user is logged in, and they're connected to the internet.
Is this possible?
This is what I have so far but when I restart the computer, the systemd service shows as failed because it's trying to send the notification when no one is logged into the system.
Quick, someone talk me out of using #NixOS again. I lost so much time to dotfile config and window managers but Maybe It It Will Be Different This Time™?
Hey #NixOS #Cloudflare #ZeroTrust
edit: I have not yet sorted out getting Docker running on NixOS yet, so for the moment I'm gonna get that installed and use the available container, which has latest build. I would like to stick to pure Nix on everything, but there is a need to be, umm, clean on opsec.
I was trying to install cloudflared from unstable repo. It installed and works from 24.11, but when I ran the command to create the credentialsFile it complained about the older version and suggested upgrading to 2025.4.0 rather than the 2024.10.0 that is in nixos.
Unstable has 2025.2.1, which is better, but is not 2025.4.0. Two branching questions from here.
1 - the unstable package returned that error: Package ‘cloudflared-2025.2.1’ in /nix/store/vxwsnfg5mys9v1qrxvim13ddmnhd4z1g-unstable/unstable/pkgs/applications/networking/cloudflared/default.nix:97 is marked as broken, refusing to evaluate.
Conveniently, it included instructions for allowing packages marked broken through. Is that considered normal in dealing with Cloudflare on NixOS? Cause it reads to me like an outtake from "How To Get Your Website Pwned By L33t H4krz".
2 - considering that even if I allow the "broken" package in, I'm still not getting the version recommended by cloudflared's error message, perhaps there's a flake or something I should try, that would get the daily build or whatever?
I'm off to do more searches and maybe poke my head into one of the actual support forums, but this seems like a pretty common task for NixOS admins to be doing, so it's probably an easy answer that I just haven't found yet.
Probably been looking at nixos.wiki again or something.
@jpmens GPG agent forwarding with a Yubikey!
I've been using this method for a while now to control sudo authentication on my local machine, and all remote devices/VMs too. Allows me to leave an undesirably long/complex password for the user account in a password manager (as an escape hatch, but which I don't actually use).
With verification of presence via touch, and also the PIN on the Yubikey cached for only a short period of time, and it self destructing after 3 incorrect PIN entries...
End result is I have super convenient *and* secure local/remote two factor authentication and privelidge escalation.
I'm also using sudo-rs, which is a much more "minimal" implementation - just as I don't need the vast array of extra stuff that bundled into the traditional version.
I use #NixOS almost entirely, so only have need for Ansible in a few places...
That said, finding a way to utilize this for Ansible Vault has been on my to-do list for a while, so looks like you've solved that one for me!
Thank you
Anduril Industries banned from recruiting on NixOS forums
https://discourse.nixos.org/t/anduril-industries-electromagnetic-warfare-team-is-hiring/62569
So, for various reasons (professional verses personal), I don't set my global user name or email in Git. Instead, I have NixOS and Home Manager set up to give me a git command:
home-manager.users.dmoonfire =
{ pkgs, config, ... }:
{
home.packages = [
(pkgs.writeShellScriptBin "git-moonfire" ''
git config user.name "D. Moonfire"
git config user.email "contact@moonfire.us"
git config core.sshCommand 'ssh -i ~/.ssh/moonfire-rsa'
'')
};
That way, I can easily call this with:
git clone https://some...path/
git moonfire
git commit -am 'feat: everything is awesome'
Installed #NixOS 24.11 on #VirtualBox today. Apparently the demo image was deprecated https://nixos.org/manual/nixos/stable/release-notes#sec-release-24.11-incompatibilities in favor of using the standard ISO, but the installation instructions on the manual have not kept up.
Due to a corporate CA, just getting the installer to work at all https://discourse.nixos.org/t/nixos-in-corporate/50041/9 was painful, especially due to one being DER, so, had to install openssl before adding CA certs with nix-shell
I only noticed the Don't reboot https://itsfoss.com/install-nixos-vm/#dont-reboot-but-turn-off-the-vm after it was too late
1/2
#NixOS is interesting. Pretty reliable (not as much as #AtomicDesktops in my noob tests) while also performant
Note that such old hardware will have #microcode vulnerabilities and locking it down will further slow it down. At least thinking of #spectre or #meltdown (not sure if hyperthreading was even thought of back then)
@pmidden So this is kinda like using aptitude instead of apt-get on a Debian distro? It still connects to the real nix repos, with their godlike rolling schedules and whatnot?
I'm what you might call a conservative about this sort of thing - I'm not against these side versions, but as long as the majority of the community is using regular nix, the most likely scenario is that I'm gonna stay there as well, strictly because it is easier to find help and guidance from the largest user community.
As long as they are not giving up essential things for their mainstream choice, of course, and it seems to me that nix decides what's mainstream.
I remain a highly enthusiastic #NixOS user but I know I am not the first to complain about their atrocious documentation practices. I am still working on fully understanding the beast, but once I do I expect I'll try to help out with that, as my main contribution.
Main thing is nixos.wiki has to fucking go. It's just fucking embarrassing.
I’ve officially deployed a Nixos based slideshow/ info screen for a client. It runs a rust client for the Xibo open source backend. It turns itself on and powers off at the end of the day. Has different systemd timers for different office hours throughout the week. Shows the weather, a slideshow of upcoming events and calendar showing that day’s events. Very slick and highly configurable. So far it’s been solid and I’m impressed. #nixos
@korenchkin Is nixos.wiki managed by non-NixOS or NixOS-hostile personnel?
Cause I tell ya, letting that link above just exist, with not so much as a "HEY DON'T READ THIS GO TO THE ONE AT NIXOS.ORG YOU NUMPTY" or something like that is pretty newbie-hostile.
Not just bad or clumsy management, but actively hostile. I dunno how much of my time that site just wasted, or how much it will waste before it is eradicated from the earth.
Oh how I do love the docs at #NixOS.
I am attempting to do the "System wide vim/nvim configuration" example at https://nixos.wiki/wiki/Vim and rebuild is giving me this error:
error: attempt to call something which is not a function but a set
I read on one forum that removing the { } you see there, the set in question, from the override line, that would fix it, but then I of course get
error: expected a set but found a function
Since this is coming straight from the wiki and my syntax is correct, this is what you might call
Annoying
I made an interactive treemap visualization tool for Nix derivations!
Check it out :D
I got a #nixos tempban, glad to see the mods are fighting the good fight
Account suspended until April 4, 2025: tempban