Date: Sat, 7 Jun 2003 04:30:33 +0000 (GMT) From: Chris Coleman <chrisc@vmunix.com> To: hubs@freebsd.org Subject: Re: It's time for 5.1-R bits Message-ID: <20030607042755.L90875@vnode.vmunix.com> In-Reply-To: <3EE15336.5020706@freebsd.org> References: <3EDF7E79.3000501@freebsd.org> <7mn0gw9ni0.wl@black.imgsrc.co.jp> <3EE15336.5020706@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I'd like to get my hands on the bits a bit early, like Saturday, so I can get a jump on putting together the DN CD ISOs. Is it possible that one of the mirror operators can open up something for me to get access to the bits? Chris Coleman Editor in Chief Daemon News E-Zine http://www.daemonnews.org Get BSD! http://www.getbsd.com On Fri, 6 Jun 2003, Scott Long wrote: > Alpha bits are almost up. Sparc64 bit will likely go up tonight, > though there are no sparc64 packages or a sparc64 disc1 yet. These > might very well not be ready for Monday. Oh well. It looks like the > chmod trick is working well. I apologize to the second-tier mirrors > that cannot access the bits yet. If we keep this model, you'll have > to work out arrangements with the first tier mirrors for special > access. > IMPORTANT: The official 5.1 announcement and press release will go > out at 1000EDT (1400GMT). I'd like to unmask the release bits about > an hour before the announcement, which would be 1300GMT 9-June-2003. > Please set your at(1) jobs accordingly! > > Thanks a lot! > > Scott > > Scott Long wrote: > > 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... > >>> > >>> > >> > >> > >> > > > > > > > > > _______________________________________________ > freebsd-hubs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hubs > To unsubscribe, send any mail to "freebsd-hubs-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030607042755.L90875>