Network-based RCS

When I was at Oracle, we hade a modified version of RCS which we called NETRCS. It basically worked the same as RCS, except we could set an environment variable to point to the hostname and path of the repository:

(NETRCS=hostname:/dir1/dir2/dir3 ; export NETRCS)

Obviously, we had had serveral NETRCS servers, each having sources for different projects.

Does anyone know where I might find something similar? Someone pointed me to CVS - unfortunately that didn't do what I needed.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

What is it that CVS didn't do for you?  CVS is built on top of
RCS, and it adds networking and a very nice multi-user model, and is wildly configurable to to oodles of stuff.  I am concerned that if CVS is not good enough, nothing will be. RCS, is, after all, a pretty crude, clunky tool ...

If you got the bucks, I recommend IBM's CMVC, although it will
probably cost you more than your computer did.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
drwagner061097Author Commented:
I've been told by 2 people that CVS is the package I need. I've downloaded v1.3, and in neither of the man pages (cvs.1 and cvs.5) could I find the terms "remote host", "network", or any indication that I can use the "hostname:/pathname1/pathname2" convention when specifying directories. Am I missing something? Can someone give me an example to the following scenario?:

hostA has an RCS (or CVS) repository.
hostB also has an RCS (or CVS) repository.
I'm working on hostC and want to checkout a file(s) on hostA.
Now I want to checkout a file(s) on hostB.

If you like, make it simpler and omit hostB from the above scenario - I just want to checkout a file from a remote host without using NFS. I'm told CVS is the answer - perhaps I still have an old version, but v1.3 was the latest I could find.


- David Wagner

The current official version is 1.9 so 1.3 is very very old.
Of course, I should have provided urls:

CVS does define it's own wire client-server protocol,
which is what you are looking for.  You have to dig around
a bit in the documentation to figure out how to set this up;
I vaguely remeber doing setenv CVSROOT and also having a file
called .cvspasswd which contains a pasword . I use the "pserver"
style of authentication. Everything is so automatic I gforgot how its done

I extract some random paragraphs out of random sections of
the documentation:
Notes on the Current Implementation

   The client is built in to the normal `cvs' program, triggered by a
`CVSROOT' variable containing a colon, for example

   The client stores what is stored in checked-out directories
(including `CVS').  The way these are stored is totally compatible with
standard CVS.  The server requires no storage other than the repository,
which also is totally compatible with standard CVS.

   The server is started by `cvs server'.  There is no particularly
compelling reason for this rather than making it a separate program
which shares a lot of sources with cvs.

   The server can also be started by `cvs kserver', in which case it
does an initial Kerberos authentication on stdin.  If the authentication
succeeds, it subsequently runs identically to `cvs server'.
   The current server implementation can use up huge amounts of memory
when transmitting a lot of data over a slow link (i.e. the network is
slower than the server can generate the data).  There is some
experimental code (see `SERVER_FLOWCONTROL' in options.h) which should
help significantly.

How to Connect to and Authenticate Oneself to the CVS server

   Connection and authentication occurs before the CVS protocol itself
is started.  There are several ways to connect.

     If the client has a way to execute commands on the server, and
     provide input to the commands and output from them, then it can
     connect that way.  This could be the usual rsh (port 514)
     protocol, Kerberos rsh, SSH, or any similar mechanism.  The client
     may allow the user to specify the name of the server program; the
     default is `cvs'.  It is invoked with one argument, `server'.
     Once it invokes the server, the client proceeds to start the cvs

     The kerberized server listens on a port (in the current
     implementation, by having inetd call "cvs kserver") which defaults
     to 1999.  The client connects, sends the usual kerberos

     authentication information, and then starts the cvs protocol.
     Note: port 1999 is officially registered for another use, and in
     any event one cannot register more than one port for CVS, so the
     kerberized client and server should be changed to use port 2401
     (see below), and send a different string in place of `BEGIN AUTH
     REQUEST' to identify the authentication method in use.  However,
     noone has yet gotten around to implementing this.

     The password authenticated server listens on a port (in the current
     implementation, by having inetd call "cvs pserver") which defaults
     to 2401 (this port is officially registered).  The client
     connects, sends the string `BEGIN AUTH REQUEST', a linefeed, the
     cvs root, a linefeed, the username, a linefeed, the password
     trivially encoded (see scramble.c in the cvs sources), a linefeed,
     the string `END AUTH REQUEST', and a linefeed.  The server
     responds with `I LOVE YOU' and a linefeed if the authentication is
     successful or `I HATE YOU' and a linefeed if the authentication
     fails.  After receiving `I LOVE YOU', the client proceeds with the
     cvs protocol.  If the client wishes to merely authenticate without
     starting the cvs protocol, the procedure is the same, except     `BEGIN AUTH REQUEST' is replaced with `BEGIN VERIFICATION
     REQUEST', and upon receipt of `I LOVE YOU' the connection is
     closed rather than continuing.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Programming

From novice to tech pro — start learning today.