public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "ASH, JAMES (SBCSI)" <ja7295@sbc.com>
To: cygwin@cygwin.com
Subject: RE: Cygwin's CVS - can it be a network server?
Date: Sat, 18 Aug 2001 11:47:00 -0000	[thread overview]
Message-ID: <8BFEC206D292D311921500508B0BCB8D08791E06@msgstl01.sbc.com> (raw)

I followed all the directions in the /usr/doc/Cygwin/inetutils-1.3.2.README.
I've gotten the inetd running. I can telnet to my box now, so I'm pretty
sure that the inetd is configured correctly. This is cygwin-nt4 1.3.2.

The cvs documentation from Fogel ( http://cvsbook.red-bean.com/cvsbook.html )
explains how to set up pserver by making an entry in the /etc/services file.
Through many hours of experimentation, it seems that cygwin doesn't require,
or use, the /etc/services file. (Is this statement correct?)

My question is, how do I install a cvs pserver to listen on port 2401? Does
the inetd need to be hard-coded in order to do this?

Thanks.
P.S. BTW, how does one pronounce Cygwin? Is it Cy- as in cyborg?

-----Original Message-----
From: Charles Wilson [ mailto:cwilson@ece.gatech.edu ]
Sent: Tuesday, August 14, 2001 11:24 AM
To: T.Phan
Cc: cygwin@cygwin.com
Subject: Re: Cygwin's CVS - can it be a network server?


T.Phan wrote:

> Hi,
> 
>   Where is the pserver or what is the setup procedure using pserver and
cvs?
>   Thanks!


AFAIK, you are breaking new ground: very few people have tried this (no 
one?) on cygwin.  You'll have to figure out how to do it on your own.  I 
suggest looking at non-cygwin sources of documentation, like the stuff 
at this website:

http://www.loria.fr/~molli/cvs-index.html

You'll probably need to get inetd started first; read 
/usr/doc/Cygwin/inetd.README.

--Chuck





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2001-08-18 11:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-18 11:47 ASH, JAMES (SBCSI) [this message]
2001-08-18 13:08 ` Corinna Vinschen
2001-08-21  2:19   ` David Starks-Browning
2001-08-21  9:42     ` Warren Young
2001-08-21 10:16       ` Christopher Faylor
2001-08-21 12:48         ` Warren Young
2001-08-21 14:52           ` Robert Collins
2001-08-18 18:17 ` How to find what version of cygwin one is running? nasser abbasi
2001-08-18 18:18   ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2001-08-21 16:50 Cygwin's CVS - can it be a network server? ASH, JAMES (SBCSI)
2001-08-21 23:02 ` Corinna Vinschen
     [not found] <997833795.4654.ezmlm@sources.redhat.com>
2001-08-15  4:55 ` Reini Urban
     [not found] <200108141640.MAA03457@smtpsrv1.isis.unc.edu>
2001-08-14 13:13 ` Jochen Küpper
2001-08-13 12:40 James L. Ash
2001-08-13 12:44 ` Charles Wilson
2001-08-14  7:39   ` T.Phan
2001-08-14  9:24     ` Charles Wilson
2001-08-14  9:37       ` Mark Paulus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8BFEC206D292D311921500508B0BCB8D08791E06@msgstl01.sbc.com \
    --to=ja7295@sbc.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).