I've got a similar setup, but use Kopia for backup which does all that you describe but also handles deduplication of data very well.
For example I've added older less structured backups to my "good" backup now and since there is a lot of duplication between a 4 year old backup and a 5 year old backup it barely increased the storage space usage.
There's lots of very good approaches in the comments.
But I'd like to play the devil's advocate: how many of you have actually recovered from a disaster that way? Ideally as a test, of course.
A backup system that has never done a restore operations must be assumed to be broken. similar logic should be applied to disaster recovery.
And no: I use Ansible/Docker combined approach that I'm reasonably sure could quite easily recover most stuff, but I've not yet fully rebuilt from just that yet.
Note that the Pi5 finally exposes PCIe, which introduces the potential for much better IO. technically the CM4 already did that, but that moves the price outside normal Pi prices with the necessary carrier boards to make use of it).
But I agree that for most tasks there are better, more competitively prices SBCs out there. The major reason to pick the Pi is popularity and wide usage/support (which is especially useful for new users IMO).
I was answering under the assumption/the context of of "Amazon wants to release an Android-based OS that doesn't contact any of Googles services".
So, when I said "easy enough to remove" that was relative to releasing any commercial OS based on AOSP, as in: this will be one of the smallest tasks involved in this whole venture.
They will need an (at least semi-automated) way to keep up with changes from upstream and still apply their own code-changes on top of that anyway and once that is set up, a small set of 10-ish 3-line patches is not a lot of effort. For an individual getting started and trying to keep that all up to do date individually it's a bit more of an effort, granted.
The list you linked is very interesting, but I suspect that much of that isn't in AOSP, my suspicion is that at most the things up to and excluding the Updater even exist in AOSP.
A cop out or a coping mechanism. Employers steal so much from employees: time, wages, sense of purpose, sometimes even health. And most of us don't have good ways to stop them (because socienty). So stealing a bit back might actually help feeling less hopeless.
Yes, but those minor traces are easy enough to remove, especially if you don't care about being "ceritified" by Google (i.e. are not planning to run the Google services).
That only helps when there's viable alternatives. Since pretty much all auto manufacturers do something like this it's not really a distinguishing feature.
And even if it was: how much worse/more expensive would a car need to be for you to not pick it over one that reads your text messages. And then ask the same question not for "you", but for the average consumer. Then be sad ...
One more confusion: If DNSSEC is enabled it actually switches to TCP, since DNSSEC requires messages that are much bigger than what UDP can transfer.
Good. 10 Billion $ of inheritance tax seems reasonable. Could be higher (we don't need billionaires), but it's a good start.
I just checked it out. That licensing documentation is a mess. They say that it's released under the AGPL, but not all of it? So what they are saying is that the whole product is not actually under the AGPL. I wonder if their "freeware" part can actually be removed without major loss of functionality. Because if that's possible, then you could simply rebundle that one.
But I suspect it exists exactly to "taint" the open source nature of the product.
Note that they said "not intended" and not "not allowed". you are perfectly within your right to use the program under the GPL without licensing it otherwise.
But the company would prefer if you paid for a license (and support). If you weren't allowed the use you do, they would have said as much, but they didn't.
This is a common business practice with open source software and I don't particularly think it s "wrong", but the fact that they are apparently trying to use confusion to make it look like you have to buy a license for commercial use is very icky in my opinion (but is unfortunately also very common).
yeah, there's a bunch of lessons that tend to only be learned the hard way, despite most guides mentioning them.
similarly to how RAID should not be treated as a backup.