Focus on Software
The other day, I was working on a client's system and noticed the /usr/src directory filled with every 2.2.x kernel ever released. When I asked the administrator about it, he responded he always keeps up with each new stable release just in case there are any security-related problems with the old one. (Okay, I'll buy that.) When I asked him why he didn't just download the patches and apply them, he said he didn't know what to do with them. I'm finding system administrators aren't the only ones who don't understand the patch process, as I've sent instructions to a couple of maintainers of very large packages who didn't supply patches.
Those of you with small disks or slow Internet connections can appreciate the problem of downloading 16MB files each time there's a 2KB change. While I'm sure many of you don't notice the impact on the Internet, it's there. Imagine 10% of the folks running Linux (over one million users, if you believe the latest figure of 10 million plus users) wanting to upgrade at the same time. The 2.2.14.tar.bz2 is over 12MB. A patch file from 2.2.13 to 2.2.14 is 1.4MB. That's nearly an order of magnitude difference, and that is significant in both disk space and bandwidth. This amount of traffic would swamp the kernel.org servers as well as several major routers. If you start with new pristine sources each time you compile, you have to go through and recreate your kernel configuration (make [menu|x]config). If you patch up, that rather lengthy step is not needed. Using patch files saves everyone time, so save some bandwidth and patch the code.
mcdl provides a fast, easy way to catalog your CD collection automatically, using a MySQL database. The lookup is performed once over the Internet to CDDB sites. A GUI interface is planned for access/lookups/manual input of data. This is just the back end, but those of you who can use an SQL server (or an SQL monitor like xmysql) should find this useful. It requires the MySQL server, Perl, Net::CDDB module, discid, DBI and MySQL modules.
The disc-cover utility will create a print file to print a CD cover for a jewel case. You can include an image file for use on the front cover. It uses a connection to a CDDB site to get the information for the song titles, but a manual mode is available. It can also print extended information, but you need to control the quantity of extended information manually or the layout will be destroyed. It requires the MySQL server, Perl and the FreeDB module.
Do you have any systems sitting around in which you're not sure what they have? Maybe you want to compile in support for mtrr, but only on systems that support it. This little utility will tell you all that and more. If you have more than a few systems around from different manufacturers or different models from one manufacturer, this utility will probably come in handy. It requires glibc.
fdupes is a program to find and remove duplicate files in the directory provided on the command line (required). You must have write access to the specified directory. It requires glibc.
This Perl script can be run from cron or the command line, and will provide the current price of a stock or alert you when the stock goes above or below thresholds passed to the program. You'll need to know the stock's ticker symbol, since no search facility comes with the script. It requires Perl, the Getopt::Long, LWP::Simple and Mail::Sendmail modules and recommends cron.
This utility reads the lastlog and displays numbers of logins for all users. This is modifiable in several ways. You can include FTP users with shell account users, if you wish. A good informational tool. It requires Perl.
This is a very polished, professional order and estimation program for a printing company. Customer, Product, Paper, Shipping, Order and Job Manager screens access a MySQL database. It requires a web server with PHP support, MySQL and a web browser.
Want to host a few rounds of Quake? Or another networked game you'd like to invite friends to play? Well phpLanParty will let you announce these games in advance, and players can sign up for them. Makes hosting network games easy. It requires a web server with PHP support, MySQL and a web browser.
GNU Pilot LogBook Pro: ftp://ftp.stampede.org/skibum/
This pilot logbook is designed after the Professional Pilot Logbook with which most pilots will be familiar. What you don't need to do is worry about the totals. This is well-laid-out and has a “Remarks and Endorsements” box, allowing you to enter as much data as you want—unlike the actual book, which is very limiting. Medical information isn't implemented yet, but should be added soon. It requires libgtk, libgdk, libgmodule, libglib, libdl, libXext, libX11, libm, glibc, pilot's license and airplane (last two optional).
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- 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