From the Editor, July 2005: Win-Lose Situations
We go to press at what we hope is the end of a nasty brouhaha over kernel development, with Linus Torvalds finally forced to abandon BitKeeper, his favorite source code management system, and develop an alternative. Samba guru Andrew Tridgell developed a free tool to pull data from BitKeeper repositories, BitKeeper's Larry McVoy responded by pulling the free-of-charge version that kernel developers had been using, and a lot of people's carpal tunnels took a beating in the resulting—well let's be nice and call it a discussion.
Much as we like to find the win-win situations where we can, people have different goals. Are you writing a really good operating system kernel, are you building a proprietary software business or do you want to keep up with what's going on without having to accept BitKeeper's non-compete clause? The Linux business is all grown up in a lot of ways, moving billions of dollars in hardware, software and services, but now that we are the IT marketplace, it's time to be more honest with ourselves about conflict.
Some of us are always going to sound like software freedom zealots, and some are always going to sound like greedy swindlers. The answer isn't to flame the other side with the “if you'd just compromise on my issue, it would be good for Linux” argument. Understand you're in conflict and sell your alternative as well as you can. Here's where Linux Journal comes down on a side that has to be in opposition to some of the other participants in the market—but we're not going to say it's for the good of “Linux”, or start flaming when people won't act against their own interests.
In the long run, we say it's worth a lot of late nights, hot coffee and risking getting flamed on a support list to get your organization's directory service away from a proprietary choice and onto one of the freedom-friendly, standardized alternatives. Although you might be able to move some applications to Linux sooner if you just plug Linux in to your existing proprietary directory, that is the road to lock-in. Letting readers get locked in is bad for us because we're here to help everyone do new, innovative projects on all kinds of systems, not just whatever is in the directory vendor's interest to support.
When Craig Swanson and Matt Lung proposed the now-famous “OpenLDAP Everywhere” in 2002, it was as a piece on making your whole business run on Linux. That's a big subject, so Craig and Matt decided to narrow the focus. Strangely, they still managed to cover the essentials for getting your whole company running right. A lot has changed since 2002, so Craig and Matt are back on page 40 with a new, updated version that covers new software versions and lessons learned.
It's not all controversy this month, though. The best tools don't force you into hard choices. Joshua Bentham has an intro to a cross-platform, easy-to-use way to develop database apps on page 54. Enjoy the issue.
Don Marti is editor in chief of Linux Journal.
- Android Browser Security--What You Haven't Been Told
- Epiq Solutions' Sidekiq M.2
- Readers' Choice Awards 2013
- Nativ Disc
- The Many Paths to a Solution
- Synopsys' Coverity
- Securing the Programmer
- RPi-Powered pi-topCEED Makes the Case as a Low-Cost Modular Learning Desktop
- Identity: Our Last Stand
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide