I love Linux gaming. Got the Steam deck for my SO. She kind of hates it BECAUSE it’s not a no tinker device.
Like if you pick the right games you’re good, but want to play the “wrong” game, or want to mod, and your back to tinkering.
I don’t mind it at all, it’s just what PC gaming has been for me my whole life, but for her, someone who only experienced gaming on newer consoles it’s a pain in the tush.
Neat! What proccess did you follow for building distroless? I was using buildah, mounting dir, yum installing into the mount, and exporting that container off.
No nix is super cool! I really like the idea that guix and nix in having that system as code from build to deployment. I am not sure yet on how I feel about it for fleet/cluster deployments, k8s schedulers, network patterns like service meshes, ETCD, and operating on labels and cluster state are all super powerful.
I have looked too into using nix to make OCI containers and OCI containers to make flatpaks as well. All where they make sense of course.
Containers are really awesome, but take a bit more to troubleshoot sometimes. Docker is not the only method to run them either. I prefer podman actually, but K3s is the next logical step for running services in a more powerful setup.
All true FOSS too
OpenQA is the best answer that I know of for this too! You can even trigger from Gitlabs CI jobs if you are already here.
On a similar note, I want to try boot2container as my PXE target next personally
Setup a good kickstart script (even if it’s just enough for Ansible to Configure it the rest of the way). It’s awesome when messing with a system to be able to reboot select the reinstall PXE boot option and get a fresh install to tinker on.
Noticable shift in his content for me to me too.
Technical details: ������������������������������������������������������������������
Does this mean anything to anyone else? I just see question marks (on Lemmy and Fenic)
Not of Github, but Gitlab is working towards it now.
It’s the coordinated decentralization that really defines web from web2 and 1. Cooperative vs competitive coordination is just a sub strategy within that, but I don’t think either strategy is always best for all problems.
I like Dan Olson’s video but I don’t think it’s truly unassailable. There is some real use cases for block chains in low trust networks. One of those being global monetary policy. Another critic is that web3 applications (like Mastadon and Lemmy …) I think is moving forward even more so as the age of easy money comes to a full close.
While it is funny (honestly replacing any tech term with circlejerk in a tech article makes it sound so funny to me, I have the mind of a child), it’s not very relevent here.
Honestly even this platform, but any public platform without e2e and the direct choice of who to share it with.
Can you create custom decryption keys? I like the idea of an easy to use encryption mechanism for non private platforms.
Fedora is a separate entity with RedHat employment as a prerequisite for some of the key leadership roles. It’s ran and designed to feed into RedHat.
I love Fedora, heck I like RHEL too, but they have gone from my top recommendation for enterprise solutions to me having to research whether their offering is even FOSS and constant concern that a EULA will put us in legal jeopardy for treating our FOSS product choices like FOSS.
“Wait I’m being held indefinitely and being censored online? That’s only supposed to be used on Terrorists and Antifas!”
Honestly it’s wild how many people after Jan 6 have this wild notion that the rioters there are being persecuted worse than any other rioter…
There is always some solutionizm in tech, but I’m interested in containerzation as a solution to problems I’ve had with configure drift building up on my systems and make it easier to share and work with the community.
The immutable desktop work to me is specifically working on bridging the gap between the UX of a local admin (you know wanting custom configuration and fast reaction to user input) and the industrial expectations of being able to test and track every change and reduce the number of different pieces you need to operate a system.
Hopefully we can lose some of the industries bad habits though. Like “relying on this proprietary piece is ok because we can move faster” or making other excuses as if you are going to have to explain to your boss why some metric looks bad instead of just trying to make the best system or solution we can.