Date: Mon, 8 Aug 2005 02:24:51 +0800 From: Xin LI <delphij@frontfree.net> To: Colin Percival <cperciva@freebsd.org> Cc: freebsd-arch@freebsd.org Subject: Re: /usr/portsnap vs. /var/db/portsnap Message-ID: <20050807182451.GB61057@frontfree.net> In-Reply-To: <42F63353.7030707@freebsd.org> References: <42F60443.2040301@freebsd.org> <20050807.231125.26489231.hrs@allbsd.org> <42F61960.4020400@freebsd.org> <20050807.100622.54623722.imp@bsdimp.com> <42F63353.7030707@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--+g7M9IMkV8truYOl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 07, 2005 at 09:14:11AM -0700, Colin Percival wrote: > M. Warner Losh wrote: > > In message: <42F61960.4020400@freebsd.org> > > Colin Percival <cperciva@FreeBSD.org> writes: > > : very little reason for anyone to be running > > : a portsnap mirror unless it's a public mirror, > >=20 > > Our experience with cvsup would suggest otherwise. Many places with > > large numbers or even small numbers of machines run cvsup mirrors that > > are private. I expect that universities will want to run mirrors that > > they might not want non-students accessing (eg, internal bandwidth is > > free, external is expensive). >=20 > Portsnap !=3D CVSup. In particular, an HTTP proxy which is used by five > hundred users running portsnap will use less bandwidth than a portsnap > mirror. The "right" solution for nearly all organizations is a caching > HTTP proxy. I must say that HTTP proxy-able is the 1st reason why I like portsnap. There are so many people asking "Hey, how can I break the firewall that blocks cvsup connection?" Where I can only say "The only solution at this time would be to negotiate with the local network administrator" in the pre-postsnap age. Using CVSup to synchonorize CVS tree while distributing ports tree through portsnap looks quite convinent for these people. Cheers, --=20 Xin LI <delphij frontfree net> http://www.delphij.net/ See complete headers for GPG key and other information. --+g7M9IMkV8truYOl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC9lHz/cVsHxFZiIoRAuS6AJ98yt/UhDQHqVVnK1qNTNIFHJh+rwCeMtdM D6NP7a+mhpL4iEz0jZhXI1U= =qjfi -----END PGP SIGNATURE----- --+g7M9IMkV8truYOl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050807182451.GB61057>