RE: CVS Unix to Linux Migration

Rez <[email protected]>
Newsgroups gmane.comp.version-control.cvs.general
Message-ID <[email protected]>
> Date: Wed, 4 Feb 2009 07:18:17 -0700> From: [email protected]> CC: [email protected]> Subject: Re: CVS Unix to Linux Migration> > Amaresh Chandra Das wrote:> > > > 1- if the migration is more involved than simply tarballing the repository> > from the old server and untarring and mounting it on the new server?> > Meaning, the repository is independent and not affected by the old OS in any> > way as far as file system or formatting or any other thing go. What else do> > I need to do on the old server to prepare?> > Yes, although, if you have put your lock directories in a different place, > you will need to create those on the new server. The other catch, is that > often on CVS server, the CVSTMP point somewhere else than the default > (because the default, /tmp, is too small), again you need to make sure that > that directory exists, and that there is enough space in there.
 
Does cvs by default use the /tmp directory to keep track of locked files? Where's this directive set, in what file, should I tell cvs to direct to another directory, /etc/inetd.conf?> > The other thing is, if you use extended ACL, then you need to translate > those between the Solaris ones and the Linux ones.> > > 2- Because it's a migration by way of untarring, do I still need to execute> > "cvs -d /repo/path init" since the existing repo already contains the> > CVSROOT directory?> > No, when you untar, it will create the CVSROOT directories, which is what > "cvs init" does.> > > > > > 3- Also, I would like to get rid of some old projects in the repository> > before I migrate it, we don't need the history and don't need to save them,> > so could I just log into the old server as Admin and do an rm or mv command> > (carefully of course) w/o trashing or corrupting the repository?> > Are those modules, or repositories ?> If they are repositories, then yes it is easy to delete (mv), if they are > modules, then it is also easy, but it means that your log file will be wrong > which might be an issue if, for example, you transfer to another SCM later.
 
They're not respositories but projects under it.  So then does that mean I have to use a cvs client to remove them and commit them to the attic?  Thanks for your help.
> > In either case, disk space is cheap, personally I would archive rather than > delete.> > -- > Yves.> http://www.sollers.ca/blog/2008/> > > 
_________________________________________________________________
Windows Live™: Keep your life in sync. 
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_022009
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.