Should Linux Standardize on a Single Distro?
When I demonstrate software for Linux Journal, I tend to use Ubuntu as my operating system. The reason is simply because Ubuntu is extremely popular, but it begs the question, should the Linux community standardize on a single distribution? Let's look at some of the pros and cons:
Advantages of a Single Linux Distro
- Linux support would be simplified, as the quesion of "what distro" wouldn't be relevant.
- Software vendors could release a single package that would install on all Linux desktops.
- The apt/rpm/yum/up2date/synaptic wars would end.
- Linux certification would be easier to define.
- Tux would be everyone's logo. :)
I'm sure I could come up with many other advantages that a "One Distro to Rule Them All" idea would provide. The problem is that the disadvantages are so profound, I think it negates any validity to the first list. Just a few:
Disadvantages to a Standard Linux Distribution
- A select few individuals at the top would control the present and future direction of Linux.
- There would be no internal competition in the Linux community. How sad would it be if we only had Windows and OSX to compare ourselves to?
- We lose the ability to choose, which is a fundamental part of everything Linux stands for.
- We become a monolithic, bloated, close minded, inbred, operating system with no hope for innovation, and no motivation to think different.
Ok, I admit, the last point is starting to get preachy. It's important to realize, however, that our diversity is where we draw our strength. It's the community that empowers us. It's the freedom to choose that allows us find the solution that best fits our needs, instead of taking whatever vendor solution is provided.
So yes, I tend to use Ubuntu. For my purpose, it makes the most sense. Thankfully, you have the right to choose whatever you like. And that's the way it should be. Thanks Linux.
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!
- Stunnel Security for Oracle
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- SourceClear Open
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
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