

Kitty has a setting that makes Ctrl-C copy text, but only if you’ve selected something. If you haven’t it does a regular break. Best of both worlds!
Kitty has a setting that makes Ctrl-C copy text, but only if you’ve selected something. If you haven’t it does a regular break. Best of both worlds!
A 10 Gbps network is MUCH slower than even the smallest oldest PCIe slot you have. So cramming the GPUs in any old slot that’ll fit is a much better option than distributing it over multiple PCs.
That already happened though. Tens of thousands of games on Steam can be played by hitting the install and then the play button. Only a few “competitive multiplayer” holdouts with rootkits and an irrational hatred of Linux don’t work.
Absolutely, that’s basically the same thing
I once switched from Debian i386 to amd64 in-place. That was MUCH harder than you would expect, I guess somewhere between medium and hard in your list. That server is still running that install btw, so in the end it all worked out.
I’ve started using this method in the past weeks and it mostly does what I want it to do: https://github.com/eriksjolund/podman-caddy-socket-activation/
That is a very useful article, thanks for linking it!
The difference might be HTTP vs HTTPS. On a Pi the extra CPU load to properly encrypt the HTTPS stream is probably significant.
This simply isn’t true. FF on Android is fine and allows you to use tons of extensions for far more things than ad blocking, such as the wonderful Consent-O-Matic that automatically deals with cookie popups for you. Huge timesaver on mobile.
I have read them. While Vaxry makes his points in typical Vaxry fashion he’s not wrong IMHO.
I think it’s ridiculous and unprecedented to demand that other open source projects adhere to the rules of another project. If more projects would do that then where will it end? The big COC wars where camps of open source projects are split and fractured along opinions of how one should moderate their own communities? This is not the way to work together with others.
The demand was not about Vaxry’s own behaviour outside freedesktop, but about his community. I disagree that behaviour there reflects on freedesktop itself. Hell, I think a lot of people who use Hyprland couldn’t even explain what freedesktop is and does.
So in my opinion Vaxry was right to refuse the demand, and right to publish the email conversation about it. Openness in open source about these sorts of things is important. His hostility in writing about it is something else altogether. Feel free to judge him on that, but it doesn’t retroactively excuse freedesktop’s behaviour.
Last part isn’t true, he was banned for refusing to give his own community a COC that was compatible with the freedesktop one. Which is quite an overreach IMHO.
Object storage (the S3 API stuff) is the most logical answer here, it’s much simpler and thus more reliable than solutions like Gluster, and the abstraction actually matches your use case. Otherwise something like an NFS share from a central fileserver works too.
But I agree with the other comment that you’re trying to do kubernetes on hard mode and most likely with a worse result.
Thunder has experimental support, haven’t tried it yet though (says it costs extra battery)
btop has GPU stats in recent versions.
Good on you for getting it fixed. One of the reasons Linux is a great OS in my opinion is that everything is in the file system and not in some arcane hidden thing. So every problem is solvable without a reinstall if you’re motivated enough to figure it out.
Most of the delays are effectively from pre-ordering. I ordered mine just after last Christmas, got it the first week in January. Would have probably been faster without the holidays. Also, get the AMD model if you can, it’s much better than the Intel offerings.
That’s not true, “regular” Li-ion batteries have become tremendously cheaper and have increased their capacity by a lot in the past decade. The next jump in their capacity is about 50% more again, and it’s already being previewed by the big battery manufacturers. They’re not going to be cheap though.
PostgreSQL shitting itself is generally a hardware problem. I’ve had it “detect” faulty RAM modules in a few cases in the decades I’ve been using it.