I wonder if mpd in a container with a front-end can solve your problems
I wonder if mpd in a container with a front-end can solve your problems
UART to USB adapter, use a terminal multiplexer on your laptop
How do you reach into your server with SSH disabled without lugging a monitor and keyboard around?
I’m using k8s at work and am planning to set up k3s at home, because even though PVCs and Ingresses are not the easiest to grasp and write in templates, I think the way I want to do storage is beyond the capabilities of podman which I used earlier. Also, Kubernetes on either end so knowledge transfer is ready
You can run a VPN and tunnel your outbound DNS queries over that. Heck, you could tunnel your DNS queries over TOR
I’d like a blog please
It’s actually better privacy since it talks directly to the root servers instead of cloudflare knowing all of your DNS traffic. Quad9 is a good alternative with better data policies
Thanks, I’ll take a look!
Your opinion is that systemd is objectively better being more than an init system?
I prefer my software to work as single units which can communicate using standard, agnostic technologies to one another, not be a gigantic binary blob which is too hard for even some of the most brilliant people in the community to understand
All I’m saying is that it shouldn’t have gone beyond being an init system. Is it so hard to understand that one might want one application to do one thing and do it well?
I didn’t know much about Linux when Systemd was adopted by Debian. And how would I make myself loud enough for people to notice? I still don’t have the technical knowledge to completely grasp the operating reasons why people chose it, all I know is that systemd was meant to be an init system, and now it is no longer just an init system. It’s in things it shouldn’t be in. I’m sure people worked hard on it but one program edging out general alternatives shouldn’t have been the way of development
I’m pissed off because he didn’t limit it to just being an init and made it into a much bigger mess
K3s is an embedded Kubernetes distribution by a Californian company called Rancher, which is owned by the Enterprise Linux Giant SUSE.
Kubernetes works on the idea of masters and workers. I.e. you usually cannot bring up (“schedule”) containers (pods) on the master nodes (control nodes for brevity). K3s does away with such limitations, meaning you can just run one VM with k3s and run containers on top.
Although if Kubernetes is too hard I would push you towards Podman.
I do not know the extrapolation for CSI but Longhorn is a storage backend of Kubernetes for persistent storage across nodes
Thank you!
I’ll have to try that. Thanks!
Exactly. It’s junk after that
Now that’s amazing
Debian. Always have, always will
It’s a coincidence, I was thinking about a PiKVM myself, although with much more modest hardware (a Raxda/Banana Pi Zero at best - I wonder if these can actually hold up). I’m not very familiar with PiKVM setup; do I need to compile the repository from source on whatever I run on these machines? Is there a minimum requirement for specs?
You might want to study more about SNI. Your ISP knows anyway