home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
nosaa107.zip
/
nosaadm.inf
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1999-11-11
|
114KB
|
1,936 lines
ΓòÉΓòÉΓòÉ 1. OS/2 Netlabs Open Source Archive Administrator ΓòÉΓòÉΓòÉ
in association with
present the
OS/2 Netlabs Open Source Archive Administrator
Select one of the following topics:
What is it all about ?
Prerequisites
Copyright & Co.
Installation
Usage
How can I ... ?
Limitations
Revision history
Trademarks
Credits
ΓòÉΓòÉΓòÉ 1.1. What is it all about ? ΓòÉΓòÉΓòÉ
Select one of the following topics:
Overview
Concurrent Versions System (CVS)
Info-Zip
EMX Runtime
ΓòÉΓòÉΓòÉ 1.1.1. Overview ΓòÉΓòÉΓòÉ
OS/2 Netlabs Open Source Archive Administrator
Are you an OS/2 developer, who uses the OS/2 Open Source Archive Client to
access the OS/2 Netlabs Open Source Archive ? Do you want to know, how OS/2
Netlabs sets up a new archvie from a zip archive file with a handful of
commands in minutes ? Do you want to host an own software archive ? Have you
ever wondered how one could secure such archive even without filesystem
security on an OS/2 client ?
Then use the software, that is used by OS/2 Netlabs to setup the archvies for
several OS/2 internet projects, namely the OS/2 Netlabs Open Source Archive
Administrator. It supports the OS/2 Netlabs administrator in:
creating a new archive
importing existing sources out of a zip file
adding keyword lines to all source files
securing the new archive by protecting it from unwanted write access down
to directory level
setting up the TCP/IP configuration and especially the CVS services
creating backups
creating snapshots of the archive
creating a changelog of the changes being committed to the archive
Want more ? Well, just read this online book...
ΓòÉΓòÉΓòÉ 1.1.2. Concurrent Versions System (CVS) ΓòÉΓòÉΓòÉ
See the following links in order to learn more about the Concurrent Versions
System (CVS):
Cyclic Software, the home of CVS
CVS Bubbles with links to documentation
You can download CVS for OS/2 from:
The Hobbes OS/2 Archive
or search the nearest FTP server near you via
FTP Search
Note:
CVS requires the EMX Runtime.
See also
- How can I solve the 'Too many open files' problem ?
ΓòÉΓòÉΓòÉ 1.1.3. Info-Zip ΓòÉΓòÉΓòÉ
The OS/2 Netlabs Open Source Archive Administrator uses the Zip and UnZip
program of Info-Zip.
Note:
The source of Info-Zip is freely available. On the Info-Zip homepage
follow the links to the source on the download pages.
The filename scheme for the executable packages and source packages
differ a littlebit from UnZip to Zip unzip. This is a littlebit
confusing, so the scheme is listed here for the curreint versions Zip
V2.20 and UnZip V5.40 as an example:
zip22x1.zip Zip 2.2, OS/2 16-bit exes (no encryption)
zip22x2.zip Zip 2.2, OS/2 32-bit exes (no encryption)
zip22.zip Zip 2.2, source code
unz540d2.zip UnZip 5.40, OS/2 DLL (32-bit, C and REXX)
unz540x1.exe UnZip 5.40, OS/2 self-extr. exes (16-bit)
unz540x2.exe UnZip 5.40, OS/2 self-extr. exes (32-bit)
unzip540.zip UnZip 5.40, source code
You can download the zip and unzip program of Info-Zip for OS/2 from:
The Info-ZIP homepage
Follow both the links to UnZip and Zip and download the latest version
for OS/2.
ΓòÉΓòÉΓòÉ 1.1.4. EMX Runtime ΓòÉΓòÉΓòÉ
EMX is an environment for creating 32-bit programs for OS/2 (and DOS).
Developers can use the GNU C compiler to compile programs for emx. The main
design goal of emx is to simplify porting Unix software to OS/2 and DOS.
This has been done with the Concurrent Versions System (CVS), which is a widely
used Unix software.
As CVS is being used by the OS/2 Netlabs Open Source Archive Administrator, the
runtime of the EMX package is required.
You can download the EMX runtime for OS/2 from:
The Hobbes OS/2 Archive
OS/2 Supersite (fast hobbes mirror)
Download the file emxrt.zip from the subdirectory with the highest revision
number.
See also
How can I solve the 'Too many open files' problem ?
ΓòÉΓòÉΓòÉ 1.2. Prerequisites ΓòÉΓòÉΓòÉ
The following prerequisites apply to the current version of OS/2 Netlabs Open
Source Archive Administrator:
The OS/2 Netlabs Open Source Archive Administrator runs under OS/2 WARP
Version 3 or later.
Also required is the OS/2 version of the Concurrent Versions System (CVS)
for to provide access the OS/2 Netlabs Open Source Archive.
CVS in turn requires the EMX Runtime.
The Zip and UnZip program of Info-ZIP are required.
For providing access to the OS/2 Netlabs Open Source Archive, also of
course a working internet connection is required.
ΓòÉΓòÉΓòÉ 1.3. Copyright & Co. ΓòÉΓòÉΓòÉ
Select one of the following topics:
Copyright
freeware license
Disclaimer
The author
ΓòÉΓòÉΓòÉ 1.3.1. Copyright ΓòÉΓòÉΓòÉ
OS/2 Netlabs Open Source Archive Administrator
was written by Christian Langanke, 1999.
All rights reserved.
You are welcome to send me your comments/suggestions via internet e-mail.
Send your e-mail to C.Langanke@TeamOS2.DE
Visit also the homepage of
the OS/2 Netlabs Open Source Archive
the author Christian Langanke
the OS/2 Netlabs
Team OS/2 Germany and its member associations
ΓòÉΓòÉΓòÉ 1.3.2. freeware license ΓòÉΓòÉΓòÉ
This software package is freeware. It can be used wherever you use OS/2 WARP
Version 3 or later.
You are allowed to freely use and distribute the OS/2 Netlabs Open Source
Archive Administrator as long as
OS/2 Netlabs Open Source Archive Administrator or its components are not
sold as a part of another program package;
no fee is charged for the program other than for cost of media;
the complete package is distributed unmodified;
ΓòÉΓòÉΓòÉ 1.3.3. Disclaimer ΓòÉΓòÉΓòÉ
Since this program is free, it is supplied with no warranty, either expressed
or implied.
I disclaim all warranties for any damages, including, but not limited to,
incidental or consequential damage caused directly or indirectly by this
software.
All software is supplied AS IS. You may use the OS/2 Netlabs Open Source
Archive Administrator package only at your own risk.
The OS/2 Netlabs Open Source Archive Administrator must not be used in states
that do not allow the above limitation of liability.
ΓòÉΓòÉΓòÉ 1.3.4. The author ΓòÉΓòÉΓòÉ
This program is written by Christian Langanke.
You can contact the author via internet e-mail.
Send your email to C.Langanke@TeamOS2.DE
Visit also the homepage of
the OS/2 Netlabs Open Source Archive Administrator
the author Christian Langanke
the OS/2 Netlabs
Team OS/2 Germany and its member associations
ΓòÉΓòÉΓòÉ 1.4. Installation ΓòÉΓòÉΓòÉ
Select one of the following topics:
Copy files
installation program
The OS/2 Netlabs Open Source Archive Administrator folder
- Refresh this folder
- Create new project archive
- Administrator OS/2 Window
ΓòÉΓòÉΓòÉ 1.4.1. Copy files ΓòÉΓòÉΓòÉ
If you received the OS/2 Netlabs Open Source Archive Administrator package as a
ZIP file, create a directory for the files on your harddisk and unzip all files
from the ZIP file into it.
Make sure that the directory structure stored within the ZIP file is preserved.
Then execute the installation program.
ΓòÉΓòÉΓòÉ 1.4.2. installation program ΓòÉΓòÉΓòÉ
To setup the OS/2 Netlabs Open Source Archive Administrator, execute the
following steps:
1. open an OS/2 Window
2. change into the directory, where the files of the OS/2 Netlabs Open
Source Archive Administrator package reside
3. run the command
install
The installation program first prompts for several values.
You can accept the default values being displayed in brackets by just hitting
Enter. Values marked as optional may be empty. You also can interrupt the
installation program by hitting Ctrl-Break and Enter. You also can rerun the
installation program at any time in order to modify any of these values.
These are the values, that you are prompted for:
hostname for the Netlabs Open Source Archive server
The hostname of the server, under it is to be adressed via internet. This
hostname is being written into archives.lst and/or private.lst, which in
turn are being used by the OS/2 Netlabs Open Source Archive Client.
root directory of the Netlabs Open Source Archive
The directory, where all archive directories, that you use with the OS/2
Netlabs Open Source Archive Administrator, are being created.
root directory for working directories on your computer
The directory, where all working directories, that you use with the OS/2
Netlabs Open Source Archive Administrator, are being created.
root directory for snapshot zipfiles on your computer
The directory, where the snapshot zip files of the source are being
created
root directory for backup zip files on your computer
The directory, where the backup zip files of the archive directories are
being created
CVS home directory
The (empty) directory, where CVS settings are stored
Init Command for project windows (optional)
any command that you want to be executed before OS/2 Netlabs Open Source
Archive Administrator executes any CVS operation. This is especially
useful when you frequently use cvsenv in a archive OS/2 Windows and/or
shells like telnet or SSH, for which you may need to setup a different
environment.
Leave that field empty, if you do not need any init command.
CVS Administrator User Id
your user id, that you want to use with a CVS archive on the OS/2 Netlabs
Open Source Archive server.
Note:
If the environment variable %USER% is set, this value is offered as
default.
In an archive OS/2 Window ot shells liketelnet or SSH, where you
call cvsenv, the environment variable %USER% will be set up with the
user id, that you specify here. Keep that in mind, if you have to
use different values for %USER% within the OS/2 Netlabs Open Source
Archive Administrator and elswewhere.
Directory of CVS installation
This prompt only appears, if the CVS executables are not reachable by
your PATH statement in CONFIG.SYS. Then you can specify the installation
directory of CVS. Just call cvsenv on the commandline and the OS/2
Netlabs Open Source Archive Administrator will extend the PATH for you,
so that you can use CVS in that session
After that, to create a WorkplaceShell folder with precustomized program
objects in it, execute the following steps:
1. open an OS/2 Window
2. change into the directory, where the files of the OS/2 Netlabs Open
Source Archive Administrator package reside
3. run the command
cvsenv
This program creates the OS/2 Netlabs Open Source Archive Administrator
Workplace Shell folder with several objects in it.
ΓòÉΓòÉΓòÉ 1.4.3. The OS/2 Netlabs Open Source Archive Administrator folder ΓòÉΓòÉΓòÉ
To (re)create the OS/2 Netlabs Open Source Archive Administrator folder with
precustomized program objects in it, execute the following steps:
1. open an OS/2 Window
2. change into the directory, where the files of the OS/2 Netlabs Open
Source Archive Administrator package reside
3. run the command
cvsenv
The following Workplace Shell objects are created within the OS/2 Netlabs Open
Source Archive Administrator folder:
Refresh this folder
Create new project archive
Administrator OS/2 Window
Note:
If you want to change the location of the files of the OS/2 Netlabs Open
Source Archive Administrator package, move the directory, where the files
reside, to the new location and rerun the installation program to update
the objects.
ΓòÉΓòÉΓòÉ 1.4.3.1. Refresh this folder ΓòÉΓòÉΓòÉ
This object refreshs the OS/2 Netlabs Open Source Archive Administrator. For
each CVS archive, that you maintain with the OS/2 Netlabs Open Source Archive
Administrator, this icon creates an
Administrator OS/2 Window and
a shadow ot the working directory
If you have created new archives or deleted old ones, you have to refresh the
folder, because these icons are not created or deleted automatically.
ΓòÉΓòÉΓòÉ 1.4.3.2. Create new project archive ΓòÉΓòÉΓòÉ
This object creates a new archive within the OS/2 Netlabs Open Source Archive.
When prompted, specify the name of the archive directory (not the archive name,
which may be different !).
Warning:
With the current version of the OS/2 Netlabs Open Source Archive
Administrator, the name of an archive directory MAY NOT CONTAIN BLANKS
!!!
The name of the base directory of an archive may not start with a ! or ?.
ΓòÉΓòÉΓòÉ 1.4.3.3. Administrator OS/2 Window ΓòÉΓòÉΓòÉ
This object exists for each archive, that you maintain within the OS/2 Netlabs
Open Source Archive, and it opens an OS/2 Window with the environment variables
set fot to access it.
If you have created new archives or deleted old ones, you have to refresh the
folder, because the icons are not created automatically.
See also
Refresh this folder
ΓòÉΓòÉΓòÉ 1.5. Usage ΓòÉΓòÉΓòÉ
Select one of the following topics:
Using the NOSA security
Security levels
Configuring TCP/IP and CVS service
Modified files
- The CVS service program
- %ETC%\services
- %ETC%\inetd.lst
- TCPSTART.CMD
- archives.lst
- private.lst
The userid/password synchronization program
The security program
Modified files
- CVSROOT\passwd
- CVSROOT\writers
- CVSROOT\checkoutlist
- CVSROOT\commitinfo
- CVSROOT\taginfo
- CVSROOT\writeinfo
- CVSROOT\writeinfo.log
Using the administrator package on the commandline
- setup the CVS environment
- Initialize a new archive
- Reinitialize a new archive
- Edit an archive comment
- restrict an archive to private access
- Import zip files with source
- Secure archive
- Create snapshot
- Create backup
- List current archives
- Clear working directory
- Generate a changelog
- Configure CVS service
- Change to the working directory of an archive
- Change to the tree root of an archive
- Change to the NOSAADM program directory
Generating a changelog
- The fullnames list file
- samples\fullnames.lst
Using the administrator package locally with WPS
- Refresh the administrator folder
- Create new project archive
ΓòÉΓòÉΓòÉ 1.5.1. Using the NOSA security ΓòÉΓòÉΓòÉ
Warning:
Read this section carefully, if you allow others to use a CVS service on
your computer !
If so, you may want to use the OS/2 Netlabs Open Source Archive
Administrator security feature in order to protect your system from
unwanted access and/or modifications 1
Within all CVS archives on all platforms, or better, with all services, that
allow to login on a computer in any way, there is a need to secure the server
from unwanted access, that could destroy the system. Under OS/2, this has to
be achieved by different methods as under other operating systems.
Restricting login access to the archive
The first step is to restrict login access to the archive. In case of the OS/2
Netlabs Open Source Archive the only security issue is, that we do not only
need to enable login (and write access) for all developers, but also have a
commin "user id - password" combination, that allows everybody in the world to
access the archive - but of course only in readonly mode. Otherwise this
archive would not be an open one, right ?
The OS/2 Netlabs Open Source Archive Administrator will support you by
initially creating a login account for you as the administrator and for a
guest user with the password readonly. You will have to add more accounts,
when you want to allow others to make modifications to your archive (see
below).
Restricting write access to the complete archive
The second step is to restrict write access to the archive by creating a list
of users, who may write to the archive, excluding all users not being in that
list from being able to make any modifications to the archive.
The OS/2 Netlabs Open Source Archive Administrator will support you by
initially creating a list with only our user id in it, but you have to
customize this list further, when you want to allow others to make
modifications to your archive (see below).
Restricting write access to the archive administrative database (CVSROOT)
The third step is to restrict write access to each directory within the
archive, and most important is the CVSROOT directory of each archive, as it
contains the administration database for it. The files in that directory
especially need protection, because by modification of certain of these files,
any person, that can modify them, can achive to execute any program on the
server. You as the archive administrator should be the only person to have
write access to this crucial directory, and, as other restrictions are
considered, all users, that you give also write access to this directory, are
also considered to be an administrator.
In order to implement such access restriction to the CVSROOT directory, we
could use any mechanism, that restricts access to any directory within the
archive, like mentioned in the next section.
Implementing CVS write access restrictions per directory under OS/2
On platforms with filesystem security, normally the sysadmin would restrict
access to these files by applying appropriate filesystem ACLs (detetmining,
that only the administrator can write these files).
Currently, the OS/2 WARP client has no filesystem security, so that we need a
different approach here. We can instead use a CVS feature for this, which was
invented to allow the setup of check routines. These are for to check for
certain conditions before allowing commit and tag operations, namely the
pre-commit and pre-tag checks.
That is exactly what also we will do. The security program will check, wether
a user may make the desired changes (commit or tag) to files within the
archive or not.
The OS/2 Netlabs Open Source Archive Administrator will support you in setting
up this pre-check feature and a list file CVSROOT\writeinfo, that contains the
information, who may write to which directory. You may have to customize this
listfile further, if you want to allow others to make modifications to your
archive.
Implementing CVS tag restrictions for developers
Tags are a good mechanism to document, who has changed which files. Also,
after having build a release, it is good practise to tag all files with a
release tag name. In order to protect such release tags from being
accidentally deleted by developers, only the archive administrator (having
write access to CVSROOT) can set tags with any name. All other writers are
forced to use personal tags, that is, they have to preceed the tagname by
their userid and underscore, if they want to tag files.
Setting up the security
If you use the OS/2 Netlabs Open Source Archive Administrator to secure your
CVS archives, it makes modifications to some files in CVSROOT, setting up
access security for each directory already existing in the archive. All
directories being created afterwards, inherit their security information fro
their parent directory, unless you add such information for such directory
manually to the appropriate file containing this information.
In order to secure an archive, execute
cvsenv [archive_dirname] $SECURE
within a shell. See section
Modified files
in order to find out how your archive is secured.
ΓòÉΓòÉΓòÉ 1.5.2. Security levels ΓòÉΓòÉΓòÉ
These are the following security levels provided both by CVS and the OS/2
Netlabs Open Source Archive Administrator:
administrator
The administrator is included in
the CVSROOT\passwd file for being able to login
- this file resides in the archive tree only !
- maintain this file with the the userid/password
synchronization program of the OS/2 Netlabs Open Source
Archive Administrator
in the CVSROOT\writers file, so that the administrator can make
changes to files within the archive.
in the CVSROOT\writeinfo in order to determine, within which
directories the administrator can change ot tag files. The
administrator normally is allowed to make modifications within
all directories, especcially within the archive administrative
database in the CVSROOT directory.
developer
The developer is included in
the CVSROOT\passwd file for being able to login
- this file resides in the archive tree only !
- maintain this file with the the userid/password
synchronization program of the OS/2 Netlabs Open Source
Archive Administrator
in the CVSROOT\writers file, so that the developer can make
changes to files within the archive.
in the CVSROOT\writeinfo in order to determine, within which
directories the developer can change ot tag files. Developers
may be restricted to change files only within certain
directories, this depends on decisions of the project team. At
least developers should not be allowed to write the archive
administrative database in the CVSROOT directory.
Note:
A developer can only use personal tags, that means that a
developer has to preceed tag names by his/her userid and
underscore.
guest
The guest accound is implemented by only adding the appropriate user
definition to the CVSROOT\passwd file. With the password readonly a
guest user can only download sources, but cannot make any
modifications to the archive.
ΓòÉΓòÉΓòÉ 1.5.3. Configuring TCP/IP and CVS service ΓòÉΓòÉΓòÉ
The OS/2 Netlabs Open Source Archive Administrator automates the configuration
of both TCP/IP and the CVS service. Simply run the configuration command and
let cvsenv do the work for you, namely modifying and/or creating several files.
Warning:
You need to use this command, whenever you modify the Autostart section
within the TCP/IP configuration program, because this program will
discard any information from %etc%\inetd.lst about services not coming
with the TCP/IP software itself ! OTHERWISE YOUR CVS SERVICE WILL BE
INACTIVE !
Note:
After having added new archives or deleted obsolete ones, run this
command update the current CVS service program.
ΓòÉΓòÉΓòÉ 1.5.4. Modified files ΓòÉΓòÉΓòÉ
The following files are created or modified, when you run the configuration
command:
The CVS service program
%ETC%\services
%ETC%\inetd.lst
TCPSTART.CMD
archives.lst
private.lst
See also
Configuring TCP/IP and CVS service
ΓòÉΓòÉΓòÉ 1.5.4.1. The CVS service program ΓòÉΓòÉΓòÉ
This program is the so called service program of the OS/2 Netlabs Open Source
Archive Administrator. cvsenv rewrites this service program each time the
$CONFIG command is being executed. This service program contains the call to
CVS, as it normally would reside in %ETC%\inetd.lst.
Thus cvsenv adds an --allow-root paramter for each directory in the root
directory of the Netlabs Open Source Archive, that you specified within the
installation program.
This method is particularly intended to avoid to call CVS directly from within
the internet super daemon (inetd) process. There are two advantages of calling
CVS indirectly:
normally a reboot would be required after adding a new project to the CVS
line in %etc%\inetd.lst, as to some unknown reason the CVS port is being
kept in use and on restart of the inetd CVS would be unavailable, once
CVS had been called via inetd before.
internet super daemon (inetd) seems to have a line limit of about 127
characters when reading %etc%\inetd.lst :-(.
When your server shall host several archives at a time, you quickly will
exceed this limit. By calling a spearate program, CMD.EXE and not
INETD.EXE has to deal with the long command line - obviously without any
problems so far.
ΓòÉΓòÉΓòÉ 1.5.4.2. %ETC%\services ΓòÉΓòÉΓòÉ
%etc%\services
This file contains the numbers and symbolic names of TCP/IP. If the CVS port
with the number 2401 is not already included, cvsenv will add it by using the
symbolic name cvspserver.
ΓòÉΓòÉΓòÉ 1.5.4.3. %ETC%\inetd.lst ΓòÉΓòÉΓòÉ
This file contains the TCP/IP services, that are being autostarted by the
internet super daemon (inetd). If CVS is not already included here, cvsenv will
add it here. This is especially important, because after each use of the
TCP/IP configuration program, where you save the configuration data, this file
is completely overwritten and all entries, that are not known to the TCP/IP
configuration program (like CVS) are deleted. In these cases, just run the
$CONFIG command again.
Note:
cvsenv will use the service name, that is specified within
%etc%\services. If you have added a different name than cvspserver to
%etc%\services, cvsenv will use your symbolic name when adding CVS to
%etc%\inetd.lst.
Instead of adding a line, that calls CVS directly, cvsenv will rewrite
the CVS service program, which in turn calls CVS.
ΓòÉΓòÉΓòÉ 1.5.4.4. TCPSTART.CMD ΓòÉΓòÉΓòÉ
This file contains the calls, that autostarts activated TCP/IP services during
system startup. For runnig a CVS service the internet super daemon (inetd) is
required.
If inetd is configured not to be autostarted, the appropriate lines are
preceeded by REM commands. If this is still the case, cvsenv simply removes
these REM commands and thus activates the autostart feature.
Note:
You need to restart TCP/IP in order to activate the changes by executing
the following command within an OS/2 window or fullscreen:
tcpstart
If an instance of the internet super daemon (inetd) is already running,
you will have to close this session first, before you run the tcpstart
command. Otherwise, the new instance of inetd cannot properly be started
and the CVS service will be unavailable.
ΓòÉΓòÉΓòÉ 1.5.4.5. archives.lst ΓòÉΓòÉΓòÉ
When you run the configuration command after having setup some archives, cvsenv
will create this file, which is used by the OS/2 Netlabs Open Source Archive
Client.
This file will only enlist the public archives (not containing
CVSROOT\readers). Private archives are enlisted in private.lst.
ΓòÉΓòÉΓòÉ 1.5.4.6. private.lst ΓòÉΓòÉΓòÉ
When you run the configuration command, and at least one of the archives is
private (containing CVSROOT\readers), cvsenv will create this file.
Public archives are enlisted in archives.lst.
ΓòÉΓòÉΓòÉ 1.5.5. The userid/password synchronization program ΓòÉΓòÉΓòÉ
Users should be able to use the same userid/password combination for all of the
archives being hosted by the OS/2 Netlabs Open Source Archive server.
This can only be achieved by keeping the CVSROOT\passwd files in the archive
trees of all archives equal. Normally, you would maintain all these files
separately with cvspw.exe of the CVS package, or would have to copy one of the
CVSROOT\passwd files to the archive trees of all archives manually.
Instead the OS/2 Netlabs Open Source Archive Administrator comes with the
password utility nosapw.cmd, which accepts all valid parameters of cvspw.exe,
but extends it in the following ways:
nosapw maintains only one passwd file, namely one in the OS/2 Netlabs
Open Source Archive Administrator program directory. If this changes
during a nosapw operation, it is automatically distributed to the CVSROOT
directory in the archive tree of all archives, thus keeping all
user/password conbinations of all archives in sync.
a new option -query allows to query, wether a user is already being
defined in the passwd file in the OS/2 Netlabs Open Source Archive
Administrator program directory.
Note:
execute nosapw without parameters to get a brief online help
ΓòÉΓòÉΓòÉ 1.5.6. The security program ΓòÉΓòÉΓòÉ
The security program of the OS/2 Netlabs Open Source Archive Administrator will
check, wether a commit or tag operation is allowed for the user performing it.
Note:
This program is to be called by the CVS service only and automatically
activated, when you secure an archive. By doing this, several files are
beind modified within the archive, wich in turn activates the automatic
useage of the security program.
It requires, that the file CVSROOT\writeinfo is properly customized, as
this holds the access information per directory within the archive.
Directories not heing exlicitely listed in writeinfo inherit their
security information from their parent directory.
It writes the file CVSROOT\writeinfo.log on the server, where each
successful and unsuccessful pre-commit and pre-tag check is recorded.
ΓòÉΓòÉΓòÉ 1.5.7. Modified files ΓòÉΓòÉΓòÉ
The following files are created or modified, when you secure an archive:
CVSROOT\passwd
CVSROOT\writers
CVSROOT\checkoutlist
CVSROOT\commitinfo
CVSROOT\taginfo
CVSROOT\writeinfo
CVSROOT\writeinfo.log
See also
Using the NOSA security
Security levels
ΓòÉΓòÉΓòÉ 1.5.7.1. CVSROOT\passwd ΓòÉΓòÉΓòÉ
This file contains both userids and encrypted password for each user, that may
login to the archive. It does not exist in a working directory tree, instead it
has to be placed into the archive directory tree of an archive, where CVSROOT
holds the archive administrative database of an archive.
If you secure your archive with the OS/2 Netlabs Open Source Archive
Administrator security feature, it will initially create this file with two
accounts:
the account for the administrator. You are prompted twice for a password,
that is being used here.
a guest account with the password readonly
Note:
Unlike all other files in the CVSROOT directory, you cannot modify this
file remotely, but only directly on the server, as this file is not to be
added to the archive!
Execute nosapw without parameters to get help for how to customize the
CVSROOT\passwd file for all archives at once.
See also
CVSROOT\writers
Using the NOSA security
Security levels
ΓòÉΓòÉΓòÉ 1.5.7.2. CVSROOT\writers ΓòÉΓòÉΓòÉ
This file contains the user ids of all, who may write to the archive.
If you secure your archive with the OS/2 Netlabs Open Source Archive
Administrator security feature, it will initially create this file only with
your user id in it.
Note:
If you want to allow more users to make modifications, you have to add
their user ids to this file (one per line). Do not include a password
here, you have to customize the login account in CVSROOT\passwd.
You can modify this file remotely.
See also
CVSROOT\passwd
Using the NOSA security
Security levels
ΓòÉΓòÉΓòÉ 1.5.7.3. CVSROOT\checkoutlist ΓòÉΓòÉΓòÉ
This file contains the names of the files, that are added to the standard file
list of the administrative database in the CVSROOT directory. As we are adding
a new file to this database, we will have to extend this file.
Whenever one commits changes to files in the CVSROOT directory, CVS needs to
checkout the changed files also on the server to make them available for the
server process. For this, CVS needs to know from CVSROOT\checkoutlist, what
files beside the standard files need this treatment, too.
If you secure your archive with the OS/2 Netlabs Open Source Archive
Administrator security feature, it will add the file CVSROOT\writeinfo to this
file to make sure, that this file is available for the security program on the
server.
Note:
You will not have to modify that file further, unless you plan to add
more files to the administrative database
See also
CVSROOT\writeinfo
Using the NOSA security
Security levels
ΓòÉΓòÉΓòÉ 1.5.7.4. CVSROOT\commitinfo ΓòÉΓòÉΓòÉ
This file contains the names of the filter programs, that are to be executed
before a commit operation is allowed within the archive.
If you secure your archive with the OS/2 Netlabs Open Source Archive
Administrator security feature, it will add the security program to this file,
making sure that this program is called before allowing commit operations
within the archive.
Note:
You will not have to modify that file further, unless you want to add
more filter programs for pre-commit checks.
See also
CVSROOT\writeinfo
The security program
Using the NOSA security
Security levels
ΓòÉΓòÉΓòÉ 1.5.7.5. CVSROOT\taginfo ΓòÉΓòÉΓòÉ
This file contains the names of the filter programs, that are to be executed
before a tag operation is allowed within the archive.
If you secure your archive with the OS/2 Netlabs Open Source Archive
Administrator security feature, it will add the security program to this file,
making sure that this program is called before allowing tag operations within
the archive.
More, only the archive administrator (having write access to CVSROOT) can set
tags with any name. All other writers are forced to preceed the tagname by
their userid and underscore, if they want to tag files.
Note:
You will not have to modify that file further, unless you want to add
more filter programs for pre-tag checks.
See also
CVSROOT\writeinfo
The security program
Using the NOSA security
Security levels
ΓòÉΓòÉΓòÉ 1.5.7.6. CVSROOT\writeinfo ΓòÉΓòÉΓòÉ
This file is created by the OS/2 Netlabs Open Source Archive Administrator,
when you secure your archive.
It extends the archive administrative database in the CVSROOT directory and is
used by the by the security program on the server side. Both parts together
implement access restrictions to each directory within an archive by using the
pre-commit check and pre-tag check feature of CVS.
One line is required for each archive directory in this file, for that you want
to set up access restrictions. Directories, that are not exlicitely listed in
writeinfo, possibly because they are being created later, inherit their
security information from their parent directory, as long as the administrator
does not manually add a line to writeinfo for such directory.
As a minimum only a line for the rootdirectory (/) is required, although it is
highly recomended to have at least also a line for the /CVSROOT directory
included in order to protect the administrative database of the archive from
unwanted write access.
Each line contains the following:
the pathname of the directory relative to %CVSROOT% (no blanks allowed in
directorynames !!!)
a list of the ids of those users, that may perform commit and tag
operation within that directory. If the id list contains a "*", all
users, that may write to the archive, may also write to that directory.
If you secure your archive with the OS/2 Netlabs Open Source Archive
Administrator security feature:
it will initially create this file with all directories currently
existing in the archive and allowing all writers to access all
directories except for CVSROOT, which is allowed to write only for you as
the administrator.
Note:
all users having write access to CVSROOT are considered to be archive
administrators. They can set tags with any name, while all other other
writers are forced to preceed the tagname by their userid and underscore,
if they want to tag files.
See also
CVSROOT\commitinfo
CVSROOT\taginfo
CVSROOT\checkoutlist
Using the NOSA security
Security levels
ΓòÉΓòÉΓòÉ 1.5.7.7. CVSROOT\writeinfo.log ΓòÉΓòÉΓòÉ
This file is written on the server side, and it contains one line for each
pre-commit and pre-tag check, that has been processed by the security program.
Note:
You can deactivate logging by simply deleting or renaming this file and
reactivate it by recreating it or renaming it back.
See also
CVSROOT\writeinfo
The security program
Using the NOSA security
Security levels
ΓòÉΓòÉΓòÉ 1.5.8. Using the administrator package on the commandline ΓòÉΓòÉΓòÉ
As the administrator package has to run on the machine, where the OS/2 Netlabs
Open Source Archive resides, you mostly will use the programs of the OS/2
Netlabs Open Source Archive Administrator through a telnet or shell and cannot
make use of Workplace Shell folders and objects.
Therefore you will have to know, how you can perform all actions via
commandline. All actions are performed by calling the program cvsenv with
the name of an archive directory and
optionally an action to be taken onto the archive.
Select one of the following topics:
setup the CVS environment
Initialize a new archive
Reinitialize a new archive
Edit an archive comment
restrict an archive to private access
Import zip files with source
Secure archive
Create snapshot
Create backup
List current archives
Clear working directory
Generate a changelog
Configure CVS service
Change to the working directory of an archive
Change to the tree root of an archive
Change to the NOSAADM program directory
ΓòÉΓòÉΓòÉ 1.5.8.1. setup the CVS environment ΓòÉΓòÉΓòÉ
Execute
cvsenv archive_dirname
within a shell in order to setup the environment variables for access to the
specified CVS archive and to change to the working directory of the project.
Note:
the specified archive must exist
By specifiying different archive names on consecutive calls, you can
switch between archives. This applies to all cvsenv commands, no matter
what action you also specify.
ΓòÉΓòÉΓòÉ 1.5.8.2. Initialize a new archive ΓòÉΓòÉΓòÉ
Execute
cvsenv archive_dirname $INIT
within a shell in order to initialize a new CVS archive.
During initialization, you are prompted for an archive comment. This comment
is being stored in the file CVSROOT\projectinfo in the archive directory and
not checked in, so it cannot be checked out into a working directory.
This comment is being written into archives.lst, when you run the
configuration command. This file in turn is being used by the OS/2 Netlabs
Open Source Archive Client, displaying this comment in folder title names. You
can modify this comment at every time using the comment command.
Note:
With the current version of the OS/2 Netlabs Open Source Archive
Administrator, the name of an archive directory MAY NOT CONTAIN BLANKS
!!!
The name of the base directory of an archive may not start with a ! or ?.
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
if the archive directory already exists, cvsenv skips the initialization
of the archive in order to prevent any data loss.
After initialization, the archive is in an empty, unsecured and public
state.
ΓòÉΓòÉΓòÉ 1.5.8.3. Reinitialize a new archive ΓòÉΓòÉΓòÉ
Execute
cvsenv [archive_dirname] $REINIT
within a shell in order to reinitialize an existing CVS archive to an empty
state and unsecured state.
Warning:
This call deletes the contents of the specified archive WITHOUT ANY
SECURITY PROMPT ! All files in both the archive and the working directory
are completely deleted.
After deletion, the archive is initialized again to an empty and
unsecured state
Note:
The specification of archive_dirname is optional, if you have already
setup the environment with cvsenv archive_dirname in that shell before.
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
ΓòÉΓòÉΓòÉ 1.5.8.4. Edit an archive comment ΓòÉΓòÉΓòÉ
Execute
cvsenv [archive_dirname] $COMMENT [comment]
within a shell in order to set the comment for an archive.
If you do not specify a comment text with this command, you are prompted for
one.
This comment is being stored in the file CVSROOT\projectinfo in the archive
directory and not checked in, so it cannot be checked out into a working
directory.
This comment is being written into archives.lst, when you run the
configuration command. This file in turn is being used by the OS/2 Netlabs
Open Source Archive Client, displaying this comment in folder title names. You
can modify this comment at every time using the comment command.
Note:
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
ΓòÉΓòÉΓòÉ 1.5.8.5. restrict an archive to private access ΓòÉΓòÉΓòÉ
Execute
cvsenv [archive_dirname] $PRIVATE
within a shell in order to restrict an archive to private access. This is
being achieved by adding the file CVSROOT\readers to the archive.
Note:
At first, your user id is bein gadded to this file, so that after running
this command, you are the only one who can read from this archive. All
other users currently being defined in the passwd file in the OS/2
Netlabs Open Source Archive Administrator program directory, are also
added, but with a preceeding semicolon, thus inactivating these entries.
Just remove the semicolon from a line to let a project member read from
the archive.
In order to make an archive public again, simply remove the file
CVSROOT\readers from the archive.
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
ΓòÉΓòÉΓòÉ 1.5.8.6. Import zip files with source ΓòÉΓòÉΓòÉ
Execute
cvsenv [archive_dirname] $IMPORT
within a shell in order to import sources from a source zip file.
Note:
The specification of archive_dirname is optional, if you have already
setup the environment with cvsenv archive_dirname in that shell before.
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
The working directory has to be completely empty for this, otherwise
cvsenv will abort the import. cvsenv needs an empty directory, but will
not delete any files within it itself, because uncommitted data changes
may be destroyed.
If you are sure, that you have committed all changes (if any) to the CVS
archive, you can use the "Clear working directory" feature of cvsenv
before performing an import again.
ΓòÉΓòÉΓòÉ 1.5.8.7. Secure archive ΓòÉΓòÉΓòÉ
Execute
cvsenv [archive_dirname] $SECURE
within a shell in order to add commit and tag security to the archive. If you
use an archive only for use on your own computer and will not allow others to
access it, you may not need to secure this archive.
See section
Modified files
in order to find out how your archive is secured.
Note:
Read the VERY IMPORTANT section Using the NOSA security, if you allow
others to use a CVS service on your computer !
The specification of archive_dirname is optional, if you have already
setup the environment with cvsenv archive_dirname in that shell before.
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
several files are changed for to add security. For all changes cvsenv
checks, wether the change has already been applied to the archive, and if
so, does not perform it again.
See also
Modified files
ΓòÉΓòÉΓòÉ 1.5.8.8. Create snapshot ΓòÉΓòÉΓòÉ
Execute
cvsenv [archive_dirname] $SNAPSHOT [tagname]
within a shell in order to create a snaptshot zip file. You can specify tag
name in order to create a snapshot of a certain build.
Note:
The specification of archive_dirname is optional, if you have already
setup the environment with cvsenv archive_dirname in that shell before.
If you specify a tagname, only these files are included in the snapshot
zip file, that have this tagname. All other files are ignored.
The zip file is created in the subdirectory <archive_dirname> of the root
directory for snapshot zipfiles, that you specified within the
installation program.
The filename of the zip file consists of the <archive_dirname> and a
timestamp.
The complete pathname of the zip file is as follows :
(CVS_SNAPSHOTROOT)\<archive_dirname>\<archive_dirname>_yyyymmdd.zip
where
- <archive_dirname> is the name of the archive directory
- yyyymmdd represents the current date
Example:
d:\netlabs.snap\odin32\odin32_19990515.zip
Note:
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
ΓòÉΓòÉΓòÉ 1.5.8.9. Create backup ΓòÉΓòÉΓòÉ
Execute
cvsenv [archive_dirname] $BACKUP
within a shell in order to create a backup zip file of the archive.
Note:
The specification of archive_dirname is optional, if you have already
setup the environment with cvsenv archive_dirname in that shell before.
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
The zip file is created in the subdirectory <archive_dirname> of the root
directory for backup zipfiles, that you specified within the installation
program.
The filename of the zip file consists of a timestamp.
The complete pathname of the zip file is as follows :
(CVS_BACKUPROOT)\<archive_dirname>\yyyymmddhhmmss.zip
where
- <archive_dirname> is the name of the archive directory
- yyyymmddhhmmss represents the current date and time of the backup
Example:
d:\netlabs.bak\odin32\19990515172509.zip
ΓòÉΓòÉΓòÉ 1.5.8.10. List current archives ΓòÉΓòÉΓòÉ
Execute
cvsenv $LIST
within a shell in order to display a list of all currently defined archives.
For each archive a status is being displayed, wether this archive is public
(e.g. all have read access) or it is private (read access restricted by a
readers list).
Note:
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
ΓòÉΓòÉΓòÉ 1.5.8.11. Clear working directory ΓòÉΓòÉΓòÉ
Execute
cvsenv [archive_dirname] $CLEARWORK
within a shell in order to clear a working directory for an existing CVS
archive.
Warning:
This call deletes the contents of the working directory WITHOUT ANY
SECURITY PROMPT ! Make sure that you have committed all changes to the
archive before doing so.
Note:
The specification of archive_dirname is optional, if you have already
setup the environment with cvsenv archive_dirname in that shell before.
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
ΓòÉΓòÉΓòÉ 1.5.8.12. Generate a changelog ΓòÉΓòÉΓòÉ
Execute
cvsenv [archive_dirname] $GENLOG [outputfile]
within a shell in order to create or to continue a changelog for an existing
CVS archive.
Note:
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
The default output file is changelog.txt in the current directory.
The filename for the output file may not contain blanks.
Do not modify the first lines of the output file, because they are read
the next time in order to determine the time range for the cvs log
command.
The working directory is updated to the current contents of the archive.
This is required in order to get a correct output from the cvs log
command.
Configure the full names of the archive writers in the the fullnames list
file, otherwise only the userids are included in the changelog.
See also
Generating a changelog
The fullnames list file
samples\fullnames.lst
ΓòÉΓòÉΓòÉ 1.5.8.13. Configure CVS service ΓòÉΓòÉΓòÉ
Execute
cvsenv $CONFIG
within a shell in order to modify your TCP/IP configuration to support and
autostart the CVS service.
Warning:
You need to use this command, whenever you modify the Autostart section
within the TCP/IP configuration program, because this program will
discard any information from %etc%\inetd.lst about services not coming
with the TCP/IP software itself ! OTHERWISE YOUR CVS SERVICE WILL BE
INACTIVE !
Note:
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
After having added new archives or deleted obsolete ones, run this
command update the current CVS service program.
See also
Configuring TCP/IP and CVS service
Modified files
ΓòÉΓòÉΓòÉ 1.5.8.14. Change to the working directory of an archive ΓòÉΓòÉΓòÉ
Execute
cvsenv $WORK
within a shell in order to change to the root of the working directory of the
current archive. This is identical with executing
cvsenv archive_dirname
with the name of the current archive.
Note:
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
See also
Change to the tree root of an archive
Change to the NOSAADM program directory
ΓòÉΓòÉΓòÉ 1.5.8.15. Change to the tree root of an archive ΓòÉΓòÉΓòÉ
Execute
cvsenv $ARCHIVE
within a shell in order to change to the root of an archive directory tree of
the current project archive. There you might want to check the files in the
archive administrative database in the directory CVSROOT, for example the
passwd file.
Note:
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
See also
Change to the working directory of an archive
Change to the NOSAADM program directory
Using the NOSA security
Security levels
ΓòÉΓòÉΓòÉ 1.5.8.16. Change to the NOSAADM program directory ΓòÉΓòÉΓòÉ
Execute
cvsenv $BIN
within a shell in order to change to the program directory of the OS/2 Netlabs
Open Source Archive Administrator. There you want might to check the current
CVS service program, which is to be updated by the config command of cvsenv,
or the fullnames list file, which is being used to generate a changelog.
Note:
You can abbreviate the command name. It depends on the command, how many
letters are required for this command. Execute
cvsenv /?
in order to get more information on the command names and the valid
abbreviations.
See also
Change to the working directory of an archive
Change to the tree root of an archive
ΓòÉΓòÉΓòÉ 1.5.9. Generating a changelog ΓòÉΓòÉΓòÉ
The OS/2 Netlabs Open Source Archive Administrator can create a changelog out
of the cvs log output. This is done for all files within the archive either
from the begin or the archive or from the last point of time, when the
changelog file has been written, up to the current point of time.
Every time, when an existing changelog file is extended, the new entries are
prepended to the beginning of the old file. This way you can automatically
extend an existing changelog continuously by any scheduler.
Configure the full names of the archive writers in the the fullnames list file,
so that not only the userids appear in the changelog.
See also
Generate a changelog
The fullnames list file
samples\fullnames.lst
ΓòÉΓòÉΓòÉ 1.5.9.1. The fullnames list file ΓòÉΓòÉΓòÉ
The OS/2 Netlabs Open Source Archive Administrator can only determine the
userids of the writers out of the CVS log output. If you want to have the full
usernames (plus the email adresses) within the changelog instead, add this
information to the file fullnames.lst in the program directory of the OS/2
Netlabs Open Source Archive Administrator.
Each line of the file contains:
the userid
the fullname (in whatever format you like, e.g. with email address)
Note:
If a userid is not contained in this file, the plain userid is used
within the changelog instead of the fullname.
You can find a sample fullnames.lst file in the samples.lst subdirectory
within the OS/2 Netlabs Open Source Archive Administrator program
directory. Use the $BIN command of cvsenv in order to quickly change to
this directory.
all spaces between the userid and the fullname are discarded, so that you
can start all fullnames in the same column.
See the sample fullnames list file
samples\fullnames.lst
ΓòÉΓòÉΓòÉ 1.5.9.2. samples\fullnames.lst ΓòÉΓòÉΓòÉ
This is the sample fullnames list file:
ktk Adrian Gschwend <ktk@netlabs.org>
cla Christian Langanke <C.Langanke@TeamOS2.DE>
ΓòÉΓòÉΓòÉ 1.5.10. Using the administrator package locally with WPS ΓòÉΓòÉΓòÉ
While you mostly will access a CVS server via telnet and therefore cannot
access the admin package via Workplace Shell folders and objects, you may test
the admin package also on a machine, that you have local access to. There you
can use the The OS/2 Netlabs Open Source Archive Administrator folder for some
operation as well.
Select one of the following topics:
Refresh the administrator folder
Create new project archive
ΓòÉΓòÉΓòÉ 1.5.10.1. Refresh the administrator folder ΓòÉΓòÉΓòÉ
In order to refresh the The OS/2 Netlabs Open Source Archive Administrator
folder after having created or deleted an archive, perform the following steps:
open the OS/2 Netlabs Open Source Archive Administrator folder
execute the icon
Refresh this folder
See also
Create new project archive
ΓòÉΓòÉΓòÉ 1.5.10.2. Create new project archive ΓòÉΓòÉΓòÉ
In order to create a new archive, perform the following steps:
open the OS/2 Netlabs Open Source Archive Administrator folder
execute the icon
Create new project archive
specify the name of the archive directory (not the archive name, which
may be different !).
Warning:
With the current version of the OS/2 Netlabs Open Source Archive
Administrator, the name of an archive directory MAY NOT CONTAIN BLANKS
!!!
The name of the base directory of an archive may not start with a ! or ?.
See also
Refresh this folder
ΓòÉΓòÉΓòÉ 1.6. How can I ... ? ΓòÉΓòÉΓòÉ
Select one of the following topics:
How can I solve the 'Too many open files' problem ?
How can I secure an archive ?
How can I create a new archive ?
How can I add a new user to all archives ?
ΓòÉΓòÉΓòÉ 1.6.1. How can I solve the 'Too many open files' problem ? ΓòÉΓòÉΓòÉ
If CVS displays the message "To many open files", you must increase the default
file handle limit of the EMX Runtime.
In order to do so, add the following environment variable to your CONFIG.SYS:
SET EMXOPT=-c -n -h1024
where
-c disables core dumps caused by signals and exceptions (they are only
really useful if you use debug versions of a software).
-n Suppress popups for exceptions. As emx.dll displays an appropriate
error message, popups are not required.
-h1024 Set OS/2 file handle limit for CVS (and other EMX based programs)
to 1024, thus eliminating your current problem. The number must be
between 10 and 65536, possibly CVS will also run with a smaller
value.
See also the file doc\emxrt.doc of the EMX Runtime for further details on
values of the EMXOPT environment variable.
ΓòÉΓòÉΓòÉ 1.6.2. How can I create a new archive ? ΓòÉΓòÉΓòÉ
In order to create a new archive, you have to perform the following actions:
initialize the new archive. If it already exists, and you want to replace
an existing archive, reinitialize the existing archive instead.
import the existing source, if any.
secure the archive. See section
Modified files in order to find out how your archive is secured.
ΓòÉΓòÉΓòÉ 1.6.3. How can I secure an archive ? ΓòÉΓòÉΓòÉ
See sections
Using the NOSA security
Security levels
Secure archive
for more information on how to implement access restrictions to an existing
archive.
ΓòÉΓòÉΓòÉ 1.6.4. How can I add a new user to all archives ? ΓòÉΓòÉΓòÉ
In order to add a new user or change an existing user to/in all archives at
once, simply do not use cswps to maintain the CVSROOT\passwd file. If you would
use cvspw (coming with CVS), you would have to make either
the change to all archives one after another or
make the change to one archive and then distibute the resulting
CVSROOT\passwd file to all archive trees.
Instead, use the userid/password synchronization program nosapw to let the
OS/2 Netlabs Open Source Archive Administrator do the distribution job. For
that, a main passwd file is being kept in the program directory of the OS/2
Netlabs Open Source Archive Administrator. If this changes during a nosapw
operation, it is distributed automatically to all archive trees.
Note:
execute nosapw without parameters to get a brief online help
ΓòÉΓòÉΓòÉ 1.7. Limitations ΓòÉΓòÉΓòÉ
The following limitations apply to the current version of OS/2 Netlabs Open
Source Archive Administrator:
The name of the base directory of an archive may not start with a ! or ?.
directory names of and within CVS archives may currently not include
blanks. However this restriction does not exist for filenames.
output filenames for changelogs may not contain blanks.
This packages is available only in english. This is due to the reason,
that programmers mostly understand english and that development tools,
such as the required Concurrent Versions System (CVS) are also only
available in english.
When users import new directories, they will not be able to add files to
it, because this requires to add the directory to CVSROOT\writeinfo by
the administrator.
ΓòÉΓòÉΓòÉ 1.8. Revision history ΓòÉΓòÉΓòÉ
Select one of the following topics:
file_id.diz
Version 1.07
Version 1.06
Version 1.05
Version 1.04
ΓòÉΓòÉΓòÉ 1.8.1. file_id.diz ΓòÉΓòÉΓòÉ
(v1.07) NOSA Administrator - FREEWARE
The "OS/2 Netlabs Open Source Archive
Administrator" enables you to setup CVS
archives with a handful of batch commands.
NOSAADM takes care of setup of CVS,
initializing new archives, importing zip
files, adding keyword lines ($Id$) to all
known file types and adding security.
NOSAADM homepage: www.netlabs.org/nosa
Author: C.Langanke@TeamOS2.de
ΓòÉΓòÉΓòÉ 1.8.2. Version 1.07 ΓòÉΓòÉΓòÉ
New:
added new sections to this book about the EMX Runtime, wich is a
prerequisite for the Concurrent Versions System (CVS).
See
- EMX Runtime
- Prerequisites
- How can I solve the 'Too many open files' problem ?
You do not longer need to write the cvsenv commands in uppercase. More,
you can use abbreviations, mostly with only one letter behind the dollar
sign (e.g. $L or $list instead odf $LIST).
Take care though, where two commands start with the same letter: in order
to distinct between such commands, you may have to specify more than one
letter of the command name. Execute
cvsenv /?
in order to get an overview of all commands.
Fixed:
The $COMMENT command now queries the old comment of the project.
The OS/2 Netlabs Open Source Archive Administrator can now use also a
project definition not containing a comment. Previously, such project was
simply ignored.
when creating a backup from an archive, directories are now also stored
within an archive (removed switch -D).
fixed a bug in the $INIT command. In some cases you needed to
(re)initialize a new archive twice.
The CVS service program is now deleted, if you run the $CONFIG command
and no archive is present.
The CVS service program from now on is written as a plain batch file.
(REXX seems to have a problem with literals longer than 256 chars :-( ).
Doing this the current limit for the commandline of the CVS server is
1000 characters (either implied by CVS.EXE or CMD.EXE), wich leads to a
practical limit of 15 to 25 projects per server.
ΓòÉΓòÉΓòÉ 1.8.3. Version 1.06 ΓòÉΓòÉΓòÉ
New:
added new sections to this book about configuration of TCP/IP and the CVS
service. See
- Configuring TCP/IP and CVS service
- Modified files
Especially new is that the following files are generated during the
configuration:
- archives.lst
- private.lst
added a new cvsenv command for setting a comment for an archive on the
commandline:
- $COMMENT - Edit an archive comment
Archive comments are being written either to the private.lst or the
private.lst (depending on the privacy status of the archive), when you
run the config command.
the installation program now also prompts for the hsotname of the OS/2
Netlabs Open Source Archive server. This hostname is being written into
archives.lst and/or private.lst, which in turn are being used by the OS/2
Netlabs Open Source Archive Client.
added a new cvsenv command for listing the currently defined archives: on
the commandline:
- $LIST - List current archives
added a new cvsenv command for restricting an archive to private access
on the commandline:
- $PRIVATE - restrict an archive to private access
Added the userid/password synchronization program in order to have an
easy way to set up the users for all archives across one server. Just use
nosapw instead ov cvspw, and all CVSROOT\passwd files are kept in sync.
See also
- How can I add a new user to all archives ?
added two new cvsenv commands for easier change between directories on
the commandline:
- $WORK - Change to the working directory of an archive
- $ARCHIVE - Change to the tree root of an archive
- $BIN - Change to the NOSAADM program directory
removed the obsolete cvsenv command $RECONFIG for reconfiguration of the
CVS service. This is not longer required, since cvsenv now uses a
separate service program to maintain the list of hosted archives.
See also
- Configuring TCP/IP and CVS service
- Configure CVS service
Added contents to pages
- OS/2 Netlabs Open Source Archive Administrator
- Overview
Fixed:
fixed several bugs in the program fo generating a changelog.
fixed a bug in the security program, preventing the correct determination
of access rights, if the only directories in CVSROOT\writeinfo are / and
CVSROOT.
added information about a limitation: The name of the base directory of
an archive may not start with a ! or ?.
ΓòÉΓòÉΓòÉ 1.8.4. Version 1.05 ΓòÉΓòÉΓòÉ
New:
enhanced the security program:
CVSROOT\writeinfo does not longer need to contain all directories of the
archive. If new directories are being created in that archive, they
implicitely inherit the access rights from its parent directory.
The specification of archive_dirname is now optional for most cvsenv
commands, if you have setup the environment with
cvsenv archive_dirname
before.
implemented a new cvsenv command for generating a changelog.
added a cvswrappers file for the initialization of a new archive. This
file implements wrappers, that disables keyword substitution for all
sorts of binary files.
fixed a bug in this file:
replaced all cvswps with cvsenv (as it should be).
enhancements/modifications to this book
- added sections to the How can I ... ? section.
- rearranged the Usage section: Security comes first !
- reworked all security sections in the Usage section. Please read
them !
Implemented a new cvsenv command for reconfiguration of the CVS service,
which rewrites the CVS information in the %etc%\inetd.lst with the actual
existing archives.
Fixed:
fixed an error within the configuration of the CVS service:
in certain situations tcpstart.cmd could not be found.
ΓòÉΓòÉΓòÉ 1.8.5. Version 1.04 ΓòÉΓòÉΓòÉ
First public release
ΓòÉΓòÉΓòÉ 1.9. Trademarks ΓòÉΓòÉΓòÉ
The following trademarks are used in this online help file:
OS/2 is a trademark of IBM Corporation.
ΓòÉΓòÉΓòÉ 1.10. Credits ΓòÉΓòÉΓòÉ
Select one of the following topics:
General credits
ΓòÉΓòÉΓòÉ 1.10.1. General credits ΓòÉΓòÉΓòÉ
Credits go to:
all people having helped the development of this program.
all developers, who share and who will share their code through the OS/2
Netlabs Open Source Archive. You all help the current and wannabe
developers of the OS/2 community building better code, participating
within internet projects and bringing OS/2 forward with new programs,
that we all need.
all developers being ivolved in making
- Concurrent Versions System (CVS)
- Info-Zip
Without these programs, the OS/2 Netlabs Open Source Archive would not
have been possible.