Here comes the AI slop into core system utilities. Further reason why I want bullshit parrots nowhere near any critical software.
tridge and claude committed 2 weeks ago
find /usr/ports -name clone pkg search -o cloneI only used rsync a few times thinking it'd be useful for NAS restores; plain cp is still fine![]()
Regression in 3.4.3, "Invalid argument (22)" on all file reads when using native protocol · Issue #897 · RsyncProject/rsync
In rsync 3.4.3, when doing a simple remote directory read using native protocol, we see the following regression: rsync -av --delete imap::top/mnt/ /tmp/foo/ receiving incremental file list rsync: ...github.com
Back in the day when tcp/ip was uncommon, I used to carry around a program called "cpt" (copy-tree) for my contracting jobs as cp wasn't quite flexible enough. It also behaved differently based on the name it was called with; e.g. copy, move, link, symlink, flatten (tar), make-tree (untar). But I stopped using it a long time ago as rsync was more than good enough.plain cp is still fine
$ cpt -h
Usage: cpt [-abcCdDehiI:lLnNoO:prsStTuvVx] file1 file2
or cpt [-abcCdDehiI:lLnNoO:prsStTuvVx] file1 ... directory
where
-a ask on all files
-b backup - only if st_ctime of source > dest
-c complain about unresolved links
-C copy if link not possible
-d ask only on directories and special files
-D <n> print debugging info of level <n>
-e operate only if destination exists
-i interactive - ask if would overwrite
-I <f> take source file names from input file <f>
-l link if possible
-L sym Link if possible
-n only if file doesn't already exist
-N No copy or link or mkdir, just do -t and -o
-o owner - preserve uid and gid
-O <f> put source files names operated on in file <f>
-p full path name to destination
-r recursive
-s do special files specially
-S copy/link/symLink only if src & dst files are the same
-T retain original source access time
-u unlink dest file before copying
-v,V verbose, partial (v) or full(V)
-x Do not cross a mount point