Letters to the Editor

Readers sound off.
Why So Slow?

Questions:

1. How come your January issue is on the Web and I still haven't received my December issue? Did it get lost in the mail or am I impatient?

2. Can you put more articles on-line for us paying subscribers? I paid my dues and feel like I am due the flexibility of reading online or on paper, please.

—RSVPAdam Holt holt@mit.edu

“Circumstances beyond our control”

1. The December issue was mailed one week late due to a problem at our printers, which set back printing, and therefore mailing, by one week.

The Table of Contents is posted to the WWW and Usenet as soon as an issue is sent to the printer; printing and mailing take another three to four weeks.

2. We are working on putting articles on-line, but our first priority is putting the magazine on paper. If we don't get the magazine on paper, there won't be one on the WWW, either. We are not over-staffed, and right now many of the articles you see already on our site were html-ized by volunteers. Our goal is to have the entire journal on on the WWW, and we are working towards that goal by creating tools that will allow us to work simultaneously on the paper and WWW versions of the articles. But that's another project which competes for time with the all-important process of getting the articles on paper.

We understand that you feel that we owe you having all the articles on-line; but it's not something we offer as part of the subscription, partly because we don't have the resources to provide that service in a timely fashion. We would like to suggest that you compare the WWW service that we provide now, with a full, interactive index, many of our previous articles, and response forms all available, with what we provided a year (and less) ago—no WWW service at all. Please understand that we are growing, and increasing our level of service as we grow, but it takes time.

New Hungry Programmers Location

I'm just writing to give you the current URLs and e-mail addresses for the Hungry Programmers stuff that were mentioned in the Lesstif and Viewkit article in the November issue of LJ.

The URL for the Hungry Programmer's homepage is now http://www.hungry.com:8000/

The URL for the lesstif stuff is now http://www.hungry.com:8000/products/lesstif/

The URL for the lesstif documentation project is now www.hungry.com:8000/products/lesstif/Lessdox/LessTif.html

The URL for the viewkit stuff is now http://www.hungry.com:8000/products/viewkit/

The e-mail address for the hungry programmers is now hungry@hungry.com

The address for the mailing list is also different than what was published in the article. It is now majordomo@hungry.com.

—Thanks, Chris Toshok toshok@hungry.com www.cs.uidaho.edu/~toshok

Error found ...

An alert LJ reader, Robert Day, pointed out an error in the Find tutorial published in the December issue. The tutorial provided an incorrect example for using find to locate files with the SUID bit set.

The example was:

find / -perm 4000 -print

As shown earlier in the article, this command would find only files whose permissions are exactly 4000. The correct example is:

find / -perm -4000 -print

That's it.

______________________

White Paper
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions