summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTails developers <amnesia@boum.org>2014-03-30 11:07:55 +0000
committerTails developers <amnesia@boum.org>2014-03-30 11:09:58 +0000
commit3c434520d7462b6210c262bcdb3620b0a4467cf7 (patch)
treea418647f5a52fadfd46108241624a469a8c6218f
parent45ceed8dbb296471e76c860f9fac02031f11f562 (diff)
Clarify and update bandwidth expectations.
-rw-r--r--wiki/src/contribute/how/mirror.mdwn7
1 files changed, 4 insertions, 3 deletions
diff --git a/wiki/src/contribute/how/mirror.mdwn b/wiki/src/contribute/how/mirror.mdwn
index cc49e79..5864788 100644
--- a/wiki/src/contribute/how/mirror.mdwn
+++ b/wiki/src/contribute/how/mirror.mdwn
@@ -60,9 +60,10 @@ bandwidth: a domestic DSL connection won't help; neither will a shared
web hosting setup that provides FTP access only.
To give you an idea, a few dedicated Mb/s is a must; you must expect
-pushing at least a few dozens [[!wikipedia GiB]] (bytes, not bits) on
-a normal day, and at least 100 GiB a day for a short period after
-each release.
+pushing at least 50-100GB [[!wikipedia GiB]] (bytes, not bits) on
+a normal day, and twice as much for a short period after each release.
+So, it is a must to be able to push at least 2 [[!wikipedia TiB]]
+a month, and preferably 3 or 4 TiB.
If you satisfy these practical requirements, please read on!
Else, please consider seeding Tails images over BitTorrent instead.