For a handful of servers, try zabbix.
Every distribution has a packaged zabbix agent.
It has everything: web ui, a way to Auto discover things with a bit of setup, nice graphs, alerting, LDAP User Management if you need it, a way to define per person/group alerting/notification schedules.
And the community is big enough that many common services (fail2ban/postfix/MySQL/etc.) have premade custom monitoring scripts.
Adding your own metrics is also very easy.
That's in no way a rich people thing. Polluting less often means that stuff people are used to will cost more or will be less available.
The greens in Germany suggested that maybe meat is too cheap and people should eat it less and maybe also don't drive your car so much. And a good chunk of the population lost their fucking mind at the audacity to suggest doing something in two sectors that massively contribute to climate change.
The reality is that effective action against climate change is hugely unpopular and politicians realize that it's often political suicide because people hate change and there is no way to combat climate change without lifestyle changes for every single citizen.
I don't know where you take that from but the super rich are a tiny tiny fraction of the problem.
They don't buy containerships full of stuff, they don't eat millions of animals per day, they don't constitute the vast majority of travel.
Yes, on a per person basis they have an extremely large footprint, but it's still a drop in the bucket compared to the industries that feed the consumption of the average citizens.
I don't quite agree because children will also readily make other children or trees or stones or the sky their enemy if they feel like it.
And they will go out of their way to recruit other people to fight against said perceived enemies.
13€/month to never see ads on any device, give a lot more money to creators and free access to YouTube music so I don't need Spotify anymore. It's amazing how much you get for comparatively little money.
Disabling CoW in Btrfs also disables checksums. Btrfs will not be able to detect corrupted nodatacow files. When combined with RAID 1, power outages or other sources of corruption can cause the data to become out of sync.
If you are planning to have any kind of database with regular random writes, stay away from btrfs. It's roughly 4-5x slower than zfs and will slowly fragment itself to death.
I'm migrating a server from btrfs to zfs right now for this very reason. I have multiple large MySQL and SQLite tables on it and they have accumulated >100k file fragments each and have become abysmally slow. There are lots of benchmarks out there that show that zfs does not have this issue and even when both filesystems are clean, database performance is significantly higher on zfs.
If you don't want a COW filesystem, then XFS on LVM raid for databases or ext4 on LVM for everything else is probably fine.
Crude oil is 85% carbon.
Dry wood is about 50% carbon.
Average oil production worldwide in the last 20 years is about 73million barrels per day or 26.6 billion barrels per year.
So just in oil, we produced around 26.6*20 = 532 billion barrels of oil.
At a weight of 136kg/barrel, that equals 72billion tonnes of oil.
Because it's 85% carbon, that equals 61.5billion tonnes of pure carbon.
Converting this into wood would require 123 billion tonnes of wood.
At an average density of 650kg/m3 for Oak, which grows reasonably fast, that equals 189 billion cubic meters of wood.
That's a solid 1 meter thick square of wood with an edge length of 434km that we would need to STORE indefinitely to offset just the crude oil of the last 20 years.
That's 53% of the surface area of Germany in 1 meter thick wood and every year we'd additionally need to grow, harvest and store enough wood to cover 46% of Wales in 1 meter of solid dry wood.
For personal use, I don't bother with databases on k8s. They are waaay easier to manage if you just let your host distribution run it as a regular service and Upgrade it through that
Most of the time, it's enough to copy the whole EFI partition to the new machine and update whatever boot entries are in there to point to the right new partitions.
In case of a switch to something like zfs, it's a bit more involved and you need to boot a live Linux, chroot into the new "/" with /boot mounted and /dev, /proc, /sys bind mounted into the chroot.
Then you can run the distro-appropriate command to reinstall/ update grub into the EFI partition and they will usually take care of adding the right drivers.
What's the problem with that script? That's such a basic use case and not very hard to do at all in systemd.
Where do you struggle with it? Can we maybe help with something?