Letters to the Editor
I read your article in Linux Journal #32 about using PGP and came across the comment that building PGP from source for Linux was, well, difficult.
I have included a patch which will allow you to build PGP 2.62 on a Linux 2.0 box. (I'm running gcc 2.7.2, and a 2.0.25 kernel, so your mileage may vary with other setups).
Obtain the US distribution of PGP 2.6.2 from http://web.mit.edu/network/pgp.html (this may work for the international version, but I haven't tried it). Untar everything. Following the instructions in setup.doc, do the following:
cd rsaref/install/unixstrip pgp
Then do the tests setup.doc suggests.
There's definitely a cleaner way to do things, but I stopped playing with it once it worked. Sean C. Malloye-Net, Inc., firstname.lastname@example.org
See Listing 1 for the code Sean included with his letter.
It was good to see Michael Johnson's introductory PGP article in the December issue (#32). PGP can indeed be a bit of a challenge to set up, as he notes. This is particularly true for people with ELF systems. I put together a tips page for my local Linux user's group when we had a meeting devoted to installing PGP and integrating it with other applications. It's at http://www.rust.net/~strix/pgphand1.htm.
You really don't need to be a cloak and dagger type to appreciate PGP. In a more mundane setting, I like the ability to keep things private (like course gradebooks) and discourage e-mail forgery (“emergency, exam cancelled...”).Regards, email@example.com
In the December (#32) issue of Linux Journal, a reader asks whether it would be possible to see more FreeBSD-related articles. Your response mentioned an informal survey, with which I must say I'm unfamiliar, citing a lack of interest in the FreeBSD community.
I'm not sure how you were given such an impression, but I can certainly say that such a verdict is rather inconsistent with my own experience—we're always happy to see articles (or, indeed, entire magazine issues) devoted to our operating system and currently invest considerable energies in promoting it through magazine articles, public presentations and trade show appearances. I would be more than pleased to see the Linux Journal take a greater interest in FreeBSD and, until reading your response, was not even aware that such a possibility really existed.
Though some of the more overzealous users in both camps might perceive FreeBSD and Linux as operating systems in strong competition, this viewpoint is both short-sighted and foolish. The real dividing line here is free software vs. commercial software and open systems with complete source code vs. “open systems” which are open only in some marketing department's imagination.
Linux and FreeBSD have far more in common than the zealots would care to admit, and far more important than lineage is the fact that both provide users with something none of the commercial operating systems can match—a sense of actual control over the OS environment and the ability to learn from or change any aspect of it as they see fit, no longer tightly constrained by whatever arbitrary restrictions the manufacturer chooses to impose on them.
I hope that LJ does someday extend its reach beyond the implied focus of its title, making it clear the real fight lies not between FreeBSD and Linux but in combating market ignorance about the kinds of things of which free software is capable and how truly viable an alternative to the much more well-known commercial alternatives it can so often be.
The world of free software is only the richer for having multiple solutions to choose from, each with its own unique strengths and areas of coverage, and frankly, I wouldn't have it any other way. Jordan Hubbard jkh@FreeBSD.org, http://www.freebsd.org/
Now more than ever, I find Linux to be the number one operating system of choice for several reasons. Not only is its stability far superior to some commercially developed operating systems; the variety of applications available for Linux is exploding like never before. Its practicality for Internet access exceeds that of any other OS for the PC, and more hardware than ever is supported by it.
I'm the president of the Computer Society at Western Connecticut State University. The goals of the Society are to enlighten and inform its members and to create a common ground on which computer students, professionals, and educators can convene. To meet ongoing demand, we hold Linux discussions and demonstrations as frequently as possible. In addition, Linux is now being used as the primary teaching tool for the Operating Systems course. Not only are computer majors, professionals, and hobbyists alike using Linux as a primary operating system; even those less technically inclined are finding Linux suitable for everyday tasks.
My only question has been and remains: Why are we still not finding Linux distributions on the shelves of local software stores? Currently, I see it widely available at trade shows, expos, conventions, the computer sections of local book stores, and several other locations the general public does not go for software. So, while Joe or Jill Average shop around for new software to try out on their computers, they never see Linux. Why hasn't some company put Linux on the shelf where the light shines? Cory Plock 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!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- Returning Values from Bash Functions
- Parsing an RSS News Feed with a Bash Script
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