Finally! SecDef signs Clarifying Guidance Regarding Open Source Software
It is official! As of the 16th of October 2009, the United States Department of Defense recognizes Open Source software as Commodity, Off the Shelf (COTS) software, eligible for purchase, read implementation, under the purchasing rules of the Department.
Why is this a big deal? Because, until this point, using Open Source software in any form within the DOD and associated programs required a great deal of scrutiny and in many cases, it meant that it could not be used. Now, before you jump up and tell me about this or that program, yes, Open Source software is used in a number of areas – many in custom applications, but the use is program by program, at the discretion of the program office. Just because on program office says yes to Open Office, does not mean that another program office can use Open Office automatically, even if the mission statement is essentially the same. I am greatly simplifying the issue – the intricacies of the Federal Acquisition Register are frankly byzantine even for those that understand it. This now allows program and departmental level organizations to be able to compete, in a true, fair and open competition the best solution for the mission, and that is a big deal, because up until now, that has not been the case.
As a side note, this memo was discussed in a meeting of Open Source folks I attended in DC more than two years ago. Then it was stuck in the Secretary of the Navy’s office, having been drafted by the staff of the Office of the Naval CIO. The big question everyone was asking at the time was not when would SecNav sign it, but when would SecDef sign it.
This has been a long time coming.
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!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- SourceClear Open
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