Slashdot Mirror

← Back to Stories (view on slashdot.org)

DragonFlyBSD Team Interviewed

Posted by CowboyNeal on from the getting-to-know dept.

lowks writes "A nice little interview from the ONLamp BSD advocacy page where we get to peer a little into the goings ons and updates as well as plans for DragonFlyBSD. Highlights include the rationale behind DragonFlyBSD and peeks into the current engine as well as goodies planned to be implemented in the future versions. DragonFlyBSD is another flavour of BSD which forked from the FreeBSD 4.x branch not too long ago. It's headed by Matt Dillon, who forged out on his own and started DragonFlyBSD due to technical differences with the FreeBSD team ."

2 of 39 comments (clear)

  1. Technical differences? by Anonymous Coward · · Score: 1, Interesting

    If by "technical differences with the FreeBSD core team" you mean "kicked off the team and mailing lists for hostile, inflammatory behavior," then you're right on the money.

    I listened to Dillon's crap on the -current mailing list and elsewhere. 'Technical differences' were the least of the concerns in getting rid of him.

    Sure, he's competent, and he's contributed some great things to FreeBSD over the years, but that doesn't mean he's not a troll.

  2. New BSD on the block by CustomFort · · Score: 4, Interesting

    It seems like this new DragonFLy BSD project could become very interesting. I have been wondering for a while what their exact purpose was for the split, and I think I like it. Their goal of implementing cleaner and more scalable structures sounds like a worthy one, even if it is a long tem goal.

    Who knows, someday the BSD world might break up lke this:
    OpenBSD is for Routers and firewalls
    NetBSD is for XBox/Toaster/microwave/everything else =P
    FreeBSD is for Servers
    and
    DragonBSD is for SSI Supercomputers or other highly scalable systems.