Someone is *Wrong* On The Internet
This is a blog post about blog post comments. Not just comments on Linux Journal, but blog post comments in general, especially about blogs that support 'Anonymouse' contributions.
I've been a Linux geek for a long time. We won't discuss how long, but Get Off Of My Lawn!
When I worked at Los Alamos National Laboratory (for a long time, but again, we won't go into that) we had an internal mailing list named NMUG, for Network Manager's User Group. Fully two thirds of the list members were Linux geeks, gurus, HPC whizes, kernel developers, admins, etc. The others came from, you know, the Windows world. We had some wonderful flame wars! Just yesterday I received a message via Facebook from one of my ex-LANL colleagues who still works there saying, and I quote:
Today on NMUG it was lamented that it's impossible to have a proper flame war without you.
I've also run high-volume, high-visibility, highly contentious blogs in the past. See LANL, The Real Story as an example.
All of this is a long-winded way of saying that I am quite familiar with the spittle-laden delivery style that some of our more passionate Linux Journal comment providers use when trying to make their point on whatever issue has them all worked up. The authority on this style of internet information exchange, IMO, is Xkcd.
Now please don't misunderstand, I am not attempting to discourage this style of flaming delivery -- quite the opposite. It is often most entertaining. In fact, let me share with you one of my favorite "throw some gasoline on the fire" flaming techniques. Reply to a flame by making a spelling or grammar correction in the offending comment. Works like a charm!
What prompted this thread, you might ask? Well, I was reading Michael Read's recent KDE4: It hurt, but did it work? article, and was tickled by the fervor of the anti/pro camps surrounding the great KDE vs. Gnome debate. Did the anti-KDE flamers win over any converts to whatever was being claimed as a superior desktop environment? I doubt it. Did it make for entertaining reading? I think so.
So, how about if we start a new discussion on the button placement in Ubuntu Lucid 10.04? No? How about the new default color scheme then?
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!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- Interview with Patrick Volkerding
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
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