Backups only used blocks. Backup to or from various locations, NFS shares, ftp, WebDAV, ssh server, samba, etc. Encryption of the images, backup of single partitions or whole disks.
If you want to deploy to several machines at once it also has a load of tools for that too.
You 100% want to use Clonezilla for this job. It should be on everyone’s Ventoy stick.
No. The less code for a given set of functionality the better… often. Removing functionality just to reduce code is daft. Otherwise stop adding any features. Remove all features of the kernel until machines only just boot. Lot less code!
But that’s true of all code in the kernel. If any change can break something then all broken bits will need fixing. Why not remove all drivers in case an update breaks them. Things can’t be preemptively fixed before breaking changes are made. A driver can be complete and only need updating if someone else breaks stuff, so leave it alone until then and only remove it I’d no one comes to fix it.
Removing functionality just in case is daft.
Why clear them out if they still work and are useful? Seems like a backwards step. What’s that phrase that people throw about:sometimes things are just done and don’t need changing.
I’ve never heard anyone say ZFS broke, corrupted their data or failed in any way at all. With btrfs it’s a consistent complaint. And btrfs literally has modes of operation that are known to be broken. I could understand if it was a new file system, but it can almost drink in pubs.
So, what you’re saying is, “it works on my machine”
You’re right to give up on btrfs. It’s been so long in development and it just isn’t ready. Ext4 or ZFS are mature and excellent file systems. There’s no need for btrfs these days. It always has and always will disappoint.
Everyone singing the praises of it are the sysadmin equivalent of the software engineer yelling ‘it works on my machine’ when a user finds an issue.
That was my point
20 years ago there were 2000000000 fewer people in the world.
I haven’t paid anything for it
As long as there are no problems with the btrfs code? Hahahahaha!! There are.
It was forked but somehow lacked a huge amount of functionality that Emby had (and still has) Like I think it only supported films, not music or TV shows. The app infrastructure was awful across fire stick, Roku and android and wasn’t backward compatible with the Emby apps. I just didn’t see the point of forking it if you’re just going to make it worse or only address the server side and neglect the clients. The whole thing has to work together with good clients and server.
Last time I tried it it was a much worse experience than Emby across all devices and for all media types. I don’t understand all the love it gets.
Everyone saying it’ll be fine is speaking theoretically. Practically I can attest to full and total file system corruption under this scenario.
Careful. You might get hit by a bus.
I gave up trying to setup a Mastodon server in docker. Lemmy was pretty tricky at the time as the docs were wrong. My email server was a bit tricky, but I’ve not really done much to tinker with it in the proceeding 6 years, so was worth it.
Probably helps add a certain gravitas.
Been running Ubuntu LTS releases on all my server VMs for 8 years and haven’t had a single problem. Absolutely solid as a rock. Fantastic support, loads of guides to do anything. Plus you can get 10years of support as a home user with a free Ubuntu Pro subscription.
Others have stated how they’re different already. To an end user the difference is that EndeavourOS is incredibly good, whereas Manjaro is a bit pants.