site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Nov 14, 2006, at 6:13 AM, Thomas Tempelmann wrote: # RELEASE = [... cd9660 ...] and remove cd9660. Ronnie _______________________________________________ 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... Hi, I've been writing ISO 9660 file system drivers for Mac OS 9 and for Toast, and I'd now like to bring OS X's old ISO 9660 driver up to date, with the hope that Apple will incorporate the improvements into OS X. As I've never done anything with Darwin before, I have a few beginner's problem. Please guide me a little: 1. All I need is to build the XNU sources, right? That gets me a new kernel which I can then boot from. But I wonder if, for testing, there is a better way, i.e. if I can exchange the file system alone at runtime without the need to rebuild the entire kernel? I've heard that it's possible to load file systems dynamically, I just wonder how hard it would be to turn that ISO file system from the kernel into a loadable one? Or is the one in the kernel not even the one OS X uses - is there another one that's loaded later? You should be able to turn off the ISO filesystem in the kernel by turning off the "cd9660" configuration option in MASTER.i386 and/or MASTER.ppc in the bsd/conf directory. Find the line that looks something like You can then try to turn cd9660 into a kext, but that might be difficult since it probably depends on having access to internal kernel functions that aren't exposed through KPIs... 4. Lastly, if I should succeed, what's the chances that Apple incorporates the improvements? How would I go about that? I've already filed a bug report about what I plan to fix, but I know of others who files related bug reports years ago and nothing ever changed with the iso 9660 file system. As others mentioned on this list, you should file a bug on <http:// bugreport.apple.com> and attach your patches. Also, mention it on the list and hopefully the Apple engineers on the list will try to champion your cause. :) This email sent to site_archiver@lists.apple.com