ruffsl
I’m a robotics researcher. My interests include cybersecurity, repeatable & reproducible research, as well as open source robotics and rust programing.
- 112 Posts
- 127 Comments
1·2 months agooh, my hand typing was atrocious, that’s what I get for not voice dictating with my regular assistive tech.
Indeed it’s just a placeholder logo until a real human artist would like to contribute, as I’m no talented graphics designer myself. I still think it serves a purpose to quickly and visually illustrate what the project does, as all of the key words and terminology used by similar efforts never reached a consensus or becoming a household names.
Xbox initially called this Copilot (lol, on brand), Apple calls this buddy mode, PlayStation just filled it under Access™, so something to link words to an intuition is better than nothing at the moment. If you have any suggested SEO for folks to find this is that’s what their looking for, let me know. I’ve been in the trench for too long to know less technical jargon folks would use.
I’m also already transparent in using AI for rubber duck sessions in the public pull requests, so anyone agents AI would already probably object to its origins.
1·2 months agoNot sure if something like that would even support x86 or C99, so would probably still need an older mainframe and early GCC source tree. Could probably get by with a virtual emulator for the former.
Would be good to cross post this to:
https://programming.dev/c/nix
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?
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.
5·4 months agoI 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.
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.
Indeed perhaps. I’d really like to see something like a Content-addressed Storage model from snix get upstreamed. That could really revolutionize bandwidth requirements for nix package updates and store sizes. Imagine downloading only the binary diffs for updates to packages like large modern browsers, IDEs, election apps, etcs, that mostly share common files across versions and packages. Suddenly, daily driving a rolling distro on the bleeding edge would be no more taxing on networks or disks than your average infrequent Debian update.
Sounds like their target customers are commercial service providers and industrial device manufacturers using NixOS, but need to support stable deployments for longer than NixOS’s current 6 month release cycle. Probably not to applicable for individual desktop users, but they still plan on hosting a public channel and cache for newer releases.
IBM acquired the company behind Fedora Linux. Although I doubt they had any corporate influence in the production of this particular vlog.
I wonder if they would have had better luck with Kubuntu or KDE Neon? Perhaps if they’re still on KDE by the time KDE releases their Arch distro variant, they could test that too on their hardware.
Given the amount of trouble shooting demonstrated throughout the video, don’t think the marketing was entirely positive…
Appreciate the detailed context, and thank you for your work!
It’s a great video, and I hope the author is able to publish more nix content like this again soon. We’ll just have to watch their blog’s RSS feed in the meantime.
I never want to go back to an OS I can’t diff or track under revision control. I just love being able to solve an issue once and move on without worrying about if I’ll forget all the minutiae of changes I made to my customized system when it eventually comes to migrating workstations or replicating across my computers.