site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com <http://developer.apple.com/programs/> S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Technical Support * Networking, Communications, Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... At 9:39 -0600 29/12/04, Daryl Warkentin wrote: I understand the UDF source code has not been released. That's true. Our current UDF VFS plug-in contains code that we can't release under APSL. Will support for version 2.0 of the UDF file system be added soon? As Justin says, Apple generally doesn't comment on our future plans, modulo big marketing announcements such as Tiger. If not, can it be worked on by outsiders (i.e. me)? Well, that depends on exactly what you mean. If your want to improve /our/ UDF VFS plug-in, the answer is "No, because it's not open source." If you mean "Is it possible to write a UDF 2.0 VFS plug-in for Mac OS X?", the answer is "Yes, see below." At 13:12 -0600 30/12/04, chuck remes wrote: The driver model (IOKit) for darwin/OSX is sufficiently different from other OSs that doing a simple port as you describe is anything but simple. That's true, but not really relevant. UDF is not an I/O Kit driver, it's a VFS plug-in. Apple's VFS architecture (at least prior to Tiger) is very similar to the other BSDs, so it should be relatively simple to port a UDF driver from another BSD to Mac OS X. The drawback here is the binary compatibility story. BSD plug-ins (VFS and NKE) have a very poor binary compatibility story on current versions of Mac OS X. We are fixing that in Tiger, but that means that any VFS plug-in work that you do on 10.3 will have to be ported to Tiger. My advice is that, if you're planning to do VFS work, join ADC as a Select member, download the Tiger seed build, and start work on that. However, I should caution you that, as a third party developer, it's always unwise to start project where there's an obvious customer need in a large market that Apple is strongly committed to. This email sent to site_archiver@lists.apple.com