Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
BSD

DragonFly BSD 4.0 Released 66

An anonymous reader writes 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.
This discussion has been archived. No new comments can be posted.

DragonFly BSD 4.0 Released

Comments Filter:
  • I know that DragonFly BSD forked from FreeBSD about a decade ago. What are the major differences between DragonFly and FreeBSD?

    Also what does the boot process look like?

    • by pigiron ( 104729 )

      Is your finger broken?

    • Also what does the boot process look like?

      They switched to systemd. kidding :)

      • That really is a concern for many distros, though.

        I have to admit that the Linux principle "do one thing and do it well" actually does work. Did some things need improvement? Yes. But systemd has become like a Cthulhu in the system, with tentacles everywhere, far beyond its original concept.

        I have to agree with some others who have said that systemd resembles Windows a hell of a lot more than Linux.
    • by fender_strato ( 776201 ) <carlos_canavessi@@@hotmail...com> on Wednesday November 26, 2014 @03:26PM (#48469573)
      "Dillon started DragonFly in the belief that the methods and techniques being adopted for threading and symmetric multiprocessing in FreeBSD 5 would lead to poor system performance and cause maintenance difficulties. He sought to correct these suspected problems within the FreeBSD project. Due to ongoing conflicts with other FreeBSD developers over the implementation of his ideas, his ability to directly change the FreeBSD codebase was eventually revoked. Despite this, the DragonFly BSD and FreeBSD projects still work together contributing bug fixes, driver updates, and other system improvements to each other. Intended to be the logical continuation of the FreeBSD 4.x series, DragonFly's development has diverged significantly from FreeBSD's, including a new Light Weight Kernel Threads implementation (LWKT), a lightweight ports/messaging system, and feature-rich HAMMER file system. Many concepts planned for DragonFly were inspired by the AmigaOS operating system." According to http://en.wikipedia.org/wiki/D... [wikipedia.org]
      • by cant_get_a_good_nick ( 172131 ) on Wednesday November 26, 2014 @04:49PM (#48470161)

        This... specifically the way he felt FreeBSD over complicated threads.

        A simple implementation would be "every user space thread has a kernel thread". FreeBSD kind of went to the "lets give a lot of knobs and levers for people to play with." It went to something similar to the old Solaris multithreading model where you can say how many kernel threads for each user thread, or one kernel thread per app, or whatever combination. This added a lot of complexity. Ironically, this happened just as Solaris was moving to a much simpler 1:1 model.

        Dillon was worried that it would make it so complicated that only a handful of people could do any coding in the kernel scheduler. This for very little gain as most people couldn't do anything useful with those knobs and levers. He was kind of proven right. FreeBSD kind of stalled out for a bit.

        That was the initial reason for the break. Over time, the design diverged to where he added more message passing architecture in the kernel, inspired by the Amiga's design.

  • by __aaclcg7560 ( 824291 ) on Wednesday November 26, 2014 @03:35PM (#48469651)
    Another OS that has dropped support for 32-bit architecture. This is probably not an issue for most users as 32-bit processors are less common these days. If you have an older machine with a 32-bit processor, you can't slap on the latest and greatest *nix OS.
    • Hey, now that the systemd nutters have broken Linux we can go back to calling Unix Unix instead of *nix.

      • Hey, now that the systemd nutters have broken Linux we can go back to calling Unix Unix instead of *nix.

        At least one trademarked Unix [opengroup.org] uses a launch-on-demand-based init daemon [apple.com], so it's not clear that the use of systemd-the-daemon is sufficient to make Linux not be a Un*x. Maybe systemd-the-software-bundle is sufficient.

        • Hey, now that the systemd nutters have broken Linux we can go back to calling Unix Unix instead of *nix.

          At least one trademarked Unix [opengroup.org] uses a launch-on-demand-based init daemon [apple.com], so it's not clear that the use of systemd-the-daemon is sufficient to make Linux not be a Un*x. Maybe systemd-the-software-bundle is sufficient.

          It changes the user space sufficiently that the historical text configuration files for logging and other facilities no longer function compatibly with the VSC test suite. If those were changed back, or the test suite was somehow made independent of configuration variances for the purposes of testing, I might agree with you, but as it is, there is no way a systemd based system would pass VSC, and would also likely fail VSX, and the parts of the VSTH and VSRT testing, based on the posix_spawn implementation

    • The release anouncment makes it seem like they didn't have old or low end desktops in mind as their audience.

    • Another OS that has dropped support for 32-bit architecture. This is probably not an issue for most users as 32-bit processors are less common these days. If you have an older machine with a 32-bit processor, you can't slap on the latest and greatest *nix OS.

      PC-BSD also dropped 32-bit support a year ago.

      • by fnj ( 64210 )

        And FreeBSD tells you that 32-bit will hamstring ZFS, so if you want the good stuff on FreeBSD it's 64 bits for you.

    • This only applies in the PC world, which means it applies to FreeBSD. But there are BSD alternatives that like to target more than PCs where 32-bit CPUs are more common.

      • by x0ra ( 1249540 )
        ZFS will hamstring your system no matter what...
        • I figured that out with FreeNAS on an older Dell system. It was always crashing. The minimum hardware requirements for FreeNAS 9.x was more demanding than previous versions. In particular, ZFS required 8GB minimum (or 1GB per terabyte of raw storage) for optimal performance. Rebuilt the system with a different old Dell system that had more memory.
    • by jma05 ( 897351 )

      I have a 64bit processor on my laptop, but I elected to go back to a 32bit OS because I decided that having more free RAM is more important to me than the 64bit advantages. All my VMs use 32bit OSes even on 64bit hosts for the same reason. So its not just for older machines.

  • 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.

    I'm not sure if it supports Haswell graphics or not. Can someone look in to that for me?

    • Why is Intel HD Graphics called "i915", by the way? In my mind it always reminds of the 915G chipset from a decade ago.
      • ding ding ding! We have a WINNER!!!

      • by nawcom ( 941663 )
        It's the common name for the open source Intel GMA driver for the BSDs and Linux. Supports some old Intel GMA900 (915g) all the way to Haswell Intel HD support, with some obvious exclusions like GMA500. I don't know if it supports older, though I believe in the Linux kernel they moved old 815G support to i915.
    • by x0ra ( 1249540 )
      It does, but it's still buggy. Which is rather laughable, they're shipping a release to get beta-tester to hopefully fix the code :-/
  • by Anonymous Coward

    Because of her humongous shittiness and discrimination related work on Twitter, the FreeBSD name has gone into disrepute.

    Please sack her or tell her to rename her handle to freeBS-girl.

    • by x0ra ( 1249540 )
      She's gonna call other FreeBSD committers (say, Colin Percival, her former mentor) to her rescue, and then she's gonna ban/block you, because it's all she knows about. I guess she could have a chance to work in China for their Great Firewall, but I doubt she has the competence. Even her work in FreeBSD is pretty laughable, it's all on her LinkedIn account, there should not be more than a dozen commit for a rather miserable line count.
  • Seriously? This deep in the thread? And nobody's gone for the classic? Fine, I'll get it started...

    It is now official. Netcraft has confirmed: *BSD is dying

    One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known

Real programmers don't bring brown-bag lunches. If the vending machine doesn't sell it, they don't eat it. Vending machines don't sell quiche.

Working...