Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <432F1B2B.441370E6@dessent.net>
Date: Mon, 19 Sep 2005 13:10:19 -0700
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems
References: <0IN200HC9Y8P15@pmismtp01.mcilink.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: cygwin@cygwin.com

Mark Paulus wrote:

> Has anyone explored the option of an IFS that would implement the cygwin
> managed filesystem semantics, but it would be transparent to all
> cygwin apps.  From the brief investigation I have done, it appears there would
> need to be 2 flavors, 9x/ME & NT/2K/XP, but that would relieve a big burden
> from the cygwin1.dll, I would estimate.

I don't know much about writing kernel mode code.  MS charges $109 for
the IFS SDK, so unless somebody's company sponsored it most people would
not have the tools or documentation.  I don't know if w32api has
reimplemented the required headers and libs to be able to compile such a
thing with gcc, and I don't think cygwin would want to accept binaries
that require MS tools to build.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/