www@openbsd.org
! $OpenBSD: ctm.html,v 1.15 2001/04/02 00:00:56 naddy Exp $
! For any problems, suggestions, reports and questions regarding CTM contact the CTM maintainer Hans Günter Weigand. (Please do not ask other OpenBSD people for CTM support, --- 24,30 ---- and therefore available for every platform supported by OpenBSD.
! For any problems, suggestions, reports and questions regarding CTM, contact the CTM maintainer Hans Günter Weigand. (Please do not ask other OpenBSD people for CTM support, *************** *** 53,61 ****
There are currently two kinds of base set files. For quite a while we were making tar.gz files manually, but we are ! switching back to real CTM base deltas. The latter contain MD5 checksums and are generated automatically, thus are a bit safer. You ! can distinguish these two kinds of base set by their filename. An example for a tar.gz file is OpenBSD-cvs.1450.tar.gz, whereas a CTM base delta would be named OpenBSD-cvs.1500A.gz. See below for --- 53,62 ----
There are currently two kinds of base set files. For quite a while we were making tar.gz files manually, but we are ! switching back to real CTM base deltas. The latter contain ! md5(1) checksums and are generated automatically, thus are a bit safer. You ! can distinguish these two kinds of base sets by their filename. An example for a tar.gz file is OpenBSD-cvs.1450.tar.gz, whereas a CTM base delta would be named OpenBSD-cvs.1500A.gz. See below for *************** *** 206,212 ****
Repeat this last step every time you receive a delta from the ! mailing list. If you like you can automate this step using procmail or any similar program. --- 207,213 ----
Repeat this last step every time you receive a delta from the ! mailing list. If you like, you can automate this step using procmail or any similar program. *************** *** 265,275 ****
This depends on your diskspace, among other factors. Since CTM doesn't deal very well with files which have been modified locally, ! the "better" choice is probably the CVS repository. You can check out ! your working copy of the source tree from your CVS repository then, ! and keep your local modifications in your source tree. CVS is ! smart enough to merge in your local changes. You can also use the ! full range of CVS commands except cvs commit.
The drawback, however, is the amount of diskspace it takes. A --- 266,277 ----
This depends on your diskspace, among other factors. Since CTM doesn't deal very well with files which have been modified locally, ! the "better" choice is probably the CVS ! repository. You can check out your working copy of the source tree ! from your CVS repository then, and keep your local modifications in ! your source tree. CVS is smart enough to merge in your local changes. ! You can also use the full range of CVS commands except cvs ! commit.
The drawback, however, is the amount of diskspace it takes. A *************** *** 282,291 ****
If you just get the source tree, you will need to deal with local modifications. One way to do this is to use the union filesystem, ! although there have been reports that the union filesystem can be ! unstable if both the upper and lower layers reside on the same physical ! filesystem. If you place your upper and lower layers on separate filesystems ! you should have no problems. A sample of this is as follows:
Suppose your CTM-updated tree is in /usr/src-ctm, and --- 284,294 ----
If you just get the source tree, you will need to deal with local modifications. One way to do this is to use the union filesystem, ! (see mount_union(8)) ! although there have been reports that the union filesystem can be ! unstable if both the upper and lower layers reside on the same physical ! filesystem. If you place your upper and lower layers on separate ! filesystems you should have no problems. A sample of this is as follows:
Suppose your CTM-updated tree is in /usr/src-ctm, and *************** *** 358,364 **** second day the remaining 46, plus the first 4 messages of the following delta.
www@openbsd.org