Letters to the Editor
I just read your PageSat article. We've been waiting for our system for three months. Unfortunately if you dial the main PageSat number you get another number to call, 415-493-9592—which says PageSat is history, gone, no longer in service. (It was a good article anyway.)
It's too bad. I was eagerly waiting for this, since our Newsfeed is very poor. Do you have any other suggestions for an alternate newsfeed? Ed Longstrom firstname.lastname@example.org
Rich Myers, who wrote the article in question, recently sent us e-mail on this very question:
NCIT (aka Pagesat) has ceased operations effective 12/4/96. Norman Gillaspie is starting a new business, PC-Sat, to continue the satellite newsfeed for both current and future customers.
We should have a web page on-line by the time you read this. The location of the web page will be: http://www.pc-sat.com.
Would you please pass on this info to the interested parties?
Thanks in advance for your assistance! Rich Myers email@example.com
First let me say that I enjoy LJ very much and get a lot out of every issue.
I'm considering using Linux in some commercial installations and have held off because of a glaring omission in the networking subsystem. I can find no evidence of Linux support for the NFS lockd and statd network lock managers which are required to guarantee exclusive file access over NFS. Our application support software uses a shared NFS mounted file system and must have this to work. I believe the lack of this capability will impede Linux's acceptance in enterprise computing environments that depend on robust networking support. Other than that, it seems Linux offers the most bang for the buck for Unix computing and networking. Toby L. Kraft firstname.lastname@example.org
I read with interest your editorial (“The Politics of Freedom”, Phil Hughes) in the October 1996 Linux Journal, #30, and thanks for webbing Richard M. Stallman's letter for background. Will you entertain a comment from an outsider?
It's too bad the word “political” has such a bad flavor. Virtually everyone wants to make things better in his community (the polis) and tries to persuade others to cooperate in doing so, i.e., acts politically... the catch, of course, being how to decide what is “better”.
I don't use Linux. I make a living writing commercial software for commercial platforms. I have also written, published, and placed in the public domain a few utility programs. I did so for at least three reasons I'm consciously aware of (not necessarily in priority order):
to make useful tools available to others
to share my pleasure in solving a problem elegantly
to show off what a clever bugger I am
At least one of these motivations—the desire to benefit my fellows—RMS also feels. Perhaps he feels the others as well. Nothing wrong with any of 'em.
You suggest RMS “feels that everyone has to believe exactly the same things he does.” I read his letter somewhat differently.
First, let's dispose of the myth of “free” software. They ain't no sech animal. Even if you obtain it without exchange of valuta, you must still invest time and skullsweat to use it—both scarce and valuable commodities, perhaps more so than money. So, any system competes with all others for your investment, whether cash changes hands or not.
Perception is reality. If Linux and GNU do not share a name, they are more likely to be perceived as distinct rather than variants of the same thing (one of RMS's points, and I agree). If they are distinct, they compete.
And “free” software already competes with the notion “if it really was valuable, you'd be charging us for it”—as Heinlein pointed out, why do you think they take collection in church? Added competition between Linux and GNU can't help but drain both against the “common enemy”, which I think is what he is saying.
I'm sorry to have to disagree with Linus Torvalds, but it does matter what people call Linux, and this is why. Since Adam's day, to name a thing is to have power over it... and to be trapped by its paradigm.
(Insert clever pun about “Paradigms Lost” here. Oh, never mind.) That's my two pfennigs, anyway. Hope you enjoyed it.Davidson CorryDAVIDSCO@Attachmate.com
Phil Hughes points out RMS asked for and was offered the opportunity to respond, but so far, we've not heard from him.
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
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- SourceClear Open
- 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