After the usual grind re-setting everything up again, restoring backups, etc. I have everything I need set up now (except #nix 🤓)

I am *very* happy with this phone. It's such a massive upgrade to the broken (or non-broken) Xperia 10iii phones I have been daily-driving with #SailfishOS for far too long now. 😅

- 🤩 double-tap to wake like in good old times
- 🤩 fingerprint unlock
- 🤩 dang it's fast and smooth!
- 🤩 configurable (privacy) switch on the side

#JollaPhone

My NixOS system update is satisfying and also informative to stare at.

Thanks to #nom (#nix-output-monitor). Btw, I use nh which have nom etc builtin

The most useful flag I use for system update is `-a` which asks for confirmation after building and showing all changes, so I know if I have commented or forgot to enable a service by mistake etc etc. pretty useful TBH

`nh clean all --optimize` is another one I use regularly

#nix #nixos #systemupdate #nixhelper #nh #Linux #OS

Alt...

NixOS system update output tree view with nix output monitor in the terminal

Beautiful #NixOS #Nix Wallpaper.

From: Sametaor on Reddit.
Source: https://www.reddit.com/r/NixOS/comments/1voa2rb/wallpaper_based_on_windows_7_harmony/

Alt...

Rainbow Nix OS Logo with Blue light background

I got interested in trying out #PICO8 but found that it was not in #nixpkgs.
And running it was requiring steam-run.

If you're also on #nixos / use #nix and want to give it a try, I made a flake for it :3

Repository can be found at
https://codeberg.org/husjon/nix-pico-8

Feedback / comments etc are all welcome. :3

[lien] The Nixpkgs core team has disbanded - Announcements / Nixpkgs Core Team - NixOS Discourse #gik #nix

The Reticulum Network Stack and its companion daemon, LXMD, are now available as NixOS services!

Setting up your own Reticulum node is now a piece of cake !

https://github.com/NixOS/nixpkgs/blob/master/nixos/doc/manual/release-notes/rl-2611.section.md#new-modules-sec-release-2611-new-modules

#nixos #nix #Reticulum

Yes. Like countries and democracies, every organisation has to make the decisions it believes are necessary. I respect that. My point is simply that #Codeberg has become system-critical to my work, including infrastructure built with #LLM assistance for #Nix. I now have to fear that a key part of that infrastructure could be removed without warning. 1/2

Yay, I added my #yannix flake to search.nixos.org. You can now find my #nix / #NixOS stuff on the official search page:

📦 my packages: https://search.nixos.org/flakes?query=yannix

🔧 my NixOS options: https://search.nixos.org/flakes?query=yannix&type=options

> nix shell nixpkgs#uv
copying "/nix/store/0lgkd7b0s5ykklkijr9g62r832qdvgvx-nixos-25.05.20250622.c7ab752/nixos" to the store

Why does it take 30 seconds to (uselessly) copy something from the nix store to the nix store?

#nix #nixos

Time for some shameless self-advertisement: I have some availability starting this September!

I'm an experienced OSS maintainer, with lots of work done on @doctrine and @getlaminas

I push for #DDD (with humans & tactical).

Languages mostly #Go, #PHP, although I'd love to do some #Rust, and I read anything at all.

I can #Terraform your infrastructure, work on hardening CI/SA pipelines, Docker and #Nix builds, test suites.

Rates between 700~1100 EUR/day depending on terms. #getfedihired

People who know stuff about #Nix:
How useful is Nix/Lix without being able to access nixpkgs (theoretically)?

GuixPkgs: every Guix package, as a Nix flake via @pbsds https://lobste.rs/s/rm7qnt #nix
https://fzakaria.com/2026/06/25/guixpkgs-every-guix-package-as-a-nix-flake

Oh great, nixos-rebuild tried to be smart again. You apparently need to keep a dirty worktree of the root git project or it'll clone all of the submodules from github (once you found the changelog where it tells you how to enable submodule support).

Why can't you just be normal?

I used relative paths for a reason. I didn't want you to download it from github each time. The local repo is the authoritative one...

Edit: or deleting the remote from the git repo, that also worked

#nixos #nix

[lien] Arcanesys - Gestion de flotte NixOS en GitOps signé #gik #git #nix

#NixOS #Nix

What's the general opinion of the #Nix community on hardening systemd services? Aka. adding isolation and restriction properties?

Is there a reason it is currently not that commonly done? Would PRs in that regard be appreciated or would it just be dismissed?

#systemd #NixOS

@xcabal05 I'm in the first batch and haven't gotten mine yet. I'm a fulltime #SailfishOS user since its beginnings though and I am happy thus far. It's a real Linux in the pocket, terminal, ssh, #nix, etc. which is what matters to me. The Android apps I need work fine. But expect annoyances here and there. I really hope the new phone fixes annoyances I have with my Sony Xperia 10iii now. Most notably the camera sometimes not saving photos or videos and network switching wrecking connectivity.

So, I gave #devenv a try.

I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
So, yeah, I'll keep my #flake for now.
At work and at home.

CC @Ilygad

NixOS - Das Multi-Host-Setup individualisieren

In meinem letzten Beitrag der NixOS-Reihe zeige ich, wie man einen einzelnen Rechner aus dem gemeinsamen Setup herauslöst und individuell konfiguriert – ohne die anderen Rechner auch nur zu berühren.

#NixOS #Nix #Flakes #Nix_Store #Linux

https://gnulinux.ch/nixos-das-multi-host-setup-individualisieren

NixOS - Major-Upgrade, Pakete aus 'unstable' einbinden und "Wegwerf-Pakete"

Ein Major-Update steht an. Zudem binden wir Programme aus dem Rolling-Release-Zweig ein – und nutzen Software, ohne sie überhaupt zu installieren.

#Nix #NixOS #Flakes #Linux

https://gnulinux.ch/nixos-major-upgrade-unstable-wegwerf-pakete

NixOS - Multi-User-Setup einrichten

Weitere Benutzer werden anlegt – am Beispiel eines Gastnutzers und einer neuen regulären Benutzerin. Nebeneffekt des heutigen Setups: Heute wird nochmal ganz klar, welche "Nixe" für was zuständig ist.

#Nix #NixOS #Flakes #Linux

https://gnulinux.ch/nixos-pakete-aus-unstable-einbinden-und-quot-wegwerf-pa

@nobodyinperson

Ok, but this probably is really the best I can do to simplify it.

But I'm not sure if it is a good idea to use something called "legacyPackages".

(Also just a disclaimer I don't really fully understand what I'm doing here. But it works, so...)

#NisOS #Nix

Alt...

{ description = "Nix dev environment"; inputs = { nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11"; }; outputs = { nixpkgs, ... }: { devShells = nixpkgs.lib.genAttrs nixpkgs.lib.systems.flakeExposed ( system: { default = nixpkgs.legacyPackages.${system}.mkShell { nativeBuildInputs = with nixpkgs.legacyPackages.${system}; [ git git-lfs yq jq python313 python313Packages.pip python313Packages.setuptools python313Packages.wheel python313Packages.cython python313Packages.ansible-core python313Packages.pyyaml python313Packages.jinja2 python313Packages.pyopenssl python313Packages.requests python313Packages.libselinux python313Packages.netaddr ]; }; } ); }; }

Just learned that you can use #NIX to build #OCI containers. To be fair the format appears to be a bit unintuitive at first sight, but I guess I'll give it a try soon anyway.

Alt...

# docker.nix { pkgs ? import <nixpkgs> {} }: pkgs.dockerTools.buildImage { name = "my-dev-env"; tag = "latest"; copyToRoot = pkgs.buildEnv { name = "image-root"; paths = [ pkgs.python311 pkgs.git pkgs.nodejs pkgs.bashInteractive ]; }; config = { Cmd = [ "${pkgs.bashInteractive}/bin/bash" ]; Env = [ "MY_VAR=hello" ]; }; }

But sadly none of this helps me understand what the c'n'p-crimes I've committed here a few months ago and what that first github repo it references is or why it is needed :D

(note, this is a shell.nix though)

#Nix #NixOS

Alt...

{ description = "Nix dev environment"; inputs = { flake-utils.url = "github:numtide/flake-utils"; nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11"; }; outputs = inputs@{ self, ... # Populate the inputs variable with all of its members }: inputs.flake-utils.lib.eachDefaultSystem (system: let pkgs = import inputs.nixpkgs { inherit system; config.allowUnfree = true; }; in { devShell = pkgs.mkShell { # packages = [ # pkgs.python3 # ]; nativeBuildInputs = with pkgs; [ git git-lfs yq jq python313 python313Packages.pip python313Packages.setuptools python313Packages.wheel python313Packages.cython python313Packages.ansible-core # python313Packages.ansible-lint python313Packages.pyyaml python313Packages.jinja2 python313Packages.pyopenssl python313Packages.requests python313Packages.libselinux # pip package is just called "selinux" python313Packages.netaddr ]; }; }); }

NixOS - Codeberg-Kommunikation optimieren und Troubleshooting

In diesem Teil optimieren wir die Kommunikation mit Codeberg, so dass keine Passwörter mehr eingegeben werden müssen. Git- und Codeberg-Troubleshooting inklusive.

#Nix #NixOS #Flakes #Git #Codeberg #Linux

https://gnulinux.ch/nixos-multi-user-setup-einrichten-und-die-kommunikation-mi

Seriously, nixpkgs derivations need a way to distinguish between inputs that are only required to produce certain outputs. E.g. if something is only needed to create the documentation of a package, it should not cause a mass rebuild.

Latest example: https://github.com/NixOS/nixpkgs/pull/497416#issuecomment-4509167991
An update to maven triggering a rebuild of a C library...

#nix #nixos #nixpkgs #maven

I've met lots of people in the Nix space who love to rant about Java. But differentiating between different build inputs / dependencies has been the standard in Maven/Gradle for 20 years for good reasons...
At the scale of the nixpkgs repository you can't afford to build things for now good reason.

#java #maven #gradle #nix #nixos #nixpkgs

New work laptop acquired, a Thinkpad T14 with AMD CPU and 64GB RAM.

Installed #nixos with Gnome and it's working fine.

Only glitch so far is that the NFC hardware causes a core to spin at 100% with a little IRQ storm, but I don't need that so I just BIOS disabled it and it's all good now.

Configuration based Nix seems easy enough to install everything I wanted... Except...

I need to get two things running to be compliant with corp policies and both lack #nix packages.

The first is Kolide, but it looks like there's a nix flake for that... So I'll need to use flakes even though I wasn't intending to.

The second is fleetdm and I need fleetd, for which there's no package, but fleetctl is packaged and can build fleetd, so I guess that's the route... But it immediately means part of the system won't be managed by nix and I don't know if I like that... I guess it's doable, just dirty.

Overall though... This laptop is nice, the newer gnome is nice, nixos is nice.

NixOS - Setup-Guide, Teil 3

Im abschließenden Teil zeige ich, wie man in nur je 30 Minuten weitere eigene Rechner mit der vorhandenen NixOS Konfiguration von Null an aufsetzt und mit Codeberg synchron hält.

#Nix #NixOS #Flakes #Linux

https://gnulinux.ch/nixos-setup-guide-teil-3

I hate NixOS but I love NixOS.
So i wrote a Blogpost to explain.

And no it is not just "i can never leave NixOS"
it is actual critique and i am probably gonna leave NixOS

Here is the Blogpost why that is

Though it is super long with an expected reading time of almost 20min if you go purely by WPM

I hope you like it and it is understanable. I appreciate all thoughts!

If you like that one: check out my website in general i bet you will find more things you like :3

#nix #nixos #nixoslove #linux #blog #blogpost

NixOS - Setup-Guide, Teil 2

In diesem Teil geht es darum wie Starkoch NixOS wirklich zum Sternekoch wird. Wie man die Integration anderer Köche vorbereitet und wie die Speisekarte gesichert wird.

#NixOS #Nix #Flakes #Linux

https://gnulinux.ch/nixos-setup-guide-teil-2

😑 seriously?

#nix #nixos

Alt...

GitHub screenshot, NixOS/nix repo, showing "A user you've blocked has previously contributed to this repository", namely Claude

Would be really great if

> nix run codeberg:user/repo

was possible. It works for #GitLab and #GitHub already. #Codeberg should also work. Instead, one needs to write this unergonomic thing:

> nix run git+ssh://git@codeberg.org/<user>/<repo>

EDIT: You could upvote this feature request: https://github.com/NixOS/nix/issues/14064

#nix #nixos

Security Advisory: Local privilege escalation in Lix and Nix https://lobste.rs/s/g0crsm #nix #security
https://discourse.nixos.org/t/security-advisory-local-privilege-escalation-in-lix-and-nix/77407

"nix" on Fedora Linux 44. What a time to be alive 😀

#linux #fedora #fedora44 #nix

NixOS - Setup-Guide, Teil 1

Das ist der Auftakt zu einem dreiteiligen Set-up-Guide. Es geht bei Null los und endet in einem Multi-Host-Set-up. Im Teil 1 beschreibe ich die NixOS-Idee, also den brillanten Paradigmenwechsel, sowie erste Schritte für Ein- und Umsteiger.

#NixOS #Nix #Flakes #Linux

https://gnulinux.ch/nixos-setup-guide-teil-1

An attempt at #nix​ifying udev rules:

https://gitlab.com/nobodyinperson/yannix/-/blob/main/OPTIONS.md#servicesudevsimplerules

#nixos