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

Move the "mirrors-cvsup" ID attribute to the correct element. Some

Browse source 
internal links now work properly.  Pointed out by a cast of thousands.

Move the anonymous CVS stuff out of the cutting-edge chapter and into the
mirrors appendix.  As with the other commits in this series, this was a
straight cut-n-paste from one file to another, *and* then updating the
<sect?> elements to promote everything up a level.
This commit is contained in:
Nik Clayton 2000-07-16 16:41:55 +00:00
parent d059ff5c85
commit ddb9cef979
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7634
4 changed files with 666 additions and 666 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

331
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.50 2000/06/16 19:52:36 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.51 2000/06/16 22:01:54 jim Exp $
-->
<chapter id="cutting-edge">
@ -447,335 +447,6 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<application>CTM</application>, and
<application>CVSup</application> is available further down in this
section.</para>
<sect2 id="anoncvs">
<title>Anonymous CVS</title>
<sect3>
<title><anchor id="anoncvs-intro">Introduction</title>
<para>Anonymous CVS (or, as it is otherwise known,
<emphasis>anoncvs</emphasis>) is a feature provided by the CVS
utilities bundled with FreeBSD for synchronizing with a remote
CVS repository. Among other things, it allows users of FreeBSD
to perform, with no special privileges, read-only CVS operations
against one of the FreeBSD 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>
<para>While it can also be said that the <link
linkend="mirrors-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's your
intention to support local development in one repository shared
with the FreeBSD project bits then
<application>CVSup</application> is really your only
option.</para>
</sect3>
<sect3>
<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 FreeBSD project's
<emphasis>anoncvs</emphasis> servers. At the time of this
writing, the following servers are available:</para>
<itemizedlist>
<listitem>
<para><emphasis>USA</emphasis>:
:pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs
(Use <command>cvs login</command> and enter the password
<quote>anoncvs</quote> when prompted.)</para>
</listitem>
</itemizedlist>
<para>Since CVS allows one to <quote>check out</quote> virtually
any version of the FreeBSD sources that ever existed (or, in
some cases, will exist <!-- smiley -->:-), 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 FreeBSD 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>Here are the branch tags that users might be interested
in (keep in mind that the only tags valid for the <link
linkend="ports">ports collection</link> is
<literal>HEAD</literal>).</para>
<variablelist>
<varlistentry>
<term>HEAD</term>
<listitem>
<para>Symbolic name for the main line, or FreeBSD-CURRENT.
Also the default when no revision is specified.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_4</term>
<listitem>
<para>The line of development for FreeBSD-4.X, also known
as FreeBSD-STABLE.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3</term>
<listitem>
<para>The line of development for FreeBSD-3.X, also known
as 3.X-STABLE.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.X, also known
as 2.2-STABLE. This branch is mostly obsolete.</para>
</listitem>
</varlistentry>
</variablelist>
<para>Here are the 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
revisions.</para>
<variablelist>
<varlistentry>
<term>RELENG_4_0_0_RELEASE</term>
<listitem>
<para>FreeBSD 4.0.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_4_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.4.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_3_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.3.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_2_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.2.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_1_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.1.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_0_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.0.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_8_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.8.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_7_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.7.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_6_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.6.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_5_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.5.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_2_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.2.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_1_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.1.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_0_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.0.</para>
</listitem>
</varlistentry>
</variablelist>
<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; man page for more details.</para>
</sect3>
<sect3>
<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;) and
deleting it again:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Checking out the version of &man.ls.1; in the 3.X-STABLE
branch:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co -rRELENG_3 ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Creating a list of changes (as unified diffs) to &man.ls.1;</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs rdiff -u -rRELENG_3_0_0_RELEASE -rRELENG_3_4_0_RELEASE ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Finding out what other module names can be used:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co modules</userinput>
&prompt.user; <userinput>more modules/modules</userinput>
&prompt.user; <userinput>cvs release -d modules</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
</sect3>
<sect3>
<title>Other Resources</title>
<para>The following additional resources may be helpful in learning
CVS:</para>
<itemizedlist>
<listitem>
<para><ulink
url="http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/cvs/">CVS Tutorial</ulink> from Cal Poly.</para>
</listitem>
<listitem>
<para><ulink url="http://www.cyclic.com/">Cyclic Software</ulink>,
commercial maintainers of CVS.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVSWeb</ulink> is
the FreeBSD Project web interface for CVS.</para>
</listitem>
</itemizedlist>
</sect3>
</sect2>
</sect1>
<sect1 id="makeworld">

335
en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.74 2000/07/09 18:09:37 alex Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.75 2000/07/15 06:00:55 kuriyama Exp $
-->
<appendix id="mirrors">
@ -822,6 +822,335 @@
</variablelist>
</sect1>
<sect1 id="anoncvs">
<title>Anonymous CVS</title>
<sect2>
<title><anchor id="anoncvs-intro">Introduction</title>
<para>Anonymous CVS (or, as it is otherwise known,
<emphasis>anoncvs</emphasis>) is a feature provided by the CVS
utilities bundled with FreeBSD for synchronizing with a remote
CVS repository. Among other things, it allows users of FreeBSD
to perform, with no special privileges, read-only CVS operations
against one of the FreeBSD 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>
<para>While it can also be said that the <link
linkend="mirrors-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's your
intention to support local development in one repository shared
with the FreeBSD 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 FreeBSD project's
<emphasis>anoncvs</emphasis> servers. At the time of this
writing, the following servers are available:</para>
<itemizedlist>
<listitem>
<para><emphasis>USA</emphasis>:
:pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs
(Use <command>cvs login</command> and enter the password
<quote>anoncvs</quote> when prompted.)</para>
</listitem>
</itemizedlist>
<para>Since CVS allows one to <quote>check out</quote> virtually
any version of the FreeBSD sources that ever existed (or, in
some cases, will exist <!-- smiley -->:-), 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 FreeBSD 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>Here are the branch tags that users might be interested
in (keep in mind that the only tags valid for the <link
linkend="ports">ports collection</link> is
<literal>HEAD</literal>).</para>
<variablelist>
<varlistentry>
<term>HEAD</term>
<listitem>
<para>Symbolic name for the main line, or FreeBSD-CURRENT.
Also the default when no revision is specified.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_4</term>
<listitem>
<para>The line of development for FreeBSD-4.X, also known
as FreeBSD-STABLE.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3</term>
<listitem>
<para>The line of development for FreeBSD-3.X, also known
as 3.X-STABLE.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.X, also known
as 2.2-STABLE. This branch is mostly obsolete.</para>
</listitem>
</varlistentry>
</variablelist>
<para>Here are the 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
revisions.</para>
<variablelist>
<varlistentry>
<term>RELENG_4_0_0_RELEASE</term>
<listitem>
<para>FreeBSD 4.0.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_4_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.4.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_3_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.3.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_2_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.2.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_1_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.1.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_0_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.0.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_8_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.8.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_7_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.7.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_6_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.6.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_5_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.5.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_2_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.2.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_1_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.1.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_0_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.0.</para>
</listitem>
</varlistentry>
</variablelist>
<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; man 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>
<example>
<title>Checking out something from -CURRENT (&man.ls.1;) and
deleting it again:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Checking out the version of &man.ls.1; in the 3.X-STABLE
branch:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co -rRELENG_3 ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Creating a list of changes (as unified diffs) to &man.ls.1;</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs rdiff -u -rRELENG_3_0_0_RELEASE -rRELENG_3_4_0_RELEASE ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Finding out what other module names can be used:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co modules</userinput>
&prompt.user; <userinput>more modules/modules</userinput>
&prompt.user; <userinput>cvs release -d modules</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
</sect2>
<sect2>
<title>Other Resources</title>
<para>The following additional resources may be helpful in learning
CVS:</para>
<itemizedlist>
<listitem>
<para><ulink
url="http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/cvs/">CVS Tutorial</ulink> from Cal Poly.</para>
</listitem>
<listitem>
<para><ulink url="http://www.cyclic.com/">Cyclic Software</ulink>,
commercial maintainers of CVS.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVSWeb</ulink> is
the FreeBSD Project web interface for CVS.</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="ctm">
<title>Using CTM</title>
@ -1190,7 +1519,7 @@
FTP search is a great free archie server in Trondheim, Norway.</para>
</sect2></sect1>
<sect1 id="mirrors-cvsup">
<sect1>
<title>Using CVSup</title>
<sect2 id="cvsup-intro">
@ -2611,7 +2940,7 @@ src-all</programlisting>
of the program at <email>cvsup-bugs@polstra.com</email>.</para>
</sect2>
<sect2>
<sect2 id="mirrors-cvsup">
<title>CVSup Sites</title>
<para><link linkend="mirrors-cvsup">CVSup</link> servers for FreeBSD are running

331
en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.50 2000/06/16 19:52:36 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.51 2000/06/16 22:01:54 jim Exp $
-->
<chapter id="cutting-edge">
@ -447,335 +447,6 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<application>CTM</application>, and
<application>CVSup</application> is available further down in this
section.</para>
<sect2 id="anoncvs">
<title>Anonymous CVS</title>
<sect3>
<title><anchor id="anoncvs-intro">Introduction</title>
<para>Anonymous CVS (or, as it is otherwise known,
<emphasis>anoncvs</emphasis>) is a feature provided by the CVS
utilities bundled with FreeBSD for synchronizing with a remote
CVS repository. Among other things, it allows users of FreeBSD
to perform, with no special privileges, read-only CVS operations
against one of the FreeBSD 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>
<para>While it can also be said that the <link
linkend="mirrors-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's your
intention to support local development in one repository shared
with the FreeBSD project bits then
<application>CVSup</application> is really your only
option.</para>
</sect3>
<sect3>
<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 FreeBSD project's
<emphasis>anoncvs</emphasis> servers. At the time of this
writing, the following servers are available:</para>
<itemizedlist>
<listitem>
<para><emphasis>USA</emphasis>:
:pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs
(Use <command>cvs login</command> and enter the password
<quote>anoncvs</quote> when prompted.)</para>
</listitem>
</itemizedlist>
<para>Since CVS allows one to <quote>check out</quote> virtually
any version of the FreeBSD sources that ever existed (or, in
some cases, will exist <!-- smiley -->:-), 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 FreeBSD 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>Here are the branch tags that users might be interested
in (keep in mind that the only tags valid for the <link
linkend="ports">ports collection</link> is
<literal>HEAD</literal>).</para>
<variablelist>
<varlistentry>
<term>HEAD</term>
<listitem>
<para>Symbolic name for the main line, or FreeBSD-CURRENT.
Also the default when no revision is specified.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_4</term>
<listitem>
<para>The line of development for FreeBSD-4.X, also known
as FreeBSD-STABLE.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3</term>
<listitem>
<para>The line of development for FreeBSD-3.X, also known
as 3.X-STABLE.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.X, also known
as 2.2-STABLE. This branch is mostly obsolete.</para>
</listitem>
</varlistentry>
</variablelist>
<para>Here are the 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
revisions.</para>
<variablelist>
<varlistentry>
<term>RELENG_4_0_0_RELEASE</term>
<listitem>
<para>FreeBSD 4.0.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_4_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.4.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_3_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.3.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_2_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.2.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_1_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.1.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_0_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.0.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_8_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.8.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_7_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.7.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_6_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.6.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_5_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.5.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_2_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.2.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_1_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.1.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_0_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.0.</para>
</listitem>
</varlistentry>
</variablelist>
<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; man page for more details.</para>
</sect3>
<sect3>
<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;) and
deleting it again:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Checking out the version of &man.ls.1; in the 3.X-STABLE
branch:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co -rRELENG_3 ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Creating a list of changes (as unified diffs) to &man.ls.1;</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs rdiff -u -rRELENG_3_0_0_RELEASE -rRELENG_3_4_0_RELEASE ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Finding out what other module names can be used:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co modules</userinput>
&prompt.user; <userinput>more modules/modules</userinput>
&prompt.user; <userinput>cvs release -d modules</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
</sect3>
<sect3>
<title>Other Resources</title>
<para>The following additional resources may be helpful in learning
CVS:</para>
<itemizedlist>
<listitem>
<para><ulink
url="http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/cvs/">CVS Tutorial</ulink> from Cal Poly.</para>
</listitem>
<listitem>
<para><ulink url="http://www.cyclic.com/">Cyclic Software</ulink>,
commercial maintainers of CVS.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVSWeb</ulink> is
the FreeBSD Project web interface for CVS.</para>
</listitem>
</itemizedlist>
</sect3>
</sect2>
</sect1>
<sect1 id="makeworld">

335
en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.74 2000/07/09 18:09:37 alex Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.75 2000/07/15 06:00:55 kuriyama Exp $
-->
<appendix id="mirrors">
@ -822,6 +822,335 @@
</variablelist>
</sect1>
<sect1 id="anoncvs">
<title>Anonymous CVS</title>
<sect2>
<title><anchor id="anoncvs-intro">Introduction</title>
<para>Anonymous CVS (or, as it is otherwise known,
<emphasis>anoncvs</emphasis>) is a feature provided by the CVS
utilities bundled with FreeBSD for synchronizing with a remote
CVS repository. Among other things, it allows users of FreeBSD
to perform, with no special privileges, read-only CVS operations
against one of the FreeBSD 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>
<para>While it can also be said that the <link
linkend="mirrors-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's your
intention to support local development in one repository shared
with the FreeBSD 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 FreeBSD project's
<emphasis>anoncvs</emphasis> servers. At the time of this
writing, the following servers are available:</para>
<itemizedlist>
<listitem>
<para><emphasis>USA</emphasis>:
:pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs
(Use <command>cvs login</command> and enter the password
<quote>anoncvs</quote> when prompted.)</para>
</listitem>
</itemizedlist>
<para>Since CVS allows one to <quote>check out</quote> virtually
any version of the FreeBSD sources that ever existed (or, in
some cases, will exist <!-- smiley -->:-), 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 FreeBSD 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>Here are the branch tags that users might be interested
in (keep in mind that the only tags valid for the <link
linkend="ports">ports collection</link> is
<literal>HEAD</literal>).</para>
<variablelist>
<varlistentry>
<term>HEAD</term>
<listitem>
<para>Symbolic name for the main line, or FreeBSD-CURRENT.
Also the default when no revision is specified.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_4</term>
<listitem>
<para>The line of development for FreeBSD-4.X, also known
as FreeBSD-STABLE.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3</term>
<listitem>
<para>The line of development for FreeBSD-3.X, also known
as 3.X-STABLE.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.X, also known
as 2.2-STABLE. This branch is mostly obsolete.</para>
</listitem>
</varlistentry>
</variablelist>
<para>Here are the 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
revisions.</para>
<variablelist>
<varlistentry>
<term>RELENG_4_0_0_RELEASE</term>
<listitem>
<para>FreeBSD 4.0.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_4_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.4.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_3_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.3.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_2_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.2.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_1_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.1.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3_0_0_RELEASE</term>
<listitem>
<para>FreeBSD-3.0.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_8_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.8.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_7_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.7.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_6_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.6.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_5_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.5.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_2_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.2.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_1_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.1.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2_0_RELEASE</term>
<listitem>
<para>FreeBSD-2.2.0.</para>
</listitem>
</varlistentry>
</variablelist>
<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; man 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>
<example>
<title>Checking out something from -CURRENT (&man.ls.1;) and
deleting it again:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Checking out the version of &man.ls.1; in the 3.X-STABLE
branch:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co -rRELENG_3 ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Creating a list of changes (as unified diffs) to &man.ls.1;</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs rdiff -u -rRELENG_3_0_0_RELEASE -rRELENG_3_4_0_RELEASE ls</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
<example>
<title>Finding out what other module names can be used:</title>
<screen>
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
&prompt.user; <userinput>cvs co modules</userinput>
&prompt.user; <userinput>more modules/modules</userinput>
&prompt.user; <userinput>cvs release -d modules</userinput>
&prompt.user; <userinput>cvs logout</userinput>
</screen>
</example>
</sect2>
<sect2>
<title>Other Resources</title>
<para>The following additional resources may be helpful in learning
CVS:</para>
<itemizedlist>
<listitem>
<para><ulink
url="http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/cvs/">CVS Tutorial</ulink> from Cal Poly.</para>
</listitem>
<listitem>
<para><ulink url="http://www.cyclic.com/">Cyclic Software</ulink>,
commercial maintainers of CVS.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVSWeb</ulink> is
the FreeBSD Project web interface for CVS.</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="ctm">
<title>Using CTM</title>
@ -1190,7 +1519,7 @@
FTP search is a great free archie server in Trondheim, Norway.</para>
</sect2></sect1>
<sect1 id="mirrors-cvsup">
<sect1>
<title>Using CVSup</title>
<sect2 id="cvsup-intro">
@ -2611,7 +2940,7 @@ src-all</programlisting>
of the program at <email>cvsup-bugs@polstra.com</email>.</para>
</sect2>
<sect2>
<sect2 id="mirrors-cvsup">
<title>CVSup Sites</title>
<para><link linkend="mirrors-cvsup">CVSup</link> servers for FreeBSD are running