X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/3bd9f51917ed5718275c6132006be155239a0550..73b9b90a0b548d1177d2bf004c800ae6d9926a1f:/rsync.yo

diff --git a/rsync.yo b/rsync.yo
index 5c11d956..838d9688 100644
--- a/rsync.yo
+++ b/rsync.yo
@@ -943,7 +943,8 @@ destination exactly matches that on the source.  Cases in which the
 destination may end up with extra hard links include the following:
 
 quote(itemization(
-  it() If the destination contains extraneous hard-linked files, rsync will not
+  it() If the destination contains extraneous hard-links (more linking than
+  what is present in the source file list), the copying algorithm will not
   break them explicitly.  However, if one or more of the paths have content
   differences, the normal file-update process will break those extra links
   (unless you are using the bf(--inplace) option).
@@ -1177,10 +1178,6 @@ dit(bf(-S, --sparse)) Try to handle sparse files efficiently so they take
 up less space on the destination.  Conflicts with bf(--inplace) because it's
 not possible to overwrite data in a sparse fashion.
 
-NOTE: Don't use this option when the destination is a Solaris "tmpfs"
-filesystem. It seems to have problems seeking over null regions,
-and ends up corrupting the files.
-
 dit(bf(-n, --dry-run)) This makes rsync perform a trial run that doesn't
 make any changes (and produces mostly the same output as a real run).  It
 is most commonly used in combination with the bf(-v, --verbose) and/or