It’s so superior that they finally added color in 2024!

We live in a wild world where people feel so confident about the wayland snake oil that they only added color in 2024!

On the one hand sounds sensible, on the other hand I wonder if that’s possible when wanting to apply things that need to take place as early in boot as possible (eg.: modprobe options for a module, apparmor profiles, …).

The OP doesn’t say that they have a trademark. For me it sound as they don’t have one.

Ooooh might have misinterpreted that, still not fully sure on a second read. But in which case, it’s even more important that they get that “hoarder dot app” trademark filed.

Absolutely depends on what do you want it for and what resources can you apply on it (learning, set-up, etc).

That said, MySQL is owned by Oracle. The more-or-less blessed alternative IIRC is MariaDB.

Trademark is weird. Like, from what I can understand (IANAL and all the ANAL disclaimers) you can’t trademark “motherfucker” or “mother fucker”, but you can trademark “Mother Fucker’s” for, say, an escort service of dirty nuns.

They registered “hordr”, not “hoarder”. It’s not your fault that there exist valid words in the dictionary, that describe what your app is doing, that they are not using.

This is just the usual case of domain and trademark squatting. If they attempt to further raise a finger (which from what I have read, from a judiciary point of view they haven’t), you have good grounds to countersue. You can also provide the C&D as evidence of threatening and harassment and probably counts for suing the party who sent it if they used a third party, as there’s supposedly a penalty for issuing false or trolling C&Ds.

That said: in a decent legal system no one should be able to trademark dictionary words. I’d suggest you change your trademark from “hoarder” to “hoarder.app” or something similar, as at the moment you trying to trademark a dictionary word is a vulnerability point that opponents with more money to waste can use to attack you, as this shows.

Since the idea is that the “root partition” is immutable, serious question:

How do you fix a hardware config issue or a distro packaging / provision issue in an immutable distro?

Several times in my Linux history I’ve found that, for example, I need to remove package-provided files from the ALSA files in /usr/share/alsa in order for the setup to work with my particular chipset (which has a hardware bug). Other times, I’ve found that even if I set up a custom .XCompose file in my $HOME, some applications insist on reading the Compose files in /usr/share/X11/locale instead, which means I need to be able to edit or remove those files. In order to add custom themes, I need to be able to add them to /usr/share/{icons,themes}, since replicating those themes for each $HOME in the system is a notorious waste of space and not all applications seem to respect /usr/local/share. Etc.

Unless I’m mistaken on how immutable systems work, I’m not sure immutable systems are really useful to someone who actually wants to or needs to power user Linux, or customize past the “branding locking” that environments like Gnome have been aiming for for like a decade.

Did you follow any particular tutorial for this migration to k3s that you could recommend?

…backup servers? 👀