|
|||||||||||
|
Re: FileSystem Question
From: William Pursell <bill.pursell(at)gmail.com>
Date: Sat Jun 30 2007 - 18:05:41 EDT
>> On 6/29/07, Douglas Allan Tutty > > Hi Manon, > > See the apt descriptions for subversion and cvs. From the description > of cvs: > CVS is a version control system, which allows you to keep old > versions of files (usually source code), keep a log of who, > when, and why changes occurred, etc. > > As I understand it, a user will 'check out' a file from the cvs to work > on it. While it is 'checked out', others can read that version of the > file but they can't 'check it out' to edit it. The person who has it > checked out can then check the file back in with whatever changes they > made. The cvs then keeps diffs and checkpoints so that the state of the > repository at any point in time can be recreated. I.e. the question > "what did that file look like on June 15?" is a valid question that the > cvs can answer. > > The whole cvs sits on top of a regular file system. There's nothing > preventing root from directly editing a file owned by cvs. > > I think that there are web-based interfaces to the cvs so that files can > be retreived over https as well. > > This is all I know about cvs and it may not be accurate. Keep in mind that CVS is extremely old, and entirely obsolete. Subversion was a new implementation of the same idea, and did in fact address many of CVS's shortcomings. However, if you are going to look into using a VCS (Version Control System) for doing backups like this, look into git. http://git.or.cz -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Sat Jun 30 17:57:16 2007 This archive was generated by hypermail 2.1.8 : Sat Jun 30 2007 - 18:00:04 EDT |
||||||||||
|
|||||||||||