From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17552 invoked by alias); 14 Feb 2002 20:20:23 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Received: (qmail 17459 invoked from network); 14 Feb 2002 20:20:20 -0000 Received: from unknown (HELO ligarius-fe0.ultra.net) (146.115.8.189) by sources.redhat.com with SMTP; 14 Feb 2002 20:20:20 -0000 Received: from enterprise-e.rfk.com (209-122-233-153.s1963.apx2.sbo.ma.dialup.rcn.com [209.122.233.153]) by ligarius-fe0.ultra.net (8.8.8/ult/n26500/mtc.v2) with ESMTP id PAA22746; Thu, 14 Feb 2002 15:20:18 -0500 (EST) Message-Id: <4.3.1.2.20020214150054.01f00a28@pop.ma.ultranet.com> X-Sender: lhall@pop.ma.ultranet.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Thu, 14 Feb 2002 12:20:00 -0000 To: "Mack, Daemian" , cygwin@cygwin.com From: "Larry Hall (RFK Partners, Inc)" Subject: Re: Cygwin Registry Entries and Scriptability? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-SW-Source: 2002-02/txt/msg00742.txt.bz2 At 02:51 PM 2/14/2002, Mack, Daemian wrote: >Hi all. I'm using Wise Installer to package and script an upgrade utility >for Windows machines. As part of this package, I'm using Cygwin's bash.exe, >rsync.exe, and the latest cygwin1.dll. At the moment, I'm just copying >these three files to the hard disk on the target machine, then launching a >bash.exe process with various arguments to rsync.exe to perform an rsync >over the net. > >I've heard that the way I'm doing it might not be correct, mostly because >the full setup of Cygwin provides registry entries concerning mount points, >so that, for instance, the directive /cygdrive/c/windows/desktop means >something to Cygwin utilities. > >But what I'm finding with my testing is that every time I run bash.exe on a >machine with no other Cygwin install, these registry entries are created >dynamically. I suspect cygwin1.dll is doing this when it's called by >bash.exe. > >To all appearances, then, a full install of Cygwin seems redundant, since I >can reference /cygdrive/c and get my work finished just fine without it. > >I'd like confirmation or denial of this, because I'd like to move forward >without scripting a full Cygwin installation, using only these three files. I'm not sure what you mean by a "full Cygwin installation, using only these three files". To people on this list, a full Cygwin installation is more than just the three files you indicate. /cygdrive is meant to represent implicit mounts to local hard drives. The Cygwin DLL takes care of generating these. Other mount points (/usr/bin, /usr/lib, and /) are created by setup.exe and are not dynamically created as needed. Your biggest concerns, though, should be: 1. Detecting an existing Cygwin installation so that your installation doesn't clash with Cygwin's. 2. Robustly handling a subsequent installation of Cygwin. It's worth noting that the installation you're describing would be considered a custom one by this list and should come with its own support channel. This list can't be it. I suspect that you're aware of this but in case you're not, it's an important point to consider. Hope that helps, Larry Hall lhall@rfk.com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- 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/