[trivial patch] link overloaded

jw schultz jw at pegasys.ws
Thu Jan 30 09:17:26 EST 2003


This is just a trivial documentation change.  The word
"link" is overloaded.  It refers to symlinks, hardlinks and
network links.  When looking for references to file links in
the manpages the network references get in the way.

This patch changes when reasonable to do so the word "link"
to "connection" when referring to the network.

This is just a suggested ease-of-use adjustment born of my
own annoyance. 


-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw at pegasys.ws

		Remember Cernan and Schmitt
-------------- next part --------------
Index: rsync.yo
===================================================================
RCS file: /cvsroot/rsync/rsync.yo,v
retrieving revision 1.114
diff -u -r1.114 rsync.yo
--- rsync.yo	28 Jan 2003 03:11:57 -0000	1.114
+++ rsync.yo	29 Jan 2003 22:09:52 -0000
@@ -25,7 +25,7 @@
 exists.
 
 The rsync remote-update protocol allows rsync to transfer just the
-differences between two sets of files across the network link, using
+differences between two sets of files across the network connection, using
 an efficient checksum-search algorithm described in the technical
 report that accompanies this package.
 
@@ -251,7 +251,7 @@
 
 quote(rsync -Cavz . arvidsjaur:backup)
 
-each night over a PPP link to a duplicate directory on my machine
+each night over a PPP connection to a duplicate directory on my machine
 "arvidsjaur".
 
 To synchronize my samba source trees I use the following Makefile
@@ -266,7 +266,7 @@
       sync: get put)
 
 this allows me to sync with a CVS directory at the other end of the
-link. I then do cvs operations on the remote machine, which saves a
+connection. I then do cvs operations on the remote machine, which saves a
 lot of time as the remote cvs protocol isn't very efficient.
 
 I mirror a directory between my "old" and "new" ftp sites with the
@@ -657,7 +657,7 @@
 dit(bf(--csum-length=LENGTH)) By default the primary checksum used in
 rsync is a very strong 16 byte MD4 checksum. In most cases you will
 find that a truncated version of this checksum is quite efficient, and
-this will decrease the size of the checksum data sent over the link,
+this will decrease the size of the checksum data sent over the connection,
 making things faster. 
 
 You can choose the number of bytes in the truncated checksum using the
@@ -698,7 +698,7 @@
 
 dit(bf(-z, --compress)) With this option, rsync compresses any data from
 the files that it sends to the destination machine.  This
-option is useful on slow links.  The compression method used is the
+option is useful on slow connections.  The compression method used is the
 same method that gzip uses.
 
 Note this this option typically achieves better compression ratios
Index: rsyncd.conf.yo
===================================================================
RCS file: /cvsroot/rsync/rsyncd.conf.yo,v
retrieving revision 1.53
diff -u -r1.53 rsyncd.conf.yo
--- rsyncd.conf.yo	27 Jan 2003 03:07:18 -0000	1.53
+++ rsyncd.conf.yo	29 Jan 2003 22:09:52 -0000
@@ -389,7 +389,7 @@
 quality security then I recommend that you run rsync over ssh.
 
 Also note that the rsync server protocol does not currently provide any
-encryption of the data that is transferred over the link. Only
+encryption of the data that is transferred over the connection. Only
 authentication is provided. Use ssh as the transport if you want
 encryption.
 


More information about the rsync mailing list