LVM itself does not provide redundancy, that’s RAID.
I think this is potentially a bit confusing.
LVM does provide RAID functionality and can be used to set up and manage redundant volumes.
See --type and --mirror under man 8 lvcreate.
LVM itself does not provide redundancy, that’s RAID.
I think this is potentially a bit confusing.
LVM does provide RAID functionality and can be used to set up and manage redundant volumes.
See --type and --mirror under man 8 lvcreate.
My next suspicion from what you've shared so far apart from what others suggested would be something out of the http server loop.
Have you used some free public DNS server and inadvertently queried it with the name from a container or something? Developer tooling building some app with analytics not disabled? Any locally connected AI agents having access to it?
You say you have a wildcard cert but just to make sure: I don't suppose you've used ACME for Letsencrypt or some other publicly trusted CA to issue a cert including the affected name? If so it will be public in Certificate Transparency Logs.
If not I'd do it again and closely log and monitor every packet leaving the box.
I adored Budgie precisely because it was still on X11 🥲
Anyway, for a relatively simple and clean holistic GNOME-that's-not-GNOME, it's a very polished desktop. Worth checking out for your F&F.
The need to think about and deal with snaps is the reason I don't recommend Ubuntu to noobs in general. It's confusing and unnecessary and adds to the frustration of being forced to make judgement calls about things you don't want to understand just to do your thing (we have enough of that as it is). And if you do decide against snaps, it's a bit of an uphill battle and it's easy to start feeling that the OS, like what they came from, is antagonistic. Canonical decided to isolate and take control of part of the Ubuntu ecosystem with snaps and that has made the distro a bit more niche compared to before.
For better or worse Ubuntu is also known to be on the edge with new developments on the desktop. Switching to new shiny desktop environments between major versions, being very early on Wayland-first, etc. Having to learn new OS UI after an upgrade is not ideal if you are not an enthusiast.
Other than that, Ubuntu can be a fine distro, both for server and desktop. If you either accept the particularities like snaps or know how to work around them, it can be a very good experience and it's well-maintained in general. But it's less of a no-brainer and more situational if it's appropriate or not.
Like Alpine or Gentoo: Great distros but for different reasons not anything I would recommend a non-technical Linux virgin to replace their Windows or macOS with.
Good first distros for beginners:
Not Good first distros but still getting picked up by people who don't know:
Everyone: If you've only used one of the latter, try another distro before you believe "Desktop Linux is not ready" or "Linux is not for me".
Specifically on Steam: Which hardware you run on can affect on which distro it runs out of the box on and if you need to fiddle with drivers and firmware or not to get things running smoothly. There is also some difference between installation methods (some people swear by the flatpak version and others swear off it).
Maybe also check the health of your SSD and that your firmware/BIOS are up to date.
I run the overleaf (formerly sharelatex) container stack locally and edit in a browser for the rare occasion. Had to patch up the containers a bit but it still seems like less trouble than setting up a proper latex cli env with all the plugins and stuff.
zsh envy is dead
If anyone else is seeing high resource use from seeding: There's quite some spam and griefing happening to at least Debian and Arch trackers and DHT.
Blocking malicious peers can cut down that by a lot. PeerBanHelper is like a spam filter for torrent clients.
https://github.com/PBH-BTN/PeerBanHelper/blob/dev/README.EN.md
What you can do is segregate networks.
If the browser runs in, say, a VM with only access to the intranet and no internet access at all, this risk is greatly reduced.