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: Tue, 13 Jun 2000 17:09:48 -0400
Message-Id: <200006132109.RAA08578@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: Jason DOT Tishler AT dothill DOT com
CC: cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <3946A03A.C5452A47@dothill.com> (message from Jason Tishler on
	Tue, 13 Jun 2000 16:57:30 -0400)
Subject: Re: Cygdrive Path Prefix Patch Issue
References:  <3946A03A DOT C5452A47 AT dothill DOT com>


[moved to cygwin-developers]

> I would like to follow the above suggestion and further enhance
> mount by adding --show-cygdrive-prefix functionality.
> Unfortunately, given the current public API there is no way (that I
> could find) to pass the cygdrive path prefix information from inside
> Cygwin to mount for display purposes.  Is it acceptable to add
> something like cygwin_get_cygdrive_paths() to the public API?  Any
> other suggestions?

Could getmntent be extended to return, as one of the entries, the
automount path?  It would probably mess up *some* program somewhere.

Otherwise, either add a new set/get pair, or use the existing
cygwin_internal() function for "hidden" functions.