If you don't know SCCS, you probably thought it was hard to learn. Not true. Here is a simple introduction to SCCS.
That's it. You're done. There are three more commands you need to know:
You may also want to add the following to your list of:
The get command will get a copy of the file from the Source Code Control System. The file will be . If you want to edit the file, use the edit command. Once you are done, return the file to the SCCS directory with the command delta . Each time you store the file, you'll get a new version number, or "delta."
That's all there is to it! If you are not using SCCS, you should. It is the best way to protect yourself. It does not require dozens of tapes.
It is much easier to just type:
One command, and version 1.12 is restored. If it's not the right one, restore the version before or after the one you just grabbed. If you are worried that you are keeping 12 versions of the file on the disk, and that this will use up a lot of disk space, don't. SCCS stores the differences in a clever manner that allows it to recover any version of the file in a single pass through the file.
Suppose you delete a file by accident? Well, if the file is just checked out with a get , it will be retrieved and marked read-only, so deleting the file will cause rm to ask you for confirmation. If you do delete it, you can recover it with another get command. Suppose you check out a file with edit , because you planned to change it. Well, if this file gets deleted accidentally, you would lose the most recent changes. This is why you should check your files back into SCCS frequently - several times a day, if you wish. Do it whenever you make significant changes to the file, and it would be difficult to remember all of the changes. Making hundreds of changes to a file without checking it back into the system is just begging for trouble.