Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3CCDA73E.5000503@ece.gatech.edu> Date: Mon, 29 Apr 2002 16:04:14 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Charles Wilson CC: cygwin AT cygwin DOT com Subject: Re: Using a real mirroring tool... References: <3CCC7290 DOT 706 AT ece DOT gatech DOT edu> <3CCD971A DOT 5050205 AT ece DOT gatech DOT edu> <3CCD9F4D DOT 20209 AT ece DOT gatech DOT edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Charles Wilson wrote: > So, if someone cares enough to do the work, there is still a need for > the "additional tool" that uses the setup.exe codebase to do > "cygwin-specific distributed mirroring". See my earlier rant. Oh, I left out the most obvious reason why rsync won't solve all of our problems: we have lots of ftp and http mirrors, but very few (ONE?) rsync mirrors. That really kills the "distributed" nature of the mirror system; that poor guy in Thailand with the slow connection would be rsync'ing across the Pacific from Indiana...that can't be good. A tool that leverages the setup.exe codebase would inherit the ability to use the existing ftp and http mirror sites. --Chuck P.S. you might want to add --exclude *-src.tar.* to the option string, if you don't want the -src tarballs. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/