From owner-svn-doc-head@FreeBSD.ORG Wed Oct 10 23:14:39 2012 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 01388A1B; Wed, 10 Oct 2012 23:14:39 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:4f8:fff6::2c]) by mx1.freebsd.org (Postfix) with ESMTP id DC3BF8FC0C; Wed, 10 Oct 2012 23:14:38 +0000 (UTC) Received: from svn.freebsd.org (localhost [127.0.0.1]) by svn.freebsd.org (8.14.4/8.14.4) with ESMTP id q9ANEc9T019050; Wed, 10 Oct 2012 23:14:38 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.4/8.14.4/Submit) id q9ANEc3t019048; Wed, 10 Oct 2012 23:14:38 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201210102314.q9ANEc3t019048@svn.freebsd.org> From: Warren Block Date: Wed, 10 Oct 2012 23:14:38 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r39731 - head/en_US.ISO8859-1/books/handbook/mirrors X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2012 23:14:39 -0000 Author: wblock Date: Wed Oct 10 23:14:38 2012 New Revision: 39731 URL: http://svn.freebsd.org/changeset/doc/39731 Log: Whitespace-only cleanup, fixing indentation and long line wrap. Translators, please ignore. Modified: head/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml Wed Oct 10 20:40:46 2012 (r39730) +++ head/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml Wed Oct 10 23:14:38 2012 (r39731) @@ -22,7 +22,8 @@
Frys Electronics - WWW: + WWW:
@@ -34,129 +35,143 @@ &os; CD and DVD sets are available from many online retailers: - - -
- &os; Mall, Inc. - 700 Harvest Park Ste F - Brentwood, CA 94513 - USA - Phone: +1 925 240-6652 - Fax: +1 925 674-0821 - Email: info@freebsdmall.com - WWW: -
- - - -
- Dr. Hinner EDV - St. Augustinus-Str. 10 - D-81825 München - Germany - Phone: (089) 428 419 - WWW: -
- - - -
- JMC Software - Ireland - Phone: 353 1 6291282 - WWW: -
- - - -
- Linux Distro UK - 42 Wharfedale Road - Margate - CT9 2TB - United Kingdom - WWW: -
- - - -
- The Linux Emporium - Hilliard House, Lester Way - Wallingford - OX10 9TA - United Kingdom - Phone: +44 1491 837010 - Fax: +44 1491 837016 - WWW: -
- - - -
- Linux+ DVD Magazine - Lewartowskiego 6 - Warsaw - 00-190 - Poland - Phone: +48 22 860 18 18 - Email: editors@lpmagazine.org - WWW: -
- - - -
- Linux System Labs Australia - 21 Ray Drive - Balwyn North - VIC - 3104 - Australia - Phone: +61 3 9857 5918 - Fax: +61 3 9857 8974 - WWW: -
- - - -
- LinuxCenter.Ru - Galernaya Street, 55 - Saint-Petersburg - 190000 - Russia - Phone: +7-812-3125208 - Email: info@linuxcenter.ru - WWW: -
- + + +
+ &os; Mall, Inc. + 700 Harvest Park Ste F + Brentwood, + CA + 94513 + USA + Phone: +1 925 240-6652 + Fax: +1 925 674-0821 + Email: info@freebsdmall.com + WWW: +
+ + + +
+ Dr. Hinner EDV + St. Augustinus-Str. 10 + D-81825 München + Germany + Phone: (089) 428 419 + WWW: +
+ + + +
+ JMC Software + Ireland + Phone: 353 1 6291282 + WWW: +
+ + + +
+ Linux Distro UK + 42 Wharfedale Road + Margate + CT9 2TB + United Kingdom + WWW: +
+ + + +
+ The Linux Emporium + Hilliard House, Lester Way + Wallingford + OX10 9TA + United Kingdom + Phone: +44 1491 837010 + Fax: +44 1491 837016 + WWW: +
+ + + +
+ Linux+ DVD Magazine + Lewartowskiego 6 + Warsaw + 00-190 + Poland + Phone: +48 22 860 18 18 + Email: editors@lpmagazine.org + WWW: +
+ + + +
+ Linux System Labs Australia + 21 Ray Drive + Balwyn North + VIC - 3104 + Australia + Phone: +61 3 9857 5918 + Fax: +61 3 9857 8974 + WWW: +
+ - + +
+ LinuxCenter.Ru + Galernaya Street, 55 + Saint-Petersburg + 190000 + Russia + Phone: +7-812-3125208 + Email: info@linuxcenter.ru + WWW: +
+ + Distributors - If you are a reseller and want to carry &os; CDROM products, - please contact a distributor: + If you are a reseller and want to carry &os; CDROM + products, please contact a distributor: - +
Ingram Micro 1600 E. St. Andrew Place - Santa Ana, CA 92705-4926 + Santa Ana, + CA + 92705-4926 USA Phone: 1 (800) 456-8000 - WWW: -
- + WWW: + +
Kudzu, LLC 7375 Washington Ave. S. - Edina, MN 55439 + Edina, + MN + 55439 USA Phone: +1 952 947-0822 Fax: +1 952 947-0876 @@ -173,7 +188,8 @@ Russia Phone: +7-812-3125208 Email: info@linuxcenter.ru - WWW: + WWW:
@@ -183,8 +199,8 @@ FTP Sites - The official sources for &os; are available via anonymous FTP - from a worldwide set of mirror sites. The site + The official sources for &os; are available via anonymous + FTP from a worldwide set of mirror sites. The site is well connected and allows a large number of connections to it, but you are probably better off finding a closer @@ -192,17 +208,18 @@ mirror site). Additionally, &os; is available via anonymous FTP from the - following mirror sites. If you choose to obtain &os; via anonymous - FTP, please try to use a site near you. The mirror sites listed as - Primary Mirror Sites 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 but some sites also provide access via other methods. The access - methods available for each site are provided in parentheses - after the hostname. + following mirror sites. If you choose to obtain &os; via + anonymous FTP, please try to use a site near you. The mirror + sites listed as Primary Mirror Sites 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 + but some sites also provide access via other methods. The + access methods available for each site are provided in + parentheses after the hostname. &chap.mirrors.ftp.inc; @@ -217,15 +234,15 @@ The ISO images for the basic release CDs are available via BitTorrent. A collection of torrent files to download the images is available at http://torrents.freebsd.org:8080 + url="http://torrents.freebsd.org:8080/">http://torrents.freebsd.org:8080 The BitTorrent client software is available from the net-p2p/py-bittorrent port, or a precompiled package. After downloading the ISO image with BitTorrent, you may - burn it to CD or DVD media as described in , burncd. + burn it to CD or DVD media as described in + , burncd. @@ -330,569 +347,595 @@ - - Anonymous CVS + + Anonymous CVS + + + <anchor id="anoncvs-intro"/>Introduction + + + CVS + anonymous + + + Anonymous CVS (or, as it is otherwise known, + anoncvs) is a feature provided by the CVS + utilities bundled with &os; for synchronizing with a remote + CVS repository. Among other things, it allows users of &os; + to perform, with no special privileges, read-only CVS + operations against one of the &os; project's official anoncvs + servers. To use it, one simply sets the + CVSROOT environment variable to point at the + appropriate anoncvs server, provides the well-known password + anoncvs with the cvs login + command, and then uses the &man.cvs.1; command to access it + like any local repository. + + + The cvs login command, stores the + passwords that are used for authenticating to the CVS server + in a file called .cvspass in your + HOME directory. If this file does not exist, + you might get an error when trying to use + cvs login for the first time. Just make + an empty .cvspass file, and retry to + login. + + + While it can also be said that the + CVSup and + anoncvs services both perform essentially + the same function, there are various trade-offs which can + influence the user's choice of synchronization methods. In a + nutshell, CVSup is much more + efficient in its usage of network resources and is by far the + most technically sophisticated of the two, but at a price. To + use CVSup, a special client must + first be installed and configured before any bits can be + grabbed, and then only in the fairly large chunks which + CVSup calls + collections. + + Anoncvs, by contrast, can be + used to examine anything from an individual file to a specific + program (like ls or + grep) by referencing the CVS module name. + Of course, anoncvs is also only + good for read-only operations on the CVS repository, so if it + is your intention to support local development in one + repository shared with the &os; project bits then + CVSup is really your only + option. + + + + <anchor id="anoncvs-usage"/>Using Anonymous CVS - - <anchor id="anoncvs-intro"/>Introduction + Configuring &man.cvs.1; to use an Anonymous CVS repository + is a simple matter of setting the CVSROOT + environment variable to point to one of the &os; project's + anoncvs servers. At the time of this + writing, the following servers are available: - - CVS - anonymous - - - Anonymous CVS (or, as it is otherwise known, - anoncvs) is a feature provided by the CVS - utilities bundled with &os; for synchronizing with a remote - CVS repository. Among other things, it allows users of &os; - to perform, with no special privileges, read-only CVS operations - against one of the &os; project's official anoncvs servers. - To use it, one simply sets the CVSROOT - environment variable to point at the appropriate anoncvs server, - provides the well-known password anoncvs with the - cvs login command, and then uses the - &man.cvs.1; command to access it like any local - repository. - - - The cvs login command, stores the passwords - that are used for authenticating to the CVS server in a file - called .cvspass in your - HOME directory. If this file does not exist, - you might get an error when trying to use cvs - login for the first time. Just make an empty - .cvspass file, and retry to login. - - - While it can also be said that the CVSup and anoncvs - services both perform essentially the same function, there are - various trade-offs which can influence the user's choice of - synchronization methods. In a nutshell, - CVSup is much more efficient in its - usage of network resources and is by far the most technically - sophisticated of the two, but at a price. To use - CVSup, a special client must first be - installed and configured before any bits can be grabbed, and - then only in the fairly large chunks which - CVSup calls - collections. - - Anoncvs, by contrast, can be used - to examine anything from an individual file to a specific - program (like ls or grep) - by referencing the CVS module name. Of course, - anoncvs is also only good for - read-only operations on the CVS repository, so if it is your - intention to support local development in one repository shared - with the &os; project bits then - CVSup is really your only - option. - - - - <anchor id="anoncvs-usage"/>Using Anonymous CVS - - Configuring &man.cvs.1; to use an Anonymous CVS repository - is a simple matter of setting the CVSROOT - environment variable to point to one of the &os; project's - anoncvs servers. At the time of this - writing, the following servers are available: - - - - France: - :pserver:anoncvs@anoncvs.fr.FreeBSD.org:/home/ncvs - (For pserver mode, use cvs login and - enter the password anoncvs when prompted. - For ssh, no password is required.) - - - - Taiwan: - :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs - (For pserver mode, use cvs login and - enter any password when prompted. For ssh, no password - is required.) + + + France: + :pserver:anoncvs@anoncvs.fr.FreeBSD.org:/home/ncvs + (For pserver mode, use cvs login and + enter the password anoncvs when prompted. + For ssh, no password is required.) + + + + Taiwan: + :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs + (For pserver mode, use cvs login and + enter any password when prompted. For ssh, no password + is required.) - SSH2 HostKey: 1024 02:ed:1b:17:d6:97:2b:58:5e:5c:e2:da:3b:89:88:26 /etc/ssh/ssh_host_rsa_key.pub + SSH2 HostKey: 1024 02:ed:1b:17:d6:97:2b:58:5e:5c:e2:da:3b:89:88:26 /etc/ssh/ssh_host_rsa_key.pub SSH2 HostKey: 1024 e8:3b:29:7b:ca:9f:ac:e9:45:cb:c8:17:ae:9b:eb:55 /etc/ssh/ssh_host_dsa_key.pub - - - - - Since CVS allows one to check out virtually - any version of the &os; sources that ever existed (or, in - some cases, will exist), you need to be - familiar with the revision () flag to - &man.cvs.1; and what some of the permissible values for it in - the &os; Project repository are. - - There are two kinds of tags, revision tags and branch tags. - A revision tag refers to a specific revision. Its meaning stays - the same from day to day. A branch tag, on the other hand, - refers to the latest revision on a given line of development, at - any given time. Because a branch tag does not refer to a - specific revision, it may mean something different tomorrow than - it means today. - - contains revision tags that users - might be interested - in. Again, none of these are valid for the Ports Collection - since the Ports Collection does not have multiple - branches of development. - - When you specify a branch tag, you normally receive the - latest versions of the files on that line of development. If - you wish to receive some past version, you can do so by - specifying a date with the flag. - See the &man.cvs.1; manual page for more details. - - - - Examples - - While it really is recommended that you read the manual page - for &man.cvs.1; thoroughly before doing anything, here are some - quick examples which essentially show how to use Anonymous - CVS: + + + + + Since CVS allows one to check out virtually + any version of the &os; sources that ever existed (or, in some + cases, will exist), you need to be familiar with the revision + () flag to &man.cvs.1; and what some of the + permissible values for it in the &os; Project repository + are. + + There are two kinds of tags, revision tags and branch + tags. A revision tag refers to a specific revision. Its + meaning stays the same from day to day. A branch tag, on the + other hand, refers to the latest revision on a given line of + development, at any given time. Because a branch tag does not + refer to a specific revision, it may mean something different + tomorrow than it means today. + + contains revision tags that + users might be interested in. Again, none of these are valid + for the Ports Collection since the Ports Collection does not + have multiple branches of development. + + When you specify a branch tag, you normally receive the + latest versions of the files on that line of development. If + you wish to receive some past version, you can do so by + specifying a date with the flag. See + the &man.cvs.1; manual page for more details. + - - Checking Out Something from -CURRENT (&man.ls.1;): + + Examples + + While it really is recommended that you read the manual + page for &man.cvs.1; thoroughly before doing anything, here + are some quick examples which essentially show how to use + Anonymous CVS: + + + Checking Out Something from -CURRENT + (&man.ls.1;): - &prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs + &prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs &prompt.user; cvs login At the prompt, enter any word for password. &prompt.user; cvs co ls - - + + - - Using SSH to Check Out the <filename>src/</filename> - Tree: - &prompt.user; cvs -d anoncvs@anoncvs1.FreeBSD.org:/home/ncvs co src + + Using SSH to Check Out the <filename>src/</filename> + Tree: + + &prompt.user; cvs -d anoncvs@anoncvs1.FreeBSD.org:/home/ncvs co src The authenticity of host 'anoncvs1.freebsd.org (216.87.78.137)' can't be established. DSA key fingerprint is 53:1f:15:a3:72:5c:43:f6:44:0e:6a:e9:bb:f8:01:62. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hosts. - + - - Checking Out the Version of &man.ls.1; in the 8-STABLE - Branch: + + Checking Out the Version of &man.ls.1; in the 8-STABLE + Branch: - &prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs + &prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs &prompt.user; cvs login At the prompt, enter any word for password. &prompt.user; cvs co -rRELENG_8 ls - - + + - - Creating a List of Changes (as Unified Diffs) to &man.ls.1; + + Creating a List of Changes (as Unified Diffs) to + &man.ls.1; - &prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs + &prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs &prompt.user; cvs login At the prompt, enter any word for password. &prompt.user; cvs rdiff -u -rRELENG_8_0_0_RELEASE -rRELENG_8_1_0_RELEASE ls - - + + - - Finding Out What Other Module Names Can Be Used: + + Finding Out What Other Module Names Can Be + Used: - &prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs + &prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs &prompt.user; cvs login At the prompt, enter any word for password. &prompt.user; cvs co modules &prompt.user; more modules/modules - - - - - - Other Resources + + + - The following additional resources may be helpful in learning - CVS: + + Other Resources - - - CVS Tutorial from California - Polytechnic State University. - + The following additional resources may be helpful in + learning CVS: - - CVS Home, - the CVS development and support community. - + + + CVS + Tutorial from California Polytechnic State + University. + - - CVSweb is - the &os; Project web interface for CVS. - - - - + + CVS + Home, the CVS development and support + community. + + + CVSweb + is the &os; Project web interface for CVS. + + + + Using CTM - - CTM - + + CTM + + + CTM 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 CTM for other + things. + + + Why Should I Use <application>CTM</application>? + + CTM will give you a local copy + of the &os; source trees. There are a number of + flavors of the tree available. Whether you + wish to track the entire CVS tree or just one of the branches, + CTM 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, + 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, with an + occasional (one in ten) being 10-50K and every now and then a + large 100K+ or more coming around. + + You will also need to make yourself aware of the various + caveats 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 Staying current with &os;. + + + + What Do I Need to Use + <application>CTM</application>? - CTM 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 CTM - for other things. - - - Why Should I Use <application>CTM</application>? - - CTM will give you a local copy of - the &os; source trees. There are a number of - flavors of the tree available. Whether you wish - to track the entire CVS tree or just one of the branches, - CTM 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, - 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, with an - occasional (one in ten) being 10-50K and every now and then a - large 100K+ or more coming around. - - You will also need to make yourself aware of the various - caveats 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 Staying - current with &os;. - - - - What Do I Need to Use - <application>CTM</application>? - - You will need two things: The CTM - program, and the initial deltas to feed it (to get up to - current levels). - - The CTM program has been part of - &os; ever since version 2.0 was released, and lives in - /usr/src/usr.sbin/ctm if you have a copy - of the source available. - - The deltas you feed - CTM 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 - CTM: + You will need two things: The + CTM program, and the initial deltas + to feed it (to get up to current + levels). + + The CTM program has been part + of &os; ever since version 2.0 was released, and lives in + /usr/src/usr.sbin/ctm if you have a copy + of the source available. + + The deltas you feed + CTM 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 + CTM: - + - or see section or see section mirrors. - FTP the relevant directory and fetch the - README file, starting from there. + FTP the relevant directory and fetch the + README file, starting from there. + + If you wish to get your deltas via email: + + Subscribe to one of the + CTM distribution lists. + &a.ctm-cvs-cur.name; supports the entire CVS tree. + &a.ctm-src-cur.name; supports the head of the development + branch. &a.ctm-src-7.name; supports the 7.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.) + + When you begin receiving your + CTM updates in the mail, you may + use the ctm_rmail program to unpack and + apply them. You can actually use the + ctm_rmail program directly from a entry in + /etc/aliases if you want to have the + process run in a fully automated fashion. Check the + ctm_rmail manual page for more + details. + + + No matter what method you use to get the + CTM 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 CTM system + will be posted. Click on the list name above and follow the + instructions to subscribe to the list. + + + + + Using <application>CTM</application> for the First + Time + + Before you can start using CTM + deltas, you will need to get to a starting point for the + deltas produced subsequently to it. + + First you should determine what you already have. + Everyone can start from an empty directory. + You must use an initial Empty delta to start + off your CTM supported tree. At + some point it is intended that one of these + started deltas be distributed on the CD for + your convenience, however, this does not currently + happen. + + Since the trees are many tens of megabytes, you should + prefer to start from something already at hand. If you have a + -RELEASE CD, you can copy or extract an initial source from + it. This will save a significant transfer of data. + + You can recognize these starter deltas by + the X appended to the number + (src-cur.3210XEmpty.gz for instance). + The designation following the X corresponds + to the origin of your initial seed. + Empty is an empty directory. As a rule a + base transition from Empty is produced + every 100 deltas. By the way, they are large! 70 to 80 + Megabytes of gzip'd data is common for the + XEmpty deltas. - If you wish to get your deltas via email: + Once you have picked a base delta to start from, you will + also need all deltas with higher numbers following it. + - Subscribe to one of the - CTM distribution lists. - &a.ctm-cvs-cur.name; supports the entire CVS tree. - &a.ctm-src-cur.name; supports the head of the development - branch. &a.ctm-src-7.name; supports the 7.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.) - - When you begin receiving your CTM - updates in the mail, you may use the - ctm_rmail program to unpack and apply them. - You can actually use the ctm_rmail program - directly from a entry in /etc/aliases if - you want to have the process run in a fully automated fashion. - Check the ctm_rmail manual page for more - details. - - - No matter what method you use to get the - CTM 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 - CTM system will be posted. Click - on the list name above and follow the instructions - to subscribe to the - list. - - - - - Using <application>CTM</application> for the First - Time - - Before you can start using CTM - deltas, you will need to get to a starting point for the deltas - produced subsequently to it. - *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***