Letters to the Editor
Just got my comp copies today of the 3/97 issue. Thanks very much. It's always a thrill getting those first copies of a published work.
I am very disappointed on one count, though. My e-mail address was removed from the short bio at the end (page 72). All my esteemed fellow authors included their e-mail addresses, so I assume it was an unconscious mistake on some editor's part. (Not to excuse it; careless mistakes are the most preventable and least forgivable variety in my book.)
Funny thing is, I'm decidedly unimpressed with authors who avoid interaction with their readers. They abdicate the stewardship of knowledge their work otherwise earned them. Now I'm involuntarily guilty of this very sin. The main reason I write articles is to try to make contact with forms of intelligent and enlightened life out there. I missed my chance this time. I guess my lesson for the next time is to insist on a review copy.
In all other respects, it's been a real pleasure working with you folks. Mary Webber, by the way, is wonderful. —Bob Stein email@example.com
Much to my surprise, I found that in the article “A Point About Polygons” by Bob Stein in the March 1997 issue of Linux Journal, the code in Listing 2 (TESTPOLY.C) was specifically written for Turbo C and the DOS environment. As it was apparently coded back in 1995, one may assume that Stein has since discovered a more mature development platform, but I do hope this is not to be taken as a subtle shift of focus on the part of the editors of LJ. —Robert V. Schipper firstname.lastname@example.org
Thanks for writing, Robert.
You're quite right, TESTPOLY.C was for the Borland/DOS environment. At Galacticomm we've been using Borland's command line development environment for some time, and we continue to do so for both the DOS and NT versions of Worldgroup. So at the time, it was convenient, taking me only an hour or two to use.
If you're hoping I've seen the light and started using Linux I'm afraid I'll disappoint you. Lately I've been using Microsoft's Visual C++ and Sun's Java for graphics programming. I assume my article was accepted for its Websmithing theme [Yes, that's why—Ed.]. —Bob Stein email@example.com
I was reading the article titled “Setting Up UUCP” in issue 35, and noticed the author was wondering why his modem dials when there is no dial tone. I have discovered over the years that some modems return:
while others return:
NO DIAL TONE
So, including a line:
would probably solve his problem. —Scott Barker firstname.lastname@example.org
I am very disappointed that after twice sending information to you guys about my company (the second time was actually about a dozen copies of the same e-mail, sent every week or so until I finally got a reply), you still got it wrong. My company is MostlyLinux, but my entry in the Linux Journal 1997 Buyer's Guide lists me as “Calgary UNIX Users Group”, with my phone numbers, but with their snail-mail address instead of mine, and my e-mail address through them rather than through my own company.
This is going to cause confusion both for myself and the Group (with whom I volunteer, and on whose behalf I have dealt with SSC, which may have caused confusion on your part). I remain a loyal reader of Linux Journal (which I find very useful), but am very unhappy that I am going to have to deal with the problems this creates. For future reference, if you intend to publish another Buyer's Guide, please note that I am: —Scott Barker MostlyLinux, Inc. Voice Mail: 403-209-9406Fax: 403-285-1399E-mail: email@example.com URL: http://www.mostlylinux.ab.ca
We just received our copy of the Linux Journal 1997 Buyer's Guide. I feel this type of effort is very good for the industry. Craftwork Solutions is focused on making Linux an accepted commercial solution for businesses. We are glad to see SSC make the effort to explain to the general public the benefits of using Linux.
What did trouble me came at the end of the issue. Craftwork Solutions announced back in Sept/Oct '96 our 2.2 release for both the Intel and Alpha architectures. We were across the aisle from SSC at Comdex in November '96, showing our 2.2 releases. Unfortunately, your table included only the out-of-date information on our 2.0 product.
You made room for both the 3.0 and 4.0 releases of Red Hat. I would have expected that at least our 2.2 information would have been used! Craftwork Solutions has advertised with LJ since 1995. I would very much like to understand how this oversight occurred.
Your publishing of our old data makes us look like a company that is not concerned about the direction of the industry and not interested in providing the best product and support to its customers. I personally take that very hard. My staff worked long weeks during the summer to have the new releases ready for Comdex.
I realize the information we filled out for you back in May '96, reflected the 2.0 product. What confuses me is that the Red Hat 4.0 wasn't available back in May '96 either. Please explain to me how this mixup occurred, and how we can prevent it from occurring in the future. —Lee Morse, Chief Technology Officer firstname.lastname@example.org Craftwork Solutions, Inc.
- Android Browser Security--What You Haven't Been Told
- Readers' Choice Awards 2013
- Epiq Solutions' Sidekiq M.2
- The Many Paths to a Solution
- Nativ Disc
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Synopsys' Coverity
- Securing the Programmer
- Downloading an Entire Web Site with wget
- Naztech's Roadstar 5 Car Charger
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