To create an sccs archive of a source file foo.c, do
admin -ifoo.c s.foo.c
This creates the archive file s.foo.c and initialises it
with the current contents of your source file, foo.c. If you use
Emacs as your editor, you can just use C-x v i instead.
Another frequently-used option is ‘-b’, which indicates that the
file is to be treated as a binary file rather than as text. You might
want to do this because the file actually contains binary data, or just
characters that have other meanings within an sccs file, for
example ‘^A’, the character whose code is 1.
- Add user or group xxx to the list of those authorised to check
revisions in (that is, use
get -e and
must be specified by name and groups by numeric id.
This feature is often used in conjunction with a setuid installation of
sccs driver program (see sccs). This is not a good idea
because the cssc suite is not secure (see Known Problems).
- Ensure that the file is encoded as a binary file. This option only
works in conjunction with the
This option is not available if binary file support is turned off
(see Interoperability) though this can be re-enabled if necessary
with an environment variable (see Environment Variables).
- Delete flag F from the flags present in the file (see Flags).
admin -dl to unlock a release, you need to specify
which release should be unlocked. For example
unlocks all releases, while
admin -dl2 unlocks only release 2.
This means that
admin -dl will do nothing, since no release was
specified. If all releases are locked, attempting to unlock just one
release will have no effect.
- Erase the specified user or group from the list of those authorised to
check revisions in or out.
- Add the flag F (with optional value xxx) to the file's
flags (see Flags). For example, -fv/tmp/checkit sets the
MR-validation flag to /tmp/checkit.
- Check the sccs file. The exit value will be 0 if the file is
valid, and not 0 otherwise. The checks made are the same as those
val. Some problems with the sccs file may not be
Warning messages may be emitted, indicating things that may or may not
be wrong (e.g. time apparently going backwards), but if no actual errors
are encountered, the exit value will still be zero.
This option is silently incompatible with all the other options; the
specified sccs files will not be modified by
admin if the
-h flag is used.
- Initialise the sccs file with the contents of the file foo.
If no argument is given, read from standard input. This implies the
- When initialising a file, add the specified list of mr numbers
(see Modification Request Numbers) to the delta commentary for the
initial version. This list can be empty. The specified mrs are
validated according to the setting of the v flag, which should be
set (see Flags). If the v flag is set but has no value
(i.e. is set to the empty string), validation silently succeeds. If the
v flag is not set, the -m option causes
- Create a new sccs file. Unless -i is also used, the new
file will contain control information but the body will be initially
empty. Some versions of sccs require the -i option to
be specified if ‘-n’ is used. Therefore for greatest
portability, specify ‘-i/dev/null’ if you want an empty initial
- Set the initial release number to N. The initial level within
that release is always 1. Some versions of SCCS allow you to specify
actual an actual sid here (for example ‘1.2’ or
‘188.8.131.52’). cssc also allows this, but emits a warning. If
you use the -r option, you must also use the -i
option (not just the -n option). If the initial sid you
specify is not on the trunk, some tools will fail to work with the
resulting file. See also See SCCS Version Differences.
- Read in descriptive text for this file from desc. This replaces
any existing description. If no argument, remove any existing
description (this is illegal if -i or -n is used).
- Display version information.
- When initialising a file, set the comment for that delta to
adayada. If the option is given just as -y, the
comment is recorded as empty. The following word in the argument list
is not used as the comment. Note that this behaviour is different
to most Unix programs, but is the same as the behaviour of traditional
- Fix the checksum information. The sccs file is still validated
by CSSC; apart from possibly having an incorrect checksum, the s-file
must be valid. If you use this option on an sccs file which
really is invalid, then the attempt may fail or silently write
out a valid but incorrect file. This option does not work on
BitKeeper files. Use this option with extreme care.