Microsoft Hits a New Low — Below the Belt
We have a lot of fun here on LinuxJournal.com, bringing you the news and poking fun at companies like Microsoft — but it's always intended as journalism with a lighthearted twist. This time, though, we're not being silly, because the subject matter is too serious for laughing.
We all know that Microsoft has engaged in questionable practices trying to get OOXML approved by the ISO. It's not acceptable that they've tried every dirty trick in the book to rig the vote, but if the latest reports are true, they're even more desperate than we thought.
According to the New Zealand Open Source Society, Matthew Holloway, a prominent member of NZOSS active in the debate over OOXML was singled out and — in their words — slurred by a Microsoft employee in an email sent to one of the groups advising national standards bodies. Standards New Zealand — the National Standards Body for New Zealand — is taking the matter very seriously; Chief Operating Officer Grant Thomas has written an email refuting the statements made about Matthew, and objecting to the email's implication that they were the views of Standards New Zealand.
While we don't have the original email, NZOSS has published Grant Thomas' response — with permission — and among the lines quoted from the original are "[Matthew's goal] has always been to de-rail OOXML rather than making it a better specification” and “while his efforts have been appreciated by the Standards NZ people on the OOXML advisory group his attitude and disingenuous approach (especially with regard to reaching outside NZ to stir things up) have not gone down well.”
Groklaw — ever vigilant — has an extended analysis of the matter, an interesting read to be sure. NZOSS has expressed concerns that other organizations and national bodies may have received the same email, and asks that anyone aware of a body receiving such please point them to the SNZ/NZOSS refutation.
In all honesty, it's really sad that a multi-billion dollar enterprise with the resources to swallow near-equals whole has to resort to ad hominem attacks on individuals to win a standards vote. Most of their maneuvers don't faze us at all, some come as a minor shock, but this is really surprising.
Justin Ryan is a Contributing Editor for 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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- 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