From owner-freebsd-hubs@FreeBSD.ORG Sat May 31 10:31:40 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 955F237B401; Sat, 31 May 2003 10:31:40 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9DF643F3F; Sat, 31 May 2003 10:31:39 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h4VHVbVo079329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 31 May 2003 13:31:37 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id h4VHVbA0079326; Sat, 31 May 2003 13:31:37 -0400 (EDT) (envelope-from wollman) Date: Sat, 31 May 2003 13:31:37 -0400 (EDT) From: Garrett Wollman Message-Id: <200305311731.h4VHVbA0079326@khavrinen.lcs.mit.edu> To: Scott Long In-Reply-To: <3ED8D49C.40804@btc.adaptec.com> References: <3ED8D49C.40804@btc.adaptec.com> X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) cc: re@freebsd.org cc: hubs@freebsd.org Subject: Re: Coordinating and distributing the release 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: Sat, 31 May 2003 17:31:41 -0000 < said: > Can we just enable :archive 0770 on the files/directories and have > them safely propogate out to all of the mirrors that way, while still > leaving them invisible to normal visitors? I certainly do not want to > exclude the secondary mirrors. Not reliably, since users and groups are not standardized across all the mirrors. (For example, a 770-mode file on my mirror would only be readable by members of group `mirror', which has only one member, the user `mirror'. rsyncd and cvsupd run under different users and groups.) However, I think it may well be good enough, and the intermediate mirror operators can deal if you give them enough advance notice as to how the release will be handled. -GAWollman