site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com = Mike _______________________________________________ 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... On Mar 22, 2007, at 2:50 PM, Craig Newell wrote: On Mar 22, 2007, at 17:10 , Michael Smith wrote: Neither of these are true. In addition, you truly have no idea of the scope of the work involved to identify, scrub, validate and package the number of source code projects involved in a Darwin source release. Does this mean that you can not recompile the sources and get a kernel that will function with all the usual Mac OS X applications? I am getting tired of poor filesystem performance and I was just thinking that I might spend a weekend fixing the obvious stuff in the VFS layer. As folks have noted, it is a special concern of the kernel team that it be possible for the kernel sources to be buildable by a third party into a viable replacement for the shipped kernel binary. If you're looking at making changes to the VFS layer, and you want them to be generally useful (by this I mean picked up and used for future Darwin versions) then I'd encourage you to go ahead and design your changes, then check in with someone like Terry Lambert to get a feel for how reasonable they might be in the context of Apple's ongoing work in that area. If you just want to tweak the bits for yourself, then the only caveat I would offer is that as with drivers, many of the filesystems are implemented as plug-in modules for the kernel and you may find yourself with binary compatibility problems. This email sent to site_archiver@lists.apple.com