Remember when you first starting learning how to use #rsync and forgetting to include or leave off the trailing forward slash (/) would make a tremendous mess of things?

#Bash #Computers #Linux #Shell #UnixLike

I made a full circle on large data #backup options and am now back to #rsync. The difference is that I’m now much more confident in running headless data sync by cron.

Data origin -> DAS -> #Hetzner Storage Box

It looks like 3-2-1, and I’m now all set to migrate my family from #iCloud to #Immich and #OpenCloud.

Also, the DAS is #exFAT, which allows my siblings to just detach it from my #homelab to have data exported in case of my sudden disappearance by any reason.

"rsync goes AI slop, breaks your backups" from @davidgerard

🔗 https://pivot-to-ai.com/2026/06/03/rsync-goes-ai-slop-breaks-your-backups/

#AI #rsync

The are deploying a new application version at $WORK. Of course, this is OpenShift and pipelines and Agile and YAML and YeePeeHaYeah.

It’s been loads of minutes (like 15+) and deployment is still "in progress". For something like 5 Java containers.

I think it never took more than 10 minutes to deploy #OpenBSD and its packages and configs and data using #rdist and #rsync.

Honestly… what have they done to IT 🙄🙄🙄🙄🙄

I think "free as in beer" software is more appropriately called "Libertarian and Open Source Software", or LOSS. Among other things it involves no obligations on other people, and expects no obligations in return (*). But this means it's an everyone for themselves, anti-communitarian endeavor. We should be honest about this. We should also be honest when a project changes state from FOSS to LOSS, because that's a meaningful change, and actually is a loss in my view.

I continue to believe that enthusiastic embrace of AI/LLM coding tools is a leading indicator of an impending FOSS→LOSS transition.

It seems to me at least one driver of the uproar over rsync is that a bunch of people thought it was a FOSS project but it had, in a short period of time, converted into a LOSS project and the shock was jolting (understandably). As a FOSS project, rsync served a community function, leading people to depend on it, make assumptions about its longer-term stability, and so on. Those are reasonable expectations of a communitarian project. As a LOSS project, rsync is under no obligations to anyone and the maintainer(s) can change the software at any time, for any reason, at their discretion alone. It seems rsync is a LOSS.

#tech #dev #software #SoftwareDevelopment #FOSS #freedom #rsync #AI #GenAI #GenerativeAI #LLMs

RE: https://fedi.lwn.net/@lwn/116686303139385065

A while back, rsync's maintainer had not quite gone silent, but there were long stretches of quiet, and there was some concern about the maintenance of the project. A few things happened, and it resulted in Tridge coming back to maintain the project.

As with many FOSS projects, there's a ratio of about 100,000,000 users to one maintainer. I saw reports about a regression and "a bunch of slop commits" to rsync and was a bit alarmed, but I also thought "that... does not sound very Tridge-like".

If you actually *look* at the commits, which a lot of the slop accusers have not, the bulk of them are tests and not actually commits to rsync itself. There are some LLM-written or co-written commits with (I think) Claude, but I think if you actually did the work to comb through them all (which I did not) you'd find the ratio is like 9:1 in favor of tests.

Anyway, I was pondering whether we should write an article on the situation after Tridge had made some comments in the rsync Discord* but his response here seems more than adequate for the moment.

The harassment that Tridge was getting is not OK. It's fine to decide "this project is no longer for me." Folks who are 100% opposed to LLM-driven work in all its forms will probably still want to find an alternative. That's fine. I respect that. If you're an "LLM vegan" then right now the world looks pretty damn bleak, because it's winding up in everything. But piling on maintainers who are doing this stuff for free... that's just a community killer.

If you're not contributing, you have very little standing to complain.

* I'm actually a bit more disappointed in the decision to use Discord than anything. But Tridge is stepping up to do the work though he's retired, so I will largely keep that to myself and say "thank you for the work" instead. #rsync #llms #opensource

UGREEN NAS: ZUGRIFFSPROTOKOLLE VERSTEHEN: SMB, NFS, WEBDAV ETC. – TUTORIAL

https://gadgetchecks.de/ugreen-nas-zugriffsprotokolle-verstehen-smb-nfs-webdav-etc-tutorial/

.
.
.

#ugreennas #nas #ugospro #smb #nfs #webdav #ftp #sftp #ftps #rsync #dlna #netzwerk #homeserver #linux #windows #tutorial #netzwerkspeicher #selfhosting #mediaserver #datensicherung

ICYMI: some dork used #Claude #LLM to 'fix' an issue in #rsync and broke it (v3.4.3).

#GenAI is shit and shld not be used for code that needs to work, even if you have the morals of a billionaire skunk.

Lots of critical tasks, such as backup 🤦‍♂️ will be broken as people update their #Debian #Linux thanks to this stupid obsession and psychosis.

How much will that cost? On top of all the costs inflicted on people who never touch the stuff and don't want to run anything built with it, like me.

So here's one of the cool things you can do with Gentoo. You're not forced to stick to the latest version of a package, multiple stable versions might be available simultaneously. So in this case you can mask rsync-3.4.3 to avoid the slop-induced bugs and the package manager will automatically fall back to rsync-3.4.1-r2. See that '-r2' suffix? That's important, it means that it's the base 3.4.1 version plus a set of patches added by the Gentoo maintainers. In this particular case those patches address CVE-2025-10158, so you get the important security fix but avoid the slop issues introduced in the next stable release. Naturally, while the technical brilliance of this system is remarkable, what really shines it the will of Gentoo maintainers to go above and beyond to solve users' issues. Thanks (and donations) should go to them.

https://mastodon.gamedev.place/@JeremiahFieldhaven/116654345332213390

#Gentoo #rsync

It's very sad to see #rsync getting polluted with LLM slop now.

Even more sad, given who is doing it.

People are talking angrily about "the maintainer" and suggesting "this guy" [should have his commit bit revoked] etc. apparently not realising that "this guy" is Tridge, both the original author of rsync and creator of samba. His PhD thesis "Efficient Sorting & Synchronization Algorithms" describes the original rsync algorithm. Still worth a read, even now.

https://en.wikipedia.org/wiki/Andrew_Tridgell

The author went the extra mile and had some kind words to write about OpenBSD's OpenRsync as well:

https://michael.stapelberg.ch/posts/2026-05-24-minimal-memory-safe-go-rsync-vulns/#openrsync

Ironically, I saw this not long after closing a Pull Request to submit an OpenRync port to MacPorts: https://github.com/macports/macports-ports/pull/28096

Not that I don't still have an interest in such things, but it seems as if there are some other things going on (if I observed things correctly, it seems as if Apple maybe commissioned Klara Systems to port OpenRsync to macOS (e.g. https://github.com/KlaraSystems/openrsync)? Yet, it didn't seem as if they did so in a very collaborative spirit with the lead developer Kristaps Dzonsons?). Moreover, I didn't want to just leave that dangling when other MacPorts contributors were side-eyeing the PR as being left open for so long.

#OpenRsync #rsync #vulnerabilities #OpenSource #Security #Infosec #SecurityResearch #OpenBSD

Huh, looks like there is a #openrsync package in the #FreeBSD packages — slop-free #rsync implementation, using in the #OpenBSD.

I'm using rsync to make backups of my valuable files to the USB drive (so this program should work without problems and should be written by people who see programming as an art and could be accountable for their code), and also for copying files in Dired.

Using openrsync for #Emacs Dired is pretty simple — just point the dired-rsync package to the right binary, like:

(setopt dired-rsync-command "/usr/local/bin/openrsync")

Alt...

Screenshot of Dired configuration in the Emacs. The main line: dired-rsync-command "/usr/local/bin/openrsync".