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

Remove trailing whitespaces.

Browse source
This commit is contained in:
Jun Kuriyama 2004-03-18 00:21:04 +00:00
parent 0d45e5a025
commit 6add184c97
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=20354
1 changed files with 46 additions and 46 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

92
en_US.ISO8859-1/articles/hubs/article.sgml
View file

@ -25,10 +25,10 @@
</affiliation> </affiliation>
</author> </author>
<author> <author>
<firstname>Valentino</firstname> <firstname>Valentino</firstname>
<surname>Vaschetto</surname> <surname>Vaschetto</surname>
<affiliation> <affiliation>
<address><email>logo@FreeBSD.org</email></address> <address><email>logo@FreeBSD.org</email></address>
</affiliation> </affiliation>
</author> </author>
<author> <author>
@ -120,10 +120,10 @@
which is determined by the server's policy. It is which is determined by the server's policy. It is
also affected by the types of services you want to offer. also affected by the types of services you want to offer.
Plain FTP or HTTP services may not require a huge Plain FTP or HTTP services may not require a huge
amount of resources. Watch out if you provide amount of resources. Watch out if you provide
CVSup, rsync or even AnonCVS. This can have a huge CVSup, rsync or even AnonCVS. This can have a huge
impact on CPU and memory requirements. Especially impact on CPU and memory requirements. Especially
rsync is considered a memory hog, and CVSup does rsync is considered a memory hog, and CVSup does
indeed consume some CPU. For AnonCVS it might indeed consume some CPU. For AnonCVS it might
be a nice idea to set up a memory resident file system (MFS) of at least be a nice idea to set up a memory resident file system (MFS) of at least
300 MB, so you need to take this into account 300 MB, so you need to take this into account
@ -222,14 +222,14 @@
<title>RSYNC (optional for FTP fileset)</title> <title>RSYNC (optional for FTP fileset)</title>
<para> <para>
<application>rsync</application> is often offered for access to the <application>rsync</application> is often offered for access to the
contents of the FTP area of FreeBSD, so other mirror sites can use your system as their source. The contents of the FTP area of FreeBSD, so other mirror sites can use your system as their source. The
protocol is different from FTP in many ways. protocol is different from FTP in many ways.
It is much more It is much more
bandwidth friendly, as only differences between files bandwidth friendly, as only differences between files
are transferred instead of whole files when they change. are transferred instead of whole files when they change.
<application>rsync</application> does require a significant amount of memory for <application>rsync</application> does require a significant amount of memory for
each instance. The size depends on the size of each instance. The size depends on the size of
the synced module in terms of the number of directories and the synced module in terms of the number of directories and
files. <application>rsync</application> can use <command>rsh</command> and files. <application>rsync</application> can use <command>rsh</command> and
<command>ssh</command> (now default) as a transport, <command>ssh</command> (now default) as a transport,
or use its own protocol for stand-alone access or use its own protocol for stand-alone access
@ -290,13 +290,13 @@
offering it via <application>CVSup</application>. It is possible to offer offering it via <application>CVSup</application>. It is possible to offer
the CVS repository via <application>AnonCVS</application>, FTP, the CVS repository via <application>AnonCVS</application>, FTP,
<application>Rsync</application> or HTTP, but <application>Rsync</application> or HTTP, but
people would benefit much more from <application>CVSup</application> access. people would benefit much more from <application>CVSup</application> access.
<application>CVSup</application> was developed by &a.jdp;. <application>CVSup</application> was developed by &a.jdp;.
It is a bit tricky to install on non-FreeBSD platforms, It is a bit tricky to install on non-FreeBSD platforms,
since it is written in Modula-3 and therefore requires since it is written in Modula-3 and therefore requires
a Modula-3 environment. John Polstra has built a a Modula-3 environment. John Polstra has built a
stripped down version of M3 that is sufficient to stripped down version of M3 that is sufficient to
run <application>CVSup</application>, and can be installed much easier. run <application>CVSup</application>, and can be installed much easier.
See <ulink url="http://www.polstra.com/projects/freeware/ezm3/">Ezm3</ulink> See <ulink url="http://www.polstra.com/projects/freeware/ezm3/">Ezm3</ulink>
for details. Related ports are: for details. Related ports are:
@ -315,18 +315,18 @@
There are a few more like There are a few more like
<filename role="package">net/cvsup-without-gui</filename> you might want to have <filename role="package">net/cvsup-without-gui</filename> you might want to have
a look at. If you prefer a static binary package, take a look a look at. If you prefer a static binary package, take a look
<ulink url="http://people.FreeBSD.org/~jdp/s1g/">here</ulink>. <ulink url="http://people.FreeBSD.org/~jdp/s1g/">here</ulink>.
This page still refers to the S1G bug that was present This page still refers to the S1G bug that was present
in <application>CVSup</application>. Maybe in <application>CVSup</application>. Maybe
John will set up a generic download-site to get John will set up a generic download-site to get
static binaries for various platforms. static binaries for various platforms.
</para> </para>
<para> <para>
It is possible to use <application>CVSup</application> to offer It is possible to use <application>CVSup</application> to offer
any kind of fileset, not just CVS repositories, any kind of fileset, not just CVS repositories,
but configuration can be complex. but configuration can be complex.
<application>CVSup</application> is known to eat some CPU on both the server and the <application>CVSup</application> is known to eat some CPU on both the server and the
client, since it needs to compare lots of files. client, since it needs to compare lots of files.
</para> </para>
</sect3> </sect3>
@ -364,14 +364,14 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
</programlisting> </programlisting>
See the manpage for details of the options. Also see the CVS <emphasis>info</emphasis> See the manpage for details of the options. Also see the CVS <emphasis>info</emphasis>
page about additional ways to make sure access is read-only. page about additional ways to make sure access is read-only.
It is advised that you create an unprivileged account, It is advised that you create an unprivileged account,
preferably called <username>anoncvs</username>. preferably called <username>anoncvs</username>.
Also you need to create a file <filename>passwd</filename> Also you need to create a file <filename>passwd</filename>
in your <filename>/home/ncvs/CVSROOT</filename> and assign a in your <filename>/home/ncvs/CVSROOT</filename> and assign a
CVS password (empty or <literal>anoncvs</literal>) to that user. CVS password (empty or <literal>anoncvs</literal>) to that user.
The directory <filename>/anoncvstmp</filename> is a special The directory <filename>/anoncvstmp</filename> is a special
purpose memory based file system. It is not required but purpose memory based file system. It is not required but
advised since &man.cvs.1; creates a shadow directory advised since &man.cvs.1; creates a shadow directory
structure in your <filename>/tmp</filename> which is structure in your <filename>/tmp</filename> which is
not used after the operation but slows things not used after the operation but slows things
dramatically if real disk operations are required. dramatically if real disk operations are required.
@ -399,7 +399,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<para> <para>
The FTP area is the largest amount of data that The FTP area is the largest amount of data that
needs to be mirrored. It includes the <emphasis>distribution needs to be mirrored. It includes the <emphasis>distribution
sets</emphasis> required for network installation, the sets</emphasis> required for network installation, the
<emphasis>branches</emphasis> which are actually snapshots <emphasis>branches</emphasis> which are actually snapshots
of checked-out source trees, the <emphasis>ISO Images</emphasis> of checked-out source trees, the <emphasis>ISO Images</emphasis>
to write CD-ROMs with the installation distribution, to write CD-ROMs with the installation distribution,
@ -435,7 +435,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
In general FTP is not really good for mirroring. It transfers In general FTP is not really good for mirroring. It transfers
the whole file if it has changed, and does the whole file if it has changed, and does
not create a single data stream which would benefit from not create a single data stream which would benefit from
a large TCP congestion window. a large TCP congestion window.
</para> </para>
</sect3> </sect3>
<sect3 id="mirror-ftp-rsync"> <sect3 id="mirror-ftp-rsync">
@ -443,16 +443,16 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<para> <para>
A better way to mirror the FTP area is <application>rsync</application>. A better way to mirror the FTP area is <application>rsync</application>.
You can install the port <filename role="package">net/rsync</filename> and then use You can install the port <filename role="package">net/rsync</filename> and then use
rsync to sync with your upstream host. rsync to sync with your upstream host.
<application>rsync</application> is already mentioned <application>rsync</application> is already mentioned
in <xref linkend="mirror-serv-rsync">. in <xref linkend="mirror-serv-rsync">.
Since <application>rsync</application> access is not Since <application>rsync</application> access is not
required, your preferred upstream site may not allow it. required, your preferred upstream site may not allow it.
You may need to hunt around a little bit to find a site You may need to hunt around a little bit to find a site
that allows <application>rsync</application> access. that allows <application>rsync</application> access.
<note> <note>
<para> <para>
Since the number of <application>rsync</application> Since the number of <application>rsync</application>
clients will have a significant impact on the server clients will have a significant impact on the server
machine, most admins impose limitations on their machine, most admins impose limitations on their
server. For a mirror, you should ask the site maintainer server. For a mirror, you should ask the site maintainer
@ -479,7 +479,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<title>With CVSup</title> <title>With CVSup</title>
<para> <para>
A few sites, including the one-and-only <hostid role="fqdn">ftp-master.FreeBSD.org</hostid> A few sites, including the one-and-only <hostid role="fqdn">ftp-master.FreeBSD.org</hostid>
even offer <application>CVSup</application> to mirror the contents of even offer <application>CVSup</application> to mirror the contents of
the FTP space. You need to install a <application>cvsup</application> the FTP space. You need to install a <application>cvsup</application>
client, preferably from the port <filename role="package">net/cvsup</filename>. client, preferably from the port <filename role="package">net/cvsup</filename>.
(Also reread <xref linkend="mirror-serv-cvsup">.) (Also reread <xref linkend="mirror-serv-cvsup">.)
@ -561,7 +561,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<title>Using other methods</title> <title>Using other methods</title>
<para> <para>
Using other methods than <application>CVSup</application> is Using other methods than <application>CVSup</application> is
generally not recommended. We describe them in short here generally not recommended. We describe them in short here
anyway. Since most sites offer the CVS repository as anyway. Since most sites offer the CVS repository as
part of the FTP fileset under the path part of the FTP fileset under the path
<filename>/pub/FreeBSD/development/FreeBSD-CVS</filename>, <filename>/pub/FreeBSD/development/FreeBSD-CVS</filename>,
@ -580,7 +580,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<important> <important>
<para> <para>
You can <emphasis>NOT</emphasis> use AnonCVS to You can <emphasis>NOT</emphasis> use AnonCVS to
mirror the CVS repository since CVS does not allow mirror the CVS repository since CVS does not allow
you to access the repository itself, but only checked you to access the repository itself, but only checked
out versions of the modules. out versions of the modules.
@ -599,10 +599,10 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
and a <emphasis>cronjob</emphasis>, that calls <command>cvs up -d -P</command> and a <emphasis>cronjob</emphasis>, that calls <command>cvs up -d -P</command>
on a regular basis, maybe just after your repository was updated. on a regular basis, maybe just after your repository was updated.
Of course, the files need to remain in a directory available Of course, the files need to remain in a directory available
for public WWW access. The installation and configuration of a for public WWW access. The installation and configuration of a
webserver is not discussed here. webserver is not discussed here.
</para> </para>
<note><para>For the website to be visible, users must execute the &man.make.1; <note><para>For the website to be visible, users must execute the &man.make.1;
command in the main <filename>www</filename> directory. This command command in the main <filename>www</filename> directory. This command
will create the standard <filename>*.html</filename> files for web will create the standard <filename>*.html</filename> files for web
@ -610,7 +610,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<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>
If you don't have a local repository, you can use If you don't have a local repository, you can use
<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
@ -639,8 +639,8 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<sect3 id="mirror-www-doc"> <sect3 id="mirror-www-doc">
<title>Mirroring the FreeBSD documentation</title> <title>Mirroring the FreeBSD documentation</title>
<para> <para>
Since the documentation is referenced a lot from the Since the documentation is referenced a lot from the
webpages, it is recommended that you mirror the webpages, it is recommended that you mirror the
FreeBSD documentation as well. However, this is not FreeBSD documentation as well. However, this is not
as trivial as the www-pages alone. as trivial as the www-pages alone.
</para> </para>
@ -670,7 +670,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
Then you need to install a couple of ports. Then you need to install a couple of ports.
You are lucky, there is a meta-port: You are lucky, there is a meta-port:
<filename role="package">textproc/docproj</filename> to do the work <filename role="package">textproc/docproj</filename> to do the work
for you. You need to set up some for you. You need to set up some
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>
@ -704,7 +704,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<para> <para>
Every mirror should be updated on a regular Every mirror should be updated on a regular
basis. You will certainly need some script basis. You will certainly need some script
framework for it that will be called by framework for it that will be called by
&man.cron.8;. Since nearly every admin &man.cron.8;. Since nearly every admin
does this his own way, we cannot give does this his own way, we cannot give
specific instructions. It could work specific instructions. It could work
@ -787,14 +787,14 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
</para> </para>
<para> <para>
Additionally there exists a hierarchy of mirrors, which Additionally there exists a hierarchy of mirrors, which
is described in terms of <emphasis>tiers</emphasis>. is described in terms of <emphasis>tiers</emphasis>.
The master sites are not referred to but can be The master sites are not referred to but can be
described as <emphasis>Tier-0</emphasis>. Mirrors described as <emphasis>Tier-0</emphasis>. Mirrors
that mirror from these sites can be considered that mirror from these sites can be considered
<emphasis>Tier-1</emphasis>, mirrors of <emphasis>Tier-1</emphasis>-mirrors, <emphasis>Tier-1</emphasis>, mirrors of <emphasis>Tier-1</emphasis>-mirrors,
are <emphasis>Tier-2</emphasis>, etc. are <emphasis>Tier-2</emphasis>, etc.
Official sites are encouraged to be of a low <emphasis>tier</emphasis>, Official sites are encouraged to be of a low <emphasis>tier</emphasis>,
but the lower the tier the higher the requirements in but the lower the tier the higher the requirements in
terms as described in <xref linkend="mirror-requirements">. terms as described in <xref linkend="mirror-requirements">.
Also access to low-tier-mirrors may be restricted, and Also access to low-tier-mirrors may be restricted, and
access to master sites is definitely restricted. access to master sites is definitely restricted.
@ -812,7 +812,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
role="fqdn">ftp.FreeBSD.org</hostid>. role="fqdn">ftp.FreeBSD.org</hostid>.
The short answer is: from the The short answer is: from the
site that is closest to you in Internet terms, or gives you site that is closest to you in Internet terms, or gives you
the fastest access. the fastest access.
</para> </para>
<sect3 id="mirror-where-simple"> <sect3 id="mirror-where-simple">
<title>I just want to mirror from somewhere!</title> <title>I just want to mirror from somewhere!</title>
@ -867,8 +867,8 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<title>I want to access the master sites!</title> <title>I want to access the master sites!</title>
<para> <para>
If you have good reasons and good prerequisites, If you have good reasons and good prerequisites,
you may want and get access to one of the you may want and get access to one of the
master sites. Access to these sites is master sites. Access to these sites is
generally restricted, and there are special policies generally restricted, and there are special policies
for access. If you are already an <emphasis>official</emphasis> for access. If you are already an <emphasis>official</emphasis>
mirror, this certainly helps you getting access. mirror, this certainly helps you getting access.
@ -891,7 +891,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<sect4 id="mirror-where-master-ftp"> <sect4 id="mirror-where-master-ftp">
<title>ftp-master.FreeBSD.org</title> <title>ftp-master.FreeBSD.org</title>
<para> <para>
This is the master site for the FTP fileset. This is the master site for the FTP fileset.
</para> </para>
<para> <para>
<hostid>ftp-master.FreeBSD.org</hostid> provides <hostid>ftp-master.FreeBSD.org</hostid> provides
@ -972,8 +972,8 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<note> <note>
<para> <para>
The following applies mainly to the FTP fileset, The following applies mainly to the FTP fileset,
since a CVS repository should always be mirrored since a CVS repository should always be mirrored
completely, and the webpages are a case of completely, and the webpages are a case of
its own. its own.
</para> </para>
</note> </note>
@ -983,7 +983,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<itemizedlist> <itemizedlist>
<listitem><para>carry the complete fileset</para></listitem> <listitem><para>carry the complete fileset</para></listitem>
<listitem><para>allow access to other mirror sites</para></listitem> <listitem><para>allow access to other mirror sites</para></listitem>
<listitem><para>provide <application>FTP</application> and <listitem><para>provide <application>FTP</application> and
<application>RSYNC</application> access</para></listitem> <application>RSYNC</application> access</para></listitem>
</itemizedlist> </itemizedlist>
@ -1038,7 +1038,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
If everything works so far, contact the DNS administrator responsible If everything works so far, contact the DNS administrator responsible
for your region/country, and ask for a DNS entry for your for your region/country, and ask for a DNS entry for your
site. The admin should able to be contacted via site. The admin should able to be contacted via
<email>hostmaster@CC.FreeBSD.org</email>, where <email>hostmaster@CC.FreeBSD.org</email>, where
<emphasis>CC</emphasis> is your country code/TLD. <emphasis>CC</emphasis> is your country code/TLD.
Your DNS entry will be as described Your DNS entry will be as described
in <xref linkend="mirror-where-organization">. in <xref linkend="mirror-where-organization">.
@ -1058,7 +1058,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
<ulink url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook">FreeBSD <ulink url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook">FreeBSD
Handbook</ulink>. Handbook</ulink>.
</para> </para>
</step> </step>
</procedure> </procedure>
<para>That is it.</para> <para>That is it.</para>
</sect2> </sect2>
@ -1078,7 +1078,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para>ftp.is.FreeBSD.org - <email>hostmaster@is.FreeBSD.org</email> - <para>ftp.is.FreeBSD.org - <email>hostmaster@is.FreeBSD.org</email> -
<ulink url="http://www.rhnet.is/status/draupnir/draupnir.html"> <ulink url="http://www.rhnet.is/status/draupnir/draupnir.html">
(Bandwidth)</ulink> <ulink url="http://www.rhnet.is/status/ftp/ftp-notendur.html">(FTP (Bandwidth)</ulink> <ulink url="http://www.rhnet.is/status/ftp/ftp-notendur.html">(FTP
processes)</ulink> <ulink url="http://www.rhnet.is/status/ftp/http-notendur.html">(HTTP processes) processes)</ulink> <ulink url="http://www.rhnet.is/status/ftp/http-notendur.html">(HTTP processes)
@ -1124,7 +1124,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
</sect1> </sect1>
</article> </article>
<!-- <!--
Local Variables: Local Variables:
mode: sgml mode: sgml
sgml-indent-data: t sgml-indent-data: t