From owner-freebsd-hubs@FreeBSD.ORG Thu Jun 5 15:18:51 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 73E5337B401; Thu, 5 Jun 2003 15:18:51 -0700 (PDT) Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 393E543F75; Thu, 5 Jun 2003 15:18:50 -0700 (PDT) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by white.imgsrc.co.jp (Postfix) with ESMTP id B8E9041E5; Fri, 6 Jun 2003 07:18:48 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2::130]) by white.imgsrc.co.jp (Postfix) with ESMTP id 9AE5B41D9; Fri, 6 Jun 2003 07:18:47 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2::130]) by black.imgsrc.co.jp (Postfix) with ESMTP id 6CE3B1E4620; Fri, 6 Jun 2003 07:18:47 +0900 (JST) Date: Fri, 06 Jun 2003 07:18:47 +0900 Message-ID: <7mn0gw9ni0.wl@black.imgsrc.co.jp> From: Jun Kuriyama To: hubs@freebsd.org, re@freebsd.org In-Reply-To: <3EDF7E79.3000501@freebsd.org> References: <3EDF7E79.3000501@freebsd.org> User-Agent: Wanderlust/2.10.0 (Venus) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.4 Emacs/21.2 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20020531 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: Thu, 05 Jun 2003 22:18:51 -0000 At Thu, 05 Jun 2003 11:31:37 -0600, Scott Long wrote: > i386 and pc98 bits for 5.1-R are ready to go online. Alpha and sparc64 > will happen over the next 2 days. We are scheduled to make the > announcement and press release on Monday, June 9. So, it's time to > decide on how to push out the bits to the mirrors without allowing > public access, how to quickly grant public access, and what, if > anything, should be done about BitTorrent. > > 1. Distributing to the mirrors. The easiest approach seems to be > to use a permission setting of 0660 on the files and 0770 on the > directories. However, this will exclude the second-tier mirrors > that mirror off of others using anonymous access. What should be > done about this? Even if 0770 dir, anonymous access can be done if mirror is done with group which is same as anonymous ftp user. Should we write the rule for mirror site maintainers about this? > 2. Granting anonymous access. If I publish an exact time, will > everyone be able to tweak their mirrors by hand? If not, will > rsync'ing the permission change be fast enough and not eat up too > much bandwidth? I think we should not hope every mirror maintainer can tweak. CVSup and rsync can handle permission change effectively. > 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. Hmm, I don't know how BitTrront works and has good performance for us. It seems we should continue the duscussion about this (and we should not use it for 5.1-R yet). Anyways, it is difficult to coordinate with mirror maintainers for new configuration/installation in few days. If 0770 dir can works, doing such for few days (for tier-1 mirrors) may work... -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project