Date: Sat, 25 May 1996 10:02:13 -0400 (EDT) From: Chuck Robey <chuckr@Glue.umd.edu> To: FreeBSD-doc@FreeBSD.org Subject: Better ctm/sup explanation Message-ID: <Pine.OSF.3.91.960525095906.4268B-200000@skipper.eng.umd.edu> In-Reply-To: <9605242130.AA07562@fslg8.fsl.noaa.gov>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
I thought I'd give a whack at a better ctm/sup description. What's
attached is a diff to synching.sgml, so that it better contrasts the two
methods.
I hope it's useful. I didn't change the authorname (now Jordan), I don't
know the policy on that, and my change isn't all that big.
----------------------------+-----------------------------------------------
Chuck Robey | Interests include any kind of voice or data
chuckr@eng.umd.edu | communications topic, C programming, and Unix.
9120 Edmonston Ct #302 |
Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD
(301) 220-2114 | version 2.2 current -- and great FUN!
----------------------------+-----------------------------------------------
[-- Attachment #2 --]
--- synching.sgml.orig Fri May 24 19:35:38 1996
+++ synching.sgml Fri May 24 20:20:35 1996
@@ -13,9 +13,44 @@
use the internet to keep development sources in synch.
-->
- <p>There are various ways of using an Internet (or email) connection
- to stay up-to-date with whatever collection of FreeBSD project sources
- it is that interests you. The primary services we offer are:
+<p>There are various ways of using an Internet (or email) connection
+to stay up-to-date with whatever collection of FreeBSD project sources
+it is that interests you. The primary services we offer are ctm and sup.
+<p>It's been suggested that ctm obsoletes sup. This isn't true, because:
+<p>Each method was originally designed to serve a different constituency,
+and although they have both undergone improvement since first going into
+service, they remain fundamentally different. sup was originally
+designed to support those who had direct net connection, while ctm was
+originally produced to support those who were limited to email access
+to the net.
+<p><bf>sup</bf> is a system that looks at the sources that you have on
+your local disk, and (by using configuration files you set up) makes
+a request over the network to get and update any files that have changed
+from those on a FreeBSD archive.
+<p><bf>ctm</bf> does not interactively compare the sources you have
+with those on a FreeBSD archive. Instead, a script is run several
+times a day, on the archive, to identify changes in files. These changes
+are encoded, compressed, and sent to your home system, where they
+are used to patch your sources, to bring them current. ctm does not
+use config files (it is not interactive between the FreeBSD archive and your
+home system), so you can only use ctm on specific source sets, that
+are having ctm diffs being auto-generated.
+<p>Ctm is for folks that want to stay updated via mail, and
+sup is for users with direct net connectivity. Ctm is somewhat more
+limited in that you can only get updates for certain defined file
+collections, that are having ctm scripts run on them. Sup can be
+configured to build more selective collections (you can customize what
+file collections you want).
+<p>With sup, you can wipe out portions of your archive, sup will see that,
+and rebuild it for you. ctm won't do that, if you wipe some of it out,
+you have to start from scratch and rebuild it all. sup compares what you
+have with what its trying to maintain, and rebuilds intelligently, but
+ctm is a one way street, with no feedback on what you need, just on
+changing what you have.
+<p>ctm is more conservative, and sends
+compressed diffs, while sup sends whole files.
+As you can see, they are different, they serve different audiences.
+
⊃
&ctm;
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.91.960525095906.4268B-200000>