When on God’s green earth would someone want to delete the partition table and not immediately create a new partition?

counterpoint: https://wiki.archlinux.org/title/Btrfs#Partitionless_Btrfs_disk

Btrfs can occupy an entire data storage device, replacing the MBR or GPT partitioning schemes,

I really like this take on it: https://forgejo.org/docs/latest/user/actions/github-actions/#familiarity-instead-of-compatibility

For all of these reasons, Forgejo Actions strives for familiarity instead of compatibility. We want users of GitHub actions to feel familiar using Forgejo Actions, even if there are some small changes here and there. Workflows should work with some minimal changes.

I think the same thing applies to Linux DE’s. Linux is not and never will be a 1 for 1 to windows workflows. If we chase perfect compatibility, we will be perpetually behind on a wild goose chase.

But, doing things like what KDE does, where most of the common keyboard shortcuts are the same, and things like virtual desktops allow for similar workflows with very little adaptation, is very reasonable.

Unfortunately, the browser extension is proprietary. They used to have an open source one but they stopped maintaining it.

Proprietary was a dealbreaker for me. There is no way to verify that it isn’t selling everything I type even if I do have it configured to point at a local server.

I’m also concerned that the extension may eventually no longer work against local servers as well.

https://github.com/languagetool-org/languagetool-browser-addon/issues/247

As an alternative, there is harper by wordpress: https://github.com/Automattic/harper

It is webassembly and runs entirely in your browser.

EDIT:

I will add that the rest of the languagetool ecosystem continues to work fine. Libreoffice now has a built in client, which you can point at your own hosted server. VSCode [1] also has their own languagetool extension. I use those and those work great. But in the browser I use harper nothing. I should probably install harper.

[1] Well, technically I use [code-oss]https://wiki.archlinux.org/title/Visual_Studio_Code), which gets the extension from https://open-vsx.org/

On kubernetes it’s pretty much the same amount of work. Every possible storage option exposes a generalized, abstracted “storageclass”, from which storage can be provisioned and mounted into containers.

https://kubernetes.io/docs/concepts/storage/storage-classes/

Well, I run a one node cluster…

But yes, I did use ceph via rook-ceph, because Openstack (a locally hosted AWS alternative), at least the Kubernetes version, wanted a ceph “cluster” to store stuff on.

Longhorn is much easier. Although again, my “cluster” was one node. I deployed it because I wanted snapshots.

I like to use more uncommon tools (it often bites me afterward but it’s funnier this way

I know the feeling.

How about this: https://docs.xcp-ng.org/installation/install-xcp-ng/#9-networking

Try setting a static ip address on xcp-ng itself, during the install phase. (this was how devices got onto networks before dhcp). You’ll have to make sure it doesn’t conflict with anything else on the network.

Kubernetes makes distributed storage easy.

Basically, all the components get deployed for you, since that’s part of what kubernetes is good at.

And then, services/containers can provision storage by requesting storage via making a “claim” and whatever distributed storage providee you have gives it to you.

https://sso.tax/

It’s unfortunately common, even though it probably shouldn’t be.

They don’t have to support it. It’s more that the database they are connecting to supports HA, and/or both are using shared storage. So when one container dies, kubernetes restarts another container on another node with the same shared storage attached.

Docker is often configured to automatically restart containers when a container dies, just in case it’s a one off bug or something like that, and kubernetes is like a more resilient version of that.

You can do oidc with the proxmox ui itself.

I use oidc with Incus, which is a fork of lxd and a similar software to proxmox, it can run vm’s and lxd containers.

Proxmox is also making their own: https://www.proxmox.com/en/products/proxmox-datacenter-manager/overview

source code: https://github.com/proxmox/proxmox-datacenter-manager

Two more that I have found:

https://docs.pegaprox.com/

And: https://github.com/xdkaine/uma-proxmox-wrapper-public

When people say that linux adds a second life to bad hardware, they don’t just mean making 8 gb of ram usable again. They also mean stuff like this, using dying hardware to it’s last breath.

Related: https://lorenz.brun.one/dealing-with-bad-ram-on-linux/

You can mark the failing parts of ram as explicitly bad so Linux avoids them, just like with hard drives. Another way to get more lifespan out of this hardware.

I run a single node cluster.

My single node has 256 gb of ram and 24 cores. I do this because, if you want a lot of ram/cores/storage, it is cheaper to get a used “tower server” type device and then upgrade it as you go over time, than it is to buy entirely new devices for every bit of ram you want to add to the cluster.

I like kubernetes because I like configuration as code, gitops, the way it abstracts over components so I can swap components out easily, the way that helm charts are an easier way of orchestrating containers, and a bunch of other things.

Clustering is merely one of many benefits of kubernetes, one that isn’t particularly important to me. Although, my opinion on that has changed somewhat recently. Waiting for a reboot is annoying, since I am rebooting the whole thing and I have to wait for each service to go down or come up before the machine reboots properly. But if I was running kubernetes as a virtual machines inside incus with multiple nodes, I could update each node one by one without the whole thing going down. Or, I could snapshot them, allowing me to reboot the host without waiting for kubernetes. But these things are mostly just somewhat nice to have, rather than a core feature I really require.

Even used stuff is expensive nowadays.

Anyway, you can buy these used refurbished small form factor business PC’s.

These things: https://www.servethehome.com/introducing-project-tinyminimicro-home-lab-revolution/

I was recently at a tech conference and I met a guy who was selling 16 gb ram one’s for 30 usd, since they had managed to track them down that cheap in bulk somewhere. What happens is that corporations or govt get rid of them due to warranty expiry, so they need to be offloaded somewhere.

You probably won’t be able to find them that cheap but it’s definitely more affordable than new stuff. It used to be cheaper but I mostly see 200 usd in my searches.

How many devices and of how many types do you manage with how many people?

Automatically patch is another solution.

Of course it’s difficult on the tech side. You can do something like failover/high availability, and then auto update one and it fails over if something breaks.

99% of cybersecurity news is what I call “cyberslop” and probably actively harmful to consume.

The vast majority of it is either so trivial that somebody else handled it, and you don’t need to do anything. Like they often overhype a malware that doesn’t do any novel techniques to get onto your systems and has already been added to the antivirus database anyways.

Or it’s so grand in scale that you can’t do anything, like nation states doing nation state things. Interesting yes, but it’s ultimately a waste of my time to consume because it’s not actionable.

Only a tiny fraction of news is actually actionable. It’s usually stuff like cve’s or zero days and the like. I just only really pay attention to those and ignore everything else.

Better, is probably to subscribe to an actual vulnerability feed so you don’t have to go through the news cycle.

I hope we get something that’s not distro specific. Docker/podman work for a lot of stuff, but some apps/services aren’t available via them, and I really would like an alternative to snaps, which often can ship those apps.

Also, these and the fedora one mentioned in the other comment appear to target immutable distros. Snaps work on any distro.

Cuz there are more than just browser caches I would like to nuke.

Cuz bleachbit is more granular, seperating out site data and cookies, enabling me to delete the 1gb alpine docker image downloaded by https://github.com/MercuryWorkshop/anuraOS without logging me out of anything that is using cookies. Firefox doesn’t appear to have that option.

Edit: cuz I use multiple browser profiles, and this can delete cache from all of them at once instead of me having to do it once per profile 2-3 times.

Show is better than tell:

Often, when viewing images, firefox “caches” the image in order to be able to load it faster when visiting that site again. Left unchecked, this cache (of images and other assets) can pretty much infinitely grow. Many other apps also have big caches.

Bleachbit actually is useful. Instead of hunting through your system and accidentally rm -rfing the wrong folder and losing all your precious firefox profile data, it enables you to quickly nuke all caches, freeing up a significant amount of space. I would probably free up 15gb+ if I ran it based on these images.

EDIT: just ran it. I freed up 6gb of space. Not 15gb. Huh. Still, pretty good though, and if you are space starved (I used to use a machine with only 32 gb of storage TOTAL), then it’s useful to keep things slim.