DragonFly 4.0 released!

The 4.0 release of DragonFly is out!  Quoting from the release page:

Version 4 of DragonFly brings Haswell graphics support, 3D acceleration, and improved performance in extremely high-traffic networks. DragonFly now supports up to 256 CPUs, Haswell graphics (i915), concurrent pf operation, and a variety of other devices.

The more eagle-eyed downloader will notice it’s version 4.0.1, not 4.0.0.  That’s because nobody trusts .0 releases I tagged 4.0.0 just before a few useful commits went in, and it’s better to retag to make sure everyone got them.  See also my message to kernel@/users@

7 Replies to “DragonFly 4.0 released!”

  1. BSDfan says:

    Is support for FUSE broken in DragonFly?
    I don’t see any FUSE (ntfs-3g, exfat, etc) packages in dports.

  2. John says:

    broken? no, it never existed.

  3. BSDfan says:

    Oh, I see.
    However I always thought that DragonFly supports these filesystems via PUFFS.

  4. John says:

    puffs doesn’t actually work and all these ports needs libfuse port which won’t build (and probably wouldn’t work right if it did)

  5. Anonymous says:

    I thought PUFFS was OpenBSD specific.

  6. BSDfan says:

    PUFFS is NetBSD specific. OpenBSD has FUSE support from 5.4 version and DragonFly is the last from BSD family which doesn’t have working FUSE support. IMHO this is very important feature for desktop usage. Possibility for reading and writing HDD/SSD/flash drives formatted with NTFS or exFAT filesystems would be very handy. Second feature IMHO would be support for newer UDF format (NetBSD has the best support for this).
    So, does anyone know if someone is working on this to fix it?

  7. John says:

    DragonFly has puffs. It’s just not stable. Nobody cares, nobody is working on it. I woudn’t mind removing it, frankly.

    I’m not impressed with FreeBSD FUSE either. None of the fuse ports have maintainers, nobody answers FUSE filesystem bugs, and I don’t think anyone is even designed to fix fuse kernel issues.

    puffs/fuse — interesting idea, but ultimately a failure. I guess people will need another way to ready ntfs or exfat. Apparently it’s not an pressing issue for the masses.

Comments are closed.