Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <199907091702.MAA32469@mercury.xraylith.wisc.edu>
To: elliot AT lexra DOT com
cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: rlogin, rsh, and cvs server 
In-Reply-To: Your message of "Fri, 09 Jul 1999 08:03:21 EDT."
             <000301beca03$0a271a40$0e08a8c0 AT lexra DOT com> 
Date: Fri, 09 Jul 1999 12:02:29 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

"Elliot Mednick" <elliot AT lexra DOT com> writes:
> 
> And, can someone recommend the best way to use cvs as a client from Cygwin?
> Is the rsh method best?  Or should I attempt to use the inetd method?

Use pserver. Builds out of the box, and works reliably, albeit slowly. 
All source code on my NT box is maintained in a remote repository on a 
Unix server. I believe I'm using 1.10.5 on the Cygwin side and 1.10.2 
on all the rest of the machines. 

I strongly suggest keeping all the source directory mounts binary if 
you're doing a lot of development to avoid awkward problems with diffs 
having CR/NL etc.

> 
> (No firewall involved.  I can use cvs now by mounting the repository via a
> Samba server, and I can checkout, but I cannot commit because other users
> change ownership of the repository files and Samba apparently will not allow
> my Cygwin cvs to delete those files.  Therefore the client/server approach.)
> 

Another side benefit of client/server is that you can freely move around
the directory tree without having to muck with CVS/Repository etc files.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com