delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2000/03/01/13:57:36

Message-Id: <200003011857.NAA04965@delorie.com>
Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: "Parker, Ron" <rdparker AT butlermfg DOT org>
To: "'cygwin-developers AT sourceware DOT cygnus DOT com'"
<cygwin-developers AT sourceware DOT cygnus DOT com>
Subject: RE: Setup over a previous installation
Date: Wed, 1 Mar 2000 12:54:09 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)

> -----Original Message-----
> From: Earnie Boyd [mailto:earnie_boyd AT yahoo DOT com]

<snip>

> Hmm...  WAIT A MINUTE, mount.exe requires cygwin1.dll which 
> isn't installed
> yet.  If you store cygwin1.dll in c:\temp then cygwin1.dll 
> will do an automount
> for / to point to c:/temp.  I don't think this is what you want.

<snip>

Actually it would automount / to point to WINDRIVE:\.

I think it may be a safe bet to assume that if a user has
{HKLM,HKCU}\Software\Cygnus Solutions in their registry that they already
have some mount entries from some Cygnus software.  My proposal would be to
check for this registry key and if found issue a "mount --import-old-mounts"
followed by "mount" and parse the output looking for the root directory.
Otherwise, I would assume a default directory of WINDRIVE:\cygwin.

Note: This is only the default root directory. The user would still be
allowed to override it.

Does this make sense to everyone?

My other concern is that the umount-mount sequence for changing the root
directory only works from bash and not from the Windows command line.  When
using the windows command line to issue the (re)mount command, an automount
occurs in cygwin1.dll.  My current line of thought is that setup.exe will do
a LoadLibrary on cygwin1.dll followed by an unmount-mount sequence and that
this should suppress the automount that occurs at the Windows command
prompt.

Could someone more experienced with the workings of cygwin1.dll let me know
if this is off base?

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019