Nagios fork warning to Oracle

Nagios fork warning to Oracle

Summary: As Oracle prepares to take possession of open source projects like OpenOffice, Java and mySQL, the Nagios fork is a warning that open source code can't be suppressed.


A fork of the Nagios network monitoring tool called Icinga has officially launched, with the first stable version due October 28.

Matt Asay says this illustrates the health of the open source movement. 

Nagios is a 10 year-old project and those involved with the fork say they include members of its community advisory board and makers of Nagios add-ons.

But there is meaning here for more than Nagios. There is great meaning here for Oracle.

As Oracle prepares to take possession of open source projects like OpenOffice, Java and mySQL, the Nagios fork is a warning that open source code can't be suppressed.

Whatever Nagios' managers did to cause the fork, it can't be nearly as bad as the actions Oracle has been suspected of in its approach to open source competition.

Forks of these larger projects would doubtless move even more quickly, and gain more support from both developers and users, than Icinga, which is used by network managers and not the general user community.

The open source warning to Oracle is clear and was probably put best by Tina Turner, above. You better be good to me.

Topics: Networking, Open Source, Oracle

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • IMHO

    I suspect that several of the Sun F/OSS projects are more than ready to strike out on their own. OO.o, for instance, has certainly benefited from the resources Sun has put into the project but has also suffered from Sun's dominance.

    Like when Netscape set Mozilla free, losing a corporate sponsor can be very good for a project.
    Yagotta B. Kidding
  • Open source is aggressive?

    I like open source because it is open and free, not because it is aggressive!
    Oracle is no more than a commercial company. There is NO immorality if it cuts the open source projects. If other companies think that MySQL suits its business model, they should continue the work themselves.
    • But no one is "cutting" Open Source projects here.

      The projects are forking. You cut with a knife, fork with Open Source.
  • URL for the "why" of the fork
  • The bigger question: Would it matter to Oracle?

    It's pretty clear to everyone (and I would think Oracle is included in that "everyone") that MySQL is in no danger in Oracle's hands. Sun has technologies that would benefit Oracle FAR more than MySQL (Java - tightly coupled with many of Oracle's commercial products, just to name one), so I'm still of the opinion that MySQL probably isn't even on Oracle's near-term radar. The bigger question I would ask is whether Oracle would even care if it forked or not.

    1) They already support a more advanced, Open-Source database system than MySQL (Postgre) as well as the major transactional component of MySQL (innodb). Owning MySQL doesn't really make them any more or less in control, and it doesn't really affect either of these other projects.

    2) Oracle's flagship products have nothing to gain technologically from MySQL - MySQL has been and still is playing major catch-up with most commercial RDBMS. Oracle may gain a little bit of mind-share, but they already have plenty of that which they gained all by their onesies.

    3) MySQL, on the other hand, could gain many benefits from being in Oracle's fold, if Oracle decided to put effort into the project. My guess would be Oracle might see where Postgre and MySQL might benefit from each other and support some effort to merging the best technologies of the two. I'd be surprised to see any significant Oracle DB technology show up in MySQL other than cross-compatibility work (ie, make PL/SQL and Objects work in MySQL so that projects can have an easy upgrade path to Oracle DB).

    Whether or not MySQL forks is more up to the community around it. Either they see Oracle's involvement as a benefit or they don't. If Oracle decides to ignore the project, then there will be the same amount of benefit/liability as there was before Oracle bought Sun. If Oracle "tries to kill it" (which I'm pretty sure they're smart enough to know that they can't), then, again, the community will still be no worse off than they were before.

    Indeed, even if Oracle *has* any intentions with MySQL, they probably lean more toward the "good for the project" side of the spectrum rather than toward the "killing the project" side. A forked product would be giving up any gains to be had from the involvement of a major technological player like Oracle.
  • Preemptive fork would be wrong

    Any fork of these projects based only on Oracle's suspected future wrong-doings would be wrong.

    Here is one protocol -