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: <00c501c2d6ae$7ee314e0$78d96f83@pomello> From: "Max Bowsher" To: "Dieter Meinert" , References: Subject: Re: Why the rash of people bypassing setup.exe to install? Date: Mon, 17 Feb 2003 18:00:45 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Dieter Meinert wrote: > I was going through all this thread wondering if noone > would see the (to me as a late Un*x guy) obvious: > > Consider a slooooooooooooooooooooow net connection, e.g by > 14.4 K Modem, or as Hannu does, > several hosts to be updated. The natural thing to me > appears to download the tar file, unpack > it somewhere, probably on a CD, and then run setup on your > target machine. What are you talking about? You do *not* unpack the downloaded tar files manually. EVER. You use setup.exe. Why do you think that is a good idea? > This would account for a load on the tar files while setup > isn't really triggered on the mirrors. I think you are confused. Setup is an .exe that is run locally. The phrase "setup isn't triggered on the mirrors" is meaningless. > In this context I'd consider it a bad, at least confusing, > idea to rename the tar.bz2 files to something else. It seems to me that you are confused, and if the files had been renamed, you wouldn't be. Max. -- 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/