Slashdot Mirror

← Back to Stories (view on slashdot.org)

DragonFly BSD Announces 1.0RC1

Posted by CowboyNeal on from the so-close-to-release-it-hurts dept.

CoolVibe writes "Matt Dillon announced the availability of DragonFly BSD's 1.0 Release Candidate #1. Get it at Dragonfly BSD's site (please use a mirror or post mirrors as comments). Changes and features include: variant symbolic links, UDF support, lightweight kernel threads, message passing, GCC 3.4 in the tree, binutils 2.14, Kernighan's awk 2004-02-07, BIND 9.2.4 rc4, CVS 1.12.8, libpcap 0.8.3, tcpdump 3.8.3, less 381, MMX/XMM kernel optimizations are now on by default, greatly improving bcopy/bzero/copyin/copyout performance for large (>4K) buffers, XIO, acpica5, new AC'97 codec support, network stack revamping, long standing bug fixes for wide variety of support and stability issues, and way, way, way more. A new installer is also in the works that uses DragonFly's new CAPS IPC mechanism. The installer beta is available from LiveBSD. (Not updated to RC1 just yet, but it gives a nice idea of the progess made)"

2 of 124 comments (clear)

  1. Re:Suffer fools gladly by Anonymous Coward · · Score: 4, Insightful

    There is a huge difference in developer support, which is the main reason that FreeBSD is the only fork that has reasonably modern performance features.

    Sorry, but that's bullshit. With people like Poul-Henning Kamp nuking stuff they don't consider useful (see the recent ibcs/sysv compat thread on freebsd-current) and doing damage to the team work others have put so much effort on, I see more and more people migrating to NetBSD (alpha support is almost EOL'd for FreeBSD too) and DragonFlyBSD.

    NetBSD's scheduler activations already outperform FreeBSD's KSE, and work on most architectures (as opposed to FreeBSD's x86-only KSE)

    Sorry, but NetBSD is already ahead of the game, sans the flamers like Poul-Henning and David O'Brien.

    Maxim Hermione

  2. Re: Welcome to the same hell by Anonymous Coward · · Score: 4, Insightful

    Linux doesn't do any of those, since it's just a kernel. Some distros might hack in something like PAX, but its nowhere near as pervasive and as well tested as on OpenBSD - it takes toolchain support for randomised shared libraries, and OpenBSD also fixed a lot of bugs in Propolice while integrating it, showing noone else has seriously tried it to use it before across multiple architectures.

    Oh I didn't even mention stuff like StackGhost on sparc...