<P>TortoiseCVS works extremely well as a client. Some IDE/Editor programs like PeggyPro also work easily. ViewCVS will fairly easily work with Build 57J, and with Build 65 is you configure things properly. (read the history in ViewCVS mailing list).
<P>The copy of the repository will probably work, although you may have to manually edit the plain text files in the CVSROOT to correct the paths, then when CVSNT is running, check out CVSROOT, do the same changes, and commit them.
<P>Alternate try: Checkout a full copy of the repository from the Linux Box. Delete all the \CVS\ dirs in it. Then Add the whole thing to the new server. And finally, overwrite the newly created repo files (xxx,v) with the ones from the Linux box - that should put the history into each file.
<P>I believe the repository files are supposed to be the same format for CVS and CVSNT. If not: Check in a simple one line file to both the linux box and the new server. Then compare the contents of the two new repository xxx,v files. You can use an IDE/Edittor with multifile replace (PeggyPro, CodeWright...) to adjust a copy of the repository files for use in the new repository.
<P>Good luck!
<P>- Paul
<P> <B><I>Mark Stuhr <mark@nolo.com></I></B> wrote:
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">We are considering doing what the subject line says and are doing some<BR>testing.<BR><BR>We've successfully got CVSNT up and running.<BR><BR>I'm trying to run it with only ssspi for logins. This seems to mean that<BR>we can only use wincvs beta 1.3 clients is that correct??<BR><BR>Now for the meaty thing.<BR><BR>Is it possible to commit all existing changes outstanding in our linux<BR>repository and then just move the whole repository over to the Win2K<BR>server that's running cvsnt??<BR><BR>If possible what steps would need to be made after the copy to get the<BR>repository up and running and available to all clients?? (Mainly will I<BR>have to recreate all the repository routes manually in the cvsnt control<BR>panel??)<BR><BR>I've tried a version of this (just moving over the CVSROOT folder and one<BR>repository and whenever I try to do anything with that migrated repository<BR>there's a message in the terminal window of wincvs that it can't find<BR><BR>Cannot access E:/cvsrepo/ql_biz_2004_win/CVSROOT<BR>No such file or directory<BR><BR>That looks like correct directory structure on the cvsnt server except<BR>there's no CVSROOT folder inside the repository folder??<BR><BR>If it's not possible to move the repository files over is there some other<BR>method for migrating this information in a way that wouldn't take too much<BR>work and would allow us to keep all of the version history of the existing<BR>projects/files??<BR><BR>Thanks<BR><BR>Mark Stuhr<BR>Director of Inf. Tech.<BR>Nolo<BR>mark@nolo.com<BR><BR><BR>_______________________________________________<BR>cvsnt mailing list<BR>cvsnt@cvsnt.org<BR>http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt<BR></BLOCKQUOTE><p><br><hr size=1>Post your free ad now! <a href="http://ca.personals.yahoo.com/"><b>Yahoo! Canada Personals</b></a><br>