Towards simpler #btrfs raid setup with #disko:

https://discourse.nixos.org/t/btrfs-raid-with-disko/52503/3?u=nobodyinperson

#nix #nixos

This article is misleading non NixOS users in some way and spooks them unnecessarily.

https://www.zdnet.com/article/nixos-linux-review/

He's misunderstanding things and doing it wrong and thus thinking & portraying NixOS as unnecessarily hard. It's clearly not the right way.

Should I write my reply blog/content dispelling some of the misunderstood things?

#nix #nixos #blog

I want to write a config file to `$HOME/Dev/.my-config` using nix ... how would I do that?

I only find how to write files to the home directory, but I want to place files everywhere around the system I need them to be 😬

#nix #nixos #nixdarwin

You're telling me I only need to do

```
{
services.caddy = {
enable = true;

virtualHosts."oolongtechnologies.io".extraConfig = ''
redir https://www.oolongtechnologies.io{uri} permanent
'';
virtualHosts."www.oolongtechnologies.io".extraConfig = let
site = self.packages.${pkgs.system}.oolong-site;
in ''
root * ${site}
file_server
'';
};
}
```

And don't need to set up 5 YAML files and figure out resource constraints to schedule full containers in order to host my static website?

Bye k8s welcome to a brave new world

#Nix #NixOS

On est au #FOSDEM à Bruxelles aujourd'hui pour deux présentations.

@pierreozoux fera une présentation technique sur notre infrastructure, basée sur #k8s et #nix, à 15h30 et sera diffusée en direct ici : https://fosdem.org/2026/schedule/event/ZPLYXT-libresh-nix/

@unteeem fera une présentation sur le modèle d'organisation coopérative qu'on est en train de construire avec @LaSuiteCoop pour développer les communs numériques.
Elle aura lieu à 13h00 et diffusée en direct ici : https://fosdem.org/2026/schedule/event/THRG3E-la_suite_coop_model_for_digital_commons/

#cooperative #communs

Such an amazing effort by @mynacol to compile #Zotero from source in nixpkgs. This will make it possible to easily try out Zotero patches or even make your own version with custom changes. Power of Nix! 💪

https://github.com/NixOS/nixpkgs/pull/483099

#nix #nixos #nixpkgs

@dbtechyt I got it to build and run with #nix (will publish later and probably submit to #nixpkgs), but I keep running into this issue, which completely cripples usage as you can't add items 😅

EDIT: one needs to add categories first, the onboarding UX is not perfect yet

https://github.com/PanSalut/Koffan/issues/37

Is it just me, or is `nix-store` just awfully slow ? Nix is usually fine in terms of performance, but ~1h45m for a single command that didn’t even fix my problem is starting to get really painful…

Are there simple performance boosts I can get as a Nix / NixOS user ?

#Nix #NixOS

Alt...

A screenshot of a terminal where I ran the command `sudo nix-store --verify --repair --check-contents`. It took the command 1 hour, 48 minutes and 6 seconds to run, and printed a grand total of 4 lines in the console : reading the Nix store... checking path existence... checking link hashes... checking store hashes...

@xameer I've heard about overlays quite a lot, especially regarding the #nvim setup, but as I want to keep my editor's config portable I never dived into it.
I'm sure it's like every thing with #nix : sounds hard, hard the first time, and then it becomes the most natural thing in the world.

@Linux_in_a_Bit @zstg
For me the math probably won't change, coz nixpkgs is supported not only on NixOS, but also with other distros and even Mac. Also with android via nix-on-droid(like termux - cli based)

I also use flatpaks for certain applications (declaratively though), but still nixpkgs is my first choice always. Coz I can manage the dotfiles too with nix home manager.
#nix #nixpkgs #flatpak #distro #packagemanager

@nobodyinperson If you want the local file system assets to have timestamps matching the last #vcs modification, then yes of course.

The GH repo works as a #Nix flake:

nix run github:alerque/git-warp-time

The version in #nixpkgs isn't 1-point-0 yet but as I said there are no major changes with that release. The 0.8.x series works just fine too ;-)

Well apparently I now need to learn all about #Nix. The summary I read mentioned "configuring the whole system". That didn’t sound like something I wanted; but I’m willing to learn more before I make any decisions.

I have an issue using my graphical tablet with hyprland on nixos. If you have any thoughts about finding the cause and fixing it, please reply here or on Nixos discourse. Boosts appreciated

https://discourse.nixos.org/t/100-load-of-one-core-using-a-graphical-tablet-on-hyprland/73553?u=liveifsh

(text in alts)

#nix #nixos #hyprland #debugging

Alt...

I have been using nixos several moths now, almost everything works like a charm. One day I bought a cheap graphical tablet, I checked that it’s supported by linux. Everything worked, but I had sudden crashes using drawpile (Related issue, I closed it for now because I suppose it’s a driver issue, not a software one). Solution was to use an AppImage and crashes stopped. But now there’s a different problem. After 15 minutes or something like that my laptop starts heating up and I see constant 100% one cpu core usage in btop. The process in question is .Hyprland-wrapped (I use uwsm as suggested in hyprland wiki). What can I do to investigate the problem further? Maybe I should do some profiling and debugging with GDB or something like that?

Alt...

Screenshot from btop with 100% single core load

Alt...

Tablet that I have (truncated output from hyprctl devices): Tablets: Tablet at 55a66b466410: xppen-deco-640-pen size: 159.8390243902439x90.01923076923077mm

Installing Every NixOS Package https://lobste.rs/s/u7yz80 #nix
https://unnamed.website/posts/installing-every-nixos-package/

Organising my #nix code and splitting out sharable things into a separate repo. Here for example is my package for #forgejoAneksajo ( #forgejo + #gitAnnex support) with a couple of my patches applied:

https://gitlab.com/nobodyinperson/yannix/-/blob/6353a52f63ec866b39fd50046f875587fcfed49e/packages/forgejo-aneksajo.nix

> nix build --refresh gitlab:nobodyinperson/yannix#forgejo-aneksajo
> result/bin/forgejo -v
forgejo version 13.0.3-git-annex2 built with go1.25.4 : sqlite, sqlite_unlock_notify

@embedding_shapes Yeah 😅 That is quite common in the #nix #NixOS realm, but is also often warranted. In this case, my approach really is a bit backwards and I'll switch it around.

Thoughts on keeping parts (assets *and* #nix code) of your public #NixOS config private?

https://discourse.nixos.org/t/public-reusable-flake-with-private-parts/73049

Terrible #nix error messages... 🙄 One of the things making #NixOS annoying at times.

*Something* (not my files) puts types-typed-ast (removed in NixOS 25.11) into environment.systemPackages and I cannot figure out what. `options.environment.systemPackages.definitionsWithLocation` at least gets me a huge list of .nix files adding to systemPackages, but not line numbers (?) nor the information which one actually adds that broken package, unless I manually go through all 😩

@irfan @ahappydeath The cool thing with #nix is that "you can make your own AUR" by putting a nix file or a flake out there on a git hosting platform of choice, which people then can source. You don't even need to put it into nixpkgs, although that's not too hard once you have figured it out for yourself.

I also have several AUR packages, and the AUR infrastructure and Arch packaging in general is not well designed for sharing.

@agowa338 So then how would you do it? How do you mark specific files to be opened with specific old independent versions? Turn individual files into a custom file format with a #nix or what preamble that then opens itself as I described?

@agowa338 I mean nix also works on non-nixos, I think requiring that is reasonable. I know of all the other app distribution systems, I am more interested in the mechanism to make double-click-file-to-open-creating-version and the equivalent during saving work ergonomically. Especially the I-use-a-custom-patched-version sounds very much like #nix.

A #nix flake next to the file would basically solve this, but one would need to go through the terminal. `nix develop` or something, then use the provided executable to open the file. But that's not very ergonomic. I guess it would be possible to turn the file into some kind of nix wrapper or polymorphic file that opens itself with a specific version on click. Does something like this exist? 🤔

#nixos

#Zigbee #HomeAutomation without #HomeAssistant, instead all defined in #nix / #NixOS, this is neat! 😲

https://quackhack-mcblindy.github.io/blog/house/

(Too?) many months of work, one of the release I'm the most proud of.

#Lix 2.94.0 is now officially available.

https://lix.systems/blog/2025-11-18-lix-2.94-release/

#Lix 2.95.0 will be even better.

#Nix #NixOS

#Guix has already raised half of its annual budget 👇
https://guix.gnu.org/en/blog/2025/update-on-the-guix-fundraising/

This is great but the journey’s not over!

If you can, if you care about #Guix (or #Nix!), about #FreeSoftware and independent projects, consider donating. 🤲

Alt...

Badge with the Guix logo reading: "Proud donor, may Guix prosper"

I just discovered a new reproducible builds toolchain and software collection:

https://stagex.tools/

Has anyone with #Guix or #Nix experience looked at this? What are the similarities, what are the differences, beyond the use of OCI containers pointed out in large letters on that site?

I'm in the process of write my second flake.nix file and so far it goes smoother than what I feared 😅 .. BUT!
I'm packaging a rust app with a gui, so needing X11 and a bunch of libX* , and I'm currently in this loop:
> nix build
[wait 10mn for cargo to build from scratch]
> ./result/bin/my_app
Error: libXbla.so not found
> [add pkgs.xorg.libXbla to buildInputs]
> repeat

Is there a way to speed this up? Can I tell nix to cache some/most of what cargo compiles? Or guess the deps quicker?
#nix

ok now I'm stuck 😥
if I try to run my app it crashes instantly with:
> Library libxkbcommon-x11.so could not be loaded.

I've added libxkbcommon to buildInputs.
If I run $ find /nix/store/ | grep libxkbcommon-x11 , it find several instances of libxkbcommon-x11.so , for example:
/nix/store/klv07fh03501djj4q146z6pl7ywc550w-libxkbcommon-1.11.0/lib/libxkbcommon-x11.so

So I guess I have to fix the LD_LIBRARY_PATH of my package but I'm not sure how?
#nix

he choose by following some YouTube howto maybe not the most adviced choice (but he keep this way)

I call this "Linux by the north path..."

#linux #arch #nix #hyprland