X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
Subject: Re: MD5s of setup.exe on mirrors.
References: <5qd5179mvu DOT fsf AT hod DOT lan DOT m-e-leypold DOT de> 	<4644CB03 DOT 9070707 AT determina DOT com> 	<o7d5164e3s DOT fsf AT hod DOT lan DOT m-e-leypold DOT de> 	<063001c7947a$3312cea0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> 	<lblkfu5olv DOT fsf AT hod DOT lan DOT m-e-leypold DOT de> 	<46461FA2 DOT E6EFA773 AT dessent DOT net> <i646w3lyh DOT fsf AT hod DOT lan DOT m-e-leypold DOT de> 	<20070513161110 DOT GA5651 AT ednor DOT casa DOT cgf DOT cx> 	<46489A67 DOT 7090503 AT determina DOT com> <4648A523 DOT 1010705 AT cygwin DOT com> 	<5mabw7gnhe DOT fsf AT hod DOT lan DOT m-e-leypold DOT de> 	<073801c79665$d8637b10$2e08a8c0 AT CAM DOT ARTIMI DOT COM>
From: "Markus E.L." <ls-cygwin-2006 AT m-e-leypold DOT de>
Date: Mon, 14 May 2007 22:53:47 +0200
In-Reply-To: <073801c79665$d8637b10$2e08a8c0@CAM.ARTIMI.COM> (Dave Korn's  message of "Mon, 14 May 2007 21:24:16 +0100")
Message-ID: <73zm47f7ok.fsf@hod.lan.m-e-leypold.de>
User-Agent: Some cool user agent (SCUG)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


"DaveKorn" writes:

> On 14 May 2007 21:27, Markus E.L. wrote:
>
>> often. Did you mean setup.ini instead? But setup.ini is coming from
>> the mirror, isn't it?
>
>   Well, it comes from the mirror, same as the packages do, but it isn't
> generated there, if that's what you mean.

No, that wasn't what I meant. I thought, just for a moment, wether
setup.exe wouldn't take the setup.ini from the master site every time
to ensure that it is current. Of course then the mirror site wouldn't
necessarily be up date, so that was not really good idea. Just
triggered by Larry's idea about the propagation delay, which, then, I
really don't get.

>> (And this is a serious question: If it comes from the mirror, what
>> happens if a mirror has setup.ini updated, but not all of the packages
>> yet?)
>
>   Setup.ini is autogenerated on cygwin.com every five or ten minutes or so.
> It will only change /after/ the package changes on cygwin.com, so the mirror
> will either get the changed package but not the new .ini, or it will get both,
> but it shouldn't be possible to get the new .ini without the changed package
> unless it is travelling backwards in time. 

I should possibly read up some more about running a mirror. What I
thought though, was more along the lines of that the mirror starts
downloading the master site from the top and might fetch setup.ini and
then take considerable time until atually getting the changed package
deeper down the tree. This is probably not how mirrors are actually
run (by doing a plain rsync or recursive wget).

>   Which would be a very odd way to run a mirror!

:-) But very interesting. I sometimes would want a mirror that travels
back in time.

Regards -- Markus


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/