Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Tue, 13 Jun 2000 17:34:38 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Cygdrive Path Prefix Patch Issue Message-ID: <20000613173438.C17607@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006132123.RAA08705@envy.delorie.com>; from dj@delorie.com on Tue, Jun 13, 2000 at 05:23:13PM -0400 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 and if there is a way to work around it. cgf