Slashdot Mirror

← Back to Stories (view on slashdot.org)

IRC Forum with Matthew Dillon of DragonFly BSD

Posted by CowboyNeal on from the up-close-and-personal dept.

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.

3 of 223 comments (clear)

  1. The real shame by the+man+with+the+pla · · Score: 3, Insightful

    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
  2. Re:focus by thallgren · · Score: 5, Insightful

    >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

  3. Re:Shame.... by CoolVibe · · Score: 4, Insightful
    Why the hell is everyone thinking that Matt left? This fork isn't an 'angry' fork. DFBSD is just another BSD based off of FreeBSD 4 that is exploring some new ideas that Matt has. It's evolution. If DragonFly beats the pants off of 5.x in the future, I'm sure lots of DragonFly code will be appearing in the "official" FreeBSD tree.

    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.