From owner-freebsd-hubs@FreeBSD.ORG Tue Jun 10 05:37:36 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 2F51037B401 for ; Tue, 10 Jun 2003 05:37:36 -0700 (PDT) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 415A943FA3 for ; Tue, 10 Jun 2003 05:37:35 -0700 (PDT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) h5ACbYbr028805; Tue, 10 Jun 2003 08:37:34 -0400 (EDT) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.9/8.12.9/Submit) id h5ACbXb9028804; Tue, 10 Jun 2003 08:37:33 -0400 (EDT) Date: Tue, 10 Jun 2003 08:37:33 -0400 From: Ken Smith To: Jun Kuriyama Message-ID: <20030610123733.GA28649@electra.cse.Buffalo.EDU> References: <200306091636.h59GavDW043030@freefall.freebsd.org> <20030609195142.U581@korben.in.tern> <20030610064507.GA22617@fit.vutbr.cz> <7mn0gqh10y.wl@black.imgsrc.co.jp> <20030610070407.GA27204@fit.vutbr.cz> <7mllwah0ek.wl@black.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7mllwah0ek.wl@black.imgsrc.co.jp> User-Agent: Mutt/1.4.1i cc: freebsd-hubs@freebsd.org Subject: Re: [FreeBSD-Announce] FreeBSD 5.1 Released! 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: Tue, 10 Jun 2003 12:37:36 -0000 On Tue, Jun 10, 2003 at 04:11:47PM +0900, Jun Kuriyama wrote: > collection > ------------------------------------------------------------ > ftp-all same as FreeBSD-archive > ftp-releases FreeBSD/releases/* > ftp-ports FreeBSD/ports/* > ftp-branches FreeBSD/branches/* > ftp-development FreeBSD/development/* > ftp-snapshots FreeBSD/snapshots/* > ftp-CERT FreeBSD/CERT/* Those all sound great, I've needed to sub-divide the rsync's myself for a while now. Jason's suggestion of breaking down to the architecture level if possible would be good too, I see a lot of mirror sites that don't carry all the architectures. May I add the suggestion of publicizing somewhere(s) exactly when the ports get updated? If it's a routine weekly thing and more or less always predictable putting that in a FAQ somewhere so that the mirror sites only hammer on ftp-master for ports shortly after they were supposed to change you might lower the load on ftp-master. It seems like the ports updates are a roughly weekly thing but I don't think I have ever seen anyone say that. > ftp-other rest of above I know the purpose of that and I've got an rsync that does it. But can someone else with more rsync experience than me say whether having a module that does this can be configured to work? I could be mistaken but it could be the case that a pull using that module would need to never delete files. Otherwise it would remove the ports directory, the branches directory, etc. I do this in my rsync by excluding the ports, branches, etc. explicitly and I don't use --delete-excluded on that one so it just ignores those sub-directories and doesn't touch the contents. I might be missing something though... :-/ -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |