Nokia is Preaching, But not Really to the Choir
Nobody likes to be told they need to learn how things work in their own back yard, but when the lesson is about being taken to the cleaners, it's doubly offensive. Such was the message from Nokia on Tuesday, as its Open Source head took the OS community to task for not letting corporate greed run roughshod over the principles upon which Open Source stands.
"We want to educate open-source developers. There are certain business rules [developers] need to obey, such as DRM, IPR, SIM locks and subsidised business models." Thus came the proclamation from Berlin on Tuesday, at the Handsets World conference and out of the mouth of Ari Jaaksi, VP of software and Open Source chief for Nokia. He went on to acknowledge that such things "go against the open-source philosophy," but stuck to the corporate line that they're necessary evils that cell companies won't shed without a fight. Jaaksi was at least able to acknowledge that the industry has quite a bit to learn about playing nice with the OS community, having been burned by an inadvisable fork from the community developing Maemo, which runs the company's N800 "Internet Tablet."
Apparently the burn was not enough to drive them to learn anything about Open Source development, however. Jaaksi's speech went on to call for a "much needed" dialogue, followed immediately by this quote, quite possibly the most concise expression of corporate disregard for the principles of Open Source we've ever heard: "As an industry, we plan to use open-source technologies, but we are not yet ready to play by the rules." Our best advice to Nokia is to pick up a copy of the GPL and read it very carefully, because the times have changed, and these days, Open Source plays hardball, and wins.
Justin Ryan is a Contributing Editor for Linux Journal.
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!
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Interview with Patrick Volkerding
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
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