Letters to the Editor
In the April “Letters to the Editor” column, two people made comments about commercial applications for Linux. Every time I call a software manufacturer about an application, I ask if they have a version to run on Linux. If not, I ask them to put in a request.
I use Linux as my main operating system at work with Wabi so that I can use MS Office. Now that MS has upgraded Office, I am finding it hard to maintain this plan.
To convince more companies to build software applications for Linux, it might help to run a survey on a web site. The survey would find out how many people are running Linux, if they would be willing to buy software applications, and what price they would be willing to pay. The information garnered from the survey should be made public.
—David Hepner email@example.com
In response to Michael Scott Shappe, “Accelerated X Laptop Display Server v4.1”, March 1998 (Issue 47), there is a simple fix to the problem of the rightward-shifted X display on the Fujitsu Lifebook (and possibly other laptops with a Phoenix BIOS, where the problem arises).
Go into the BIOS setup, select “Advanced”, then “Video Features”, then “Compensation: Enabled”. The X display will now fill the screen (using either XFree86 or Xi), and you can run Linux in text mode. Windows (I boot both 95 and NT 4.0) will still work with no problems (other than the usual ones).
Some technical details of my laptop: Fujitsu Lifebook 435D, NeoMagic video card and Phoenix NoteBIOS 4.0. It boots Linux (2.0.30), Windows95, NT 4.0 workstation and the NT 4.0 server.
—Dr. Constance A. Stillinger firstname.lastname@example.org
I enjoyed Mr. Browning's article in the March 1998 issue, “Getting Rid of Spam”, on using procmail and the Alcor filters to catch spam. However, I think I've found an easier way to filter spam using procmail. I've observed that spammers seldom send mail to your personal mailing address; instead, they use a mailing list. So instead of seeing a header line like this:
I'm seeing lines like:
Knowing this, it is easy to write a procmail rule to catch it:
:0: *! ^To:.*email@example.com *! ^Cc:.*firstname.lastname@example.org /home/rsmit06/.incoming-mail/junk-mail
This rule catches virtually 100% of the spam I get. Unfortunately, it also catches the mailing lists to which I subscribe. The solution is to write rules that intercept the valid mailing lists and put them before the “spam-interceptor” in your .procmailrc file. This has two advantages: all mailing lists can be put in a separate folder, and virtually all spam is caught. The only disadvantage is adding each valid mailing list to your .procmailrc file. For me, this isn't a problem.
—Roland Smith, The Netherlands email@example.com
I feel compelled to correct Michael Babcock about what he wrote in his article “The Importance of the GUI in Cross Platform Development” (March 1998) regarding OpenStep. I have been a professional consultant for 14 years and have worked on most workstations, operating systems, languages and engineering paradigms.
I have been staying with OpenStep/NeXT Step/Rhapsody for some time now because it is, in my opinion, the best software development and deployment platform.
OpenStep is not simply a “GUI API (along with some non-GUI functions)...” as he puts it. The very use of the term “API” is misleading. OpenStep is an operating system based on a MACH microkernel, BSD UNIX and object-oriented frameworks, consisting of other frameworks (of objects and classes) for everything from graphics to distributed objects to enterprise computing. This is a radical departure from “APIs” like the ones he discusses in the article; they are not even in the same category.
OpenStep is a complete software solution that lets you write programs using its objects, or extending its objects, and can run on Intel, Motorola, SPARC and HP. Furthermore, the OpenStep OS and development tools run on Windows95/NT, MACH native Intel, MACH Motorola, MACH SPARC, Solaris and HP/UX. With Rhapsody around the corner, we can add Power PC to that list, and most likely Macintosh OS.
As for the complaint about learning ObjectiveC, I have to say that it is much easier to learn than Java and has a smaller linguistic requirement. The hardest thing to learn is that one sends a message to an object with “[object message:arg]” rather than “object.message(arg)”.
OpenStep has a lot of momentum behind it right now. Major Fortune 500 companies and many others have been using it for years. There is no need for “hype” in order to make this technology mainstream. It is a well-established technology that in my opinion could literally save Apple-NeXT. While I am prevented from disclosing details about Rhapsody, suffice it to say this is truly a next-generation technology. It is UNIX, too.
Finally, I wish to say that I applaud the efforts of the GNUStep developers; it would be very useful to have a version that is free, for which source code is available. My hope is that Michael Babcock does indeed get an OpenStep box, so that he can discover his vast underestimation of it for himself.
—Erik Scheirer, sonYx, Inc. 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!
- 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
- Doing for User Space What We Did for Kernel Space
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