[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server mirror.html standards/README.html st...
|
From: |
Karl Berry |
|
Subject: |
www/server mirror.html standards/README.html st... |
|
Date: |
Fri, 20 Nov 2009 16:11:23 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Karl Berry <karl> 09/11/20 16:11:23
Modified files:
server : mirror.html
server/standards: README.html README.webmastering.html
Log message:
Merge continues: sitemap; mirror update, more ftpmirror publicity
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/mirror.html?cvsroot=www&r1=1.75&r2=1.76
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.html?cvsroot=www&r1=1.62&r2=1.63
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.96&r2=1.97
Patches:
Index: mirror.html
===================================================================
RCS file: /web/www/www/server/mirror.html,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -b -r1.75 -r1.76
--- mirror.html 17 Nov 2009 14:27:11 -0000 1.75
+++ mirror.html 20 Nov 2009 16:11:12 -0000 1.76
@@ -1,22 +1,32 @@
<!--#include virtual="/server/header.html" -->
-<title>Advice for Running Mirrors - GNU Project - Free Software
+<title>Using and Running Mirrors - GNU Project - Free Software
Foundation (FSF)</title>
<!--#include virtual="/server/banner.html" -->
-<h2>Advice for Running Mirrors</h2>
+<h2>Using and running mirrors</h2>
+
+<p>First, the address <a
+href="http://ftpmirror.gnu.org/";>http://ftpmirror.gnu.org/</a>
+multiplexes between the mirrors, trying to choose one that is nearby and
+up to date. E.g., <a
+href="http://ftpmirror.gnu.org/emacs/";>http://ftpmirror.gnu.org/emacs/</a>
+should go to a mirror's directory of <a href="/software/emacs/">GNU
+Emacs</a>. We recommend using this generic address wherever possible,
+to reduce load on the main GNU server.
+
<h3>Mirroring the GNU FTP server</h3>
-<p>First, if you mirror ftp.gnu.org, please drop us a line
-at <a href="mailto:address@hidden";><address@hidden></a>
-so we can add you to the <a href="/order/ftp.html">mirror list</a>.
-And thanks.</p>
-
-<p>Mirroring the entire GNU FTP server requires approximately 40GB
-disk space (as of 22 February 2009), which is distributed by
-the following way:</p>
+<p>If you establish a mirror of ftp.gnu.org, please drop us a line at <a
+href="mailto:address@hidden";><address@hidden></a> so we
+can add you to the <a href="/order/ftp.html">mirror list</a>. And
+thanks.</p>
+
+<p>Mirroring the entire GNU FTP server requires approximately 40GB disk
+space (as of 22 February 2009), which is distributed by the
+following way:</p>
<pre>
/gnu: 18G
/non-gnu: 400M
@@ -30,24 +40,24 @@
from us nightly and you may access them with (via rsync):</p>
<ul>
- <li><tt>rsync://ftp.funet.fi/ftp/pub/mirrors/ftp.gnu.org/pub/gnu/</tt>
(Finland)</li>
- <li><tt>rsync://gnu.c3sl.ufpr.br/gnu/ftp/</tt> (Brazil)</li>
- <li><tt>rsync://mirror.its.uidaho.edu/gnu/</tt> (Idaho, USA)</li>
- <li><tt>rsync://mirrors.ibiblio.org::gnuftp/</tt> (North Carolina, USA)</li>
- <li><tt>mirror.cinquix.com::gnuftp</tt> (New York, USA)</li>
+<li><tt>rsync://ftp.funet.fi/ftp/pub/mirrors/ftp.gnu.org/pub/gnu/</tt>
(Finland)</li>
+<li><tt>rsync://gnu.c3sl.ufpr.br/gnu/ftp/</tt> (Brazil)</li>
+<li><tt>rsync://mirror.its.uidaho.edu/gnu/</tt> (Idaho, USA)</li>
+<li><tt>rsync://mirrors.ibiblio.org::gnuftp/</tt> (North Carolina, USA)</li>
+<li><tt>mirror.cinquix.com::gnuftp</tt> (New York, USA)</li>
</ul>
-<p>rsync is so much more efficient than any other protocol that we
-recommend using only rsync for mirror transfers.</p>
-
<p>If your site can also offer general access for other mirrors, please
<a href="mailto:address@hidden";>contact us</a>.</p>
-<p>If your mirror will be available via http (which is very useful, so
-please enable this if you can), please set up your configuration to
-avoid sending <tt>.gz.sig</tt> files (signatures of compressed files,
-of which there are many on our servers) as gzip-encoded. For Apache,
-this would mean:</p>
+<p>rsync is so much more efficient than other protocols that we
+recommend using only rsync for mirror transfers.</p>
+
+<p>If your mirror will be available to users via http (which is very
+useful, so please enable this if you can), please set up your
+configuration to avoid sending <tt>.gz.sig</tt> files (signatures of
+compressed files, of which there are many on our servers) as
+gzip-encoded. For Apache, this would mean:</p>
<pre>
AddType application/pgp-signature .sig
@@ -88,16 +98,9 @@
<li><tt>rsync://gnu.c3sl.ufpr.br/gnu/alpha/</tt></li>
</ul>
-<p>and</p>
-
-<ul>
- <li><tt>ftp://mirrors.ibiblio.org/pub/mirrors/gnu/alpha/</tt></li>
- <li><tt>ftp://ftp.funet.fi/ftp/pub/mirrors/alpha.gnu.org/gnu/</tt></li>
- <li><tt>ftp://gnu.c3sl.ufpr.br/gnu/alpha/</tt></li>
-</ul>
-
<p>Nightly updates are sufficient for GNU FTP and Alpha material.</p>
+
<h3 id="nongnu">Mirroring nongnu releases from Savannah</h3>
<p>We are looking for volunteers to mirror releases of
@@ -120,13 +123,13 @@
href="http://dl.sv.gnu.org/releases/00_MIRRORS.html";>list</a>. Thanks!</p>
-<h3>Mirroring the GNU web server</h3>
+<h3>(Not) Mirroring the GNU web server</h3>
<p>We no longer recommend creating web mirrors, because it has turned
-out that (a) few users can actually make use of them, and
-(b) many mirrors either became out of date or went offline
-relatively frequently. We don't want outdated information about the
-GNU project to be disseminated.</p>
+out that (a) few users can use them, and (b) many mirrors
+either became out of date or went offline relatively frequently. We
+don't want outdated information about the GNU project to be
+disseminated.</p>
<p>Nonetheless, if you wish to mirror www.gnu.org for your own
purposes, that is ok with us. We recommend using <tt>mod_proxy</tt>.
@@ -176,7 +179,7 @@
<p>Updated:
<!-- timestamp start -->
-$Date: 2009/11/17 14:27:11 $
+$Date: 2009/11/20 16:11:12 $
<!-- timestamp end -->
</p>
</div>
Index: standards/README.html
===================================================================
RCS file: /web/www/www/server/standards/README.html,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -b -r1.62 -r1.63
--- standards/README.html 19 Nov 2009 18:27:24 -0000 1.62
+++ standards/README.html 20 Nov 2009 16:11:18 -0000 1.63
@@ -24,9 +24,6 @@
<a id="TOC7" href="README.html#SEC7">Update the What's New page!</a>
</li>
<li>
- <a id="TOC8" href="README.html#SEC8">Update the Sitemap page?</a>
-</li>
-<li>
<a id="TOC9" href="README.html#SEC9">Update GNUs Flashes on the
home page http://www.gnu.org/</a>
</li>
@@ -99,22 +96,6 @@
the new items first.
</p>
-<h4><a id="SEC8" href="README.html#TOC8">Update the Sitemap page?</a></h4>
-
-<p>
-When you add something <strong>very</strong> significant
-to www.gnu.org, please add
-an entry to /home/www/html/server/sitemap.html<br />
-in the right section.
-</p>
-
-<p>
-Entries that can, should contain a <a href=" to the page (or section
-of a page (<a ... id="...")) that has the newly added text.
-Multiple <a href=" are OK, if appropriate (HTML 3.2 and 2
-use id= instead of id=).
-</p>
-
<h4>
<a id="SEC9" href="README.html#TOC9">Update GNUs Flashes on the
home page http://www.gnu.org/</a>
@@ -218,7 +199,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2009/11/19 18:27:24 $
+$Date: 2009/11/20 16:11:18 $
<!-- timestamp end -->
</p>
</div>
Index: standards/README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.96
retrieving revision 1.97
diff -u -b -r1.96 -r1.97
--- standards/README.webmastering.html 19 Nov 2009 18:27:24 -0000 1.96
+++ standards/README.webmastering.html 20 Nov 2009 16:11:18 -0000 1.97
@@ -618,11 +618,10 @@
<h4>Announcements</h4>
-<p>
-When significant new content is added, notices should be put up to make
-people aware of it. Simply add a new entry to /server/whatsnew.html
-by adding an entry to the /server/whatsnew.txt file (see <a href="#polnews"
>Adding news</a>)
-</p>
+<p>When significant new content is added, notices should be put up to
+make people aware of it: Add a new entry to /server/whatsnew.html by
+adding an entry to the /server/whatsnew.txt file (see the next section,
+<a href="#polnews">Adding news</a>).</p>
<p>If you're adding a new page, add a link to the directory's main page.
For example, if you've created a new page with more GNU history,
@@ -630,10 +629,8 @@
page is particularly useful, consider adding a link on
/server/sitemap.html as well.</p>
-<p>
-If the page discusses an important issue, consider adding a notice about it
-to the front page, /home.html.
-</p>
+<p>Finally, if the page discusses a sufficiently important issue,
+consider adding a notice about it to the front page, /home.html.</p>
<h4 id="polnews">Adding news</h4>
@@ -706,30 +703,34 @@
<a name="mirrors"></a><h4>Mirrors</h4>
-<p>The <a href="/server/mirror.html">Advice for mirrors</a> page
-explains what we ask mirror volunteers to provide.</p>
-
-<p>www mirrors: we no longer recommend or list mirrors of www.gnu.org.</p>
+<p><b>ftp mirrors:</b> we have <a href="/server/mirror.html">advice for
+mirrors</a> that explains what we ask mirror volunteers to provide.</p>
-<p>ftp mirrors: when we get a request to add, change, or remove an ftp
-mirror, edit the file prep/FTP (in CVS); it's plain text, not HTML.
+<p>When we get a request to add, change, or remove a mirror of
+ftp.gnu.org, edit the file prep/FTP (in CVS); it's plain text, not HTML.
Then make in the prep/ subdirectory. Then cvs commit both of the files
FTP and ftp.html. Then update /gd/gnuorg/web/FTP.contacts on fencepost,
-following the existing pattern. A <a
-href="http://gnu-mirmon.basemirror.de";>mirmon page</a> tracks how
-up-to-date each mirror is; it is good to write a mirror contact when it
-has gotten more than a week or two out of date.</p>
-
-<p>nongnu mirrors: when we get a request to add, change, or remove a
-nongnu savannah mirror, email address@hidden with the
-information. The reason to use -private is to avoid the contact address
-from becoming public.</p>
-
-<p>When we get a request relating to contact information for a mirror,
-update the file /gd/gnuorg/web/FTP.contacts on fencepost. For that
-matter, if a mirror admin writes us for any reason (not just to update
-addresses), please check that file and add contact information if it's
-not there already.</p>
+following the existing pattern.</p>
+
+<p>A <a href="http://gnu-mirmon.basemirror.de";>mirmon page</a> tracks
+how up-to-date each mirror is; it is good to write a mirror contact when
+it has gotten more than a week or two out of date. The address
+<tt>http://ftpmirror.gnu.org/PKG</tt> (maintained by Randy Kobe at
+Winnipeg) multiplexes between the mirrors, trying to choose one that is
+nearby and up to date.</p>
+
+<p><b>nongnu mirrors:</b> when we get a request to add, change, or
+remove a nongnu savannah mirror, email address@hidden
+with the information. The reason to use -private is to avoid the
+contact address from becoming public.</p>
+
+<p><b>www mirrors:</b> we no longer recommend or list mirrors of
+www.gnu.org.</p>
+
+<p><b>Mirror contact information:</b> when we get a request relating to
+a mirror, please check the file /gd/gnuorg/web/FTP.contacts on
+fencepost. and add contact information if it's not there already. We
+lack information for many older mirrors.</p>
<a id="distros"></a>
@@ -1246,7 +1247,7 @@
<p>Updated:
<!-- timestamp start -->
-$Date: 2009/11/19 18:27:24 $
+$Date: 2009/11/20 16:11:18 $
<!-- timestamp end -->
</p>
</div>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/server mirror.html standards/README.html st...,
Karl Berry <=