Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Linux CVS Server and Windows CVS Server



On 10/7/05, Dave Peters <gameslover987 at yahoo.com> wrote:
> Hello all,
>
> Can anyone help me to give some ideals about what's
> different between Linux CVS Server and Windows CVS
> server? What is advantage and disadvantage? I try to
> push for Linux CVS instead Windows.
>
UNLESS things have changed since last time I setup a CVS server, you
can NOT USE WINDOWS as a CVS server operating system for more than a
local client, meaning it is only good for a single user.  So much for
enabling the concept of collaboration.

Actually, I checked the CVS book on it
(http://cvsbook.red-bean.com/cvsbook.html)

Limitations Of The Windows And Macintosh Versions

The Windows and Macintosh distributions of CVS are generally limited
in functionality. They can all act as clients, meaning that they can
contact a repository server to obtain a working copy, commit, update,
and so on. But they can't serve repositories themselves. If you set it
up right, the Windows port can use a local-disk repository, but it
still can't serve projects from that repository to other machines. In
general, if you want to have a network-accessible CVS repository, you
must run the CVS server on a Unix box.




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org