Rsync replaced with openrsync on macOS Sequoia

Original Article ↗ Hacker News Discussion ↗

Replacement and immediate reactions

  • macOS Sequoia replaces the ancient, GPLv2 rsync 2.6.9 with the BSD‑licensed openrsync from the OpenBSD world.
  • Many power users say they immediately install “real” rsync (via Homebrew/MacPorts/Nix) anyway, as they already did for bash, coreutils, grep, etc.
  • Some welcome the change, arguing the bundled rsync was “old and crappy” and Apple’s userland has been rotting due to GPL avoidance.

Compatibility, regressions, and correctness concerns

  • openrsync intentionally supports only a subset of rsync’s options and older protocol versions; several commenters report real breakage:
    • Options like --xattrs, --acls, --hard-links, --log-file and some --rsh behaviors are missing or different.
    • Extended attributes now require --extended-attributes instead of -E, breaking scripts (e.g., rsync -Eva no longer works).
    • One user observed duplicate “deleting” lines and unexpected ._ files when copying directories with xattrs; they deem it “not an acceptable replacement”.
  • People relying on rsync for “perfect” copies (data + all metadata: xattrs, ACLs, resource forks, high‑precision timestamps) are especially wary; openrsync’s docs don’t clearly guarantee that level of fidelity.

Rsync as protocol and multiple implementations

  • Some commenters are enthusiastic that rsync now has multiple independent implementations, pushing it toward a true protocol (like SSH/HTTP).
  • openrsync’s origin is tied to RPKI work where a non‑GPL implementation was needed; other implementations (Go, .NET, librsync, rsync‑over‑gRPC) are mentioned.
  • Others argue a single strong reference implementation can avoid fragmentation, but rsync is now mature enough to benefit from diversity.

Apple’s GPLv3 avoidance and corporate licensing culture

  • Large part of the thread debates why Apple avoids GPLv3:
    • Fears around “TiVoization” clauses (ability to install modified code on locked‑down devices) and around GPLv3 patent retaliation.
    • Legal departments at many big companies reportedly mandate “no GPLv3” and restrict GPLv2, citing ambiguity, lack of case law, and risk of becoming a test case.
    • Some see this as Apple preserving freedom to further lock down macOS (e.g., signed system volume) without ever having to unwind GPLv3 code.
  • Others counter that GPLv3 clarified user freedoms and that industry’s shift toward permissive licenses has weakened copyleft’s power.

Broader ecosystem themes

  • Several comments lament diverging tool behaviors (BSD vs GNU, old vs new versions) making portable shell scripting harder.
  • Consensus among heavy users: treat macOS’s bundled tools as minimal, install your own toolchain, and don’t assume Apple’s rsync/openrsync is a drop‑in replacement.