[FreeBSD-Announce] FreeBSD 5.1 Released!

[Ken Smith]

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 at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |