www/ctm.html - diff

Return to ctm.html CVS log

Up to [local] / www

Diff for /www/Attic/ctm.html between version 1.15 and 1.16

version 1.15, 2001/04/02 00:00:56

version 1.16, 2001/04/06 14:08:21

Line 24

and therefore available for every platform supported by OpenBSD.

For any problems, suggestions, reports and questions regarding CTM

For any problems, suggestions, reports and questions regarding CTM,

contact the CTM maintainer

<a href="mailto:hgw@d1906.inka.de">Hans Günter Weigand</a>.

(Please do not ask other OpenBSD people for CTM support,

Line 53

There are currently two kinds of base set files. For quite a while we

were making <tt>tar.gz</tt> files manually, but we are

switching back to real CTM base deltas. The latter contain MD5

switching back to real CTM base deltas. The latter contain

checksums and are generated automatically, thus are a bit safer. You

can distinguish these two kinds of base set by their filename. An

can distinguish these two kinds of base sets by their filename. An

example for a <tt>tar.gz</tt> file is

<tt>OpenBSD-cvs.1450.tar.gz</tt>, whereas a CTM base delta

would be named <tt>OpenBSD-cvs.1500A.gz</tt>. See below for

Line 206

Line 207

Repeat this last step every time you receive a delta from the

mailing list. If you like you can automate this step using procmail

mailing list. If you like, you can automate this step using procmail

or any similar program.

</ul>

Line 265

Line 266

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

the "better" choice is probably the <a href="anoncvs.html">CVS</a>

your working copy of the source tree from your CVS repository then,

repository. You can check out your working copy of the source tree

and keep your local modifications in your source tree. CVS is

from your CVS repository then, and keep your local modifications in

smart enough to merge in your local changes. You can also use the

your source tree. CVS is smart enough to merge in your local changes.

full range of CVS commands except <tt>cvs commit</tt>.

You can also use the full range of CVS commands except <tt>cvs

commit</tt>.

The drawback, however, is the amount of diskspace it takes. A

Line 282

Line 284

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

(see <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mount_union&sektion=8">mount_union(8)</a>)

unstable if both the upper and lower layers reside on the same physical

although there have been reports that the union filesystem can be

filesystem. If you place your upper and lower layers on separate filesystems

unstable if both the upper and lower layers reside on the same physical

you should have no problems. A sample of this is as follows:

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 <tt>/usr/src-ctm</tt>, and

Line 358

Line 361

second day the remaining 46, plus the first 4 messages of the

following delta.

<li> The CTM software could be rewritten, or at least fixed in a

better manner. It's C implemtation is not an example of good

better manner. Its C implemtation is not an example of good

programming. That would also be a nice opportunity for adding

new features, like signing CTM deltas with PGP.

</ul>