site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Oct 31, 2007, at 4:15 AM, Andreas Fink wrote: I can't resist at least one more comment. Great! I look forward to helping review your kernel patch. :-) cr _______________________________________________ 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... If Andreas wants to add SCTP support to the kernel, I have a proposal. When the leopard sources appear (in a few days, weeks or months), do the hard work to create the KPI infrastructure you need to support this protocol. Write the code, create tests if possible along with a test harness (hard work for kernel code), plus documentation and submit it to Apple as a patch. Publish this patch far and wide, take feedback from other interested kernel hackers and *maintain* the patch as new Leopard releases ship. Make it your mission to get the patch accepted in 10.5.x or whatever the next major release is in 20 months. Don't wait for Apple to do this work for you (once you have the sources). Do the work, create the patch and be its champion. I think Apple folks would be surprised. Thus far the level of "community" support for kernel patches barely rises above *apathy*. Anyone who created a kernel patch and tried to support it this way would probably garner some sub-rosa engineering support within Apple simply because they'd be impressed with the effort. Interesting idea. I'll definitively bite into that one... but it basically means no benefits because it basically means doing the same thing with every release. So to make a public API for just one release. HOWEVER: I've just seen the source has been posted... so back to WORK... This email sent to site_archiver@lists.apple.com