-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Using an ISO has traditionally been the realm of the advanced user, not the "Joe Average" user. Although it is simple to burn an ISO to a disk properly, the software required to do so isn't as simple.
Torrent clients are simply advanced download managers. It's not hard to teach someone how to use one. http://utorrent.com/beginners-guide.php is a good example of a first-timer's guide to BT. The bar for the technical knowledge level of "Joe Average" is typically higher for ISO distributions than it is for the regular installers. (At least it has been in my experience, so ISO users are more likely to know how to use torrents and may be more likely to use them if they're available. Additionally, if the site managers want to use torrent to mirror instead of rsync, they may. They also have the option of continuing to be a seed for the torrents after completing the download. I personally prefer having the torrent hashset available to verify when I download a file, that way I know it doesn't arrive corrupted, and that I don't have to re-download the whole file if corruption does get detected. In regards to the torrents being made, it makes sense to make the torrents as close to the origin point of the files themselves to reduce the likelihood of a broken torrent being made, even if the seeding happens 2 or 3 rsyncs down the road. Florian Effenberger wrote: > Hi Harold, > >> The torrent mirror system is capable of supporting the additional files >> fairly easily, given that there are mechanisms in place to permit >> bridging of traditional mirrors (HTTP/FTP) directly into the torrent >> swarms (although they may not be getting used properly yet, as the >> primary client that supports them is still in a beta stage rather than >> release). > > that, however, doesn't solve the problem that a lot of "Joe Average" > users (e.g. those downloading our ISOs) do NOT use BitTorrent and for > that, we just need some HTTP/FTP mirrors for that. > > Florian > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRO4Sql8nceBm0DUaAQKwzQgAlCp8Blcyam5DCwveZR4a9MbpxiLlF1zN VO5A6mLlxC8urcJVhkL+jU22z7GmA0DyFJTmjR24tW0LbwAGbPMRphbAVLNFciCQ yNiOExooEGQW7xJB/949EJ2eGHOkeygVaefjyf55+Z8OEC56jBBEElpsiMQDYPZz tpsYdCE27227PloNy0vz3tfK3DggjduANRrUERkMj3mn0vh1CFTR490YHX0s7O4v SCCHj1SZzC5VB77Bg8Y9DRKlky5j85uj4O1MsblzpY4Exlip7D42+QlOhayLHLrd 3OBLc+WXvl5/i7ZXeXACwfCu1IWL8T/nodc3+diNC3CaueH9ekwD8A== =VQUt -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
