From owner-freebsd-hubs@FreeBSD.ORG Fri Jun 6 01:09: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 B069A37B404; Fri, 6 Jun 2003 01:09:51 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA6F743F85; Fri, 6 Jun 2003 01:09:50 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h5684ce31143; Fri, 6 Jun 2003 01:04:38 -0700 Received: from freebsd.org (hollin.btc.adaptec.com [10.100.253.56]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id BAA03299; Fri, 6 Jun 2003 01:09:49 -0700 (PDT) Message-ID: <3EE04C63.30203@freebsd.org> Date: Fri, 06 Jun 2003 02:10:11 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hubs@freebsd.org References: <3EDF7E79.3000501@freebsd.org> <7mn0gw9ni0.wl@black.imgsrc.co.jp> <3EDFE735.30604@freebsd.org> In-Reply-To: <3EDFE735.30604@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: re@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 08:09:52 -0000 i386 and pc98 iso and ftp bits are up with the restricted permissions. Scott Scott Long wrote: > The 5.1-R ISO's for i386 are up with the permissions that I stated > below. I'm going to do a spot check later tonight and see how they > show up on the mirrors. > > Scott > > Jun Kuriyama wrote: > >> 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... >> >> > > >