Russian Linux: The Push Continues
We've talked about the concept of national Linux distributions before, and the Russians are a nation that has engaged in previous attempts to standardize on Linux. Recently, Vladimir Putin, the Russian Prime Minister, made an announcement of a renewed effort towards open source adoption on a massive, despite the previous failures.
Armchair pundits have had to make do with translated versions of the report and of the announcement, but what seems clear is that under the new plan Russian institutions will undergo a transition to open source software between 2011 and 2015. For example, the translated document specifies that in the fourth quarter of 2011, federal institutions will engage in:
Formation of the base package of free software solutions for typical problems of the federal executive bodies with the needs of the federal bodies of executive power in the types of software.
Followed by, in the second quarter of 2012:
Creating and maintaining a single repository of free software used in the federal bodies of executive power.
The whole 25 point plan runs along these lines, and it's detailed and well thought out. In fact, this focused plan of action reveals two truths about the Russian governmental attitude towards open source software:
Firstly, despite failures in the past, the powers in charge are determined to go through with adopting Linux and open source. This shows just how much value they attach to FOSS adoption.
Secondly, the documentation shows that Russian policy makers have learned, the hard way, that an uncoordinated and vague initiative is unlikely to succeed. As I mentioned in my earlier article, any initiative to move over to Linux is typically doomed if it is not part of a coordinated strategy. For example, I would argue that a plan to move all schools over to Open Office as the de facto office suite would have more chance of success than a plan to move one part of the school system entirely over to Linux and open source.
The dissemination of the announcement on the forums has been mixed. The competence of governments to efficiently organize large projects of this nature is a theme that always rears its head in these discussions.
The success of open source software anywhere benefits open source software in general, but some of the commenters suggested that the Russian government might not want to share improvements that they make to source code. I think that this is unlikely because it would be technically difficult to make modifications to the source code without sharing those changes, as anyone who has been involved with the maintenance of backports will attest.
The commentary also reveals a bias on the part of English speaking nations against the trustworthiness of a former cold war foe. These comments themselves fall into two categories, suggesting both that the Russian state may add security back-doors for its own nefarious purposes and that the plan might itself be motivated by a fear that American companies are secretly complicit with US government schemes of the same type.
Certainly, events such as the recent Stuxnet worm saga, that allegedly harmed the Iranian nuclear program, are a point in favor of Linux, and John Le Carrier would be intrigued by the level of imagination on display. However, I suspect that the Russians want to move over to FOSS for the same, slightly mundane, reasons as most of us: reduced costs, freedom from the whims of commercial companies along with greater flexibility and choice of solutions.
UK based freelance writer Michael Reed writes about technology, retro computing, geek culture and gender politics.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- 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