X-Spam-Check-By: sourceware.org
Date: Sun, 15 Jan 2006 23:56:09 -0800
From: Yitzchak Scott-Thoennes <sthoenna AT efn DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Installing cygwin by manually copying c:\cygwin to another machine
Message-ID: <20060116075609.GB2088@efn.org>
References: <cd30ef8c0601130100q25a590b3lb45c2d2846440a7b AT mail DOT gmail DOT com> <1137149072 DOT 2980 DOT 251770934 AT webmail DOT messagingengine DOT com> <43C789D2 DOT 8020505 AT equate DOT dyndns DOT org> <1137201240 DOT 1365 DOT 251826199 AT webmail DOT messagingengine DOT com> <43C851B8 DOT 3000307 AT equate DOT dyndns DOT org> <1137203965 DOT 3893 DOT 251827605 AT webmail DOT messagingengine DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1137203965.3893.251827605@webmail.messagingengine.com>
User-Agent: Mutt/1.4.2.1i
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

On Fri, Jan 13, 2006 at 08:59:25PM -0500, Brett Serkez wrote:
> [snip]
> > Not particularly, assuming you use the same local package cache on
> > each machine, especially if you use the trick for pulling in all the
> > packages you want automatically.
> 
> Right.
> 
> > I don't know about chere,
> 
> chere must have settings in the registry, as it adds a 'bash here' menu
> option in explorer when you right click on a directory.  You'd have to
> run 'chere -i' on the new system.
> 
> > That means that setup, services like sshd, cron, inetd, etcetera will
> > be available for installation.
> 
> Right, available for installation, you'd have to run the setup scripts.
> I suppose running ssh-host-config wouldn't be a bad idea, not only would
> it install the Windows sshd service on the new system, but it would
> generate unique host keys, otherwise both the new and old systems would
> have the same key.
> 
> Sounds like this is doable, but there may be a series of commands that
> need to be run, depending on the original installation.

I'm not sure what this approach buys you over running setup.exe in
unattended install mode on a copied local package cache, except
fragility.

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