The Generation Gap
The Internet has gone from being tiny to small to huge to gigantic. The use of open-source software has gone from being tiny to small to huge. The parallels between open source and the Internet are particularly interesting, because the cultures overlap—the infrastructure of the Internet was developed by and is maintained by hackers.
The Internet and its culture can be viewed as having passed through four generations:
The U.S. Defense Department connects the ARPA-net with other defense networks to support military research. This proves to be a great way for researchers to communicate and share information. Demand for networking grows, but access is limited to a small community of computer science researchers, government employees and government contractors. A culture based on sharing is established.
The National Science Foundation commissions the NSF-NET to connect colleges with five supercomputer centers. The NSF pays for campus connections if access will be generally available to students. Anyone at a four-year college can get on the network. Everything still revolves around sharing; commercial use is forbidden by the people providing the funding.
Demand for networking increases, and commercial Internet Service Providers appear. Commercial use of the Internet is still frowned upon (and sometimes flamed upon), but for people and businesses paying for their own access, there is no one to forbid it. The emphasis shifts from sharing to using—surfing, chatting, e-mailing, browsing, finding cool stuff and being entertained. Commercial use increases. The idea of a business having a web site goes from being flaky to being obvious. The original culture, with its strict mores enforcing an ethic of sharing, is apparently losing its dominance.
Millions and millions of people are on the Internet. You can do just about anything you want. Strict mores have given way to true freedom. It's changing the world. More people are sharing on the Internet than ever before. It's the hacker spirit on a gigantic scale.
Linux began as an operating system used primarily by programmers. Now it is used by all kinds of people, and the proportion of Linux users who are programmers is steadily decreasing. Most of these non-programmers know very little about the traditions of the hacker culture. Many of them use Linux simply to make money, and it's just about the best thing that could have happened to the Open Source movement.
Open-source software isn't going to replace closed-source software any time soon. People write closed-source applications because they believe they can make money renting them, and they will continue to believe this. Companies write software for their own use, and want to guard their trade secrets.
Closed-source development is a wonderful market for open-source components. The more companies use open-source components, the more they will contribute to open-source development.
It's great that programmers can create something like Linux in their spare time, but they also spend a lot of time at their paying jobs. Component development may be where the Open Source movement invades company time.
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|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader 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