Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BC8A088.E4366424@iee.org>
Date: Sat, 13 Oct 2001 21:14:00 +0100
From: Don Sharp <dwsharp AT iee DOT org>
X-Mailer: Mozilla 4.78 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: gnuwin32 <cygwin AT cygwin DOT com>
Subject: Re: cannot exec as
References: <3BC789B9 DOT B9AB2DD3 AT goingware DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



"Michael D. Crawford" wrote:
> 
> Yes, it seems the way I've been using a single download to install to two
> computers is the problem.
> 
> It fixed my problem to show the full listing in the installer, then select
> reinstall for each package (maybe it would be handy to have a quick way to force
> a full reinstall).

I believe if you remove /etc/setup/installed.db that a full install will
be called for, (no record of previous installation).

> 
> What would you advise to be the best way to download to one machine but install
> on two machines?  My habit of never throwing anything away has me perpetually
> short on disk space so I don't want to duplicate the download files.
> 

I have three machines all of which have access to each others filestore.
I do normal downloads to one machine and then install on the other
machines running setup and installing from the cygwin directory
containing latest and contrib directories. Works fine.

If you want to use a common directory structure, held on only one
machine, then you need the appropriate registry entries on each machine.
These are most easily created by doing a local directory setup on the
other machines after removing /etc/setup/installed.db before each
install. Thereafter, as long as you don't alter your mount points,
updating the master version should make the updates available to all the
machines.

I believe someone suggested a script approach which would just set up
the mount points. I can't remember whether it was published on the list.

HTH

Don Sharp


> Mike
> crawford AT goingware DOT com
> http://www.goingware.com/
> 
>    Tilting at Windmills for a Better Tomorrow.
> 
> --

--
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/