One standard dist. with choices?
The comments on the single distro story got me thinking about what I want/need/use. I have been using Linux since before Bill Gates heard of it and my uses, needs and interests have changed over time.
Ten or more years ago I was in the "I need to get Linux to do X" mode. That included a web server, an office network and a bunch of desktops—some for geeks but also some for the rest of the office including the shipping clerk and the receptionist. The right answer varied but, in virtually every case, it was:
- Start with a stable distribution
- Customize it do work in each environment
While I am capable of patching the kernel if need be, I don't want to. Linux is a tool. The more systems I can set up with close to zero work, the more time I have left to do the geeky side of Linux where it is needed. The map of Linux systems in my life looks like this:
- My personal desktop that I also use for program development. It is running Kubuntu.
- An IBM laptop that I mostly use to "try things". It is running Kubuntu.
- An Asus laptop that is my "travel system". It is running Kubuntu.
- Two other desktops in my office. They are running Kubuntu.
- Desktop in the livingroom for "everyone". It is running Kubuntu and has an assortment of logins in English and Spanish.
- The future biofilter system for the Geek Ranch. It will probably be running Devil Linux.
- A remote controlled FM radio station system. I set it up a few years ago as a test and don't even remember what distribution I used. But, it will be running from flash memory and will use Devil or some other "mini-Linux".
- Two different shared Linux hosts where I have some web sites such as the one for the Geek Ranch. I actually don't know what they are running and am glad to say that I don't have to know.
Does this mean I have become a non-geek? No, not at all. But, I don't enjoy just setting up desktops. As I have proved here, a 10 year old with no computer experience, can quickly become a happy Kubuntu user. That means I have more time to work on strange projects such as embedded systems. Thus, Kubuntu is my "one standard". That doesn't mean I think Kubuntu is the one distribution that is right for everyone—it is just the "it works for desktops" choice for me.
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!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Interview with Patrick Volkerding
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Tech Tip: Really Simple HTTP Server with Python
- 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