I could imagine bootstrapping via Bell Labs Unix from the 90's would be more authentic, yet demanding LFS experience. I wonder how far back computer historians could bootstrap up to a modern compiler for integrity and verification purposes?
https://www.owlfolio.org/research/bootstrapping-trust-in-compilers/
https://www.theregister.com/2025/11/07/unix_fourth_edition_tape_rediscovered/
I've observed some notable improvements when benchmarking with the CachyOS kernel on NixOS via Chaotic’s Nyx using moderately old hardware:
https://programming.dev/post/38304031
Haven't yet tried replicating the same comparison on newer hardware, but would be interested to see what others have tested. Any observations?
You should be able to rebuild offline if the minimal change set is self contained enough, as in purely local. Did you update any other inputs? I guess you could be missing some kind of extra TLS or CA store dependency for adding custom CAs, but that doesn't seem likely for regular NixOS install. I use flakes instead of channels, so I wouldn't know what else may be blocked you. A stdout log may showcase your error more clearly.
I think you may need a successful switch to actually apply the addition of the proxy CA to your root CA store before attempting any other changes that could require reaching out across the network. At least that was the order of operations I had to follow to remove an offline remote cache before attempting any package updates.
I'm in search for the same white whale. There's quite a bit of documentation for multi-seat configurations for Linux, i.e. supporting the use of multiple screens and keyboards for separate simultaneous logins.
However I'd like to remote into a separate game scope session with its own human interface inputs and virtual audio and video outputs, as the same primary user normally logged in active desktop environment session. I'd like it so the remote and local sessions would not interfere with each other state, but without necessitating multiple Linux users for each session use case.
That last bit is what makes it more tricky and very niche. Supporting essentially multiple desktop environments probably demands separate user debus sockets. Using c groups via containers makes that viable, but like you, I also like to avoid containers and extensive volume mounts.
I top linked the most recently published video mostly for the introductory breakdown in ternary logic equivalence, but the interview with the ternary researcher, Dr Bos, also linked in the description above includes a number of corrections and accurate description of the subject.
Yeah, definitely not a lost art or anything, as physical ternary signals already have applications in communication like high data rate interfaces. Still, would be interesting to see ternary expand into logic domains with emerging developments in TCMOS research.
This is discussed around the 27 min mark of the video with Dr. Steven Bos, particularly in maintaining voltage thresholds for signal propagation when using multiple devices, in context of logic, memory, and communication use cases. Interestingly, for example, GDDR7 and USB 4.2 already use physical ternary signals.
Edit: signal to noise ratio is also discussed at the 40min mark, also with respect to increasing information density vs complexity from higher symbol bandwidth, or terms of radix vs frequency.
Thank you for all the work that goes into maintaining this instance!
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?
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...
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.
I wasn't sure if these results were specific to my older hardware, or more generalizable to newer systems.