Letters to the Editor
I have just received the April 1998 issue of Linux Journal. My highest regards for such an informative article as “Satellite Remote Sensing of the Oceans” by S. Keogh, E. Oikonomou, D. Ballestero and I. Robinson. My attention was held very closely by the details and explanations written in this article. I'm well aware of the problems in remote sensing systems, and the potentially enormous amounts of data which must be manipulated in order to make sense of it. This was great! Find more authors like them.
—Bill Staehle firstname.lastname@example.org
First let me congratulate all of LJ's editors. I am staying up hours to digest and learn all I can possibly read. It is really wonderful to have a chance to learn so much.
Here I am referring to “Writing a Linux Driver” by Fernando Matía. I find it to be a good foundation for device drivers. An added reference for anyone who would like to look into drivers further is Writing A UNIX Device Driver by Janet Egan and Thomas Teixeira (John Wiley and Sons, 1988). Even though it is for UNIX, it proves very useful for Linux. Thanking you and Fernando Matía.
I have subscribed to your wonderful magazine since 1995 and I have found it to be useful, informative and fair. But I must tell you my disappointment about your graphical user interfaces issue, March 1998.a) XView is old and passing out of favor, even though it is still useful.b) CDE is proprietary.c) TkDesk is nothing more than an elaborate file manager.d) GTK and GNOME are by no means ready for production machines.
You failed to mention the wonderful, useful, highly advanced KDE project (see http://www.kde.org/), despite the fact that it is in the beta three stage. I have installed it on production machines in radiological clinics under both Linux (x86 architecture) and SunOS. I wonder why you did not dedicate a few lines to a project like KDE—in my opinion, the only runner capable of stopping the wave of Microsoft's products. If libQT licenses are the problem, it is inconsistent with the presence of articles on all-commercial products like CDE and X-Designer/Motif, since libQT is free for free Linux development. Please reconsider this position and take a look at KDE.
Thank you very much for your consideration and keep up the excellent LJ--I love it.
—Daniel Benenstein email@example.com
There was no conscious decision on my part to snub KDE. In fact, I had a KDE article scheduled, but it came in after the deadline and the issue was already full. I plan to run this article in the near future. The May issue does have a short comparison review of both KDE and GNOME in the Linux Gazette column —Editor
The most elegant method for dealing with cookies is simply to symbolically link the cookie file to /dev/null, like so:
ln -s ~/.netscape/cookies /dev/null
This has the effect of accepting all cookies, so you are not denied access to any web sites, but immediately funnels them into a black hole. Having /dev/null “world readable” is infinitely preferable to disclosing your browsing habits to webbots.
—M. Leo Cooper firstname.lastname@example.org
I have been reading LJ (which I find very nice) for three months. I have learned different things (as I do from any journal), but I have also found some bugs. In the article “Ghostscript” by Robert Kiesling (March 1998), there are two points I do not agree with.
The author says that it is not possible to see .eps files included in LaTeX files with xdvi. I say: wrong. I use LaTeX2e and xdvi almost every day, and I can see the .eps files through xdvi. (I cannot zoom, but I can see what is displayed, which is usually enough.) The .eps files I use are generated by xfig and transfig.
The author says that gs used with device X11 will create a window. I have tried this, and the X11 device is not a default one for gs 4.xx. I can see my .ps files with gs, but I must use Ghostview as the GUI. I do not think that the programmers have taken the X11 device away from version 3 to version 4. Has the author made a mistake in his script files?
I am using Red Hat 4.0 (with a lot of patches and a Slackware-like installation) but my LaTeX2e, xdvi and Ghost(script/view) are original and standard ones, so I should be able to do what the author mentioned, but I cannot.
—Raphael Marvie email@example.com
I have to blame my use or installation of xdvi for the inability to print \special commands. The distribution on which the article is based has been upgraded several times now. I've received plenty of mail from TeXperts saying they have no problem with reproducing EPS graphics on screen.
The X11 driver is standard in every recent version of Ghostscript, but it is not necessarily the default. It can, however, be specified on the command line with the parameter -sDEVICE=X11. During the process of building Ghostscript, it and all of the other supplied driver code can be specified in the Makefile.
—Robert Kiesling 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
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
- 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