Open Source Debate
Last month we published an article by Eric Raymond on Netscape's decision to release the source code for their web browser. A lot has happened since Eric's article, and that lot is what I wish to talk about this month.
As part of Eric's article, he introduced a new phrase for talking about software such as Netscape Navigator as well as other software where the source code is freely available. The phrase is Open Source.
The idea for a new name and the choice of that name has been an ongoing debate and, at this writing, continues. The confusion is associated with the term Free Software. Free has many different meanings. In particular, free can refer to price or to freedom. While freedom is the issue that we are attempting to address, there has continued to be confusion.
Rather than attempting to define what we mean by free, the introduction of a new term seemed in order. With the new term comes the opportunity to define it.
Bruce Perens (of Software in the Public Interest) and I decided that a web site with a repository of information on Open Source was the best approach. That web site is at http://www.opensource.org/ and includes the definition of Open Source and extensive resources to get others on the Open Source bandwagon.
By the time you read this magazine, the source code for Netscape Communicator 5.0 Standard Edition should be available. Netscape announced they would release this code on March 31, 1998.
Netscape released a preliminary version of their license agreement (Netscape Public License) for public comment. That comment period ran through March 11.
Netscape put the proposed license on the Web along with a FAQ and annotations. The ongoing saga of this license is available on the Web at http://www.mozilla.org/. I'm not a lawyer but what I see of the license makes sense. It isn't a GPL and it isn't a BSD license, but that is because neither makes sense for Netscape.
One thing in the license I found interesting is they have elected to keep the name Netscape for branded products and allow the use of Mozilla for derived works. This makes sense to me. When I was talking to Eric Raymond before he met with Netscape, I brought up the concern that a bad port or modification of a Netscape product could reflect poorly on all Netscape products. The decision to use a different name offers the needed freedom, yet allows the consumer to differentiate between a Netscape product and a derived product.
Netscape is not the only commercial vendor in the Open Source camp; there are others.
One hardware vendor who got into this camp before it even existed is Cyclades. Cyclades was the first communications board manufacturer to embrace Linux. They have always made the source code available for their drivers and their sales growth in the Linux and BSD markets has supported their decision to release source code for their drivers.
Another long-term vendor in this community is Cygnus Solutions. They offer commercial support for open source software and continue to grow and evolve with the community.
Of course, all the Linux vendors are there by default as well as the Apache web server and the Perl programming language. Vendors who elect to get involved with these products become part of the Open source vendor base.
I have already mentioned the Open Source and Mozilla web sites. As always, we put late-breaking Linux news up on the Linux Resources web site, http://www.linuxresources.com/.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
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