Endless September 2.0
Back in January of 1994, Dave Fischer coined the idea of the "September that never ended." Basically, it referred to the influx of new Usenet users that came to college every September, and had to acclimate to how one conducts themselves on the 'net. The 1993-94 school year was the first year that Internet access really caught on globally. It was also my freshman year at Michigan Tech University, so I was a founding member of the Long September.
For over a decade, the geeks of the Internet have happily been communicating in a way that was never before possible. Dial in BBS's transitioned to Telnet based "talkers", the passive Usenet complimented the realtime IRC, and the one-way information superhighway (uh, the web) was offset by the two-way email. The real, large scale group communication was kept to things like IRC and Usenet. As geeks of the 90s, we owned barrier free communication. The Internet bridged the gaps between ethnic and geographic differences. Men and women were on equal footings. Intelligent teens could be respected by their knowledge and insight rather than the length of time since their birth. It was awesome.
Now, it's September all over again. I don't mean that derogatorily, because after all I'm a poster child for Endless September Part One. Now, however, the online communication has a different look. Instead of IRC and Usenet, it's Facebook and Twitter. Instead of sharing ASCII art, we're sharing video. Instead of communicating for communication's sake, we're communicating for collaboration on real life things.
15 years on, the Internet is still all about information and communication. We recently started communicating in a whole new way. It's new. It's exciting. It's still far from perfect. I have no idea what it's going to be like in another 15 years, but I'm sure glad I to be a part of the process.
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
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- 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