Exciting future ahead for BSD

FreeBSD LogoTrollaxor has written up an interesting piece about the history and future of the major BSD systems: FreeBSD, netBSD, OpenBSD, DragonFlyBSD and Darwin.

In the new year the Berkeley Software Distribution family of Unix-like operating systems is growing at a phenomenal rate and excitement over the possibilities for this operating system family is in the air. After unprecedented development and adoption as well as major shifts in the marketplace, it’s time to take a look at what’s new with this demonic family of operating systems.

FreeBSD

FreeBSD 5 was the darkest period in this operating system’s history and morale and marketshare were at an all-time low. The problem originated from merging BSD/OS into FreeBSD; though the two systems shared a lot of code, the difference of just a couple years was staggering. FreeBSD’s virtual memory and multi-processing code was immature, while BSD/OS’s libraries were archaic. Mating the two was a mess that cost FreeBSD face and kept users on an older branch from the Nineties, 4.11.

Now, with FreeBSD 7.0b on the horizon promising to wrap it all up, FreeBSD is once again taking the free Unix world by storm. It’s a tight, efficient codebase leveraging the best of BSD/OS, Darwin, and FreeBSD that users have been clamoring for. FreeBSD users and sites now have a shining future ahead of them.

… [discusses NetBSD, OpenBSD, DragonFlyBSD & Darwin]

With all of these great improvements to the Berkeley operating system family in the last few years, BSD is clearly where it’s at. Linux is a throwback to when Open Source was a hot buzzword and sharing code was a novel idea. Now, Apple and company use it as standard coding procedure to share and improve the tech they have and leverage their individual strengths.

Even when taking the few commercial Unices that still exist into account, like AIX and Solaris, BSD still owns the arena in its frantic steamroll to the top of the supercomputing mountain. Whether you want the general wholesomeness of FreeBSD, the KGB-like security of OpenBSD, the more experimental NetBSD or DragonFlyBSD, or the utter perfection of Mac OS X, BSD has your bases completely covered with room to grow in the future.

Read the whole article here

2 thoughts on “Exciting future ahead for BSD

  1. David says:

    I read the article; it is not very in-depth and it is quite opinionated. It focuses on the foibles (and _only_ the

    foibles) of Theo deRaadt (to the exclusion of the entire OpenBSD team) and slams OpenBSD unfairly; it also slams NetBSD unfairly as well over the change in

    numbering (for another view of the same situation, consider what happened in Slackware Linux – people get tired of resisting the tidal wave). The article

    also does not mention that OpenBSD has the largest support of wireless cards anywhere, nor that the same project is also responsible for OpenSSH and for the

    firewall PF (not to mention the lesser known CARP, OpenBGP, OpenNTP, and more).

    I don’t feel the treatment of the hard work of the various BSD teams was

    shown fairly. Too bad. I was hoping for a ‘State of the BSD Union’ article….

  2. Justin says:

    Kinda a pointless article; the facts aren’t even right.

    - It claims FreeBSD 6 was essentially created by Apple.
    - It calls the

    i386 ‘obsolete hardware’, comparable to the z80.
    - Gnome and KDE won’t run on NetBSD, according to the article.
    - ‘DragonFly 1.14 will be synced with

    FreeBSD 4.11 in what Dillon has called “mirrored perfection.”‘ – there’s no such thing as DragonFly 1.14, and there’s no ‘syncing’ with FreeBSD

    4.anything. That direct quote is a complete fabrication – Dillon’s never said that.

    It just gets farther from reality the farther you get into the

    article. This isn’t just poorly checked facts on a random internet article – it’s lies, on purpose. Don’t bother with it.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>