[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

web s



Update of /org/volatile.debian.net/cvs/web
In directory alius:/org/volatile.debian.net/web

Modified Files:
	mirroring.html 
Log Message:
added remaining information


Index: mirroring.html
===================================================================
RCS file: /org/volatile.debian.net/cvs/web/mirroring.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- mirroring.html	5 Aug 2005 23:51:52 -0000	1.3
+++ mirroring.html	6 Aug 2005 00:30:11 -0000	1.4
@@ -43,6 +43,8 @@
 a full working mirror the whole time.The following options to rsync
 (besides what you normally have) do the trick:</p>
 
+<hr>
+
 <table>
 <tr>
  <th>Run</th>
@@ -53,32 +55,105 @@
 <tr>
 <td>1</td>
 <td>--exclude Packages* --exclude Sources* --exclude Release*</td>
-<td>You download new binary files, sources and Packages, but not the metadata for them that <code>apt-get</code>
- uses. Also note that no delete option is given.</td>
+<td>You download new binary files, sources and Packages, but not the metadata
+for them that <code>apt-get</code> uses. Also note that no delete option is
+given.</td>
 
 </tr>
 <tr>
 <td>2</td>
 <td>--delete --delete-after</td>
-<td>The second run now fetches the files excluded in the first run and also deleted all files not any longer in
-the archive.</td>
+<td>The second run now fetches the files excluded in the first run and also
+deleted all files not any longer in the archive.</td>
 </tr>
 </table>
 
+<hr>
+
 <p>
-This two-way mirror approach makes sure that users with their apt-get can always fetch the files that are announced
-to be there (via the Packages files), even when your mirror is updating itself at the moment they try to download stuff.
-You are free to use any other option to rsync you may like, but we strongly suggest to use at least -lH.
+This two-way mirror approach makes sure that users with their apt-get can
+always fetch the files that are announced to be there (via the Packages files),
+even when your mirror is updating itself at the moment they try to download
+stuff.  You are free to use any other option to rsync you may like, but we
+strongly suggest to use at least -lH.  </p> <p>Now you need to add <a
+href="id_mirrorpush.pub">this ssh key</a>to the mirror-user's
+.ssh/authorized_keys file.  If you look into the key you see that it is limited
+to only one command.  This means that we are NOT able to log on to your system
+with this key. There
+is no way for us to do anything other to your system then to just trigger the
+mirror - so the only harm we can do would be to trigger your mirror every few
+seconds, but for that the script we provide as an example uses a lockfile to
+avoid multiple runs at the same time.  <b>You need to change that to whatever
+script you use, but do NOT delete the & at the end.</b> </p>
+
+
+<h2>Getting the push</h2> 
+
+<p> As soon as you finished setting it up you are ready to be added to the list
+of "pushed" servers.  For that please email the hostname and the username where
+the signal should be sent to <a href="mailto:rsync@ftbfs.de";>rsync@ftbfs.de</a>.
 </p>
 
+<h2>Getting listed as mirror</h2>
 
+<p> Simple, after the above is finished and running you are normally added to
+our mirror list.  While you send the hostname/username to the address above
+please send the the following information to <a
+href="mailto:debian-volatile@lists.debian.org";>debian-volatile@lists.debian.org</a>.
+This data will be used to generate our mirrorlist. </p>
+
+<pre>
+Site: Your Primary Hostname
+Aliases: If you are known under other names also, maybe multiple times
+Type: [TYPE] (Type can be push or , whatever you want to be)
+Archive-ftp: /debian-volatile/
+Archive-http: /debian-volatile/
+Archive-rsync: debian-volatile/
+Mirrors-from: volatile.debian.net
+Maintainer: Your Name &lt;your&#64;ema.il&gt;
+Country: ISO Countryname
+Location: City
+Comment: comment (eg. network bandwidth)
+</pre>
+<p>
+Change the paths for Archive-* to fit your layout and delete lines with services you don't have.
+An example for an entry follows.
+</p>
+<pre>
+Site: ftp.uk.debian.org
+Aliases: debian.hands.com
+Type: Push
+Archive-ftp: /debian-volatile/
+Archive-http: /debian-volatile/
+Archive-rsync: debian-volatile/
+Mirrors-from: volatile.debian.net
+Maintainer: Philip Hands  &lt;<phil&#64;hands.com&gt;
+Country: DE Germany
+Location: Dresden
+Sponsor: Technical University of Dresden, Dept. of Computer Science http://www.inf.tu-dresden.de/
+Comment: 
+</pre>
+
+<h2>Finished</h2>
+<p>Yes, that was it. THANK YOU for offering a mirror service!</p>
+
+<h2>Traffic and Space Considerations</h2>
+<h3>Traffic</h3>
+<p>
+Maybe you want to know what traffic you will get - or how much disk space you
+need.  I can't say much about the bandwith usage, as that's dependent on the
+users, how they use it and what mirror they choose. I know that we have a
+currently about 20GB a month on volatile.debian.net. Some mirrors might have
+more, some less traffic.
+</p>
+
+<h3>Space</h3>
+
+<p>
+At the moment our archive takes about 200MB of space. As we add packages from
+time to time please expect this archive to grow.
+</p>
 
-A "push" mirror is a normal mirror which gets notified by the
-volatile master mirror abSimply said: A normal mirror, with the only difference that we tell
-you when something has changed in the archive. No need to go and just
-try a sync, you know when it changed. A good page describing it, and
-some parts of the setup, is available on the debian.org servers.
-Please read it if you are not familiar with it.
 
 
 <hr />



Reply to: