ruffsl

joined 2 years ago
[โ€“] ruffsl@programming.dev 1 points 16 hours ago

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.

[โ€“] ruffsl@programming.dev 3 points 1 day ago* (last edited 1 day ago) (1 children)

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.

 

Background:

[โ€“] ruffsl@programming.dev 9 points 4 days ago (1 children)

Thank you for all the work that goes into maintaining this instance!

[โ€“] ruffsl@programming.dev 1 points 2 weeks 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?

[โ€“] ruffsl@programming.dev 2 points 2 weeks ago* (last edited 2 weeks 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...

[โ€“] ruffsl@programming.dev 2 points 2 weeks ago (2 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.

[โ€“] ruffsl@programming.dev 2 points 2 weeks ago (4 children)

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

[โ€“] ruffsl@programming.dev 3 points 3 weeks ago

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.

[โ€“] ruffsl@programming.dev 1 points 4 weeks ago

I haven't gotten around to testing this yet, but I think they just share the Android app proot scaffolding. I wasn't too satisfied with the proot performance on Android in general using Termux, as with interpreted runtimes like python, the system call overhead really shows itself. That of course doesn't change here with nix-on-droid.

[โ€“] ruffsl@programming.dev 1 points 1 month ago

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.

[โ€“] ruffsl@programming.dev 0 points 1 month ago

@Ategon@programming.dev , this project's logo reminds me of your fun community icon artwork here.

view more: next โ€บ