Linux Distribution Chart
Reasons I use Arch:
Up to date packages.
Simple from top to bottom.
Teaches me as I go.
“I use CentOS simply because of its reliability. It's also flexible, and very light—with it being light leaves more resources to actually do what you want. Hence, that's why I use it for all my servers.”
“I've had nothing but utterly awful experiences over ten years with RHEL, despite its high cost. I can see the point of CentOS if you need RH without the cost, but it's just revolting to work with and the documentation is terrible too, so I'd never run either by choice.”
“Debian combines great sysadmin friendliness with a terrible release policy; Ubuntu takes its great design and adds sanity.”
“I now use Fedora because each successive version of Ubuntu caused different problems with my 3.5-year-old laptop (camera, sound, wireless, graphics). Each version would fix some problems and cause others. Fedora has been stable, fast and less trouble to set up than Ubuntu.”
“I like Gentoo for its extremely useful control over the system and love the flexibility. It appeals to the tweaker in me! All my systems, including laptops, run Gentoo! That's five systems in total! I have tried other distros, but nothing comes close to Gentoo. I loved portage so much, at some point in time, I ported it to Solaris. Now, with prefix support, anybody can use portage on Solaris, BSD or Mac OS. The Gentoo community is exemplary!”
“I've been using Windows for a long time, since Windows 95, and I've been an IT professional for about 9 years. Through it all, I've always been turned off to Linux. I didn't have time to try anything new. I was just trying to keep up with the changes in Windows. Just a month ago, a new coworker gave me a Linux Mint CD. I took it home and ran the live CD on one of my IBM laptops. I've been hooked ever since. I even changed my wife's laptop from XP to Mint. The bottom line is, Linux just works....I'm sold.”
“I use openSUSE because it always has just worked for me. It has a large selection of software available in repos and through the build service. Information is easily found on-line in the wiki and forums.”
“I love live CDs, but liked PCLOS Big Daddy so much, I felt the need to install it with a dual-boot of Windows at the time. By the time PCLOS 2007 came out, I'd gotten a newer computer and erased the Windows partition to put the exclusive Linux desktop on it. I haven't looked back since. I no longer dual-booted. The other people I know who have PCLinuxOS tend not to be techie types that you see at work, but more like teenagers and housewives and early-adopter-gadgety folk around here—not the Computer Crowd, as much as the people with lots of cool toys. They don't dual-boot either. When VirtualBox came to Synaptic repos years ago, I put my Windows XP install disk in there to test it out and made a video of Linux running Windows better than Windows. I ended up taking the virtual Windows off though, because I never used it. PCLinuxOS rules.”
Justin Ryan is a Contributing Editor for Linux Journal.
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
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Interview with Patrick Volkerding
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
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