This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 31 October 2006 12:47, Brian Dessent wrote:...
Ben Wing wrote:
Also, has anyone considered building something like FUSE into Cygwin? ... The result would be Cygwin-specific, i.e. wouldn't work in non-Cygwin utilities, but that's OK; the benefit of having such a system would be so great that it would vastly outdo the trouble of not being able to use non-Cygwin utils.No doubt that many have *considered* it, but nobody has done it (to my knowledge at least.)
If you do it right and make it a real filesystem driver, then you both need the expertise and time to code and test a NT kernel module,
Yes, of course. Goes without saying really.
And in order to get any patches of this kind accepted by Cygwin maintainers you'd need to show clear evidence that the presence of all this extra code did not affect performance of the standard filesystem access and path translation. That part of the code tends to be somewhat of a sore spot, due to the fact that it is already complex and easy to break, and a critical path performance-wise.
I think you worry too much. The kernel-mode driver would be nicely isolated, and we'd just need to add a new fhandler type to interact with it; the extra code wouldn't ever be called if not used.
-- 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/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |