Why Broadcom's Release May be More Significant than Just Code
On September 9 the news of Broadcom's release of the code for some of its wireless Ethernet chip sets sent shockwaves throughout the Linux community. Broadcom owners, as well as distribution developers have a reason to celebrate.
In the past, Broadcom owners had to resort to NDISwrapper or rely upon the limited reversed engineered drivers. Neither was optimal. The release of the code by Broadcom should eventually mean a much better Wi-Fi experience for owners of systems with Broadcom chip sets. But for those that like to read between the lines there may also be a deeper significance to this move.
There are two trains of thought as to the "deeper" significance in this surprising move. Some say Linux installs / computers still make up only 1% of total computers in use. Others believe it's much higher. One well-respected writer believes it is probably about 10% while another estimates it is closer to 14%. So some see the Broadcom move as proof that the higher figures are the accurate figures. The thinking being that Broadcom wouldn't worry about a mere 1% share of the market but would be concerned about a double digit market share.
The second theory, while similar in nature, is that the move is due to the growing number of large industrial and commercial Wi-Fi hot-spot networks. Many of these are relying on Linux due to its security and reliability. Again the thinking is that this is a large enough market that Broadcom does not want to lose it to a competitor that has better native Linux support, such as Intel.
Whether it's due to pressure from users, loss of sales, or just a change in attitude, it's good news for Linux and that's all that matters. Most Linux users probably don't care why, they're just happy it happened - even if it does still leave many with older chips that still may need to rely upon b43 or NDISwrapper.
Susan Linton is a Linux writer and the owner of tuxmachines.org.
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