I happily use Fedora for workstation purposes but hate to admit I use it, so it’s an accurate critique. It’s a great operating system though, naming aside.
I happily use Fedora for workstation purposes but hate to admit I use it, so it’s an accurate critique. It’s a great operating system though, naming aside.
It literally was in the opening paragraph. Previous years keynotes are available in a playlist here, so I assume they’ll do the same for this year’s keynotes as well. The event only just ended yesterday.
Open Source Summit 2024 keynotes. I don’t think any of the recordings are available yet.
The malicious code is only thought to have affected deb/rpm packaging (i.e the backdoor only included itself with those packaging methods). Additionally, arch doesn’t link ssh against liblzma which means this specific vulnerability wasn’t applicable to arch. Arch may have still been vulnerable in other ways, but this specific vulnerability targeted deb/rpm distros
I hope you’re right and this isn’t about them getting ready to DRM brush handles to brush heads. Sonicare brush heads are ridiculously overpriced compared to the knock offs
I mean, certain airlines are starting to adopt size policies which will grant you an additional seat if you are overweight. Why is it such a stretch to believe that tall people should receive the same accommodation?
This is a feature of SATA devices too. Use UUIDs in your fstab unless you enjoy playing musical chairs with your mount points
Been a sync user since 2010. LJ has taken a lot of breaks but has always come back
You need to use chown if you want to own the libs
The LE steam decks are shipping with a screen manufactured by BOE.
Mine just arrived and indeed has 3 dead subpixels (2 blue, 1 green)
LE, order placed 10:19 Pacific. Not shipped yet, but packaged. Guess the Canada shipping backlog is real – hopefully it comes this week.
But you actually don’t know what monero is being used for when it’s used in transactions, no one does. You just have a bias that if people want to keep their transactions secret, it must be illegal.
You could make the same argument for cash.
This is called the “Door in the face method” of bargaining. Start with a request so high and absurd that you “slam the door in their face” because it’s so absurd.
The next time they try, they’ll come back with an offer that sounds far more reasonable than the original request. Since you’re still primed with the previous context, your brain makes it sound less bad than it probably is ("At least it’s not the first offer!). You’re more likely to accept after this.
The opposite technique is called “foot in the door”, start with a small request (get your foot in the door) and then increase the ask after the small request goes over.
You need a budget, but it’s not free.
But with Intuit, you are the product, so it’s only free in the sense that they get your info and you get mint in return.
I don’t really use it for this, but here are some things I do use it for:
I mostly just use it for metrics scraping though
Air Canada: we’re not happy until you’re not happy
I mean you could just use docker and if all you want is a plex container, it may be the way to go. Kubernetes is definitely a lot to learn if you are kind of hesitant to get started with it in the first place. I would just say that single binary distribution like k0s just basically becomes a docker on steroids when used in a single node environment. I’ve become so familiar with k8s that going back to docker feels like a massive downgrade for anything but a simple and straightforward task (which a single plex container, admittedly is).
Just do yourself a favour and if you go that route, at least use docker-compose to template your container. Searching through your bash history to find the command you used to start the container is just a recipe for frustration waiting to happen.
One major feature that k8s has which docker doesn’t (I mean, there are lots tbh) is the ability to use helm charts. These are basically install templates, if you don’t like the defaults then you can provide your own (assuming the chart author has written good charts) and the helm chart will template your values into the default chart and spin up a bespoke version for you.
For instance, a theoretical helm chart whose purpose is to install qbittorrent would likely provide the following:
However, say this ingress by default doesn’t use SSL, but you want to ensure you’re using https when you enter the password on your web interface, but the rest of the chart defaults meet your needs – then a well written chart would allow you to provide values that let you template the SSL setup for the ingress object and provide for cert-manager to go and provision some certificates for your provided hostname with Let’s Encrypt.
Helm charts basically are a way to provide a sane set of defaults which can be extended and customized to personal needs.
k8s (or the lightweight cousins) may not be ideal for you and, as I said, I’m biased because I’m a certified k8s admin, so tinkering with k8s resembles something like fun for me. Your mileage may vary :)
Terms:
A complete kubernetes cluster for a homelab probably would be overkill (unless you really wanted a kubernetes playground, which some folks do). However, yes, my recommendation these days would be k0s directly. I did use k3s up until recently but gave k0s a shot and realized it’s a bit lighter on resources, more configurable (for instance you can choose to run cri-o instead of containerd, which isn’t an option with k3s) and has some extra features like letting you put helm charts with their values directly in the k0s config.
k0s vs k3s just comes down to personal preference but for me it came down to:
As for distro to run it on, I use MicroOS myself (immutable os, I have it set to automatically update and reboot once a week), but Debian is my second choice and my personal preference for server distros. The beauty of this setup is the container host really just needs the bare minimum to run the containers. There’s less that can break because the containers are all managed by others upstream so the main concern of breakage areas basically becomes did server boot and did k0s start?
NFS is fine and actually natively supported as a kubernetes volume type: https://kubernetes.io/docs/concepts/storage/volumes/
Your option could be to mount it directly to the host first and then use a hostPath to mount it to the container, or just mount the NFS path directly to the pod. As for permissions you may need to do some mapping, but kubernetes also has security contexts that can let you alter the UID of the user running the pod. If you need user to be privileged and root, you can do that or if you need UID 5124 you can do that too.
If your goal right now is a Plex server and not much else to start then this makes things very easy:
You can add nginx ingress, cert-manager, metal lb, etc later on down the line if you get curious and want to expand a bit (sonarr, radarr, adguard home, etc)
You could also just go full stupid with kubevirt, but it’s not a project I’ve personally explored using. Iirc it basically allows for the provisioning of more persistent VMs with k8s rather than containers
Opinion? Try again. It’s called slander.