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

Fix grammar, contractions and the make.conf example..

Browse source 
PR:			docs/72462
Submitted by:		Joel Dahl <joel at automatvapen dot se>
Approved by:		simon (mentor)
This commit is contained in:
Remko Lodder 2005-03-07 22:30:10 +00:00
parent ca7d37868b
commit 8c8a095230
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=24021
1 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -335,7 +335,7 @@
Generally there are two ways
to access a CVS repository remotely: via
<emphasis>pserver</emphasis> or via <command>ssh</command>
(we don't consider <command>rsh</command>).
(we do not consider <command>rsh</command>).
For anonymous access, <emphasis>pserver</emphasis> is
very well suited, but some still offer <command>ssh</command>
access as well. There is a custom crafted
@ -346,7 +346,7 @@
anonymous user's home-directory. This may not be possible
for all sites. If you just offer <emphasis>pserver</emphasis>
this restriction does not apply, but you may run with
more security risks. You don't need to install any special
more security risks. You do not need to install any special
software, since &man.cvs.1; comes with
FreeBSD. You need to enable access via <command>inetd</command>,
so add an entry into your <filename>/etc/inetd.conf</filename>
@ -602,7 +602,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
installed.</para></note>
<para>
If you don't have a local repository, you can use
If you do not have a local repository, you can use
<application>CVSup</application> to maintain an <quote>up to date copy</quote>
of the www pages. A sample supfile can be found in
<filename>/usr/share/examples/cvsup/www-supfile</filename> and
@ -666,18 +666,18 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
environment variables, like
<literal>SGML_CATALOG_FILES</literal>.
Also have a look at your <filename>/etc/make.conf</filename>
(copy <filename>/etc/defaults/make.conf</filename> if
(copy <filename>/usr/share/examples/etc/make.conf</filename> if
you do not have one), and look at the
<literal>DOC_LANG</literal> variable.
Now you are probably ready to run <command>make</command>
in you doc directory (<filename>/usr/share/doc</filename>
in your doc directory (<filename>/usr/share/doc</filename>
by default) and build the documentation.
Again you need to make it accessible for your web server
and make sure the links point to the right location.
<important>
<para>
The building of the documentation, as well as lots
of side issues, is documented itself in:
of side issues, is documented itself in the
<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
have problems building the documentation.
@ -845,7 +845,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
</procedure>
</sect3>
<sect3 id="mirror-where-official">
<title>I'm an official mirror, what is the right site for me?</title>
<title>I am an official mirror, what is the right site for me?</title>
<para>
In general the description in <xref linkend="mirror-where-simple">
still applies. Of course you may want to put some
@ -992,7 +992,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
</para>
<para>
It is also important that hub administrators try to keep their mirrors as up-to-date as
possible (again, even more crucial for Tier-1 mirrors). If Mirror1 doesn't update for a
possible (again, even more crucial for Tier-1 mirrors). If Mirror1 does not update for a
while, lower tier mirrors will begin to mirror old data from Mirror1 and thus begins
a downward spiral... Keep your mirrors up to date!
</para>