IRC Forum with Matthew Dillon of DragonFly BSD
weebl writes "Thursday October 9th at 6:00PM PDT (9PM EDT/1AM GMT) SlashNET's #forum channel will be hosting a Q&A session with Matthew Dillon of the DragonFly BSD Project. This is your opportunity to ask about DragonFly BSD, BSD in general, or any other questions you might have for him.
DragonFly BSD was first announced this past July." If you can't make it to the forum, SlashNET will have a bot running earlier in the day for question submissions, and logs available afterward.
(Joking aside....)
Everyone knows that the BSD codebase is infinitely more clean than the Linux codebase.
Remember, the last few times there have been license issues with FreeBSD, it was people (*ahem* linux *ahem*) stealing FROM them.
--
Use Vobbo for Video Blogs
Perhaps you can learn at this webpage, dipshit.
Matt Dillon deserves absoluetely no pitty. His outrageous immaturity justified the revocation of his commit bit 1000 times over. Shame on you for painting him to be some kind of victim.
The linux hacker
He didn't use the right words. He meant that Linux kernel developers use code from BSD and don't have the decency to give credits -still perfectly within the BSD lincese. Of course this is not something new to Linux. IMHO, i'm not sure if Linux is more BSDish or SCOish -time will tell.
>There's a LOT of work going into fine grained locking to allow faster SMP
:-)
Unless I'm totally wrong, this is exacly the opposite from what DragonFlyBSD is about. Matt has never liked the way FreeBSD and Linux are designed, a kernel sprinkeled with locks.
Instead, he's trying to do a kernel where kernel-side subsystems communicate via message-passing, not too far from how exec.library worked in AmigaOS.
So Matt and his cowboys/cowgirls are actually removing locks.
Regards, Tommy
Matt already wrote a SHITLOAD of code for DragonFly. He already overhauled the threading in the kernel, and put in a totally new slab allocator. Right now he's overhauling the namecache system.
Also, the DragonFly gang are doing chores nobody in the official FreeBSD camp cares enough about, like removal of __P(), removal of the 'register' keyword and ANSIfication of old K&R code. Of course we'll be seeing those efforts back in the other BSDs.
These changes that Matt and his merry gang of hackers are making are changes that would never be accepted by the FreeBSD deities with a commit bit,because they're intrusive. Hence the reason Matt forked off DragonFly.
He never left FreeBSD, dammit. Get over it.