Generally there are two ways

          Generally there are two ways

          to access a CVS repository remotely: via

          to access a CVS repository remotely: via

          <emphasis>pserver</emphasis> or via <command>ssh</command>

          <emphasis>pserver</emphasis> or via <command>ssh</command>

          For anonymous access, <emphasis>pserver</emphasis> is

          For anonymous access, <emphasis>pserver</emphasis> is

          very well suited, but some still offer <command>ssh</command>

          very well suited, but some still offer <command>ssh</command>

          access as well. There is a custom crafted

          access as well. There is a custom crafted

          anonymous user's home-directory.   This may not be possible

          anonymous user's home-directory.   This may not be possible

          for all sites. If you just offer <emphasis>pserver</emphasis>

          for all sites. If you just offer <emphasis>pserver</emphasis>

          this restriction does not apply, but you may run with

          this restriction does not apply, but you may run with

          software, since &man.cvs.1; comes with

          software, since &man.cvs.1; comes with

          FreeBSD. You need to enable access via <command>inetd</command>,

          FreeBSD. You need to enable access via <command>inetd</command>,

          so add an entry into your <filename>/etc/inetd.conf</filename>

          so add an entry into your <filename>/etc/inetd.conf</filename>

        <filename role="package">textproc/docproj</filename> port must be

        <filename role="package">textproc/docproj</filename> port must be

        installed.</para></note>

        installed.</para></note>

      <para>

      <para>

        <application>CVSup</application> to maintain an <quote>up to date copy</quote>

        <application>CVSup</application> to maintain an <quote>up to date copy</quote>

        of the www pages. A sample supfile can be found in

        of the www pages. A sample supfile can be found in

        <filename>/usr/share/examples/cvsup/www-supfile</filename> and

        <filename>/usr/share/examples/cvsup/www-supfile</filename> and

         environment variables, like

         environment variables, like

         <literal>SGML_CATALOG_FILES</literal>.

         <literal>SGML_CATALOG_FILES</literal>.

         Also have a look at your <filename>/etc/make.conf</filename>

         Also have a look at your <filename>/etc/make.conf</filename>

         you do not have one), and look at the

         you do not have one), and look at the

         <literal>DOC_LANG</literal> variable.

         <literal>DOC_LANG</literal> variable.

         Now you are probably ready to run <command>make</command>

         Now you are probably ready to run <command>make</command>

         by default) and build the documentation.

         by default) and build the documentation.

         Again you need to make it accessible for your web server

         Again you need to make it accessible for your web server

         and make sure the links point to the right location.

         and make sure the links point to the right location.

         <important>

         <important>

           <para>

           <para>

             The building of the documentation, as well as lots

             The building of the documentation, as well as lots

             <ulink url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/fdp-primer/">fdp-primer</ulink>.

             <ulink url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/fdp-primer/">fdp-primer</ulink>.

             Please read this piece of documentation, especially if you

             Please read this piece of documentation, especially if you

             have problems building the documentation.

             have problems building the documentation.

        </procedure>

        </procedure>

      </sect3>

      </sect3>

      <sect3 id="mirror-where-official">

      <sect3 id="mirror-where-official">

        <para>

        <para>

          In general the description in <xref linkend="mirror-where-simple">

          In general the description in <xref linkend="mirror-where-simple">

          still applies. Of course you may want to put some

          still applies. Of course you may want to put some

        </para>

        </para>

        <para>

        <para>

          It is also important that hub administrators try to keep their mirrors as up-to-date as

          It is also important that hub administrators try to keep their mirrors as up-to-date as

          while, lower tier mirrors will begin to mirror old data from Mirror1 and thus begins

          while, lower tier mirrors will begin to mirror old data from Mirror1 and thus begins

          a downward spiral... Keep your mirrors up to date!

          a downward spiral... Keep your mirrors up to date!

        </para>

        </para>