I was very impressed with the September 2001 issue of LJ. The new look is great. It even seems the writing is more professional in these last two issues than it had been in the past. I initially thought this issue was the best I'd read! But the October 2001 issue is right up there, if not better! I had considered dropping my subscription to LJ because the articles read too informally. I don't know if that makes sense. But these last two issues have been excellent! Keep up the good work.
I must say that overall I like the new format of Linux Journal. I am disappointed, however, in the reduced content of the UPFRONT section. I really enjoyed all the quotes and odd statistics in the old format of the UPFRONT section. I hope that the lack of these items in the September 2001 issue is only a temporary condition.
Not to worry, John—the amount of UPFRONT content varies somewhat month to month.
I could not resist trying the small driver from the article “Loadable Kernel Module Exploits” (LJ, September 2001). But there were some problems: 1) there are too many headers in Listing 1, 2) char * temp_buf is unused, 3) wrapped_write() should stick whether to “n” or “count” as one of its parameters and 4) wrapped_write I would put as wrapped_write(int fd, void *buf, size_t n).
I liked the idea about replacing all “Linux sucks” phrases to “Linux rules”, so I tried to implement it. I extended the wrapped_write function to do such a replacement. The function strstr() gave me problems while compiling, and I did not find an implementation of it on my Mandrake 8.0 laptop. “extern strstr” was everywhere. So I used a simple loop with strncmp(), and it proved to be more useful because it can replace several occurrences of a phrase. To do so and please the compiler, I removed “const” from the wrapped_write() parameters to write back to “void *buf”. Also, I had to change the linux/version.h file because I had compiled the kernel myself, and insmod was swearing at the difference. But in the end when I had succeeded, I really enjoyed playing with such a kernel module: whenever I tried to type that dirty phrase it was immediately replaced. I tried some editors, sent naughty e-mails to myself and so on...great! Thanks a lot to the author; now I agree with Linus Torvalds: the real purpose of Linux is to have fun.
I would like to express my strong agreement with Daniel D. Jones, whose letter you published in the October 2001 issue of Linux Journal. The French chef gag employed in Marcel Gagné's Cooking with Linux column is irritating and tiresome. While the content of the column is of some value, I doubt I'm alone in finding the style annoying and unhelpful.
I look forward to my monthly visit to Chez Marcel. His topics are always interesting, his explanations have that extreme French lucidity, and I live in hope that François will pour me some of that Chambertin 1998. Perhaps Mr. Jones has a touch of the mal de mer, non?
—Peter P. Chase
“El Cheapo Linux” Mr. Rosen? Come on. How about “CheapLinux”? Living next to a major city like San Francisco in the state of California, I guess one just starts speaking Spanish without realizing it. A Spanish name does not imply low quality. But are you sure you haven't stepped on some legal toes using the name El Cheapo Linux? Google finds 2,440 pages with El Cheapo Linux.
—Steven M. Ruiz
Rosen replies: Mr. Ruiz, I'm sorry you took offense at my Spanish-sounding name for Linux. I suppose I could have used the made-up mark “Cheap Linux” to make the point that a trademark eventually becomes associated with a product and conveys many marketing messages based on the meaning of the words in common parlance as well as the mental associations created by advertising dollars. I didn't have to go to Spanish for that point. I used a foreign-sounding mark for another reason, although I failed to explain the reason in my article. (There is only so much one can say in about 500 words!) Many people assume that translating a trademark into a foreign language (or foreign-sounding language) will help them avoid trademark infringement claims. The law doesn't work that way. I doubt the US Trademark Office would allow registration of Manzana computers, or Linux Sombrero Rojo, or that Apple Computer or Red Hat would stand idly by while those marks were applied to competing goods. I suppose I could have chosen more precise Spanish (Linux Barato), French (Linux Vulgaire) or German (Linux Billig) for my example. Perhaps then someone else besides you would have taken umbrage, or I could have escaped without criticism at all. I did a quick Google search on “El Cheapo Linux”. Indeed there are many hits. But my quick scan found none that would qualify as a valid trademark. (That's a relief!) It appears that, even were a person to seek trademark registration for that mark, it would be disapproved as being merely descriptive, or perhaps now, generic. For what it is worth, I meant no disrespect. I represent a number of Spanish-speaking clients, I do pro-bono work for nonprofit Hispanic groups in the Bay Area, and I even lived in Guatemala when I was a child. So I'm not trying to sound like I'm disparaging your language (or any language) or the people who speak it.
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
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
- 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