APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

2004/06/11 CVS

Concurrent Versions Systems. The general standard for version control. Allows multiple people to work on a project by tracking changes and controlling access. Primarily used for code, but there's no reason it can't be used for any project where multiple people make changes to a document set. See http://www.whoishostingthis.com/compare/cvs/resources/

Got something to add? Send me email.

1 comment

Increase ad revenue 50-250% with Ezoic

More Articles by

Find me on Google+

© Tony Lawrence

Sometimes people even use it for their home directories.
see here:

It allowed this guy to synchronize the home file and user configurations of the dozen or so different enviroments he has to operate in. It also allows for document revisioning to have undo abilities when editing files over the long term (like if your a writer), makes making backups easy, and adds undelete capbabilities to the operating enviroment.

The down side though, of course, is that it's not easy to set up if your not familar with CVS. Also some people say that other versioning software like Subversion is superior to these sort of tasks then CVS.

Never used it myself, though.


Kerio Samepage

Have you tried Searching this site?

Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us

Generally, old media don't die. They just have to grow old gracefully. Guess what, we still have stone masons. They haven't been the primary purveyors of the written word for a while now of course, but they still have a role because you wouldn't want a TV screen on your headstone. (Douglas Adams)

This post tagged: