offline cygwin install question

Thu Jun 27 18:25:00 GMT 2013

I have win7 64-bit computers set up in another location. It would seem 
that the easiest option would be to make sure that one of those is up to 
date and then just tar up the cygwin directory and move it. I have also 
found that you can just tar up the local package directory and then run 
a local install, but this seems to have issues if there are packages in 
the local install dir from more than one mirror.

If I download the normal setup.exe to a 64-bit windows install, will it 
automatically install the 4-bit version? have never seen the setup64.exe 
that was mentioned in a previous post. Where would that be located?

I have to assume at this point that the cygwin I have running on w7 
64-bit installs is the 32-bit version of cygwin, since I didn't do 
anything special when I set those up. I know that many 32-bit 
applications run perfectly well on a w7 64-bit install. What specific 
advantages would there be in running the 64-bit version of cygwin?

The main thing I want to do is to upgrade to the minty terminal and make 
sure I am using the most current version of cygwin. I think that the 
version on this rig is pretty old.

Thanks for the advice,


Christopher Faylor wrote:
> On Thu, Jun 27, 2013 at 10:32:33AM +0200, Corinna Vinschen wrote:
>> On Jun 26 16:16, LMH wrote:
>>> I have a win7 64-bit machine that is not online and I want to update
>>> the cygwin install. What is the best method for doing this? Can I
>>> just copy the current cygwin install off of my XP 32-bit machine and
>>> drop it into the 64-bit win7 rig, or will that create a problem?
>> The easiest way, especially if you have more than one machine, is
>> IMHO to create a local mirror of the Cygwin distro first:
>>   <Check if you have at least 30 Gigs of free space>
>>   mkdir cygwin
>>   rsync -av --delete-after cygwin
>> This creates a local mirror of the 32 and 64 bit Cygwin versions.
>> The 32 bit version is more complete and runs on 32 and 64 bit,
>> as cgf pointed out.
> Yow.  Please don't encourage people to perform high-bandwith-consuming
> operations to  I don't want to have to start limiting rsync
> access to because everyone thinks that doing full copies of
> the release area is a good idea.
> You could use an rsync mirror (see for
> this but this seems like severe overkill for what the OP wanted.
> Duplicating their installation from one system to another shouldn't
> involve downloading the whole Cygwin release, whether it is 32-bit or
> 64-bit.
> cgf
> --
> Problem reports:
> FAQ:         
> Documentation:
> Unsubscribe info:

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list