Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE 08-05-2008 Deployment Manual page 736

There is no conflict handling in rsync. The user is responsible for not accidentally
overwriting files and manually resolving all possible conflicts. To be on safe side, a
versioning system like RCS can be additionally employed.
38.2.5 Selecting and Adding Files
In CVS, new directories and files must be added explicitly using the command cvs add.
This results in greater user control over the files to synchronize. On the other hand, new
files are often overlooked, especially when the question marks in the output of
cvs update are ignored due to the large number of files.
38.2.6 History
An additional feature of CVS is that old file versions can be reconstructed. A brief
editing remark can be inserted for each change and the development of the files can
easily be traced later based on the content and the remarks. This is a valuable aid for
theses and program texts.
38.2.7 Data Volume and Hard Disk
Requirements
A sufficient amount of free space for all distributed data is required on the hard disks
of all involved hosts. CVS require additional space for the repository database on the
server. The file history is also stored on the server, requiring even more space. When
files in text format are changed, only the modified lines need to be saved. Binary files
require additional space amounting to the size of the file every time the file is changed.
38.2.8 GUI
Experienced users normally run CVS from the command line. However, graphical user
interfaces are available for Linux, such as cervisia, and for other operating systems,
like wincvs. Many development tools, such as kdevelop, and text editors, such as Emacs,
provide support for CVS. The resolution of conflicts is often much easier to perform
with these front-ends.
720 Deployment Guide