Language Selection

English French German Italian Portuguese Spanish

PC-BSD May Be the Next Linux

Filed under
BSD

With all of the BSD variants available for download, it's easy to incorrectly assume all of them are pure, incompatible forks from each other. Actually, there are more shades of BSD out in the world than just separate forks. One in particular made the news a couple of weeks ago when it was commercially acquired.

The BSD in question is PC-BSD. The company that bought it (for the ubiquitous "undisclosed" terms) is iXsystems, a systems deployment and integrator firm out of San Jose that has pretty strong experience implementing *BSD, Unix and Linux systems for its customer base. So, why, pray tell, did the company up and buy PC-BSD?

The answer may lie in the type of operating system PC-BSD is. Unlike other, incompatible, BSD variants, PC-BSD is completely compatible with its antecedent FreeBSD. It is, for all intents and purposes, a FreeBSD distribution, in much the same way Red Hat or SUSE are Linux distributions. In fact, the similarity runs a bit deeper than that, since PC-BSD has long been designed with business users in mind. Its acquisition only solidifies that commonality.

Full Story.

Why iXsystems Bought PC-BSD

iXsystems is a leading provider of high-performance computing clusters, blade servers, rackmount servers, and storage solutions based on FreeBSD, NetBSD, OpenBSD, and Linux. iXsystems also recently announced its acquisition of the PC-BSD operating system.

I had the opportunity to interview Kris Moore, founder and lead developer of the PC-BSD project, and Matt Olander, CTO of iXsystems, about the acquisition.

Dru: From both the PC-BSD and iXsystems perspectives, what were the reasons for considering a collaboration and what benefits do you perceive from the acquisition?

Matt: From a server manufacturing perspective, we want to help our customers adopt the platform that is right for them. Of course, we ship quite a few systems with some flavor of Linux pre-installed, but it tends to be because the customer is looking for a commercially supported operating system. If iXsystems can assist increasing the adoption of FreeBSD, we think that's a good thing for us as well as our customers. A higher adoption rate of FreeBSD encourages vendors to provide documentation so that the appropriate drivers can be created and supported. It also attracts developers to the project so that FreeBSD continues to progress and be the modern, stable operating system platform that it is currently.

Full Interview.

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Fedora: Anaconda Improvements, Greenboot, Fedora Scientific Vagrant Boxes and Abhishek

  • Anaconda improvements in Fedora 28
    Fedora 28 was released last month, and the major update brought with it a raft of new features for the Fedora Installer (Anaconda). Like Fedora, Anaconda is a dynamic software project with new features and updates every release. Some changes are user visible, while others happen under the hood — making Anaconda more robust and prepared for future improvements.
  • Lorbus: Introducing: greenboot
    Not too long ago, I applied to Google Summer of Code for the student scholarship position together with a Fedora project ideated by Peter Robinson, who is the principal IoT architect at Red Hat, named Fedora IoT: Atomic Host Upgrade Daemon. As you may be guessing by now, I was very fortunate and the proposal was accepted! The coding phase started on the 14th of May and in this blog post I’ll try to give a little insight into my first month working on the project.
  • Pre-release Fedora Scientific Vagrant Boxes
    I am very excited to share that sometime back the Fedora project gave the go ahead on my idea of making Fedora Scientific available as Vagrant boxes starting with Fedora 29. This basically means (I think) that using Fedora Scientific in a virtual machine is even easier.
  • [Week 5] GSoC Status Report for Fedora App: Abhishek

Red Hat News

  • An Open Source Load Balancer for OpenShift
    A highly-available deployment of OpenShift needs at least two load balancers: One to load balance the control plane (the master API endpoints) and one for the data plane (the application routers). In most on-premise deployments, we use appliance-based load balancers (such as F5 or Netscaler).
  • Red Hat Beefs Up Platform as a Service Suite
    Red Hat has begun shipping Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service (iPaaS) offering, Fuse Online. With Fuse 7, the vendor says expanding its integration capabilities natively to Red Hat OpenShift Container Platform, an enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • Red Hat ‘Fuses’ Low Code Development and Data Integration
    Red Hat, a provider of open source solutions, has announced Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service offering, Fuse Online. With Fuse 7, Red Hat is expanding its integration capabilities natively to Red Hat OpenShift Container Platform, a comprehensive enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • The GPL cooperation commitment and Red Hat projects
    As of today, all new Red Hat-initiated open source projects that opt to use GPLv2 or LGPLv2.1 will be expected to supplement the license with the cure commitment language of GPLv3. The cure language will live in a file in the project source tree and will function as an additional permission extended to users from the start. This is the latest development in an ongoing initiative within the open source community to promote predictability and stability in enforcement of GPL-family licenses. The “automatic termination” provision in GPLv2 and LGPLv2.x is often interpreted as terminating the license upon noncompliance without a grace period or other opportunity to correct the error in compliance. When the Free Software Foundation released GPLv2 in 1991, it held nearly all GPL-licensed copyrights, in part a consequence of the copyright assignment policy then in place for GNU project contributions. Long after the Linux kernel and many other non-GNU projects began to adopt the GPL and LGPL, the FSF was still the only copyright holder regularly engaged in license enforcement. Under those conditions, the automatic termination feature of GPLv2 section 4 may have seemed an appropriate means of encouraging license compliance.
  • Monness Believes Red Hat (NYSE: RHT) Still Has Room to Grow
  • Comparing Red Hat (RHT) & Autoweb (AUTO)
  • As Red Hat (RHT) Share Value Rose, Calamos Advisors Upped Its Position by $300,831; Chilton Capital Management Increases Stake in Equinix (EQIX)
  • Blair William & Co. IL Buys 23,279 Shares of Red Hat Inc (RHT)

Total War: WARHAMMER

Red Hat changes its open-source licensing rules

From outside programming circles, software licensing may not seem important. In open-source, though, licensing is all important. So, when leading Linux company Red Hat announces that -- from here on out -- all new Red Hat-initiated open-source projects that use the GNU General Public License(GPLv2) or GNU Lesser General Public License (LGPL)v2.1 licenses will be expected to supplement the license with GPL version 3 (GPLv3)'s cure commitment language, it's a big deal. Read more