os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Reflect current state of the CTM world.

Browse source 
Submitted by: Richard Wackerbarth <rkw@Dataplex.Net>
This commit is contained in:
Jordan K. Hubbard 1997-10-20 07:45:23 +00:00
parent eee6016a3d
commit 658e23b33f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=2091
1 changed files with 46 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

76
handbook/ctm.sgml
View file

@ -3,7 +3,7 @@
# #
# Converted by Ollivier Robert <roberto@FreeBSD.ORG> # Converted by Ollivier Robert <roberto@FreeBSD.ORG>
# #
# $Id: ctm.sgml,v 1.21 1997-10-19 13:32:08 jraynard Exp $ # $Id: ctm.sgml,v 1.22 1997-10-20 07:45:23 jkh Exp $
# #
# ---------------------------------------------------------------------------- # ----------------------------------------------------------------------------
# "THE BEER-WARE LICENSE" (Revision 42): # "THE BEER-WARE LICENSE" (Revision 42):
@ -16,7 +16,7 @@
<sect1><heading>CTM<label id="ctm"></heading> <sect1><heading>CTM<label id="ctm"></heading>
<p><em>Contributed by &a.phk;. Updated 31-July-1997.</em> <p><em>Contributed by &a.phk;. Updated 19-October-1997.</em>
<tt/CTM/ is a method for keeping a remote directory tree in sync with a <tt/CTM/ is a method for keeping a remote directory tree in sync with a
central one. It has been developed for usage with FreeBSD's source central one. It has been developed for usage with FreeBSD's source
@ -26,17 +26,24 @@
for more information should you wish to use <tt/CTM/ for other things. for more information should you wish to use <tt/CTM/ for other things.
<sect2><heading>Why should I use <tt/CTM/?</heading> <sect2><heading>Why should I use <tt/CTM/?</heading>
<p><tt/CTM/ will give you a local copy of the ``FreeBSD-current'' <p><tt/CTM/ will give you a local copy of the FreeBSD source trees.
sources. If you are an active developer on FreeBSD, but have lousy There are a number of ``flavors'' of the tree available. Whether
or non-existent TCP/IP connectivity, <tt/CTM/ was made for you. you wish to track the entire cvs tree or just one of the branches,
You will need to transfer up to four deltas per day (or you can <tt/CTM/ can provide you the information.
have them arrive in email automatically), the sizes for which are If you are an active developer on FreeBSD, but have lousy
or non-existent TCP/IP connectivity, or simply wish to have the
changes automatically sent to you, <tt/CTM/ was made for you.
You will need to obtain up to three deltas per day for the most
active branches. However, you should consider having them sent
by automatic email. The sizes of the updates are
always kept as small as possible. This is typically less than 5K, always kept as small as possible. This is typically less than 5K,
with the occasional (one in ten) being 10-50K and every now and with an occasional (one in ten) being 10-50K and every now and
then a biggie of 100K+ or more coming around. then a biggie of 100K+ or more coming around.
You will also need to make yourself aware of the various caveats in You will also need to make yourself aware of the various caveats
running ``current'' sources, and for this it is recommended that related to working directly from the development sources rather
than a pre-packaged release. This is particularly true if you
choose the ``current'' sources. It is recommended that
you read <ref id="current" name="Staying current with FreeBSD">. you read <ref id="current" name="Staying current with FreeBSD">.
<sect2><heading>What do I need to use <tt/CTM/?</heading> <sect2><heading>What do I need to use <tt/CTM/?</heading>
@ -65,11 +72,13 @@
FTP the relevant directory and fetch the <tt/README/ file, FTP the relevant directory and fetch the <tt/README/ file,
starting from there. starting from there.
If you only have access to electronic mail or are otherwise blocked If you may wish to get your deltas via email:
from using FTP then you may wish to get your deltas via email:
Send email to &a.majordomo to subscribe to Send email to &a.majordomo to subscribe to one of the <tt/CTM/
the list ``ctm-src-cur''. (If you do not know how to subscribe distribution lists. ``ctm-cvs-cur'' supports the entire cvs tree.
``ctm-src-cur'' supports the head of the development branch.
``ctm-src-2_2'' supports the 2.2 release branch, etc.
(If you do not know how to subscribe
yourself using majordomo, send a message first containing the yourself using majordomo, send a message first containing the
word ``help'' - it will send you back usage instructions.) word ``help'' - it will send you back usage instructions.)
@ -89,20 +98,27 @@
<sect2><heading>Starting off with <tt/CTM/ for the first time</heading> <sect2><heading>Starting off with <tt/CTM/ for the first time</heading>
<p>Before you can start using <tt/CTM/ deltas, you will need to get a <p>Before you can start using <tt/CTM/ deltas, you will need to get a
special ``base'' delta that provides the starting point for all to a starting point for the deltas produced subsequently to it.
deltas produced subsequently to it.
First you should determine what you already have. Everyone can
You can recognize a base delta by the ``<tt/Empty/'' appended to the start from an ``Empty'' directory. However, since the trees are
number (<tt/src-cur.0341Empty.gz/ for instance). As a rule a base many tens of megabytes, you should prefer to start from something
delta is produced every 100 deltas, the next one will be already at hand. If you have a RELEASE CD, you can copy or extract
<tt/src-cur.0400Empty.gz/. By the way, they are large! 50 to 100 an initial source from it. This will save a significant transfer
Megabytes of <tt/gzip/'ed data is common for a base delta. of data.
<!-- Once you identify a suitable starting point, you must use an initial
If you do have the 2.0-RELEASE <tt/srcdist/, you can instead ``transition'' delta to transform your starting point into a
retrieve the <tt/src-cur.0372R20.gz/ file, it is only 4Mb and it <tt/CTM/ supported tree.
will take you to level 372 from the 2.0-RELEASE sources.
--> You can recognize these transition deltas by the ``<tt/X/'' appended
to the number (<tt/src-cur.3210XEmpty.gz/ for instance).
The designation following the ``<tt/X/'' corresponds to the origin
of your initial ``seed''. ``Empty'' is an empty directory, ``R225''
would designate the 2.2.5 release, etc.
As a rule a base transition from ``Empty'' is producted
every 100 deltas. By the way, they are large! 25 to 30
Megabytes of <tt/gzip/'ed data is common for the ``XEmpty'' deltas.
Once you've picked a base delta to start from, you will also need Once you've picked a base delta to start from, you will also need
all deltas with higher numbers following it. all deltas with higher numbers following it.
@ -112,7 +128,7 @@
To apply the deltas, simply say: To apply the deltas, simply say:
<tscreen><verb> <tscreen><verb>
cd /where/ever/you/want/the/stuff cd /where/ever/you/want/the/stuff
ctm -v -v /where/you/store/your/deltas/src-cur.* ctm -v -v /where/you/store/your/deltas/src-xxx.*
</verb></tscreen> </verb></tscreen>
<p> <p>
<tt/CTM/ understands deltas which have been put through <tt/gzip/, <tt/CTM/ understands deltas which have been put through <tt/gzip/,
@ -186,7 +202,7 @@ ctm -v -v /where/you/store/your/deltas/src-cur.*
run the commands: run the commands:
<tscreen><verb> <tscreen><verb>
cd /where/ever/you/want/to/extract/it/ cd /where/ever/you/want/to/extract/it/
ctm -e '^lib/libc/Makefile' ~ctm/src-cur.* ctm -e '^lib/libc/Makefile' ~ctm/src-xxx.*
</verb></tscreen> </verb></tscreen>
<p> <p>
For every file specified in a CTM delta, the ``<tt>-e</tt>'' and For every file specified in a CTM delta, the ``<tt>-e</tt>'' and