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 email@example.com
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 firstname.lastname@example.org
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 email@example.com
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 firstname.lastname@example.org
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 email@example.com
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- August 2015 Issue of Linux Journal: Programming
- Django Models and Migrations
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Huge Package Overhaul for Debian and Ubuntu
- Shashlik - a Tasty New Android Simulator
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile
- diff -u: What's New in Kernel Development