On Mon, 15 Nov 1999 [EMAIL PROTECTED] wrote:
> o Upgrading Taz. RAID disks, more memory, faster CPUs, whatever. > > o Partitioning the load. Taz is handling a lot of stuff; perhaps > moving all of the Apache XML stuff (CVS, web server, mailing lists) > to their own machine would make sense. Or it could be split > based on function rather than project, with CVS, mail and web > serving on separate machines, but with each handling all of the > projects. I'd prefer this partitioning > o Some way of running local CVSs that mirror the main one on Taz. Rather than upgrading taz or mirroring. If the machine is fast enough, badnwith is rarely ever a limit; even doing things like a cvs update on, say the entire freebsd repository is very doable. Though we could offload some anon access with cvssup. I am willing to see if I can arrange some shelfspace at Above.Net in San Jose though I might run into my 256k cap. But it should be physically near to taz and most people. Dw
