From owner-freebsd-hubs@FreeBSD.ORG Thu Jun 5 21:52:56 2003 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5971537B401 for ; Thu, 5 Jun 2003 21:52:56 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7F6343F93 for ; Thu, 5 Jun 2003 21:52:55 -0700 (PDT) (envelope-from bmah@employees.org) Received: from bmah.dyndns.org (12-240-204-110.client.attbi.com[12.240.204.110]) by attbi.com (rwcrmhc52) with ESMTP id <2003060604525505200mtudae>; Fri, 6 Jun 2003 04:52:55 +0000 Received: from intruder.bmah.org (localhost [127.0.0.1]) by bmah.dyndns.org (8.12.9/8.12.9) with ESMTP id h564qt9c029154; Thu, 5 Jun 2003 21:52:55 -0700 (PDT) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.9/8.12.9/Submit) id h564qtV1029153; Thu, 5 Jun 2003 21:52:55 -0700 (PDT) Date: Thu, 5 Jun 2003 21:52:54 -0700 From: "Bruce A. Mah" To: Tim Baur Message-ID: <20030606045254.GA29084@intruder.bmah.org> References: <3EDF7E79.3000501@freebsd.org> <0306052049200.26609@neobe.cnanfb.pbz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: <0306052049200.26609@neobe.cnanfb.pbz> User-Agent: Mutt/1.4.1i X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-url: http://www.employees.org/~bmah/ cc: hubs@FreeBSD.org Subject: Re: It's time for 5.1-R bits X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Distributions Hubs: mail sup ftp List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 04:52:56 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable If memory serves me right, Tim Baur wrote: > On Thu, 5 Jun 2003, Scott Long wrote: >=20 > > 3. BitTorrent. I personally like this idea. We only need a few > > mirrors to act as seeds. Once the release happens and people start > > using these seeds, they'll become seeds themselves and the load will > > quickly flatten out. However, it's up to you guys. >=20 > It only takes one box to get the ball rolling. I'm sure you can find a > couple people to toss it up. I'd run with it Scott, even if you decide not > to make it public in the official release. Just jump on irc and pass the > word. It'll spread fast enough, and then you'll know how well it works for > next time. I played with BT a little bit today. A few observations: 1. It seems well suited for transfering large hunks of stuff that don't change (such as *.iso files). It can handle directory hierarchies, but not if the files contained within might change. (I was thinking that our package trees might not work well with this, since we always need to tweak these with last-minute fixes.) 2. The tracker process (rendezvous point for the clients) needs to run somewhere. I'm not sure if a project-sanctioned torrent would need to have its own tracker or whether it's OK to use some existing tracker. Anyone know the convention for this? 3. Because there's no access control (well, none that I can see), using BT as a method for staging bits on mirrors (before a release) isn't ideal because anyone with the *.torrent files can download the *.iso files or whatever. I think it makes more sense to use it as a mechanism for distributing to end-users and mirrors after the release is announced. Bruce. --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+4B4m2MoxcVugUsMRAvobAKCLQQ2dW/6y3YdoJC5rKlCcWeCyCACdFGMI 7p8raIWGCmpf+6ZBGJv0RzI= =8bQ9 -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR--