Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"ntfsd__AT__pavitrasoft" <ntfsd AT pavitrasoft DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Cygwin to make ext2fs, xfs, reiserfs aware in windows
X-IPAddress:	67.161.48.244
MIME-Version:	1.0
Message-Id:	<E1B3MEQ-0005X0-00@host22.ipowerweb.com>
Date:	Tue, 16 Mar 2004 13:36:14 -0800
X-AntiAbuse:	This header was added to track abuse, please include it with any abuse report
X-AntiAbuse:	Primary Hostname - host22.ipowerweb.com
X-AntiAbuse:	Original Domain - cygwin.com
X-AntiAbuse:	Originator/Caller UID/GID - [564 565] / [564 565]
X-AntiAbuse:	Sender Address Domain - host22.ipowerweb.com

Hi all,
What would be best way to make cygwin dll aware of existence of UNIX 
file systems ext2fs, ffs, nfs, xfs and reiserfs.  Currently with our 
software Crossmeta it will go through windows layer and the results 
will not be good. It will have the same problem of ls -l taking lot of 
time and security uid/gid mapping confusion.  Instead if it can be 
converted to make use of VFS style calls getdents, stat ..etc directly 
to crossmeta the results will be great. Crossmeta also provides windows 
native file system via loopback file system driver.
I am guessing the file handler code would be the starting point for 
this and replace dll entry points for those. Is this going to be lot of 
effort?

PS:
Crossmeta can be downloaded from 
http://www.pavitrasoft.com/products/crossmeta/

--
Crossmeta - FFS, nfs, ext2fs, reiserfs and xfs file system for Windows
Download here http://www.pavitrasoft.com/


--
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/

- Raw text -