I have been a subscriber to Crynwr Software's Free Software Business mailing list for years. It is an open discussion forum for people in the free-software business. Other well-known members include Bob Young, Brian Behlendorf and Tim O'Reilly.
A discussion is still currently going on, which inspired this post to our news site. The title is Licenses vs. public domain. You will see the typical GPL vs. BSD license issue being discussed, although Brian Behlendorf posted something I hadn't previously thought about. His point, using Apache as an example which is under the BSD license, is the fact that the license, while allowing a proprietary fork in the code, does not allow the use of the Apache name.
For something new to the market, this probably doesn't matter. But, once your product is established, the name becomes very important. Having a web server that works like Apache is much less important than having a web server you can call Apache in today's market.
A second interesting issue that was raised in this same discussion is how the licensing of Perl made it possible for Perl (and Python) support to be added to the Microsoft Visual suite. Before you panic, this is not MS-Perl; it is a development environment.
Rather than re-hash the discussion, check out the archive. You can read it and even join the FSB list by visiting www.crynwr.com/fsb/. If you are interested in open licensing issues, it is well worth reading.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
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.Register Now!
- Stunnel Security for Oracle
- SourceClear Open
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
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