09.06.2013 Views

Intel XENIX 286 Programmers Guide (86) - Tenox.tc

Intel XENIX 286 Programmers Guide (86) - Tenox.tc

Intel XENIX 286 Programmers Guide (86) - Tenox.tc

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SCCS: Source Code Control System <strong>XENIX</strong> Programming<br />

Locking a Version<br />

The lock flag, 1, lists by release number all versions in a given s-file that are locked<br />

against further editing. You can set the flag by using the -f flag of the admin command.<br />

The flag must be followed by one or more release numbers. Multiple release numbers<br />

must be separated by commas (,). For example, the command<br />

admin -fl3 s.demo.c<br />

locks all versions with release nu mber 3 against further editing. The command<br />

admin -fl4,5,9 s.def.h<br />

locks all versions with release numbers 4, 5, and 9.<br />

Note that the special symbol "a" may be used to specify all release numbers. The<br />

command<br />

admin -fla s.demo.c<br />

locks all versions in the file s.demo.c.<br />

Repairing sees Files<br />

SCCS carefully maintains all SCCS files, making damage to the files very rare. Damage<br />

can result from hardware malfunctions that cause incorrect information to be copied to<br />

the file. The following sections explain how to check for damage to SCCS files and how<br />

to repair the damage or regenerate the file.<br />

Checking an s-file<br />

You can check a file for damage using the -h option of the admin command. The option<br />

causes the checksum of the given s-file to be computed and compared with the existing<br />

sum. An s-file's checksum is an internal value computed from the sum of all bytes in<br />

the file. If the new and existing checksums are not equal, the command displays the<br />

message<br />

corrupted file (coG)<br />

indicating damage to the file. For example, the command<br />

admin -h s.demo.c<br />

checks the s-file s.demo.c for damage by generating a new checksum for the file and<br />

comparing the new sum with the existing sum.<br />

5-24

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!