Letters to the Editor
As a new convert to Linux, I am very satisfied with my subscription to LJ. I have comments about two of the articles in the July issue, one positive, the other less so.
Thank you for the avalanche predictor model by Richard Sevenich and Rick Price. It reminded me—at an optimal time—of the power and utility of fuzzy logic to many of the real-world problems we deal with on each project. I've applied fuzzy logic to a GIS (Geographic Information System) for land use decision making support. But, in the press of too many things to do and not enough time, I had forgotten about this powerful set of tools. Thanks to this article, I have a solution to at least one environmental problem which affects the mining industry. Since we use Linux, the model will be developed and run on this platform. If there's demand, we'll make it available on Windows 95, too, using Tcl/Tk for the user interface.
On a less positive note, I need to ask why Richard Parry's article on position reporting using GPS and ham radio was published. After reading the article, I still have the unanswered question, “So what?”
We use GPS data extensively in our field work. We use it to delineate wetlands, orthorectify aerial photos, measure mines and quarries for modeling of storm water runoff and reclamation planning, locate wildlife nests/burrows and other phenomena of the world out of doors. We also know that many surface mines use GPS technology to dispatch haul trucks and maximize operations, many police and fire vehicles are equipped with GPS/GIS systems for emergency response, and at least one long-haul trucking company (Schneider, with the orange tractors and trailers) uses the technology to increase their efficiency, customer service and driver satisfaction. Given all this, what is the value of having one's vehicle location transmitted to a network of amateur radio stations? I was a licensed ham operator (many, many moons ago), so I'm certainly not belittling them.
What I'm saying is that this article appears to be more of a reporting on, “we know how to do this, so we will,” than a solution to a real problem. If I've missed something in the article, please do let me know. Each of the other five articles related to the issue theme report how Linux facilitates solving a problem. This one article doesn't appear—to me—to fit that mold.
Regardless, kudos are due to all of you for a very useful information source (including the ads). I'll be buying a SCSI adapter from one of your advertisers tomorrow, since my relatively new (but shortly out of warranty) HP/CMS tape drive has decided to die.
—Dr. Richard B. Shepard firstname.lastname@example.org
I thought Mr. Parry's article was fun; not every article needs to address a “real” problem. If I had a GPS article describing some of the ways it's used that you mention, I'd have been happy to publish it too —Editor
In the “Best of Technical Support” column in the July issue, Mark Bishop responded to a question titled “Editing motd and issue”. Mr. Bishop forgot to point out that the Slackware distribution, by default on startup, overwrites the /etc/motd and /etc/issue files. To change this, one must comment out (#) the commands that overwrite the /etc/motd and /etc/issue files. Check out the /etc/rd.d/rc.local (I think) file in Slackware to make the changes. After doing so, you can edit the /etc/motd and /etc/issue files without fear of them being overwritten.
—Andrew Dvorak andrew_dvorak@IName.com
You have contacted me about the Slackware distribution overwriting on bootup. Not all distributions do this, however, and I believe that hasn't always been the default behavior of Slackware. I wish I had the time to keep up with all the distributions, and I plan on installing Slackware on my new machine now that a new version has been released (too bad it's not based on libc6). Thank you for pointing out that not all distributions are created equal.
—Mark Bishop email@example.com
I am writing in response to Dave Lutz's (firstname.lastname@example.org) letter on removing files and security. In it he discusses security issues presented by IRC and lynx, along with “hacker flags”.
He discusses how IRC is a security risk. IRC has been around for many years, and is the main form of chat used by people on the Internet. The act of being on IRC does not become a security risk. He cites the trading of “warez” and pirated software as an example. Web pages and other forms of chat are used to spread those, and they are not security risks. He also mentions the “eggbot”. The proper name of this is “Eggdrop”, and as one of the developers of this program, I can assure you that, if properly configured, the bot poses no security threat.
His letter also mentions how lynx can be used to bring in malicious files. Any program that can transfer files, be it ftp, mail, lynx or IRC, can be used to bring in files. Disabling them is not the proper way to secure a system, as this only hides the problem—it does not solve it. Several key issues should be looked into when securing a system.
One of the main issues would be setuid root programs, that is, programs which run under root permissions. Several distributions, especially older ones, come with setuid root programs which can be used to gain root access on the system. These include SuperProbe, xterm and others. The command find / --perm +4000 can be used to list setuid root programs. If a program doesn't have a specific need to be root (try chmod a-s program and run it as a normal user), you should probably remove the setuid bit to be safe.
Several security lists are available which detail security problems as they are found, one of the main ones being Bugtraq. To subscribe, send mail to email@example.com with “subscribe bugtraq” as the subject.
Once again, security through obscurity can work for only so long. If the person wants into your system, the methods described by Dave will not prevent them from getting in.
—Jason Slagle 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!
- Google's SwiftShader Released
- 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!
- Interview with Patrick Volkerding
- 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