Linux for Suits - Picking New Fights
Although it's easy to point to the exemplary successes of Linux-built giants such as Google and Amazon, it's just as easy to overlook the degree to which the practical value system behind Linux development has become the default approach to networked progress.
Yet even as Linux and the LAMP+ stack have become standard building materials, there's nothing to stop them from being used in service of a proprietary mentality that seeks to lock in customers, lock out competition and lock down markets. As Steven Hodson puts it (www.winextra.com/?p=354):
Many would like to believe that the best and strongest weapon against the old guard of technology is the Open Source movement, but what they don't see is that they have already been co-opted and have just become another way to make money. While the roots of the OSM (Open Source movement) may still technically be free to all, the old guard is quickly locking up parts of it with service contracts and corporate licensing.
It's still customary for VCs to ask their potential portfolio companies, “What's your lock-in?” This is an Industrial Age mentality that needs to be exposed as a value-subtracting anachronism in a world where creation and choice yield abundances that can be put to countless productive uses. You should want to build goods and provide services that customers choose freely. You should keep customers because they want to stay, not because you've trapped them in a silo.
Even Steve Jobs this year came out and said the record industry would be better off without DRM. That's because he's no less trapped than any of his customers.
The protagonist here is nothing less than the cause of freedom, which will never be old Gnus. (Pun intended.) The problem here—the enemy—is a mentality that's as old as the Industrial Age.
The battle for freedom, of course, is one we've been fighting all along. The difference now is that the logic of lockup is more and more exposed, and its flaws are more and more evident—though not yet widely obvious.
The fight, then, will shift from ideals to practical matters. How do you make money by building with free stuff and putting it to use, rather than just by selling it? How is software more useful and important as it becomes less and less of an industry? How do you get more work done, and become more valuable as a contributor because you're working with free and open goods?
These are still new questions, even though Linux Journal has been a living answer to all of them since 1994.
So now the question goes to the floor. What are the Good Fights you want to read about in Linux Journal? You tell us. Write to firstname.lastname@example.org.
Doc Searls is Senior Editor of Linux Journal. He is also a Visiting Scholar at the University of California at Santa Barbara and a Fellow with the Berkman Center for Internet and Society at Harvard University.
Doc Searls is Senior Editor of 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!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- 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