The first item I should address is what I would think is a perceived "bad point" about a 24-hour system setup time. Although some may consider this compile time to be excessive, this is not 24 working hours. All together, I spent about three hours in front of the machine, and most of this was spent watching Portage do its thing.
The second thing I want to address about the time is my case is an extreme that, if you choose to use the Gentoo system, you don't have to go to. Only if you want to bootstrap your system and compile everything from the ground up are you required to go through these steps. You can, and many people choose to, install from the Stage 2 or Stage 3 tarballs, which have many packages precompiled using standard directives. In using the compiler directives that I chose for my processor, I have noticed a speed improvement by what I would estimate to be about 10% to 15%. My main reason for choosing the Stage 1 tarball was to become intimately familiar with building the Gentoo system from the ground up. Additionally, the Gentoo group does provide ISO images with software precompiled using compiler directives for specific branches of processor families (for example, Athlon/Duron, Pentium 4, Athlon-XP). These offer the optimization without the hassle of the wait of compiling.
A huge plus that has kept me with the Gentoo system is the ease with which I can add packages to, remove packages from and update packages installed on my system. Essentially, all of these are accomplished using the emerge command. For example, to install OpenOffice on my machine, I dropped into a shell and typed emerge openoffice. After a two-hour optimized compilation period, OpenOffice was available to me and my users (my wife). When a security patch was offered for OpenSSL, in order to update it and my entire system, I merely typed emerge -u world. All the packages I had installed on my system that had updates available then were updated.
Another huge plus that I have found has little to do with the Gentoo distribution itself but the support community and the Gentoo Web site. Gentoo's documentation is surprisingly commercial-grade, even more so than some documentation for the commercial distributions. The Gentoo group's reliance on XML and CSS for its Web site gives it a uniform look, feel and implementation. It's clean, robust and functionally usable.
As far as support is concerned, any question that I have asked has been answered within minutes of posting it to the mailing list. Generally speaking, the users I have encountered have been warm to newcomers, and they appear to be interested in cultivating a large base of users for this product. It's rare in the technical community to find seasoned users who are as adept at answering the questions of newcomers such as myself as they are at helping other seasoned users solve technical problems.
Last, but not least, an operating system with no application support is not a good thing. With Gentoo, there are no worries. The Gentoo community has produced more than 4,000 applications in the Portage/ebuild format (from completely free software such as Ximian's Evolution to proprietary software such as VMware), and the library keeps on growing. And if you can't find an ebuild for a particular product, you always can download the source and install it as you would on any of the other Linux distributions.
Gentoo Linux offers an option for the user who wants an easily and highly customizable system that also can be kept up to date with ease. If this is you, I highly recommend looking at this metadistribution.
Sean Bossinger manages the University Technology Services Support Center at Florida International University. In his copious free time, he enjoys playing in the park with his wife, Tracy, and two rambunctious sons, Donovan and Logan.
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- 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