Letters to the Editor
Most people prefer tar because it is a little easier to learn how to use, for most people. When cpio needs to create a directory that isn't explicitly included in the archive, it does it with 700 permissions, whereas tar uses 755. 755 is arguably more useful in most circumstances. Some people simply prefer cpio's interface (see Eric's article on page 44). find and cpio are often thought of together; in fact, SVR4 find has a ->cpio option that can be used as an action to add files to a cpio archive. I understand that some versions of tar have not properly preserved hard links, but I've just tested to make sure that GNU tar does preserve hard links correctly.
In general, most of the advantages of each archiver have been added to the other over time, so it's a matter of taste.
Eric Goebelbecker replied, in response to the second point:
“I would move the software over and soft link it myself for one reason: I did it, and know what I did. Come upgrade time, that knowledge becomes real valuable...”
I would like to commend the folks at S.u.S.E. in Germany for being generous enough to give something back to those from whom they have gained.
It is their practice to offer a free copy of their distribution to the authors of free software that they include. As the maintainer of GNU awk, I recently received my second distribution from them, and I felt that the Linux community ought to be aware of this company's fine practice.
Arnold Robbins firstname.lastname@example.org
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!
- Stunnel Security for Oracle
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
- Parsing an RSS News Feed with a Bash Script
- 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