Difference: CVS (1 vs. 10)

Revision 102011-02-09 - DavidThompson

Line: 1 to 1
 
META TOPICPARENT name="SunGridEngine"

CVS"> Using CVS

Revision 92007-10-22 - KevinLeytonBrown

Line: 1 to 1
 
META TOPICPARENT name="SunGridEngine"

CVS"> Using CVS

Line: 24 to 24
  Use version 1.8.13, other versions may not work correctly.
Changed:
<
<
  • CVS Checkout Setup:
>
>
  • CVS Checkout Setup: use the same as the picture below, except that you should use your own user name, the appropriate module name that you're trying to check out, and the repository folder /ubc/cs/research/arrow/cvs
  CVS Checkout Setup

Revision 82007-10-18 - ErikZawadzki

Line: 1 to 1
 
META TOPICPARENT name="SunGridEngine"

CVS"> Using CVS

Line: 24 to 24
  Use version 1.8.13, other versions may not work correctly.
Added:
>
>
  • CVS Checkout Setup:
    CVS Checkout Setup
 

Setting up a public/private key pair so that you don't have to authenticate every time

Line: 38 to 41
  -- KevinLeytonBrown - 16 May 2007
Added:
>
>
META FILEATTACHMENT attr="h" comment="CVS Checkout Setup" date="1192733121" name="cvs.PNG" path="cvs.PNG" size="14288" user="epz" version="1.1"

Revision 72007-10-18 - ErikZawadzki

Line: 1 to 1
 
META TOPICPARENT name="SunGridEngine"

CVS"> Using CVS

Line: 22 to 22
  A good Windows CVS client that integrates with Explorer is TortoiseCVS. It's open-source. Use Okanagan as your server, and connect using SSH.
Changed:
<
<
Use version 1.8.13, other versions may not work correctly.
>
>
Use version 1.8.13, other versions may not work correctly.
 

Setting up a public/private key pair so that you don't have to authenticate every time

Revision 62007-10-16 - ErikZawadzki

Line: 1 to 1
 
META TOPICPARENT name="SunGridEngine"

CVS"> Using CVS

Line: 22 to 22
  A good Windows CVS client that integrates with Explorer is TortoiseCVS. It's open-source. Use Okanagan as your server, and connect using SSH.
Added:
>
>
Use version 1.8.13, other versions may not work correctly.
 

Setting up a public/private key pair so that you don't have to authenticate every time

Revision 52007-09-27 - KevinLeytonBrown

Line: 1 to 1
 
META TOPICPARENT name="SunGridEngine"
Changed:
<
<

Permissions

Users of CVS have to take some one-time steps so that the permissions of files the commit will be correct. (Otherwise, other uses will be unable to modify or even update files that such users have created.)

  1. Set up permissions so all files are group writable. All directories need to be group rwx. (as far as I know, this is already done in /ai/kevinlb/cvs, for the group klb).
  2. Copy the file from /hooks/post-commit.tmpl to /hooks/post-commit and add the lines:
>
>

CVS"> Using CVS

 
Changed:
<
<
  • chgrp -R
  • chmod -R g+rwx
>
>
This page is part of the EmpiricalAlgorithmics web.
 
Changed:
<
<
Each student will have to do this so that whenever they commit files, the files will get chgrp'ed and chmod'ed.

These instructions come from Tim (timkl@csDELETEthisTEXT.ubc.ca); please direct questions to him.

Permissions redux

>
>

Permissions

 
Changed:
<
<
The above didn't seem to always work. Here's something else from Sean Godel:
>
>
Here's something from Sean Godel:
 
Deleted:
<
<
Hi Kevin, so doing more research into this I discovered a few things.
 If the CVS client is configured to go through okanagan then group inheritance is preserved. If it goes through cascade group inheritance is preserved for the first directory created but nothing after that.
Line: 31 to 20
 

CVS in Windows

Changed:
<
<
A good Windows CVS client that integrates with Explorer is TortoiseCVS. It's open-source.
>
>
A good Windows CVS client that integrates with Explorer is TortoiseCVS. It's open-source. Use Okanagan as your server, and connect using SSH.
 

Setting up a public/private key pair so that you don't have to authenticate every time

Revision 42007-09-21 - KevinLeytonBrown

Line: 1 to 1
 
META TOPICPARENT name="SunGridEngine"
Deleted:
<
<

CVS in Windows

I like to use TortoiseCVS.

 

Permissions

Users of CVS have to take some one-time steps so that the permissions of files the commit will be correct. (Otherwise, other uses will be unable to modify or even update files that such users have created.)

Line: 18 to 14
  These instructions come from Tim (timkl@csDELETEthisTEXT.ubc.ca); please direct questions to him.
Added:
>
>

Permissions redux

The above didn't seem to always work. Here's something else from Sean Godel:

Hi Kevin, so doing more research into this I discovered a few things. If the CVS client is configured to go through okanagan then group inheritance is preserved. If it goes through cascade group inheritance is preserved for the first directory created but nothing after that. This might be an issue with NFSv4 and the NetApp as we have discovered other Unix conventions that operate differently with this mapping.

For now I would recommend all your users to switch to okanagan as their contact server. If some have trouble with it, let me know as its most likely their environment which can be easily fixed.

CVS in Windows

A good Windows CVS client that integrates with Explorer is TortoiseCVS. It's open-source.

 

Setting up a public/private key pair so that you don't have to authenticate every time

  • In UNIX type ssh-keygen -t dsa.

Revision 32007-07-23 - KevinLeytonBrown

Line: 1 to 1
 
META TOPICPARENT name="SunGridEngine"

CVS in Windows

I like to use TortoiseCVS.

Added:
>
>

Permissions

Users of CVS have to take some one-time steps so that the permissions of files the commit will be correct. (Otherwise, other uses will be unable to modify or even update files that such users have created.)

  1. Set up permissions so all files are group writable. All directories need to be group rwx. (as far as I know, this is already done in /ai/kevinlb/cvs, for the group klb).
  2. Copy the file from /hooks/post-commit.tmpl to /hooks/post-commit and add the lines:

  • chgrp -R
  • chmod -R g+rwx

Each student will have to do this so that whenever they commit files, the files will get chgrp'ed and chmod'ed.

These instructions come from Tim (timkl@csDELETEthisTEXT.ubc.ca); please direct questions to him.

 

Setting up a public/private key pair so that you don't have to authenticate every time

  • In UNIX type ssh-keygen -t dsa.

Revision 22007-06-29 - KevinLeytonBrown

Line: 1 to 1
 
META TOPICPARENT name="SunGridEngine"

CVS in Windows

Line: 12 to 12
 
  • Install Putty
  • Use the PuttyGen program to convert the key to Putty format
  • Then run the Pageant program and add the key that you just created.
Added:
>
>
  • To load the key automatically when Windows starts, put Pageant in the startup folder, and add the full path to the key (in quotes if necessary) as an argument.
 
  • Now you will not be prompted for a password when doing a CVS update with Tortoise.

-- KevinLeytonBrown - 16 May 2007

Revision 12007-05-16 - KevinLeytonBrown

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="SunGridEngine"

CVS in Windows

I like to use TortoiseCVS.

Setting up a public/private key pair so that you don't have to authenticate every time

  • In UNIX type ssh-keygen -t dsa.
  • Copy the resulting .pub file to the .ssh directory in your UNIX home directory, and append it to the authorized_keys file in the same directory. (Create that file if you need to)
  • Copy the resulting file with no extension (your private key) to the computer you want to connect from
  • Install Putty
  • Use the PuttyGen program to convert the key to Putty format
  • Then run the Pageant program and add the key that you just created.
  • Now you will not be prompted for a password when doing a CVS update with Tortoise.

-- KevinLeytonBrown - 16 May 2007

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback