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
Date: Thu, 25 May 2000 01:05:06 -0400
Message-Id: <200005250505.BAA02497@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: auto-mounting /


OK, I'm working through the code to LoadLibrary cygwin1.dll (*that*
was a project) and using getmntent() to find any existing "/" mount.

Guess what?  There's always one, because starting cygwin1.dll creates
on if needed.

Why?  Why can't we just leave "/" unmounted if there isn't one?  Won't
that mean that the default is that "/" is the root of the current
drive, which might make a lot of sense for cygwin programs running
outside a fully configured environment?

Meanwhile, I've at least reconfigured cygwin1.dll to not do the
mounting if it was loaded via LoadLibrary.  I had to add a new DLL
entry point to do further initialization that init.cc couldn't do,
which an app calls after LoadLibrary to tell the dll "you aren't part
of a cygwin app" and enables even more functionality.  I'm not sure if
we can call this from the init.cc startup hook; that may get called
for cygwin-built dlls too, if *they* are called via LoadLibrary.