nu.kanga.list.mud-dev

4735: Re: [MUD-Dev] Version Control (was: DBs and Events)

On 20/02/98 at 01:47 PM, Vadim Tkachenko <vadimt@4cs.com> said:
>coder@ibm.net wrote:
>> 
>> On 16/02/98 at 03:37 PM, Vadim Tkachenko <vadimt@4cs.com> said:
>> >coder@ibm.net wrote:
>> 
>> >[skipped]
>> >> I am becoming a fast fan of journalling versioning file systems.  These
>> >> problems just disappear.
>> 
>> >Can you please elaborate on that?
>> 
>> Journalling filesystems (loosely speaking) run the filesystem as a
>> journalling database.

>OK, I see - I just jumped at the wrong sentence being under influence of
>my RCS investigations :-))

Have a look at the following:

  http://www.wv.com/
  ftp://ftp.pn.com/pub/bb/wvfs/wvfs-2.2.14430954-alpha.tar.gz
  http://www.objs.com/survey/OFSExt.htm

>> RCS, CVS, SCCS and company are version control systems.  They have nothing
>> to do with filesystems per se -- they operate at the file or directory
>> level.  I use RCS -- I haven't looked into CVS (tho I suppose I should).
>> Comparitively RCS is a superset of SCCS, and is quite simple.

>CVS announces itself as a wrapper for RCS, as it goes from the docs I
>managed to read so far, you can keep the repository as a single entity
>instead of multiple RCS files.

See PRCS: http://www.XCF.Berkeley.EDU/~jmacd/prcs.html.  It doesn't do
distribution (yet), but has much other promise.

>> Note a versioning filesystem would essentially do RCS int he background
>> without your ever having to touch it.  cf ClearCase.

>By the way, what does 'cf' stand for?

cf, from the latin 'confer', or compare.

--
J C Lawrence                               Internet: claw@null.net
----------(*)                              Internet: coder@ibm.net
...Honourary Member of Clan McFud -- Teamer's Avenging Monolith...