In the examples below, the group name is "dieharder", which is simple enough. Now change to the directory immediately above the CVS root directory, e. The first causes the entire project to be group accessible to members of dieharder. The next two are very important -- they permit team member A to be able to make changes to files that belong to team member B in this directory!
These permit fine grained control over who can access any given file or directory. ACLs do not require root privileges in order to set up what amounts to a "group". However, it is pretty complex and I'm going to omit a step-by-step in this first draft. If you really need it and cannot figure it out on your own or with locally provided documentation, write me and I'll add it in the next major revision. This will make all CVS commands entered without an explicit root defined refer by default to it.
If your shell is bash, put the following into e. If it is csh or tcsh put the following into. If you work on several shared projects, you'll have to specify the correct CVS root for the project for every CVS command you enter in association with the project.
We already used this syntax above with the "init" command to create the CVS root directory in the first place. Similar considerations will hold for any CVS root directory that you own or participate in a project under -- if you want to use it using the commands above, you have to be "local" to the actual CVS root directory to do so.
Sometimes, however, you'll want to be able to access the project from faraway -- a system at home or a laptop that is not a trusted part of the department LAN and does not mount the filesystem on which the CVS root directory resides.
There is a way to do this via a "cvs server" that is used by for example sourceforge to provide both authenticated and anonymous access. However, it requires all sorts of root access and is somewhat dubious from a security point of view. The following presumes that you and other project members have an account on a system that mounts the CVS root, which might be one or more LAN clients with NFS access or a dedicated project server with only a local mount.
Go ahead and commit them: cvs commit -m "original file" sample. This latter form is usually more useful. Write good log messages! It updates your working directory from the repository, but also tells you status of files. Try it: cvs update Probably all you got was a message like "cvs update: Updating.
The result of update will have the letter M next to the sample. This indicates that you have modified the file. No account on the CVS repository is needed. To test anonymous access to the CVS repository, log in to another machine as an unprivileged user and execute the following command:. The -m flags specifies an initial descriptive entry for the new module.
The cvstest parameter is the name used for the module in all subsequent cvs commands. The vendortag and releasetag parameters are used to further identify each CVS module and are mandatory whether used or not. Other Server Software Prev rsync Testing anonymous access to the new repository requires an account on another machine that can reach the CVS server via network. No account on the CVS repository is needed.
To test anonymous access to the CVS repository, log in to another machine as an unprivileged user and execute the following command:. The -m flags specifies an initial descriptive entry for the new module. The "cvstest" parameter is the name used for the module in all subsequent cvs commands. The "vendortag" and "releasetag" parameters are used to further identify each CVS module and are mandatory whether used or not. Beyond Linux From Scratch - Version 5.
0コメント