First pass at improving the flow of this chapter.

More commits to come.

Sponsored by: iXsystems
This commit is contained in:
Dru Lavigne 2014-02-12 19:08:16 +00:00
parent 3432ca0e57
commit 556c8c3a51
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=43885

View file

@ -84,26 +84,26 @@
</sect1>
<sect1 xml:id="mirrors-ftp">
<title>FTP Sites</title>
<title><acronym>FTP</acronym> Sites</title>
<para>The official sources for &os; are available via anonymous
FTP from a worldwide set of mirror sites. The site
<acronym>FTP</acronym> from a worldwide set of mirror sites. The site
<uri xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp://ftp.FreeBSD.org/pub/FreeBSD/</uri> is well
connected and allows a large number of connections to it, but
you are probably better off finding a <quote>closer</quote>
mirror site (especially if you decide to set up some sort of
mirror site).</para>
<para>Additionally, &os; is available via anonymous FTP from the
<para>Additionally, &os; is available via anonymous <acronym>FTP</acronym> from the
following mirror sites. If you choose to obtain &os; via
anonymous FTP, please try to use a site near you. The mirror
anonymous <acronym>FTP</acronym>, please try to use a site near you. The mirror
sites listed as <quote>Primary Mirror Sites</quote> typically
have the entire &os; archive (all the currently available
versions for each of the architectures) but you will probably
have faster download times from a site that is in your country
or region. The regional sites carry the most recent versions
for the most popular architecture(s) but might not carry the
entire &os; archive. All sites provide access via anonymous FTP
entire &os; archive. All sites provide access via anonymous <acronym>FTP</acronym>
but some sites also provide access via other methods. The
access methods available for each site are provided in
parentheses after the hostname.</para>
@ -138,99 +138,117 @@
</indexterm>
<para><application>CTM</application> is a method for keeping a
remote directory tree in sync with a central one. It has been
developed for usage with &os;'s source trees, though other
people may find it useful for other purposes as time goes by.
Little, if any, documentation currently exists at this time on
the process of creating deltas, so contact the
&a.ctm-users.name; mailing list for more information and if you
wish to use <application>CTM</application> for other
things.</para>
remote directory tree in sync with a central one. It is built into &os;
and can be used to synchronize a system with &os;'s source repositories.
It supports synchronization of an entire repository or just the specified branches.</para>
<sect2>
<title>Why Should I Use <application>CTM</application>?</title>
<para><application>CTM</application> is specifically designed for use on
lousy or non-existent TCP/IP connections. It provides the ability
for changes to be automatically sent by email. It requires the user
to obtain up to three deltas per day for the most active
branches. Update sizes are always kept as
small as possible and are typically less than 5K. About one in very ten
update is 10-50K in size and rarely there will be an update
larger than 100K+.</para>
<para><application>CTM</application> will give you a local copy
of the &os; source trees. There are a number of
<quote>flavors</quote> of the tree available. Whether you
wish to track the entire CVS tree or just one of the branches,
<application>CTM</application> can provide you the
information. If you are an active developer on &os;, but have
lousy or non-existent TCP/IP connectivity, or simply wish to
have the changes automatically sent to you,
<application>CTM</application> 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, with an
occasional (one in ten) being 10-50K and every now and then a
large 100K+ or more coming around.</para>
<para>You will also need to make yourself aware of the various
<para>When using <application>CTM</application> to track &os; development,
refer to the
caveats related to working directly from the development
sources rather than a pre-packaged release. This is
particularly true if you choose the <quote>current</quote>
sources. It is recommended that you read <link linkend="current">Staying current with &os;</link>.</para>
</sect2>
sources rather than a pre-packaged release. These are discussed
in <link linkend="current-stable">Tracking a Development Branch</link>.</para>
<sect2>
<title>What Do I Need to Use
<application>CTM</application>?</title>
<para>Little documentation exists on
the process of creating deltas or using <application>CTM</application>
for other purposes. Contact the
&a.ctm-users.name; mailing list for questions on using
<application>CTM</application>.</para>
<para>You will need two things: The
<application>CTM</application> program, and the initial deltas
to feed it (to get up to <quote>current</quote>
levels).</para>
<sect2 xml:id="mirrors-ctm">
<title>Getting Deltas</title>
<para>The <application>CTM</application> program has been part
of &os; ever since version 2.0 was released, and lives in
<filename>/usr/src/usr.sbin/ctm</filename> if you have a copy
of the source available.</para>
<para>The <quote>deltas</quote> used by
<application>CTM</application> can be obtained either through
anonymous <acronym>FTP</acronym> or
email.</para>
<para><acronym>FTP</acronym> deltas can be obtained from the following mirror sites.
Download the relevant directory and read its
<filename>README</filename>. When using anonymous <acronym>FTP</acronym> to obtain <application>CTM</application> deltas,
select a geographically close mirror.
In case of problems, contact the &a.ctm-users.name;
mailing list.</para>
<para>The <quote>deltas</quote> you feed
<application>CTM</application> can be had two ways, FTP or
email. If you have general FTP access to the Internet then
the following FTP sites support access to
<application>CTM</application>:</para>
<variablelist>
<varlistentry>
<term>California, Bay Area, official source</term>
<para><uri xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/">ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/</uri></para>
<listitem>
<itemizedlist>
<listitem>
<para><uri xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/</uri></para>
</listitem>
<listitem>
<para><uri xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/">ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/</uri></para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
<para>or see section <link linkend="mirrors-ctm">mirrors</link>.</para>
<varlistentry>
<term>South Africa, backup server for old deltas</term>
<para>FTP the relevant directory and fetch the
<filename>README</filename> file, starting from there.</para>
<listitem>
<itemizedlist>
<listitem>
<para><uri xlink:href="ftp://ftp.za.FreeBSD.org/pub/FreeBSD/CTM/">ftp://ftp.za.FreeBSD.org/pub/FreeBSD/CTM/</uri></para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
<para>If you wish to get your deltas via email:</para>
<varlistentry>
<term>Taiwan/R.O.C.</term>
<para>Subscribe to one of the
<listitem>
<itemizedlist>
<listitem>
<para><uri xlink:href="ftp://ctm.tw.FreeBSD.org/pub/FreeBSD/development/CTM/">ftp://ctm.tw.FreeBSD.org/pub/FreeBSD/development/CTM/</uri></para>
</listitem>
<listitem>
<para><uri xlink:href="ftp://ctm2.tw.FreeBSD.org/pub/FreeBSD/development/CTM/">ftp://ctm2.tw.FreeBSD.org/pub/FreeBSD/development/CTM/</uri></para>
</listitem>
<listitem>
<para><uri xlink:href="ftp://ctm3.tw.FreeBSD.org/pub/FreeBSD/development/CTM/">ftp://ctm3.tw.FreeBSD.org/pub/FreeBSD/development/CTM/</uri></para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
</variablelist>
<para>To instead receive deltas through email, subscribe to one of the
<application>CTM</application> distribution lists.
&a.ctm-src-cur.name; supports the entire Subversion tree.
&a.ctm-src-cur.name; supports the head of the development
branch. &a.ctm-src-9.name; supports the 9.X release branch,
etc.. (If you do not know how to subscribe yourself to a
list, click on the list name above or go to
&a.mailman.lists.link; and click on the list that you wish to
subscribe to. The list page should contain all of the
necessary subscription instructions.)</para>
&a.ctm-src-cur.name; supports the entire source tree,
&a.ctm-src-cur.name; supports the HEAD of the development
branch, and &a.ctm-src-9.name; supports the 9.X release branch.</para>
<para>When you begin receiving your
<application>CTM</application> updates in the mail, you may
use the <command>ctm_rmail</command> program to unpack and
apply them. You can actually use the
<command>ctm_rmail</command> program directly from a entry in
<filename>/etc/aliases</filename> if you want to have the
process run in a fully automated fashion. Check the
<command>ctm_rmail</command> manual page for more
<para>As
<application>CTM</application> updates arrive through email,
use <command>ctm_rmail</command> to unpack and
apply them. This command can be run directly from an entry in
<filename>/etc/aliases</filename> in order to
automate this process. Refer to
&man.ctm.rmail.1; for more
details.</para>
<note>
<para>No matter what method you use to get the
<application>CTM</application> deltas, you should subscribe
to the &a.ctm-announce.name; mailing list. In the future,
this will be the only place where announcements concerning
the operations of the <application>CTM</application> system
will be posted. Click on the list name above and follow the
instructions to subscribe to the list.</para>
<para>Regardless of the method which is used to get deltas,
<application>CTM</application> users should subscribe
to the &a.ctm-announce.name; mailing list as
this is the only place where announcements concerning
the operation of the <application>CTM</application> system
are posted.</para>
</note>
</sect2>
@ -238,18 +256,11 @@
<title>Using <application>CTM</application> for the First
Time</title>
<para>Before you can start using <application>CTM</application>
deltas, you will need to get to a starting point for the
deltas produced subsequently to it.</para>
<para>First you should determine what you already have.
Everyone can start from an <quote>empty</quote> directory.
You must use an initial <quote>Empty</quote> delta to start
off your <application>CTM</application> supported tree. At
some point it is intended that one of these
<quote>started</quote> deltas be distributed on the CD for
your convenience, however, this does not currently
happen.</para>
<para>Before <application>CTM</application>
deltas can be used, a starting point for the
deltas must be produced from an <quote>empty</quote> directory.
An initial <quote>Empty</quote> delta is used to start
the local <application>CTM</application>-supported tree.</para>
<para>Since the trees are many tens of megabytes, you should
prefer to start from something already at hand. If you have a
@ -409,76 +420,11 @@
counter intuitive.</para>
</listitem>
</itemizedlist>
</sect2>
<sect2>
<title>Miscellaneous Stuff</title>
<para>There is a sequence of deltas for the
<literal>ports</literal> collection too, but interest has not
been all that high yet.</para>
</sect2>
<sect2 xml:id="mirrors-ctm">
<title>CTM Mirrors</title>
<para><link linkend="ctm">CTM</link>/&os; is available via
anonymous FTP from the following mirror sites. If you choose
to obtain <application>CTM</application> via anonymous FTP,
please try to use a site near you.</para>
<para>In case of problems, please contact the &a.ctm-users.name;
mailing list.</para>
<variablelist>
<varlistentry>
<term>California, Bay Area, official source</term>
<listitem>
<itemizedlist>
<listitem>
<para><uri xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/</uri></para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
<term>South Africa, backup server for old deltas</term>
<listitem>
<itemizedlist>
<listitem>
<para><uri xlink:href="ftp://ftp.za.FreeBSD.org/pub/FreeBSD/CTM/">ftp://ftp.za.FreeBSD.org/pub/FreeBSD/CTM/</uri></para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
<term>Taiwan/R.O.C.</term>
<listitem>
<itemizedlist>
<listitem>
<para><uri xlink:href="ftp://ctm.tw.FreeBSD.org/pub/FreeBSD/development/CTM/">ftp://ctm.tw.FreeBSD.org/pub/FreeBSD/development/CTM/</uri></para>
</listitem>
<listitem>
<para><uri xlink:href="ftp://ctm2.tw.FreeBSD.org/pub/FreeBSD/development/CTM/">ftp://ctm2.tw.FreeBSD.org/pub/FreeBSD/development/CTM/</uri></para>
</listitem>
<listitem>
<para><uri xlink:href="ftp://ctm3.tw.FreeBSD.org/pub/FreeBSD/development/CTM/">ftp://ctm3.tw.FreeBSD.org/pub/FreeBSD/development/CTM/</uri></para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
</variablelist>
<para>If you did not find a mirror near to you or the mirror is
incomplete, try to use a search engine such as <link xlink:href="http://www.alltheweb.com/">alltheweb</link>.</para>
</sect2>
</sect1>
<sect1 xml:id="svn">
@ -2507,7 +2453,7 @@ usr.bin/</programlisting>
which transfers only the differences between two sets of files,
thus greatly speeding up the synchronization over the network.
This is most useful if you are a mirror site for the
&os; FTP server, or the CVS repository. The
&os; <acronym>FTP</acronym> server, or the CVS repository. The
<application>rsync</application> suite is available for many
operating systems, on &os;, see the
<package>net/rsync</package>
@ -2523,12 +2469,12 @@ usr.bin/</programlisting>
<para>Available collections:</para>
<itemizedlist>
<listitem>
<para>ftp: A partial mirror of the &os; FTP
<para>ftp: A partial mirror of the &os; <acronym>FTP</acronym>
server.</para>
</listitem>
<listitem>
<para>&os;: A full mirror of the &os; FTP server.</para>
<para>&os;: A full mirror of the &os; <acronym>FTP</acronym> server.</para>
</listitem>
</itemizedlist>
</listitem>
@ -2543,7 +2489,7 @@ usr.bin/</programlisting>
<para>Available collections:</para>
<itemizedlist>
<listitem>
<para>&os;: A full mirror of the &os; FTP server.</para>
<para>&os;: A full mirror of the &os; <acronym>FTP</acronym> server.</para>
</listitem>
</itemizedlist>
</listitem>
@ -2559,7 +2505,7 @@ usr.bin/</programlisting>
<itemizedlist>
<listitem>
<para>&os;: A full mirror of the &os; FTP server.</para>
<para>&os;: A full mirror of the &os; <acronym>FTP</acronym> server.</para>
</listitem>
<listitem>
@ -2569,7 +2515,7 @@ usr.bin/</programlisting>
<listitem>
<para>&os;-Archive: The mirror of &os; Archive
FTP server.</para>
<acronym>FTP</acronym> server.</para>
</listitem>
</itemizedlist>
</listitem>
@ -2584,7 +2530,7 @@ usr.bin/</programlisting>
<para>Available collections:</para>
<itemizedlist>
<listitem>
<para>&os;: A full mirror of the &os; FTP server.</para>
<para>&os;: A full mirror of the &os; <acronym>FTP</acronym> server.</para>
</listitem>
</itemizedlist>
</listitem>
@ -2603,7 +2549,7 @@ usr.bin/</programlisting>
<para>Available collections:</para>
<itemizedlist>
<listitem>
<para>&os;: A full mirror of the &os; FTP server.</para>
<para>&os;: A full mirror of the &os; <acronym>FTP</acronym> server.</para>
</listitem>
</itemizedlist>
</listitem>
@ -2619,7 +2565,7 @@ usr.bin/</programlisting>
<itemizedlist>
<listitem>
<para>ftp.freebsd.org: A full mirror of the &os;
FTP server.</para>
<acronym>FTP</acronym> server.</para>
</listitem>
</itemizedlist>
</listitem>
@ -2636,7 +2582,7 @@ usr.bin/</programlisting>
<para>Available collections:</para>
<itemizedlist>
<listitem>
<para>&os;: The master archive of the &os; FTP
<para>&os;: The master archive of the &os; <acronym>FTP</acronym>
server.</para>
</listitem>
@ -2651,7 +2597,7 @@ usr.bin/</programlisting>
<itemizedlist>
<listitem>
<para>&os;: A full mirror of the &os; FTP server.</para>
<para>&os;: A full mirror of the &os; <acronym>FTP</acronym> server.</para>
</listitem>
</itemizedlist>
</listitem>