I. CVS version problem
CVS separates two programs on the client and server, the server side with CVSNT under the Windows platform, current software is basically stable, but the speed is slightly slower than the Linux / UNIX. But for those who are familiar with the Windows application, because of their simple operation, it is not a good choice.
Note: The client and server side are uniform. This article is recommended:
Server: cvsNT2.0.34 Download file CVSNT-2.0.34.EXE in www.cvsnt.org
Client: WinCvs13b17.zip Download WinCvs13b17.zip in SourceForge.net/Projects/cvsgui/
The method of checking can be successfully connected, run:
CVS Version
***** CVS EXITED NORMALLY with CODE 0 *****
Client: Concurrent Versions System (CVSNT) 2.0.34 (Client / Server)
Server: Concurrent Versions System (CVSNT) 2.0.34 (Client / Server)
It can be seen that the version of these two software is very matched. When the version is inconsistent, the client's command server explains the case.
Or on the server side, start-> setting -> Control Silver Open CVSNT profile, you can also see the version of the server (as shown below):
In the client, in the DOS state, go to C: / Program Files / GNU / WinCVS 1.3 / CVSNT (default installation directory) Enter the command CVS version, you can see the version information of the client (as shown below):
In addition, since WinCvs1.3 comes with some convenient management macros (of course, you can also refer to these macro themselves), you can see a bunch in C: / Program Files / GNU / WinCVS 1.3 / Macros. * .tcl file, these actually Python and TCL script files, it is recommended to install the Windows version of Python and TCL to run these scripts or to extend their own tools for themselves.
After installing these two compilers, you can easily switch these two scripting languages in WinCvs1.3 (as shown below):
2. CVS permission management
CVS has its own set of rights management rules, but only the level of the directory. The owner of the administrator and directory of the CVS can set the permissions in the corresponding directory. In the directory of each CVS (server side), you can find a .owner and .perms file, the two files record the permissions of the directory owner and the corresponding settings, respectively.
It is worth noting that the permission management of CVS is a very simple manner, only to the first level of the directory, each directory below to specifically manages the current directory, if not These files, the permissions are inherited by the directory of the previous level. But the permissions it set is limited to CVS, and will eventually be controlled by system authority. For example, even if a directory is clear. Wener has recorded a user, but the user is defined in the server system to define the read permissions of this directory, which can not checkout to this directory.
Therefore, CVS's permission management is weak than the system's permissions, it can be seen as an appropriate and simple supplement under system authority management. When you don't want to build too much system users, when you use appropriate system users to shoot more CVS users, CVS's permissions management acts. At this time you need an administrator or directory owner to run CVS Chak for each directory to define user permissions. III. CVS is controlled under Window2000
Since the permissions management function of Window2000 is already very rich, if there is too many users who do not mind the system users, it is recommended to use CVS under the Windows platform (referring to the server side) to set up.
Establish a group, you can use Window2000 rich permission management to implement cross-management of permissions through group definitions.
The specific recommendations are as follows:
1. Create a cvsadmin user in the system, belonging to the Administrators group.
The management of the CVS system will be made by this user.
2. Add new repository in CVSNT, for example C: / CVSFiles, and then automatically generate a c: / cvsfiles under the CVSROOT directory.
3. Permissions control for cvsfiles, set to only fully control of the Administrators group, remove the original Everyone default setting (as shown below):
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory. 9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied increases the content:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
2. CVS permission management
CVS has its own set of rights management rules, but only the level of the directory. The owner of the administrator and directory of the CVS can set the permissions in the corresponding directory. In the directory of each CVS (server side), you can find a .owner and .perms file, the two files record the permissions of the directory owner and the corresponding settings, respectively. It is worth noting that the permission management of CVS is a very simple manner, only to the first level of the directory, each directory below to specifically manages the current directory, if not These files, the permissions are inherited by the directory of the previous level. But the permissions it set is limited to CVS, and will eventually be controlled by system authority. For example, even if a directory is clear. Wener has recorded a user, but the user is defined in the server system to define the read permissions of this directory, which can not checkout to this directory.
Therefore, CVS's permission management is weak than the system's permissions, it can be seen as an appropriate and simple supplement under system authority management. When you don't want to build too much system users, when you use appropriate system users to shoot more CVS users, CVS's permissions management acts. At this time you need an administrator or directory owner to run CVS Chak for each directory to define user permissions.
III. CVS is controlled under Window2000
Since the permissions management function of Window2000 is already very rich, if there is too many users who do not mind the system users, it is recommended to use CVS under the Windows platform (referring to the server side) to set up.
Establish a group, you can use Window2000 rich permission management to implement cross-management of permissions through group definitions.
The specific recommendations are as follows:
1. Create a cvsadmin user in the system, belonging to the Administrators group.
The management of the CVS system will be made by this user.
2. Add new repository in CVSNT, for example C: / CVSFiles, and then automatically generate a c: / cvsfiles under the CVSROOT directory.
3. Permissions control for cvsfiles, set to only fully control of the Administrators group, remove the original Everyone default setting (as shown below):
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied increases the content:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
In addition, since WinCvs1.3 comes with some convenient management macros (of course, you can also refer to these macro themselves), you can see a bunch in C: / Program Files / GNU / WinCVS 1.3 / Macros. * .tcl file, these actually Python and TCL script files, it is recommended to install the Windows version of Python and TCL to run these scripts or to extend their own tools for themselves.
After installing these two compilers, you can easily switch these two scripting languages in WinCvs1.3 (as shown below):
2. CVS permission management
CVS has its own set of rights management rules, but only the level of the directory. The owner of the administrator and directory of the CVS can set the permissions in the corresponding directory. In the directory of each CVS (server side), you can find a .owner and .perms file, the two files record the permissions of the directory owner and the corresponding settings, respectively.
It is worth noting that the permission management of CVS is a very simple manner, only to the first level of the directory, each directory below to specifically manages the current directory, if not These files, the permissions are inherited by the directory of the previous level. But the permissions it set is limited to CVS, and will eventually be controlled by system authority. For example, even if a directory is clear. Wener has recorded a user, but the user is defined in the server system to define the read permissions of this directory, which can not checkout to this directory.
Therefore, CVS's permission management is weak than the system's permissions, it can be seen as an appropriate and simple supplement under system authority management. When you don't want to build too much system users, when you use appropriate system users to shoot more CVS users, CVS's permissions management acts. At this time you need an administrator or directory owner to run CVS Chak for each directory to define user permissions.
III. CVS is controlled under Window2000
Since the permissions management function of Window2000 is already very rich, if there is too many users who do not mind the system users, it is recommended to use CVS under the Windows platform (referring to the server side) to set up.
Establish a group, you can use Window2000 rich permission management to implement cross-management of permissions through group definitions.
The specific recommendations are as follows:
1. Create a cvsadmin user in the system, belonging to the Administrators group.
The management of the CVS system will be made by this user.
2. Add new repository in CVSNT, for example C: / CVSFiles, and then automatically generate a c: / cvsfiles under the CVSROOT directory.
3. Permissions control for cvsfiles, set to only fully control of the Administrators group, remove the original Everyone default setting (as shown below):
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files. 4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration. / --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT |
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
2. CVS permission management
CVS has its own set of rights management rules, but only the level of the directory. The owner of the administrator and directory of the CVS can set the permissions in the corresponding directory. In the directory of each CVS (server side), you can find a .owner and .perms file, the two files record the permissions of the directory owner and the corresponding settings, respectively.
It is worth noting that the permission management of CVS is a very simple manner, only to the first level of the directory, each directory below to specifically manages the current directory, if not These files, the permissions are inherited by the directory of the previous level. But the permissions it set is limited to CVS, and will eventually be controlled by system authority. For example, even if a directory is clear. Wener has recorded a user, but the user is defined in the server system to define the read permissions of this directory, which can not checkout to this directory.
Therefore, CVS's permission management is weak than the system's permissions, it can be seen as an appropriate and simple supplement under system authority management. When you don't want to build too much system users, when you use appropriate system users to shoot more CVS users, CVS's permissions management acts. At this time you need an administrator or directory owner to run CVS Chak for each directory to define user permissions.
III. CVS is controlled under Window2000
Since the permissions management function of Window2000 is already very rich, if there is too many users who do not mind the system users, it is recommended to use CVS under the Windows platform (referring to the server side) to set up.
Establish a group, you can use Window2000 rich permission management to implement cross-management of permissions through group definitions.
The specific recommendations are as follows:
1. Create a cvsadmin user in the system, belonging to the Administrators group. The management of the CVS system will be made by this user.
2. Add new repository in CVSNT, for example C: / CVSFiles, and then automatically generate a c: / cvsfiles under the CVSROOT directory.
3. Permissions control for cvsfiles, set to only fully control of the Administrators group, remove the original Everyone default setting (as shown below):
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT | TEST2.TXT
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below): User1 and USER2 can be checkout, but can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
In the client, in the DOS state, go to C: / Program Files / GNU / WinCVS 1.3 / CVSNT (default installation directory) Enter the command CVS version, you can see the version information of the client (as shown below):
In addition, since WinCvs1.3 comes with some convenient management macros (of course, you can also refer to these macro themselves), you can see a bunch in C: / Program Files / GNU / WinCVS 1.3 / Macros. * .tcl file, these actually Python and TCL script files, it is recommended to install the Windows version of Python and TCL to run these scripts or to extend their own tools for themselves.
After installing these two compilers, you can easily switch these two scripting languages (as shown below): II. CVS permission management
CVS has its own set of rights management rules, but only the level of the directory. The owner of the administrator and directory of the CVS can set the permissions in the corresponding directory. In the directory of each CVS (server side), you can find a .owner and .perms file, the two files record the permissions of the directory owner and the corresponding settings, respectively.
It is worth noting that the permission management of CVS is a very simple manner, only to the first level of the directory, each directory below to specifically manages the current directory, if not These files, the permissions are inherited by the directory of the previous level. But the permissions it set is limited to CVS, and will eventually be controlled by system authority. For example, even if a directory is clear. Wener has recorded a user, but the user is defined in the server system to define the read permissions of this directory, which can not checkout to this directory.
Therefore, CVS's permission management is weak than the system's permissions, it can be seen as an appropriate and simple supplement under system authority management. When you don't want to build too much system users, when you use appropriate system users to shoot more CVS users, CVS's permissions management acts. At this time you need an administrator or directory owner to run CVS Chak for each directory to define user permissions.
III. CVS is controlled under Window2000
Since the permissions management function of Window2000 is already very rich, if there is too many users who do not mind the system users, it is recommended to use CVS under the Windows platform (referring to the server side) to set up.
Establish a group, you can use Window2000 rich permission management to implement cross-management of permissions through group definitions.
The specific recommendations are as follows:
1. Create a cvsadmin user in the system, belonging to the Administrators group.
The management of the CVS system will be made by this user.
2. Add new repository in CVSNT, for example C: / CVSFiles, and then automatically generate a c: / cvsfiles under the CVSROOT directory.
3. Permissions control for cvsfiles, set to only fully control of the Administrators group, remove the original Everyone default setting (as shown below):
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 ***** CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified) | TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
2. CVS permission management
CVS has its own set of rights management rules, but only the level of the directory. The owner of the administrator and directory of the CVS can set the permissions in the corresponding directory. In the directory of each CVS (server side), you can find a .owner and .perms file, the two files record the permissions of the directory owner and the corresponding settings, respectively.
It is worth noting that the permission management of CVS is a very simple manner, only to the first level of the directory, each directory below to specifically manages the current directory, if not These files, the permissions are inherited by the directory of the previous level. But the permissions it set is limited to CVS, and will eventually be controlled by system authority. For example, even if a directory is clear. Wener has recorded a user, but the user is defined in the server system to define the read permissions of this directory, which can not checkout to this directory.
Therefore, CVS's permission management is weak than the system's permissions, it can be seen as an appropriate and simple supplement under system authority management. When you don't want to build too much system users, when you use appropriate system users to shoot more CVS users, CVS's permissions management acts. At this time you need an administrator or directory owner to run CVS Chak for each directory to define user permissions.
III. CVS is controlled under Window2000
Since the permissions management function of Window2000 is already very rich, if there is too many users who do not mind the system users, it is recommended to use CVS under the Windows platform (referring to the server side) to set up.
Establish a group, you can use Window2000 rich permission management to implement cross-management of permissions through group definitions.
The specific recommendations are as follows:
1. Create a cvsadmin user in the system, belonging to the Administrators group.
The management of the CVS system will be made by this user.
2. Add new repository in CVSNT, for example C: / CVSFiles, and then automatically generate a c: / cvsfiles under the CVSROOT directory.
3. Permissions control for cvsfiles, set to only fully control of the Administrators group, remove the original Everyone default setting (as shown below):
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group. Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only) | TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified) Test2Dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
In addition, since WinCvs1.3 comes with some convenient management macros (of course, you can also refer to these macro themselves), you can see a bunch in C: / Program Files / GNU / WinCVS 1.3 / Macros. * .tcl file, these actually Python and TCL script files, it is recommended to install the Windows version of Python and TCL to run these scripts or to extend their own tools for themselves.
After installing these two compilers, you can easily switch these two scripting languages in WinCvs1.3 (as shown below):
2. CVS permission management
CVS has its own set of rights management rules, but only the level of the directory. The owner of the administrator and directory of the CVS can set the permissions in the corresponding directory. In the directory of each CVS (server side), you can find a .owner and .perms file, the two files record the permissions of the directory owner and the corresponding settings, respectively.
It is worth noting that the permission management of CVS is a very simple manner, only to the first level of the directory, each directory below to specifically manages the current directory, if not These files, the permissions are inherited by the directory of the previous level. But the permissions it set is limited to CVS, and will eventually be controlled by system authority. For example, even if a directory is clear. Wener has recorded a user, but the user is defined in the server system to define the read permissions of this directory, which can not checkout to this directory.
Therefore, CVS's permission management is weak than the system's permissions, it can be seen as an appropriate and simple supplement under system authority management. When you don't want to build too much system users, when you use appropriate system users to shoot more CVS users, CVS's permissions management acts. At this time you need an administrator or directory owner to run CVS Chak for each directory to define user permissions.
III. CVS is controlled under Window2000
Since the permissions management function of Window2000 is already very rich, if there is too many users who do not mind the system users, it is recommended to use CVS under the Windows platform (referring to the server side) to set up.
Establish a group, you can use Window2000 rich permission management to implement cross-management of permissions through group definitions. The specific recommendations are as follows:
1. Create a cvsadmin user in the system, belonging to the Administrators group.
The management of the CVS system will be made by this user.
2. Add new repository in CVSNT, for example C: / CVSFiles, and then automatically generate a c: / cvsfiles under the CVSROOT directory.
3. Permissions control for cvsfiles, set to only fully control of the Administrators group, remove the original Everyone default setting (as shown below):
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below): User1 and USER2 can be checkout, but can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
2. CVS permission management
CVS has its own set of rights management rules, but only the level of the directory. The owner of the administrator and directory of the CVS can set the permissions in the corresponding directory. In the directory of each CVS (server side), you can find a .owner and .perms file, the two files record the permissions of the directory owner and the corresponding settings, respectively.
It is worth noting that the permission management of CVS is a very simple manner, only to the first level of the directory, each directory below to specifically manages the current directory, if not These files, the permissions are inherited by the directory of the previous level. But the permissions it set is limited to CVS, and will eventually be controlled by system authority. For example, even if a directory is clear. Wener has recorded a user, but the user is defined in the server system to define the read permissions of this directory, which can not checkout to this directory.
Therefore, CVS's permission management is weak than the system's permissions, it can be seen as an appropriate and simple supplement under system authority management. When you don't want to build too much system users, when you use appropriate system users to shoot more CVS users, CVS's permissions management acts. At this time you need an administrator or directory owner to run CVS Chak for each directory to define user permissions. III. CVS is controlled under Window2000
Since the permissions management function of Window2000 is already very rich, if there is too many users who do not mind the system users, it is recommended to use CVS under the Windows platform (referring to the server side) to set up.
Establish a group, you can use Window2000 rich permission management to implement cross-management of permissions through group definitions.
The specific recommendations are as follows:
1. Create a cvsadmin user in the system, belonging to the Administrators group.
The management of the CVS system will be made by this user.
2. Add new repository in CVSNT, for example C: / CVSFiles, and then automatically generate a c: / cvsfiles under the CVSROOT directory.
3. Permissions control for cvsfiles, set to only fully control of the Administrators group, remove the original Everyone default setting (as shown below):
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Increase content is also:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory. 9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
The benefits of doing this are because the Window2000 default permission management is sub-directory authority inherits in the parent directory, if you don't remove EVERYONE, the general user is easier to add to this directory with the project-related files.
4. Create a group and this item in the system, for example, Team1.
5. Establish a related user, set to a general user (Users) and return to the Team1 group. For example, USER1, User2.
6. At this point, you can see that CVSRoot can be seen, because inherited from the parent directory, it can only be fully controlled by members of the Administrators group.
Note: To set CVSROOT to the general user (here is the read-free read permissions) read-only, otherwise the general CVS user can not checkout. Set the History file under CVSROOT to Team1 fully controlled.
7. User1, user2 can be logged in, but it is not possible to checkout to cvsroot.
CVS -Z9 Checkout CvsRoot
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied increases the content:
CVS import -m "test1" test vendor start
***** CVS EXITED NORMALLY with CODE 1 *****
CVS [Server Aborted]: Cannot Access C: / CVSFILES / CVSROOT: Permission Denied
Therefore, the work of importing modules is still made through CVSADMIN.
For example, the module TEST1 is imported.
8. For the newly imported modules TEST1 TEST1, USER1 and USER2 or Checkout, you need to use Window Permissions to add permissions to them. For example, they can only read this module (as shown below):
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
User1 and USER2 can be checkout, but they can not modify this directory.
9. If the permissions attached to the following Test2Dir are given to USER1 (as shown below), USER1 can modify this subdirectory.
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
10. The tree picture below is the permissions of this demonstration.
/ --- Test1 (Team1 read-only)
| TEST1.TXT
| Test2.txt
|
--- TestDir (user2 can be modified)
| TEST11.TXT
|
/ --- Test2Dir (user1 can be modified)
Test2dir1.txt
