Book Review: Tuning and Customizing a Linux System
Even though its title gives the impression, the goal of this four-hundred-page book is not to explain how to build a GNU/Linux distribution from scratch. For example, there are no step-by-step explanations of how to tune a kernel or the X Window system, nor is any instruction given for how to build from scratch a customized KDE or GNOME desktop. The issues discussed at length, however, are clearly stated on the cover: "give insight into what happens behind GNU/Linux scenes", "explain the architecture of Red Hat, Slackware and Debian", "give guidelines and best practices for installing several types of packages".
All the source code written for the book is available on-line, in the Downloads section of the Apress Web site. The book says that "You will need to answer questions pertaining to this book in order to successfully download the code", but that was not the case for me.
The material is divided in four sections, and the first one simply provides a short presentation of the GNU/Linux movement, free software and open-source concepts. The second section illustrates how a GNU/Linux distribution is created and thoroughly analyzes the three distributions mentioned above.
The first chapter of the second section, which can be read on-line on the Apress site, introduces the necessary concepts and definitions. Following this, and for each chosen distribution, the author presents the differences between its kernel and the official one and discusses the package management system used. The latter element, being one of the things that make the real difference between two distribution, is covered much more exhaustively than the former.
The programs available for installing and upgrading packages are introduced through examples, together with their main command-line options and the related front ends, where available. A nice table is included that lists side by side, for each package management operation, the complete rpm (Red Hat) or dpkg (Debian) syntax.
The filesystem layout is explained directory by directory, making clear what is the content and purpose of each. All deviations from the Filesystem Hierarchy standard are presented.
The startup scripts also receive extended coverage, and summaries are given of the differences between the SYSV and BSD startup systems. The reader learns how they interact with each other and how they must be written and installed to be integrated with the rest of the system, depending on the distribution.
The other cornerstones of all GNU/Linux system are presented as well: system libraries (and the importance of their versions), the role of X and, very briefly, the Linux Standard Base. The chapters dedicated to each distribution also lists their most popular derivatives.
This second section ends with a useful check list titled "Learning a New Linux Distribution in Ten Easy Steps", and it sums up in one page everything a person should look at when switching from one distribution to another. The only tip missing is how easy are they to upgrade.
The third section of the book is titled "Installing Software", and it begins with an introductory chapter that lists the necessary steps, from choosing between source or binary installs to configuring the user environment. The author then chooses six packages, and for each one devotes am entire chapter to explaining how to install and configure it. This section is really interesting because each tool belongs to a different category, as far as building and installation are concerned. The author makes clear which actions are necessary only for the chosen application and which ones are best practices for all packages of the same kind.
The fourth and final section of the book explains how to build three real world systems: a multimedia capable desktop, a corporate software development workstation and a network firewall. The case studies choices are good here, because together they cover almost every possible kind of problem. The multimedia desktop chapter is probably the least satisfying: it does list all the components and issues that the reader would encounter in building such a system, but it gives little more information than that.
The hardware support part of this chapter, however, stands independent and is worth reading. It synthesizes clearly, without going in technical detail, the Linux way to support ZIP drives, USB devices and, through SCSI emulation, IDE CD-ROM burners.
The corporate workstation case is more useful, as it covers criteria for local versus network software installation, (again, briefly) VMware and what needs to be done in order to develop J2EE applications.
The network firewall chapter is the best of this section: it includes several diagrams and listings, all carefully explained, and discusses all the steps and alternatives to run a Linux-based firewall on general purpose hardware. Intrusion detection systems, booting from read-only media and peculiarities of dial-up firewalls are covered, as are tips on firewalling wireless LANs and building VPNs.
Articles about Digital Rights and more at http://stop.zona-m.net CV, talks and bio at http://mfioretti.com
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- 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