We paid our first payment twice because autopay showed as off, so we did it manually. Then magically a week later autopay figured itself out and charged us anyway.
Rsync is more "copy on steroids" than "backup utility". Many people use it as a backup tool because it allows very lightweight syncs between a source and a destination. It has no concept of snapshots or restores, it's just copying files. You'd have to build a snapshot system around rsync. It's not the solution you think you're looking for, but by the time you figure out how to use it it's the solution you probably always wanted. If that makes any sense
Flash drives are notorious for spontaneous and ungraceful failures. At the very minimum, you want a proper Hard Drive or SSD. Generally, any reputable brand marketing a "NAS" drive is probably what you want. Nothing spectacularly fast, but designed for a lot of power on hours.
My strategy has always been to separate what should be persistent from what shouldn't be.
On every system I deploy for home or work, I have a tree similar to below
/storage/[local/remote]/[where it is, enclosure, backplane,etc]/[what it is]
E.g
/storage/local/e1/raid/r6a/[this is my mount point]
/storage/remote/nfs4/oldserver/[this is my mount point]
I then build all of my workflows off of the assumptions that things go there. Docker containers have a subdirectory in r6a for persistent volumes, etc
Even my containers themselves have a /storage/remote/persistent that I symlink anything to that I care about.
On the desktop side, I tend to physically just mount a second drive or a second partition as a subdirectory of /storage. That way my assumption can always be safe in that if it's a subdirectory of a mount, my data is safe. If it's not, it isn't. It's also nonstandard, so I can be relatively certain I won't have conflicts between different distributions.
The main issue I have with submounting system directories like /home is that applications tend to put junk there, and old junk might not be compatible with a newer version of, or different distro. It can make for more effort than it's worth
I'm sure you're probably not wrong in spirit, being a terrorist organization charter and all... but a good way to convince people you're taking out of your ass is to quote a source and have the text of the quote not be in the source.
The context is not that the Hamas charter is reasonable, it's that the sentiment that birthed the charter may have historical foundation. Just like Israeli animosity towards muslims as a whole has historical foundation.
The place is indeed "never". Every action should be addressed in the vacuum of its own context. Whatabousims detract from the argument at hand and prevent a Socratic exchange from narrowing its scope sufficiently enough to reach a consensus of understanding.
It's not about deflecting hypocrisy, it's about being able to have sane arguments in good faith.
I would be very interested to see the percentage of lemmy users that were reddit users right up until the point they switched primary platforms. I have to imagine that number is near 99%.
It's not like I don't use open source solutions, I use docker for example rather than automating chroots/cgroups by hand in bash. I just use them as little as possible. While you're correct, I don't lose data in a well designed open source project, I do lose work, workflow, and convenience when those projects change or shut down. What's really nice about the pure bash solutions is they're entirely portable once you have them dialed in. If I wanted to switch from docker back to vms or forward to something like harvester/rancher/k3s I'd be able to port the projects very trivially. If I built everything around one of those projects in mind, all of my work would rely on it not changing. I acknowledge it's sometimes a little more work but it's work that I get to decide when to do, not when the project maintainers decide it for me.
My entire homelab env is written in "pure bash". Bare metal deployments, creation, build, deployment, update, and backup, of docker containers (which are also just convenience wrappers around other pure bash projects of mine.). Etc...
I do it because I got sick of losing data, work, workflow or convenience to black boxes I didn't create myself. Hell, even with my third party projects like Plex I have a lot of bash automation around extracting playlists from the internal sqlite db, etc. It really shifts your perspective on what's possible when you build things by hand yourself.
Not that I'm remotely defending corporate bloat, but it is important to do the math and make sure we're fighting the right battles. 3.5B sounds like a lot, but Ford has around 175k US employees, if you divide that 3.5B over the ten years over the 175k employees, that's only an extra $2000/employee/yr. $2000/yr is not going to help a factory worker's future medical debt nor allow someone to afford a house or a family that couldn't $2k ago. One could probably even with a straight face make the argument that 3.5b in stock buybacks sets Ford up for future sustainability, and ensures they can keep the bulk of those workers in the US that probably could be exported for cheaper.
What we need back is the culture of taking care of corporations that take care of you when you retire. Pensions and stock options for regular employees.
We paid our first payment twice because autopay showed as off, so we did it manually. Then magically a week later autopay figured itself out and charged us anyway.