Date: Wed, 10 Oct 2012 23:14:38 +0000 (UTC) From: Warren Block <wblock@FreeBSD.org> 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 Message-ID: <201210102314.q9ANEc3t019048@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
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 @@ <listitem> <address> <otheraddr>Frys Electronics</otheraddr> - WWW: <otheraddr><ulink url="http://www.frys.com/"></ulink></otheraddr>; + WWW: <otheraddr><ulink + url="http://www.frys.com/"></ulink></otheraddr>; </address> </listitem> </itemizedlist> @@ -34,129 +35,143 @@ <para>&os; CD and DVD sets are available from many online retailers:</para> - <itemizedlist> - <listitem> - <address> - <otheraddr>&os; Mall, Inc.</otheraddr> - <street>700 Harvest Park Ste F</street> - <city>Brentwood</city>, <state>CA</state> <postcode>94513</postcode> - <country>USA</country> - Phone: <phone>+1 925 240-6652</phone> - Fax: <fax>+1 925 674-0821</fax> - Email: <email>info@freebsdmall.com</email> - WWW: <otheraddr><ulink url="http://www.freebsdmall.com/"></ulink></otheraddr>; - </address> - </listitem> - - <listitem> - <address> - <otheraddr>Dr. Hinner EDV</otheraddr> - <street>St. Augustinus-Str. 10</street> - <postcode>D-81825</postcode> <city>München</city> - <country>Germany</country> - Phone: <phone>(089) 428 419</phone> - WWW: <otheraddr><ulink url="http://www.hinner.de/linux/freebsd.html"></ulink></otheraddr>; - </address> - </listitem> - - <listitem> - <address> - <otheraddr>JMC Software</otheraddr> - <country>Ireland</country> - Phone: <phone>353 1 6291282</phone> - WWW: <otheraddr><ulink url="http://www.thelinuxmall.com"></ulink></otheraddr>; - </address> - </listitem> - - <listitem> - <address> - <otheraddr>Linux Distro UK</otheraddr> - <street>42 Wharfedale Road</street> - <city>Margate</city> - <postcode>CT9 2TB</postcode> - <country>United Kingdom</country> - WWW: <otheraddr><ulink url="https://linux-distro.co.uk/"></ulink></otheraddr>; - </address> - </listitem> - - <listitem> - <address> - <otheraddr>The Linux Emporium</otheraddr> - <street>Hilliard House, Lester Way</street> - <city>Wallingford</city> - <postcode>OX10 9TA</postcode> - <country>United Kingdom</country> - Phone: <phone>+44 1491 837010</phone> - Fax: <fax>+44 1491 837016</fax> - WWW: <otheraddr><ulink url="http://www.linuxemporium.co.uk/products/bsd/"></ulink></otheraddr>; - </address> - </listitem> - - <listitem> - <address> - <otheraddr>Linux+ DVD Magazine</otheraddr> - <street>Lewartowskiego 6</street> - <city>Warsaw</city> - <postcode>00-190</postcode> - <country>Poland</country> - Phone: <phone>+48 22 860 18 18</phone> - Email: <email>editors@lpmagazine.org</email> - WWW: <otheraddr><ulink url="http://www.lpmagazine.org/"></ulink></otheraddr>; - </address> - </listitem> - - <listitem> - <address> - <otheraddr>Linux System Labs Australia</otheraddr> - <street>21 Ray Drive</street> - <city>Balwyn North</city> - <postcode>VIC - 3104</postcode> - <country>Australia</country> - Phone: <phone>+61 3 9857 5918</phone> - Fax: <fax>+61 3 9857 8974</fax> - WWW: <otheraddr><ulink url="http://www.lsl.com.au"></ulink></otheraddr>; - </address> - </listitem> - - <listitem> - <address> - <otheraddr>LinuxCenter.Ru</otheraddr> - <street>Galernaya Street, 55</street> - <city>Saint-Petersburg</city> - <postcode>190000</postcode> - <country>Russia</country> - Phone: <phone>+7-812-3125208</phone> - Email: <email>info@linuxcenter.ru</email> - WWW: <otheraddr><ulink url="http://linuxcenter.ru/shop/freebsd"></ulink></otheraddr>; - </address> - </listitem> + <itemizedlist> + <listitem> + <address> + <otheraddr>&os; Mall, Inc.</otheraddr> + <street>700 Harvest Park Ste F</street> + <city>Brentwood</city>, + <state>CA</state> + <postcode>94513</postcode> + <country>USA</country> + Phone: <phone>+1 925 240-6652</phone> + Fax: <fax>+1 925 674-0821</fax> + Email: <email>info@freebsdmall.com</email> + WWW: <otheraddr><ulink + url="http://www.freebsdmall.com/"></ulink></otheraddr>; + </address> + </listitem> + + <listitem> + <address> + <otheraddr>Dr. Hinner EDV</otheraddr> + <street>St. Augustinus-Str. 10</street> + <postcode>D-81825</postcode> <city>München</city> + <country>Germany</country> + Phone: <phone>(089) 428 419</phone> + WWW: <otheraddr><ulink + url="http://www.hinner.de/linux/freebsd.html"></ulink></otheraddr>; + </address> + </listitem> + + <listitem> + <address> + <otheraddr>JMC Software</otheraddr> + <country>Ireland</country> + Phone: <phone>353 1 6291282</phone> + WWW: <otheraddr><ulink + url="http://www.thelinuxmall.com"></ulink></otheraddr>; + </address> + </listitem> + + <listitem> + <address> + <otheraddr>Linux Distro UK</otheraddr> + <street>42 Wharfedale Road</street> + <city>Margate</city> + <postcode>CT9 2TB</postcode> + <country>United Kingdom</country> + WWW: <otheraddr><ulink + url="https://linux-distro.co.uk/"></ulink></otheraddr>; + </address> + </listitem> + + <listitem> + <address> + <otheraddr>The Linux Emporium</otheraddr> + <street>Hilliard House, Lester Way</street> + <city>Wallingford</city> + <postcode>OX10 9TA</postcode> + <country>United Kingdom</country> + Phone: <phone>+44 1491 837010</phone> + Fax: <fax>+44 1491 837016</fax> + WWW: <otheraddr><ulink + url="http://www.linuxemporium.co.uk/products/bsd/"></ulink></otheraddr>; + </address> + </listitem> + + <listitem> + <address> + <otheraddr>Linux+ DVD Magazine</otheraddr> + <street>Lewartowskiego 6</street> + <city>Warsaw</city> + <postcode>00-190</postcode> + <country>Poland</country> + Phone: <phone>+48 22 860 18 18</phone> + Email: <email>editors@lpmagazine.org</email> + WWW: <otheraddr><ulink + url="http://www.lpmagazine.org/"></ulink></otheraddr>; + </address> + </listitem> + + <listitem> + <address> + <otheraddr>Linux System Labs Australia</otheraddr> + <street>21 Ray Drive</street> + <city>Balwyn North</city> + <postcode>VIC - 3104</postcode> + <country>Australia</country> + Phone: <phone>+61 3 9857 5918</phone> + Fax: <fax>+61 3 9857 8974</fax> + WWW: <otheraddr><ulink + url="http://www.lsl.com.au"></ulink></otheraddr>; + </address> + </listitem> - </itemizedlist> + <listitem> + <address> + <otheraddr>LinuxCenter.Ru</otheraddr> + <street>Galernaya Street, 55</street> + <city>Saint-Petersburg</city> + <postcode>190000</postcode> + <country>Russia</country> + Phone: <phone>+7-812-3125208</phone> + Email: <email>info@linuxcenter.ru</email> + WWW: <otheraddr><ulink + url="http://linuxcenter.ru/shop/freebsd"></ulink></otheraddr>; + </address> + </listitem> + </itemizedlist> </sect2> <sect2> <title>Distributors</title> - <para>If you are a reseller and want to carry &os; CDROM products, - please contact a distributor:</para> + <para>If you are a reseller and want to carry &os; CDROM + products, please contact a distributor:</para> <itemizedlist> - <listitem> + <listitem> <address> <otheraddr>Ingram Micro</otheraddr> <street>1600 E. St. Andrew Place</street> - <city>Santa Ana</city>, <state>CA</state> <postcode>92705-4926</postcode> + <city>Santa Ana</city>, + <state>CA</state> + <postcode>92705-4926</postcode> <country>USA</country> Phone: <phone>1 (800) 456-8000</phone> - WWW: <otheraddr><ulink url="http://www.ingrammicro.com/"></ulink></otheraddr>; - </address> - </listitem> + WWW: <otheraddr><ulink + url="http://www.ingrammicro.com/"></ulink></otheraddr>; + </address> + </listitem> <listitem> <address> <otheraddr>Kudzu, LLC</otheraddr> <street>7375 Washington Ave. S.</street> - <city>Edina</city>, <state>MN</state> <postcode>55439</postcode> + <city>Edina</city>, + <state>MN</state> + <postcode>55439</postcode> <country>USA</country> Phone: <phone>+1 952 947-0822</phone> Fax: <fax>+1 952 947-0876</fax> @@ -173,7 +188,8 @@ <country>Russia</country> Phone: <phone>+7-812-3125208</phone> Email: <email>info@linuxcenter.ru</email> - WWW: <otheraddr><ulink url="http://linuxcenter.ru/freebsd"></ulink></otheraddr>; + WWW: <otheraddr><ulink + url="http://linuxcenter.ru/freebsd"></ulink></otheraddr>; </address> </listitem> </itemizedlist> @@ -183,8 +199,8 @@ <sect1 id="mirrors-ftp"> <title>FTP Sites</title> - <para>The official sources for &os; are available via anonymous FTP - from a worldwide set of mirror sites. The site + <para>The official sources for &os; are available via anonymous + FTP from a worldwide set of mirror sites. The site <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/"></ulink>; is well connected and allows a large number of connections to it, but you are probably better off finding a <quote>closer</quote> @@ -192,17 +208,18 @@ mirror site).</para> <para>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 - <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 but some sites also provide access via other methods. The access - methods available for each site are provided in parentheses - after the hostname.</para> + 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 <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 + but some sites also provide access via other methods. The + access methods available for each site are provided in + parentheses after the hostname.</para> &chap.mirrors.ftp.inc; </sect1> @@ -217,15 +234,15 @@ <para>The ISO images for the basic release CDs are available via BitTorrent. A collection of torrent files to download the images is available at <ulink - url="http://torrents.freebsd.org:8080/">http://torrents.freebsd.org:8080</ulink></para>; + url="http://torrents.freebsd.org:8080/">http://torrents.freebsd.org:8080</ulink></para>; <para>The BitTorrent client software is available from the <filename role="package">net-p2p/py-bittorrent</filename> port, or a precompiled package.</para> <para>After downloading the ISO image with BitTorrent, you may - burn it to CD or DVD media as described in <xref - linkend="burncd"/>, burncd.</para> + burn it to CD or DVD media as described in + <xref linkend="burncd"/>, burncd.</para> </sect1> <sect1 id="mirrors-svn"> @@ -330,569 +347,595 @@ </informaltable> </sect1> - <sect1 id="anoncvs"> - <title>Anonymous CVS</title> + <sect1 id="anoncvs"> + <title>Anonymous CVS</title> + + <sect2> + <title><anchor id="anoncvs-intro"/>Introduction</title> + + <indexterm> + <primary>CVS</primary> + <secondary>anonymous</secondary> + </indexterm> + + <para>Anonymous CVS (or, as it is otherwise known, + <emphasis>anoncvs</emphasis>) 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 + <envar>CVSROOT</envar> environment variable to point at the + appropriate anoncvs server, provides the well-known password + <quote>anoncvs</quote> with the <command>cvs login</command> + command, and then uses the &man.cvs.1; command to access it + like any local repository.</para> + + <note> + <para>The <command>cvs login</command> command, stores the + passwords that are used for authenticating to the CVS server + in a file called <filename>.cvspass</filename> in your + <envar>HOME</envar> directory. If this file does not exist, + you might get an error when trying to use + <command>cvs login</command> for the first time. Just make + an empty <filename>.cvspass</filename> file, and retry to + login.</para> + </note> + + <para>While it can also be said that the + <link linkend="cvsup">CVSup</link> and + <emphasis>anoncvs</emphasis> 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, <application>CVSup</application> 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 <application>CVSup</application>, a special client must + first be installed and configured before any bits can be + grabbed, and then only in the fairly large chunks which + <application>CVSup</application> calls + <emphasis>collections</emphasis>.</para> + + <para><application>Anoncvs</application>, by contrast, can be + used to examine anything from an individual file to a specific + program (like <command>ls</command> or + <command>grep</command>) by referencing the CVS module name. + Of course, <application>anoncvs</application> 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 + <application>CVSup</application> is really your only + option.</para> + </sect2> + + <sect2> + <title><anchor id="anoncvs-usage"/>Using Anonymous CVS</title> - <sect2> - <title><anchor id="anoncvs-intro"/>Introduction</title> + <para>Configuring &man.cvs.1; to use an Anonymous CVS repository + is a simple matter of setting the <envar>CVSROOT</envar> + environment variable to point to one of the &os; project's + <emphasis>anoncvs</emphasis> servers. At the time of this + writing, the following servers are available:</para> - <indexterm> - <primary>CVS</primary> - <secondary>anonymous</secondary> - </indexterm> - - <para>Anonymous CVS (or, as it is otherwise known, - <emphasis>anoncvs</emphasis>) 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 <envar>CVSROOT</envar> - environment variable to point at the appropriate anoncvs server, - provides the well-known password <quote>anoncvs</quote> with the - <command>cvs login</command> command, and then uses the - &man.cvs.1; command to access it like any local - repository.</para> - - <note> - <para>The <command>cvs login</command> command, stores the passwords - that are used for authenticating to the CVS server in a file - called <filename>.cvspass</filename> in your - <envar>HOME</envar> directory. If this file does not exist, - you might get an error when trying to use <command>cvs - login</command> for the first time. Just make an empty - <filename>.cvspass</filename> file, and retry to login.</para> - </note> - - <para>While it can also be said that the <link - linkend="cvsup">CVSup</link> and <emphasis>anoncvs</emphasis> - 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, - <application>CVSup</application> 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 - <application>CVSup</application>, a special client must first be - installed and configured before any bits can be grabbed, and - then only in the fairly large chunks which - <application>CVSup</application> calls - <emphasis>collections</emphasis>.</para> - - <para><application>Anoncvs</application>, by contrast, can be used - to examine anything from an individual file to a specific - program (like <command>ls</command> or <command>grep</command>) - by referencing the CVS module name. Of course, - <application>anoncvs</application> 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 - <application>CVSup</application> is really your only - option.</para> - </sect2> - - <sect2> - <title><anchor id="anoncvs-usage"/>Using Anonymous CVS</title> - - <para>Configuring &man.cvs.1; to use an Anonymous CVS repository - is a simple matter of setting the <envar>CVSROOT</envar> - environment variable to point to one of the &os; project's - <emphasis>anoncvs</emphasis> servers. At the time of this - writing, the following servers are available:</para> - - <itemizedlist> - <listitem> - <para><emphasis>France</emphasis>: - :pserver:anoncvs@anoncvs.fr.FreeBSD.org:/home/ncvs - (For pserver mode, use <command>cvs login</command> and - enter the password <quote>anoncvs</quote> when prompted. - For ssh, no password is required.)</para> - </listitem> - <!-- - <listitem> - <para><emphasis>Japan</emphasis>: - :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs - (Use <command>cvs login</command> and enter the password - <quote>anoncvs</quote> when prompted.)</para> - </listitem> - --> - <listitem> - <para><emphasis>Taiwan</emphasis>: - :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs - (For pserver mode, use <command>cvs login</command> and - enter any password when prompted. For ssh, no password - is required.)</para> + <itemizedlist> + <listitem> + <para><emphasis>France</emphasis>: + :pserver:anoncvs@anoncvs.fr.FreeBSD.org:/home/ncvs + (For pserver mode, use <command>cvs login</command> and + enter the password <quote>anoncvs</quote> when prompted. + For ssh, no password is required.)</para> + </listitem> + <!-- + <listitem> + <para><emphasis>Japan</emphasis>: + :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs + (Use <command>cvs login</command> and enter the password + <quote>anoncvs</quote> when prompted.)</para> + </listitem> + --> + <listitem> + <para><emphasis>Taiwan</emphasis>: + :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs + (For pserver mode, use <command>cvs login</command> and + enter any password when prompted. For ssh, no password + is required.)</para> - <programlisting>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 + <programlisting>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</programlisting> - </listitem> - <!-- - <listitem> - <para><emphasis>USA</emphasis>: - anoncvs@anoncvs1.FreeBSD.org:/home/ncvs (For ssh, use ssh - version 2 and no password is required.)</para> - - <programlisting>SSH2 HostKey: 2048 53:1f:15:a3:72:5c:43:f6:44:0e:6a:e9:bb:f8:01:62 /etc/ssh/ssh_host_dsa_key.pub</programlisting> - - </listitem> - --> - </itemizedlist> - - <para>Since CVS allows one to <quote>check out</quote> virtually - any version of the &os; sources that ever existed (or, in - some cases, will exist), you need to be - familiar with the revision (<option>-r</option>) flag to - &man.cvs.1; and what some of the permissible values for it in - the &os; Project repository are.</para> - - <para>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.</para> - - <para><xref linkend="cvs-tags"/> 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.</para> - - <para>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 <option>-D date</option> flag. - See the &man.cvs.1; manual page for more details.</para> - </sect2> - - <sect2> - <title>Examples</title> - - <para>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:</para> + </listitem> + <!-- + <listitem> + <para><emphasis>USA</emphasis>: + anoncvs@anoncvs1.FreeBSD.org:/home/ncvs (For ssh, use ssh + version 2 and no password is required.)</para> + + <programlisting>SSH2 HostKey: 2048 53:1f:15:a3:72:5c:43:f6:44:0e:6a:e9:bb:f8:01:62 /etc/ssh/ssh_host_dsa_key.pub</programlisting> + + </listitem> + --> + </itemizedlist> + + <para>Since CVS allows one to <quote>check out</quote> virtually + any version of the &os; sources that ever existed (or, in some + cases, will exist), you need to be familiar with the revision + (<option>-r</option>) flag to &man.cvs.1; and what some of the + permissible values for it in the &os; Project repository + are.</para> + + <para>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.</para> + + <para><xref linkend="cvs-tags"/> 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.</para> + + <para>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 <option>-D date</option> flag. See + the &man.cvs.1; manual page for more details.</para> + </sect2> - <example> - <title>Checking Out Something from -CURRENT (&man.ls.1;):</title> + <sect2> + <title>Examples</title> + + <para>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:</para> + + <example> + <title>Checking Out Something from -CURRENT + (&man.ls.1;):</title> - <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput> + <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput> &prompt.user; <userinput>cvs login</userinput> <emphasis>At the prompt, enter any word for</emphasis> <quote>password</quote>. &prompt.user; <userinput>cvs co ls</userinput> - </screen> - </example> + </screen> + </example> - <example> - <title>Using SSH to Check Out the <filename>src/</filename> - Tree:</title> - <screen>&prompt.user; <userinput>cvs -d anoncvs@anoncvs1.FreeBSD.org:/home/ncvs co src</userinput> + <example> + <title>Using SSH to Check Out the <filename>src/</filename> + Tree:</title> + + <screen>&prompt.user; <userinput>cvs -d anoncvs@anoncvs1.FreeBSD.org:/home/ncvs co src</userinput> 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)? <userinput>yes</userinput> Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hosts.</screen> - </example> + </example> - <example> - <title>Checking Out the Version of &man.ls.1; in the 8-STABLE - Branch:</title> + <example> + <title>Checking Out the Version of &man.ls.1; in the 8-STABLE + Branch:</title> - <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput> + <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput> &prompt.user; <userinput>cvs login</userinput> <emphasis>At the prompt, enter any word for</emphasis> <quote>password</quote>. &prompt.user; <userinput>cvs co -rRELENG_8 ls</userinput> - </screen> - </example> + </screen> + </example> - <example> - <title>Creating a List of Changes (as Unified Diffs) to &man.ls.1;</title> + <example> + <title>Creating a List of Changes (as Unified Diffs) to + &man.ls.1;</title> - <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput> + <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput> &prompt.user; <userinput>cvs login</userinput> <emphasis>At the prompt, enter any word for</emphasis> <quote>password</quote>. &prompt.user; <userinput>cvs rdiff -u -rRELENG_8_0_0_RELEASE -rRELENG_8_1_0_RELEASE ls</userinput> - </screen> - </example> + </screen> + </example> - <example> - <title>Finding Out What Other Module Names Can Be Used:</title> + <example> + <title>Finding Out What Other Module Names Can Be + Used:</title> - <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput> + <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput> &prompt.user; <userinput>cvs login</userinput> <emphasis>At the prompt, enter any word for</emphasis> <quote>password</quote>. &prompt.user; <userinput>cvs co modules</userinput> &prompt.user; <userinput>more modules/modules</userinput> - </screen> - </example> - </sect2> - - <sect2> - <title>Other Resources</title> + </screen> + </example> + </sect2> - <para>The following additional resources may be helpful in learning - CVS:</para> + <sect2> + <title>Other Resources</title> - <itemizedlist> - <listitem> - <para><ulink - url="http://users.csc.calpoly.edu/~gfisher/classes/308/handouts/cvs-basics.html">CVS Tutorial</ulink> from California - Polytechnic State University.</para> - </listitem> + <para>The following additional resources may be helpful in + learning CVS:</para> - <listitem> - <para><ulink url="http://www.nongnu.org/cvs/">CVS Home</ulink>, - the CVS development and support community.</para> - </listitem> + <itemizedlist> + <listitem> + <para><ulink + url="http://users.csc.calpoly.edu/~gfisher/classes/308/handouts/cvs-basics.html">CVS + Tutorial</ulink> from California Polytechnic State + University.</para> + </listitem> - <listitem> - <para><ulink - url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVSweb</ulink>; is - the &os; Project web interface for CVS.</para> - </listitem> - </itemizedlist> - </sect2> - </sect1> + <listitem> + <para><ulink url="http://www.nongnu.org/cvs/">CVS + Home</ulink>, the CVS development and support + community.</para> + </listitem> + <listitem> + <para><ulink + url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVSweb</ulink>; + is the &os; Project web interface for CVS.</para> + </listitem> + </itemizedlist> + </sect2> + </sect1> <sect1 id="ctm"> <title>Using CTM</title> - <indexterm> - <primary>CTM</primary> - </indexterm> + <indexterm> + <primary>CTM</primary> + </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> + + <sect2> + <title>Why Should I Use <application>CTM</application>?</title> + + <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 + 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> + + <sect2> + <title>What Do I Need to Use + <application>CTM</application>?</title> - <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> - - <sect2> - <title>Why Should I Use <application>CTM</application>?</title> - - <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 - 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> - - <sect2> - <title>What Do I Need to Use - <application>CTM</application>?</title> - - <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> - - <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> 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> + <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> + + <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> 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> - <para><ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/"></ulink></para>; + <para><ulink + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/"></ulink></para>; - <para>or see section <link + <para>or see section <link linkend="mirrors-ctm">mirrors</link>.</para> - <para>FTP the relevant directory and fetch the - <filename>README</filename> file, starting from there.</para> + <para>FTP the relevant directory and fetch the + <filename>README</filename> file, starting from there.</para> + + <para>If you wish to get your deltas via email:</para> + + <para>Subscribe to one of the + <application>CTM</application> 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.)</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 + 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> + </note> + </sect2> + + <sect2> + <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>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.</para> + + <para>You can recognize these <quote>starter</quote> deltas by + the <literal>X</literal> appended to the number + (<filename>src-cur.3210XEmpty.gz</filename> for instance). + The designation following the <literal>X</literal> corresponds + to the origin of your initial <quote>seed</quote>. + <filename>Empty</filename> is an empty directory. As a rule a + base transition from <literal>Empty</literal> is produced + every 100 deltas. By the way, they are large! 70 to 80 + Megabytes of <command>gzip</command>'d data is common for the + <filename>XEmpty</filename> deltas.</para> - <para>If you wish to get your deltas via email:</para> + <para>Once you have picked a base delta to start from, you will + also need all deltas with higher numbers following it.</para> + </sect2> - <para>Subscribe to one of the - <application>CTM</application> 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.)</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 - 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> - </note> - </sect2> - - <sect2> - <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> - *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201210102314.q9ANEc3t019048>