=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/Attic/ctm.html,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- www/Attic/ctm.html 2001/10/16 19:02:21 1.18 +++ www/Attic/ctm.html 2001/11/02 21:17:19 1.19 @@ -9,19 +9,23 @@ -
CTM is a system which was designed by Poul-Henning Kamp for making -changes to a source tree available on a daily basis by email. +changes to a source tree available on a regular basis by email. This is a good way to stay up to date with the current source tree or CVS repository if you have a slow Internet connection, for instance via modem.
+OpenBSD CTM distributes all modules of the OpenBSD CVS repository +plus checked out versions of several of theses modules. CTM uses very low bandwidth for distributing the changes to the tree, and compresses them using gzip -9. In contrast to CVSup, CTM is written in plain C language and therefore available for every platform supported by OpenBSD. +CTM implements a so called push system, while all other methods to +get access to the OpenBSD CVS repository are pull systems.
For any problems, suggestions, reports and questions regarding CTM, @@ -30,11 +34,11 @@ (Please do not ask other OpenBSD people for CTM support, as they are busy doing other things. Thank you.) -
The basic idea of CTM is that you subscribe to a special mailing list -for a particular source tree. Each day you receive an email message +for a particular CVS module or source tree. Each day you receive email messages containing all the changes to that tree during that period. One such set of differences is called a delta. Actually, the CTM server makes new deltas every twelve hours. @@ -53,7 +57,7 @@
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 +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 @@ -62,19 +66,19 @@ would be named OpenBSD-cvs.1500A.gz. See below for detailed instructions. -
You obtain the base set and all relative deltas up to the recent one via ftp from the sites listed below. Sizes are:
The following commands will subscribe you to the appropriate lists:
-For the CVS repository (without the X11 and XF4 modules): +For the CVS repository (CVSROOT, ports, src and www modules, +but not X11 and XF4):
echo subscribe OpenBSD-cvs | mail majordomo@OpenBSD.org@@ -108,15 +113,19 @@
echo subscribe OpenBSD-cvs-x11 | mail majordomo@OpenBSD.org-For the source tree (without the X11 and XF4 modules): +For the XF4 module of the CVS repository:
+ echo subscribe OpenBSD-cvs-xf4 | mail majordomo@OpenBSD.org ++For a checked out copy of the src module: +
echo subscribe OpenBSD-src | mail majordomo@OpenBSD.org-For the X11 module of the source tree: +For a checked out copy of the X11 module:
echo subscribe OpenBSD-src-x11 | mail majordomo@OpenBSD.org-For the ports tree: +For a checked out copy of the ports module:
echo subscribe OpenBSD-ports-ctm | mail majordomo@OpenBSD.org@@ -125,9 +134,6 @@ echo subscribe ctm-log | mail majordomo@OpenBSD.org -There is no mailing list for the XF4 module, yet. It is available -via FTP only. -
- cat split/OpenBSD-cvs.1500.tar.gz.* > OpenBSD-cvs.1500.tar.gz + cat split/OpenBSD-cvs.1450.tar.gz.* > OpenBSD-cvs.1450.tar.gz cd target - tar -xzvf .../OpenBSD-cvs.1500.tar.gz + tar -xzvf .../OpenBSD-cvs.1450.tar.gz
@@ -171,7 +177,7 @@
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. +mailing list. If you like, you can automate this step using procmail, +maildrop, or any similar program from the +ports collection.
-The addresses of the FTP servers carrying CTM deltas are: +Here is the list of FTP servers carrying CTM deltas:
This server is updated by CTM deltas received from the mailing lists. It additionally has the split base deltas in the base -subdirectory. +subdirectory, mirrored from + + ftp://openbsd.rug.ac.be:/pub/OpenBSD-ctm/ +.
-
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 +the better choice is surely 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 +from your CVS repository then, can track a stable branch, +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. +You can also use the full range of CVS commands except commands like +cvs commit and cvs tag.
The drawback, however, is the amount of diskspace it takes. A -checked-out source tree takes about 350MB or so, but if you have your +checked-out source tree takes about 370MB or so, but if you have your own CVS repository you need more than 1Gb for it, plus another -350MB for the checked out tree. +370MB for the checked out tree. This doesn't count the 100MB or more (depending on the architecture) -you will need to do a build, i.e. compile the sources. +you will need for generated files during a build, i.e. compiling the sources.
If you just get the source tree, you will need to deal with local @@ -319,8 +330,8 @@
The commands ls -W and rm -W will be -useful too, as objects named "whiteouts" in /usr/src will also hide -files in src-ctm. +useful too, as objects named "whiteouts" in /usr/src +will also hide files in src-ctm.
If you get the CVS repository, you can use the cvs checkout @@ -332,7 +343,7 @@ To get an initial src repository:
cd /usr - cvs -qd YOUR_CVS_REPOSITORY checkout -A src + cvs -qd YOUR_CVS_REPOSITORY checkout -PA src
and after each CTM update: @@ -341,12 +352,12 @@ cvs -q update -PAd -
-
-Important notes and announcements about CTM will be posted to: -
-