Of all the replies, this is the first one to actually make a good point instead of random google-bad handwaving.

Thank you

No need to be sorry. English is not my first language. I appreciate the correction.

THIS IS A PAID SERVICE.

Dude, they don’t only do ads. Google has a whole bunch of payed-for services that are never touched for ad-tracking. This is one of them. You are implying that Google Cloud would also use ad-tracking based on customer data, which is absurd.

Please stop spreading this FUD. Just because the free services are payed for by ads does not mean that everything they do is.

(edit: Paid, not Payed)

So your argument has nothing to do with the product itself and everything to do with “hurr Durr Google bad”.

Which is fine, and a valid opinion, but has nothing to do with the product.

I’m annoyed because 90% of the comments here imply or outright state that google will use this data for ads or other means, which has no basis in reality.

I’m super confused by the FUD spread in nearly every comment here.

Pretty much every argument boils down to “we don’t trust google does what they say”, which is funny because I’d like to challenge anyone to provide evidence that google actually sells any of your data. They sell advertising slots that they promise will find the right people, but your data never leaves google. No advertiser gets to see it.

This VPN service promises and has been independently audited to never log or analyze your traffic and even has built in provisions to anonymize your traffic within Google so they can’t reconstruct it.

So apart from the questionable assumption that google is blatantly lying, what’s the argument here? Apart from maybe missing some popular VPN Features like country selection.

Also this is for people that already pay for Google storage anyways, so I don’t see the problem for the intended target audience, it’s sticky an improvement in privacy for them and they get it for free. It sure as hell beats getting your traffic intercepted and ads injected into random http pages like some ISPs do.

Pretty much every alerting system I know also has a filter option to only apply automated discovery rules to certain filesystem types.

But yes, most don’t first squashfs or mounted read-only snapshots by default and it sucks.

How old are you?

Are you using zfs?

That’s why you do regular restore tests on separate systems. That should be standard procedure for any company. A fully encrypted disk should be noticable immediately.

If your backups are online and not in a warehouse, you are doing it wrong. Even my own personal backups are on disconnected disks. What a bunch of amateurs.

You can’t trust any full disk encryption without it because only a TPM can verify that your bootloader and initrd are not compromised.

I get what you mean but please read the study: https://link.springer.com/article/10.1007/s41347-023-00304-7

They themselves note that the very small sample size would be an issue. They say they would need 78 people for even remotely confident results, then they initially targeted 74 people, of which 20 dropped out.

Let me be clear that I too want to believe that social networks are bad for people, but studies like this one do very very little to provide any meaningful data to base my opinion on.

Sample size, 50 students. Lol nothing to see here. This has no value whatsoever.

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?

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.

Because I get a non-toxic personalized YouTube feed that does not suck…

From arch wiki:

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.

No thanks

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.

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.