this post was submitted on 30 Sep 2025
24 points (92.9% liked)

Linux

9670 readers
477 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev
24
Experimenting with CachyOS kernel on NixOS via Chaotic's Nyx - NixOS Discourse (discourse.nixos.org)
submitted 1 week ago by ruffsl@programming.dev to c/linux@programming.dev
9 comments fedilink hide all child comments
top 9 comments
sorted by: hot top controversial new old
[–] dinckelman@programming.dev 3 points 1 week ago (1 children)

My biggest issue with Nyx, and the reason why I've yanked it out of my flake twice now, is because unfortunately this repo has no quality control.

If the Nix foundation Hydra fails, the whole merge is cancelled. If Nyx' build system fails, they just write the broken packages into the equivalent of shit_that_broke.json, and still push it.

Given that I've only wanted to use 1 package from the entire repo, it is shocking that it's both impossible to bisect for debugging, but also increasingly frustrating to get any help with.

This is especially obvious for kernel packages, where nixos-unstable is a little behind Nyx, so fully expect your builds to error out frequently, if you use applications, reliant on specific kernel functions, like what openrgb/openrazer people experienced a few releases ago

[–] ruffsl@programming.dev 1 points 1 week ago

Appreciate the heads up. Looks like they use merge bots to auto update the package version JSON files for git packages, making for a very large/frequent commit history. Was that what made bisecting imposable?

I also see they pin the nixpkgs input, but do others normally modify that nixpkgs input to follow their global nixpkgs from their own system flake, or does that invalidate the use of Nyx community cache?

[–] just_another_person@lemmy.world 1 points 1 week ago (2 children)

Why? You could just diff and build for yourself. This is a bit unhinged...

[–] ruffsl@programming.dev 2 points 1 week ago (1 children)

I wasn't sure if these results were specific to my older hardware, or more generalizable to newer systems.

[–] just_another_person@lemmy.world 1 points 1 week ago (1 children)

Wait...what? If anything, building on your current hardware would yield more realistic results.

What exactly did you do here, just swap packages?

[–] ruffsl@programming.dev 2 points 1 week ago (1 children)

I don't have resources to locally build an optimized kennel for every update for each of my systems, thus my interests in keeping with a community cache.

I didn't do much here, just swapped the kernel via config and ran some benchmarks. I posted as I was more curious to hear of what engineering trade offs may be at play, and what experience folks have had in daily driving CatchyOS's kernel patch sets.

[–] just_another_person@lemmy.world -2 points 1 week ago (1 children)

You...just run commands. What resources are you talking about? It's a one liner.

[–] ruffsl@programming.dev 2 points 1 week ago* (last edited 1 week ago)

Compiling the Linux kernel from scratch takes over an hour on this laptop. Given I'm tracking the unstable channel on a rolling distro means doing that several times a week. Ain't nobody got time for that. Or at least I don't...

[–] Telorand@reddthat.com 1 points 1 week ago

"I was so focused on whether I could, I didn't stop to consider whether I should." —inventor of the Steam Brick