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
Message-ID: <3948E232.8811D07F@dothill.com>
Date: Thu, 15 Jun 2000 10:03:30 -0400
From: Jason Tishler <Jason DOT Tishler AT dothill DOT com>
Organization: Dot Hill Systems Corporation
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Cygdrive Path Prefix Patch Issue
References: <3946A03A DOT C5452A47 AT dothill DOT com> <200006132109 DOT RAA08578 AT envy DOT delorie DOT com> <20000613172026 DOT A17487 AT cygnus DOT com> <200006132123 DOT RAA08705 AT envy DOT delorie DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Chris Faylor wrote:
> On Tue, Jun 13, 2000 at 05:23:13PM -0400, DJ Delorie wrote:
> >
> >> I think this is the best solution, actually.  It could return a flag
> >> indicating that this was a "cygdrive prefix" mount.  I don't know
> >> why this would screw up anything.
> >
> >I was thinking of "df".
> 
> Good point.  It's worth looking at the df sources to see if this would
> cause a problem

I looked into the df source -- specifically read_filesystem_list() in
fileutils/lib/mountlist.c.  The current implementation would attempt
to interpret the cygdrive prefixes as ordinary file systems.

> and if there is a way to work around it.

I can add Cygwin specific code to ignore the cygdrive prefixes.  But,
I'm concerned that all other code that uses getmntent() would need a
similar change.

DJ Delorie wrote:
> Could getmntent be extended to return, as one of the entries, the
> automount path?

Implementing the above is certainly doable but will be fairly ugly.

Do we really want to go with this approach?  If the consensus is yes,
then I will do so.  Are there any other, hopefully better, alternatives
before I dive in?

Thanks,
Jason

-- 
Jason Tishler
Director, Software Engineering       Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corporation         Fax:   +1 (732) 264-8798
82 Bethany Road, Suite 7             Email: Jason DOT Tishler AT dothill DOT com
Hazlet, NJ 07730 USA                 WWW:   http://www.dothill.com