The case for National Linux Distributions
There's a lot of news flying around at the moment about the latest Russian attempt to create a national, Linux-based operating system. Let's take a look at some of the issues that surround the creation of national Linux distributions.
The first point to make is that this isn’t the first Russian attempt to adopt open source software. In 2007, the Armada group won the government tender to supply Russian schools with a Linux based operating system, making use of ALT Linux, a Russian fork of Mandrake Linux. Red Flag (China), Pardus (Turkey) and Bayahnian (Philippines ) were all created to meet the requirements of state institutions.
A national standard Linux distribution solves two of the biggest problems that face Linux adoption in education, business and government institutions:
First, Linux suffers from the problem of offering simply too much choice in terms of desktop environments and applications. If every school in the UK (for example) switched over to Linux and open source tomorrow, they could, conceivably, all be using considerably different set ups. A national standard distribution offers the advantage of a standard platform that workers and students can be trained to use and maintain.
Second, and this is a point that I think that a lot of people miss, most efforts to introduce Linux aren’t based around a strategic, simultaneous push. For example, a school will be reluctant to switch to a system that isn’t going to be in use in the workplace. For the same reasons, a workplace is unlikely to use a system that education doesn’t use.
If you were a parent who didn’t know much about computers, how would you feel if you discovered that your kids were being trained on a computer system that wasn’t in use outside of education, or one that was being used in schools but not in higher education? If you were a business, wouldn’t the fact that a given system is being gradually introduced into schools and other government institutions make it seem more attractive?
Even if establishing a national Linux distribution amounted to merely nominating Ubuntu or Fedora as the standard open source desktop for a country, it would be a step in the right direction. What’s being offered to businesses, education and government offices at moment is a proposition that is confusing and uncoordinated.
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
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Rogue Wave Software's Zend Server
- 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